I don't recommend using 'Communication Manager'. Under 'Communication Manager', the 'NodeId' type of OPC UA can only be of type 'OPAQUE'. This will bring compatibility issues to the development of the upper computer.
This seems to be because when creating 'OPC UA' with 'Communication Manager', the 'IdentifierType' of 'NodeId' cannot be configured as' String 'type. This issue is not an isolated case. For this issue, CODESYS seems to have not provided guidance to users on how to proceed. We can provide feedback on this issue in the 'My Question' section of the 'CODESYS Store' to make CODESYS take it seriously.
I have the same problem, it seems like there is no solution.
CODESYS IDE is not a modern IDE. Its interface is ugly, its operation is not user-friendly, its functions are lacking, its feedback is slow, and its development is not good enough. In fact, CODESYS is a helpless choice under the current situation. But this situation will not last long. For example, SIMATIC AX is a strong competitor of CODESYS, which is more open and inclusive.
You should use this method: VAR NULL:REFERENCE TO FB_MSG END_VAR Add_EVT_OUT REF= NULL;
It seems that there is no solution to this problem.
Dear, When I use "__NEW" to dynamically create the object "Object_1", and assign this object "Object_1" to another object "Object_2". At this point, I use "DELETE" to release the object from "Object_2". At this time, I cannot judge whether the object has been released normally through "Object_1" (in fact, the object has been released theoretically). Thanks for you help.
Memory addressing is measured in bytes, with BOOL occupying one byte. BIT is quite unique as it occupies one bit. So, try not to use BIT in the program. You can use the Unpack function to solve your problem.