@tja And the restart of evok fixes it or you also have to restart the modbus service? Could you provide the log from evok (/var/log/evok.log) and also the state of modbus TCP server (systemctl status neurontcp) when it stops working?

@dsurname Can you try it on our latest UniPian Neuron OS? Everything is preinstalled so you just try to run the python code...

@dsurname Do the TX/RX diodes on the M103 and/or the modbus device blink? Also check the RS485 + modbus parameters... Only /dev/extcomm... is correct.

@dsurname it's now a bit offtopic from the thread description, so please start a new topic which will better describe your issues. At first, you do not need to worry about the RUN led. If you try to read a DI, the behavior of RUN led will change.

/dev/ttyAMA0 is the UART of RPi, not the RS485 of Neuron. If you want to access the RS485, you need to install UniPi drivers (currently is part of in Evok https://github.com/UniPiTechnology/evok, in future, there will be Debian packages). Once installed, the RS485 ports are will be available for example at /dev/extcomm/0/0

@dsurname short blink after 2 secs means, that the main program, that controls the IOs (e.g. evok if installed). If it is on for 2secs and then off for 2secs, it means that the there is no master app trying to communicate with the IOs

@dsurname so they blink in 2s interval or they stay in one state for the whole time?

@mdturnerphys Thanks for popping up the topic. TO_REAL function will be able to parse string to float in the upcoming release

@mdturnerphys As far as I know, there is no such fbd because TO_REAL does not handle string

Hello @mdturnerphys,

sorry!! This is not mentioned anywhere (will write it in the step by step) this is Mervis internal mapping.... The numbering is following:

• USB1-USB4 - 10-13

So USB1(as labeled on the case) has ID 10.

@bsc101 Great work! Let us know when it's released... We will be happy to test it :)