@Jan-Teunis Than everything should be working well. The RUN led also indicates if there has been a recent communication with the group (1-3).

@sabrus Sorry it should be 0.0000125s. From the formula in the documentation. (5+1)/48000000*100 equals 0.0000125. And yes...

Hello @Boy-Lenssen ,

list itemDIs are a galvanically isolated so unless the voltage and current will stay in the limits, you should be OK Digital outputs & analog inputs and outputs are coupled together to common ground. So a there could be a risk of potential damage to these components when you are off the limits.

But do not worry the device is designed to provide maximum reliability when installed in the standard installation environment. And yes, replacing the device in case something goes wrong is the easiest and cheapest solution.

@Tomas_hora Thank you for advice to me.

@Meethos If you are in full mode, then the datapoints are not generated. Try to set autogen - this will create variable and assign it to the hw.

@m.brugger Hello, that is an issue of some versions of the fiirmware. If anyone else will be facing this issue please contact me directly.

@bazza2000 Webcosckets and other web services are provieded by Evok API which is also available for Neurons.

But Mervis does not have these web apis, you can only create a TCP Modbus server and wire your internal variables to its registers.

Do not mix Evok and Mervis.

@matteos Hello, all certifications can be found on http://downloads.unipi.technology under the product folder.

Basically we have only certifications for Europe, so basically CE and Neuron products has a few more (according to the datasheet):

ČSN EN 6095‐1 ed. 2 ČSN EN 61000‐6‐3 ed. 2 ČSN EN 55014‐1 ed. 3 ČSN EN 55022 ed. 3 2006/95/EC 2004/108/ES 2014/35/EU 2014/30/EC

@zeus The latest development version of evok already supports Neurons as well as websockets the same way as the first generation UniPi: https://github.com/UniPiTechnology/evok#debugging

@Baggz 30 meters is OK - https://www.unipi.technology/content/1-wire-network-46?identifier=hardware_documentation

@HarishKumar That is the point of the API to allow you to controll the IOs of with a simple python script so you do not need to write the low level programs... But if you do not want to use websockets or http, you can use the TCP Modbus.

Evok: https://github.com/UniPiTechnology/evok#testing-latest-git-versions
TCP Modbus (already included in evok): https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay

@lgab my reason for using the socket solution is that it pushes changes of the inputs so that I don't need to poll

Thanks Tomas.

@tomas_hora I got it working, thanks! I did not have a power supply at hand, but I just abused the 5v of a Raspberry Pi I had laying around to see if the light goes on :)

I also got the notification via websocket...awesome stuff :heartpulse:

@HarishKumar The internal communication is little bit modified Modbus, I suggest you to use the TCP Modbus: https://github.com/UniPiTechnology/neuron_tcp_modbus_overlay

The map of the TCP Modbus registers can be found at http://downloads.unipi.technology

@Boy-Lenssen DR-30-24 is the power supply recommended for used for powering the big Neurons.

You need to see what is the power requirements of the device you will be using and choose the power supply accordingly. Eg. Neuron S103 requires 12W at 24VDC so people should use power supply that gives 24VDC and min 12W(0.5A). The same it is with any other device...