Thread: nanocom thinks transfer case in low range when in high position and vice aversa

I think "they all do that" and it's a known problem with Nanocoms.
Regards Philip A

Whose programming is on the ECU?
What model ECU?

Originally Posted by Bazzle218

.... noticed that transfer case thinks its in low range when in high and vise a versa. Could it be the ECU if so what effect will it have? Take off / initial acceleration is poor to say the least but once you get going all is fine. ....

it's only a terminology issue as the "high" and "low" terms are not about the selected ratio but about the signal's strenght when the earth input gets to the ECU, Offtrack can explain that better but the conclusion is to not be stressed cos in reality the selection is OK as long as the high-low input is changing when the lever is moved fom high to low and vice-versa

The problem actually seems to be that the Nanocom's Td5 Engine Module was developed on MSB ECU's.
It doesn't take into account the differences between MSB and NNN diagnostic responses.

The range switch is one of the differences.
The MSB responds with the debounced state of the range switch where 1 = high, 0 = low.
The NNN responds with the raw input state of the range switch where 0 = high, 1 = low.

The Td5 Engine module appears to assume the ECU is always MSB.

The problem is fairly significant - 25% of fault codes in the range 1,x -> 6,x identify the wrong sensor on NNN ECU's.