Messages

1

Tips & Tricks / Re: AdvancedHMI on a Raspberry Pi

« on: December 02, 2019, 08:28:11 PM »

I'm new sorry.  did not know about the addressing

2

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 30, 2019, 01:06:24 PM »

Good to see everyone is friendly 

3

Tips & Tricks / Re: AdvancedHMI on a Raspberry Pi

« on: November 28, 2019, 03:31:44 PM »

Here is how to run an AdvancedHMI application on a Raspberry Pi

1) Download the Debian Wheezy image
http://www.raspberrypi.org/downloads/

2) Copy the image to the MicroSD card using Win32DiskImager
3) Install the card and boot up the Pi
4) When it gets to the configuration screen, set it to expand the image and also to boot to a Graphical User Interface
5) Select Finish in the configuration and Reboot
6) Once booted into the GUI, open a Command Prompt
7) Type these series of commands:

sudo su
apt-get update
apt-get install mono-complete
apt-get install mono-vbnc

8 ) Put in a memory stick with an AdvancedHMI application on it
9) In the command prompt, use the "cd" command to browse to the memory stick to the directory /bin/debug
10) mono AdvancedHMI.exe

In a few seconds the application should start.

There are a few things you may run into.

- You cannot use an OPC server because it is not a .NET application
- The MessageDisplayByValue may stop the application because it uses a speech library. There is a work around. Find System.Speech.DLL on your Windows PC and copy the file into the /bin/debug directory

Archie, you should add in here just for the new people like myself the following: You have to set up raspberry pi for a static ip address:

sudo nano /etc/dhcpcd.conf.
Type in the following lines on the top of the file: interface eth0 static ip_address=192.168.1.XX/24 static routers=192.168.1.1 static domain_name_servers=192.168.1.1.
sudo reboot.

Then Make sure the PLC and the Pi have the same (subnet?) first two numbers on the ip..............

I came across this writeup first and thought i would be set. I was wrong and it took me quite a while to figure this out. It would just be super helpful to have all the info in one place to get the pi and AHMI communicating.

Just a thought. thanks

4

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 23, 2019, 11:16:10 PM »

Ok so the key is setting up the pi for a static ip address. JESUS I FIGURED IT OUT FINALLY!!! Thanks for your guys help

5

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 23, 2019, 06:35:09 PM »

I will try that when I get home today. Working right now

6

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 23, 2019, 10:51:39 AM »

I keep trying to get this to communicate and I cannot. Is there a missing step in the wright ups that is just assumed the everyone knows and I do not?

7

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 15, 2019, 12:22:55 PM »

are you talking of setting the raspberry up for a static ip?

8

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 06, 2019, 11:36:48 AM »

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)

9

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 05, 2019, 02:52:08 PM »

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.

10

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 04, 2019, 04:56:58 PM »

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?

11

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 04, 2019, 04:25:35 PM »

ill give that a try real quick.

12

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 04, 2019, 03:13:54 PM »

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.

13

Open Discussion / Re: Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 04, 2019, 11:30:27 AM »

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.

14

Open Discussion / Raspberry Pi 3 + AHMI + Automation Directs Click PLC

« on: November 01, 2019, 02:16:53 PM »

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.