Forum Replies Created
-
Posts
-
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/Hi,
RecursionLevel is used by Auto Control module to avoid infinite command loop.
When the module processes incoming commands by command triggers, it ignores commands having RecursionLevel > 10.
RecursionLevel > 0 for commands that are sent by Auto Control module.
10 is a constant hardcoded in the module.Hello,
> how you link the connectors to the same channel
Use external file sharing like Google Drive or https://imgbb.com/> I don’t understand the procedure since there is only one file in the program
I mean that you should deploy additional Rapid SCADA instance on virtual machine that includes Agent and Communicator. This instance also contains ScadaAgentConfig.xml1. Setup the 1st Communicator as usual. It will server GPRS channel.
2. You need to deploy the 2nd instance of Rapid SCADA that includes Agent and Communicator services. You can deploy it on the same machine or on another machine.
Is it convenient for you to use another (may be virtual machine) for testing? It allows to install Rapid SCADA by the installer. Do you use Windows or Linux?3. On the 2nd instance, edit ScadaAgentConfig.xml. You should change Default instance to new instance name.
4. In your Rapid SCADA project, add a new instance and configure the deployment profile to be able to upload the configuration to it.
When the above is done, configure the 2nd Communicator to use TETRA.
Be free to ask follow up questions. Provide screenshots to explain possible questions.
