Forum Replies Created
-
AuthorPosts
-
MikhailModeratorHi,
The topic called “Webstation error”, but the error is displayed in Communicator. You should check the Communicator log file.
MikhailModeratorHi,
Probably the error is caused by version mismatch.
Check the current version of SCADA\ScadaAdmin\ScadaCommCommon.dll
MikhailModeratorHello,
Byte order is set in the template options https://ibb.co/9wWZHG4
Could you make a screenshot of the settings and the error?
MikhailModeratorHi,
The last question is off topic. Please post in the appropriate thread.
MikhailModeratorInstance configuration is stored in *.rsproj file. You should open a project file in a text editor and check what is inside.
If instance content is disappeared, probably the project file has been damaged. You should take the project from a backup copy.
MikhailModeratorYou should check the log file of the module. Select Modules in the log filter combo box.
MikhailModeratorCurrently it does not work with ulong data type. We should add this option in the future.
MikhailModeratorByte order in the Modbus template is 76543210
MikhailModeratorHello,
I managed to make it work:
https://ibb.co/82BgRvJ
https://ibb.co/7nHQ7Hn
https://ibb.co/sb4vvyk
https://ibb.co/m4MdhqY
https://ibb.co/GTG0P8Z
MikhailModeratorHello,
You should check log files of the module.
MikhailModeratorHi,
Rapid SCADA 6: Create new formats in the Formats table. Use the created format for a channel. See Off-On as an example.
Rapid SCADA 5: the same, but add new rows to the Units table.
-
This reply was modified 3 years ago by
Mikhail.
MikhailModeratorIn logs you can find timestamps of all command steps.
MikhailModeratorHi,
A command goes the following way: Webstation – Server – Communicator – Device.
Using the logs, analyze why it takes too long.
May be a command waits while Communicator ends a current polling session.
MikhailModeratorHello,
Could you make screenshots of the channels, Modbus template, and device data (in Communicator)?
MikhailModeratorHello,
Could you try the following:
1. In Modbus template change element’s data type to ulong (8 bytes)
2. Update channel data type to Integer, and set channel format to Hexadecimal
This can help to check the actual channel values. -
This reply was modified 3 years ago by
-
AuthorPosts