Forum Replies Created
-
Posts
-
I do not know what you have for the relay fee, I bought Chinese with Modbus in the documentation which was specified as on and off.
256 – off, 512 – on, 768 – toggle
I always gave the command 1 and multiplied by 768 and the relay changed its state. In other boards can be on different. Therefore, I try not to buy boards, which do not have a description, and then here on the forum there was an example when the Chinese mixed up the sequence of bytes of the checksum in ModbusOr you can use the standard command buttons from this database
Sometimes the device should be fed not 0 or 1 but for example 256 or 512, then using the values for commands 1 and 2 additionally in the output channel multiply by 256 using the formula Cmd*256
example in the formula base: NOT
public double NOT(double val) { bool boolVal = val > 0; return Convert.ToDouble(!boolVal); }In the output channel, write NOT (Cmd) and your command on the button will be changed to the opposite. Works only with 0 or 1 that actually follows from the name of the formula.
It is not quite clear what you want to do with the separation of the buttons ?
In response, the device says that it has included the network variable NI1, so most likely at the program level it is not included.
c Q2 you have no problem because it is not yet tied to the program. Q1 may not be enabled due to overwriting in the program. Now there is no Logo at hand! Soft Comfort to understand.
As for the lack of response to the NI1 input, a possible problem is that the Communicator sends to the double device,and the input user variables you have are word. The formula for rearranging the bytes before sending the command.
You have a table of registers from the manufacturer Logo! ?
Status of inputs and outputs.
Plus, the other registers you create yourself in the program Logo! and there should be a register card after its programming.install_with_xsp.txt or 13 file install_with_apache.txt
10. In case of using SD card, protect it by moving frequently used folders to RAM.
Skip this step if you use a regular HDD.
Add the lines below to /etc/fstabtmpfs /tmp tmpfs defaults,noatime,size=50m 0 0
tmpfs /var/log tmpfs defaults,noatime,size=50m 0 0
tmpfs /opt/scada/ScadaComm/Log tmpfs defaults,noatime,size=100m 0 0
tmpfs /opt/scada/ScadaServer/Log tmpfs defaults,noatime,size=10m 0 0
tmpfs /opt/scada/ScadaWeb/log tmpfs defaults,noatime,size=10m 0 0
tmpfs /opt/scada/ArchiveDAT/Cur tmpfs defaults,noatime,size=10m 0 0Hope just for those who have devices with m-Bus. At least it is planned to make free drivers that work with a specific device on the logs of requests and responses of the device. It is not difficult, as little changes there.
There is also a problem with scanning devices, not all manufacturers lay this functionality. For example, Wesser Heat Meter does not have this functionality and does not even have an address provided by the Protocol. It has only ID and only it can be used to run a survey.
Sorry for my English, I use online translator
Thanks for the links. But the problem I have is not with the description of the Protocol, and with real data from the devices. The Protocol gives a greater freedom of choice of data transmission, which of them will choose the manufacturer only knows. I would like to see different types of data transmission from different manufacturers. At the moment I have only two devices and both transmit Variable data Structure.
At the moment I have implemented the processing of Variable Data Structure in the response.
01 03 30 00 00 08 4B 0C
So it became clear that any online calculator Modbus CRC in the calculation of CRC along with it should give the result 0
It was necessary to buy such a module, there is a description in English and you can check the information on the Protocol and the method of calculation of channels.
