March 1, 2017 at 11:04 pm #1973
I’ve downloaded the Chart Pro plugin in order to see if it is what I need for my project. but I’m having a minor issue with activating the plugin on my web application. I’m using Rapid SCADA v220.127.116.11 and firefox is my browser for the web application.
Step 5 and Step 6 state consequently “Login the web application and go to Main Menu > Plugins” and “Find the Chart Pro plugin on the page and click the Activate link.” However, I cannot seem to find it anywhere. Here are screenshots of the the interface and the plugins available in my browser.
I would appreciate it if you can help me with this.March 2, 2017 at 6:11 am #1974
The current version of Chart Pro plugin is compatible with Rapid SCADA 5.
I highly recommend you to update Rapid SCADA to the new version.March 2, 2017 at 9:39 am #1975
The thing is I already set up the system with this version of scada and have been retrieving readings for about a month. I don’t want to lose all this data I already collected. Plus I’m not sure if my designed scheme is compatible with the new version.
So, if there is a way to keep all my readings while being easily mapped to the new configurations that would be OK. Else I think I should purchase an older compatible version.March 2, 2017 at 12:13 pm #1976
You can save all the data.
It is possible to upgrade softly:
1. Install only the new web application using other virtual path name.
2. Specify the views into the configuration database as written in the current version of manual.March 3, 2017 at 1:21 pm #1982
I did like you suggested but for the installation to be successful it required me to clear the SCADA-Web directory. I chose ‘SCADA5’ for my virtual path name. However, whenever I try to login the SCADA application from my browser, ‘server not available’ message always appears.
One more thing concerning specifying the views in the configuration database, the ‘interface’ tab in the SCADA-Admin has different columns from the one currently in the manual. I think that may not be inter operable with the new WebStation.
Suggestions ?March 3, 2017 at 2:55 pm #1983
Sorry, my advice was not fully correct.
You can manually install Webstation into C:\SCADA\ScadaWeb5 and give a name Scada5 for the website.
Use this manual in the part describes web app installation.March 3, 2017 at 2:56 pm #1984
Columns just change their display names, but were not changed in the database ))March 3, 2017 at 5:28 pm #1986
I did exactly as you advised but still ‘Server is unavailable’ message appears when i try to log into the web application. I’am posting the SCADAWeb log below in addition to two images one for the defined interfaces in the configuration database and the other for the defined web application in the IIS management console.
2017-03-03 19:10:39 <TOSHIBA-PC><DefaultAppPool><ACT> Connect to SCADA-Server “localhost”
2017-03-03 19:10:44 <TOSHIBA-PC><DefaultAppPool><EXC> Error connecting to SCADA-Server: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2017-03-03 19:10:44 <TOSHIBA-PC><DefaultAppPool><ACT> Disconnect from SCADA-Server
2017-03-03 19:10:44 <TOSHIBA-PC><DefaultAppPool><EXC> Error refreshing the tables of the configuration database:
Scada.ScadaException: Unable to receive the configuration database modification time.
2017-03-03 19:10:44 <TOSHIBA-PC><DefaultAppPool><ERR> Unable to connect to SCADA-Server. Try again.
2017-03-03 19:10:44 <TOSHIBA-PC><DefaultAppPool><ERR> Unsuccessful login attempt: admin – Server is unavailable. IP address: ::1March 4, 2017 at 6:51 am #1989
Does the old version of the web application work well or not?
Is the connection between Sever and Communicator established?March 4, 2017 at 7:57 am #1990
Yes and yes.March 4, 2017 at 1:25 pm #1991
Open WebSettings.xml of the new Webstation and check CommSettings section.
I recommend to test migration on clear virtual machine.March 8, 2017 at 9:07 am #2002
Yeah that did the trick. The new Webstation was not configured to run on the same port number as the server.
Thanks a lot.
- You must be logged in to reply to this topic.