leadjae.blogg.se

1. #Ford ids testman error failed to load drivers#
2. #Ford ids testman error failed to load driver#
3. #Ford ids testman error failed to load pro#
4. #Ford ids testman error failed to load software#
5. #Ford ids testman error failed to load iso#

there must be a layer I'm not seeing as the capacitor marked in the pic below shows a resistance from it's legs to pin 13. but the pin13 trace leads down the side of the other one and though a resister where it seems to end. the writing was done on my phone so excuse if it's unreadable. I was partially expecting to discover that it just wasn't hooked up to anything but it turns out it actually is.

#Ford ids testman error failed to load driver#

(VCX/Mongoose and a bunch from the VCM) you asked why I kept hitting detect, it was because it's not clear what it detected and in one of the logs later on it actually had the details of the VCX driver (which was odd because the VCX was apart on my kitchen table for reasons I'll detail shortly.)Īs I said I would, I pulled the VCX apart and started tracing pin13 to see if it actually went anywhere.

#Ford ids testman error failed to load drivers#

the log shows about 6 found drivers from mine. IF you want a suggestion Rolls, put the name of the active J2534 that gets loaded up in the UI somewhere. I want it because it's the only other turbo one I have (other than the one in my car) but not a super big deal. I still have the tune from that PCM here and I'm gonna see if my CAN logger gets anything at all from the PCM. I figured if you put it there and setup telemetry. So basically if you want to view the file in IDA use real offsets, if you want to just save it to write back later, don't select it. Either should be writeable back now, I think I added that option. Otherwise it will just pack the file and make a file 0x170000 long.

#Ford ids testman error failed to load pro#

WOULD YOU LIKE TO SAVE THE FILE WITH ACTUAL OFFSETS? NOTE YOU WILL NOT BE ABLE TO WRITE THIS BACK TO THE PCMĬould you explain that to us mate? or is because it was in the car still not on a test bench?Īctual offsets will insert a bunch of nulls from 70k to 500k so when you load it up in IDA pro the pointers are correct. I will probably remove J2534 logging to the GUI and just log to file.Ĩ0gus wrote:Hey mate got a chance today to try reading a BA Falcon in car come up with this following

#Ford ids testman error failed to load software#

I will also ensure all other buttons on the software are disabled during a flash write.Īnother one is the J2534 logging whilst a flash is not recommended, there is a shitload of text generated which lags the GUI out at this stage.

The BF/FG PCM however seems unbrickable at the moment, other than purposely overwriting the bootloader I'm not sure how you can brick them. So in the time being be more careful with a BA PCM, it may not recover if you power it off or pull the cable during a flash write. Two other guys I know have bricked BA pcms by writing BF files onto them (with other software), but I imagine this is due to overwriting the bootloader. The other possibility is the BA does not have a recovery mode. I'm not quite sure how this could happen. What I'm assuming is that by enabling CAN sniffing and trying a flash at the same time the PCM wrote to sector 0x0 instead of 0x10000 which overwrote the bootloader. All of these failure modes have been recoverable to date. I have also flashed an FG file onto BF which causes the PCM to erase itself on bootup. I have tested my recovery mode by pulling out the OBD cable during an erase/flash, also tried pulling all ECU power mid flash and it results in an erased PCM which can still accept a flash on reboot. It seems even the security access command is failing as I don't see "unlocking controller" in the log. I then try and send the security access command and if that succeeds I assume it is in recovery mode. So as part of my recovery if I get any errors during the auto detect including J2534 errors (only buff_empty or timeout, cable hardware errors are still critical) I treat them as an autodetect failure but not a complete critical failure causing a disconnect. In recovery mode the PCM rejects all OBD commands and only accepts the UDS command security access and flash write. UDS error means the UDS command structure got back an invalid response or an error code.

#Ford ids testman error failed to load iso#

OBD error means the basic ISO connect command or poll PID etc got back a packet but it contained an OBD error code.

Usually this means cable unplugged, no power etc.

J2534 error means the cable didn't receive any packets or it failed to write. In case anyone is interested this is what I do He has tried my new version (haven't sent it out to others yet as I haven't finished the DMR stuff completely) and the recovery process also doesn't work. I should have disabled the flash write buttons if sniffing was enabled as it uses a different comms mode which doesn't reply, this will result in timeouts and the flash write failing, it should however be recoverable. He had ticked sniff ISO15765 comms and then tried a flash during the sniff all with the same cable. Ok we have our first possible bricked PCM (a test spare PCM of which he has about 20) which is quite interesting.