Thats not a problem. Each to their own!
Since our focus is working with willing developers and individuals, we cannot expect everyone to be like that or be willing to take time away to email logs.
Regardless, back to it!
This morning I have been lucky enough to have a cardaq3 and MDI2 on loan, we have some interesting results flashing some of the trouble some GMLAN based modules.
The main points for cardaq3:
1) When the module requests 1ms, it is doing approximately 2-4ms
2) Out of 30 flashes on one of these modules, we have had 12 failures (37% failure rate)
3) When forcing it to 2ms (I am sending the flow control before the module responds), we are seeing 5-8ms delay (0% failure rate)
4) We see random spikes of longer delay times, I would guess this is interrupts running in the scantool operating system.
The main points for MDI2:
1) 100% failure rate with Techline, it would not accept flashing the bootloader. Appears to be too large for its memory??
2) Similar delays to what the MDI1 does. Occasionally had next to no delay directly after a tester present message which appears to be a fault/timing issue.
3) When flashing with my own software, only 1 failure out of 30.
With that said, I believe I am out of options for tools to test against that I know supports GMLAN
I can genuinely understand why technicians have a dozen different J2534 tools now since every tool manufacture has a different delay multiplier that they follow as a safety barrier.
I don't believe having to use OEM specific tools is needed, the MDI2 is meant to be GMs flagship tool and it technically doesnt seem to even support this properly
I guess I am just going to keep going through module after module with delaership tools and OBDX tools until I find something that doesnt work to repeat all the tests again!