Hi Gabriel,

You can find most of the information in the articles on inputs and outputs in the products section on our KnowledgeBase.

Below you will find the answers to your questions:

What are the use cases of these relays? Is it dangerous to use these common relays with outputs having different power supplies?

• It depends on the specific circuit connection, but in most cases such a connection is undesirable.

Finally, is it recommended for safety reason to use a different power source between the unipi power supply and the dry contact equipment (in input) ?

• Yes

Hi @Vesa-Kauppinen,

From Unipi Patron I/O boards by:

• Section 1: mbpoll -m tcp 127.0.0.1 -a 0 -0 -1 -r 1003 -p 502
• Section 2: mbpoll -m tcp 127.0.0.1 -a 0 -0 -1 -r 1103 -p 502
• Section 3: mbpoll -m tcp 127.0.0.1 -a 0 -0 -1 -r 1203 -p 502

And from Unipi Extension using ttyNS0 port:

• mbpoll -m rtu /dev/ttyNS0 -b 19200 -P none -0 -1 -r 1003 -a 15

Best regards,
Antonin

Hi everybody,

It has been fixed with a new version of the unipi-kernel-modules package.
At the same time, we increased the output testing of packages.

Best regards,
Antonin

Hi everybody,

It has been fixed with a new version of the unipi-kernel-modules package.
At the same time, we increased the output testing of packages.

Best regards,
Antonin

Hi @lyngaas,

This bug where it is not possible to write a value from the PLC to the connected device appeared in some versions of the Mervis IDE, but we have always fixed it with the release of a newer version of the IDE.

It is currently functional in all Mervis IDE versions supporting BACnet:

• Mervis IDE 2.3.0 (106337)
• Mervis IDE 2.4.0 (117845)
• Mervis IDE 2.4.1 (125493)

Best regards,
Antonin

Dobrý den @Beny44,

pokud budete postupovat dle zmíněného návodu, dosáhnete požadované funkce.
Výsledkem, což se můžete přesvědčit na posledním snímku návodu, je umožnění funkce PWM, kdy pro řízení již nepoužíváte datové body (proměnné) DO_y.x (bool), ale PWM_y.x (real), které mohou nabývat hodnot 0 až 100 (%).

Vše potřebné je v návodu zmíněno.

S pozdravem
Antonín z Unipi

Dobrý den @ladmanj,

To co hledáte naleznete přímo v okně PLC (dvojklik na PLC), konkrétně v záložce tasky.

Ve zjednodušeném módu se každý nový program (i kopie stávajícího) automaticky doplňuje mezi programy mapované pro úlohu. V plném módu je nutné toto řídit manuálně, což je důležité zejména v případě, kdy máte více PLC a každé má vykonávat jiný program a podobně.

S pozdravem,
Antonín z Unipi

Hi @ladmanj,

You can find what you are looking for in the PLC window (double-click on PLC), specifically in the tasks tab.

In simple mode, each new program (even a copy of an existing one) is automatically added to the programs mapped for the job. In full mode, it is necessary to control this manually, which is especially important when you have multiple PLCs and each one has to execute a different program, etc.

Best regards,
Antonin

Dobrý den @ladmanj,

rozdíl mezi zjednodušeným a plným módem je popsán v článku První projekt s jednotkou Unipi.

Doporučuji také přečtení článku o funkci autogen, jejíž chování je přepnutím do plného módu nejvíce ovlivněno.

S pozdravem
Antonín z Unipi

Hi @AllanL,

From your description, I assume it's a wrong connection. The digital inputs on our units are not potential-free, but instead respond to voltages in the range of 7 to 35 VDC. At the same time, it is necessary that the negative pole of the voltage source is connected to DIGND.

More information can be found in the article dedicated to digital inputs:
https://kb.unipi.technology/en:hw:02-neuron:description-of-io:01-description-of-di

Best regards,
Antonin

Hi @johni2212,

Despite all the advantages, this variant has one disadvantage, which is that you have to upload the terminal and all programs to all controllers at the same time.
In general, the web interface (either local or external version) should be uploaded last.

If this is a problem and you do not have a lot of shared data, I recommend choosing Modbus TCP or SSCP communication between the controllers and then using a local web server.

Best regards,
Antonin

Hi @nfmax,

The method of searching/reading 1-Wire devices depends on the SW used. In SW EVOK, searching/reading is handled using the OWFS package.

If you have a 1-Wire cable, for example, next to a power line, it can cause a lot of interference, to which the 1-Wire bus is very susceptible. Furthermore, it is possible that this is an error in the connection of the 1-Wire Hub.
I recommend studying this article about 1-Wire, where the connection, as well as the whole issue surrounding 1-Wire, is dealt with in detail.

If you want to achieve the highest possible stability and only use original DS18b20 sensors (which can also perform parasitic mode), I recommend using the Unipi xG18 (RS485 Modbus device), to which up to 8 DS18b20 sensors can be connected. Due to the higher stability of RS485, it is possible to stably connect a total of up to 80 sensors to one RS485 bus (using ten Unipi xG18).

Best regards,
Antonin