Previous Updates
Day 1 Recap
https://schindlerengineering.com/public/2024/05/05/troubleshooting-extinct-platforms/
https://schindlerengineering.com/public/2024/05/05/codiac-godiag-j2534-vs-ford-thnk-city/
Today started with jumpstarting the 12V system using “TruckNutz”
Day 2
There are two running assumptions on why we cant charge with J1772
Player 1 (not me)
He thinks the BMS module is “bad”
Player 2 (me)
He thinks the car just sat too long and the battery resting voltage sagged below the BMS limits.
I want an excuse to break THIS bad boi out
Observations
* The J1772 charger is reporting Freezing conditions at 64F and it is dumping about 60W
* The dashboard linked above (someone elses rig) has a CEL, we actually dont have that! We just have a dead battery notification
* I experienced something similar with a Ford Transport EV – wont take a charge – on that one it was a dead board… but its comms software package actually worked
Links and Updates
Facebook Group: https://www.facebook.com/groups/27279972050/posts/10159593703302051/
Forum in Norwegian (from the YouTube Video)
https://elbilforum.no/index.php?board=29.20
- I have the Factory Software
- I have the Aftermarket Dongle
- I have the PEAK Dongle
We know the XML above guides the Factory Software tool to its “Resource”. Supposedly newer software can work magically, I have not seen that happen yet.
The values entered above are Known Incorrect (KI) – an earlier attempt. Today was written off to BHoLT because … even tho I performed a full factory re-install on the software, the damn bugger did not blow out these files!
SO
All of my troubleshooting today was lost time. PassThruName was set wrong for the PEAK dongle (grrr). I remedied that by absolutely blowing the ASS out of the install with the DELETE button in the file system. SO… when I re-install again, we should get some clean XML.
Lets do that now
That installs first, for a clean un-install you have to blow that out. One shows up as Omnitek and the other one LTD
Still dont know what that window means. It pops up during a CLEAN install. If you dont get that pop-up, dirty install. Anyhow, it will spin forever until you ACK that NAG.
Then you get to install this smoking hot pile of shit. I call it that because it is missing the most critical tool that any Diag software has
- UNIT TEST
Just some kind of window to tell me a few binaries - The Hardware is connected or not
- The Vehicle is connected via the hardware
Right?
Somebody missed that one, I guess its not a problem if you run the Proprietary Hardware that we dont have
Ok, maybe I just had a bad cache on the last open, because even after DELETING the files and re-installing mine popped with the stale data. I deleted that out of Sublime, now I see the above, which is Factory
<!--<add key="PassThruName" value="OCII Interface" />-->
<add key="PassThruName" value="3G VCI"/>
<add key="PassThruVersion" value="DashTwo" />
So somehow we need to aim that pointer at the dongle, YES?That can be understood here
https://www.peak-system.com/PCAN-PassThru-API.405.0.html?&L=1
Ok, so we are pointing at an Abstraction
Excellent, if we can just add to this a Virtual Machine or a Legacy WIN7 laptop and some poorly hacked DB9 jumpers we will be at starting point -001
…
Get your sack frosted with some virus laden links over here… using the above search terms
https://mhhauto.com/Thread-think-city-electric-car-vci-interface
Bah Bugger it all
PEAK drivers installed but no Pass-Thru
Not for GOAG or PEAK
So… I imagine that is the hangup
Now we have at least a little bit more installed over here in the Registry. Earlier hacks worked by drawing the name out of the Registry and placing that in the XML
KEYSTONE
- This is a KEY WORD
- HKEY_LOCAL_MACHINE\SOFTWARE\PassThruSupport.04.04
So “PassThruSupport.04.04 is generic. It can hold inside of it PEAK – PCAN as well as GODIAG
AH HA
Frost your nads with a bit more Virus Packed goodness here…
https://mega.nz/file/9csFybqb#SFqJjf4WQydz3Q3CrsctirxmUzL2F9D0E9X7lE7FowM
Yea, just keep clicking those links, LOL
Eventually I will get’cha
uh hu
You know I install all that shit
They give you that, which you can RawDawg with, … that is probably only good for confirming your hardware cabling (like CAN_HI, CAN_LO, GND)
- If you see good hex
- It MAY be wired correctly
BINGO
Super Obvious now
- The XML is pointing at the PassThru
- The PasThru has keywords in it
Off to try it again
PAUSE
OMFG I missed this link before
KEYSTONE
https://hrmnc.github.io/2023/11/16/Installing-Think-Diagnostics.html
Ok, I did a clean install THREE TIMES and my XML is still differing. They are claiming version 2.2.5 and I pulled from their link. Resultant install is
and about half the time I get scripting errors. Probably because it cant find the hardware. I do not always get the errors.
Grrrrrr……
-Schindler