I have found that if you have an ethernet cable connected to the ML1100 and then you go to the "setup" screen it will show you the IP address, if you do not have the cable connected and you go to the "setup" screen it will not show the IP address.
I don't think this anomaly applies to the 1763-L16DWA model.
I guess did not hold down escape long enough. Man i feel like an idiot.
Don't. Those buttons are clunky. I often find I have to press them twice to navigate or hold them a bit longer the second time. Now you know!
In the mean time can anyone tell me what fault code 0187h is?
If I'm reading you right, you can now navigate the LCD menus and are displaying 0187h error code on the LCD screen, but have still not established comms to the controller?
The error does indeed relate to an I/O configuration mismatch, but you first need to get connected before you can sort that out.
With Ethernet plugged out of controller, cycle power and check your controllers current IP address and Subnet mask using Robo77 navigation guide. I'm not infront of a MicroLogix at the moment, but I'm sure there is ENET Status as well as ENET Cfg. This is quicker to view current ENET config as you don't have to navigate through all the flashing editable screens. Assuming your programming laptop/PC is still set as outlined in the BOOTP user manual, using 192.168.1.20 and Subnet 255.255.255.0, use ENET Cfg on LCD to edit the controller settings to 192.168.1.10/255.255.255.0 and cycle again. Check ENET Status again to verify the config held. Double check each octet of IP and Subnet are correct. Many a time I and others have put a 198. instead of 192. or similar.
With Ethernet plugged in between PC/PLC use CTRL+R, type cmd and OK. At the command prompt type:
ping 192.168.1.10
and see if the controller is on the network. If so then type exit. Proceed to RSLinx to check its visible there. Assuming again you have configured your Ethernet driver correctly, adding the controller to the drivers IP list. If it's visible in RSLinx go to RSLogix500 and browse to it and attempt an upload to pull in the application from the controller. Then you can start looking a the I/O configuration error.
My guess is this controller had expansion I/0 of at least 1 extra module in its last used configuration. You have powered it up without the expansion module(s) and its faulted. The communication problem is a seperate issue entirely to the flashing fault light. That's just my hunch going on info before me.
Let us know where your at?
G.