administrators

Hi Tad,

When making a complaint or repair, follow the complaint procedure: https://www.unipi.technology/return

In this case, however, it may not be a faulty HW, but only an inappropriate output setting:

• The digital outputs on the Unipi units also enable the so-called PWM mode, where the output is controlled in a different way than during normal on / off switching.
• Another function that could affect the outputs in this way is the so-called DirectSwitch function.

If you work in Mervis SW, you can upload the default configuration simply by creating a new project in the Mervis IDE, assigning a PLC and uploading the Unipi module configuration.

For other SW solutions, I recommend checking the values in the Modbus registers.

• To check that PWM is off, check registers 16 to 19, all of which should contain a value of 0.
• To check that the DirectSwitch function is turned off, check register 1014, it should also contain the value 0.

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

Hello @Vesa-Kauppinen,

this has been subject to change between Linux kernel versions - the older one

cat /sys/devices/soc0/soc_uid

comes from the original iMX kernel and has been removed by NXP in newer releases. In our kernel image, we additionally preserve it for backward compatibility.

However,

cat /sys/devices/soc0/serial_number

is a "Linux standard" provided by recent NXP kernels that we recommend using as a unique identification.

Hello @Vesa-Kauppinen,

The 'dev' field describes an object type (similarly to di or relay) so the key has to be constant regardless of the PLC series. You are right, this can be a little bit confusing - it's a piece of history ;-).

Now, we will add the new field of a family containing Patron/Neuron/Axon string.

The 'dev' field fix is a breaking change of the existing API and will be subject to change within an upcoming new Major version.

Dobrý den,

váš předchozí příspěvek prověřím a případně doplním.

Na aktuální otázku je odpověď: ANO, lze funce I/O nastavit i jinak
Pro nastavení u rozšiřujících modulů Unipi můžete použít např. program mbpoll v linuxu (po připojení přes SSH) a komunikovat se zařízením přes modbus, kde si jednotlivé funkce nastavíte dle modbus tabulky.

Přeji hezký den
Antonín

Dobrý den,

licence je skutečně vyžadována až od verze IDE 2.3.0. Ve verzi IDE 2.2.0 se sice zobrazí stav "Nezalicencováno", ale jedná se jen o přípravu.

Doporučuji přejít na nejnovější verzi IDE 2.4.1, která má lépe řešenu práci s úložištěm a nedochází tak při správném nastavení k upisování SD karet, nebo eMMC úložiště (u vyšších řad PLC).

Licenci Mervis je možné zakoupit na našem e-shopu.

Transformaci DS2408_sh_trans nahraďte za lib.Unipi.ds2408_sh_trans. Jsou totožné.

Přeji hezký den,
Antonín

Hello Fabio,

You can select the EMO-R8 module to expand the Unipi 1.1 board with another 8 relays. This module communicates via I2C, as does the relay on the Unipi 1.1 board. Documentation for this module can be found on our KnowledgeBase.

For communication, you can choose either direct control via I2C, or use our EVOK API, which allows you to control, for example, via the REST API or WebSocket.

EMO-R8 connection and EVOK configuration:

You must first set the address jumpers on the EMO-R8 and connect to Unipi 1.1 using an I2C cable. Then connect the power supplies, connect to the Unipi unit via SSH and edit the /etc/evoc.conf file. Then restart EVOK and the outputs on the EMO-R8 will be available.

• In the /etc/evok.conf file, find the lines related to EMO-R8 and uncomment them (remove the semicolons at the beginning of the lines). Open file with administrator privileges (sudo).
  • sudo mc -e /etc/evok.conf
• Then restart EVOK.
  • sudo systemctl restart evok.service

Best regards,
Antonin

Hello Vesa,

Only some Patron ports are available using the deprecated /dev/extcomm/Y/X notation.
I recommend using the ports from the table in this article: Patron serial port mapping

To verify communication with all our Modbus devices, I recommend asking the holding register 1003, which is available for all Modbus devices Unipi and whith contains a unique identifier, according to which the device can also be recognized.

Best regards,
Antonin

Dobrý den,

email k nám bohužel nedorazil.
Doporučuji projekt neposílat v příloze emailu, ale přes libovolnou "úschovnu" a do emailu vložte pouze odkaz ke stažení.

Přeji hezký den,
Antonín

Hi @klaschudi,
can you please post the exact commands (or tutorial) which you followed to install docker? It is not exactly clear just from the error output. Thank you.

In general, Docker is able to run on Patron.