log WGDC in EvoScan
Mar 24, 2007 | 09:18 PM
#31
Thanks jcsb. I wish I could take full credit, but I started with a Vishnu flash. I just made some changes to suit my preferences and try to improve upon it. Since I did start with a Vishnu flash, I'm not sure I should post the actual maps even though they are now somewhat different than the Vishnu values. However, I figure its fair enough to say that that the posted WGDC curve is not too different than what I programmed into the MWGDC tables. :-)
Mar 25, 2007 | 09:35 AM
#33
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 130
From: Tri-Cities, WA // Portland, OR
In my case, I'm using what Shiv calls a "passive solenoid emulator" which is nothing more than an inline bleeder that goes in place of the OEM restrictor pill and reduces line pressure by venting air to atmosphere. It creates lots of headroom for creating a WGDC curve that can give a flat boost response.
Mar 25, 2007 | 01:09 PM
#35
Newbie
Joined: May 2006
Posts: 28
Likes: 0
From: Uk
Didn't work? What numbers did it give? Whilst I'd looked for these previously and failed, what Bez has found looks to be the hardware ports, and the req85 appears to be the equivalent to 86...
They will of course log different values, but not the values from the tables, what the actual solenoids are running.
I really thought this was it:
They will of course log different values, but not the values from the tables, what the actual solenoids are running.
I really thought this was it:
I've put the standard restrictors back in again and will recheck it asap.
I recon you could be right about the induction making the maf read low as that would explain the extra boost, exellent power and nice fuelling from his first rr run, it may also explain why it was so rich this time round as if it was reading low the timing would also be further advanced than it should be so may have been causing some knock, hence retarding the timing and richening the fuelling.
Last edited by Ducks; Mar 25, 2007 at 01:16 PM.
Mar 26, 2007 | 11:38 AM
#37
Newbie
Joined: Jan 2005
Posts: 62
Likes: 0
When using mitsulogger to log the WGDC, I get a max value of 78.43 way before my WGDC map hits 100%
Anybody else notice this?
I also edited the mitsulogger definition file for DLL to support seeing the WGDC
Anybody else notice this?
I also edited the mitsulogger definition file for DLL to support seeing the WGDC
Code:
[Column] Name=WGDC Description=Waste Gate Duty Cycle ColumnTitle=WGDC DataItemID=10 Type=1 ColumnDecimalPlaces=2 DisplayDecimalPlaces=2
Mar 27, 2007 | 11:33 AM
#38
Newbie
Joined: Jan 2005
Posts: 62
Likes: 0
Ok, I just found out that the value 78.43 is the maximum value, so I modifed mitsulogger's requestid.xml and divided by .7843, which now shows up as the WGDC in percent which matches exactly with what ecuflash is set to when the Boost Error Control is zeroed out.
Code:
<Request LogReference="WGDC" RequestID="86" Eval="(x*100/255)/.7843" Unit="%" Response="2" />
Last edited by turbotiger; Mar 27, 2007 at 12:23 PM.
Mar 27, 2007 | 11:51 AM
#39
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 130
From: Tri-Cities, WA // Portland, OR
Ok, I just found out that the value 78.43 is the maximum value, so I modifed mitsulogger's requestid.xml and divided by .7843, which now shows up as the WGDC in percent which matches exactly with what ecuflash is set to when the Boost Error Control is zeroed out.
Code:
<Request LogReference="WGDC" RequestID="86" Eval="(x*100/255).7843" Unit="%" Response="2" />
Mar 27, 2007 | 02:51 PM
#43
Newbie
Joined: Jan 2005
Posts: 62
Likes: 0
I made a typo in my earlier post, it's now corrected for the eval formula. Your quote had the / omitted.
