Hi @daho,
for the toggle functionality you can use the FB "toggle". The rest of the task is simple boolean logic. If the toggle output is true and another DI is false (not true), set the RO to true. Use the FB "and" and "not" for that.

Best regards,
Martin

Hello John-paul,

the communication between Axon and Weintek can be over ModbusRTU or BACnet/IP. I strongly recommend to use the latter - BACnet/IP. For both types communications, we have tutorials for configuration in MervisIDE:

https://kb.unipi.technology/en:sw:01-mervis:weintek-hmi-bacnet-mervis-hidden

https://kb.unipi.technology/en:sw:01-mervis:weintek-ip-series-hidden

Hi @dalibor,
no, the DIs don't have this capability. Mainly because it would require to have DIVCC terminal, to ensure galvanic isolation.

Hello @msoenen,
the Mervis mobile app is available for download in the official stores for Android and iOS. However, to use this app, you need Mervis IDE capable of deploying projects to Mervis SCADA. Currently we are working on release of such Mervis IDE, which, with any luck, will be released to public next month.

Best regards,
Martin

Hello @leif-edh,
due to the Covid 19 quarantine in Czech Republic, I am out of access to the base image which we use for the initial flashing of the NanoPi. Once I will regain access, I can send it to you. Please, bear in mind that this is highly unusual request and I am not able to give you any other support for it and by opening the device, you have effectively lost warranty for the device.

Thank you for understanding,
Martin

Hello @leif-edh, to understand it correctly - you have opened the PLC and connect to the serial interface of the NanoPi?

Hi @dalibor,
we typically sort this out by connecting 24V to the contact 11 of the PIR's relay and connecting the contact 14 (NO) to the DI. Would that pose some problem in your installation?

Best regards,
Martin

Hi @mmcreativ,
the issue might arise, if you try accessing the IP 192.168.8.91 from another subnet. The WiFi interface doesn't have default gateway set, therefor it doesn't know how to reach different subnet. Could this be the issue?

Best regards,
Martin

Hello @pascal37,
I would blame the serial converter first for the disconnecting issue. You said it started to behave like this after 2 months of operation and I guess you haven't tried it for the same amount of time on the second USB port.

Generally, the enumeration of USB devices is dynamic and if you want the device to be enumerated statically, you need to write an udev rule. Try following this tutorial: https://unix.stackexchange.com/questions/91629/symlinks-on-dev-ttyusb-via-udev

Best regards,
Martin

Hello @pascal37,
there isn't a moving average FB per-se, but try looking into the B86 Filter:

Best regards,
Martin