I seem to be making some headway, I moved everything off the rpie and am working from my toughbook. I can poll the slave now and get some data the big problem was i only have 10 counters to work with and the default on the modprobe was set to 100. This device is very slow to respond (waterlog h-350XL) and is hit and miss when i poll with rtu over rs232 but for the most part i get a response every 3 seconds or so. However if i use tcp mbusd seems to be overrun and i just get a Reply time-out!. Ive tried dialing back everthing that has to do with time and frequency of poling but it still seems to fast. Im using this "mbusd -L/tmp/mbusd.log -W 10000 -N 1 -R 10000 -p /dev/ttyUSB0 -s 9600 -P 502 -d -v9"

from mbusd.

I GOT IT!! I just needed to increase the time out on the poller program to 10 seconds and BOOYAAA!.

However the one problem i do have is after restarting the mbusd service i have to pole it with rtu one time before tcpip will work?

from mbusd.

Ok im able to get this working but only if i launch it in the foreground.
mbusd -L/tmp/mbusd.log -p /dev/ttyUSB0 -s 9600 -P 502 -d -v9
I've tried configuring the /etc/mbusd/mbusd-ttyUSB0.conf with the exact same configuration minus the logging and foreground fork.
######### Serial port settings #############

Serial port device name

device = /dev/ttyUSB0

Serial port speed

speed = 9600
############# TCP port settings #############

TCP server port number

port = 502

Connection timeout value in seconds

timeout = 10
It just will not work.

when i look at the log file it claims resource :tty not ready?

Second issue: I have to first probe it with rtu from my toughbook that is connected to the modbus device otherwise all i get is... "Gateway Target Device Failed exception response!"
This i could work around accept, the modbus prob im working with will not run on arm arch. so im kinda sunk and i cant find a prober that will run on arm arch.

from mbusd.

Hi @shawnggraham,

when i look at the log file it claims resource :tty not ready?

Could you post the entire log file? This message looks quite weird to me.

from mbusd.

Late last night i got fed up, it was all weird. I grabbed a rpie-v3 did a fresh raspbian install on it and walked through the compile process for mbusd again on it. I cant find a single step i did any different but this one seems to work fine. The only problem i have found is that i cannot run a modbus probe on the rtu at the same time my other machines are probing via tcpip. But the only reason i wanted to do that was because i was verifying the rpie could actually communicate with the waterloger so its not something i need to be able to do at the same time im polling via tcpip. So im good to go now! Im going to recreate this on the other rpie-v2b just for followup (and i have a grip of those to work with) and ill let you know how it goes.
Also just because somebody else may want to be able to modbus rtu poll from the rpie..i did finally get that working with mbpoll from here -> https://github.com/epsilonrt/mbpoll/ It works mucho goodo!!

from mbusd.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from mbusd.