Forum Replies Created
-
AuthorPosts
-
MikhailModeratorHi,
According to the Modbus specification, in the response
00 00 00 00 00 06 02 01 02 88 02
06 is “Number of following bytes”. You can see only 5 bytes after 06. So the response is not correct.The correct response would be 00 00 00 00 00 05 02 01 02 88 02
I think, Simply Modbus doesn’t validate the incoming data.
Do you have any idea why the device sends incorrect Modbus packages?
MikhailModeratorHello,
Please clarify your question.
MikhailModeratorI suppose, you should install and switch on the Chart Pro plugin. It is used by Dashboard if a chart contains more that 1 input channel.
MikhailModeratorThe example of using the API.
MikhailModeratorHi,
Find the API here. The descriptions of the methods are included in this file as comments.
MikhailModeratorHi,
1. No. Don’t use the previous versions of Rapid SCADA. Install the actual.
2. Yes, you can.
Note: Rapid SCADA doesn’t officially support Windows XP and it is not tested on XP, but it should work most likely. The web app have to be installed manually.
MikhailModeratorHi,
Unfortunately, the link to the image you provided doesn’t work. Can you post the correct link?
MikhailModeratorHi,
The device sends not enough bytes: Receive (4/5). 5 bytes expected in the second part of package according to Modbus standard.
You can analyze packages using http://modbus.rapidscada.net/
If ModbusPoll can show communication protocol, let’s compare with Communicator.
MikhailModeratorSet the properties:
Action = Send command
Output channel = output channel number that you already created in Administrator to turn on/off a relay.
MikhailModeratorHello,
Please provide the additional info:
1. Screenshot of Modbus template
2. Screenshot of the values that you receive (Device Data tab in Communicator).
3. What values you expect?Probably, you should try different order of bytes (in Modbus template) to decode floats. For example, 2301
MikhailModeratorHello,
Computer code is shown by commercial plugins. First of all, you need to install the plugin. If you do not use commercial plugins, you don’t need any key.
MikhailModeratorHello,
This is a known bug. It relates to the web server XSP4 that is used on Raspberry.
Fortunately, there is a workaround. The idea – creating 2 instances of Webstation to local and remote access.
How to:
1. Copy the files from /opt/scada/ScadaWeb/ to /opt/scada/ScadaWebRemote/
2. Grant access to the copied files.
3. Register the web application:
sudo mono-xsp4-admin add –path=/opt/scada/ScadaWebRemote –app=scadaremote
4. In case of using SD card, protect it by moving the created folder to RAM.
5. Open http://Host name or IP address:8084/scadaremote
MikhailModeratorHello,
Try the following:
1. Restart Raspberry Pi
2. Do not open Webstation locally after restart, but open Webstation from the Internet.
Does it work?
MikhailModeratorAlso you can deploy 2 instances of Rapid SCADA: on the remote and on the office server, and connect them using the new Rapid Gate module.
MikhailModeratorHi Mat,
If you prefer to keep the existing app unchanged, you need to create a module which will pass data from your custom server app to Rapid SCADA. You should use ScadaData.dll written in C# to integrate. See http://rapidscada.org/integration-with-rapid-scada/ “Second Way. Interaction Over TCP”
The other approach is replacing the remote app to Communicator and export data from Rapid SCADA to 3rd party systems.
-
AuthorPosts