Lil' Blackbox

General => General Discussion => Topic started by: EvoAuto on July 15, 2015, 12:39:07 AM

Title: HE351VE in a 4g63
Post by: EvoAuto on July 15, 2015, 12:39:07 AM
Hi
I just finished installing the turbo. Curtis was nice enough to build me the board and answer all my questions. I need some help fine tuning it for my setup. The engine is 2.3L 4 cylinder. The default values are not the greatest. It's starting to spool at around 4000rpm.

Curtis has instructed me to change the default curve_rpm values to 9000 17000 26000 39000 67000
I will be uploading this tomorrow when I finish work tomorrow and update you guys.

I also need to learn how to change the "performance" settings. I was able to change the "cruise" setting to find the sweet spot at idle. It seemed to spin the shaft the fastest at position 700 at idle. I went from position 40 all the way to 960 in roughly 100 increments. At position 40 it's spinning at 4000rpm's; at 700 its spinning at 6500rpm's; at 960 it is spinning at around 5000rpms. I've also noticed the exhaust note is the quietest at position 960.

Thanks for reading
Title: Re: HE351VE in a 4g63
Post by: Ryan on July 15, 2015, 08:10:50 AM
Please continue to update this thread as I have been talking with curtis for quite a while now about retrofitting one of these on my auto awd 1G.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 15, 2015, 08:23:21 AM
I haven't really put the code in the wiki to explain sections but I'll try to make mention of how most of the stuff works now.

Normal operation includes idle.
Cruise is a mode
Performance is a mode

During idle, which is anytime the turbo is under idle rpm, or rpm has past the idle walkdown rpm, and is under that value, then it will attempt to walk the turbo rpm down back under idle rpm. This area is tricky, cause you can get it stuck on the first curve value if idle and walkdown aren't tuned properly

Cruise was made for freeway operation in mind. It just attempts to get turbo rpm around 50,000. If turbo rpm is under that, it uses a static cruise value which is a bit higher than you would expect, but will help off idle but still let the turbo eventually spool up. In cruise though the code is setup to just continue to open the turbo to prevent rpm going past 50,000 all the way up to 25cm if it has to.

Performance for the time being is quite simple. It is a static value added to the current curve. Configured by jp2 header position. If the current curve value + the performance increase is under vane position 800, it is static 800. Until turbo rpm finally reaches top_end_rpm which is set at 105,000


Outside of learning how it works, it will help to know your turbo idle rpm, when the motor is completely warmed up. Also what curve you're using: 1, 2, 3, 4 ?

Don't get discouraged, there is so much room to adjust the turbo, from the default values :D
Title: Re: HE351VE in a 4g63
Post by: Rx7man on July 15, 2015, 07:09:06 PM
I am trying to convince my buddy to put one of these on his 3rd gen Rx7.. I think the logic may be fairly different on a gas engine, especially because of the throttle plates... might nearly want 2 map sensors?

curious to know how it works for you :)
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 19, 2015, 12:28:29 AM
Sorry I've been busy at work. Haven't had much time for testing. I took the car out for a drive. With my old turbo I had a pretty good tune. With this turbo and the W2A intercooler the ECU has never been in these cells before so it's running very poorly. I will be tuning when I have time this week and update you guys.

Curtis when I start logging with the Arduino it says I'm on curve 4.
Title: Re: HE351VE in a 4g63
Post by: Rx7man on July 19, 2015, 09:21:13 AM
What ECU do you have in the car for the engine?
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 19, 2015, 11:19:45 AM
What is your turbo idle rpm when your motor is completely warm?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 19, 2015, 09:40:37 PM
I am using AEM v1. I will be replacing it with an Evolution 8 ecu to run Ecuflash. In my opinion it is more user friendly. As for idle speed, it will no longer autoscroll since the last changes you sent me so I cant tell.
Title: Re: HE351VE in a 4g63
Post by: Rx7man on July 19, 2015, 10:04:25 PM
A lot of settings may be a lot different on a 2.3 L gas engine than on a diesel... there's no doubt you can make it work, it may just take a bit more work... The throttle plate is going to throw a wrench in your spokes possibly as well.

*Maybe* you will need another map sensor between the turbo and throttle plates to deal with the turbo, and the one after the throttle plates for the engine mapping?... there may of course be workarounds
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 20, 2015, 12:57:12 AM
I don't think a second map sensor is needed for my setup. I have a water to air intercooler with almost no pressure drop from Turbo to manifold.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 20, 2015, 10:47:00 AM
Make sure when you're making changes in the arduino IDE, that you save them, before uploading, so things are constant.


// Turbo
const int minimum_turbo_rpm = 4000;

to

// Turbo
const int minimum_turbo_rpm = 1;

^ Will make sure the serial output is continuous as long as the turbo is actually spinning.


const unsigned int idle_position = 480;

to

const unsigned int idle_position = 720;

^ smaller idle position, may need more


const unsigned int turbo_curve_1[5] = { 800,740,700,640,600 };
const unsigned int turbo_curve_2[5] = { 820,760,720,660,620 };
const unsigned int turbo_curve_3[5] = { 840,780,740,680,640 };
const unsigned int turbo_curve_4[5] = { 860,800,760,700,660 };

to

const unsigned int turbo_curve_1[5] = { 840,780,740,680,640 };
const unsigned int turbo_curve_2[5] = { 860,800,760,700,660 };
const unsigned int turbo_curve_3[5] = { 880,820,780,720,680 };
const unsigned int turbo_curve_4[5] = { 900,840,800,740,700 };

^ is moving the curves up by a 1cm^2


const unsigned int max_position = 940;

to

const unsigned int max_position = 960;

^ is going to let the turbo use 960, which in my testing was the absolute smallest the turbo would go physically. It might goto 980 /shrug, but you're going to need more room to close the turbo up.

