Mesa pktUART RT Modbus Driver

Related to Andy's announcement here:
forum.linuxcnc.org/29-forum-announcement...or-mesa-cards#269395
I wanted to create a new discussion thread to talk about Mesa pktUART RT Modbus Driver.

First off, thanks a lot Andy for your work on the driver.

I was very curious and had to try it right away, but I can't get it to work.

Here is what I did:

1.) Flashed my 7i96 with the pktUART firmware
sudo mesaflash --device 7i96 --addr 10.10.10.10 --write 7i96_pktd.bit

2.) Downloaded and installed Andy's branch

3.) Created a simple xy-md02.mod - for a Modbus temperature / humidity sensor (working with modpoll)

4.) Modcompiled and installed OK. Added loadrt xy-md02 ports=hm2_7i96.0.pktuart.0 and addf xy-md02 servo-thread

5.) LinuxCNC starts, but I don't get any values. Modbus settings should match defaults: 9600 / no parity
but I also played with almost all combinations.

6.) I have checked the wiring and tried flipping the cables, too. No difference.
RX- and TX- to B
RX+ and TX+ to A

Endless terminal output is this:
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E
WAIT_FOR_DATA_FRAME - rxmode = 3FE00F8E

Test script output:
cnc@lcnc-dev:~/linuxcnc-andypugh-mesa_modbus/src/hal/drivers/mesa-hostmot2/modbus$ ./test-mod.sh
00200A20
3FE1148E
00008015
00000000
00000000

Not sure what else I can try. Any other debugs I can enable?


 

The '1' bit set on the RX mode register indicates a overrun error
(no stop bit when expected)

This may be because of incorrect baud rates or undriven differential
bias levels on the RX lines generating a continuous line break.

Can someone help me compile it?
This is as far as I get: undefined symbol: hm2_pktuart_queue_get_frame_sizes
I'm not sure I filled in the header correctly either so I've attached my vfdmod configuration instead