Failure reading DTCs on 2001 Ford Explorer Powertrain

[gallium]

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.

Any suggestions?

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.

Thanks

[gallium]

Some extra details:

I've been using an ATST value of 3A, which is, as recommended, 32 or more. The Adaptive Timing Control setting is at it's default value, AT1.

This afternoon, I suppose I'll try some other values for the ATST, including 32.

[gallium]

Tried multiple combinations of ATST with no success. Also tried a cheap ELM327 adapter and still encountered the same problem.

Everything appears to work correctly except for reading DTCs on the powertrain module. Reading DTCs from other modules in the vehicle works and reading PIDs from the powertrain module works.

I emailed [e-mail] on the 13th, but have not yet received a reply.

Not sure what else to try or do.