LoganB said:
...I thought that the PLC wouldn't appear in linx until after BootP was disabled...
Hi LoganB,
All BOOTP is doing in the client device, when it does not yet have an IP address, is sending UDP packet requests looking for a BOOTP Server to assign an IP address to the device. BOOTP Server software, if working properly, will automatically detect the device MAC address. Once an IP address has been assigned, and BOOTP is still enabled, it is doing nothing, again, because an IP address has now been assigned. It does not continue sending requests. You should only see the IP address assigned against the device MAC address in BOOTP Server software. Only when the device is power cycled will BOOTP, being still enabled, then clear the IP address from internal memory and start sending UDP request packets again.
In other words, leaving it enabled will have no effect on the device's ability to start using its newly assigned IP address. After the IP address is assigned, you can immediately go to RSLinx Classic and start an Ethernet driver and browse to the device, if it is connected correctly.
EDIT: Bobogrammer has also alluded to this fact since I started typing.
I'm heading home now for the evening so I don't have time to get into the bones of this thread, unfortunately, but do a search here for my name & BOOTP or I think member ASF & myself & BOOTP? I recall one thread where we both outlined many causes of BOOTP Server not playing nicely.
I have other things you can check to do with the USBCIP driver issue but I'll post again later on that, if I have time.
Regards,
George