Most frequently the software errors stem from a low level obd reader being used.
Check engine light not on but codes found.
For example any problem that affects the emissions system will automatically light the check engine light.
If the check engine light is on you ve got a trouble code stored.
I d guess that something happened which triggered the light but the condition didn t persist.
Disconnect that circuit from the ecu if the light goes off probably an issue with the ecu if the light stays on look for a short to power on that circuit.
Press the erase clear button on your scanner then turn off the key and disconnect it.
After pressing erase clear and waiting until you see a no codes message you can turn off your vehicle and disconnect the scanner.
Clearing any codes present will turn off your check engine light temporarily.
There are other cases where there s no check engine light but codes.
If your check engine light is on but no code it s your scan tool not the vehicle.
In that case you could scan the computer and find a code even though the light wasn t on.
One main reason that a check engine light comes on with no code being stored is that there is a software error.
Generally if the light is coming on and no codes are stored the processor that triggers the light is faulty or the circuit is shorted to power.
You ve only got two choices at this point.
Everything in the obdii code list is in some way related to emissions.
The same is true if you have abs light on tcs light on vsc light on etc.
However all error codes are stored so you can look at historical data even with a 10 bluetooth obdii dongle and see what the code was before.
But if the problem is not emissions related and also not critical it may be stored in the computer but not light the check engine light.