administrators

@msoenen Just the picture in the help of Mervis.. There is actually not much to show.

@msoenen Then check the "DirectSwitch_force" and its documentation which is part of Lib.UniPi

Hello @francoisd,
the ports are:

TCP/12346 - For uploading solution
TCP/80 - For Web HMI

That should be all. TCP/22 for SSH is handy to have. If you are planning to run ModbusTCP slave in Mervis, then you have to allow another port as well.

For outgoing communication there should be access to internet via:

TCP/80 - For MervisDB
TCP/6677 - For Mervis Proxy

Best regards,
Martin

Hi @ludwigj,
from the brief checking of the Papago product line from Papouch, I see the protocol is Modbus TCP, not Modbus RTU over TCP (which is non-standard). Therefor it should work with UniPi Neuron and Axon.

Best regards,
Martin

@francoisd https://kb.unipi.technology/en:sw:01-mervis:updating-a-runtime-hidden

Right now, you can only link a DiX.Y and DO/ROX.Y - X and Y has to be the same with both DO/RO and DI.

@matt Check the attached leaflet. SSH can be enabled using the web service interface.

Thanks for the tip! Created a Axon category and re-organized the UniPi Extensions category.

Hello @matt ,

not yet :(

@msoenen https://kb.unipi.technology/en:sw:01-mervis:advanced-modes-of-digital-inputs-hidden#direct_switch

That does look quite good! The CPU will indeed be high with direct polling unfortunately, particularly with Python. We are hoping to implement an interrupt structure to remove the vast majority of the load, though it will have considerably higher latency due to various extra overhead the interrupts will introduce, so it is a tradeoff. You may also get slightly lower overhead with libgpiod/libiio, but the same problem will remain.

In practice we haven't designed the I/O for particularly fast reaction times, as they are primarily intended for electro-mechanical components like buttons and relays, which themselves have very considerable switching delays. That is not to say they cannot be used in that way, but it does bring some limitations with it. In particular our PLC platforms are designed to run with multi-millisecond cycles, Mervis at ~20ms and CODESYS at ~4ms.