No MAC address (relation) from BOOT P

Hi, folks. I ran into a situation that has never happened to me.
I work in a Big 3 assembly plant and have been tasked with setting up a robot cell with 5 robots and a cool training program. I'm using Studio 5K V. 28, FTV V. 10.00. The hardware is a 17-slot chassis with a safety processor (an L76S I think), an L7SP safety partner, two EN2T ethernet modules and a standard output module. One EN2T will go to a Hirschmann Switch and all over from there on Point I/O.
I have a copy of the program and some prints, so I'm trying to set an IP address in one of the EN2T's. This is new hardware. I set the rotary switches and returned the module to it's "out of box" state, set them back to "999" and it shows BOOT P enabled scrolling across the display along with the MAC address. I set the static IP on my computer and the network settings in BOOTP. I'm wanting 10.138.12.XX. I spent all day trying to figure out why BOOT P won't show the MAC address for this module as a relation. Changed cables, tried everything I know. I tried USB direct into the module and BOOTP didn't want that, and I do see it in Linx as an unrecognized device in the ethernet tree. I decided it was my laptop, and as a last resort I set the switches to 123, thus making the IP address 192.168.1.123 as per the manual. Then I could see that IP address scrolling across the display and ping the module. Long post, sorry.
Why won't BOOTP show a MAC address from this module when the module is in BOOTP enabled mode? Thanks for any help. I'm having to use VPN and a hotspot over in that training center, and it won't let me on this forum. If I don't respond right away, that's why.

Are you plugged directly into the module, without a switch, you should also use a cross-over cable?

You can also try disabling your firewall.

Maxkling said:

Are you plugged directly into the module, without a switch, you should also use a cross-over cable?

You can also try disabling your firewall.

Click to expand...

Hi and thanks for a timely response. I have used these cables I have for years and never had a problem. I'll double check some of them, but I don't believe that's the problem.
IT (such as it is) did mention as you did about firewall issues, however I cannot disable my firewall as I don't have admin privilidges.

This project reminds me of trying to hang sheetrock, as an example, with 2" finish brads, no tape measure and a hammer that the head comes off about every third swing. Thanks again and I'll figure out something.

I am reading that you tried BOOTP via USB, this does not work. Instead expand USB driver in RSLinx and find module there. This will allow you to set IP address directly from RSLinx

Hey guys, thanks for all your responses. I've decided not to fight this, I'm sure it's my firewall settings which I cannot access and asking them is like asking a squirrel to quit eating nuts.
I've just set the I/P with the dials. This is a stand-alone network anyway, with no plant ethernet and no FIS link. Just a training cell. Thanks again and have a great fall. :site:

So in reading your post, your computer firewall was the first thing that came to mind. It is also possible that the network switch is blocking broadcast traffic. The Bootp message sent by the device is a broadcast message. And, like many large companies, getting your company to change a setting like that might be close to impossible.

Couple other items....

• The EN2T has auto-detect capability for straight through and cross-over connections (as do almost all new computers in the last 8 or so years) so a cross-over cable is not necessary.
  
• Connecting directly with your USB cable means you don't need BootP. The computer should detect the EN2T as new hardware just like a mouse or a printer. If you have installed RSLinx on that PC then it should have the drivers Windows would need to recognize this hardware. Then open RSLinx and you should see a USB driver has been created automatically. It is called ABVBP-1 by default. Clicking on that driver should show the EN2T. Right-click on it and select Module Configuration. You can go ahead and set the IP address from there.
  
• I love the option of using the switches to set the address. But being locked in to 192.168.1.xx sometimes is a no go.
  
• If your computer cannot identify the EN2T (shows a yellow question mark) then your computer doesn't have the EDS file needed to identify it. You might be able to right-click on the item and see an option to download the EDS. If not, you'll have to go to the AB site to download it.
  
• While I don't usually suggest upgrading software without a good reason, I always keep RSLinx up to date. It's free, and it includes all the latest drivers and EDS files.

OG

I have been using BootP for years and no matter what I set in the firewall and anti virus software it will never work right. I always end up turning off the firewall and the anti virus, then it works great.

Just in case ...

