Search results

You have a few!

Just wanted to shoutout @speedracercjr. He let me borrow his Mongoose and it fixed all of the corrupt Nano data i had. Its nice to be able to do a network scan with the truck connected! Sometimes jumping the gun isnt a good thing and i wish i knew about the Mongoose before i bought the...

https://www.motorcraftservice.com/AsBuilt

So the below are what seem to unlock BC? Those that have enabled BC recently, can you post your strategy/calibration? Also, Any idea on asbuilt data changes? IPC CCM IPMA PSCM GWM APIM

Are these the modules that get an update to allow Bluecruise? trying to dig through this and see what exactly needs updated for BC. thanks.

So i've had Fordpass integration (itchannel) on my Home Assistant for about a year and a half. I Made a pretty cool Card awhile back for my HA dashboard and made sensors etc. Low and behold i started looking more into the Github and of course @tonesto7 has even been killing it over there too!

@BHunted1 That data is sensor config DPAC Homography. I would assume it changes based on a setting or configuration.

Msg->ucData: 00 00 06 f8 62 f1 13 4d 4c 33 54 2d 31 34 44 30 36 38 2d 45 48 00 00 00 00 00 00 00 00 00 00 Removing the above in red makes the HEX = as shown below. Not sure what these extra values are. 4d 4c 33 54 2d 31 34 44 30 36 38 2d 45 48 00 00 00 00 00 00 00 00 00 00 = ML3T-14D068-EH

Just flipping through. For example. This transfer contains 34 messages. [19:48:29.115] PassThruReadMsgs. [19:48:29.115] ulChannelID = 1 [19:48:29.115] pstructJ2534Msg = 0x43e6c7a8 [19:48:29.115] *pulNumMsgs = 100 [19:48:29.115] ulTimeout = 50 [19:48:29.115] ulTimeoutReal = 50 [19:48:29.176] RX...

Anyone using this app have onboard scales and smart hitch? If so, Does it show any info for either? TIA.

Definitley not a coder! lol Buy yes, Coders scare me too!

Yeah, Looking at the ASCII and hex, that one space throws it all off by placing a 20 in the HEX. CORRUPT ASCII = ML3 T-14H099-AF HEX = 4D 4C 33 20 54 2D 31 34 48 30 39 39 2D 41 46 CORRECT ASCII = ML3T-14H099-AF HEX = 4D 4C 33 54 2D 31 34 48 30 39 39 2D 41 46

No worries. I have a raptor so apparently they are worthless anyway.

I have the BCM_C but not the DCACA. The SODCMC and SODCMD are the front side Obstacle Detection modules. Weird that the 2 you show now are on HS-CAN1 as the ones i have issue seeing are FD-CAN

Probably the SODCMC and SODCMD that i mentioned earlier. Forscan and my OBDMX see it but not the VXDIAG.

Most of the data is in the VDM as far as asbuilt data. I wouldnt really mess with it. It may just be a calibration if anything. The VDM is where the onboard scales calibration along with height calibration is.

@Bob_Mac Awesome. Please let us know. I’m about to throw this VXDiag Nano crap in the cul de sac and run it over.

There is a onboard scales calibration in FDRS. Wonder if that would resolve some issues.

Yeah. If i use the VXnano in forscan it wont see the SODCMC or SODCMD module. I also found issues in my FDRS datalog which is releated to my HEX data being all jacked up in FDRS. BEGIN ~~ ReadPartNumDIDsProcess BEGIN ~~ PingModule BEGIN ~~ BargraphDisplayV2 Comms ok with module STMin is NOT...

I posted a few days ago wondering this. I have issues with CAN FD and the VXnano.