Forum Replies Created
-
AuthorPosts
-
MikhailModeratorHi,
There is no such option. Units are displayed inside a popup when you move a mouse pointer to an item icon.
MikhailModeratorHello,
1. Add a button on a scheme.
2. Set the Action property to Send command.
3. Specify an output channel that needed to send command to a device.
MikhailModeratorStarting scripts feature requires development of a module for SCADA-Server.
MikhailModeratorHi,
Adding custom text to events requires additional development. It’s better to implement this feature in Rapid SCADA 6 in the next year. However, we can do it earlier in the version 5 according to a contract.
MikhailModeratorHi,
Check the editor settings that a default browser is selected.
I recommend editing Rapid SCADA projects on Windows then upload them to Linux.
In the future, Microsoft doesn’t plan provide .NET Forms on Linux Desktop, so the full editors will be on Windows, and may be we will provide a simple web editor.October 5, 2020 at 11:53 am in reply to: BadIdentityTokenInvalid error when accessing Node OPCUA server #7350
MikhailModeratorThis means that likely it’s possible to make the driver work with different security levels. Because the driver uses the same OPC UA libraries. Debug needed.
October 2, 2020 at 11:57 am in reply to: BadIdentityTokenInvalid error when accessing Node OPCUA server #7344
MikhailModeratorI can connect to Node OPCUA server now without modified source code.
Good.
I can connect with every 7 combination supported by Node OPCUA from UaExpert dan Prosys including “None and None” but only “Sign & encrypt and Basic256Sha256” with KpOpcUa.
Interesting. Could you also try this official utility made by OPC Foundation? The source code of the utility is available on OPC Foundation’s GitHub if needed.
MikhailModeratorHi,
The notifications are based on the events in the archive.
Probably, you should untick the “Event on Change” property of the input channel.
MikhailModeratorHi,
Write to the bot:
/infoIf it doesn’t answer, check the communication line log in Communicator.
MikhailModerator<Statuses>612</Statuses>– you should put statuses there, not channel numbers. Look for the existing statuses in the Event types table.<ParamIDs>11</ParamIDs>– may be it’s better to set empty string inside.October 1, 2020 at 10:05 am in reply to: BadIdentityTokenInvalid error when accessing Node OPCUA server #7335
MikhailModeratorI’ve copied my answer from GitHub:
Thank you for the pull request, but I can’t merge it because of the following:
1. Pull requests in this repository should be targeted to the develop branch.
2. Removing the lines makes impossible to apply the corresponding configuration options.
3. You should try changing the device configuration in KpOpcUa_XXX.xml to use the correct SecurityMode and SecurityPolicy.Please try the 3rd item and let me know about the result.
MikhailModeratorHello,
Please make a screenshot of the Input channels table where we can see the mentioned channels.
MikhailModeratorHi,
This is a good idea. I also thought about this feature. Hope, we will find a sponsor to implement it.
MikhailModeratorI’ll open a new thread about this problem later.
OK.
MikhailModeratorUsing Moxa NPort, I prefer TCP server or TCP client mode.
-
AuthorPosts