I imagine your curve will probably include that position, especially if you've used it and it sounds nothing like my videos ie: turbo whining at idle.
Title: Re: HE351VE in a 4g63
Post by: Rx7man on July 20, 2015, 11:26:52 AM
Quote from: EvoAuto on July 20, 2015, 12:57:12 AM
I don't think a second map sensor is needed for my setup. I have a water to air intercooler with almost no pressure drop from Turbo to manifold.
I'm not concerned about the pressure drop through the IC, I'm thinking at part throttle you're going to have a BIG pressure drop across the throttle plates, and if you try and spin the turbo too hard you'll surge it.. or the BOV is just going to be venting a whole lot depending on the setup
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 20, 2015, 01:02:29 PM
I'm sure he has a blow off, most gasser turbo cars have them. And since its rpm the rotor should have inertia and not spin down incredibly fast and bark.
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 22, 2015, 02:00:18 AM
Went for a tune last night. The car pulls very hard at 10psi. After about 30 minutes of driving though the car started to blow blue smoke. I limped it back to the shop thinking it was the engine but when I started this morning there was no blue smoke at all. Did a compression and leak down test. Engine checked out ok. I think the oil pressure might be too high coming from the oil filter housing so I decided to feed the Turbo from the head instead. I also have a poorly positioned drain due to the controller. I'll report back soon. I hope i didn't blow the turbo's seal. Very excited though the Turbo is spooling around 4000rpm and pulls very hard.
Title: Re: HE351VE in a 4g63
Post by: Ryan on July 22, 2015, 07:11:38 AM
When you say "spooling", what do you mean?  It's just starting to spool and build boost at 4000, or it's at "full" boost (10psi) by 4000? 
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 26, 2015, 06:59:42 PM
Quote from: kapok6 on July 22, 2015, 07:11:38 AM
When you say "spooling", what do you mean?  It's just starting to spool and build boost at 4000, or it's at "full" boost (10psi) by 4000? 

I'm at about 12psi at 4000RPM. I will log a bit more this week.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 26, 2015, 10:44:02 PM
If the turbo doesn't sound like a turbine, move the curves up again by 20

And if you can, save a pull from the serial output to a txt file and upload it for me to read
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 26, 2015, 10:59:49 PM
I will give it a try. I was planing on also trying what you suggested before regarding the wastegate. Once i find out what turbine speed corresponds to what boost pressure I'd like to have the controller try and regulate the boost. Where do I enter the max shaft speed?
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 27, 2015, 08:03:28 AM
It's already setup to max out at 130,000, which is about 40psi on my vehicle. You could curve it down to 80k.. etc

It is near the bottom section of the calculate curve tab
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 28, 2015, 02:41:32 AM
Did some more tuning this evening. Got the turbo to 13 psi by 3200 RPM's in 3rd gear. I'm not sure why the turbo's position does not change at all regardless of shaft RPM. At 14 psi the shaft is spinning at around 85000 RPM's at position 800. Here is a log as well as the modified LLB code.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 28, 2015, 08:29:55 AM

* Turbo RPM Curve : 4
   * 4000 - 9000  : 40 - 900
   * 9000 - 17000  : 900 - 840
   * 17000 - 26000  : 840*
   * 26000 - 39000  : 840 - 800
   * 39000 - 1464  : 800 - 740
   * 1464 - 105000 : 740 - 700
Done.


ran out of room in the int on the last curve rpm.

change the curves to

unsigned int curve_rpm[5] = { 9000, 17000, 26000, 39000, 65500 };


That'll fix that for the most part.

Performance mode sets vane position to current curve position + the position from JP1. * When calculated vane position + performance is not at least 800, vane position is set to 800. That's why you aren't going to see it change vane position at all. Keep it out of this mode until you feel like the turbo curve is right.

Please for the sake of tuning this turbo, don't use performance at all, the curve isn't tuned well at all and having perf mode on isn't going to do anything until the curve is stable.


The turbo isn't hauling until it is @ at least 110,000rpm, you need to be able to get it there without it holding your motor back.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 28, 2015, 08:47:20 AM
Here's an update for you..

I've included a lot of other changes I've made, like the accel variable is in.. etc...

I moved your curves around, let me know how it feels in the car accelerating. Is the turbo holding it back or is it just not spooling fast enough, you can find out by toggling the cruise switch and if you feel the car accelerate the moment you hit the switch, the vane positions are too constricting.
Title: Re: HE351VE in a 4g63
Post by: Ryan on July 28, 2015, 10:57:10 AM
Keep the updates coming!
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 28, 2015, 11:41:14 PM
Quote from: hakcenter on July 28, 2015, 08:47:20 AM
Here's an update for you..

I've included a lot of other changes I've made, like the accel variable is in.. etc...

I moved your curves around, let me know how it feels in the car accelerating. Is the turbo holding it back or is it just not spooling fast enough, you can find out by toggling the cruise switch and if you feel the car accelerate the moment you hit the switch, the vane positions are too constricting.

Funny you say that actually. Tonight while driving home i decided to leave it in performance mode (position:800) and did a full throttle pull; At 4500 it was at about 15psi when I flipped the switch to cruise (p:300) and the boost just kept climbing and fast. At 6000rpm it was reaching 25psi. My wastegate couldn't control the boost at all.

I will upload your new code tomorrow and try it out. 'Idle' mode is what I should be in correct?
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 29, 2015, 08:04:51 AM
Ya it should be in idle, when turbo rpm is under idle rpm, and it should walk down if turbo rpm goes over walkdown rpm once, then rpm ever goes under it

Also remember that there is priority in the modes.

Cruise > Brake > Performance.

So with Perf on, you can't get into cruise without turning perf off.
Title: Re: HE351VE in a 4g63
Post by: Rx7man on July 29, 2015, 11:15:52 AM
Isn't it a little redundant to have a wastegate as well as a VGT turbo?  At this point it might be a simple way to control the boost, but you shouldn't need it at all
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 29, 2015, 11:16:51 AM
I tried to let him know during fab that it is not necessary. For compounding it is necessary but I don't think he'll be compounding.

