M1XEP problem

One last try. Connect the M1XEP directly to the PC using the crossover cable. Cycle power on the M1XEP. Wait 10 minutes. Then follow wuench's suggestion in Post #13. Some versions of Windows use the term "alternate" instead of "secondary".

Okay, still no go. I will send this off to ELK and see what they say. When I plug into my computer using the crossover, my computer takes a really long time to access the network card, and when it finally does it tells me there is a problem with the card. Also the lights don't flash on the computer nor the XEP.

It may not be broken, but if this thing is this unreliable, I want some other way to communicate.

Thanks for all your help guys, and I'll keep you posted.
 
I think the biggest sign is that it isn't lighting up the port on your switch... if not, definitely check other cables first. If you never even get a light on the switch, that's a concern.

Other than that - I'll say that on my XEP, I had a lot of problems accessing it at first - I had DHCP on but it wouldn't get an IP and the Find never worked when I tried to manually connect via a PC - I'm an extremely experienced network engineer so I know the things to try - and it still took a lot of work to get it to work the way it was supposed to. But once I got the stinkin' thing to take an IP address, it's been extremely reliable since for close to 5 years now.
 
I think the biggest sign is that it isn't lighting up the port on your switch... if not, definitely check other cables first. If you never even get a light on the switch, that's a concern.

Other than that - I'll say that on my XEP, I had a lot of problems accessing it at first - I had DHCP on but it wouldn't get an IP and the Find never worked when I tried to manually connect via a PC - I'm an extremely experienced network engineer so I know the things to try - and it still took a lot of work to get it to work the way it was supposed to. But once I got the stinkin' thing to take an IP address, it's been extremely reliable since for close to 5 years now.

Yeah I've done multiple cables and everything else suggested here. The light was the thing that finally convinced me it was in fact, not working properly. I just wish I had paid attention to that first. :)

I do have one more question though; when it's connected to the M1G through the serial port, shouldn't I see the board in the tree?

Clay
 
Got a call from ELK. It had a bad Digi module. They repaired it and it's on it's way back! Should see it Monday.

Cool!

Clay

PS received it, plugged it in, scanned. No problems. Worked like a charm.
 
Hi, sorry for piggybacking off of this post but this was the most-relevant troubleshooting I could find related to the issues I'm having. Finally got an M1 set up and had the xep working fine. I'm fuzzy on the timeline but I feel like it crapped out on me a little while after I tried updating firmwares and such.

Now it no longer pops up in the network dhcp list or the RP software. I've tried the page-25 dhcp forcing trick but either I'm doing it wrong or it never follows the pattern that's mentioned. I put in the jumper, turn it on, watch for light activity, but all that really happens is the orange light comes on for a second, then a while later the green light flashes, maybe the orange flashes back, and then there's no pattern at all.. sometimes green, sometimes orange, but never solid, and also extremely rare flashes of light from the port it's connected to on the switch. I've tried power cycling and testing again, but nothing over the past couple of days.

Bought a crossover cable and tried hooking up directly, but I'm not sure if I'm doing that right either. I've tried putting in 192.168.0.10 or 11 say as alternate ip (but do I need to put in a fake gateway too, like 192.168.0.1?), and i've also even tried just making that the main ip.. both times they fail at pinging anything on 251.

So, I've come to a point where I'm just lost now. Anyone have any advice? Is it normal for the rj45 lights to just rarely flash orange or green now and then? Should the orange be solid? Have I made any mistakes in the steps I took?
 
No you shouldn't need a gateway, gateways are for communicating outside the network, you are trying to talk on the same network. You could try to download AdvancedIPScanner and scan the subnet and see if you can find the address it is using.
 
Thanks for the tip.. downloaded and tried it out several times on my current range as well as 192.168.0.x but unfortunately it didn't find it.
 
Back
Top