12 063
правки
Wb-mqtt-serial driver/en: различия между версиями
Новая страница: «For example, Uniel device frames start with byte 0xff, IVTM devices start with byte 0x24 ('$'), and in the case of Modbus, Mercury 230, and Milur protocols, the f…»
(Новая страница: «It is possible to use devices with different protocols on the same bus, but it is necessary to take into account the features of specific protocols.») |
(Новая страница: «For example, Uniel device frames start with byte 0xff, IVTM devices start with byte 0x24 ('$'), and in the case of Modbus, Mercury 230, and Milur protocols, the f…») |
||
| Строка 14: | Строка 14: | ||
It is possible to use devices with different protocols on the same bus, but it is necessary to take into account the features of specific protocols. | It is possible to use devices with different protocols on the same bus, but it is necessary to take into account the features of specific protocols. | ||
For example, Uniel device frames start with byte 0xff, IVTM devices start with byte 0x24 ('$'), and in the case of Modbus, Mercury 230, and Milur protocols, the first byte of the frame is the slave ID, so when you combine such devices, you should carefully choose the slave id of Milur devices, for example, the default slave ID is 0xff, which leads to a conflict with Uniel devices. Milur Devices require additional polling delays (defined in the template) and may reduce polling speed when used on the same bus with other devices. Some devices that support additional protocols may not be compatible with other protocols on the same bus, for example, it has been observed that devices supporting the A-BUS protocol produced by "razumdom.ru" can not work on the same bus with Uniel devices. The work of the IVTM devices on the same bus with devices operating on other protocols has not been tested. Proven working combination is: Modbus + Milur (slave_id != 0xff) + Uniel on one bus. | |||