@Martin-Randl
Hello, there are no plans for official support and bundle at the moment. However, we do not intentionally block this and you can try to make it working on your own.

@paolo
Hello, the problem is that the wlan0 interface is disabled on our units in U-Boot by default. Those are steps to enable and configure the Wi-Fi interface:

Set up the Wi-Fi parameters:

sudo nano /etc/wpa_supplicant/wpa_supplicant-wlan0.conf

Enable wlan0 in U-Boot

cd /etc/bootcmd.d/
sudo make enable-wifi

Set up management (DHCP) on wlan0:

sudo cp /etc/systemd/network/examples/10-wlan0.network.example  /etc/systemd/network/10-wlan0.network

A reboot is required to reflect the changes in U-Boot:

sudo reboot

@tsandrini
In the new version, the configuration is no longer for the whole unit, but there is one per board. To make it easier for our customers, we encourage them to use autogen, which uses OS configurator to make proper configuration. If you wish to make the configuration on your own, you need to follow these guides: first and second. This is how it will look like for S103:

comm_channels:
  LOCAL_TCP:
    type: MODBUSTCP
    hostname: 127.0.0.1
    port: 502
    device_info:
      family: Neuron
      model: S103
      sn: xxx
      board_count: 1
    devices:
      1:
        slave-id: 1
        model: '00'

@gabrielsoudry

Hello, the 32 bit images are currently unavailable, because of a bug in 32 bit packages, they should be available soon.

Hello @paolo,
just do as the command says, you need to add "-U" to upgrade the firmware from v5.x to v6.x.

Hello @Stoeffel

this looks like something/someone erased the definitions. They are not reinstalled, as they are in /etc/ and treated as configuration files. You can try running sudo apt-get -o Dpkg::Options::="--force-confmiss" install --reinstall evok-unipi-data and see if it helps. If not a deeper diagnosis will be needed.

It is not possible to copy them from 2.x the system was refactored.

Dobrý den, @tomasmedek

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

@tomasmedek said in modbus registry High Word a Low_Word nejsou za sebou:

Přečetl jsem si návod jak v Mervisu číst 32 bitové čísla
https://kb.unipi.technology/cs:sw:01-mervis:connecting-to-modbus-slave-device-hidden
Jak prosím ale číst dva registry High Word a Low Word když nesou vedle sebe, ale mezi nimi jsou i jiné registry? Například registr 653 Low Word a 659 High Word.

Dobrý den,
toto bohužel jen tak možné není, není to úplně standardní případ.

Teoreticky by se dalo číst celou oblast jako byte array a pak to řešit tranformací a poskládáním, ale to už vede na ST.

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.

Hello @Bart-Delaere ,

I am not sure what is the question now, but xG18 does not support humidity measuring, only temperature.

Hello @lukas009,

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

Hello @knebb,
currently we do not officially support Debian 13 or provide any images based on it for Neuron lineup, however, it is planned. Do you have any need for the upgrade?

Hello @iVar,
what is the version of the IDE? This looks like the HMI template sources might be corrupted. Can you send us the solution to support@unipi.technology?

Hello @Achilleas-Kotsis,
why do you use the dkms and not the pre-compiled modules? What is your setup?

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