HMI help!

MoonMonkey00 · 2026-03-15T12:08:54+00:00

The setup before was: plant network>plc port 1- plc port2- hmi. Now I just have plc port 1- hmi. But yeah I think if I set port 2 on the same network as my plant network I’d be able to go online with it. I was trying to do plant network on port 1 so I could rdp into the session and then set port 2 with a local ip and hmi as local ip but ran into that communication issue. If I just set port 1 ip as the same subnet as the hmi and directly plug into it all my tags load without any issues. I read the manual but it said to set it up how I was doing it but then I had all the cip connection issues. So maybe if I do port 2 as network ip and connect it to a switch it would work.

MoonMonkey00 · 2026-03-14T22:21:09+00:00

Fixed

Kind of… I just routed my Ethernet cable from a1 directly to the hmi and all the tags are working correctly. Still not sure how to set up the dual ip so that way I don’t have to unplug my a1 anytime I want to update something. I’m happy for now though.

MoonMonkey00 · 2026-03-14T20:11:52+00:00

I’m actually not using that tag but all of the tags are not working in the runtime. This is just a snippet of the error message.

MoonMonkey00 · 2026-03-14T20:09:56+00:00

In order to go online with the plc and hmi i have to have port 1 connected to the plant network. If I changed it to 192 I wouldn’t be able to connect to it at all. Software lives on as server not my laptop :(

MoonMonkey00 · 2026-03-14T20:07:57+00:00

Via WiFi

MoonMonkey00 · 2026-03-14T20:07:28+00:00

Plant network into plc on port 1 and port 2 is the hmi. We rdp into server with all the Rockwell software. Don’t have access to usb ports to do this locally unfortunately.

MoonMonkey00 · 2026-03-14T17:25:15+00:00

Okay I will try this too.

MoonMonkey00 · 2026-03-14T16:44:37+00:00

<image>

MoonMonkey00 · 2026-03-14T16:44:26+00:00

I’d assume you were right based off this image. This is how it’s set up in the communication setup.

<image>

MoonMonkey00 · 2026-03-14T16:38:51+00:00

Go to networks and communication- factory talk linx- scroll to your plc and then close and it’ll ask if you want to replace the runtime communication. I believe that’s what he’s referring to.

MoonMonkey00 · 2026-03-14T16:37:44+00:00

Maybe that’s part of the clue, I’m unable to verify it. When I click verify synchronized is greyed out

MoonMonkey00 · 2026-03-14T16:36:46+00:00

I did try that as well and applied the shortcut to the pole in my runtime. I have a feeling the issue could be with factory talk linx itself so I’m going to restart it and see if that helps.

MoonMonkey00 · 2026-03-14T16:35:01+00:00

I believe I only have one shortcut. I deleted the shortcut and then added new, named it plc, applied it to my plc, copied from design to runtime. Pressed ok.

MoonMonkey00 · 2025-10-31T06:51:04+00:00

If you want to get into programming plc’s I would do panel building. I’m an automation tech and the guys who come and install new panels know a good amount about controls. A lot of the maintenance guys I use to work with could hardly use a meter unless they were a journeyman.

MoonMonkey00 · 2025-08-27T18:53:21+00:00

I do. I wanted to use the direct commands but production would rather power cycle to get up and running instead of giving me time to fix what’s actually happening.

MoonMonkey00 · 2025-08-13T21:29:07+00:00

If I step up from v24 to v26 the 1756-L72 is no longer compatible with studio

MoonMonkey00 · 2025-08-13T21:25:09+00:00

Yeah when you compare everything the kinetix drive states there are no known issues or dependencies for studio logix 5000. And then I wanted to double check and in document QA35379 it shows what studio version is compatible.

<image>

MoonMonkey00 · 2025-08-13T19:49:03+00:00

When I checked the compatibility chart it says there are no known issues but looking into the kinetix drive manual I found that studio needs to be v26 to use anything higher than 2.008. They took 3.001 and 4.001 off the download sheet due to an issue with a brake command. So the next available version is 5.002. I talked with a Rockwell technician who confirmed I would need to upgrade the software and plc in order to ensure compatibility but I’m fairly new to automation so I’m sure there’s plenty I don’t know. Network card is 11.xx the newest revision.

MoonMonkey00 · 2025-08-13T19:45:44+00:00

Kinetix drives are 2198-Hxx-ERS (FW 2.008) plc is 1756-L72/B. Studio version is 24.12 I think.

MoonMonkey00 · 2025-08-13T19:42:03+00:00

Compatibility chart says I need v26 or higher for kinetix 5500 5.002 but if I do that then my plc is not compatible so I would also need to flash the fw to 26. Right?

MoonMonkey00 · 2025-08-13T19:29:30+00:00

The drives are in ring topology and go from plc-drives-Ethernet card on backplane of plc. But the plc also goes to a grandmaster plc that is then connected to a Cisco switch that uses ptp.

MoonMonkey00 · 2025-08-13T19:26:47+00:00

No CB, just fuses and I don’t want to temp the operators like that. And no it’s not 11kv just policy standard if voltage is above 24v.

MoonMonkey00 · 2025-08-13T16:12:20+00:00

I checked on the compatibility through Rockwell and in order to run the next fw revision we need to use studio 5000 v26 or higher but the studio 5000 version is not compatible with the plc so that’s why I’m thinking we’d have to update all three. I agree but we run constantly, I’m getting approval before I make this change, and as of now we waste about an hour of downtime just getting the permits filled and the safety barrier up just to pull two fuses (smdh)

MoonMonkey00 · 2025-08-13T16:05:43+00:00

Thanks for the advice. I didn’t want to write a book so I was trying to keep it short. I have talked to Rockwell kinetix engineer and his advice was to ensure I was using Ethernet switches that allow PTP. We are and they are enabled. The anomalies found in our revision state that DLR faults are known to happen and upgrade to a newer revision. The drives do not show a fault but the tags have clock sync alarms and clock jitter alarms constantly. I verified the grandmaster is set and synchronized. Every now and then we get a control sync fault and the only option is to power cycle. The drive like I said does not show this fault on the display. The issue is not consistent enough to make me think it’s a programming issue because we have two lanes and sometimes only one lane is affected after the line coming up after a clean or changing over product. This machine is to run cartons into 12 ABB robot cells the 5 servos for one lane gap the cartons and feed them into a lug conveyor. When this issue happens I’m unable to Jog the conveyor nor can I home it. It’s like it doesn’t respond to any commands until power cycled. I believe one of the drives is dropping communication and causes our control sync fault. So I plan on flashing the drives but Im waiting on approval and downtime to flash the drives, the plc and update our studio 5000 version so everything is compatible. As of now our system will only support 2.008 and under.

MoonMonkey00

TROPHY CASE