@seb There is a bug in the HW description of the M10x. Please download this file0_1495698539968_UniPiTechnology.Neuron_M10x.1.hw rename it to UniPiTechnology.Neuron_M10x.1.hw and replace it with the one in your instalation sub-folder \HwLibrary\PlatformIO (eg. C:\Program Files (x86)\Mervis\IDE 2.0.10 (52674)\HwLibrary\PlatformIO)

Then restart the IDE, delete the M10x from the TCP Modbus Channel and add it again, it should work well.

Sorry for the inconveniences.

@PhilesG Would you please try to update the our kernel modules to the latest version? You can do this by apt update && apt install unipi-kernel-modules or by rewriting the whole OS by a new one from https://kb.unipi.technology/en:files:software:os-images:00-start#axon_generation_os using this guide https://kb.unipi.technology/en:sw:01-mervis:running-on-axon-hidden#flashing_the_os

Hi,

the Neuron does not use the GPIOs of RPi for the I/Os. Instead there are 1-3 ARM processors (depending on the S/M/L Neuron version) for each group which communicate with the RPi using SPI, where a kind of Modbus protocol is used.

We are working on the Evok to be finalized and debloated images. Right now there is a pretty simple possibility of using the TCP modbus server (available at localhost:502) which is included in the Mervis img, map of the register is available at http://downloads.unipi.technology

So the easiest way for you might be to get a C++ library for TCP Modbus and get the advantage of the Modbus interface.

Do not forget to stop and disable unneeded seriveces which are included in the Mervis OS:

systemctl stop sharkrt
systemctl stop configtool
systemctl disable sharkrt
systemctl disable configtool

@Boy-Lenssen You need a power supply (5-24V) as on the picture in the documentation negative pole (-) goes directly to DIGND. The positive pole(+) goes through the device (in your case the magnetic contact) to the DIX.Y. So one cable of the mag. contact goes to power supply and the other to Di.

@msoenen The issue is that you deleted the definition of the L203 device on the Modbus channel (if you double click on it, you will see that its empty). Delete it and insert a it again. Make sure to set the autogen on the device since you are in full mode (simple mode does that for you).

@Boy-Lenssen I am sorry for that but we had to move on from the RPi GPIOs forward to allow better scalability and variability of our products.

Mervis is basically if this than that platform that runs in loop... Not a realtime solution but suitable for most automation applications.

Hello @Boy-Lenssen ,

• list itemDIs are a galvanically isolated so unless the voltage and current will stay in the limits, you should be OK
• Digital outputs & analog inputs and outputs are coupled together to common ground. So a there could be a risk of potential damage to these components when you are off the limits.

But do not worry the device is designed to provide maximum reliability when installed in the standard installation environment. And yes, replacing the device in case something goes wrong is the easiest and cheapest solution.

@msoenen Only the device on the Modbus TCP channel, not the whole PLC.

The proxy configuration looks good. Did you upload the configuration (right click on PLC - PLC operation - PLC setup)? If you are connected to the PLC via the LAN and start the debug mode, check the Proxy information in the System Status.

@Boy-Lenssen All the I/Os (except 1Wire) are acessible using the TCP Modbus protocol, the map of each register/coil can be found here

Since it does not uses GPIOs of RPi, you do not need to set any pullups. Just use the registers/coils to set and read the states of IOs. You will need to poll the registers/coils periodically to catch the state of the I/O.

I suggest you to take a look at some C++ ModBus TCP library that supports client mode.

You can also use the Websockets, or HTTP REST api that evok provides (it is using the underlaying TCP Modbus): https://github.com/UniPiTechnology/evok#testing-latest-git-versions

@Martijn-Hemeryck Check the documentation of evok https://evok-2.api-docs.io/1.02 but since it is only an API, I cannot give you any hints on how to start with the logic application.

Direct switches are described in the documentation of Neurons at downloads: https://files.unipi.technology/s/public But if you want to control this login in the software, then go ahead. But expect the delay caused by the ModbusTCP <---evok---> webservices delay. But there are topics in this forum how to get evok faster a bit to poll the Modbus faster than the default poll rate to be able to catch fast pulses to the DIs

Weird... @Petr-Helebrant could you please verify it really depends on the Mervis IDE 2.4.0 and its RunTime? @Martin-Kudláček please assist on this

Hello, the Mervis IDE has been released last week. Until this, the NVRAM has been overwritten with every cycle of the RunTime which depends on the complexity of the executed application...

@Petr-Helebrant vám you provider the log from the PLC(right click on the PLC)? Also can you ssh to the PLC (you need to enable ssh und the properties tab and Upload configuration) and check directly from the PLC what IP do you actually ping when you run ping db.unipi.technology ?

Hello everyone,

we suggest using SLC or pSLC cards. The differences are explained in this article https://www.unipi.technology/key_feature/what-are-the-differences-between-memory-card-types-and-why-is-it-important-to-know-them-371

Additionally, check the new upcoming Mervis IDE which features an option to configure the period of writing the nvram file (variables used at startup of Mervis RT) to the storage. If your application handles monitoring, you can set the period to 1minute and significantly reduce the amount of data written to the card.

@Poelie Check configuration of JP2-JP5 since this should be all except the motioned wiring and configuration.

@Peli yes, I have heard that the Conbee, zzh and Slaesh's are quite OK, but have not tried it on my own.

Yes, the Node-red can run on the same device as Mervis, you'll just need to find your own way how to install and run it.

Dear @Peli as far as I know nothing has been done regarding the Mevis&Zigbee topic. As mentioned previously, the easiest way is to use Modbus Zigbee gateway or some USB Zigbee dongle and implement the SW in a different application (Nodered) and tunnel the data to Mervis using Modbus or Bacnet.

@PhilesG Would you please try to update the our kernel modules to the latest version? You can do this by apt update && apt install unipi-kernel-modules or by rewriting the whole OS by a new one from https://kb.unipi.technology/en:files:software:os-images:00-start#axon_generation_os using this guide https://kb.unipi.technology/en:sw:01-mervis:running-on-axon-hidden#flashing_the_os

@noelvaes Did you reboot after the kernel modules were installed?

The development and support of the Codesys plugins for Unipi products has been discontinued by the developer. Unfortunately, there's not much we can do about it. We asked them to release the package as Open Source... More info at https://kb.unipi.technology/en:sw:03-3rd-party:codesys#codesys_on_unipitechnology_products