No problem thou, just mount a block off plate.
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 29, 2015, 11:45:23 AM
I had a different setup in the car before that's why I have a Watergate. I plan on using it for knock control since my ECU does not communicate with the arduino board.
Title: Re: HE351VE in a 4g63
Post by: Rx7man on July 31, 2015, 10:51:28 AM
That makes sense.

Your ECU could communicate with the Arduino in a limited fashion.. you could have the wastegate control hooked up to an input on the Arduino, and some added logic could open the VGT when it gets the signal that would normally open the wastegate... just a thought
Title: Re: HE351VE in a 4g63
Post by: hakcenter on July 31, 2015, 01:13:50 PM
Not on a dsm,  there's no real output. It communicates at 1953 baud, etc

Only way would be to interface the boost gauge output and make it a knock gauge. Then measure the output on an adc on the arduino.
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on July 31, 2015, 01:17:22 PM
Quote from: hakcenter on July 31, 2015, 01:13:50 PM
Not on a dsm,  there's no real output. It communicates at 1953 baud, etc

Only way would be to interface the boost gauge output and make it a knock gauge. Then measure the output on an adc on the arduino.

I have an AEM ECU. It has a few options for output.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on August 01, 2015, 12:58:38 AM
Is the new curve any better or is it lugging the motor to spool up?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on August 01, 2015, 01:30:31 AM
Quote from: hakcenter on August 01, 2015, 12:58:38 AM
Is the new curve any better or is it lugging the motor to spool up?

It is too restrictive. Engine seems to choke after 2500RPM. I will update with the new map I'm trying out. Car is at the body shop right now. I get it back on Wednesday.
Title: Re: HE351VE in a 4g63
Post by: Ryan on August 11, 2015, 07:23:46 AM
Any update?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on August 14, 2015, 02:43:56 AM
Went for a drive tonight. I am having trouble controlling boost with the VGT. No matter what I set the "top_end_rpm" value to it easily exceeds it. At roughly 100000 RPM I was at 15 PSI tonight. I had set the "top_end_rpm" to 55000 just to test the VGT. I wanted to set a low number because I disabled my wastegate and didn't want to overboost. It didn't seem to change anything. Pressure would climb to 15+PSI before I would let go. Here is the settings I was using. I can't post a log from controller. Windows 10 will not copy the entire log to paste into notepad. Just a few lines.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on August 14, 2015, 10:15:05 AM
top_end_rpm is the intro rpm into the top end control. If you want to prevent it from exceeding the top_end_rpm set the last curve point value to 40, but that isn't really the right way.

I've taken the liberty of re-writing the top end section for you.

const unsigned long top_end_rpm = 94000;

The new intro rpm is at 94,000


        // -----
        // TOP End Control Section
             if (performance_mode && turbo_rpm <= 96000) { vane_position = map(turbo_rpm, top_end_rpm, 96000, turbo_curve[4] + performance_position, 580); }
        else if (turbo_rpm <= 96000) { vane_position = map(turbo_rpm, top_end_rpm, 96000, turbo_curve[4], 600); }
        else if (turbo_rpm <= 98000) { vane_position = 500; }
        else if (turbo_rpm <= 100000) { vane_position = 400; }
        else if (turbo_rpm <= 102000) { vane_position = 340; }
        else if (turbo_rpm <= 104000) { vane_position = 280; }
        else { vane_position = map(turbo_rpm, 104000, 106000, 280, min_position); }
        if (turbo_rpm > 106000) { vane_position = min_position; }
        // Overrun protection
        if (turbo_rpm > 130000) { vane_position = 0; };

The new top end control tries to keep the shaft speed under 106,000. Adjust that section if you want to raise / lower the total top rpm of the turbo.

Also I had noticed you had minimum_position = 600;. That's really bad. The min / max positions are for constraints, and are really for hard-coded maximums do not adjust these at all. Leave them at 40 / 940. With it set at 600, the turbo can't get any larger and prevent over-run.


