Me78569

tested my sensor and it much take into account atmosphereic pressure as my pot vs sensor both start at the same position. If the sensor read 14.7 psi it would jump to a different vein position.

Issue is the boost map for vein position at various psi's doesn't account for the 14 psi that we always have IE: 00-10 psi shoudl really be 14-24 psi, I have to shift all levesl up by 14psi.

Just had a thought, and it hurt, that I will have to negate 14 psi from the boost map to account for atmosphereic pressure. I am going to test this with the actual sensors tonight,

.... thinking about this I think that MAYBE I will need to add to my code that psi difference of 14.7 actually being 0 psi in the code.

Now you know why I run a raid 0 + 1 with 8 drives haha I can currently lose up to 2 drives, hot swap a new one in and keep going on my merry way. That and I run Sata enabled Scsi's I have yet to have a Scsi actually fail fail on me. Ed, You can pull the code off in Atmel AVR machine code then spend 15 years becoming a low level coder to get it back........ might be worth it?

Really all I want out of it is a lcd screen ( ordered) do display boost, drive, and current vein position. Other than that I just want the controller to run the turbo, I don't care about much more. I am uploading a video now. I am gonna mess some more with your new stuff, I can't see why it wouldn't work so it might be an issue with my setup, I had some noise coming across a pot that was making things act weird.

