For the people who encounter the same problem or just stumble on this post by coincidence:
UniPi tech wrote: “We know the firmware update, especially of the extensions, is a sort of Achilles heel and we are thinking about some concept of dual firmware to which you can revert to if the flashing of the new firmware fails.”
I also would like to mention the excellent support from UniPi! I’ve received a very fast and meaningful response from both the technical as commercial team, and they are moving heaven and earth to provide me the fastest possible solution.
I didn’t experience such a personal approach from an international company since a long time.
it is hard to tell what's wrong without the access to the setup. Would it be possible to arrange SSH access to the PLC? We can go over the details via email: email@example.com
2.05a seems to have fixed this error too - the extensions are fully populated and the send events now (the old version didnt send events too as i had to discover).
thx for helping,
@christophebler Ok, than the serial line works well. But I still recommend using our opensource image because the parameters that can be set using the github version is limited and might cause some troubles which are fixed in the opensource image.
Byt the way, what do you want to do by 'Set Adress to 0 and rebooted both devices'? You can set address only at the slave which is the xS50 and if you set it to 0, than the SW configuration is used (address 15, 19200bps, no parity) and you are opening different device...
Address 0 is not allowed on Modbus, thus the behavior like I described.
@SorakCz In case of TCP Modbus than yes, just need to take care of the software part. Sorry for the inconveniences but a few changes in the FW can generate too much questions so I cannot give you any estimated time right now. It can be week but also four...