Please use my attached zip, at the bottom of this post, or here (http://community.lilbb.com/general-discussion/he351ve-in-a-4g63/?action=dlattach;attach=120), I've updated your setup to 1.1.1
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on August 15, 2015, 01:07:25 AM
Thank you for doing that. Looks like the code has changed . I will have to familiarize myself with it. When I try to compile and send, it gives me the following error. Not sure if I am doing something wrong.


AA_SETUP.ino: In function 'void setup()':
AA_SETUP:14: error: 'lbb_version' was not declared in this scope
AA_SETUP:21: error: 'FreqMeasure' was not declared in this scope
AA_SETUP:26: error: 't1' was not declared in this scope
AA_SETUP:27: error: 't2' was not declared in this scope
AA_SETUP:32: error: 'CAN1' was not declared in this scope
AA_SETUP:32: error: 'NORMAL' was not declared in this scope
AA_SETUP:38: error: 'SWITCH_SPARE' was not declared in this scope
AA_SETUP:42: error: 'idle_rpm' was not declared in this scope
AA_SETUP:44: error: 'idle_walkdown_rpm' was not declared in this scope
AA_SETUP:46: error: 'idle_position' was not declared in this scope
AA_SETUP:48: error: 'cruise_position' was not declared in this scope
AA_SETUP:49: error: 'HEADER_JP2' was not declared in this scope
AA_SETUP:49: error: 'performance_position' was not declared in this scope
AA_SETUP:49: error: 'perf_pos_1' was not declared in this scope
AA_SETUP:49: error: 'performance_position' was not declared in this scope
AA_SETUP:49: error: 'perf_pos_2' was not declared in this scope
AA_SETUP:51: error: 'performance_position' was not declared in this scope
AA_SETUP:54: error: 'HEADER_JP1_1' was not declared in this scope
AA_SETUP:54: error: 'HEADER_JP1_2' was not declared in this scope
AA_SETUP:56: error: 'turbo_curve' was not declared in this scope
AA_SETUP:56: error: 'turbo_curve_1' was not declared in this scope
AA_SETUP:59: error: 'turbo_curve' was not declared in this scope
AA_SETUP:59: error: 'turbo_curve_2' was not declared in this scope
AA_SETUP:62: error: 'turbo_curve' was not declared in this scope
AA_SETUP:62: error: 'turbo_curve_3' was not declared in this scope
AA_SETUP:65: error: 'turbo_curve' was not declared in this scope
AA_SETUP:65: error: 'turbo_curve_4' was not declared in this scope
AA_SETUP:70: error: 'curve_rpm' was not declared in this scope
AA_SETUP:74: error: 'turbo_curve' was not declared in this scope
AA_SETUP:109: error: 'top_end_rpm' was not declared in this scope
AA_SETUP:119: error: 'serial_out' was not declared in this scope
A_LOOP.ino: In function 'void loop()':
A_LOOP:20: error: 't1' was not declared in this scope
A_LOOP:21: error: 't2' was not declared in this scope
A_LOOP:23: error: 'FreqMeasure' was not declared in this scope
A_LOOP:30: error: 'turbo_rpm' was not declared in this scope
CALCULATE_MODES.ino: In function 'void calculate_modes()':
CALCULATE_MODES:12: error: 'port_d' was not declared in this scope
CALCULATE_MODES:13: error: 'SWITCH_CRUISE' was not declared in this scope
CALCULATE_MODES:13: error: 'cruise_mode' was not declared in this scope
CALCULATE_MODES:13: error: 'cruise_mode' was not declared in this scope
CALCULATE_MODES:14: error: 'SWITCH_PERFORMANCE' was not declared in this scope
CALCULATE_MODES:14: error: 'performance_mode' was not declared in this scope
CALCULATE_MODES:14: error: 'performance_mode' was not declared in this scope
CALCULATE_MODES:15: error: 'SWITCH_BRAKE' was not declared in this scope
CALCULATE_MODES:15: error: 'brake_mode' was not declared in this scope
CALCULATE_MODES:15: error: 'brake_mode' was not declared in this scope
CALCULATE_MODES:17: error: 'current_mode' was not declared in this scope
CALCULATE_MODES:18: error: 'idle_mode' was not declared in this scope
CALCULATE_MODES:19: error: 'idle_walkdown_mode' was not declared in this scope
CALCULATE_MODES:20: error: 'cruise_mode' was not declared in this scope
CALCULATE_MODES:21: error: 'performance_mode' was not declared in this scope
CALCULATE_MODES:22: error: 'brake_mode' was not declared in this scope
CALCULATE_MODES:23: error: 'spare_mode' was not declared in this scope
CALCULATE_MODES:25: error: 'cruise_mode' was not declared in this scope
CALCULATE_MODES:25: error: 'brake_mode' was not declared in this scope
CALCULATE_MODES:25: error: 'performance_mode' was not declared in this scope
CALCULATE_MODES:27: error: 'brake_mode' was not declared in this scope
CALCULATE_MODES:27: error: 'performance_mode' was not declared in this scope
CALCULATE_VANE_POSITION.ino: In function 'void calculate_vane_position()':
CALCULATE_VANE_POSITION:12: error: 'turbo_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:12: error: 'minimum_turbo_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:13: error: 'brake_mode' was not declared in this scope
CALCULATE_VANE_POSITION:13: error: 'cruise_mode' was not declared in this scope
CALCULATE_VANE_POSITION:14: error: 'curve_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:18: error: 'idle_check' was not declared in this scope
CALCULATE_VANE_POSITION:19: error: 'idle_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:20: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:20: error: 'idle_position' was not declared in this scope
CALCULATE_VANE_POSITION:21: error: 'idle_mode' was not declared in this scope
CALCULATE_VANE_POSITION:22: error: 'idle_walkdown_mode' was not declared in this scope
CALCULATE_VANE_POSITION:24: error: 'idle_mode' was not declared in this scope
CALCULATE_VANE_POSITION:25: error: 'idle_walkdown_mode' was not declared in this scope
CALCULATE_VANE_POSITION:25: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:25: error: 'last_vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:25: error: 'quarter_cm' was not declared in this scope
CALCULATE_VANE_POSITION:25: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:25: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:30: error: 'idle_walkdown_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:30: error: 'idle_check' was not declared in this scope
CALCULATE_VANE_POSITION:30: error: 'idle_walkdown_mode' was not declared in this scope
CALCULATE_VANE_POSITION:30: error: 'idle_walkdown_mode' was not declared in this scope
CALCULATE_VANE_POSITION:31: error: 'idle_walkdown_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:31: error: 'idle_check' was not declared in this scope
CALCULATE_VANE_POSITION:32: error: 'idle_walkdown_mode' was not declared in this scope
CALCULATE_VANE_POSITION:32: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:32: error: 'last_vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:32: error: 'quarter_cm' was not declared in this scope
CALCULATE_VANE_POSITION:33: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:33: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:34: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:34: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:35: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:35: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:36: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:36: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:38: error: 'top_end_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:39: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:39: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:43: error: 'performance_mode' was not declared in this scope
CALCULATE_VANE_POSITION:43: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:43: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:43: error: 'performance_position' was not declared in this scope
CALCULATE_VANE_POSITION:44: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:44: error: 'turbo_curve' was not declared in this scope
CALCULATE_VANE_POSITION:45: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:46: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:47: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:48: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:49: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:49: error: 'min_position' was not declared in this scope
CALCULATE_VANE_POSITION:50: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:50: error: 'min_position' was not declared in this scope
CALCULATE_VANE_POSITION:52: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:56: error: 'performance_mode' was not declared in this scope
CALCULATE_VANE_POSITION:56: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:56: error: 'top_end_rpm' was not declared in this scope
CALCULATE_VANE_POSITION:57: error: 'performance_position' was not declared in this scope
CALCULATE_VANE_POSITION:59: error: 'vane_position' was not declared in this scope
CALCULATE_VANE_POSITION:59: error: 'min_position' was not declared in this scope
MODE_CRUISE.ino: In function 'void cruise()':
MODE_CRUISE:12: error: 'turbo_rpm' was not declared in this scope
MODE_CRUISE:12: error: 'vane_position' was not declared in this scope
MODE_CRUISE:12: error: 'one_cm' was not declared in this scope
MODE_CRUISE:13: error: 'turbo_rpm' was not declared in this scope
MODE_CRUISE:13: error: 'vane_position' was not declared in this scope
MODE_CRUISE:13: error: 'half_cm' was not declared in this scope
MODE_CRUISE:14: error: 'vane_position' was not declared in this scope
MODE_CRUISE:14: error: 'min_position' was not declared in this scope
MODE_CRUISE:15: error: 'turbo_rpm' was not declared in this scope
MODE_CRUISE:15: error: 'vane_position' was not declared in this scope
MODE_CRUISE:15: error: 'quarter_cm' was not declared in this scope
MODE_CRUISE:16: error: 'vane_position' was not declared in this scope
MODE_CRUISE:16: error: 'cruise_position' was not declared in this scope
MODE_EXHAUST_BRAKE.ino: In function 'void exhaust_brake()':
MODE_EXHAUST_BRAKE:12: error: 'turbo_rpm' was not declared in this scope
MODE_EXHAUST_BRAKE:12: error: 'vane_position' was not declared in this scope
MODE_EXHAUST_BRAKE:12: error: 'vane_position' was not declared in this scope
MODE_EXHAUST_BRAKE:12: error: 'max_position' was not declared in this scope
SERIAL_OUTPUT.ino: In function 'void serial_output()':
SERIAL_OUTPUT:18: error: 'turbo_rpm' was not declared in this scope
SERIAL_OUTPUT:18: error: 'minimum_turbo_rpm' was not declared in this scope
SERIAL_OUTPUT:19: error: 'vane_position' was not declared in this scope
SERIAL_OUTPUT:33: error: 'last_vane_position' was not declared in this scope
SERIAL_OUTPUT:77: error: 'turbo_accel' was not declared in this scope
SERIAL_OUTPUT:110: error: 'current_mode_array' was not declared in this scope
SERIAL_OUTPUT:110: error: 'current_mode' was not declared in this scope
In file included from AA_SETUP.ino:11:0:
TIMER1_SET_TURBO_POSITION.ino: In function 'void set_turbo_position()':
TIMER1_SET_TURBO_POSITION:13: error: 'vane_position' was not declared in this scope
C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:87:35: note: in definition of macro 'constrain'
#define constrain(amt,low,high) ((amt)<(low)?(low):((amt)>(high)?(high):(amt)))
                                   ^
TIMER1_SET_TURBO_POSITION:13: error: 'min_position' was not declared in this scope
C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:87:41: note: in definition of macro 'constrain'
#define constrain(amt,low,high) ((amt)<(low)?(low):((amt)>(high)?(high):(amt)))
                                         ^
TIMER1_SET_TURBO_POSITION:13: error: 'max_position' was not declared in this scope
C:\Program Files (x86)\Arduino\hardware\arduino\avr\cores\arduino/Arduino.h:87:60: note: in definition of macro 'constrain'
#define constrain(amt,low,high) ((amt)<(low)?(low):((amt)>(high)?(high):(amt)))
                                                            ^
TIMER1_SET_TURBO_POSITION:14: error: 'final_vane_position' was not declared in this scope
TIMER1_SET_TURBO_POSITION:16: error: 'turbo_rpm' was not declared in this scope
TIMER1_SET_TURBO_POSITION:16: error: 'top_end_rpm' was not declared in this scope
TIMER1_SET_TURBO_POSITION:16: error: 'curve_rpm' was not declared in this scope
TIMER1_SET_TURBO_POSITION:16: error: 'brake_mode' was not declared in this scope
TIMER1_SET_TURBO_POSITION:17: error: 'last_vane_position' was not declared in this scope
TIMER1_SET_TURBO_POSITION:30: error: 'last_vane_position' was not declared in this scope
TIMER1_SET_TURBO_POSITION:36: error: 'CAN1' was not declared in this scope
TIMER1_SET_TURBO_POSITION:36: error: 'extID' was not declared in this scope
TIMER2_KEEP_TIME.ino: In function 'void keep_time()':
TIMER2_KEEP_TIME:12: error: 'timer' was not declared in this scope
TIMER2_KEEP_TIME:14: error: 'turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:14: error: 'top_end_rpm' was not declared in this scope
TIMER2_KEEP_TIME:14: error: 'update_vane_position' was not declared in this scope
TIMER2_KEEP_TIME:15: error: 'curve_rpm' was not declared in this scope
TIMER2_KEEP_TIME:15: error: 'update_vane_position' was not declared in this scope
TIMER2_KEEP_TIME:16: error: 'update_vane_position' was not declared in this scope
TIMER2_KEEP_TIME:19: error: 'accel_timer' was not declared in this scope
TIMER2_KEEP_TIME:20: error: 'alternate_accel' was not declared in this scope
TIMER2_KEEP_TIME:21: error: 'turbo_accel' was not declared in this scope
TIMER2_KEEP_TIME:21: error: 'turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:21: error: 'last_turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:24: error: 'turbo_accel' was not declared in this scope
TIMER2_KEEP_TIME:24: error: 'turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:24: error: 'last_turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:27: error: 'turbo_accel' was not declared in this scope
TIMER2_KEEP_TIME:28: error: 'last_turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:28: error: 'turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:30: error: 'accel_timer' was not declared in this scope
TIMER2_KEEP_TIME:36: error: 'update_vane_position' was not declared in this scope
TIMER2_KEEP_TIME:37: error: 'serial_out' was not declared in this scope
TIMER2_KEEP_TIME:38: error: 'turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:38: error: 'top_end_rpm' was not declared in this scope
TIMER2_KEEP_TIME:39: error: 'turbo_rpm' was not declared in this scope
TIMER2_KEEP_TIME:39: error: 'top_end_rpm' was not declared in this scope
'lbb_version' was not declared in this scope
Title: Re: HE351VE in a 4g63
Post by: hakcenter on August 15, 2015, 01:17:12 AM
unzip into a new folder named, _4g63_LBB

inside the arduino folder in documents. I put in the underscore so the variables would be on the first tab
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on August 15, 2015, 01:25:12 AM
Quote from: hakcenter on August 15, 2015, 01:17:12 AM
unzip into a new folder named, _4g63_LBB

inside the arduino folder in documents. I put in the underscore so the variables would be on the first tab

Just fixed it as you were typing it. Thank you. I will upload tomorrow and test it.
Title: Re: HE351VE in a 4g63
Post by: Ryan on August 18, 2015, 07:09:18 AM
How did the test go?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on August 18, 2015, 10:40:00 AM
Test was great. I'll upload settings I used tonight. I can get it to hold 10 psi without the wastegate opening at all. I will be going to the track on Friday and play with it some more.

Edit: File added
Title: Re: HE351VE in a 4g63
Post by: Ryan on August 20, 2015, 07:26:19 AM
What RPM are you seeing 10psi now? 
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on August 22, 2015, 02:03:31 AM
Did some more testing at the track. I am having trouble controlling boost past 10psi.

With my previous test run, I was able to hold a very steady 10psi with the settings I uploaded without the wastegates help. I then decided for tonight I would raise the limit to 105000 RPM to see what pressure it would correspond to. I also had AEM open my wastegate at 20psi just in case. I was seeing anywhere from 17 to 24psi through out the RPM range. It would spike past 20, the wastegate would open up, the boost would drop, wastegate closes and boost would spike again.

We only got 3 runs in before they closed the track so I was not able to experiment further. I am going to try and slowly raise the top-end RPM since the shaft speed vs boost is hard to predict.

Another Issue I was having was with the positioning I have set for the turbo curve. It is modifying the value as the turbo reaches the pre-set RPMs. It is opening the vane more than it should. I was able to get a log of it.

As for what RPM I get 10psi, it is around 3300 at vane position 720 and from there it climbs much faster.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on August 22, 2015, 08:04:22 AM
This section is why you can't get into 105,000.

               if (performance_mode && turbo_rpm <= 90000) { vane_position = map(turbo_rpm, top_end_rpm, 95000, turbo_curve[4] + performance_position, 580); }
        else if (turbo_rpm <= 90000) { vane_position = map(turbo_rpm, top_end_rpm, 96000, turbo_curve[4], 600); }
        else if (turbo_rpm <= 910000) { vane_position = 400; }
        else if (turbo_rpm <= 92000) { vane_position = 340; }
        else if (turbo_rpm <= 93200) { vane_position = 240; }
        else if (turbo_rpm <= 94000) { vane_position = 180; }
        else { vane_position = map(turbo_rpm, 92000, 93000, 280, min_position); }
        if (turbo_rpm > 95000) { vane_position = min_position; }
        // Overrun protection
        if (turbo_rpm > 100000) { vane_position = 0; };


First it walks into the very first if, since no performance mode, it falls into the next.

else if (turbo_rpm <= 90000) { vane_position = map(turbo_rpm, top_end_rpm, 96000, turbo_curve[4], 600); }


The expectation of this code here, is top_end_rpm is less than 96,000. Since you adjusted top_end_rpm to 95,000 and didn't adjust any of the rest of the code. It gets stuck in this if, then it walks immediately to the final catch.


if (turbo_rpm > 95000) { vane_position = min_position; }
        // Overrun protection
        if (turbo_rpm > 100000) { vane_position = 0; };


Adjust the sections, and remember top_end_rpm is the intro rpm, not the final. The final rpm you want is decided in those last 2 if statements. Overrun being the final absolute last chance to prevent overspin.

If you wanted to limit to 105,000, it would look something like this:


const unsigned long top_end_rpm = 93000;



// TOP End Control Section
             if (performance_mode && turbo_rpm <= 93000) { vane_position = map(turbo_rpm, top_end_rpm, 96000, turbo_curve[4] + performance_position, 580); }
        else if (turbo_rpm <= 93000) { vane_position = map(turbo_rpm, top_end_rpm, 96000, turbo_curve[4], 600); }
        else if (turbo_rpm <= 96000) { vane_position = 400; }
        else if (turbo_rpm <= 98000) { vane_position = 340; }
        else if (turbo_rpm <= 100000) { vane_position = 240; }
        else { vane_position = map(turbo_rpm, 102000, 104000, 280, min_position); }
        if (turbo_rpm > 104000) { vane_position = min_position; }
        // Overrun protection
        if (turbo_rpm > 105000) { vane_position = 0; };
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on August 22, 2015, 11:42:14 AM
Thank you for responding so quickly. I am talking about this section of the curve:
const unsigned int curve_rpm[5] = { 9000, 27000, 46000, 69000, 85000 };
unsigned int turbo_curve[5] = { 0,0,0,0,0 };
const unsigned int turbo_curve_1[5] = { 800,740,700,660,640 };
const unsigned int turbo_curve_2[5] = { 820,760,720,680,660 };
const unsigned int turbo_curve_3[5] = { 840,780,740,700,680 };
const unsigned int turbo_curve_4[5] = { 780,720,700,680,520 };


It is exceeding the the positions I have set. Here is an example from the log:
CPOS : 657 | APOS : 656 | RPM :  30540 | Accel :  -19 | Mode : Normal
CPOS : 659 | APOS : 659 | RPM :  29820 | Accel :   -8 | Mode : Normal
CPOS : 660 | APOS : 660 | RPM :  29160 | Accel :   -1 | Mode : Normal
CPOS : 662 | APOS : 662 | RPM :  28080 | Accel :   -1 | Mode : Normal
CPOS : 664 | APOS : 664 | RPM :  27300 | Accel :   -1 | Mode : Normal
CPOS : 665 | APOS : 665 | RPM :  26580 | Accel :   -1 | Mode : Normal
CPOS : 667 | APOS : 667 | RPM :  25680 | Accel :   -1 | Mode : Normal
CPOS : 669 | APOS : 668 | RPM :  25020 | Accel :   -6 | Mode : Normal
CPOS : 670 | APOS : 670 | RPM :  24420 | Accel :   -3 | Mode : Normal
CPOS : 671 | APOS : 671 | RPM :  23820 | Accel :   -6 | Mode : Normal
CPOS : 673 | APOS : 672 | RPM :  23220 | Accel :   -2 | Mode : Normal
CPOS : 673 | APOS : 673 | RPM :  22860 | Accel :   -6 | Mode : Normal
CPOS : 675 | APOS : 675 | RPM :  22140 | Accel :   -5 | Mode : Normal


From 20000rpm to 30000rpm it should be in position 720-700 but it is in the 600-700 range. I don't know why.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on August 22, 2015, 03:23:47 PM
const unsigned int curve_rpm[5] = { 9000, 27000, 46000, 69000, 85000 };
unsigned int turbo_curve[5] = { 0,0,0,0,0 };

unsigned int can only goto 65535, https://www.arduino.cc/en/Reference/UnsignedInt

change int to long, if you want to go higher, for both.
Title: Re: HE351VE in a 4g63
Post by: Ryan on August 31, 2015, 08:12:24 AM
Update?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on September 01, 2015, 12:46:25 AM
Quote from: kapok6 on August 31, 2015, 08:12:24 AM
Update?

Making some minor changes to intercooler piping and adding a BOV. Car should be ready for this friday at the race track for some more testing.
Title: Re: HE351VE in a 4g63
Post by: Rx7man on September 01, 2015, 10:40:55 PM
Keep us posted :)
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on September 09, 2015, 02:42:46 AM
I changed int to long as instructed and turbo started opening and closing randomly at different rpm's. I changed them back and simply set the highest rpm to 65000 and it started to work properly again.

