Forum Replies Created
-
Posts
-
Because you don’t have such a device on the lines. Equipment settings are given in the database for an example of how to do it directly with your equipment.
You need either real equipment and real experiments. Or find on the Internet emulators devices such as Modbus and set up communication with them. Everything is possible.
http://raxp2.blogspot.com/2015/03/modbus.html
The site is in Russian, but if you follow the links, there are English versions of simulators, including free.
The database is limited to 8 bytes in any case. And for the full name to appear in the Communicator window, the driver must know exactly what this text variable is. The OPC driver is a more universal thing and you just can’t tell it to display a fully text variable, as it does in the SNMP driver, for example.
p.s. we have been asking for additional text databases for such things.
Twenty-five again…. (Russian expression.)
You can make one channel number, for example 9, which will get the value from the device with the signal 9. And in the formula the estimated channels to write GetBit(9, 0), and so on ? there is no need to specify a signal in the calculation channel
If you have a channel 20 receives a signal from the device 9, then in the formula of the calculation channel it is necessary to specify the 20th channel. Example GetBit (20, 3) >0 ? 0: 1
bits in numbers start from zero. Do you want first or zero ?
bits in numbers start from zero. Do you want first or zero ? And not only the signal 9 and the Number 9 (the channel number is used in the formula)
GetBit (channel number, bit number) – you will get the same value as bit 0 or bit 1
GetBit (channel number, bit number) > 0 ? 0: 1 – you will get the opposite value if bit=0 then you will get 1, if bit=1 then you will get 0
GetBit (a,b)
a – channel data number from which you want to check the required bit
b – is the number of the bit to be checked from 0 to 64 considering that the database always has a double representation. But in fact, if you read one register, you can actually check only from 0 to 15 for example> 0 ? 0; 1 this entry you do the inversion if it is necessary
Not quite boolen, all variables RapidScada converts to double, this is a feature of the database implementation. However sometimes it is a hindrance 🙂 your perception is, Yes, a boolean.
Use C# help on MSDN
<Param name=”WriteMinPer” value=”60” descr=”Период записи минутных срезов, с” />
See settings of this file ScadaServerSvcConfig.xml but in this way you will increase the database in size
Sorry, all timer formulas still need Tiсks formula to work
public static long Ticks() { DateTime now = DateTime.Now; long time = now.Ticks/10000; return time; }Without this formula, all timers will give an error, and since the formula timers are different, but use the same calculation of the difference, the Ticks made a separate formula
Yes, the register should be read once and then on the basis of the input channel of this register to apply the formula GetBit in settlement channels. You really spend a lot of time on the same type of reading.
Then it turns out that you have everything right. 480 parameters this is clearly more than Modbus can allow with a single request. Try to separate the query groups so that the parameters you change are often in separate groups. That is to make a logical separation.
