Forum Replies Created
-
AuthorPosts
-
manjey73ParticipantThis is true for all plugins. In order for them to run, they must be copied to the runtime server and to the development server, as well as the runtime server configuration downloaded to the project.
manjey73ParticipantCopy the plugin to the runtime server, as well as to your PC, where you are developing. Then you open your project (not necessarily Hello World) And download the configuration from the server to the project.
Then you add a plugin, and passes the configuration to the server. After that, you will have the opportunity to register – information about the PC key when the plugin starts on the server.
manjey73ParticipantThere is no access
manjey73ParticipantAre you looking for the cheapest option to read DNP3?
Perhaps you should really look for another Scada solution where DNP3 is supported?
manjey73ParticipantToshiba TB 1000 – the Internet says it’s a hard drive.
It is not so important, since you use Windows for Scada, then both OPC DA and OPC UA servers for the DNP3 protocol will suit you. But I would look to the future and look specifically for an OPC UA server for this protocol. As they say, look for the pocket (the price that suits you)
manjey73ParticipantWell, first you need to find an OPC server for DNP3. Depending on the OS, it can be either OPC DA or OPC UA.
Which OS are you installing Rapid Scada on?
manjey73ParticipantEither a gateway or an OPC server.
There is no native DNP3 driver in Rapid Scada.
manjey73ParticipantReplaced the channel with the Unicode string type. Now accepts in Russian (or any Unicode) and English normally.
manjey73Participantmodbus is integrated into the system
There is nothing for Bacnet. What OS do you have? You can use OPC from Insat (Russian) or any other company.
manjey73ParticipantBut there is a gateway-bridge and a rest api that can be used when writing a driver or module. And you can also try importing from Influxdb
manjey73ParticipantUnfortunately, not yet, I suggested to Mikhail to add such an opportunity, since it was asked about back on version 5
October 22, 2024 at 8:47 am in reply to: Rapid SCADA 6.3.1 Installation, TCP port 10002 already in use. #15541
manjey73ParticipantChange the ScadaAgent port to another one other than 10002
<?xml version="1.0" encoding="utf-8" ?> <ScadaAgentConfig> <ListenerOptions> <Port>10002</Port>See the configuration file in the ScadaAgent\Config folder. After that, restart the services.
Also, when configuring the configuration, specify this port in the project Instances-
This reply was modified 1 year, 3 months ago by
manjey73.
manjey73ParticipantWith the Date and Time format, it is transmitted as a string, Cmd is not suitable here
Input Script –
Val()
Output Script –GetStrDt(CmdDataStr)orGetStrDtToUtc(CmdDataStr)Script Table
For Locale Timepublic double GetStrDt(string dt) { SetVal(CnlNum, EncodeDate(DateTime.Parse(dt))); return EncodeDate(DateTime.Parse(dt)); }For UTC Time
public double GetStrDtToUtc(string dt) { SetVal(CnlNum, EncodeDate(DateTime.Parse(dt).ToUniversalTime())); return EncodeDate(DateTime.Parse(dt).ToUniversalTime()); }
manjey73ParticipantIn a simple version, you can control it through the start variable
In this case, the PLC does not actually stop, it does the work of “Doing nothing”if (start) { Your program } else do nothing
manjey73ParticipantIt seemed to me that the start and stop of the PLC is not related to the protocol, it is a higher level.
But it can also be solved through protocol variables, but for this your PLC program must be written accordingly. These are fundamentally different approaches. -
This reply was modified 1 year, 3 months ago by
-
AuthorPosts