Looks like an apt upgrade was issued without a reboot. Same thing happened to me after an apt upgrade reboot. Now your os runs on kernel 4.19 and evok can't access the modules. I think the kernel modules are incompatible with the new kernel. Only fresh install of unipian was the easiest way to get the os working again without issuing apt upgrade.... Clean install also fails from a clean raspbian stretch with github install instructions.

Hello @asunc, absolutely no problem. The Axon is running a debootstraped arm64 Debian with added repository of our packages via which we publish fixes and new versions of our software. Best regards, Martin

Hi @dealah-in-kóma, there are basically two ways of achieving that. Both of them require connecting the Inepro energy meter via RS485. The difference is in who will be responsible for polling the Modbus data from the device. The Evok way Evok can be configured in a way, that it will poll general Modbus devices. See https://github.com/UniPiTechnology/evok/blob/master/etc/hw_definitions/CUSTOM MODBUS DEVICE.yaml The updated data are available via standard Evok API. The Node-RED way You can poll the Modbus device in Node-RED directly via node-red-contrib-modbus https://www.npmjs.com/package/node-red-contrib-modbus Personally, I would suggest you the option 2, since configuration in Evok is not easy. For configuration you need a Modbus registers map for the given device, that can be found in the documentation from the vendor. Please note, that there are several HW and SW revisions for the device and you need to use the correct documentation. The latest one is here: https://ineprometering.com/wp-content/uploads/2019/04/PRO380-user-manual-V2.18v6.pdf and the Modbus registers map starts from page 27. Best regards, Martin

If there are some missing modules, you need to compile it. On Axon (or generaly any arm64 platform) do: apt install build-essential git git clone https://git.unipi.technology/UniPi/axon-linux.git make unipi-axon_defconfig Now you can change kernel configuration to desired state make menuconfig Compile new modules make modules You can compile on amd64 platform using CROSS_COMPILE make unipi-axon_defconfig CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 make menuconfig CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 make modules CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64

@boy-lenssen Yeah, that's something we are working on to protect bricking the units during the FW upgrade process. If the RUN led is dead, send it to us so we can reflash the FW.

Added serial port map IDs https://kb.unipi.technology/en:sw:01-mervis:serial-port-numbers-hidden

Hi @r3sist, any progress with your project? Very interesting.

The issue was by the incorrect comm speed with the modem. I modified the guide provided by @roberts_lando to use the proper baudrate of 9600 instead of 115200.

Další pokračování: Když si udělám primitivní web v externím HMI editoru, smažu odkaz na šablonu (poslední dva řádky v konfiguraci PLC) a použiji webpanel z externího HMI, tak ten funguje. Zkusil jsem to po zprovoznění webu z externího HMI nahradit intergrovaným, a výsledek je stále stejný = načte se grafika, ale nefunguje propojení s programem - neukazuje aktuální hodnoty.

If you use push button via the digital input, then use own control mechanism (pulse counter) with reset from ligth sensor falling edge.

Dobrý den, vstupy a výstupy v uživatelském funkčním bloku se zobrazují v pořadí v jakém byly vytvořeny a nejde to předělat jinak, než že si v něm vstup/výstup smažete a vytvoříte znovu. POZOR! Ve všech programech, kde tento svůj funkční blok používáte bude potřeba upravit jeho napojení. PP

@tomkling Thank you for your information. I also figured out 502 is used on debugging. So it is important.

Hi Martin, thanks for the hint. It said that there was a failure in the program. I deleted that part and now it compiles fine.

Hi again and thanks for the help, I've used ModbusTCP now and the input / output rates are much better, if someone's interested: Reading only = 2,5 - 7,4 ms Reading and Writing to another pin = 7 - 15 ms Reading, Processing the measures, and Writing to another pin = 6 - 18 ms I used Analog Input 2.1 / 2.2 and Analog Output 2.1 for my application