Jump to content

Banks iDash Causing CEL?

Tomato

By Tomato
in 2020-2026 Silverado HD & Sierra HD

 Share

Recommended Posts

Tomato Enthusiast

Tomato

Posted
Posted

I am having issues with intermittent CEL's with codes U0100 and P0700.  CEL comes on and stays for about 5-6 key cycles and then shuts off.  No driving issues, etc.  Dealer is researching, and I will leave the truck with them at some point.

 

I found a GM TSB talking about how aftermarket devices plugged in to the ODBII could be the cause - even passive devices like the iDash.  However, I kept my iDash unplugged for a while, and the CEL came back.

 

Curious if anyone else with the iDash is having this issue?  Or anyone else at all for that matter.

 

Thanks.

sdelam Enthusiast

sdelam

Posted
Posted
17 hours ago, Tomato said:

I am having issues with intermittent CEL's with codes U0100 and P0700.  CEL comes on and stays for about 5-6 key cycles and then shuts off.  No driving issues, etc.  Dealer is researching, and I will leave the truck with them at some point.

 

I found a GM TSB talking about how aftermarket devices plugged in to the ODBII could be the cause - even passive devices like the iDash.  However, I kept my iDash unplugged for a while, and the CEL came back.

 

Curious if anyone else with the iDash is having this issue?  Or anyone else at all for that matter.

 

Thanks.

If you are just running an iDash (no Derringer) then I doubt its an iDash issue. Especially if they came back when you had it removed. You can try to reach out to Banks directly and ask if they've seen it anywhere else, or their tech support is very active on Facebook in the user groups. 

  • Thanks 1
kf9yr Enthusiast

kf9yr

Posted
Posted

I haven’t had a CEL with my iDash.

I have noticed that my monthly OnStar report now says communication has been blocked by an after market device plugged in the OBD2 port.




Sent from my iPad using Tapatalk Pro

gSwift Enthusiast

gSwift

Posted
Posted
2 hours ago, kf9yr said:

I haven’t had a CEL with my iDash.

I have noticed that my monthly OnStar report now says communication has been blocked by an after market device plugged in the OBD2 port.




Sent from my iPad using Tapatalk Pro

That is actually normal, per Banks.

  • 1 month later...
NYresq Enthusiast

NYresq

Posted
Posted

I had a CEL and truck popped a P0700 code a few days ago.

i have 5400 miles on my 2020 2500 Sierra duramax. Have had an IDASH on it since about 1k miles.

i drove straight to the dealer and had them check it. They reset it and told me the idash causes a communication interference between the ECM and the TCM which causes the P0700 code.

 
they said if it happens again I should remove the idash. I asked why hasn’t it been a problem for the last 4,000 miles. The service manager said they have seen it on trucks with over 20,000 miles with an idash and then it just happens.

 

if it happens again I will call Banks and have a WTF conversation, but if its just this one time no harm no foul.

even with the CEL on, the truck ran and shifted fine. I didn’t go over 60mph, so I am not sure if it dropped into any limp mode or anything.

unit Enthusiast

unit

Posted
Posted

I suppose this is a problem to watch for but I haven't had an issue with the iDash on my truck. I'm coming up on one year of ownership on March 2nd. and I've had the iDash since the truck had 500 miles on it.  I have 6,500 miles on it so far and I'd hate to be without the iDash.

Tomato Enthusiast

Tomato

Posted
  • Author
Posted

I emailed Banks a while back, and they were no help. I have not had a CEL in several weeks now, and I am beginning to wonder if it has something to do with battery voltage and may or may not be iDash related. I seem to get the CEL after I let the truck sit for 3+ days.  Also, every so often, my iDash does not power up on start, and I have to press one of its buttons to get it going.  I will have to see if I get the CEL shortly after one of these episodes.

 

Just theories and observations, but I do think it is all related.

kf9yr Enthusiast

kf9yr

Posted
Posted

I haven’t sent a CEL using an iDash on my 2020 Duramax with around 25,000 miles.

I did get a notice on the infotainment screen that a software upgrade was available. I selected Yes and the update failed.

I tried the update 3 different days and it failed each time.

This morning I unplugged the iDash before updating and it installed the update without an error.

I plugged the iDash back in and both the iDash and the truck have been working fine.

Maybe the truck checks if something is plugged in the OBDII port before updating?


Sent from my iPad using Tapatalk Pro

sdelam Enthusiast

sdelam

Posted
Posted
14 hours ago, kf9yr said:

I haven’t sent a CEL using an iDash on my 2020 Duramax with around 25,000 miles.

I did get a notice on the infotainment screen that a software upgrade was available. I selected Yes and the update failed.

I tried the update 3 different days and it failed each time.

This morning I unplugged the iDash before updating and it installed the update without an error.

I plugged the iDash back in and both the iDash and the truck have been working fine.

Maybe the truck checks if something is plugged in the OBDII port before updating?


Sent from my iPad using Tapatalk Pro

I had to try to install the update twice. It failed the first time at the house via wifi, but worked when we went out to dinner via on-star. iDash plugged in both attempts. 

unit Enthusiast

unit

Posted
Posted

I can address one comment above about iDash not starting on every startup.  I had this happen a couple of times and found that I was taking my foot off of the brake too soon when starting the truck.  iDash never fails If I start the truck and keep my foot on the brake pedal until I see the iDash lightup.  Taking my foot off too soon seems to have been the problem.

 

For the CEL problem, I'd put a battery tender on the battery and see if that fixes that issue.  Low batteries on modern cars can cause many mysterious issues.  I see similar low battery issues on the Ford and Corvette forums.  It's worth a try.

sdelam Enthusiast

sdelam

Posted
Posted (edited)

There is also a way to adjust the sensitive to start up voltage in the iDash. I have mine set to max but occasionally I still need to manually wake it up. Never correlated it to the brake pedal but its possible. 

Edited by sdelam
redwngr Senior Enthusiast

redwngr

Posted
Posted

11.10.1 Sensitivity Level

 

The iDash 1.8's automatic wakeup uses battery voltage drop when cranking the vehicle.

The wake-up sensitivity level allows you to adjust the iDash 1.8's sensitivity to the voltage drop.

Some vehicles have greater voltage drops than others and would need to set the sensitivity to the low setting. If the gauge is interfering with OnStar or other similar services, decrease the sensitivity one level lower.

 

To adjust the wake-up sensitivity level:

1. Select "Settings" from the main "MENU."

2. Select "Wake-up Sensitivity Level."

3. Select the desired sensitivity level ("Sensitivity Level: Low", "...Medium", "...High").

 

If unsure, set to "Sensitivity Level: Low" and then:

A. Turn off your vehicle and wait for the iDash to go to Sleep Mode.

B. Restart your vehicle and the iDash should start within 10 seconds after startup.

C. If it does not automatically wake-up, press any button to wake.

Increase sensitivity level by one and repeat the process.

 

 

11.10.2 Start/Stop For vehicles with engine start/stop functionality:

 

When enabled, the iDash 1.8 will not shut off when RPM drops below 600 rpm.

Instead, the vehicle will check for vehicle communication to the ECU to determine if the vehicle is shut off.

 

It will also take longer for the iDash 1.8 to go into sleep mode.

 

To enable or disable "StartStop":

1. Select "Settings" from the main "MENU."

2. Select "Wake-up Sensitivity Level."

3. Select "Start-Stop:" to "Enable" or "Disable" this feature.

4. Return to the Gauge Screen when finished.

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...