Posts made by Martin Kudláček

Hi @dickesc,
I would suggest to take at our Connecting to Modbus slave tutorial. You can select USB1 - USB4 in the configuration of the ModbusRTU channel.

Best regards,
Martin

Hi @martijn-hemeryck, those are great news! I'm glad we were able to put it together, together:) I'm looking forward for your results.

Martin

@Martijn-Hemeryck See updated answer.

Hi @ntd,
I don't have any USB sound card here at the moment, but I googled "headless pulseaudio" and so far this tutorial looks OK:

https://askubuntu.com/questions/28176/how-do-i-run-pulseaudio-in-a-headless-server-installation

The only change I did is in the first command, to which I added --no-install-recommends and it omitted the GUI stuff:

sudo apt-get install libasound2 libasound2-plugins alsa-utils alsa-oss --no-install-recommends

Again, changing kernel in embedded devices is the latest thing you should do. And I am sorry for the misinformation about the stock kernel vs. kernel provided in axon-kernel package, you are correct.

Martin

@martijn-hemeryck Each channel has to have its own power supply because otherwise you would connect all the buses together.

We don't have any trusted DALI PSUs, but Meanwell is my personal brand of choice. The only thng you need to select is the wattage and that can be deduced from the devices which you intend to connect to the bus. Some devices are powered only through the bus (switches,..), some devices have their own power supply connections (typically the more power hungry - lights and so on)

Edit: The DALI PSU is a special power supply, which powers the transcivers in the DALI devices connected to the bus and the maximum current for the bus is 250mA. The reason, why we didn't integrate the PSU into the Axon S605 is the size and the convenience of having the external power supply. The power supply should be in the middle of the bus and when the PSU dies, it is easier to replace it instead of replacing the whole PLC.

Martin

Hi @martijn-hemeryck, just a quick question - do you have the DALI power supply connected to the bus? The topology of the DALI has to be like this:

https://sc01.alicdn.com/kf/HTB1I_7_vmtYBeNjSspkq6zU8VXa3/200507234/HTB1I_7_vmtYBeNjSspkq6zU8VXa3.jpg

Martin

@ntd Downgrading of the kernel could work, but it is never the correct solution, since you will not receive updates.

The alsa-base image is not the correct one: https://packages.debian.org/search?suite=all&searchon=names&keywords=alsa-base

The preffered sound system in Debian is PulseAudio, so try following this information: https://wiki.debian.org/PulseAudio

Best regards,
Martin

Hi @ntd,
the kernel for Axons is a stock kernel provided by Debian. Can you check how your USB audio card is detected? Unplug it (if already plugged in) and then plug it again and run these commands (the lsusb will need usbutils package)

# dmesg
# lsusb

The problem probably lies in missing audio subsystem, which we ofcourse omitted. You can try following any Debian tutorial for installing ALSA or PulseAudio.

Is this answer sufficient for you?

Best regards,
Martin

Hello @msoenen,
unfortunately we don't have any beta version of MervisIDE which can upload the project to SCADA, yet. My personal guess is that we will release it by the end of the August/September.

Martin

Hello @henkka,
the ModbusTCP server is still actively developed and it is our most supported API. On Neuron and Axon, make sure you have the most up-to-date version of unipi-modbus-tools package, which you can find in our official repository: https://kb.unipi.technology/en:sw:04-unipi-firmware#apt_repository
Then you can access the ModbusTCP server on 127.0.0.1:502. The documentation of Modbus Registers Map for each device is here: https://kb.unipi.technology/files:products:00-start

If you need very fast access to the IOs (except 1-Wire), I would suggest you to take a look at the SysFS approach. You can find documentation of the endpoints here: https://git.unipi.technology/UniPi/unipi-kernel/blob/master/docs/sysfs-platform-unipi.txt

Let me know, what you have picked.

Best regards,
Martin

Hi @ayone0518,
then I suggest you to take a look at PyModbus, especially the client example: https://pymodbus.readthedocs.io/en/latest/readme.html#example-code

On the side of the Mervis, you need to create Modbus Server, see: https://kb.unipi.technology/en:sw:01-mervis:setting-modbus-server-hidden

In the Mervis Modbus Server, you will define registers and coils pointing to some Mervis variables. In the Python script, you will write value to these registers/coils.

Best regards,
Martin

Hi @Matt,
the safe way is to include the whole Mervis project directory.

Best regards,
Martin

Hi @ayone0518,
short answer is you can't.

Slightly longer answer is you can, but I don't recommend it.

The Mervis is sort of world of its own and it's not easy to make it communicate with anything over other than supported protocols. If we need to use external scripts in our projects, we use simple python script which acts as a ModbusTCP slave running inside the PLC on 127.0.0.1:503. You can add this device in the Mervis and communicate with it via registers and coils. It works, but it requires some deal of work.

Best regards,
Martin

Hi @anders-kjellström,
it works, you can check in the default installation of the Evok:

Do you have some example where the aliases don't work?

Best regards,
Martin

Hello @raubucs,
there is no such function, you have to exchange the cables at the connector side.

Best regards,
Martin

Hello @burnscm,
moreover, the Modbus doesn't allow to have address 0 and you cannot set the address 0 via our DIP switches. When the DIP switches are in "0" position, the extension uses the address which is stored in the NVRAM, which, by default, is 15.

Best regards,
Martin

Hello @juntiedt,
I'm sorry for not getting back to you in timely manner. This error is in the Evok and we have created a bugfix. Next week we will release a fixed package and if everything goes well today, the source code will be available on the Evok's Github.

hank you for your patience and have a good day,
Martin

Hello @sppilka,
the Evok is not suitable for being exposed to the Internet. You can try using some VPN solution (Wireguard seems interesting). The VPN server could be installed on the PLC and you could have clients on mobile phones, laptops, etc...

Best regards,
Martin

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

Hello @samsoric,
this isn't a known issue. However, I cannot replicate it:

Can you please provide which Evok version do you use, how did you install it and what PLC do you have?

Thank you for the infromation in advance,
Martin