Forum Replies Created
-
Posts
-
Hi Marek,
info… is the correct email, but I haven’t receive a message from you. Can you send it again, please. Usually I reply within a day.
According to my experience with Win 10 IoT, it is impossible to install usual release of Rapid SCADA to this OS. The cause is that Win 10 IoT has no “normal” .NET. The applications must be written as Windows Universal Application. More over, and the biggest problem that Win 10 IoT doesn’t include web server to deploy the web app of Rapid SCADA.
May be something changes after I experimented with Win 10 IoT. It would be great, if you share you experience.
Hi,
You can also use BitConverter.GetBytes as a formula of an output channel to convert a number into array of bytes:
BitConverter.GetBytes((float)Cmd)
In this case may be it’s faster to install Rapid SCADA manually as written at http://doc.rapidscada.net/content/en/installation-and-run/manual-installation.html
Please check the following:
1. Does the folder C:\SCADA\ exist?
2. Run services.msc
Do ScadaCommService and ScadaServerService exist?It means that Rapid SCADA already installed. If you need to reinstall it, uninstall the existing one.
To change the password you need to login. You can change the password in the configuration database to make them matched.
After password is changed in XML, you need to restart the web application. You can do it using IIS Administration console or by restarting the PC.Don’t need.Hi,
The easiest way is changing password by editing C:\SCADA\ScadaWeb\config\WebSettings.xml in your favorite text editor.The script to export data executes when the data are received by SCADA-Server. You can create a stored procedure (function in Pg) that filters data according to your needs and use this procedure in DB Export Module.
It is possible to upgrade KpOpc.dll to repair connection to OPC server. It may be done as a custom development.
Rapid SCADA does not know that the OPC server has been shutted down
It’s true. There is a workaround. You can send a command via a text file to restart the communication line:
Create a file cmdXXX.dat within C:\SCADA\ScadaComm\Cmd
where XXX is a random number[Command] Target=ScadaCommSvc Sender=ScadaCommCtrl User=Admin DateTime=12/21/2015 23:00:13 LifeTime=60 CmdType=RestartLine LineNum=1 End=
I think you can create a file by using formulas in the configuration database (Administrator app).
