Tagged: communicator MODBUS
December 25, 2020 at 3:44 pm #7845
I recently did a completely fresh install of Rapid SCADA v. 220.127.116.11.
The goal was to reproduce a known MODBUS-TCP configuration used on a different computer being retired.
For some reason I cannot get the Administrator application to “Save” the Request Sequence information. It is always lost even after UPLOADING a saved configuration.
The Communication Lines/Line Parameters/”Request Sequence” row is saved but the associated xml “Request sequence” information itself is lost each and every time I leave the configuration screens (even after making sure to UPLOAD the request sequence changes to the server).
When I return to the Request Sequence edit screen and hit the “Properies” [sic] button, the Administrator application always presents me with the default “KpModbus_NewTemplate.xml”(empty) request sequence information. The actual edited/saved .xml configuration file IS saved as a text file in the project folder, but its filename is NOT placed in the “Command Line” field and its association with the “Request Sequence’ row saved to the configuration database is always lost. Even if I manually place the name of the newly edited xml file in the “Command Line” field, save the config to the database, and then come back to editing the communication line, when I hit the “Properies” button, I am again presented with empty “KpModbus_NewTemplate.xml” XML (via GUI) file contents.
Thanks for your help.
https://photos.app.goo.gl/7m9MoTyGm1ig95yBA Communication Line Command Line/Request Sequence Not SavingDecember 26, 2020 at 7:53 am #7851
Could you update Rapid SCADA to the up to date verion 5.8.2? May be this problem will be solved by the update.December 26, 2020 at 3:03 pm #7854
Sorry, it appears that I DID download and install the latest version of Rapid SCADA 5.8, but when I looked for the version I had installed before posting this issue, I used the “About” button for the “Administrator” sub-application which displays 18.104.22.168.
The installer/uninstaller does show v.5.8.December 28, 2020 at 9:05 am #7863
Administrator 22.214.171.124 is included in Rapid SCADA 5.8.0, but the current version is Rapid SCADA 5.8.2. See the version history for the details.December 29, 2020 at 5:45 pm #7878
I could not find any way to easily determine which version of Rapid SCADA is installed. Might be nice to have the “About” feature of the Administrator application show the versions of the overall product as wells as the modules. Just a thought.
In any case. I DO have the latest version of Rapid SCADA installed and this does appear to be a bug in version 5.8.2. Would be interested to know if you, or another, can replicate the issue on your end.
I UNinstalled v.5.8.2, INSTALLED 5.7.1, which I had downloaded some time ago, and the problem is gone.
Many thanks.December 30, 2020 at 10:18 am #7888
I could not find any way to easily determine which version of Rapid SCADA is installed.
Rapid SCADA contains many applications. A user can upgrade them separately. The easiest way is to keep the downloaded installation package.December 30, 2020 at 10:20 am #7889
5.7.1 is too old. I suggest to install v5.8.2 that includes Administrator 126.96.36.199.December 30, 2020 at 5:21 pm #7897
Yes, agreed but then we are back to the beginning of the issue where this “not saving/associating the Request-Sequence XML file (template) with a device” problem appears to exist with the “latest” version v5.8.2 of Rapid SCADA.
If anything, just curious to know if you can reproduce the issue I am seeing in v.5.8.2.
Thanks.December 31, 2020 at 10:17 am #7898
This bug is really strange. You are the first who faced it. Could you provide some screenshots to show the sequence of steps before the problem?
- You must be logged in to reply to this topic.