Banks Guage- What to Monitor



I installed a Banks Data Monster Guage with the main purpose of being a boost guage, but to also have better visibility into real time conditions generally speaking and to data log if/when needed. I have been playing with the set up and building out the different guage views and ill toss out 2 topics for discussion/feedback.
1. In one view I am monitoring catalyst temp for both bank 1 and bank 2. The temp reading on bank 1 was reading 400ish while bank 2 was reading 800ish. What would cause such an imbalance? No codes but do i maybe have a bad O2? I have noticed a slight decrease in power lately.
2. This could probably be topic in itself but given all the parameters the Banks guage can monitor out of the OBDII port, what would you all suggest I prioritize? My primary guage is showing 2 parameters (boost/vac & Intake Air Temp). I have all 5 views tentatively set up but i am open to ideas on important parameters to monitor and how to logically group them (can have up to 8 parameters on a guage view) to help monitor for anomalies/issues.
appreciate the feedback especially on question 1.




Your power decrease may be directly caused by your data streaming.
OBDII DLC is tied to CAN-D but data come from busy ECU via CGW...
The stock CAN-C is bottlenecked and ECU is super sensitive to timely CAN data.
Try to use only limited logging to during quick troubleshooting, then get off the bus.
It's not even as simple as connect /disconnect because ECU/TCU work from historical maps.
Disconnecting does not return clean-status.

The expert Banks datalogger is @S-Prihadi
- He has long practice and found some erroneous PID were inverted... perhaps that will help your Lambda troubleshooting.
Last edited by CaliBenzDriver; Mar 3, 2025 at 11:48 PM.



I am not actively data logging, I actually have not yet done any data logging since I have installed the gauge and I didn't consider the impact on the ECU until now. Honestly, my perception of reduced power was somewhat the reason I got the gauge because I wanted to specifically get a read on boost pressure. Either way, I never considered the possibility of bottlenecking the ECU but I certainly am now.
To be clear, are you saying that even if I am not logging, the mere fact I am plugged into the OBDII port and monitoring data could muck up the timing on the ECU and negatively impact performance?
Thanks for the input BTW.
Last edited by TonyD_AMG; Mar 4, 2025 at 09:55 AM.



I'm not tuned though.




I am not actively data logging, I actually have not yet done any data logging since I have installed the gauge and I didn't consider the impact on the ECU until now. Honestly, my perception of reduced power was somewhat the reason I got the gauge because I wanted to specifically get a read on boost pressure. Either way, I never considered the possibility of bottlenecking the ECU but I certainly am now.
To be clear, are you saying that even if I am not logging, the mere fact I am plugged into the OBDII port and monitoring data could muck up the timing on the ECU and negatively impact performance?
Thanks for the input BTW.
MB Networking is purposely implemented to underperform to begin with.
The banging sloppy tranny shifts are delayed ECU-TCU CAN data. You can use that metric to assess your ECU Bus.
What it is is Bosch built an ECU that relies on CAN for its core timings and MB made CAN extra unstable with delays.... ain't robust.
Busy logging on top of that can very well be instrumented, just be cognisant its not to your advantage to over do it.
That's why I think it's best to find what you want and then be off the bus for good.
You don't want to measure self-feeding problems.
Pay attention to fish-bite misfires delays and poor shifts when you load the bus with PID queries.
Last edited by CaliBenzDriver; Mar 4, 2025 at 01:39 PM.


