Hello @ntd,
there should be no stability issues with the old firmware, some features might be absent and there may be some bugs, but if you test it and it works fine, it should be okay.

Using different profiles for each PLC partially solves this, as they store the PLC properties and configuration. But they don't store everything, for example the terminal settings (SCADA Terminal parameters, PLC History profile). So currently I have to change the terminal settings manually. I suppose there's a better way to do it with multiple terminals, but I struggled to get this to work.

Dobrý den,

ten result, u toho bloku se mění jen když je špatně uveděný kanál, plná emailová fronta nebo interní chyba.
Pokud Vás zajímá zda se spojení opravdu navazuje, tak při připojení přes SSH lze monitorovat připojení nástrojem netstat.
V tomto případě lze sledovat spojení takto:
netstat -natc | grep 465

Zkuste se podívat zda není na začátku nebo na konci hesla, uživatelském jména, adresy nebo portu nějaký neviditelný znak (např. mezera)

@cleve
Hello Cleve

Thanks for reply.

sudo apt-get -o Dpkg::Options::="--force-confmiss" install --reinstall evok-unipi-data

Did what it was supposed to do.
Thank a lot for your help.

Dobrý den, @tomasmedek

příklad nemáme, takto specifická věc není součástí standardní neplacené podpory.

Hello @Bart-Delaere,
unfortunately there is no definitive answer. The 1-Wire bus is technically able to connect huge amount of devices, but reality depends on cable length, quality, noise from the environment etc, so this may be trial and error for users that do not install it daily.

Unipi used to sell a hub/splitter, which we do not offer anymore.

Sometimes, a surge can occur in the environment, which can take down the whole bus. Unipi units (except Unipi 1/Lite) have an option to restart the bus (the bus is not restarted during normal system reboot), you can look in the Modbus table of your unit if you wish to implement it.

Is nobody using the Analog output (0-10V) to dim LED lights?

@cleve
Thanks for letting me know.

To be honest- there is no urgent need for upgrading.

I just prefer to be on the up-to-date version knowing the old stable gets outdated faser than expected ;)

Do you have an estimation when it might be available for Trixie?

Thanks!

/KNEBB

Hello @lukas009,

we plan to release Debian 13 based systems, but we do not have any ETA.

Tak write on change dělá přesně to co potřebuji.

Proměnnou lze modifikovat z druhého místa, ale sesynchronizuje se zpět, když se změní stav logiky v FBD.

Píšu pro případ, kdyby se to někomu také hodilo, protože v dokumentaci o tom není ani píp.

Pro ty koho by to také zajímalo, zkouším https://github.com/cervenyxp/hass_sscp_integration
Zatím to oťukávám, ještě žádné konkrétní výsledky. Nejprve musím přijít na to jak to celé efektivně "architektovat".

Found the mistake.
It was in PLC settings - Web Parameters, wrong Definition Directory.

@cleve Because I never use precompiled modules on debian based systems if I can help it since dkms was introduced in the '00s, I like the flexibility of not having to match kernels with specific precompiled modules.
For example, right now on one of my systems:
unipi-kernel-modules : Depends: linux-image-rpi-v8 (= 1:6.12.20-1+rpt1~bpo12+1) but 1:6.6.74-1+rpt1 is to be installed

I have multiple rpi3 and rpi4 based neuron systems that I maintain, most are runing raspberry pi os bookworm aarch64. BTW unipi-kernel-modules-dkms=2.70~bookworm builds just fine until at least linux-image-6.6.74+rpt-rpi-v8

Hello @lukec,
I have sent you an e-mail with further questions.

@cleve

Neuron M103 (the old one, not the current) which is still running with Raspbian 10/ buster.

How do I get the information about the firmware?

(BTW: I tried to upgrade to latest Raspbian, but failed)

Hello @knebb,
we do not provide support for Buster based systems anymore. However, on the latest firmware with BaseOS 12, the value is the actual value (the datatype is real - float32), there is no further calculation needed.