Click PLC Connection Into Ignition

Ignition
1

Does anyone have much experience with setting up a Click PLC to communicate with Ignition? I have setup the port1 connection to my desired address and believe i setup the modbus tcp section for port 1 properly as well(port 502). But i am unable to connect to my PLC. It cycles between connecting and disconnected. Apologies ahead of time as this is my first time working with these PLC's

2

Check your gateway logs for any errors.

Are you able to ping your PLC from the server that Ignition is installed on? Have you confirmed that your server is on the same subnet as the PLC? Or that your IT department has routing rules in place to allow your gateway to talk to the subnet that the PLC is on?

3

Sorry just to clarify. I'm currently running a test gateway of ignition on my computer to prove out some things. But yes i am able to ping the PLC from my computer. But ignition is failing to connect.

4

Check your Ignition gateway logs. Your laptop firewall might be blocking the Modbus comms specifically.

Also, have you configured any tags for the device in Ignition yet? I think that these PLCs will kill the connection quickly if its not actively requesting any register data. I know the BRX series does this.

Try defining a single tag to look at holding register 0 or something like that

5

Funny, I just connected to a Click Plus PLC literally 5 minutes ago for the first time. It connected just fine for me. I went to configure com port and did the typical IP address stuff.

Did you make sure to save your changes to the PLC? Can you ping the device?

6

.

1 Like
7

I believe i did everything correctly on my end within the PLC. Setup > Com port 1 setup > Entered the desired IP addresses and what not. Downloaded and saved. And yes when plugging into the desired port i am able to ping the PLC from my device. But i'm getting nothing within ignition. I also attempted to setup a few addresses to the best of my knowledge using the modbus addresses within the address picker. But i'm still getting no luck.

8

Check your ignition logs. Are there any errors present? There should be something at least saying its attempting to the Click.

9

Sounds like a firewall issue then

1 Like
10

Are you referring to the logs related to this specific device? If i go to device view for the click plc and set my log activity min level to TRACE i do see an "Error during connect"

11

Click PLC
Click PLC1494×654 112 KB

This is what i see under that.

12

Connection Refused - Firewall issue.
You'll need to add a rule to your laptop firewall to allow traffic on port 502

1 Like
13

I will give that a go and see where it gets me!

14

I setup a rule to allow port 502 within my firewall settings. Still no luck on the connection.

15

Did you make it for TCP or UDP? Should be TCP port 502 inbound and outbound.

16

Yes, i made both inbound and outbound rules for TCP port 502.

17

Are you straight wired from PC -> PLC? Like just a patch cable connecting the two? If so, it probably considers the connection a public connection. Make sure public network is allowed in the firewall rule.

Also, if this is a windows computer you might need a restart after the rule setup.

1 Like
18

Just for addition to this topic, AD just released this little nugget:

https://www.automationdirect.com/adc/shopping/catalog/programmable_controllers/click_plus_plcs_(stackable_micro_modular)/cpu_option_slot_modules/c2-opcua?srsltid=AfmBOoqGlVzBGcdwgNQXrSKsyq_eS0yDJDgcDi5-NpJr5RhtZzM7t-92

1 Like
19

I should add to this. I am not using the Click Plus PLC, i am using the standard Click PLC

1 Like
20

Unfortunately, I can't add much to the troubleshooting side of this, but I do have two of these that I added to a couple of... I'll just call them 'legacy'... assembly lines. I didn't have to do anything special on either end to get them to work, IIRC.

Let me connect up to one of them and look at the config for you, as much as a refresher for me, as a sanity check for you. :slight_smile:

1 Like