Hello @tomas_hora , thank you for your answer. that is the one I wanted to know.

Thanks, i will have a try

Hi @dickesc, you just did everything you can to fix this - you made a detailed report. I am forwarding this to the developers to have it fixed. Thank you for your contribution, Martin

Hello @søren-hedegaard-0, you didn't pass any input value to the ph_control_hourly(), so the block doesn't know anything about run_at_time and ph_hourly_feed. The call should look this: ph_control_hourly(run_at_time := local_run_at_time, ph_hourly_feed := local_ph_hourly_feed, out => local_out_value) If you look in to the help (F1) of any built-in FB, you will see a usage and you learn how the ST works: Best regards, Martin

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.

Hello @valtert, the description on the page is misleading. The real situation is this: Analog output on Group 1 is capable of outputing 0-10V, 0-20mA and measuring resistance up to 100kOhm Analog outputs on Group 2 and 3 and on the extensions are only capable of outputing 0-10V Same goes for Neuron and Axon product line. If you need second AO in current mode for your project, you have two options: add a second PLC as a "dumb" extension and communicate with the master PLC via ModbusRTU, ModbusTCP or SSCP purchase a 3rd party ModbusRTU IO module, such as this: https://www.advantech.com/products/gf-5vtd/adam-4024/mod_5e18f39b-38ef-4033-98f9-1ede917139ee I am sorry for the incovenience, we will fix the product description shortly. Best regards, Martin

Hi @knebb, definitely not. The DOs are NPN type (open collector). You can read more about how to read the NPN outputs with digital inputs here: https://forum.unipi.technology/topic/712/neuron-12v-digital-input/2 Best regards, Martin

Hi @barnabás-králik, Relays are this one: https://www.tme.eu/en/details/ftr-f3aa024e-ha/miniature-electromagnetic-relays/fujitsu/ yes, relays are difficult to replace and replacing them by yourself means losing the warranty there is no feedback about the physical state, e.g. via secondary terminals Best regards, Martin

I managed to get what I need by compiling a new (hopefully) compatible set of modules and installing by hands only the needed ones. Here are the steps I followed, executed directly on the AXON as root: v=$(uname -r) cd /usr/src wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-$v.tar.xz tar xf linux-$v.tar.xz cd linux-$v gzip -dc /proc/config.gz > .config apt install libncurses5-dev bc # Customize the kernel to your needs. In my case I enabled the # snd-usb-audio module that, in cascade, enabled other sound stuff. make menuconfig # Build and install *only* the new modules. make modules mkdir -p /lib/modules/$v/kernel/sound/usb cp sound/usb/*.ko /lib/modules/$v/kernel/sound/usb/ cp sound/core/snd-*.ko /lib/modules/$v/kernel/sound/core/ depmod # Not strictly needed, but forbidding future axon-kernel upgrades # could avoid potential hard-to-debug problems. apt-mark hold axon-kernel

@knebb said in Need Some sort of Jumpstart: it writes the state as 0 or 1 into each of the uint8_t . Or, using semantic constants, as FALSE and TRUE. Directly using bits would be really slow and error prone (and I nightmare for language bindings).

Hi @knebb, there are two approaches and you figured out both of them: Do the calculation and write to register 2 Write a value to the register 3000. The value has to be 32bit signed integer. I checked the documentation and I think there is a mistake with the registers 3000, 3001 and 3002. Those should be 3000, 3002 and 3004 since the 32bit values need two consecutive registers. I will check what is in the firmware and let you know! Best regards, Martin

@ntd Perfect! Got it finally. I mixed up modbus_read_bits and modbus_read_register. Now working like a charm! Thanks a lot! /KNEBB

Hi In the meantime i got my Neuron M203. The UniPi was just for testing. With the Neuron i can "communicate" with the SDM120-Modbus, but i can get no values. Can someone help me with the configuration for Modbus Group Parameters Comm. Value Mapped Type ST Type Data Offset MultiByte Lenght The Modbus register map you can find here: https://bg-etech.de/download/manual/SDM120C-Modbus-DE.pdf http://www.eastroneurope.com/media/_system/tech_specs/3914/SDM120 PROTOCOL.pdf Thanks

Thanks Martin. PyModbus worked great to me and I understand how to map variables on Mervis to be placed as modbus tcp touchable. I Still have curious question. I configured 503 port as modbus server, because 502 is already used as another modbus. What is this modbus used for ? thank you.

Ok, I'll do it on the board then. I'll take my chances communicating directly with the modbus tcp server instead of using Evok's layer. Cheers, Ronan

For the sake of the history: a very old SD card image was in the PLC and the current MervisIDE wasn't able to detect it properly.