@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 ,
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
This is not a standard feature of ST or FBD but there is a small hack to achieve this. See the example below. It only works if the input variable is named "in" (the same works for output variable named "out") and the type is array.
FUNCTION InDemo : LINT
VAR
i : INT;
END_VAR
VAR_INPUT
In : ARRAY[0..63] OF BOOL;
END_VAR
(*function block's body*)
result := 0;
FOR i := 0 TO 63 DO
// nejaky kod
IF In[i] THEN result := result + 1; END_IF;
END_FOR;
InDemo := result;
END_FUNCTION
Hello @wicked,
an alternative way to read data from the is Modbus RTU utilizing the RS485 serial line. Unfortunately, that only available as a standard feature of Neuron and Axon lines, but not in Unipi1. However you can use any USB-RS485 converter which is available on the market.
Hi @ZigZak,
did everything worked well after the call and email with our Support?
Hello @tmmke,
the baudrate and other parameters should be configured as decribed in the product information https://www.unipi.technology/unipi-neuron-s103-g-p107?categoryId=8
If you are using the latest Mervis IDE and Mervis OS 2.3.0, you do not need to worry about the setting the GPIO18, which is done automatically.
To send the SMS, you can follow similar tutorial https://kb.unipi.technology/en:sw:01-mervis:sending-sms-hidden
GPRS (internet) connectivity is not supported in Mervis and has to be done manually in the Linux as discussed here https://forum.unipi.technology/topic/463/s103-g-use-gsm-gprs-module-to-connect-to-internet/7
Note: The modem cannot send SMS and provide GPRS connectivity at the same time!
Hello @LubomirMaron,
If you decide to go with Meris, do not mix other solution - the direct switch functionality can be configured in Mervis as well. You see it's disabled because Mervis does not read the actual configuration from the device. It expects that the IDE is the only tool to configure the HW so the latest configuration should be there.
However, the previous configuration of DirectSwitch should not have any affect to Mervis. Are you able to deploy the solution to the PLC? Could you share yoru solution with us?
Pro využití všech předností Mervis SCADA je nutné mít PLC připojené na Proxy a nastavené posílání dat do DB. Pokud máte takto PLC, které řídí FVE, již nakonfigurováno, nemusíte do programu vůbec šahat a stačí "pro jistotu" zkopírovat složku projektu a následně otevřít zkopírovaný projekt v Mervis IDE (min. verze 2.3.0) a postupovat dle návodu https://kb.unipi.technology/cs:sw:01-mervis:mervis-scada-project-hidden
Samozřejmě je možné pro SCADA využít i další PLC, které bude fungovat jako prostředník. Ideálně využít interní protokol SSCP po IP, který vám ušetří práci s vytvářením a udržováním Modbus tabulky. Výhoda je, že opravdu nemusíte zasahovat do původního projektu. Návod máme bohužel jen na verzi, kdy jsou obě PLC v jednom projektu viz https://kb.unipi.technology/cs:sw:01-mervis:multiple-unipi-through-sscp-hidden Ale stejně tak je možné vytvořit úplně nový projekt, přiřadit PLC a přidat nový Zdroj dat (pravé kliknutí na položku Systém v Solutuion Exploreru), vybrat zdrojový soubor projektu z prvního PLC (ve složce /bin) a nastavit parametry připojení.
Relays on Unipi 1 are ware wired via I2C gpio expansion so you will needsomething a bit more complicated. There are many options:
Hello @johni2212
what SD cards are you using? The commonly available SD cards uses MLC technology which is good enough for phones/cameras, but not recommended for automation. We recommend using SLC cards such as https://www.unipi.technology/2gb-industrial-microsd-card-slc-p232?categoryId=33 which are much more reliable and handles the unexpected power outage much better.
@HonzaS Did you make it working?
Can you check the statistics registers 2000+ / 2100+?