tonesto7
Well-known member
I agree... I looked at the FRDS logs and it indicated in my opinion so sort of conversion issue with FRDSI'm not convinced it's a J2534 issue per say but an FDRS issue in general.
Sponsored
I agree... I looked at the FRDS logs and it indicated in my opinion so sort of conversion issue with FRDSI'm not convinced it's a J2534 issue per say but an FDRS issue in general.
Maybe but Jesse’s VCM II is not showing these issues.I'm not convinced it's a J2534 issue per say but an FDRS issue in general.
When did he post that? FDRS had an issue with 31.6.2 and came out with an updated one 31.6.4 in less than a week due to the .2 version causing corruption issues...Maybe but Jesse’s VCM II is not showing these issues.
I'm seeing the same issue in my as-built data. @tonesto7, please keep us updated on how you resolve. Thanks!
What device are you using to connect, i.e. VCX Nano, Mongoose, etc.? We're trying to put all the pieces together to see if we can resolve or have to wait on Ford for an updated FDRS.I'm seeing the same issue in my as-built data. @tonesto7, please keep us updated on how you resolve. Thanks!
View attachment 40954
I used the VCX Nano to update my truck.What device are you using to connect, i.e. VCX Nano, Mongoose, etc.? We're trying to put all the pieces together to see if we can resolve or have to wait on Ford for an updated FDRS.
It was a PM.When did he post that? FDRS had an issue with 31.6.2 and came out with an updated one 31.6.4 in less than a week due to the .2 version causing corruption issues...
I'm in the same boat. VCX nanoI used the VCX Nano to update my truck.
The 712 (SCMG module) field F113, F129 are certainly Network Scan related corruptions. The 7D0 (APIM module) is not. I have see the F12A field like above on trucks that posted self-report and no network scan has been performed for a while (or at all)I'm in the same boat. VCX nano
<NODEID>
712
<F110>DSMU5T-14F548-DB</F110>
<F111>MU5T-14G009-DC</F111>
<F113>MU5 T-14F548-DD</F113>
<F129>MU5 T-14G009-EA</F129>
<F159>030000</F159>
<F15C>051103</F15C>
<F15E>030804</F15E>
<F160>062500</F160>
<F161>021906</F161>
<F188>MU5T-14G003-DD</F188>
<F18C>2010</F18C>
</NODEID>
<NODEID>
7D0
<F10A>MU5T-14G680-AA</F10A>
<F110>DSMU5T-14G670-EG</F110>
<F111>MU5T-14G681-KF</F111>
<F113>MU5T-14G670-PNL</F113>
<F124>MU5T-14G677-ABA</F124>
<F129>ML3T-14G00T-18K811-AA</F129>
<F12A>ML3T-</F12A>
<F12B>ML3T-18B955-BE</F12B>
<F12C>FFF1-14F180-FE</F12C>
<F142>MLBE10218S</F142>
<F143>20210224041110</F143>
<F144>R3W9QDWA</F144>
<F16B>MU5T-14J003-AF</F16B>
<F17F>1SN12C11</F17F>
<F188>MU5T-14G676-EG</F188>
<F18C>FUBCH20346051212</F18C>
<F190>Vin Number</F190>
<F1D0>28385C047D1D</F1D0>
<F1D1>28385C047D1E</F1D1>
</NODEID>
If that's true then my UCDS adapter does not have the same J2534 passthrough corruption that occurs with the VCX NanosThe 712 (SCMG module) field F113, F129 are certainly Network Scan related corruptions. The 7D0 (APIM module) is not. I have see the F12A field like above on trucks that posted self-report and no network scan has been performed for a while (or at all)
Could be VCX Nano firmware bug, could be just baud settings or similar. I did not play with it. I will buy the Mongoose-Plus cable when I get my truck back, test it out and report my results hereIf that's true then my UCDS adapter does not have the same J2534 passthrough corruption that occurs with the VCX Nanos
Also, I would wonder how is your UCDS adapter recognized by FDRS. Is it indeed J2534 pass-through device, or perhaps this device supports other protocols (such as J1708 and J1939 as VCM3) ?If that's true then my UCDS adapter does not have the same J2534 passthrough corruption that occurs with the VCX Nanos
RIght. I remember now. The point I was making to Bob_Mac was that because not all programmers are creating corruptions, it remains unclear whether it is an FDRS problem, generally, a problem with the the use of J2534 with FDRS, or the use of the Nano in particular. Since the VCM3 seems to work without issue, it isn’t FDRS, generally. And your testing of the Mongoose should further narrow it down to either J2534 or the Nano.Jesse uses VCM3 device and this device is not J2534 pass-through device. It uses J1708 and J1939 protocols instead