Check engine light and flashing N

[dreamerman]

Thought this will not happen to a new Pajero. Came back home from work and left home again after 2 hours. All dash lights came on as normal when I started the engine (still warm) but CEL kept on and N (neutral) started flashing. I could drive as normal but CEL won't go away and N continue to flash. I drive in D and in 4WD and I have not yet install automate. I have fuel filter, catch can, EGR delete module and K&N panel filter. The EGR module is from Chiptuning and adjusted for NX with DPF. Have been flawless until now. I have a working Torque Pro.
Can anyone please provide me with some pointers?

[4ePikanini]

You have torque pro.

Scan it and post the results.

[dreamerman]

Scan it and post the results.

Torque Pro says error:
-U1100 Engine CAN timeout
-U1073 Bus Off

I cleared the code and removed the BT OBDII dongle. Started the car again and no fault codes. Will put aside the dongle and hope this won't happen again.

[oscaroo]

Yep. I had the same problem with bt dongle. Apparently the fix is to go to torque pro vehicle profile and set the obd protocol to the one the car uses rather than Auto. Search this forum for the protocol to use.

I did that but then also stopped using obd bt dongle because I'd rather a car that works than extra data I don't really need.

[geopaj]

Torque Pro says error:
-U1100 Engine CAN timeout
-U1073 Bus Off

I cleared the code and removed the BT OBDII dongle. Started the car again and no fault codes. Will put aside the dongle and hope this won't happen again.

Both are communication error codes (start with U). U1100 is a known code caused sometimes by OBD11 readers. Given you are using an OBD11 dongle, I doubt it is an issue with the car.

[BruceandBobbi]

Torque Pro says error:
-U1100 Engine CAN timeout
-U1073 Bus Off

I cleared the code and removed the BT OBDII dongle. Started the car again and no fault codes. Will put aside the dongle and hope this won't happen again.

No need to worry about those codes. Used to get the U1100 on the scan gauge.

Been using Torque Pro with the correct protocol for years and yep it's always there if I do a scan.

[psproule]

If i disconnect and reconnect the battery with my Ultragauge plugged in i have the same problem. Have to clear codes with torque pro to get it out of limp mode.

Pat

[m_and_m]

If i disconnect and reconnect the battery with my Ultragauge plugged in i have the same problem. Have to clear codes with torque pro to get it out of limp mode.

Pat

Yes. The ultragauge doesn’t like being powered up without activity on the CANBus. I always plug mine in with the ignition on

[Ian H]

I leave my Ultragauge connected all the time and don't have any issues with codes.

I did have problems using Torque causing the flashing N and limp mode until I changed the settings as advised on here. After that, no issues.

[nj swb]

I leave my Ultragauge connected all the time and don't have any issues with codes.

While your battery is connected the diagnostic port supplies power to the Ultragauge, even when the ignition is off. It's only when the battery is re-connected and powers up the Ultragauge (from no power) without any traffic on the CAN bus that issues can arise.

It's a bit like head units having permanent power, to protect clock and other settings, and accessories power, to determine when to wake up.

The diagnostic port provides permanent power (for what? ) and ignition tells the Ultragauge to wake up. It seems Ultragauge doesn't like that permanent power being first applied without traffic on the CAN bus.

[dreamerman]

Will check that the protocol is ISO15765-4CAN11/500 with faster communications disabled.