850rpm idle with the AC on is knock city for the Miata. Hence why the factory made the car idle around 1200rpm. Hence, incidentally, why i want mine to do the same.
For now i'll just go back to the stock AC-Idle up less code and set it to not come on at idle. |
your broken ass miata might idle up to 1200RPM, but that's not the norm.
and no, you're not going to knock at 850rpm with the a/c on. I do agree something is happening that shouldnt with your firmware, and it's worth figuring out what. Also, your clt temps shouldn't be dancing around so rapidly like that, that suggests a grounding problem. What lag factor is CLT/AIT set to? |
Ok. So, my car is borked. Sure. whatever you say. So you are telling me a stock 90 running the stock ecu does not go into high idle when the AC is on, but rather stays at 850rpm?
I'd rotfl, but i don't find it that funny. |
it raises from 850 to around 950. the stock ECU adds exactly 12% duty cycle to the valve when it engages the compressor.
your car still wont knock at 850RPM with the a/c engaged. |
Originally Posted by sparkstack
(Post 791545)
MSQ attached.
Also attached is a log from yesterday. Same settings just AC-Idle v5. I'll generate a new log tonight when i get out the office. Can't help you if you won't help you.... G |
Originally Posted by braineack
(Post 791622)
your car still wont knock at 850RPM with the a/c engaged.
So. assuming all other things being equal. I guess i have a broken ass tune around idle. Odd though that the v5 version of this mod worked so well for me. |
Originally Posted by gslender
(Post 791633)
Can't help you if you won't help you....
G So far your help has been along the lines of "not my problem buddy" so even if i provide a log showing what exactly is happening i doubt anything meaningful will come from you. |
Originally Posted by sparkstack
(Post 791565)
For now i'll just go back to the stock AC-Idle up less code and set it to not come on at idle.
|
Originally Posted by sparkstack
(Post 791634)
My car does, hence the high idle for AC. Hell it knocks if i put the hi-beams on. Though now i come to think of it, only with the diypnp.
hense why I said you have other issues to work out. :brain: |
Originally Posted by sparkstack
(Post 791638)
So far your help has been along the lines of "not my problem buddy" so even if i provide a log showing what exactly is happening i doubt anything meaningful will come from you.
Can you elaborate? The video didn't outline what specifically is not working. Also, what are your Output settings? How much help you get is up to you... I can't magically know what is wrong without data.... so best you do move on. |
Originally Posted by gslender
(Post 791641)
Hang on, you just told us before all was good in V5? There is little reason to go to V6 so what's the real story here?
I went to V6 because of the graceful off feature. I like the idea of that rather than just going out of closed loop and waiting for the PID idle to take over and i have to admit the graceful off part of this code seems to work very well. It's the "on" part that is giving me trouble. |
Disregard. I'm stupid.
|
Originally Posted by sparkstack
(Post 791663)
And your second post - without waiting for further data was:
#2 I'm also not the only person in the thread who is trying to help you but your attitude is getting in the way. #3 My question regarding the story is that most of what you've posted here is vague at best, contradicting, and you are incredibly argumentative. How about we start this again with a simple request - please post your MSQ and MSL with the firmware v6 and a clear description of the problem so that I (the person who wrote this mod) can appreciate your problem. If you don't do that, I'll happily ignore your posts. G |
Originally Posted by sparkstack
(Post 791663)
And your second post - without waiting for further data was:
and then, even after i tell you more data will come tonight you brush me off with: And please do not attribute fake quotes to me! The second quote, I never said anything to you in that tone! And the first quote where I suggested you make a separate thread for your specific issues...looks like I was right eh? Edit: oh I get it gslender said that 2nd quote...so how did the quote button put my name there :facepalm: |
Originally Posted by sparkstack
(Post 791565)
850rpm idle with the AC on is knock city for the Miata. Hence why the factory made the car idle around 1200rpm. Hence, incidentally, why i want mine to do the same.
For now i'll just go back to the stock AC-Idle up less code and set it to not come on at idle. |
Originally Posted by Greg G
(Post 789377)
The slight surge on AC disengagement is due to my high D reacting to the idle duty dropping. Will tune that out.
|
4 Attachment(s)
Ok,
Attached are the logs from two short runs. First with the V5 code. The second with the V6 code. The tune is the same as the one posted earlier. I also took video of the runs, so you can see what is happening. First, V5. Next, V6. |
Originally Posted by Braineack
(Post 791651)
hense why I said you have other issues to work out.
Originally Posted by bearda
(Post 791763)
If you're knocking when you increase load at idle you have a problem with those cells. From your video you look a little lean and your timing looks a little high around idle. Get things running right and you shouldn't have knock ANYWHERE on the load/rpm spectrum.
Originally Posted by gslender
(Post 791683)
#1 I'm not Greg G.
Originally Posted by gslender
(Post 791683)
#3 My question regarding the story is that most of what you've posted here is vague at best, contradicting, and you are incredibly argumentative.
Originally Posted by gslender
(Post 791683)
How about we start this again with a simple request - please post your MSQ and MSL with the firmware v6 and a clear description of the problem so that I (the person who wrote this mod) can appreciate your problem.
|
4 Attachment(s)
OK. I'm back.
Everyone said my tune sucked.. :idea: so based on the comment above from bearda i revisited the idle section. Reduced the timing down to 10 (from 17 (which was what i was advised to set it to somewhere else...) and adjusted the idle bypass screw some more. Now i have a steady(ish) 800rpm idle. I also adjusted my settings such that now the V6 code works. :facepalm: Short datalog and the msq file attached. I still see some oscillation when in AC idle which i need to tune out (pointers appreciated) but the code does indeed work. Apologies all round for jumping the gun. I'll take my tuning questions to a different thread. |
Originally Posted by sparkstack
(Post 791883)
OK. I'm back.
Everyone said my tune sucked.. :idea: so based on the comment above from bearda i revisited the idle section. Reduced the timing down to 10 (from 17 (which was what i was advised to set it to somewhere else...) and adjusted the idle bypass screw some more. Now i have a steady(ish) 800rpm idle. I also adjusted my settings such that now the V6 code works. :facepalm: Short datalog and the msq file attached. I still see some oscillation when in AC idle which i need to tune out (pointers appreciated) but the code does indeed work. Apologies all round for jumping the gun. I'll take my tuning questions to a different thread. I've got some improvements for v7 that should improve decel dashpotadder which doubles up the AC adder, which your issue was showing. You were actually jumping from pid and into decel routines, which the dashpotadder code plays into, which is why it was jumping up - so whilst that is a bug, you shouldn't really have that problem and where you are heading with a stable 850 idle and 950 with AC is the go. Cheers, G |
All times are GMT -4. The time now is 11:41 PM. |
© 2024 MH Sub I, LLC dba Internet Brands