Forum Replies Created
Maybe you should train your Rapid SCADA engineers and become our partner in India.
How should I change the source code?
It would be a huge change of source code. Otherwise, we got rid of this limit long ago.
The v6 will support more channels.
If string values are static, it’s possible to return a number from SQL request and then display it as a string (for example, Off and On values).
it seems only a few characters is obtained, not the whole string value
It supports 8 Latin characters per input channel.
Actually this statement would get a result set,but only the first record is shown, the following records are missing.
You right. The idea of the driver is to get a single row of current data.
If you need to update the existing driver to be able to get data from a row set, we could discuss the requirements and cost.May 6, 2021 at 1:11 pm in reply to: Communication Line bound to server signal limitation #8874
Thank you for the info.
the signals sent to server seems to be uncertain when the limit is exceeded.
It’s because of integer overflow. 5001 signals would send 319 items.
Thanks for the images. Interesting case.
Probably, it’s needed to add a home folder with ID = 1. And the Overview scheme is inside the home folder with ID = 2.
We should implement a possibility to move a tree node as you shown in the future.
if we can solve problem with formulas and events there is plan to test on some real project where SCADA would be accessible from outside our LAN and we would monitor location in some other company
Nice. I’m sure that all the mentioned issues can be solved. And I’ll help.
Please wait a bit when we upload the driver update. The update will provide more details about received topics in the log.
Then we should compare the driver with another MQTT client that is installed on the same machine as Communicator and subscribes the same set of topics.
About the formulas:
You should change channel type to “Real”. In this case, formulas are calculated when new value is coming from a controller or MQTT broker.
Could you provide links to the screenshots? Screenshots are more clear than text descriptions, so we could find the solution faster.
Note: the MQTT driver update is coming soon. The driver will support generating of input channels according to the configuration, and JSON parsing will be improved.
As you can see on my images I have two formulas
I don’t see any images that contains formulas. If you add them, I will check.
Value is all the time the same as in communicator
As wrote above, the result of formulas can be displayed by views, not in Communicator.
I also noticed that Rapid SCADA takes quite some time to read data from Mqtt broker. When around 80 variables is published to Rapid SCADA it takes more then 1 minute to show all the data.
Could you provide more info about that?
If we choose Rapid SCADA for our projects can we count on official support or is Mqtt community developed and so unofficial?
We also support the existing MQTT driver.
I recommend to update the file structure on disk as you need to show in the tree
Root SiteA NewFile.sch
In the title column just enter simple titles.
You can also set Title = Root\SiteA\Option1 but it’s not clear when not reflects file structure.
Is it possible to use formulas for input channels that are using MQTT?
Formulas are processed on the Server application level and they do not depend on a driver.
The result of formulas can be displayed by views, not in Communicator.