Got ya, Google decided to update their map API last night so we are scrambling to get things put back together at work. I will look into it more after the duct tape is applied to google inflicted knife wounds. CowBoy, I think Is see the issue with the EB manage void EBManage(){ //Trying to avoid using floats as they are slower to do math with, change if need be. const int Calibration = 2; //This is how much the viens will move based off the pressure difference. int Difference = (ExhaustPressure-MaxExhaustPressure); Difference = (Difference * Calibration); DesiredPosition += max(Difference, -20);//This way it doesn't close the veins to fast } Looking up "max" It says that max will choose the value of the two that is bigger (diff or -20) Lets plug some basic numbers iDP=40 max=45 desirepost pos would be 253 as you would be offboost mostly when applying eb dif= (40-45) -5=(-5*2) desiredpos = 253 + ( -10 or -20) or 243 Is my thinking right? Still doesn't really reflect what my testing showed though. very odd. As for void BtoDPressureManage(){ //Trying to avoid using floats as they are slower to do math with. const int Calibration = 2; //This is how much the viens will move based off the pressure difference. const int DesiredBDPRatio = 100; //this is percent, 100% means you want boot:DP 1:1. 90% = .9:1. int Difference = (ExhaustPressure-((BoostPressure*100)/DesiredBDRatio)); DesiredPosition += (Difference * Calibration); } Lets use dp =5 and bp = 1 desirepos = 235 ( since we are at 1 psi) 5-((1*100)/100)= 4 = dif despos = 235 + ( 4*2) so it is increasing vein pos when dp is higher than bp which is what we want. I will have to test that again on the bench, because it should be working... I think EDIT: Wait no it wouldn't as the boostcalc isn't being applied so we have no starting point do we?

Mike, Atmopsheric pressure at sea level is ~14.7 psi so that reading makes sense woudln't it?

I will toy with a bit more when I get some free time, I am curious to understand what you are trying to do. I have it working REALLY well at this point with my pots. I will have to take a video. The pot push pull switch combo is awesome.

Cowboy. Doesn't seem to be managing the drive pressure. Just goes full open when do increases. Haven't tested the eb yet.

Lol, I will take a look tonight when I get back to the house. Edit: Good news Cowboy, it compiles after I add a "P" to the int Difference = (ExhaustPressure-((BoostPressure*100)/DesiredBD"P"Ratio));

I am always up to benchtest an idea. I like what you haha. I will test it tell the cows come home. I am like you, a little out of the box thinking breaks me out of GPO/Server maintence mode. edit: Bad news on the code in your latest effort; Doesn't seem to work well. EB apply always goes full open. I am dicking with it still. The pressure 1:1 doesn't seem to do anything logical when testing. Thanks for hte tip on decimal.

put this in place to try and manage the Drive Pressure. Bench testing it the veins seem to follow the desired position unless drive pressure spikes then the veins open until drive pressure reduces or boost increase. Down and dirty, but it works pretty welll. { if ( SwitchPosition == HIGH && EBSwitchPosition == HIGH && ExhaustPressure <= (BoostPressure + 2)) DesiredPosition = BoostVeinPosCalc( BoostPressure ); //set vein position based on boostmap else if ( SwitchPosition == HIGH && EBSwitchPosition == HIGH && ExhaustPressure > (BoostPressure + 2)) DesiredPosition = BoostVeinPosCalc( BoostPressure ) - ((BoostPressure - ExhaustPressure) * (.25*(JumpSize))); //opens the veins if exhaust pressure is above max else if ( ThrottlePosition < 300 && SwitchPosition != HIGH) DesiredPosition = PotentiometerValue; //vein position is pot value else if (EBSwitchPosition != HIGH && SwitchPosition == HIGH && ThrottlePosition < 150 ) EBManage ();//If below %1.5 then engage Exhaust brake and regulate the exhaust pressure. else DesiredPosition = BoostVeinPosCalc( BoostPressure ); }

You should be able to just buy what is listied in the first page and follow basic setup of the and arduino and sheild. However if you aren't wanting to dable in the code, I am not sure this is the right choice for you. ' question for you turbo efficently guys. I know drive pressure > Boost is bad, but is boost more than drive also bad? ( not that it is really possible is it??). in theory if my code only tries to keep drive pressure close to boost by opening the viens then I shouldn't have an issue right? I should never have to watch for boost pressure being higher than drive? right??

Not sure what the issue is yet I will dig into it in a bit but the EBmanage () just makes hte veins go full open. I realy do like how the old ebmanage applies. I am testing hte dp now.

One step in front of me haha. Interesting I will read through, it and make sure I understand what you are doing ( need to get this stuff better in my mind) and go from there. Your prior EBmanage works really well though.

Thanks bud. wow I feel like an old guy. I cannot pick out the change in that either. Gonna move to a bigger screen. ( I did it finally)

I can count 7 jumps in vein position to the 50psi mark, vein position at 50psi ( half the pot) is at about 500. then after half way on the pot the turbo doesn't do squat. If I reduce the range from 100 to 50 then it still does 7 jumps, but the pot is rotated almost all the way. It is as if the map is looking at the boost psi, but assigning the vein position / 2 dunno

Yea I have tired 0,50 at that point. I have also done the boost map from 0-100psi range rather than 0-50psi ish. Turning the pot( emulating the boost sensor 0-5v) less than half way works great, then when you pass the half way point it won't advance more. so I only get 140-500ish from the boost sensor pot, but I am getting the full 0-5v range. I need to spend time now that I have a good code the rest of the way and jsut test with the boost sensor and changes.

2.5 years????? they expect people to dump $600 every 2 years? TERRIBLE.

If you used your AD for priming only it would DEF be a restriction. The bypass port ( don't remember exactly) was enough to allow the injection pump to suck "enough" fuel to get you home. Start sarcasm, You could just install some camper jacks in the bed of the truck and jack the tail of the truck up to 30* to have gravity prime your system???? Gravity is about as reliable as a BMW m30 running forever, or I guess a ford 300 for you domestic guys.

I wish I still had Charlies number. He made ALOT of claims about stuff changing, for the better, last year with airdog and I don't see it. There customer service is still some of the worst I have ever dealt with. 4 year life span??? really??? If they are going to lie they should at least give a good number.

Odd, Seems to be working today without that section added, I must have been tired last night. The first post has my current code. And yes ctrl c and crtl v are a rookie programmers best friend lol.

I adjusted the boost map to read 0-100 with the different veins and I have the same results. Gonna dig into that in a bit. Thoughts on this? I haven't benchtested it yet, but I think it should work like I want. { if ( SwitchPosition == HIGH && EBSwitchPosition == HIGH) DesiredPosition = BoostVeinPosCalc( BoostPressure ); //set vein position based on boostmap else if ( ThrottlePosition < 300 && SwitchPosition != HIGH) DesiredPosition = PotentiometerValue; //vein position is pot value else if (EBSwitchPosition != HIGH && SwitchPosition == HIGH && ThrottlePosition < 15 ) EBManage ();//If below %1.5 then engage Exhaust brake and regulate the exhaust pressure. else DesiredPosition = BoostVeinPosCalc( BoostPressure ); } // Set the Turbo Position SendTurboPosition( DesiredPosition ); // Delay for Processor delay(2); } //Manages the apply of the EB void EBManage(){ if (ExhaustPressure <= (MaxExhaustPressure - 10)) DesiredPosition -= 5;//these assume that the lower the number, the more restrictive the turbine housing is. else if (ExhaustPressure >= (MaxExhaustPressure + 10)) DesiredPosition += ((ExhaustPressure - MaxExhaustPressure) * 5);//if Exhaust Pressure spikes, open the veins quick. else if (ExhaustPressure < MaxExhaustPressure) DesiredPosition--; else if (ExhaustPressure > MaxExhaustPressure) DesiredPosition++; DesiredPosition = constrain(DesiredPosition, 140, 960); } Edit: Benchtested the above code and it is doing what I want, other than the pot not working like the sensor would. If you adjust tps it will kick you out of the eb loop and also the pot loop depending on what switches are on/off etc. Calling it a night, I will tackel the pot issue later.