[Mikhail]

KpSms.dll has no additional properties.
KpOpc.dll properies are specified for a device not for the whole library.

You don’t need to edit KpOPC_XXX.xml manually. Open the device properties from a popup menu by right clicking the device item of the tree. Device configuration form opens as shown in the article. If you open the configuration form you will easily understand the meaning of the XML.

[Mikhail]

Yes, it’s possible. You need to:
1. Add the list of command values into Command values table using SCADA-Administrator.
2. Add an output channel of Standard type. Select your list in Command values field of the output channel.
3. Create a formula and specify it for the output channel.
4. When you send a command the formula converts the given index of list value to the new value. Pay the attention that the list is indexed starting from 0.

[Mikhail]

Of course not. It depends on your hardware, power supply, etc.
In some industries there are very strict requirements for system safety.
Rapid SCADA works stable 24×7.

[Mikhail]

In my opinion you need to apply hardware protection of your system in case that server breakdown.

[Mikhail]

Hello,
I have replied here

[Mikhail]

Yes, you have correctly understood the mechanism of interaction between Rapid SCADA applications.

[Mikhail]

Hello,
Using formulas you can perform calculations but can’t send a command. There is another tool for sending commands depending on conditions: Automatic Control Module.

Automatic Control Module is commercial, the cost is US $20. You can try it for free in the test mode.
If the price is too high, it is possible to develop your own implementation as described here.

• This reply was modified 10 years, 6 months ago by Mikhail.

[Mikhail]

Thanks for Number in Russian issue. It will be fixed.

[Mikhail]

Modbus, OPC and AT commands are commonly used worldwide.
VKT-4M, etc. are specific for Russian customers, therefore they were excluded from the installation package to keep the product clear.

[Mikhail]

A Modbus element which is read from a device has Signal field. SCADA-Communicator receives data from a device and retrieves an input channal number using Device number and Signal, then SCADA-Communicator passed data to SCADA-Server.

A Modbus element which is written to a device has Command number field. When you send a command, you use a specified output channel, so SCADA-Communicator chooses the appropriate command by Device number and Command number which are defined in the output channel.

[Mikhail]

Hello,
It is strange. My configuration database contains only 11..14 channels.
I think you can delete 1..4 channels.

[Mikhail]

Hello Teleco,

1. Number is internal. It is needed for associating different information with a command.

2. Command number is sent to SCADA-Communicator when you send a command. It is processed by device driver. For example, you can bind Modbus command to a specified command number from the configuation database. Comamand number field is similar to Signal field.

3. If Command values field in Output channels table is not set you can directly input a value of command. If it is set the value of command is an index of the selected list value. Often you need to convert value according to device specification using formula of output channel.

[Mikhail]

1. To simulate “ADAM-6015 Server room” do not modify anything in Rapid SCADA configuration. Just tune up the simulator according to KpModbus_Adam6015.xml template. 101 is internal channel number for Rapid SCADA. In Modbus terms t4 is an element with address 5 from Holding Registers (4x) data table.

2. Calculated Real type is set for a channel if its formula refers to data of other channels. Use Real type if channel data is received from a device.

3. Signal binds an input channel to a tag of device. This field is processed by SCADA-Communicator.

4. The items t4_min, t4_max, t5_min, t5_max display data and allow sending commands. Each item of table view can hold either input or output channel. Channel numbers are written in item’s hint. Commands are sent manually in this example.

• This reply was modified 10 years, 6 months ago by Mikhail.

[Mikhail]

I’ve tried the same as you did.
Call numbers localhost and computer name don’t work, because of wrong IP address format.

Call number 127.0.0.1 is OK:
2015-02-01 21:57:56 Communication session with Device 11 “ADAM-6015 Server room”, type: KpModbus, call number: 127.0.0.1
Establish a TCP connection with 127.0.0.1

During testing I uncheck “Use SCADA-Server” checkbox in SCADA-Communicator. If you do not uncheck it the call number specified in the configuration database is used.

Try 127.0.0.1 again. If it doesn’t work post a part of log here.

[Mikhail]

Switch to Communication Line log tab.
Read the log carefully, usually it contains information about the cause.
Firstly, realize is the connection established or not.

[Author]

Posts