@abornand Hi ! I use aeotec z-stick with unipi and pimatic. The pimatic plugin works with neuron too. No problems so far. I control around 11 devices. Althought pimatic is at beta stage, works now for my home automation over a year.

@jelle the levels can be different if you configure the jumpers to use different power supply, if you are using the onboard 12, then the GNDs are on the same level

@martin-kudláček sorry for the late reply. My node-Red interface is only used to send/receive the intensity to a specific address or group and create scenarios. Once you have documented your documentation about dali I could check the files and try to make some changes and pull requests to the projects if needed. Thanks

Hi @Nico! That looks like it's most likely a physical layer issue. I would check the solder joints as well as check for any possible shorts of breaks in the cable due to bending. The 1Wire should be able to go out several times further than 10 meters; perhaps try using a CAT5 cable or similar for added overall shielding.

@mdturnerphys Unfortunately no. But for example, you will need to create a Server channel on one side (A) select port different than 502 and map your variables to holding/input registers/coils so you can read and write to them from the other (B) side. You can map the variables to Units for example 0-10 (if you need more, just map it as you wish). On the other side just create a custom device on Modbus TCP channel (B), set the IP address and port of the (A). Then on (B) create a read group with starting register 0 and 10 number of registers and map the variables from (A) to data points (create datapoint by right click, assign read group...). Check F1 help of Mervis for 'Modbus' there is a nice explanation. You can also check eg. the Inepro example project from our downloads section.

Thanks for the reply. In short: Modbus TCP - MQTT: I'll probably just start off simple, by polling the Modbus server and exposing any changes as MQTT events. That way, I can get some feel with the setup and I can dig deeper later on. It's nice to know I can come back here for some assistance :) the LED strip: tried it the other day, and it just works; I hadn't taken the time before to properly connect them. DALI: looking forward to hearing more about it; had already seen the thread / python-dali before. Just good to see I'm on the right track here :)

@martin-kudláček My fault, did not do step 1 in your decsription above since fwserial and firmware files were already present. It's 5.18 now, thank you!

@joe160781 Discussed in email communication

Hi @Boy-Lenssen, I have created a tutorial, how to flash the firmware via SSH: https://forum.unipi.technology/topic/693/multiple-xs50-on-a-l513-rs485/20 Let me know, if you are OK with this. We certainly can update the firmware for you via Teamviewer as promised above. Thanks, Martin

Hi @DSurname , if I understand it correctly, you are running your application on the M103 and you want to control the inputs/outputs on the M103? In that case, you cannot (or shouldn't) use ModbusRTU, because there is no Modbus Slave (Server) running on the M103 by default. To access those inputs/outputs, you can use many of the supported interfaces described in the official documentation: https://evok.api-docs.io/1.0/jKcTKe5aRBCNjt8Az/introduction Martin

@nash_78 Does not seems to be related to the previous topic. It seems you are using UniPi 1 guide instead of UniPi Neuron - https://store.codesys.com/unipi-neuron-for-codesys-sl.html

@tomasknot Thanks. I had Unipian image with old version of EVOK. After flashing new image, everything works.

Hello @Neethu, The Schneider EM6400 supports Modbus and you can read the values into Evok or Mervis. The L&T ER300P has RS485, but with some custom L&T protocol. You cannot easily read the data into Evok or Mervis. Typically, the best way is to use Modbus devices. Trying to implement any other protocol would be quite time consuming and requires vast knowledge. Martin

ok i just figured out i apparently changed the resolution somehow with some random clicking to get the sensor going. (i found the PDF file on how to change resolution of the DS18B20)

For anybody else looking for the evok-alias.yaml file, I found it under /var/evok/evok-alias.yaml Andreas

Hi..i am a new user here. As per my knowledge many times you would not use the power from the USB-UART converter. The target device will provide power to the UART. All you need to connect is Rx,Tx and Ground. The TTL signals come in different flavors. 5V, 3.3V and 1.7V being common. This is all the more reason why not to use the power from the UART adapter. Put 5V TTL on 1.7V TTL pins and something will fry. Use no power from the UART adapter.

Hello, the config file is utterly wrong. If you don't use any extension, you need to comment out all the lines of the [EXTENSION_1] block, not just the [EXTENSION_1] line. The syntax of this config file is based on the INI file. That means the active lines of the config where assigned to the [NEURON_1] block, thus resulting in unexpectable behaviour. ;[EXTENSION_1] global_id = 2 ; Mandatory, REQUIRED TO BE UNIQUE device_name = xM103 ; Mandatory modbus_uart_port = /dev/extcomm/0/0 ; Mandatory ;neuron_uart_circuit = 1_01 ; Optional, allows associating extensions wi$ ;allow_register_access = True ; Optional, False default, is mandatory with third-p$ ;address = 1 ; Optional, 1 default ;scan_frequency = 10 ; Optional, 10 default ;scan_enabled = True ; Optional, True default ; Note that the following settings will be inherited by other devices sharing the same port, i.e. /d$ baud_rate = 38400 ; Optional, NEEDS UNIPI IMAGE TO WOR$ parity = N ; Optional, NEEDS UNIPI IMAG$ stop_bits = 1 ; Optional, NEEDS UNIPI IMAGE TO WOR$

Hello @Martin-Freundl, first of all, you shouldn't apply 24V to a 0-10V input. There are 12.5V transils on the input, so you probably burned it. The voltage measurement happens between the AI input and the AGND. The AGND is not connected to any other GND. Thats why you didn't measured any voltage between AGND and 24V. Martin

It is possible, but it requires using our image instead of Raspbian. You should be able to use /sys/devices/platform/unipi_plc to find out more information about the system, or simply run "sudo dmesg" after boot, as the image driver performs automatic diagnostics.