Digital Dash Parameters

[David]

So im in the process of adding a digital dash and would like some feedback as for as. What parameters would you guys like to have. I have some in mind but figured I ask for some options incase I missed some.

1. Coolant temperature maybe with pressure for engine and turbo side
2. Oil temp and pressure
3. Boost PSI
4. IAT before and after intercooler
5. Ambient temperature
6. Wideband
7. Fuel pressure
8. Fuel level
9. TPMS
10. Battery voltage (Courtesy of Jirwin)
11.Accelerometer (Roll, Tilt, G-force)
12. Race Spec GPS (Speedometer, Odometer, Altitude, Compass, and Lap Times)
13. Data Logging USB-C Port

 

[jirwin]

Battery voltage

 

[David]

Battery voltage

Good one

 

[Desert Sasqwatch]

Depending upon how many parameters you can add to this device, how about battery current (amps) for charge and discharge? What about non- engine related items, like odometer, trip odometer, compass direction, or fuel range?

 

[Ross]

The stock LSJ doesn't have sensors for these items. Your gauge can handle these extra sensors?
1. Coolant pressure
2. Oil temp and pressure
6. Wideband
7. Fuel pressure

 

[David]

The stock LSJ doesn't have sensors for these items. Your gauge can handle these extra sensors?
1. Coolant pressure
2. Oil temp and pressure
6. Wideband
7. Fuel pressure

Yes im bluiding a digital dash and will be adding sensors. Thats the reason im trying to get a list of parameters so I can pick and choose if I cant get them all to work.

 

[David]

Depending upon how many parameters you can add to this device, how about battery current (amps) for charge and discharge? What about non- engine related items, like odometer, trip odometer, compass direction, or fuel range?

Yes some of those I will have. I will also be able to connect to the OBDII to whatever PID are allowed to get read.

Yes Odometer not sure about fuel range as that would have to be a calculation between amount of fuel in tank and level.

Compass direction wil be under the race spec GPS antenna which reads Speedometer, Odometer, Altitude, Compass, and Lap Times.

Also have an Accelerometer (Roll, Tilt, G-force)

*Edit just checked with my geek and yes estimated fuel range is possible with fuel size and level.

 

[Gtstorey]

Are you talking about real time monitoring or data logging? Because at some point you have more than you can actually comprehend while driving. Pick out the 3-4 that you find the most important and if possible, set alarm levels for the others.

 

[David]

Are you talking about real time monitoring or data logging? Because at some point you have more than you can actually comprehend while driving. Pick out the 3-4 that you find the most important and if possible, set alarm levels for the others.

Real time data will also have data logging. Yea at once you dont need that many, but good to have incase you want to toggle through incase you want to monitor something. Yes will have high limit alerts.

 

[Brian74]

Really depends on what CAN PID's are included in the CAN data stream and what you plan to add manually, as well as the PID and channel capability of the particular dash. The aeroforce supposedly supports a bunch of PID's, where the AIM (pictured) is somewhat limited by both channels and PID's for Cobalt-specific application.

As far as additional analog channels, I retrofitted an oil PSI sending unit and am running that through a programmable analog channel, as the Cobalt only uses an oil PSI switch. I also wired the security indicator, turn signals, low coolant, brake warning and high beam indicator through the analog channels.

 

[Blizzard25]

Battery voltage

My personal favorite is "Distance since last DTC clear"

 

[Blizzard25]

Real time data will also have data logging. Yea at once you dont need that many, but good to have incase you want to toggle through incase you want to monitor something. Yes will have high limit alerts.

You can log and monitor WAY more than you think, but transfer method becomes crucial. Broadcast parameters are free data that you have to send no requests to get. SAE requests are painfully slow, and if you combine SAE requests with manufacturer specific requests you can slow down the transfer speeds even further. I can't tell you the amount of times I've seen a log with someone logging 100 parameters that said "things are logging slow", and all i do is tell them to delete one parameter that happens to be a different request type, and suddenly 99 are logging ultra fast.

 

[David]

You can log and monitor WAY more than you think, but transfer method becomes crucial. Broadcast parameters are free data that you have to send no requests to get. SAE requests are painfully slow, and if you combine SAE requests with manufacturer specific requests you can slow down the transfer speeds even further. I can't tell you the amount of times I've seen a log with someone logging 100 parameters that said "things are logging slow", and all i do is tell them to delete one parameter that happens to be a different request type, and suddenly 99 are logging ultra fast.

The logging ill be doing is minimum just when at the track or AutoX. I do see it slowing down if you have alot of information going thru.

 

[Gtstorey]

A GM "P" ecm has more problems with overloading than an "E". Also pay attention to the frequency of polling nonbroadcast parameters if you have the option. No reason to read most temperatures at the sub-second level and some things, every 5 seconds will be enough.