Forum Home › Forums › Communicating with Devices › Modbus › Evento de perda de comunicação – Rapid SCADA 6.2.2
Tagged: Alertas, Comunicação, modbus
- This topic has 38 replies, 3 voices, and was last updated 1 month, 1 week ago by
Mikhail.
-
AuthorPosts
-
March 3, 2026 at 8:53 pm #17714March 4, 2026 at 12:54 pm #17717
MikhailModerator“Error saving the Scripts table” is so weird. How to reproduce it?
March 4, 2026 at 12:55 pm #17718
MikhailModeratorIt’s possible to use Auto Control Module to react on channel change with a delay. Perhaps, it is easier to configure the module via UI, because formulas are not needed in that case.
March 5, 2026 at 12:08 pm #17724isabellacog
ParticipantHello,
When I created the script, my server stopped working. The errors that appear are the ones shown in the image.
https://imgur.com/XqFxH9t script
https://imgur.com/ohZxCGY errorI tested both the TON script and also a very simple formula using Val(), and the same problem occurred.
I am able to save the script in Administrator, but when I deploy the configuration, the server stops running and those errors appear. I didn’t even create a channel using the script yet — the problem happens just by having the script in the Scripts table.
If I delete the script and deploy again, the server starts running normally.
So it seems that any script added to the Scripts table causes the server to stop after deployment, even a very simple one.
Do you know what could cause this behavior?
Also, regarding the Auto Control Module solution: how would that work in this case?
Do I need to install or download this module, or is it included by default?I would still like to understand and fix the script approach, because I want to learn why it is not working in my project.
Thank you!
March 5, 2026 at 12:40 pm #17728
MikhailModeratorHello,
Definitely, in the script should not be any XML tags.
It is a good practice to check ScadaServer.log after uploading the project if scripts were changed.March 6, 2026 at 6:34 am #17729
manjey73ParticipantAn XML script is the result of an export from a script table. It needs to be imported, not copied as it is. XML is saved in UTF-8 format, so there should be no errors due to the operation of the site, etc.
March 18, 2026 at 5:14 pm #17757isabellacog
ParticipantHi,
I managed to get it working by importing the script — thanks for the guidance!
Now I have a question about the Beep functionality. I configured the channel events by enabling: 0: Event enabled, 1: Event beep, and 3: Channel data has changed. However, the beep only sounds once.
Is there a way to make it beep repeatedly until an operator acknowledges the alarm? Something like a continuous or repeating beep until acknowledgment would be ideal for our use case.
Has anyone implemented something like this?
March 19, 2026 at 6:37 am #17761
manjey73ParticipantIf you have a Windows system and the Server is both an operator’s computer, then you can use the sound module.
If Linux or everything is separate, the web client connects remotely. The option is to use the Auto Control Module and somehow play with scripts. Another option is to add your own html page with sound to the i-frame on each page and show it when there are events, and then use a script to repeat it. In general, I have not tried these options in any way. Maybe the developer will tell you something.
March 19, 2026 at 1:42 pm #17762
MikhailModeratorPlease create a new topic for the different question.
-
AuthorPosts
- The topic ‘Evento de perda de comunicação – Rapid SCADA 6.2.2’ is closed to new replies.