Raspberry Pi 3 + AHMI + Automation Directs Click PLC

[jsathern]

I wrote a program on Automation Directs Click PLC and verified its functionality. Then I made a HMI using Advanced HMI's software. I am able to hook up to the plc via MODBUS TCP with my laptop and ethernet to use the HMI, but when I copy the .exe and appropriate folders to a thumb drive and try to run the application it is not able to communicate with the Click PLC via Ethernet. The errors on the buttons i ham getting are "Could not connect to 169.254.0.0, port 502. Timed out."

If anyone can help that would be great.

Thanks.

[Godra]

169.254.0.0 is locally assigned address. Is that a correct IP address?

See this:  https://packetlife.net/blog/2008/sep/24/169-254-0-0-addresses-explained/

[jsathern]

That is the default address to the Click. Like I said, everything is the same on the laptop compared to the Raspberry. I just try the program on the raspberry and it doesn't communicate. But I launch the same program on my laptop and it does work. Just to be clear i am directly connecting via ethernet (No router or switch between) both with the laptop and raspberry.

[Godra]

Are you running the program as a superuser (sudo)?

What is the IP address of the Pi ethernet?

[jsathern]

pi@raspberrypi:~ $ hostname -I
169.254.189.229 192.168.2.16

I try to run as sudo and its the same as running mono.

I can launch the .exe via mono or clicking on the application.

I attached a screen snip of the pi.

[Godra]

I don't have any other suggestion for you but to change the IP address of your Click PLC to 192.168.2 range.

[Godra]

This page shows a different default IP address for Click PLC:

https://www.automationdirect.com/microsites/clickplcs/click-help/Content/200.htm

[jsathern]

ill give that a try real quick.

[Godra]

Just to clarify "sudo" usage, take a look at the attached picture here which shows how I use it:

https://www.advancedhmi.com/forum/index.php?topic=2498.msg15124#msg15124

[jsathern]

Yes i used it that way and still same thing. This is a TCP connection correct? *New to modbus* so no need for the tty0tty correct?

[Godra]

Correct, tty0tty is for Modbus RTU.

[jsathern]

I been doing a lot of reading and I believe that it is due to the issue of running a .net framework on linux based software? Not positive but I would like to figure this out.

[Archie]

Can you ping the PLC IP Address from the Pi?

[jsathern]

no:

$ ping 169.254.0.0
Do you want to ping broadcast? Then -b. If not, check your local firewall rules.
pi@raspberrypi:~ $ ping 169.254.0.0 -b
WARNING: pinging broadcast address
PING 169.254.0.0 (169.254.0.0) 56(84) bytes of data.
^C
--- 169.254.0.0 ping statistics ---
60 packets transmitted, 0 received, 100% packet loss, time 387ms


You think that i'd have to use a crossover cable? I'm just using a direct connection from the pi to the CLICK with an ethernet cord. (Which works from the laptop but not from the PI)

[Godra]

I been doing a lot of reading and I believe that it is due to the issue of running a .net framework on linux based software? Not positive but I would like to figure this out.

Mono has its limitations but AHMI does run properly with the exception of maybe a few controls within its collection.

You should steer away from 169.254 range since it's barely ever used for anything and is kind of Windows thing.

Devices these days are capable of utilizing both straight-through and cross-over cables but it doesn't hurt to try either.