I am however having allot of trouble trying to control boost with the VGT. Even though I changed the setting to:
// TOP End Control Section
             if (performance_mode && turbo_rpm <= 75000) { vane_position = map(turbo_rpm, top_end_rpm, 76000, turbo_curve[4] + performance_position, 580); }
        else if (turbo_rpm <= 76000) { vane_position = map(turbo_rpm, top_end_rpm, 76000, turbo_curve[4], 600); }
        else if (turbo_rpm <= 77000) { vane_position = 400; }
        else if (turbo_rpm <= 77500) { vane_position = 340; }
        else if (turbo_rpm <= 78000) { vane_position = 240; }
        else if (turbo_rpm <= 78800) { vane_position = 180; }
        else { vane_position = map(turbo_rpm, 79000, 80000, 280, min_position); }
        if (turbo_rpm > 79000) { vane_position = min_position; }
        // Overrun protection
        if (turbo_rpm > 80000) { vane_position = 0; };

I still exceed it to the point of wastegate having to open at 17psi which is about 100000rpm. Here is the file I am using. Any help would be appreciated.
Title: Re: HE351VE in a 4g63
Post by: punisher454 on September 09, 2015, 09:36:24 PM
 I was just glancing at your code, I noticed a few posts back you had to change some constants to longs.
