beyonlo
commented
2 years ago Hi @eydam-prototyping
I think that I find an error in the https://github.com/eydam-prototyping/mp_modbus/blob/master/mp_modbus_slave.py file. I removed the lines 112, 113 and 114 on mp_modbus_slave.py file to run using the ESP32 MicroPython 1.17.
Edit 1: I added too this self.uart.write(res) after line 118 on file https://github.com/eydam-prototyping/mp_modbus/blob/master/mp_modbus_slave.py#L118 because when enter in mp mode (MicroPython) was not there a write data to UART, like as in non MicroPython mode, on the line 123.
ESP32-02 run as Slave-RTU:
Edit 2: I forgot to put the context var - I copied from the example file https://github.com/eydam-prototyping/mp_modbus/blob/master/test/test_modbus_rtu_async.py :
>>> import uasyncio
>>> from machine import UART
>>> uart1 = UART(1, baudrate=9600, tx=26, rx=25)
>>> from mp_modbus_slave import modbus_rtu_slave, modbus_tcp_server
>>> context={
"co":{"startAddr": 1000, "registers": bytearray([0xFF, 0x00, 0x00, 0x00]*5)}, # Coils: ON OFF ON OFF ON OFF ON OFF ON OFF
"di":{"startAddr": 1000, "registers": bytearray([0xFF, 0x00, 0x00, 0x00]*5)}, # Digital Inputs: ON OFF ON OFF ON OFF ON OFF ON OFF
"hr":{"startAddr": 1000, "registers": bytearray([0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F])},
"ir":{"startAddr": 1000, "registers": bytearray([0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08, 0x09, 0x0A, 0x0B, 0x0C, 0x0D, 0x0E, 0x0F])}
}
>>> rtu_slave = modbus_rtu_slave(context=context, uart=uart1)
>>> coro = rtu_slave.run_async()
>>> uasyncio.run(coro)
starting async rtu slaveESP32-01 run as Master-RTU:
>>> from mp_modbus_master import modbus_rtu_master, modbus_tcp_client
>>> rtu_master = modbus_rtu_master(uart_no=1, tx_pin=25, rx_pin=26, en_pin=27)
>>> frame = rtu_master.read_holding_registers(1000, 1)
<modbus_rtu_frame (response): device: 1, func_code: 3, frame:01 03 02 00 01 79 84>
>>> print(frame)
b'\x00\x01'
>>> frame = rtu_master.read_digital_inputs(1000, 1)
<modbus_rtu_frame (response): device: 1, func_code: 2, frame:01 02 01 00 a1 88>
>>> print(frame)
b'\x00'
>>> Is correct that results above (on Master), the b'\x00\x01' and b'\x00' based on context var on the Slave-RTU?
Observations: 1. I'm not using the RS485 in this test, just UART (10cm distance) to validate the use case, because I think that my 485 transceiver is broken. Are there problem to use this ModBus lib just using the UART? I just do not have the enable pin, so the enable pin will do nothing, right?
Edit 3: 2. I'm testing the sync mode, but I want to use the asyncio mode send/receive. I see that you created methods to send/receive in async mode (that is great) and is what I want, for RTU and TCP :) I not tested yet, because I'm trying to figureout in basic (sync) examples first are working very well.
Any examples to run the slave mode (RTU and TCP (Server)) on the MicroPython will be wellcome :)
Thank you very much.
eydam-prototyping
papercodeIN
Hello!
Congratulations for the great work for ModBus lib for the MicroPython.
I'm trying to run the Slave mode but I have no success. Could you please to create a simple example to run the slave mode (RTU and TCP (Server)) using your code?
Just to clarify about my tests: I'm using two ESP32, where ESP32-01 run as Master-RTU and ESP32-02 as Slave-RTU, using RS485. The same to ModBus TCP, where ESP32-01 run as Master (TCP Client) and ESP32-02 as Slave (TCP Server), just using WiFi between them.
I'm using MicroPython version 1.17:
Thank you in advance.