Search results

The MX adaptor is all I use. Have had no issues at all. The EX I believe is a usb wired version tested thoroughly with Forscan.

Honestly didn’t notice anything out of the ordinary with mine. It was just the adaptor, cable and small card in my Mongoose box. Lots of room for it to move around in the box though so I could see how some of them may appear used (scuffed) just from shipping/handling. Most important thing is it...

Correct, I believe it was U2400 - failure to communicate to GWM A over Ethernet or something like that.

Ok got it. This DTC is persistent however. You can clear it and it won’t come back until you drive around. Assuming that like you mentioned we are still waiting on the GWM update to fix the IPC DTC and enable BC from the mothership.

@Livnitup and team, looking at the software version and strategy for the GWM what do you think of the possibility that the IPMA DTC U2400 is just related to a GWM configuration issue? I only ask because the my current GWM version and strategy is newer than a job2 truck with BC enabled from...

Hard to say If that date actually means anything at this point. BC is not listed yet in my connected services on the Ford website like connected navigation is so it may just be an arbitrary date at this point until the GWM update is rolled out and activated.

I do see it pop up and say BC is available when driving but I agree @Bob_Mac that the gateway update is likely still missing. What I’m unsure about is if it is going to be a software update or just a configuration update for the GWM?

Sorry yes, the IPC was a mistake and would be valid for a 5.0 not the 3.5 powerboost.

No OTA, all updates via FDRS and I still have the IPMA DTC for Ethernet to gateway failure. I did although make changes to the APIM, IPMA and IPC to match a job 2 truck. I posted those changes in an earlier post. These are all the changes I made to match the job2 truck with BC from factory...

I guess I haven’t officially “Got it” yet so probably as expected.

Anyone who has updated their modules to the latest versions in FDRS also notice this hands free driving license in the about menu in their Sync? Is everyone’s showing the same?

I echo this as well but for anyone in the Calgary, Alberta area.

Does anyone have any information on the GWM as built data? It is one module not in the Forscan spread sheet and I'm wondering if we actually need a GWM update. Looking at my donor truck it looks as though the latest GWM calibration is more current then the donors truck. I'm wondering if it is...

I keep checking and sometimes see GSM and get excited until I realize I’m looking for GWM…. ?

Interesting document from the Opus (Mongoose) website. I'm not sure if this is %100 accurate or not but this document recommends not having IDS and FDRS installed on the same machine. I currently have both installed on a single laptop and don't have any problems that I notice, can anyone confirm...

Nice! Nope haven’t used that one before. Adding it to my tool bag. Thanks!

No GWM update as of yet. Just checked.

For anyone interested below is the procedure I used to verify my setup for proper cameras in motion and BC. 1 - I found a donor 2021 Job2 truck on a dealers lot exactly the same as mine with BC on the window sticker (Minus mine is a powerboost and the donor one was a 5.0) and compared IPC, APIM...

Might just be me but is anyone else who isn’t using a nano seeing a delay in their AB data updating after doing a network scan? I’m seeing delays from minutes to hours and not all AB data is being updated. For example; I made a change in my APIM with Forscan then ran FDRS and let it do its...

If it helps any here is my first 2 lines on the IPMA which is different than what you had. For reference I cleared all my codes went out for a drive, did not use cruse control and the only DTC I had come back was U2400 i believe. See the snapshots.