Topics created by roberts_lando

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

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

@PhilesG The steps (if done correctly) only resize the partition so no data is lost. BTW is something goes wrong it could. I know @Martin-Kudláček also proposed me to create a script to automatically fix the partition problem, I think that would be the safer way

Hello @roberts_lando,
here is a complete list: https://kb.unipi.technology/en:hw:01-axon:portmap

Best regards,
Martin

Do you have some USB-RS485 converter to test the communication

@martin-kudláček the only way to make this working is using a converter that also has GND, it's strange Unipi doesn't support this.

The I2C is working as you can see in the output of the i2cdetect. However the ds2482 module is not loaded. You can load it on hand using

and see if the address 0x18 in the i2cdetect will be marked with UU and you should see the list of connected 1wire devices in the /sys/bus/w1/devices/

@tomas_hora it's not a security issue but as I'm using another plc runtime with a local modbus tcp master running on port 502 unipitcp service was blocking it. I have disabled it and modbus has started working correctly

@roberts_lando Sorry, dont know.

@roberts_lando Evok uses the Modbus TCP interface to interact with the IOs, disabling it will cause that evok wont work.

You can disable it by calling "systemctl stop unipitcp" and "systemctl disable unipitcp".

Oh I have missed that line, I was looking for "static" word in that file. Thanks :)

@tomasknot This is really nice! Thanks so much I will adopt this approach.

Hi @martijn-hemeryck,
We changed the repository's name to unipi-python-lighting and it resides here: https://git.unipi.technology/UniPi/unipi-python-lighting

Hello everyone, if you use the UniPian image, than the RS485 is available in /dev/extcomm/0/0 (symlink to /dev/pts...). You do not need to do anything with the RPi UART interface.

If you have your own image, than the neuron_tcp_server is taking care of the RS485 (so the neuron tcp server must be running) but the port configuration has to be done using the Modbus registers (as described in the Modbus maps).

@roberts_lando I am afraid we won't be able to provide support to every question on slack...

I think I will stop using Mervis as main IDE as it only works with the image you provide. I think a better approach would be having a runtime that can be installed in an existing SD with upgrading features, this approach makes each update very hard expecially if you have to work with lot Unipi devices at same time... I would have to reinstall the image in each device each time an update comes out than reinstall all other softwares I need

The issue was by the incorrect comm speed with the modem. I modified the guide provided by @roberts_lando to use the proper baudrate of 9600 instead of 115200.

The issue was by the incorrect comm speed with the modem. I modified the guide provided by @roberts_lando to use the proper baudrate of 9600 instead of 115200.

@roberts_lando
For me I have Mervis Modbus client wich write registers in my C program modbus thread.
Then I have an other thread wich take care of changed values and publish on a topic to the mosquitto broker.
I have an other thread wich make some stuff on values, like a subscribed return value wich update modbus register before reply to modbus client.