MeZmeriZe wrote:
yeah, I know.. I thought at first that I had some driver loading issue due to having IDS and the mongoose setup on the same machine. (all the testman and other services for IDS were stopped though)
Probably better to do what BE and the drewtech tool do and just have a drop down with the reg entries listed and the one with the loaded driver selected.. that way you know at a glance what is there and what is active.
If you untick auto detect there is a dropdown box and you can choose the cable. I can't show which cable is chosen as it only chooses a cable when you press a button, eg it is only valid during the operation of which most are under a second. Eg if you press read VIN with your mongoose plugged in, then change to VCM2 and press read VIN it will just do it all automatically in the backgroud. It reports in the log which cable it is using eg:
2:06:46 PM Loaded J2534 Library Via: OpenPort 2.0 J2534 ISO/CAN/VPW/PWM
2:06:46 PM Successfully created OBD2 connection
2:06:46 PM Created ISO15765 connection
I remember asking some people to copy my shim dll over the top of VCM2 and other stuff to get IDS working. If you did that then its possible it would report a cable that isn't actually plugged in as working but I think it was only Tazzy and Antus that tried that.
The other possibility is the manufacturers implementations are so similar that each others driver will work with other cables, this should be highly repeatable though if it is the case. Would be interested to see if you can repeat it.
There may also be a bug where if you have no valid cable at all, then you click detect vehicle it will just use the last invalid cable it found. I tried a few things to see if I could get this to happen but couldn't repeat it.
Tazzi wrote:Looks like this ECU doesnt wanna be a happy camper, doesnt like the tester present message apparently, see logged data below:
7E0 01 3E 00 00 00 00 00 00
7E8 03 7F 3E 12 00 00 00 00
Its getting back a subfunction not supported when clicking on detect vehicle on the flash toolbox page. This occurs when before and after putting power onto FEPs.
Rolls, I can see the app unlocks the ECU, but then pops up with an error saying:
"Error Detecting Vehicle Type due to UDS error: SUBFUNCTION_NOT_SUPPORTED"
Pretty sure thats due to the above issue.
Reads bin happily though
*Edit: The XR8 is out with the old man currently, will grab a read from that when its back.
Can you send me the log?
Regarding the TESTER_PRESENT reply that is interesting. I don't parse any tester present replies so the 7F should not be of concern though. Eg I just pump the message and ignore all replies. From my testing I normally get no response at all to the tester_present message.
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. 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. 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 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. 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.
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.
Thanks for the testing guys, much better to release small iterative alpha/beta builds like this to get a polished product. I have no idea how people have a "launch" day and release something that works. I suspect that most products don't.
edit: Tazzy I'm going to filter all replies and drop anything with a subfunction other than the one requested. it will be interesting to see if this fixes your issue as that will prove the tester_present response is causing a race condition.