I'm new to Arduino, but with 2 other compilers I have previously used with AVR's there were sometimes problems mixing variable types (byte, int, long etc..). and do you have to put an "L" at the end of your numerical value if its to be used as a long or unsigned long? Maybe "75000UL" or something like that?
I'm probably way off, like I said I'm a Newbie to Arduino.

But Anyhow, I'm watching this thread with great interest.
Marvin
Title: Re: HE351VE in a 4g63
Post by: hakcenter on September 09, 2015, 11:05:10 PM
Do you have a log of the turbo running your current code ?
Title: Re: HE351VE in a 4g63
Post by: Rx7man on September 10, 2015, 09:00:48 PM
I think Marvin may have a good point, you need to specify that your literal is handled as a long.. .give it a try
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on September 12, 2015, 04:42:16 PM
Quote from: hakcenter on September 09, 2015, 11:05:10 PM
Do you have a log of the turbo running your current code ?

Here is a log. Remember my wastegate is opening at around the 90000-100,000 rpm mark. Otherwise i'm sure it would go further than 100,000 rpm's.

I'm sorry for the late reply. Did not make it to the track last week due to work.

@punisher454: I have no clue when it comes to the code. Curtis(hackcenter) does that for me. I just adjust the parameters as explained by him. Thank you for your input.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on September 15, 2015, 03:42:06 AM
This an older log ?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on September 15, 2015, 08:30:05 AM
Oops, yes it is. Will get another one tonight. Sorry.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on September 15, 2015, 01:27:31 PM
You may need to calibrate the controller on the turbo too seems like you can get just to to 100k @ max size
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on September 15, 2015, 01:52:08 PM
Quote from: hakcenter on September 15, 2015, 01:27:31 PM
You may need to calibrate the controller on the turbo too seems like you can get just to to 100k @ max size

