Hi @martin-kudláček ,

sorry for the superlate response! I went on holiday the day after my last post.

I will try to do the upgrade myself and otherwise we can still do a Teamviewer session. will let you know!

Ahh I was assuming you are using Neuron; with the UniPi 1.1 you need to rename the inputs and outputs in the "evok.conf" configuration file; using aliases with the UniPi 1.1 is not supported as the various subdevices are fundamentally different devices. Whereas for Neuron they are, well, subdevices, which are communicated with via Modbus handles. And it is these handles which are renamed with the alias.

I can have a look if we can implement the aliases for UniPi 1.1 as well, but as of right now it's not possible. We should remove the alias-setting option for UniPi 1.1 from the web inteface.

As for the instructions, they will indeed get you the latest Master version.

@mohamed-dounnani,
your calculations are in order. With the tests we did above, I am afraid you received a PLC with wrong calibration data. The calibration is a way how to ensure that when you set a desired voltage through Modbus registers, it will in fact set the correct voltage on the terminal connectors. The calibration process is one of many throughout the assembly of the unit. The calibration is done on our testbenches and it means you have to send the unit back to us. We sincerely do apologize for this.

Please send me (kudlacek@unipi.technology) your number of order for this PLC and I will get back to you with further information.

Thank you very much,
Martin

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.

@boy-lenssen Yeah, that's something we are working on to protect bricking the units during the FW upgrade process. If the RUN led is dead, send it to us so we can reflash the FW.

@Boy-Lenssen You should be OK.

@blacksoll Those products are only temperature sensors. If you are looking for humidity sensor, take a look at our offer of the Sedtronic products: https://www.unipi.technology/sedtronic-1-wire-sensor-p67?categoryId=3

Martin

@Giamba or maybe @Martin-Kudláček, i'm using this program to control my dali controler which working fine now except from the switch function.
When i push my my mometary switch on HMI and keep pushing it the light slowly increases or decreases at the next push. That's all working fine. But the switch function does work fine trough the g on the sel_0. Only problem is that when i start the plc the light is off (is ok) but the input on sel_0 is true so that results in no output on the sel_0. When i keep pushing the switch on the hmi the light increases on the output of the b30 counter but not on the output of the sel_0. Only when i realease the button the sel_0 output wil be the same as the output on the BD30 counter. After the sel_0 is high on the output and the lamp is on. i can switch the lamp on/off with a short push, no problem.
What i need is : Long push > increase or decrease light (even if the plc is just turned on) short push > turn light on/off.
Can anyone help me with this funtion to work fine?

Many regrards,

John-paul
M203_Dimmer.png

Alright, thanks! I'll try the package installation on Raspbian and report back if I have any issues.

@mdturnerphys Sure! We expect to release the new Mervis IDE and required tutorials on our new knowledge base this Friday.

Hi @knebb.

We use a modified kernel. You can use the commands

apt-mark hold raspberrypi-bootloader apt-mark hold python-tornado apt-mark hold raspberrypi-kernel

to prevent it being broken (also true for the Tornado webserver).

As a side note you should generally not do apt-get upgrade regularly on a non-desktop Linux system. 90%+ servers in the world do not do so to avoid precisely such issues. The same goes with any custom software. It's really only "safe" to do on a desktop with only standard packages, and even then it can sometimes break things. This is in fact the reason why Linux keeps older versions of packages in the repositories in the first place.

We plan to release packages, but all the above will still apply, functionally the differences will be
a) possibility to update UniPi software via apt
b) not needing to use the above commands manually (they will be instead done by the packages during installation)

You are of course welcome to compile the kernel yourself against any version which you wish, it's openly available in our repository.

We are sorry for that @zorro_66!

But it is really hard to find out this kind of issue during our test but we will update our testing procedures... Thanks for the info.

Hi @vesa-kauppinen,
writing 1 to coil 1001:

mbpoll -m tcp -a 0 127.0.0.1 -t 0 -0 -r 1001 1

Writing 0:

mbpoll -m tcp -a 0 127.0.0.1 -t 0 -0 -r 1001 0

You can learn more from the quite detailed help of the mbpoll:

mbpoll -h

Regards,
Martin

Ah, well. No I am absolutely fine with this.

My Cacti monitors the system every 5 minutes. So no need for faster- I am fine with a minute.

Thanks again!

Oh, and it is working stable. Now running for nearly 2days without a reboot.

Hooray @alydersen! Thanks for the feedback, we will update the documentation.

Martin

Hi @martin_triska,

Yes, that sums up the situation well, so I'll write to support@unipi.technology for replacement request.

Many thanks,

Pascal

As promised, here is the feedback.
The problem has definitely been solved.
Many thanks for the help

Kind regards
Stefan

@Merv Thanks a lot for the info!

@Wim-Stockman I will take a look at it during the next week. Thanks for the tip.

I did not check the code much but there should be some time buffer while decoding the correct input. The messages does not always come at the same time, there might be a tens of ms gap between each and you shoudl tie those together...

Yes, that it should work.