Thank you for your contribution!
Thank you for your contribution!
Currently, the best way is to find out the availability of the Internet connection in the OS and then write this information to the ModbusTCP server. You can create a ModbusTCP server directly in the OS as a separate program or define it in Mervis.
The subsequent logic for switching the relay on/off is already simple.
Unfortunately, so far we only have Neuron S103 with RPi4. This is due to higher cooling requirements and due to the different layout of connectors on RPi4.
The difference in communication speed between the variant in one box and the variant with Extension is not so important for most applications and it always depends on the optimization (number of read registers, reading period, etc.).
In general, you can assume that the speed for internal communication is 115200 bps (and higher) and the communication speed via RS485 is according to the settings, but 19200 bps is used by default due to the excellent ratio between speed and stability.
We always (even for Unipi 1.1) recommend using a secondary external relay and using the relay on the unit only as a signal relay.
It is better to deal with the details of the electrical installation with an installation or inspection technician according to the legislation of your country.
You must create an hmi template for the function block, or for the program. Then insert "Pop-up" in the hmi template for the local web server or SCADA, where a function block, or program can be selected as a variable. Then just select the desired small template (you can have more than one ready for one block, or program).
See the attached screenshots for examples.
The alarm status on HMI is changed automatically according to block BD56.
The solution to your second query is simple: For a flashing state, use a GIF image as the mapped state.
What software do you use on the unit?
This is probably a delay caused by the software and conversion of values in combination with communication with the chip on the Unipi board. In addition, both delay factors are manifested twice:
input signal -> communication -> conversion -> program -> conversion -> communication -> output signal
License request code can be used only once to obtain a license. If you use the request code for an account to which you later lose access, the license cannot be renewed and you must purchase a new license request to generate a new license. We therefore recommend using request codes only on the main account in the Unipi portal.
(more about the license request: https://kb.unipi.technology/en:sw:01-mervis:getting-mervis-licence-hidden)
Have a nice day
Antonín Všetula, technican
The best way to calibrate the AI on the Unipi 1.1 is to turn off the transformation for the AI, connect a voltage source with an output of exactly 10 VDC and look at the value on the AI in the Mervis IDE. Remember this value and then insert it as parameter X2 in the two-point linear transformation.
Set parameter Y2 to 10 if you want to get the voltage value directly, or set to 100 if you want to get the percentage value [%].
Set both parameters X1 and Y1 to 0.
In the attached picture you can be inspired by the settings for my Unipi 1.1.
Have a nice day
Here's a new tutorial: https://kb.unipi.technology/en:sw:01-mervis:hmi-image-hidden
First, I recommend downloading and installing the latest Mervis IDE and Mervis OS available here: https://kb.unipi.technology/en:files:software
Then open the project in a new IDE and save to convert the project to the new version. Before converting to the new version, we recommend that you always create a project archive with a suitable name.
If you use the RaspberryPi 4 computing module for Unipi 1.1 / Lite, this should also solve your problem, as support for these computing modules was added only in the last version. With my RaspberryPi 4 and Mervis v2.4.0 your project works.
The best way to communicate between SW Mervis and third party devices is to implement the Modbus protocol on these devices. Subsequent operation and modifications are simpler and faster. Another great advantage is that this protocol basically allows you to operate multiple slave devices on one serial line.
In this case, Openport is a functional block that takes care of opening the port, ie its reservation within the system.
In the input string (def) for FB io.openport it is necessary to enter for UART port 1: "def: = 'serial: 1: 9600,8, N, 1';". I also enclose a tested code example in ST for Unipi 1.1.
You can use power from the I2C connector for this current. The 5V pin in the I2C connector is directly connected to the 5V power supply from the DC connector.
If you want to be sure, use the capacitor (1000 μF) mentioned in the article on the sensor.
The sensor output is 0-5 VDC. The analog input on the Unipi 1.1 measures in the range 0-10V. Directly measured voltage values are available in EVOK, so it is not necessary to perform further calculations.
You can connect the sensor as you type: connect the ground (-) of the sensor to AI- and connect the analog output (A) of the sensor to AI+.