Hi,

How can i ask the holding register 1003 with mbpoll?

@AVsetula said in Reading the ModBus bus with the Patron:

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.

Thank you!

/Vesa

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.

For the record, this issue is currently being dealt with over email.

Martin

So the 1 wire stopped working again. I tried running the mbpoll command from Stefan, but it's not working.

Not sure whether the $ on the end of the line is some typo, it seems not valid, mbpoll complains about.

As I understand it, the command tries to set modbus coil 1001, which is named 'Enable/Disable 1Wire Bus' in Neuron documentation.
It seems the Mervis variable OW_off_1 is mapped to the same modbus coil, so turning it on/off should do the same thing. (UPDATE: confirmed by updating the variable in Mervis and watching by mbpoll)

Any other ideas?

Hello everyone,
we have just released updated Zulu kernel, which solves this particular problem.

The problem has been in the memory lock, which overused the swap, even when the swap is off on all our OS images. This has been fixed in kernel 5.10.17+. The new kernel is 5.10.35.

Whole suite of OS images is currently being generated and within an hour uploaded to the Download section

Thank you for reporting the issue nad have a nice day,
Martin @ Unipi

Hi @knebb,
you have verified, that the HW is working and returns correct value via standard tool. Checking and fixing your code is unfortunately beyond the scope of the free support.

Thank you for understanding and have a nice day,
Martin

Hi @knebb,
the firmware has been updated on our Knowledge Base as well: https://kb.unipi.technology/en:files:products:05-sensors:iaq

Martin

Hi @Csevi,
in short - the 1-Wire hub is passive device, which helps with the "linearization" of the star topology. You can find complete information about 1-Wire here: https://kb.unipi.technology/en:automation:02-glossary:1wire-hidden

Best regards,
Martin

Hello @daminou53 ,
we have released the Patron kernel (more precisly the "Zulu" kernel - Zulu is the codename for the SBC). Here's the repository: https://git.unipi.technology/UniPi/zulu-linux. Here are the config files: https://git.unipi.technology/UniPi/zulu-linux/-/tree/zulu_5.4.70/arch/arm64/configs

Best regards,
Martin

Dobrý den @lukas009,
ano, pokud má digitální vstup odpovídající releový nebo digitální výstup. Více o tom se dočtete zde: https://kb.unipi.technology/cs:hw:007-patron:description-of-io:01-description-of-di

S pozdravem,
Martin Kudláček

@tomas_hora, thank you.

I have been reading more about your products and I found out that EVOK provides websockets. I was thinking that I would write a script which would process MQTT messages from a dongle and deliver them to Mervis using websocket and the other way around. Would that work? It would replace the Node-red which you suggested.

Thank you for your help, Martin.

I fixed by simply removing gateway and dns-nameservers definitions from the eth1 file.

If anyone is interested in this the solution to make this working with also the gateway check: https://www.thomas-krenn.com/en/wiki/Two_Default_Gateways_on_One_System

Hello @Jan-Toth,

you have not specified IDE/Language used. For example, in Mervis IDE you can use the following approach:
Automatic restart of the 1-Wire bus

Can you share more info about the application?

@martin_triska said in 1-wire sensor and modbus sensor:

in this case, you have to tie the wires manually ON THE SENSOR. According to the photo, you have to connect dark-green and light-brown wires together ON THE PCB

Yes, that did the trick!

Thanks for the education and superb support here Martin. Really enjoy using your products.

Thank you for the clarification, @Martin-Kudláček .

You are absolutely correct sir!

Thanks a lot for your help - now it works like a charm. I've used Neuron's RS485 for communication with xS11 and separate USB dongle with CH340C chip (a bargain really, $2.7 from CZ shop) for communication with PRO1 energy meter through the same Node-RED setup getting data from /dev/ttyUSB0.

It's a pity that I cannot edit my previous post ^^ - feel free to edit it with a big warning that you cannot combine multiple processes on one serial (which is absolutely logical, but for us: HW newbies not obvious).

thanks for your information.

I have connected a 4 wire cable very close to the three wire sensor and connected the data line to 2 wires in order to use the hub. At the moment it works.