When did the Foxwell first show those codes? was it already plugged-in when you stopped for a picture (I don't see any warning symbols in the photo)?

My NT510 had trouble connecting to CAN (and other things gone haywire) https://xoutpost.com/bmw-sav-forums/...on-switch.html, but never set codes (while all the warning symbols were displayed), as I confirmed later using Torque Pro. I can't be sure if it was a

• 1) low battery voltage problem,
• 2) a problem caused by trying various OBD2 port extensions,
• 3) a problem with the scantool itself, or
• 4) combinations of two or more of the above.

I haven't used my Foxwell since the day I had those problems, though I updated the software since then and need to try it. This time using the factory OBD2 port only, and with the battery on a charger (to maintain over 12.5 volts).

Another thing: I also plugged and unplugged the Foxwell at least twice during that session, with the engine running, so maybe it didn't like that, and protested in its' own fashion!

__________________
01 BMW X5 E53,3.0i-5L40E, 7/13/01
topas-blau,Leder-grau,"resto-project car"

Here:
14 Lexus ES350,3.5L-U660E
09 HHR Panel,2.2L-4T45E
04 Chevy 2500HD,6.0L-4L80E
98 GMC Sierra 1500,5.7L-4L60E

Gone:
66 Chevelle Malibu 2dr ht.,327>441c.i.-TH350>PGlide/transbrake
08 Cobalt Coupe,2.2L-4T45E
69 & 75 C10s,350c.i.-TH350
86 S10,2.8L-700R4
73 Volvo 142,2.0L-MT4
72 & 73 VW SuperBeetles,1.6l-MT4
64 VW,1.2l-MT4
67 Dodge Monaco 500 2dr ht.,383c.i.-A727
56 Chevy 210 4dr,265c.i.-PGlide