Na aktuální otázku je odpověď: ANO, lze funce I/O nastavit i jinak
Pro nastavení u rozšiřujících modulů Unipi můžete použít např. program mbpoll v linuxu (po připojení přes SSH) a komunikovat se zařízením přes modbus, kde si jednotlivé funkce nastavíte dle modbus tabulky.
Thanks for the answer. I've already thought of something like that.
According to the DIP switch, the xS11 can only have a maximum baudrate of 19200. An increase has led to a loss of communication.
I thought about swapping my M303 controller for an L303 to have enough inputs on the controller to bypass the Modbus. I then only use the extension modules to use outputs and inputs where speed is not an issue.
Is it correct that the processing of the internal inputs on a controller (e.g. L303) is a faster method than Modbus?
Is my approach understandable and sensible, or do I have a mistake in thinking?
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.
@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.