Help us help you. By posting the year, make, model and engine near the beginning of your help request, followed by the symptoms (no start, high idle, misfire etc.) Along with any prevalent Diagnostic Trouble Codes, aka DTCs, other forum members will be able to help you get to a solution more quickly and easily!
I just bought a 2017 Frontier in February of this year and my check engine light came on. After putting my scanner on it, I came up with 13DTC's. Some of them seem to have a common problem. I'll start the list with the common problem. (1 Meter/M&A) U1000 Can Communication Circuit, (3 Air Bag) U1000-01 Can Communication Circuit Past, B142A-16 Ignition Voltage [LOW] Past, B142B-16 Ignition Voltage [LOW] Past, (2 Transmission) U0100 Lost Comm(ECM)A 1t; P1705 TP Sensor 1t, (2 ALL MODE AWD/4WD) U1000 Can Communication Circuit-; P1817 Shift Actuator-. That is the list for the common problem, now for the other 5 DTC's. (1 Engine) P0448 Vent Control Valve 3, (4 BCM) C1704 FL Low Pressure Past,C1705 FR Low Pressure Past,C1706 RR Low Pressure Past,C1707 LR Low Pressure Past.
I checked brake fluid reservoir, it was filled to max line. The ignition voltage low I suspect might be the battery on account of manufacture date is 1/21. Should I start working on the common problem first?
Last edit: 4 months 1 week ago by Richard6767. Reason: Putting in engine
All these codes are set in the engine control module? Typically B codes aren't power train related and won't cause an engine light.
It isn't uncommon for low voltage or communication codes to be set in multiple modules with no issue at all. Unless there is genuinely a communication issue, I tend to ignore these codes.
I would clear all the codes in all modules and drive the truck. Then see which codes come back first focusing just on the engine control module codes.
I suspect the po448 vent control valve code will the one to return and illuminate the check engine light.
Can you scan tool generate a code report? If so, could you post it? That'd help us narrow down which modules set which faults.
Like Noah said, clear everything, test drive and see what comes back. I agree that it's not unusual to see various/random network faults in ancillary modules with no actual problem.
Topic Author
