Failed J2534 connection attempt when trying to use FDRS-post-9 Fixed

[Lightning-E]

Trying to do updates via FDRS and my mongoose cable and I'm receiving a "Failed J2534 connection attempt" error. I have the mongoose cable and I've done this numerous times on my Mach-E. This is the first time trying on my Lightning. I had to install the new version of FDRS 45.6.8 so I could use the new $120 license. My Forscan has no issue connecting. Anyone else run into this? Am I missing something?

Sponsored

 

[B177y]

I would start with downloading the Mongoose driver and installing it again to see if that does anything.

Anti virus and other "protections" turned off?

Reboot?

See if it communicates with the Mach-e?

Start with the easy stuff.

 

[Lightning-E]

I've done all of that. Unfortunately, can't test the Mach-E, traded it in on the Lightning. My next thought was, well let's try a different PC. Next issue: can't release the license.

I guess the main thing is to make sure that it's isolated to me and not FDRS 45.6.8 and the Mongoose Plus Ford2 cable combination. I'll tell ya, this is annoying as hell. Not only did I have to spend twice what I used to but now I can't even get the thing to work, nor can I transfer it to a different PC to test the hardware. AND I've been on hold for 30 mins trying to contact support to help get the license released. Nailing it, Ford.

 

[B177y]

I used my Mongoose with 45.6.8 a couple of weeks ago without issues, so I can say it's not a new FDRS version thing.

Your error window says "wireless dongle status", which seems weird since it USB. Maybe play around with that. Check that the cable is connected well and screwed in tight on the Mongoose side, different USB port, etc.

That's l I can think of

 

[Lightning-E]

Thanks. Now if only I knew how to release the license from FDRS. This is so irritating.

 

[Lightning-E]

I used my Mongoose with 45.6.8 a couple of weeks ago without issues, so I can say it's not a new FDRS version thing.

Your error window says "wireless dongle status", which seems weird since it USB. Maybe play around with that. Check that the cable is connected well and screwed in tight on the Mongoose side, different USB port, etc.

That's l I can think of

I think the wireless dongle is because I had connected my OBDLink MX+ to that laptop at one point for Forscan. Of course, I don't see it listed anywhere as a wireless device, nor can I find how to remove it from the FDRS config. I think that is what's causing it, though. Just got FDRS installed on another laptop and I see the Computer Wireless Dongle Status as well. This has never touched any devices. I'm at loss.

 

[Adventureboy]

Does your Mongoose have firmware update capability? I use a Topdon JLink J2534, and a firmware update was needed to connect to the Lightning.

 

[rugedraw]

The only time I have even seen that message is if I try to connect to a vehicle without being plugged into it. If you haven't already, check to make sure the USB cable that plugs into the dongle is seated properly. I have never heard of a case where a Mongoose goes bad, but I guess it's also a possibility.

When you connected to the FORScan, did you connect using the Mongoose or the cheap FORScan cable?

 

[Lightning-E]

The only time I have even seen that message is if I try to connect to a vehicle without being plugged into it. If you haven't already, check to make sure the USB cable that plugs into the dongle is seated properly. I have never heard of a case where a Mongoose goes bad, but I guess it's also a possibility.

When you connected to the FORScan, did you connect using the Mongoose or the cheap FORScan cable?

Turns out it was a blown fuse for the data link (OBDII) port. I'm using the Mongoose cable. Replaced the fuse and was off to the races.

 

[bmwhitetx]

Turns out it was a blown fuse for the data link (OBDII) port. I'm using the Mongoose cable. Replaced the fuse and was off to the races.

You’re the second person this week. Actually the second person this year.
https://www.f150lightningforum.com/...m-the-odbii-port-post-4-fix.31863/post-585183

Sponsored