2001 Ford Explorer with (I believe) a Ford EEC-V engine controller. OBDLink LX adapter. Samsung Galaxy Tab 2 and Samsung Note 3. PWM protocol. Reading PIDs works as expected.
Upon trying to read the DTCs for the powertrain module I am presented with an, "Invalid/No Data." error. According to the PID view, there is 1 diagnostic code stored but the CEL/MIL is not illuminated.
Reading DTCs on the ISO protocol secondary modules like the ABS, Airbag, and PATS modules appears to work correctly in addition to reading PIDs.
I seem to recall that this worked as recently as this summer. I enabled the debug logging, but the resulting .txt file appears to be garbage, obfuscated, or encrypted. I can email it on request.
Incidentally, when querying the PIDs on the ABS module, the wheel rotation sensor PIDs will occaisionally report "NO DATA" instead of a reading. I believe this causes the PID auto scan to ignore those PIDs. I suspect the autoscan is querying all known PIDs and ignoring ones with an invalid response, since some reads fail with NO DATA, the autoscan will rarely list all four wheels. Again, the debug log appears to be garbage, but one could be supplied on request.