@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.

@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.

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

@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).

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.

@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.

@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.

@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

@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

Hello,

you have to create your own library. In general it is best to create an empty project just for your own libraries. Then just create a new librry project and your FB within it. By compiling the project a .slb file will be created in the library_project_name folder within your project. This file should be copied to the C:/Program files/Mervix (xxx)/Library

Hello @pascal37, I did not men to capture the data at the time it stops responding, but jus to get a longer period of the caputed data after it stops communicatig to find out if it's all timeout or what is going on the line.

What should be the configuration of the RS485 (baudrate, parity, ...)

Could you execute this command in linux while the communication stops?

cat /run/unipi/io_group1/uart_config

If you are using Axon or Neuron, use our official image with preinstalled Node-Red https://kb.unipi.technology/en:sw:03-3rd-party:nodered#os_images_with_preinstalled_node-red images for Unipi 1.1 and Lite are coming out soon

Do you see the PLC when you try to Attach it againg? (Right click on PLC->Attach PLC -> UDP Broadcast)

@pascal37 if it occurs again, please send the captured data on the port monitor in txt file from a longer period so we could get better overview

@tin-androić What do you see when you try to re-attach the unipi lite again?

@viljar-kaarde Fixed in the update of the app.

@pablofsmelo did you figured it out?

This is a very rare issue with stuck SPI line, let us know on email or phone when/if this happens next time so we can see it.

@csacher Do you mean the read period or what?

It will fit OK, however it will complain (just a warning, not an error) about old device prototypes, because newer version v2.1 are already available in the IDE. Prototypes v2.0 will be marked as obsolete in the next release so it will be needed to update to v2.1 later.