SManager 2.2.4
Re: SManager 2.2.3 (beta)
We will test this fully tomorrow and see if there is a software issue.
Re: SManager 2.2.3 (beta)
ok, let us know the results. thanks
Re: SManager 2.2.3 (beta)
is the 2.2.4 beta supposed to correct the problems that i have reported earlier? i'm having the exact same problems.Hondata wrote:It was a problem; we have fixed it now & will re-release shortly.
just to remember
under closed loop:
- Max Engine Speed - Can't set it for more than 8000rpm just keeps reverting to 8000 when I do the tab.
- Closed Loop Max TPS (Low) & (High) - I tryed to set max rpm to more than 8000 and it doesn't let me.
- Closed Loop Max TPS (Low) & (High) - I set 100% to TPS %, but only assumes 99%.
And just a doubt regarding tip-in retard conditions, does both conditions need to be meet, for the retard occur, or just one of them? for example, if i'm in 2nd gear, at 5000rpm doing 50km/h, and i have set for the tip-in, vehicle speed min. 10 max. 140 and engine speed min. 1000 max. 4500, will the retard occur or not?
Re: SManager 2.2.4 (beta)
The internal limit of the ECU is 8000 rpm for some parameters. If the highest rpm index for the maximum TPS for closed loop is 8000 rpm this does not mean that closed loop is limited to 8000 rpm - it just is the highest value of the index.
As for the tip in parameters, both conditions need to be met.
As for the tip in parameters, both conditions need to be met.
Hondata
Re: SManager 2.2.4 (beta)
Ok so let me see if I get this straight, although I can't set more than 8000 on max engine speed and on Closed Loop Max TPS, it will maintain the closed loop condition up to 9000 p.e.? based on what condition? map sensor?Hondata wrote:The internal limit of the ECU is 8000 rpm for some parameters. If the highest rpm index for the maximum TPS for closed loop is 8000 rpm this does not mean that closed loop is limited to 8000 rpm - it just is the highest value of the index.
As for the tip in parameters, both conditions need to be met.
And how about the % off TPS? will it also maintain the closed loop condition when it's set to 99% in the table, but it reads 100%?
Re: SManager 2.2.4 (beta)
If the last index of the table is 8000 rpm then it will just use the last table value no matter what the rpm goes up to.
The 99% TPS is another internal ECU thing. It will work the same as 100% (that at least is in the help file).
The 99% TPS is another internal ECU thing. It will work the same as 100% (that at least is in the help file).
Hondata
Re: SManager 2.2.4 (beta)
thank you for the clarification.Hondata wrote:If the last index of the table is 8000 rpm then it will just use the last table value no matter what the rpm goes up to.
The 99% TPS is another internal ECU thing. It will work the same as 100% (that at least is in the help file).
Re: SManager 2.2.4 (beta)
have you fixed the output test function this feature seems like it will be really handy.
Re: SManager 2.2.4 (beta)
The output functions have worked since they were introduced. You must have real-time update turned on.
-
- Posts: 116
- Joined: Tue Jun 23, 2009 10:51 pm
Re: SManager 2.2.4 (beta)
i have a problem with boost control, when im in full boost it show 0 or 1% pwm which suppose to be at 50%, it explain more in the datalog... thanks
- Attachments
-
- Mini Me boosted.skl
- calibration
- (42.47 KiB) Downloaded 173 times
-
- pwm.s3d
- datalog
- (95.99 KiB) Downloaded 168 times
-
- Posts: 116
- Joined: Tue Jun 23, 2009 10:51 pm
Re: SManager 2.2.4 (beta)
Anybody out there...allm0t0rGSR wrote:i have a problem with boost control, when im in full boost it show 0 or 1% pwm which suppose to be at 50%, it explain more in the datalog... thanks
Everything was working before I updated mine to 2.2.4. Thanks
Re: SManager 2.2.4 (beta)
Why do you have throttle position compensation set to 50%? try setting those back to default settings.
Re: SManager 2.2.4 (beta)
i tried turning real time update on i still couldnt get it to work... im not a noob we tune a lot of hondata cars. when i check the box should the solenoid start to pulse instantly?
Re: SManager 2.2.4 (beta)
Turn of the variable frequency in the calibration and the test function should work