FDR Assigning Mystery IP Address

JSIA22 · ‎2023-01-24

Hello! I'm setting up FDR on a group of ATV340s. I'm running into an issue where two out of about 30 VFDs are getting assigned IP addresses that are not listed anywhere in my program/the FDR server list. For example:

I turn on DHCP for VFD named "ATV340VFD16" and am expecting the IP to be set to ***.***.4.16 but instead, once I've restarted the VFD, the IP is set to ***.***.249.248

I've checked and verified there's no duplicate device name on another VFD, there's no duplicate IP, and the name on the device matches exactly with the FDR server list. Has anyone experienced this before/have any idea why this is happening?

Robert_Willis · ‎2023-01-24

Have you updated the FDR Server in the CPU, NOE or NOC that is communicating to the drive? This has to be done after every change.

JSIA22 · ‎2023-01-25

The FDR server in the CPU shows the listing for that VFDs as named and addressed correctly. To be safe, I completely deleted the VFD from the program reinput them from scratch, readding them to the FDR server. This did not resolve the issue unfortunately.

What I find most confusing is that the IP addresses that are being assigned to these two VFDs aren't even close to address being used in the program/on the FDR server. I'm not sure where they are coming from.

Richard · ‎2023-01-25

Without the network architecture it is difficult to tell but have you checked the wider network for another DHCP server?

JSIA22 · ‎2023-01-25

The system is currently pretty isolated right now. The VFDs are connected to an unmanaged switch which runs to a NOC. The NOC connects to the CPU. From there, there's currently no communication with a wider network.

Robert_Willis · ‎2023-01-25

Is the backplane port of the BMENOC module turned on? Based on your description it is possible that the FDR Server in the CPU and the NOC are both active. Have you ever attempted to connect the drive to the CPU? Please provide some details on "The NOC Connects to the CPU". Are you indicating that it is connected via the backplane or through a cable connection between the NOC and CPU.

JSIA22 · ‎2023-01-25

Sorry, my network description was not quite accurate! The VFD is connected to the unmanaged switch. The switch connects to the NOC which communicates with a CRA via the backplane. It's the CRA that communicates with the CPU through a cable connection.

Robert_Willis · ‎2023-01-25

Now you have me thoroughly confused on how your system is connected. Can you provide a detailed drawing?

JSIA22 · ‎2023-01-25

I'm probably not explaining it correctly. I'm new to Scheinder tech and have only been on this particular project a few days, so I'm still figuring it out myself. I'm not authorized to post the drawing unfortunately, but I'll do my best to clarify!

The VFDs are all run to a remote I/O panel with a remote rack. There are multiple remote I/O panels, so the CRA modules between these remote I/O racks are connected in a ring network with the CPU in the main panel.

A VFD is connected to an unmanaged switch. The switch is connected to a BMENOS (I think I previously said NOC. Sorry!) module on the remote I/O rack. Through the backplane, the NOS communicates to a BMECRA module which is connected to the other remote I/O rack CRA modules and the main CPU in a ring network configuration.

I hope this makes more sense than my previous description. Appreciate all the help!

Robert_Willis · ‎2023-01-25

Based on your new description it appears that the M580 CPU is handling the communication to the various VFD's that are connected through a BMENOS0300 module that is located in the X80 remote I/O drop. Does the ATV340 have a local display connected to it? Have you updated the FDR server in the Modicon M580?

JSIA22 · ‎2023-01-25

Yes, that's the correct layout! The ATV340 does have a local display (ATV340U22N4E). The FDR server in the M580 has been updated. The identifier type is device name, which exactly matches with what is on the ATV340.

Teaan · ‎2023-01-25

I would suggest you setup the NOC card's service port as a mirroring port. Then use WireShark to see who answers the ATV340's DHCP request. This will give you place to start. If you don't see any requests coming through on the NOC that seems relevant do the same on the M580's service port. Finally if you don't see anything there, then if you have a managed switch available install it in place of the unmanaged switch and do the same test as close as possible to the drive.