@tomas_hora Thank you for your quick replies. I have a first gen UniPi and I would like to use Modbus to read/write the first relay for example. What are the steps I should take to make this happen? Just installing https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay as I think you're saying probably won't work as this is specific for the Neuron. I need a Modbus server on the Raspberry Pi that can read/write the relays of the UniPi. How could this be achieved?
Posts made by cvdd
-
RE: Recommended way to access inputs/ooutputs
-
RE: Recommended way to access inputs/ooutputs
@tomas_hora Thank you for the helpful illustration. So Modbus would be the faster choice I see. Looking through the code, Evok uses https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay when installed on Neuron to host a Modbus server. Does this mean an application can't directly connect to the underlying (middle layer in the graphic) Modbus server and always has to go through Evok which itself is a Modbus client but also hosts a server to channel through requests? And why is this only on Neuron and not on default UniPi with Raspberry Pi?
Essentially, what I'm really asking is what would be the fastest way for an application to interface with the standard UniPi (not Neuron)? Am I correct that Modbus is only an option for Neuron and not standard UniPi?
-
RE: Recommended way to access inputs/ooutputs
Hi @tomas_hora
I was wondering the same thing. Would Modbus be faster than Websockets or not? Also, looking through some code it seems Modbus is only supported for the Neuron. Is there a reason there's no support for the UniPi 1.1?