This was posted in the thread on the grid heater relay recall and I did not want to take that off topic so I am creating a new thread. I thought of just messaging Jimmy to see what he thought about Banks insistence, but then realized that others may benefit from my confusion on this. Especially others like me who purchased the iDash for its advertised and manual documented ability to display and clear codes. (Of course it was purchased for many other things too, but code clearing was important to me). Hence this new thread and hopefully @Jimmy07 can comment on what the Banks tech support insisted is the way the iDash works.
Background is that with my grid heater relay disconnected, I accidently forgot to push the start button twice to start the truck. The pre-heat countdown ran its course and the truck did not start. I then pressed the start button a 2nd time and it started normally. But there was a CEL after this. My Banks iDash told me the CEL fault code was for abnormal voltage detected in the heater relay circuit. This seems to have happened because as Jimmy described, "Disconnecting (the relay) COULD set a fault if a preheat is called for. The relay control is monitored by the PCM, and when a preheat is called for, the PCM activates the relay and looks for an expected voltage fluctuation." Because this voltage fluctuation/drop was not seen, the fault code was set.
I then "cleared" the code using the iDash and the iDash told me the code was cleared successfully. When I had the iDash recheck for codes, none were found so it gave the appearance of having successfully cleared it. The CEL did not go off though so that is what prompted my question of whether the code had really been cleared and wondering why the CEL did not go off after "clearing" using the iDash. I then turned off and restarted the truck normally and the CEL light was then gone. The iDash just plugs into the OBDII port and as Jimmy described in the quote below, because of this, the iDash maybe did not really clear the code and the CEL disappeared only because this particular code is transient and will be cleared and reset upon restart if the original reason for the code is not present on that subsequent restart.
I replied that the iDash only plugs into the OBD port and not into the canbus junction block and Jimmy said:
So that is the backstory and the next part to this story is that I talked at length with two Banks tech support guys this morning and relayed all this to them. I asked if the iDash was really clearing codes or not. I asked about the security gateway or firewall on the new Rams. And I also asked specifically about the need to also be connected via the canbus junction block. Now I can not vouch for the actual knowledge and capability of Banks tech support but they sure talk like they know their stuff, even to the point of inspiring confidence in their knowledge. (Unlike say, most other tech support!)
What Banks told me is that the iDash absolutely does have the ability to clear the codes. They have never heard of having to also be plugged in to the canbus junction block. They also said that it is not unusual for a CEL not to go away after clearing a code until the ignition is cycled again. Banks insisted that if the iDash reported the code as cleared, and then rechecking for codes found none, it had really been cleared. I posited the idea that maybe the iDash only thought the code was cleared because it had run through the process and sent the signal successfully. But maybe that sent signal was really blocked by the firewall gateway Jimmy described. And maybe the reason no code fault was found when I rechecked using the iDash was, because the iDash may only be looking for codes that have been sent to it by the truck, not checking in real time. If that is the case, clearing it from the iDash memory may make the iDash report no codes even though there is still one stored in the truck's computer. Banks told me "no, when you ask the iDash to check for codes, it checks the truck's computer right then, in real time. It does not only look in its own iDash memory for stored codes, if the code was not really cleared, the iDash would pick it up again on the recheck."
So unfortunately I still do not know for sure if my iDash is really clearing codes. It gives the appearance that it is and Banks insists that it is. But on the other hand I have seen Jimmy's advice many times here and I have lots of faith in his extensive knowledge. So I am inclined to believe Jimmy is correct and Banks is not even though I would prefer to believe that my iDash is really able to clear codes. Also seems odd that Banks could be so wrong on this as this is their business every day to design and engineer their products and they "should" know what their products can and can't do. They really insisted that the iDash is truly clearing codes.
Background is that with my grid heater relay disconnected, I accidently forgot to push the start button twice to start the truck. The pre-heat countdown ran its course and the truck did not start. I then pressed the start button a 2nd time and it started normally. But there was a CEL after this. My Banks iDash told me the CEL fault code was for abnormal voltage detected in the heater relay circuit. This seems to have happened because as Jimmy described, "Disconnecting (the relay) COULD set a fault if a preheat is called for. The relay control is monitored by the PCM, and when a preheat is called for, the PCM activates the relay and looks for an expected voltage fluctuation." Because this voltage fluctuation/drop was not seen, the fault code was set.
I then "cleared" the code using the iDash and the iDash told me the code was cleared successfully. When I had the iDash recheck for codes, none were found so it gave the appearance of having successfully cleared it. The CEL did not go off though so that is what prompted my question of whether the code had really been cleared and wondering why the CEL did not go off after "clearing" using the iDash. I then turned off and restarted the truck normally and the CEL light was then gone. The iDash just plugs into the OBDII port and as Jimmy described in the quote below, because of this, the iDash maybe did not really clear the code and the CEL disappeared only because this particular code is transient and will be cleared and reset upon restart if the original reason for the code is not present on that subsequent restart.
This is a fault that clears itself after a drive cycle. With your banks idash, is it just plugged straight into the OBD port, or did you also have to plug a connector into the canbus junction block behind the headlight switch?
I replied that the iDash only plugs into the OBD port and not into the canbus junction block and Jimmy said:
If the idash is only plugged into the OBD port, it doesn’t have the capability of clearing faults because of the security gateway. It can receive info from the buses, but it can’t send a command past the gateway. It might SAY it cleared, but it was the fact that the condition wasn’t met to set the fault on the next startup that the CEL wasn’t there.
So that is the backstory and the next part to this story is that I talked at length with two Banks tech support guys this morning and relayed all this to them. I asked if the iDash was really clearing codes or not. I asked about the security gateway or firewall on the new Rams. And I also asked specifically about the need to also be connected via the canbus junction block. Now I can not vouch for the actual knowledge and capability of Banks tech support but they sure talk like they know their stuff, even to the point of inspiring confidence in their knowledge. (Unlike say, most other tech support!)
What Banks told me is that the iDash absolutely does have the ability to clear the codes. They have never heard of having to also be plugged in to the canbus junction block. They also said that it is not unusual for a CEL not to go away after clearing a code until the ignition is cycled again. Banks insisted that if the iDash reported the code as cleared, and then rechecking for codes found none, it had really been cleared. I posited the idea that maybe the iDash only thought the code was cleared because it had run through the process and sent the signal successfully. But maybe that sent signal was really blocked by the firewall gateway Jimmy described. And maybe the reason no code fault was found when I rechecked using the iDash was, because the iDash may only be looking for codes that have been sent to it by the truck, not checking in real time. If that is the case, clearing it from the iDash memory may make the iDash report no codes even though there is still one stored in the truck's computer. Banks told me "no, when you ask the iDash to check for codes, it checks the truck's computer right then, in real time. It does not only look in its own iDash memory for stored codes, if the code was not really cleared, the iDash would pick it up again on the recheck."
So unfortunately I still do not know for sure if my iDash is really clearing codes. It gives the appearance that it is and Banks insists that it is. But on the other hand I have seen Jimmy's advice many times here and I have lots of faith in his extensive knowledge. So I am inclined to believe Jimmy is correct and Banks is not even though I would prefer to believe that my iDash is really able to clear codes. Also seems odd that Banks could be so wrong on this as this is their business every day to design and engineer their products and they "should" know what their products can and can't do. They really insisted that the iDash is truly clearing codes.