Topics created by BeerGeek

Hello @beergeek, yes it is. Start the debugging mode, switch the bottom panel to "Port monitor", select the channel you want and press "play". You will see the Modbus requests and (hopefully) some responses:

Hi @beergeek, there is probably a number of ways how to do it. This could be one of them: create /usr/local/sbin/shutdown and add the exec bit to it in the script, specify the logic - get the IOs into safe state and/or light up the user LEDs at the end of the script, call shutdown -h now The logic can use the SysFS approach such as this: echo 1 > /run/unipi/io_group1/do_1_01/do_value # sets DO1.1 to true Although you don't have the user LEDs available in the SysFS right now. For that, you can use mbpoll and set it via ModbusTCP. Best regards, Martin

This is a very rare issue with stuck SPI line, let us know on email or phone when/if this happens next time so we can see it.

FIxed in EVOK 2.1.6. Thanks. But all aliases were deleted. I had to configure all aliases again.

Neuron, after apt-get upgrade $ sudo /opt/unipi/tools/fwspi -i 0 Boardset: 0 B-1000 (v1.0) Baseboard: 0 B-1000 (v0.6) Firmware: v5.27 sudo /opt/unipi/tools/fwspi -i 1 Boardset: 1 E-8Di8Ro (v1.0) Baseboard: 1 E-8Di8Ro (v0.2) Firmware: v5.27

Hello @beergeek You are right with problem when using analog output in configuration 0-20mA. When we designed nodes, we only implemented voltage output. To fast repair you can add function node to output, that recalculate output value from 0-10 to 0-20. So your input value will be 0 to 10, but output value will be 0-20. We will try to repair output node with support for current output it in next week. Function code to fast implementation: Try to import funtion and connect it as in picture. [{"id":"98b4db11.a43aa8","type":"function","z":"dd6bd412.3bde08","name":"0-20mA","func":"if(msg.payload.value) \n{\n msg.payload.value = msg.payload.value*2.00;\n}\nreturn msg;","outputs":1,"noerr":0,"x":1260,"y":220,"wires":[["a7851ed2.a7d6"]]}] Thank you for your notice.