@derinex The most important changes is described in the newsletter or also in the news on our pages https://www.unipi.technology/news/introducing-the-new-mervis-ide-2-2-0-295

All changes are inlcluded in the builtin changelog of Mervis.

@wavoigt We have tested HMI terminals from weintek like this one https://www.unipi.technology/weintek-mt8051ip-p198?categoryId=29 via Modbus RTU (RS485). Works well but the SW setup is a bit complicated.

Mervis has recently gained BACnet server support so you can connect higher verions of Weintek displays which support BACnet with Neuron or Axon via BACnet/IP

Alternatively Mervis has a web based HMI so you can also use this with any web browser while on the same IP network.

@r3sist thanks for clarification.

The best would be to setup a HMI terminal like this one https://www.unipi.technology/weintek-mt8051ip-p198?categoryId=29

Hooking buttons to DIs would be OK, but you would have to figure out the display since Neuron do not have native support for HDMI or I2C displays.

@beergeek sorry the fwspi should be like /opt/unipi/tools/fwspi -i 0 with root privileges

@beergeek can you paste output of the "dmesg | grep UNIPISPI" command? Would like to know the kernel module version. And what is the firmware version? fwspi -i 0

If you want to call a function(or FB) in a ST, you can create aditional program in ST and call the FB from there.

The display however is a HDMI and cannot be hooked to any DIs.

Hi @pascal37 ,
sure you can run the python scrip on the same Axon. We do not have a tutorial for that, but once you enable ssh (via service interface or using the new upcomming Mervis IDE) you will have access to a linux machine as you know.

What device is it?

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

modprobe ds2482

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/

Make sure the I2C bus is enabled or enable it using raspi-config tool. You should see all the I2C devices as listed in the documentation - eg. 0x18 for the 1Wire interface