DashLogic Black Friday Sale
11-25-2014, 12:34 PM
#1
Former Vendor
Thread Starter
DashLogic Black Friday Sale
DashLogic will be discounted for Black Friday 2014 running Thursday-Sunday, don't miss out on the discount! http://www.dashlogic.com/index.php?r...ory&path=61_63
Now available for
C6 Corvette
Camaro 5
GMT900 Gas and Diesel
CTS-V LSA
Solstice/Sky/HHR
Cobalt
Cruze
Now available for
C6 Corvette
Camaro 5
GMT900 Gas and Diesel
CTS-V LSA
Solstice/Sky/HHR
Cobalt
Cruze
Last edited by PalmerPerformance; 11-25-2014 at 01:16 PM.
11-25-2014, 12:43 PM
#2
Race Director
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,194 Likes
on
1,053 Posts
St. Jude Donor '15
DashLogic will be discounted for Black Friday 2014 running Thursday-Sunday, don't miss out on the discount! http://www.dashlogic.com/index.php?r...ory&path=61_63
Now available for
C6 Corvette
Camaro 5
CTS-V LSA
Solstice/Sky/HHR
Cobalt
Cruze
Now available for
C6 Corvette
Camaro 5
CTS-V LSA
Solstice/Sky/HHR
Cobalt
Cruze
11-25-2014, 01:56 PM
#4
Race Director
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,194 Likes
on
1,053 Posts
St. Jude Donor '15
11-25-2014, 09:31 PM
#6
Race Director
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,194 Likes
on
1,053 Posts
St. Jude Donor '15
Probably going to.. that way I can run wideband through it, put in a 2.5 bar map sensor (that I'm building now), and then I can see boost through the map sensor PID, then with just a fuel pressure sensor I can see fuel pressure too on the 2nd input
Can't beat it for the price
That SLP gauge pod thing is pretty sweet too though, and the wideband I have already does have a gauge (along with two outputs), so I guess I could just have readings of every thing every damn where, haha. Gauge is just stuffed in the glovebox right now
Can't beat it for the price
That SLP gauge pod thing is pretty sweet too though, and the wideband I have already does have a gauge (along with two outputs), so I guess I could just have readings of every thing every damn where, haha. Gauge is just stuffed in the glovebox right now
11-28-2014, 12:21 AM
#8
Race Director
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,194 Likes
on
1,053 Posts
St. Jude Donor '15
11-28-2014, 01:49 PM
#9
Burning Brakes
Just ordered mine too. Thank you for the BF discount. 
12-08-2014, 10:51 PM
#10
Burning Brakes
I like the new DashLogic device so much, I have just placed an order for the PLX wide band sensor kit. Does anyone have any advise on how to program one of the alarms so that will alarm if for example the motor sees +50 load and +3000 rpm with greater than 11.5 AFR? I read the configuration guide and I can't figure it out. 
12-08-2014, 11:19 PM
#11
Race Director
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,194 Likes
on
1,053 Posts
St. Jude Donor '15
(pid(10) >= 3000) && (pid(1) > 50) && (pid(xx) >= 11.5)
pid 10 = RPM
pid 1 = load
pid x you'll have to change to whatever your wideband is setup as. For this you will have to create a "calculation PID" specific to your wideband to convert the voltage that the wideband is sending to the dash logic controller to an AFR reading that makes sense to you and the rest of us. Page 6 of the config guide explains this. The formula should be easy enough to find for your wideband (same as you'd need for HP Tuners to get a wideband setup..)
Page 5/6
http://www.palmerperformance.com/dow...tion_Guide.pdf
Looks like PLX wideband formula is AFR = voltage / .5 + 10
Last edited by schpenxel; 12-08-2014 at 11:27 PM.
12-09-2014, 11:50 PM
#12
Burning Brakes
Don't mean to sound like a dick here.. but that example is straight up 99.9% called out on how to do it in the config guide... you just go under alarms and type in what they've show in the guide, changing one of the pid's/values to the wideband input and AFR you want it to watch out for
(pid(10) >= 3000) && (pid(1) > 50) && (pid(xx) >= 11.5)
pid 10 = RPM
pid 1 = load
pid x you'll have to change to whatever your wideband is setup as. For this you will have to create a "calculation PID" specific to your wideband to convert the voltage that the wideband is sending to the dash logic controller to an AFR reading that makes sense to you and the rest of us. Page 6 of the config guide explains this. The formula should be easy enough to find for your wideband (same as you'd need for HP Tuners to get a wideband setup..)
Page 5/6
http://www.palmerperformance.com/dow...tion_Guide.pdf
Looks like PLX wideband formula is AFR = voltage / .5 + 10
(pid(10) >= 3000) && (pid(1) > 50) && (pid(xx) >= 11.5)
pid 10 = RPM
pid 1 = load
pid x you'll have to change to whatever your wideband is setup as. For this you will have to create a "calculation PID" specific to your wideband to convert the voltage that the wideband is sending to the dash logic controller to an AFR reading that makes sense to you and the rest of us. Page 6 of the config guide explains this. The formula should be easy enough to find for your wideband (same as you'd need for HP Tuners to get a wideband setup..)
Page 5/6
http://www.palmerperformance.com/dow...tion_Guide.pdf
Looks like PLX wideband formula is AFR = voltage / .5 + 10
12-10-2014, 09:13 AM
#13
Race Director
Member Since: May 2004
Location: Raleigh, NC
Posts: 16,664
Received 1,194 Likes
on
1,053 Posts
St. Jude Donor '15
Here's the basics on how to do it:
Open dash logic, profile 1 (or whatever one you use), Calculation PID's
Click on one of the PID's that aren't being used. Put in the PID name as WIDEBAND_AFR. Units, AFR. Acronym WIDEBAND_AFR. Decimal places, 2
PID calculation set to "(pid(10001) / .5 + 10)" without the quotes. This is assuming the wideband is connected to input 1. If you are using input two, change 10001 to 10002
Now, save and now go back a screen. Go under Alarms. Select alarm 0 (or whatever one you want to use)
Check "alarm enabled". Select options you want for HUD/DIC/Audible/Continuous, duration, beep type and warning text.
For the "alarm condition epxress"
Use: (pid(10) >= 3000) && (pid(1) > 50) && (pid(20000) >= 11.5)
NOTE: I've used PID "20000" for the calculation PID. The actual number here will depend on which button you hit when you setup the calculation PID. Calculation 0 = 20000. Calculation 1 = 20001, and so on
To figure out which you used, just hit look up PID and scroll down to the 20000 ones and see which one is labeled WIDEBAND_AFR. Use that number in place of 20000 (if it's different)
That should be it.
This is obviously assuming the wideband is wired correctly, working, etc.
Personally I would use the wideband AFR on the DIC or HUD screen somewhere first to make sure it's working.
For this, just go under one of the DIC or HUD pages, advanced mode, and put something like AFR {20000}. Again, this will be a different number if you setup the calculation PID as something other than the very top one.. just go under lookup PID and figure out what the right number is (will be around 20000)
Hopefully that helps.
Last edited by schpenxel; 12-10-2014 at 09:15 AM.
12-11-2014, 11:53 AM
#14
Burning Brakes
You have to setup a "calculation PID" first. This converts the voltage coming in from the wideband to an AFR number that makes sense to us.. Then you can use that AFR in an alarm..
Here's the basics on how to do it:
Open dash logic, profile 1 (or whatever one you use), Calculation PID's
Click on one of the PID's that aren't being used. Put in the PID name as WIDEBAND_AFR. Units, AFR. Acronym WIDEBAND_AFR. Decimal places, 2
PID calculation set to "(pid(10001) / .5 + 10)" without the quotes. This is assuming the wideband is connected to input 1. If you are using input two, change 10001 to 10002
Now, save and now go back a screen. Go under Alarms. Select alarm 0 (or whatever one you want to use)
Check "alarm enabled". Select options you want for HUD/DIC/Audible/Continuous, duration, beep type and warning text.
For the "alarm condition epxress"
Use: (pid(10) >= 3000) && (pid(1) > 50) && (pid(20000) >= 11.5)
NOTE: I've used PID "20000" for the calculation PID. The actual number here will depend on which button you hit when you setup the calculation PID. Calculation 0 = 20000. Calculation 1 = 20001, and so on
To figure out which you used, just hit look up PID and scroll down to the 20000 ones and see which one is labeled WIDEBAND_AFR. Use that number in place of 20000 (if it's different)
That should be it.
This is obviously assuming the wideband is wired correctly, working, etc.
Personally I would use the wideband AFR on the DIC or HUD screen somewhere first to make sure it's working.
For this, just go under one of the DIC or HUD pages, advanced mode, and put something like AFR {20000}. Again, this will be a different number if you setup the calculation PID as something other than the very top one.. just go under lookup PID and figure out what the right number is (will be around 20000)
Hopefully that helps.
Here's the basics on how to do it:
Open dash logic, profile 1 (or whatever one you use), Calculation PID's
Click on one of the PID's that aren't being used. Put in the PID name as WIDEBAND_AFR. Units, AFR. Acronym WIDEBAND_AFR. Decimal places, 2
PID calculation set to "(pid(10001) / .5 + 10)" without the quotes. This is assuming the wideband is connected to input 1. If you are using input two, change 10001 to 10002
Now, save and now go back a screen. Go under Alarms. Select alarm 0 (or whatever one you want to use)
Check "alarm enabled". Select options you want for HUD/DIC/Audible/Continuous, duration, beep type and warning text.
For the "alarm condition epxress"
Use: (pid(10) >= 3000) && (pid(1) > 50) && (pid(20000) >= 11.5)
NOTE: I've used PID "20000" for the calculation PID. The actual number here will depend on which button you hit when you setup the calculation PID. Calculation 0 = 20000. Calculation 1 = 20001, and so on
To figure out which you used, just hit look up PID and scroll down to the 20000 ones and see which one is labeled WIDEBAND_AFR. Use that number in place of 20000 (if it's different)
That should be it.
This is obviously assuming the wideband is wired correctly, working, etc.
Personally I would use the wideband AFR on the DIC or HUD screen somewhere first to make sure it's working.
For this, just go under one of the DIC or HUD pages, advanced mode, and put something like AFR {20000}. Again, this will be a different number if you setup the calculation PID as something other than the very top one.. just go under lookup PID and figure out what the right number is (will be around 20000)
Hopefully that helps.