The wastegate is opening up that's why.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on September 15, 2015, 07:03:20 PM
The waste gate won't make the turbo higher rpm. So either the calibration is wrong.. Or you can spin a 25cm^2 turbo
Title: Re: HE351VE in a 4g63
Post by: Rx7man on September 16, 2015, 05:55:58 PM
There is a possibility that it can spin a 25cm turbo once it gets up to boost, which would mean you still need a wastegate (or bigger turbo)  Rotary engines are notorious for being able to spool large turbos from a small displacement engine.. my buddy had one that put 875rwhp down at 48PSI (a 1.3L engine).. yes, it took it to about 6000RPM to get going, but then it was some kind of crazy, and I'm quite sure that would have had a 25cm housing.. it was about an 80mm compressor inlet.
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on September 16, 2015, 06:56:12 PM
Quote from: Rx7man on September 16, 2015, 05:55:58 PM
There is a possibility that it can spin a 25cm turbo once it gets up to boost, which would mean you still need a wastegate (or bigger turbo)  Rotary engines are notorious for being able to spool large turbos from a small displacement engine.. my buddy had one that put 875rwhp down at 48PSI (a 1.3L engine).. yes, it took it to about 6000RPM to get going, but then it was some kind of crazy, and I'm quite sure that would have had a 25cm housing.. it was about an 80mm compressor inlet.