BOOTP will work reliably only when the NIC you are using to connect to the PLC is the only active network adapter on your PC host. Temporarily disable your Wifi, your Bluetooth, and whatever other network adapters you have, even if they are not connected to anything. Also disable the network adapter for your virtual machine software if you have that installed.

If I ever have any problems with BootP, I set the address on the thumbwheels to 192.168.1.xxx.

I then set my laptop on the same IP range, access the web browser for the hardware, and then change the IP address to what I want.

Cheers

Mark

The only thing I use for setting IP addresses in the plant is the IP Explorer.
It always works, and beats the hell out of dragging a laptop from device to device when I'm installing a line.

MarkNightingale said:

If I ever have any problems with BootP, I set the address on the thumbwheels to 192.168.1.xxx.

I then set my laptop on the same IP range, access the web browser for the hardware, and then change the IP address to what I want.

Cheers

Mark

Click to expand...

Thank, Mark. I'll try that.

KirkC said:

Just in case ...

BOOTP will work reliably only when the NIC you are using to connect to the PLC is the only active network adapter on your PC host. Temporarily disable your Wifi, your Bluetooth, and whatever other network adapters you have, even if they are not connected to anything. Also disable the network adapter for your virtual machine software if you have that installed.

Click to expand...

Kirk, hi. I've ran into this also at another plant we have, only then I was working for an integrator and had all admin privileges on my laptop. Another engineer clued me into this. I have everything disabled and thanks for the reply.

rdrast said:

The only thing I use for setting IP addresses in the plant is the IP Explorer.
It always works, and beats the hell out of dragging a laptop from device to device when I'm installing a line.

Click to expand...

Hi, I haven't heard of IP Explorer, so I will look into this. It may be in our in-house software store. Thank you.

JaxGTO said:

I have been using BootP for years and no matter what I set in the firewall and anti virus software it will never work right. I always end up turning off the firewall and the anti virus, then it works great.

Click to expand...

Yes, I'm pretty sure this is the problem, however asking IT to loosen up the firewall is like asking someone if you can take their girlfriend out to dinner and a...
Thanks, I'll keep hammering on them; I have a few favors I can call in.

Operaghost said:

So in reading your post, your computer firewall was the first thing that came to mind. It is also possible that the network switch is blocking broadcast traffic. The Bootp message sent by the device is a broadcast message. And, like many large companies, getting your company to change a setting like that might be close to impossible.

Couple other items....

• The EN2T has auto-detect capability for straight through and cross-over connections (as do almost all new computers in the last 8 or so years) so a cross-over cable is not necessary.
  
• Connecting directly with your USB cable means you don't need BootP. The computer should detect the EN2T as new hardware just like a mouse or a printer. If you have installed RSLinx on that PC then it should have the drivers Windows would need to recognize this hardware. Then open RSLinx and you should see a USB driver has been created automatically. It is called ABVBP-1 by default. Clicking on that driver should show the EN2T. Right-click on it and select Module Configuration. You can go ahead and set the IP address from there.
  
• I love the option of using the switches to set the address. But being locked in to 192.168.1.xx sometimes is a no go.
  
• If your computer cannot identify the EN2T (shows a yellow question mark) then your computer doesn't have the EDS file needed to identify it. You might be able to right-click on the item and see an option to download the EDS. If not, you'll have to go to the AB site to download it.
  
• While I don't usually suggest upgrading software without a good reason, I always keep RSLinx up to date. It's free, and it includes all the latest drivers and EDS files.

OG

Click to expand...

Hi, and thanks for your reply.
I'm not going through a switch at the moment, so that's not it. I feel good about the cables as you've mentioned.
I get the USB driver that you mentioned however the module shows as an unrecognized device. I believe as I replied to someone below, that I will have to get EDS files from Rockwell, along with upgrading Linx as you pointed out. I have V. 32.01 now and this is what I ended up loading in this project, as the L73S only offered that version of firmware. So maybe Linx is already up to date, I'll see.
Since this is a stand-alone system, no plant connection, no FIS, no nothing, I could easily use the rotary switches. I may just use all this knowledge from you guys to configure a new EN2T in the main plant. We're undergoing a re-tool, and I'll have plenty of opportunities. Thank you.