Page 1 of 1

piModbusSlave

Posted: 19 Oct 2017, 11:31
by piziwate
Hello,

I'm doing a project with the RevPi and this is very a great device !
I've just an issue with the /usr/sbin/piModbusSlave process (loaded automatically at boot).
The problem is, if I do a reboot of the RevPi, piModbusSlave is started but doesn't work (I got TCP Connection failed from my Modbus Master).

If I kill the process and start it again :

Code: Select all

top
root       513     1  0 11:24 ?        00:00:00 /usr/sbin/piModbusSlave

sudo kill 513
sudo /usr/sbin/piModbusSlave &
This is now working after the manual start... very strange
Any idea ?

Best regards
Steve

Re: piModbusSlave

Posted: 09 Nov 2017, 17:13
by Robert84
Hello,
I have the same problem on a recently bought RevPi Core.
Pimodbus-slave doesn't work after a reboot, according to netstat it didn't even open a socket but there is a piModbusSlave process up and running. Systemctl also correctly lists is as active running. Stopping and starting it by systemctl or just executing it manually, even without killing the already existing piModbusSlave process, launches a second process that works normally.

Even flashing with a fresh jessie-image didnt help, the modbus slave still doesn't work after a reboot.

When can we expect a fix or workaround for that issue?

Kind regards
Robert

Re: piModbusSlave

Posted: 10 Nov 2017, 00:24
by volker
There should be a bugfix in the actual packages. May be it is not yet in the image.
Please always make an update to the newest packages as the image is only released every several month or when having important changes.
So please do "sudo apt-get update" and then "sudo apt-get upgrade" and it should work.

Re: piModbusSlave

Posted: 10 Nov 2017, 11:40
by Robert84
Thanks for your quick reply.
I already updated the system, that was amogst the first things I tried. So there currently is nothing for apt to update.

Nevertheless, I followed your instructions and rand these two commands. As expected, no packages where updated and the issue still remains.

/usr/sbin/piModbusSlave is dated 15th of May and has an MD5 sum of a8cadebee425414b0e2dd8055a13bb11, should that be a newer version?

Re: piModbusSlave

Posted: 14 Nov 2017, 15:23
by volker
As you may have seen in "News & Announcements" this known bug had not been fixed in actual packages --- but now it has :-)
So please do an upgrade again and things should hopefully work well...

Re: piModbusSlave

Posted: 14 Nov 2017, 23:17
by Robert84
Thanks a lot, after this update modbus slave is working perfectly.