MS2/Extra 2.0 beta 14 (20071020)
Moderators: jsmcortina, muythaibxr
-
- Helpful MS/Extra'er
- Posts: 122
- Joined: Tue May 29, 2007 7:23 pm
I should have some time tomorrow to test this out again. Sorry If I make no sense I am still a newbie to tuning and overlook simple things like this sometimes. To me it just seemed my VE wouldn't be off that much, I've got it down pretty good in beta 8 oh well....
Is there any real reason to go to beta 14 from 8 if I like how the car is running? Any other serious bugs resolved since then?
-Chris
Is there any real reason to go to beta 14 from 8 if I like how the car is running? Any other serious bugs resolved since then?
-Chris
Chris -
One thing worth mentioning is that somewhere along the road VE calculations or something were altered because users going from a 2.5 bar to 4.0 bar map sensor were having issues with the fuel table - then, a later release came out that allowed better migration from one sensor to the other - I am not sure which version this entails, but it's something to remember. I'd say move to the latest beta's not because your car doesn't run but so we can test the code
One thing worth mentioning is that somewhere along the road VE calculations or something were altered because users going from a 2.5 bar to 4.0 bar map sensor were having issues with the fuel table - then, a later release came out that allowed better migration from one sensor to the other - I am not sure which version this entails, but it's something to remember. I'd say move to the latest beta's not because your car doesn't run but so we can test the code
1992 BMW 525i M50 Non Vanos 24v Turbocharged
Stock COP Wasted Spark
MS2/E v3
Stock COP Wasted Spark
MS2/E v3
-
- Site Admin
- Posts: 8230
- Joined: Thu Oct 14, 2004 12:48 pm
I think the thing you're talking about here was MS1...Jon k wrote:Chris -
One thing worth mentioning is that somewhere along the road VE calculations or something were altered because users going from a 2.5 bar to 4.0 bar map sensor were having issues with the fuel table - then, a later release came out that allowed better migration from one sensor to the other - I am not sure which version this entails, but it's something to remember. I'd say move to the latest beta's not because your car doesn't run but so we can test the code
The old code was squirting 2x more than it should, and it was doing so unevenly... The engine may run better now that the code is working correctly.
Ken
Crap that might be - I am trying my hardest not to confuse the MS1/MS2 cars I work onmuythaibxr wrote:
I think the thing you're talking about here was MS1...
The old code was squirting 2x more than it should, and it was doing so unevenly... The engine may run better now that the code is working correctly.
Ken
1992 BMW 525i M50 Non Vanos 24v Turbocharged
Stock COP Wasted Spark
MS2/E v3
Stock COP Wasted Spark
MS2/E v3
-
- Helpful MS/Extra'er
- Posts: 122
- Joined: Tue May 29, 2007 7:23 pm
-
- Super MS/Extra'er
- Posts: 1331
- Joined: Mon May 21, 2007 8:36 am
-
- Super MS/Extra'er
- Posts: 1933
- Joined: Fri May 07, 2004 12:59 pm
- Location: Tacoma, WA
- Contact:
-
- Site Admin
- Posts: 8230
- Joined: Thu Oct 14, 2004 12:48 pm
Yeah, I'm going to work on that a bit more tonight. Basically the stepper I have is very unreliable unless it's "always on."
I think this is because there needs to be a short delay between turning on the stepper controller and actually trying to make the motor move, so I'm going to try adding that.
Once I get it working the way I think it should, I'll add the ability to control it to my PID algorithm.
Ken
I think this is because there needs to be a short delay between turning on the stepper controller and actually trying to make the motor move, so I'm going to try adding that.
Once I get it working the way I think it should, I'll add the ability to control it to my PID algorithm.
Ken
If i can help, on my code (with a pic) i've not done anything strange, and the stepper move well with both 'always on' and 'move only'.muythaibxr wrote:Yeah, I'm going to work on that a bit more tonight. Basically the stepper I have is very unreliable unless it's "always on."
I think this is because there needs to be a short delay between turning on the stepper controller and actually trying to make the motor move, so I'm going to try adding that.
Once I get it working the way I think it should, I'll add the ability to control it to my PID algorithm.
Ken
I've tryied it hundred of times, forth and back, and it not loose one step...
No delay moving the stepper, as it's already slow itself :-p
I've found that with the right step time it move well in every condition...
Enrico
Opel/Vauxhall Corsa GSi MS2
Subaru v4 EJ20 MS3
Opel/Vauxhall Corsa GSi MS2
Subaru v4 EJ20 MS3
-
- Site Admin
- Posts: 8230
- Joined: Thu Oct 14, 2004 12:48 pm
muythaibxr wrote:The delay I'm talking about isn't going to be noticable really... like 5 ms or so (user configurable) between when the code turns on the stepper controller, and the pins to control the motor are toggled.
Ok, but i've not needed any pause doing my experiments...
With the pic i've bit bang-ed the outputs, this is the piece of code that i use:
if (Phase1 == 0 && Phase2 == 0) {
Phase1 = 1;
Phase2 = 0;
} else if (Phase1 == 0 && Phase2 == 1) {
Phase1 = 0;
Phase2 = 0;
} else if (Phase1 == 1 && Phase2 == 0) {
Phase1 = 1;
Phase2 = 1;
} else if (Phase1 == 1 && Phase2 == 1) {
Phase1 = 0;
Phase2 = 1;
}
//enable the stepper chip
IACDis = 0;
As you can see, i first set the right step (directly configuring the pin outputs), then enabling the IACDis pin, with no troubles in the moving of the stepper... This routine is valid with MoveOnly, AlwaysOn and 15Minutes IAC... If there is no more moviment to do, the iacdis is disabled...
I not think that you need some time between the stepper enable and the relative moviment... Probably the problem is elsewhere...
Whoo, i've tryied to take a look at the ms2 extra code... The little c that i know not help me to understand that!
Enrico
Opel/Vauxhall Corsa GSi MS2
Subaru v4 EJ20 MS3
Opel/Vauxhall Corsa GSi MS2
Subaru v4 EJ20 MS3
-
- Site Admin
- Posts: 8230
- Joined: Thu Oct 14, 2004 12:48 pm
-
- Super MS/Extra'er
- Posts: 1933
- Joined: Fri May 07, 2004 12:59 pm
- Location: Tacoma, WA
- Contact:
Seems to me, there's a setting in there (I don't have MT handy at the moment) that sets the time per step.. It's very important to have it right for your particular stepper. I know I read that the Chrysler ones take a longer step than Chevy ones.. Maybe that's the case with yours as well?
I say mine doesn't work right, you tell me it's my settings or wiring. Yours doesn't work, you start re-writing code.. hehe.. You sure you set it right? Just givin ya a hard time.. ;)
I say mine doesn't work right, you tell me it's my settings or wiring. Yours doesn't work, you start re-writing code.. hehe.. You sure you set it right? Just givin ya a hard time.. ;)
Brian
'84 Dodge Rampage
'84 Dodge Rampage
Have you already tryied with 15min iac?muythaibxr wrote:I think it probably depends on the stepper.
Ken
As some steppers need to warm up before can go in 'move only'.
I've triyed my code with 3 types of stepper, and on everyone of them the code was working... One of them was also an unipolar wired leaving the center tap unconnected.
Probably if in 'always on' it's working, the step time it's right, but also with move only, while the stepper is moving (like when trying to get the rest position), the iacdis is always 'disabled' (enabling the current at the coil).
while thestepper is moving, i leave the iacdis disabled, and only when i'm sure that there are not more steps to do i enable it... so while is moving, it's acting like an 'always on'. you are doing the same, or every step completed you enable the iacdis then re-disable it for the next step every time?
Enrico
Opel/Vauxhall Corsa GSi MS2
Subaru v4 EJ20 MS3
Opel/Vauxhall Corsa GSi MS2
Subaru v4 EJ20 MS3
-
- Site Admin
- Posts: 8230
- Joined: Thu Oct 14, 2004 12:48 pm
I tried values between 2.5 and 30 ms. None work reliably unless in the always on mode.UnaClocker wrote:Seems to me, there's a setting in there (I don't have MT handy at the moment) that sets the time per step.. It's very important to have it right for your particular stepper. I know I read that the Chrysler ones take a longer step than Chevy ones.. Maybe that's the case with yours as well?
I say mine doesn't work right, you tell me it's my settings or wiring. Yours doesn't work, you start re-writing code.. hehe.. You sure you set it right? Just givin ya a hard time.. ;)
-
- Super MS/Extra'er
- Posts: 1933
- Joined: Fri May 07, 2004 12:59 pm
- Location: Tacoma, WA
- Contact:
I'm unable to use this firmware, I get the following error:
ERROR: Stack pointer out of range, e=0xE3
I've installed the release version okay, are there further hardware mods that need to be made?
<edit>
scratch that, I answered "yes" to the are you upgrading from regular MS2 and it went through okay.
ERROR: Stack pointer out of range, e=0xE3
I've installed the release version okay, are there further hardware mods that need to be made?
<edit>
scratch that, I answered "yes" to the are you upgrading from regular MS2 and it went through okay.
If I had six hours to chop down a tree, I'd spend the first four hours sharpening the axe.
-
- Site Admin
- Posts: 8230
- Joined: Thu Oct 14, 2004 12:48 pm
I think my motor is one of those that requires jumpering around the current-limit resistors on the ms2.
Instead I'll just put a heatsink on the stepper driver, and develop the closed-loop code in that mode. I'll probably start working on it today (I'm away from home, but have my laptop) and hopefully test it tonight when I get home.
Ken
Instead I'll just put a heatsink on the stepper driver, and develop the closed-loop code in that mode. I'll probably start working on it today (I'm away from home, but have my laptop) and hopefully test it tonight when I get home.
Ken