4/5/2024 4:05 PM | |
Joined: 9/7/2023 Last visit: 5/30/2024 Posts: 24 Rating: (0) |
Good morning everyone, I have a profinet network that intermittently reports "Module configured, but not available" on some devices. I'm looking for help on what could cause this. Step7 V 5.7 Flowmeters - Endress + Hauser Promass 300. CPU - 319-3 PN/DP CP 343-1 - This network has ~25 devices, 14 of them are this same model of flowmeter. All the flowmeters use the same GSD file. Their update times are all Fixed Factor, 8ms with a 24ms watchdog time. And their data is structured the same, and used the same in the PLC. A few weeks ago I started noticing in the Online Hardware Config that one of them had the red line through it and reported "Module configured, but not available". Then a second one the next day. I don't monitor their connection status, so it's possible it has been going on for a long time. So I have two devices that are now almost always "not communicating". The profinet cables check out fine and I can ping the devices when I disconnect the cable and ping straight through the cable to the device. But once I connect the profinet cable to the Siemens Scalance network switch, there is latency in the ping and I usually drop 2 out of the 4 pings. Last week I was concerned that the Scalance switches were the problem, so I created a Profinet network on the native CPU's port and moved the two bad devices and one good one to it. That seemed to fix the comms for 1 device, but only for a number of minutes. Coming back to it later I found the device "...Configured, but not available" again. I've also replaced connectors on the profinet cables which seemed to fix one of them, but then I came back to it and found it with the same problem. The profinet names are unique, the IP addresses are unique, and the cables and connectors are good. What kind of issues could make the PLC think that a device is "configured but not available" when, in reality it is present. If I had bad logic, or was accessing the wrong addresses could it cause this? Are there other ways to diagnose the profinet connection with different software, or with all the logic bypassed? Attached is an image of when Node (2) happened to show a good connection for 30 minutes. It has 44,000 bad packets received. Is that informative? Thanks for any tips you can think of. AttachmentScreenshots.zip (71 Downloads) |
Last edited by: Jen_Moderator at: 04/08/2024 08:32:10All files added as .zip file. |
|
Follow us on