I'm going to try recalibrating it as per Curtis' instructions and get another log with the two parameters changes to "Long."
Title: Re: HE351VE in a 4g63
Post by: hakcenter on September 16, 2015, 06:57:42 PM
This is a 4banger dsm motor.
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on September 16, 2015, 07:39:16 PM
Quote from: hakcenter on September 16, 2015, 06:57:42 PM
This is a 4banger dsm motor.

What are you trying to say? Lol
Title: Re: HE351VE in a 4g63
Post by: hakcenter on September 16, 2015, 07:53:06 PM
I used to own one, also I make speed density software for the entire 1g series. But that's another story for another life. I know about the platform to say the least.

Next time you're at the car and can program the LBB.

Goto the TIMER1 tab, and change

byte data[] = { lo_byte, hi_byte, 0x01, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF }; // data message with an added counter


to


byte data[] = { lo_byte, hi_byte, 0x02, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF }; // data message with an added counter


Key just to on, and listen to the turbo reset, usually (atleast on mine) it will actually turn off and stop responding.

Change the 0x02 back to 0x01, and reupload, key off / key on. Controller box should be re-centered and calibrated.
Title: Re: HE351VE in a 4g63
Post by: Ryan on September 29, 2015, 08:00:40 AM
Need moar updates.
Title: Re: HE351VE in a 4g63
Post by: Ryan on October 21, 2015, 09:31:15 AM
Is it safe to assume this all got worked out and the car is now running 9's in the 1/4?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on October 21, 2015, 10:06:33 AM
Lol. No. I took the car off the road. I'll be taking it to the dyno in the next week or 2. We'll find out what this thing can do. I'll take some videos and post the results.
Title: Re: HE351VE in a 4g63
Post by: Rx7man on October 21, 2015, 02:09:10 PM
Nice, look forward to it :)
Title: Re: HE351VE in a 4g63
Post by: 65fpvmustang on December 07, 2015, 05:48:11 PM
Hi i'm new i have been running a he351ve on a 2.3l lima (ford turbo coupe) in a 83 ranger for around 2 years now. Using a spring and pneumatic cylinder. I see .5 psi at 1500rpm 5 at 2500 rpm 10 to 12psi at 3000 and 26 psi around 4000rpm. all with exhaust pressure 3psi above boost. It will run 1 to 1 just about any where. above 12psi i can get boost 1psi above drive pressure. I plan to switch to electric control. The vans soot up on gasoline and don't want to open all the way after about a month of dd. I run mostly on lpg so it's a none issue.
I'm building a duplicate engine to replace the one i took out of my 65 mustang.

Somthing to think about is using shaft speed to limit boost. will provide more boost at lower engine rpm and less at higher engine rpm. as the engine breaths more with higher rpm the turbo shaft speed has to increase. to increase air flow maintaining boost pressure. this could be good if your pushing your fuel injector limits.
i have data logged turbo shaft speed at boost all the way to 33psi. if your interested.
Title: Re: HE351VE in a 4g63
Post by: Ryan on December 31, 2015, 05:33:15 AM
Update on DSM?
Title: Re: HE351VE in a 4g63
Post by: 65fpvmustang on January 12, 2016, 09:33:50 AM
watch your EBP to boost ratio when tuning.
once EBP is 6psi over boost I get what sounds like a miss.
But it is violent compressor surge.
It shows up in data log boost pressure drops then returns.
afr goes extra rich then comes back. Exhaust pressure falls also.
Above 14psi boost steady state should be running 1 to 1 or better.
Title: Re: HE351VE in a 4g63
Post by: Ryan on April 14, 2016, 08:08:24 AM
Did the dsm die?
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on May 30, 2016, 12:31:51 PM
DSM is still alive. Lol
Haven't really touched it in a few months due getting another car and our shops been very busy with customer projects as well. I will be changing the setup but keeping the turbo. Didn't get a chance to go to the Dyno but will right after the changes.

I also got another HE351VE to put into my new car which is an Evo 6 from Japan. Looks like it will be much easier to install into due to the turbo's facing the left side. Don't need to worry about controller clearing the block. I don't expect to finish this project any time soon though. The talon is first priority as it will be up for sale as soon as I'm finally done with it.
Title: Re: HE351VE in a 4g63
Post by: Ryan on August 25, 2016, 10:18:50 AM
Need moar updates!
Title: Re: HE351VE in a 4g63
Post by: EvoAuto on April 13, 2019, 06:09:38 PM
Back from the dead. I actually ended up selling the car to a friend who promised to keep the setup. Finally got it on dyno last night. Made 464whp at 24psi on a dyno dynamics dyno using e85. Graph and video on my Instagram @sourajtuned.  I didn't do too much with the vgt settings as I was on a time crunch.

It's on the old 1.1 firmware in performance mode map 1. I plan on updating the firmware as well as the hardware so that we can tune the Turbo on Android.

Btw this is using a wastegate for boost control. I have to start reading the documentation that Curtis provided to optimise it. Will keep updating as we go.
Title: Re: HE351VE in a 4g63
Post by: hakcenter on April 16, 2019, 07:39:01 AM
Very nice