- #Ford ids testman error failed to load update#
- #Ford ids testman error failed to load full#
- #Ford ids testman error failed to load software#
It does however read out all the details happily on a full normal read. which repeats the successful unlocking ect. So power ecu (Unclip from bench), back on, then can test again. which I think is because it has already been unlocked? Im not sure if these ecus timeout on the security. If I attempt to read again, when watching the log, the ECU replies with a :7E8 03 7F 27 22 Nothing else is sent, and doesnt attempt to read any other info/ Tool the does security negotiation and unlocks ECU. no mofule should reply to that but all should see it. This is the global indicator to say tester is present. Periodic tester present request of 7E0 01 3E (Maybe change this to 101 FE 01 3E. I see the following occurring (In order): Had to power off/on before it would let me try again though.įrom what I can see while monitoring the bus. No dramas! Ill grab the log in a moment! It did it multiple times in a row. it will be interesting to see if this fixes your issue as that will prove the tester_present response is causing a race condition. I suspect that most products don't.Įdit: Tazzy I'm going to filter all replies and drop anything with a subfunction other than the one requested. I have no idea how people have a "launch" day and release something that works. Thanks for the testing guys, much better to release small iterative alpha/beta builds like this to get a polished product. Is this fault reliable, eg does it happen every single time? Be good to see the log when it does occur as these sort of odd things would be good to iron out. If there is a race condition I would suspect the behavior is not always the same though, as there is a 1 second delay between pumps depending on when you press the auto detect button I wouldn't expect the error to occur every time. I should probably do something more clever like iterate all replies (normally there is only 1-3 j2534 replies, TX, SOF, then NONE which contains the actual reply ) and ignore any with a subfunction other than the one I want. I guess there could be a race condition where it receives immediately after my clear and before my send, then I would interpret the reply as for my transmit command. I clear the RX buffer before any transmits so even if the cable has buffered a SUBFUNCTION_NOT_SUPPORTED packet from the tester_present command it should still get dropped. If you get SUBFUNCTION_NOT_SUPPORTED this error is most likely occurring at another stage, most likely the read memory command during the auto detect. From my testing I normally get no response at all to the tester_present message. Eg I just pump the message and ignore all replies. I don't parse any tester present replies so the 7F should not be of concern though. Regarding the TESTER_PRESENT reply that is interesting. *Edit: The XR8 is out with the old man currently, will grab a read from that when its back. Pretty sure thats due to the above issue. "Error Detecting Vehicle Type due to UDS error: SUBFUNCTION_NOT_SUPPORTED"
Rolls, I can see the app unlocks the ECU, but then pops up with an error saying: This occurs when before and after putting power onto FEPs. Its getting back a subfunction not supported when clicking on detect vehicle on the flash toolbox page. Tazzi wrote:Looks like this ECU doesnt wanna be a happy camper, doesnt like the tester present message apparently, see logged data below: Fix ISO15765 extend addr process (Toyota IMMO). Fix ISO14230 receive KWP frame length process without P1MAX.ġ. Fix DeviceInfo.HwName to be correct with SerialNo.ġ. Fix ISO15765 receive RX_START flag message.Ģ. Fix ISO15765 receive message as RAW when Filter do not set FlowControl.ġ. Fix ISO15765 receive message as ISO15765 when Filter OFF.ġ. Fix TP20 Channel request RX ID start from 0.ġ.
Fix ISO15765 recv error when RAW CAN message mixed.ġ. Fix OPEL KW82 protocol for GM Tech2Win.ġ.
#Ford ids testman error failed to load update#
I just installed a new update now, so gonna see if it makes a difference.
Interestingly, the firmware on the device has had a lot of updates this year so it's clearly a going concern. annoyingly the chips seem to have had the labels removed so I can't tell what the CPU is, but looks like an ARM of some sort. Ford, Mazda, PDU and J2534-2 Passthrough, but I can buy and add a ton of other licences including Toyota TIS, honda HDS, JLR SDD, Subaru SSM, Volvo Vida, Porsche PT2, GM GD S2/T2W and VW ODIS. I have the following listed as active in mine. because you can buy licences to add functionality.
#Ford ids testman error failed to load software#
near as I can tell, as much as possible of the functionality is software defined. The one I have is marketed as a Ford/Mazda. VCI has it hooked up to a gpio pin but the software isn't programmed to do anything. Rolls wrote:What car is the VCX meant to work with? If it isn't Toyota or ford then it might be hooked up but I doubt it will be programmed to do anything.
0 kommentar(er)
