Author Topic: Not Running to healthy  (Read 67946 times)

Offline Tony C

  • Hero Member
  • *****
  • Posts: 650
  • BHP: 8
    • Capriracing
Re: Not Running to healthy
« Reply #15 on: April 26, 2007, 09:01:30 pm »
yeah checked all of that mate. :(

Vems Ecu, Twin Plenum efi and N2o
13.314 @ 104.39 mph (10/06/07 3.9 v8)
Sponsored by: www.caprisport.com & www.interpart.biz
Web site: http://www.capriracing.co.uk

Vems Firmware: V1.1.74

Offline cliffb75

  • Global Moderator
  • Full Member
  • *****
  • Posts: 167
  • BHP: 10
Re: Not Running to healthy
« Reply #16 on: April 26, 2007, 09:22:59 pm »
You've tried changing the main reqfuel value too yeah?

Other than that could the injector earth (or earths) be shorting to ground somewhere - i.e. 100% duty cycle occurring

Anything in the VEMs driver setup that could cause this (Rob?)

 ???

Offline Agriv8

  • Full Member
  • ***
  • Posts: 145
  • BHP: 4
Re: Not Running to healthy
« Reply #17 on: April 26, 2007, 09:30:57 pm »
ok Air leaks ?

are all you readouts clean ( as expected ) what do your logs show ? not and expert but a different set of eyes ect.

what have you added to vems since ( extra inputs ect ) since  it was last running ?

checked your pins in the econoseal have you knocked one back ?

I'll keep the ideas flowing and hope that I am not insulting your inteligence but somtimes its the bleeding obvious that you miss ( my best to date when running under hotwire was AF the wrong way round  :o :o took nearly 2 weeks and I was ready to put a match to it )

regards

Agriv8

'The older I get the faster I was'

Offline Tony C

  • Hero Member
  • *****
  • Posts: 650
  • BHP: 8
    • Capriracing
Re: Not Running to healthy
« Reply #18 on: April 26, 2007, 09:45:12 pm »
the car was running prior to engine mods,
the battery and ecu was disconected for about 3 weeks,
whne every thing was fitted back up and we tried to start the car parts of the original map in the ecu was gone, values had reset to 0 but not all of them,
reason we found this out was car was running real sick and hardly idling, loaded the .msq file back up from laptop and it ran sweet,
did 30-40 miles the same day with out a hiccup,
following day this started.......
have changed plugs,
changed map settings  added latest firmware, sealed plenum 6 times but still naff all,
the car revs up real crisp, but no idle now, and is lumpy as hell and near stalls,
im near wits end with it now....

Vems Ecu, Twin Plenum efi and N2o
13.314 @ 104.39 mph (10/06/07 3.9 v8)
Sponsored by: www.caprisport.com & www.interpart.biz
Web site: http://www.capriracing.co.uk

Vems Firmware: V1.1.74

Offline Agriv8

  • Full Member
  • ***
  • Posts: 145
  • BHP: 4
Re: Not Running to healthy
« Reply #19 on: April 26, 2007, 10:25:45 pm »
MMMMmmmmm.

Tony just had a look at pictures on the web site.

good spark ? was the dizzi in use before upgrade ? i have head about problems with the condensers ? whats doing the actual switching of the coil.

loosing parts of the map thats a worry from a computer procesor point of view ( memory ) could it have also lost bits that megatune cant get to  ? I think we need to get a log realy.

going of to work  way to do that shortly.

regards

Agriv8
'The older I get the faster I was'

Offline Tony C

  • Hero Member
  • *****
  • Posts: 650
  • BHP: 8
    • Capriracing
Re: Not Running to healthy
« Reply #20 on: April 26, 2007, 10:30:30 pm »
getting a log would be ok if it didnt take ages to get it to at least run for a few seconds,
the dizzy is a mallory unilite electronic, and has been in the car since day one,
the coil is a mallory promaster which is fed by a mal685 unistrike cd ignition unit.
like i said all ran fine after the mods for one day
then the following day this

Vems Ecu, Twin Plenum efi and N2o
13.314 @ 104.39 mph (10/06/07 3.9 v8)
Sponsored by: www.caprisport.com & www.interpart.biz
Web site: http://www.capriracing.co.uk

Vems Firmware: V1.1.74

Offline Tony C

  • Hero Member
  • *****
  • Posts: 650
  • BHP: 8
    • Capriracing
Re: Not Running to healthy
« Reply #21 on: April 26, 2007, 10:33:02 pm »
could something of died? or be dying in the ecu?
my sponsors are getting edgy now and are asking questions as i have missed 2 race meeting so far and no hope of getting to this weekends one either

Vems Ecu, Twin Plenum efi and N2o
13.314 @ 104.39 mph (10/06/07 3.9 v8)
Sponsored by: www.caprisport.com & www.interpart.biz
Web site: http://www.capriracing.co.uk

Vems Firmware: V1.1.74

Offline Agriv8

  • Full Member
  • ***
  • Posts: 145
  • BHP: 4
Re: Not Running to healthy
« Reply #22 on: April 26, 2007, 11:05:01 pm »
Simple procesors ( like the vems ) are little computers

Info in ----> process ----> info out.

or as used in computing world

CICO = Crap In Crap Out

email me the config file you are using and ill take a look with a fesh set of eyes ill u2u my email addr .

regards

agriv8


'The older I get the faster I was'

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: Not Running to healthy
« Reply #23 on: April 26, 2007, 11:14:53 pm »
I've never heard of the maps getting wiped like that - but if the map got wiped then theres every likelyhood that the configuration would get mullered.

I dont understand how so much of this is moving about though - the split diaphram on the Mallory explained the MAP readings going to pot the way they did.

Last we spoke you'd upgraded to one of the newer firmware versions, can you tell me what version you're running at the moment?

Rob

Offline Tony C

  • Hero Member
  • *****
  • Posts: 650
  • BHP: 8
    • Capriracing
Re: Not Running to healthy
« Reply #24 on: April 26, 2007, 11:24:52 pm »
its the one i mailed you rob, 1.0.69
the diaphram never made a dent in the fault mate when we replaced it tonight,
it was the same as before we replaced it,
its got me beaten i dont mind admiting it,  ???
the annoying part is im £400 lighter due to the work over easter and its a non runner  :'( :'(

we are going to try and run it on open loop tomorrow afternoon to see if the wdeband has a fault,
i hope we can resolve this problem as i dont really want to go back to a 4bbrl carb  :-[

Vems Ecu, Twin Plenum efi and N2o
13.314 @ 104.39 mph (10/06/07 3.9 v8)
Sponsored by: www.caprisport.com & www.interpart.biz
Web site: http://www.capriracing.co.uk

Vems Firmware: V1.1.74

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: Not Running to healthy
« Reply #25 on: April 26, 2007, 11:34:45 pm »
Re-reading this...
And re-reading it again...
And checking the MSQ you sent to me on 8th April
Settings->Primary Trigger Settings

I have number of teeth on wheel = 35 which would give you some very funny rpm readings IIRC there should be 8 trigger teeth.

The Closed loop settings can only increase the fuel by 19% or 5%

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: Not Running to healthy
« Reply #26 on: April 26, 2007, 11:42:58 pm »
If I open that MSQ in Megatune from 1.0.69 it gives 25 warnings.

There can be problems if the firmware was upgraded using the msq's only.

Without datalogs theres no way I can see whats happening, and datalogging the startup is as important as anything else TBH.

Plan of action:

Set the teeth on wheel to 8 which should be correct.
Turn off closed loop closed loop wont be working before the lambda is upto temperature.

If all fails send me the ECU and I can test it on my test bench.

Offline Tony C

  • Hero Member
  • *****
  • Posts: 650
  • BHP: 8
    • Capriracing
Re: Not Running to healthy
« Reply #27 on: April 26, 2007, 11:55:24 pm »
will the trigger teeth effect it when im only doing fuel with the vems at mo mate?

Vems Ecu, Twin Plenum efi and N2o
13.314 @ 104.39 mph (10/06/07 3.9 v8)
Sponsored by: www.caprisport.com & www.interpart.biz
Web site: http://www.capriracing.co.uk

Vems Firmware: V1.1.74

Offline Tony C

  • Hero Member
  • *****
  • Posts: 650
  • BHP: 8
    • Capriracing
Re: Not Running to healthy
« Reply #28 on: April 26, 2007, 11:57:12 pm »
the .msq we got here has 2 warnings which we can't seem to get rid of,
we changed the settings in MT to correct the 25 warnings, which made no difference to the running,

Vems Ecu, Twin Plenum efi and N2o
13.314 @ 104.39 mph (10/06/07 3.9 v8)
Sponsored by: www.caprisport.com & www.interpart.biz
Web site: http://www.capriracing.co.uk

Vems Firmware: V1.1.74

Offline rob@vems.co.uk

  • Hero Member
  • *****
  • Posts: 3115
  • BHP: 49
    • VEMS Forum
Re: Not Running to healthy
« Reply #29 on: April 27, 2007, 12:51:26 am »
Right then I went and had a shower, nothing worse than being stressed AND dirty.

Lets approach this another way...
what we're interested in here is purely the pulsewidths of the injectors - as we know what they were when they were working well.

Looking at the datalog you sent me last year of your 13.435sec run we see that at idle you had pressures of 58kpa@843rpm and a injector PW of 3.1ms, to 48kpa@980rpm & PW of 2.6ms

In that datalog you sent where the MAP was briefly okay but rubbish for the rest of the time we saw: 41.3kpa@779rpm PW=3.1ms and 31kpa@487rpm PW2.4

The rest of the time VEMS was kicking out a PW of about 7.4ms which is way too rich.

So.

You suspect the MAP sensor or the VEMS :), I suspect anything but the VEMS (because I am biased ;D) so lets try and find some middle ground where we can do some experiments.

We can eliminate the MAP sensor by going to AlphaN, http://www.vems.co.uk/forum/index.php?topic=93.0
We know that your engine likes to idle at 850 to 950 rpm with PWs of 2.6 to 3.1
So save all your current settings.
Convert to AlphaN.  Set your first three RPM cells to 650, 850, 1050 and try to start the engine
watch the inejctor pulse width in the Tuning->VE Table screen and as you will be warming up you'll need to factor in the warm-up enrichment, you have 140%@15.5c and 110%@26.6 so if the weather is warmish tomorrow you should be looking for initial tick over PWs of 3.64 to 4.34 at around 15deg, dropping to 2.9 to 3.4 as it warms up.
This will effectively tell us that the VEMS is working correctly and injecting the fuel as it should.  From that we can decide the next course of action.