Did my M1XEP just die?

[IVB]

I was doing tons of network rewiring, adding in a 2nd switch.  Didn't do anything with the M1XEP run except to trim off excess wire & put back into the patch panel.
 
ElkRP2 wouldn't connect. Tried tons of things, finally did the "short-JP2 to reset it back". Still can't "find" from within ElkRP M1XEP setup.
 
I moved it to a managed switch, I can tell its sending & receiving data, but ElkRP2 won't connect to it.
 
I then built a crossover cable and connected it directly to the PC. Nope, no love, still get "no M1XEP" found.
 
Normally I'd say screw it and just buy another one since this one is approaching 10 years old but its Saturday of a long weekend, so AO won't be open until Tuesday. And Amazon is both stupidly high prices *and* nobody will ship for a few days.  So I ask of you: Anything else you can think of for me to test, or do I just admit defeat and buy a new one?

 

[wkearney99]

Sounds like you accidentally let out the magic smoke.  On a holiday weekend.  Ouch.

 

[IVB]

Dang. Well, the upside of being on sabbatical is every day is the Saturday of a long weekend. I have *TONS* of house projects and cleanup to do before I start working again, so this'll be nothing more than a hassle.
 
Thx.

 

[vc1234]

Dang. Well, the upside of being on sabbatical is every day is the Saturday of a long weekend. I have *TONS* of house projects and cleanup to do before I start working again, so this'll be nothing more than a hassle.
 
Thx.

If you are curious enough, you could wireshark the XEP to see if it attempts to transmit something.  It may give you a hint if anything further can be done to fix it.

 

[IVB]

If you are curious enough, you could wireshark the XEP to see if it attempts to transmit something.  It may give you a hint if anything further can be done to fix it.

Actually I know it's transmitting, I've got a managed switch so I can see packets on that port.

I think I'll hunt down a real jumper and keep cycling it at some point today. I used a flat point screwdriver but maybe it needs something better. #HailMaryPass

 

[pete_c]

Wondering if you should change your IVB name to Glitch?
 
I am writing in jest cuz had a friend that worked for GM and specifically on the corvette and in his basement 99% of the time. 
 
He would go to HQ maybe once a month relating to his projects.  He did have terminals all over his house (not PCs) always connected to GM.
 
IE: he did electronics but had a wind tunnel set up in his basement.  He lived in Rochester, Michigan.  He could machine a little electric box in just a few minutes with his wizard tools.  Shared interest at the time was touchscreens and firmware stuff and cryptology and linux hacker dot org.  He was a wizard at this kind of stuff.
 
Some time in the 90's he got the nickname glitch.  I never asked him though about it but really did know.

 

[RAL]

Actually I know it's transmitting, I've got a managed switch so I can see packets on that port.

I think I'll hunt down a real jumper and keep cycling it at some point today. I used a flat point screwdriver but maybe it needs something better. #HailMaryPass

 
When you power the XEP on with the jumper, watch the LEDs on the RJ45 jack carefully to see if they flash as described at the bottom of page 25 of the manual.  That's a pretty good indication that the XEP is still alive, at least to some extent.
 
I'm wondering if maybe you have a connection problem between the XEP and the serial port of the M1.

 

[mikefamig]

When you power the XEP on with the jumper, watch the LEDs on the RJ45 jack carefully to see if they flash as described at the bottom of page 25 of the manual.  That's a pretty good indication that the XEP is still alive, at least to some extent.
 
I'm wondering if maybe you have a connection problem between the XEP and the serial port of the M1.

 
 
What DEL said......is it Windows 10? If yes then I would upgrade to the newest version of RP2 before doing anything else.
 
Mike.

 

[IVB]

Wondering if you should change your IVB name to Glitch?
 
I am writing in jest cuz had a friend that worked <snipped> in his basement 99% of the time. 

 
Heh, i'm in my basement cleaning up this mess right now. Spare parts shelf turned into spare parts room turned into spare parts floor.  Call me crazy, but I think i'm going to ditch the 3 SVideo cables I still have. And I'm capping it at 237 USB cables and 48 RCA cables. Everything else must go!
 

When you power the XEP on with the jumper, watch the LEDs on the RJ45 jack carefully to see if they flash as described at the bottom of page 25 of the manual.  That's a pretty good indication that the XEP is still alive, at least to some extent.
 
I'm wondering if maybe you have a connection problem between the XEP and the serial port of the M1.

 
Well thats terrifying,this board is 4 months old, just swapped old one out. The closest PC is 9 feet away (just measured), I just found all my serial cables, assuming they still work I wonder if I can string 2 6 foot RS232 cables together and try a direct serial connection. Don't see why 2 serial connected wouldn't work...

 

[IVB]

What DEL said......is it Windows 10? If yes then I would upgrade to the newest version of RP2 before doing anything else.
 
Mike.

Hmm, I have a W7 machine with ElkRP on it, i'll try that first. Thanks!

 

[Sparkman1]

Don't see why 2 serial connected wouldn't work...

 
If the cables roll the TX and RX, then two cables won't work.  You may need one regular and one straight through.  3 regular ones may work too.
 
Cheers
Al

 

[BraveSirRobbin]

FYI, just in case you wind up ordering another one, latest vendor thread from AO:
 

During the Labor Day weekend only, take advantage of our online special offers!

10% Off all Elk Products

Use Code LABORDAY16 at check out!

 

[IVB]

thx BSR, i got that too. 
 
Looks like I need to hunt down serial pinouts, i have 3 cables but not sure whats straight through vs null vs whatever. Its not working, elkRP says "cannot detect comm settings". Ugh.

 

[vc1234]

thx BSR, i got that too. 
 
Looks like I need to hunt down serial pinouts, i have 3 cables but not sure whats straight through vs null vs whatever. Its not working, elkRP says "cannot detect comm settings". Ugh.

Well, you can check the cable with a multi-meter.  It should be a straight cable, and I believe Elk's serial port uses only pins 2,3 and 5 with a 115,200 baud rate.
 
I used a serial-to-USB FTDI cable with no issues as well.

 

[pete_c]

Everything else must go!
 
Been doing similiar here (WAF thing).
 
Glitch mastered the GM serial bus and actually modernized it becoming a serial com in firmware wizard.
 
A glitch is a short-lived fault in a system. It is often used to describe a transient fault that corrects itself, and is therefore difficult to troubleshoot. The term is particularly common in the computing and electronics industries, and in circuit bending, as well as among players of video games, although it is applied to all types of systems including human organizations and nature.