administrators

Dobrý den @ptirala,

můžete nám prosím poslat na email ([email protected]) schéma zapojení, archiv projektu a případně i fotky?

Zdeněk z Unipi

Hi @domguard,

The mentioned problems should not be related to EVOK at all. It's not clear from your description what kind of controller you have or what you actually need. Do you need to connect to an existing WiFi, or do you want to create a WiFi access point from the controller?

But EVOK works normally, right?

Best regards,
Antonin, Unipi team

Hello @tsandrini ,

first of all, we appreciate your effort which confirms us the open-source approach is the best way :-).

To your question:

1. Yes, you have to apply the appropriate overlay(s) to the "base" device-tree in order to tell the unipi kernel modules what kind of hardware (I/O boards) is present. Every model of the PLC (e.g. S103, L523, ...) has a separate overlay located in the package unipi-os-configurator-data. In a standard OS Image, this stuff is invoked automatically by unipi-os-configurator based on the identification stored in the internal EEPROM (and accessible via unipi-id module - see /run/unipi-plc/unipi-id, this module should be preset on all our units). Typically, this process needs two reboots - after the first of them only unipi-id is loaded in order to get the PLC model and apply the right overlay. After the next reboot, the previously selected overlay is loaded and all of the peripherals (inc. /dev/unipichannel*) should be available.

2. Anwer is in the previous text - appropriate driver(s) for Unipi-specific hardware are loaded automatically based on the devicetree (devicetree overlay) nodes.

3. Yes, the /dev/unipichannel* represents the main communication channel between the Linux and I/O boards (the second one is sysfs). This kind of device is created dynamically by the Unipi kernel modules based on values given in devicetree overlays. It is used by unipitcp as well as by the firmware upgrade tool.

Has this answer got you forward?

Hello PEPITO82,

The RPi CM4 is currently not an officially supported platform. However, according to my information, should be mostly compatible with "standard" RPi.

One option may be to use the RaspberryPi OS image and install the necessary components: EVOK, Node-RED.

If you also want so-called Unipi nodes for communication with inputs and outputs, which are available in our Node-RED OS image, just add a suitable module from the palette to Node-RED.

Best regards,
Antonin

Dobrý den @ondbyr2561 ,

příklad naleznete na snímku níže:

Přeji hezký den,
Antonín z Unipi

Hi everyone,

In these cases, this guide can help: https://kb.unipi.technology/en:sw:01-mervis:automatic-restart-of-1-wire-hidden

Unfortunately, if you have improperly processed cabling, or if you have a large number of sensors connected to this bus, you cannot achieve the desired stability, because the 1-Wire bus is very sensitive to interference.

In this case, I recommend checking the wiring to make sure you have all unused wires and the cable shield connected to the ground terminal. Next, check the length of the bus and the number of sensors on the bus.

An alternative to this connection is also the connection of sensors via Extension xG18, which has 8 separate 1W channels, each reserved for one sensor. Perhaps the only disadvantage of this module is that it is possible to connect only sensors DS18b20 and supporting parasitic power.

Finally, I also recommend reading this article about 1-Wire: https://kb.unipi.technology/en:automation:02-glossary:1wire-hidden

Best regards,
Antonin, Unipi

Hi everyone,

Currently this is possible by flashing Mervis OS and then installing Node-RED following the standard installation instructions: https://nodered.org/docs/getting-started/raspberrypi

However, this solution is not tested and we cannot guarantee that the Mervis RT will behave correctly if other such demanding SW is running on the controller.

Best regards,
Antonin, Unipi

Hi @Vesa-Kauppinen,

try apt update && apt upgrade again.
We made some adjustments due to the new Unipi Iris HW, but this should work fine now.

Best regards,
Antonin, Unipi

Hi @lukec,

You can try the current Node-RED image, which is available at this link: https://kb.unipi.technology/en:hw:007-patron:download-image:02-nodered

Best regards,
Antonin, Unipi

Hi @Brzezinol,

you can try using nginx + LetsEncrypt for this.

Best regards,
Antonin, Unipi