Forum Replies Created
-
Posts
-
In Rapid SCADA all data uses UTC timestamps. Some databases (like PostgreSQL) have special data type to work with timezone, some databases don’t have such data type.
If actual timestamps always differs by timezone offset, it’s OK and can be corrected in the SQL request.Hi,
I recommend use the same Tag Code and Topic parameters.
You don’t need to create commands under the Command node.
If a subscription is created and not read only, a value can be published.I suggest trying broker.mqtt-dashboard.com for testing.
Hello,
Could you add a screenshots of Device 4 Properties – Options?
If you try the same on public broker broker.mqtt-dashboard.com, does it work or not?Hello,
Currently, the MQTT driver doesn’t support strings. It’s possible to implement in the future.
Strings are supported by OPC UA driver, for example.If device communication was OK, and then the device become unavailable, the device data in Communicator should be changed to
---. If not, let me know and provide communication line log.In your screenshot, “On normalization” checkbox is set. Likely, be the message was sent when value became normal.
Hello,
I checked the source code: {CnlVal} variable should show a value that caused the trigger to fire. Could you create a simple project based on HelloWorld to reproduce the issue using data generated by simulator?
Note: the issue should be also occurred in Rapid SCADA 6, because any new changes are made in the 6th version.
Hi,
After the connection is established successfully, you will get new data when topics change, and the device status will change to normal. New data will be written in communication line log.Hello,
1. Yes, the driver converts all MQTT data to double. You can set data format to display in channel properties. It affects web interface.
2. Convert time to number of milliseconds in JavaScipt. Then it’s possible to convert it to date and time using channel formula.
Hello,
This forum is in English. For using Russian, please write on https://forum.rapidscada.ru/
