administrators

@raubucs Can you share the whole project? Have you tried all of the RS485 lines?

@heikkim Hello, to enable wifi you should enable the interface in /boot/boot.cmd by commenting the followin lines (add a # at the beginning)

fdt set /soc/mmc@01c10000/bcrmf@1 status "disabled"
fdt set /soc/mmc@01c10000 status "disabled"

Then run mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr and reboot.

Does it work?

@jcmschoot what UART device? Do you have some RS485 usb converter?

@mmcreativ Unfortunately the source project is not stored on the PLC so there is no way to recover it.

@roberts_lando Evok uses the Modbus TCP interface to interact with the IOs, disabling it will cause that evok wont work.

You can disable it by calling "systemctl stop unipitcp" and "systemctl disable unipitcp".

@leif-edh That is doable but you would need to setup WiFi access point on one of those M205 (find a tutorial for hostapd), and enable bridging (available in bridge-utils package).

If you won't use static IP addresses, you would have to also setup a DHCP server on the WLAN and eth, br interfaces.

This tutorial might help you a bit: https://www.cyberciti.biz/faq/debian-ubuntu-linux-setting-wireless-access-point/

Another option is to put a router AP in the middle of it all.

Also, note that the internal wifi antenna does not have much gain and is inside an aluminum box so the range is limited...

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