VEMS Community Forum

I'm well underway towards the initial start-up on my project 1969 Camaro, and have started configuring and testing the ECU.

General project details can be found at the following link:

http://www.vems.hu/wiki/index.php?page=MembersPage%2FMTRacing (http://www.vems.hu/wiki/index.php?page=MembersPage%2FMTRacing)

I have uploaded firmware version 1.0.73 with the matched MegaTune version and have started modifying a borrowed configuration as a base line. I will post questions for specific areas as I move along and tweak each area.  The following are links to the initial config.txt and tables.txt files being used:

http://scirocco.dhs.org/cheapassron/MT/config.txt (http://scirocco.dhs.org/cheapassron/MT/config.txt)
http://scirocco.dhs.org/cheapassron/MT/tables.txt (http://scirocco.dhs.org/cheapassron/MT/tables.txt)

I've been able to connnect to the VEMS and can see initial readings for voltage, CLT, MAT, MAP, EGT and TPS but do not see a RPM signal when cranking.

I'm using an Electromotive 60-2 VR crank trigger and can read a clean 1.2 Vpp sign wave on my scope at the ECU connector when cranking. Using the mlp01 command, I'm not seeing any feedback or errors and MegaTune does not show an RPM reading. VEMS acts as if the crank trigger is not connected.

I'm using a VEMS factory V-8  harness and can also control the fuel pump, fans and water pump so I'm not inclined to think the P259 chip is bad.

The ultimate goal and plan for the car is COP and sequential injection.  The firing order is 1 8 4 3 6 5 7 2 and I'm using a Hall cam sync signal.

I've followed Rob's suggestions from the wiki site and need to know what to look at next. Any ideas or setting changes to get me closer?

Thanks,

Mike

Most likely you'll need a different VR sensor. With smaller than stock wheels, most VR sensors don't want to give signal suitable for VEMS. You should try Ford VR sensr that is from Galaxy 2.0 85kW. It's tested to work well on small(ish) size 60-2 trigger wheels.

Are you using the cam trigger yet?  Try turning it off and configuring for wasted spark using just the crank trigger as a test to isolate the two triggers if you haven't done so already.

Hi all,

I've been helping Mike on this project.  It's getting frustrating as we've been led to believe that what's installed *should* work or at least generate errors...but we get no sign that a trigger is even connected.

Here's the trigger setup:
(http://scirocco.dhs.org/cheapassron/mt/P1010215a.JPG)

Here's the waveform:
(http://scirocco.dhs.org/cheapassron/mt/P1010207a.JPG)

And just for fun, we're safe trying anything since we made up these cool litter testerators:
(http://scirocco.dhs.org/cheapassron/mt/P1010200a.JPG)

Is that a good waveform?  If not what does VEMS need vs what we have?

Thx in advance,

Ron

Looking at the config you have it looks pretty much right, although you have:
primary_trigger=02 and the other primary_trigger=01
Which may cause an issue - BUT if the VEMS sees any trigger signal it will prime the fuel pump ready so that when the crank signal is synchronised it will be able to start injecting with a good pressure.

So that suggests that the trigger is 'deaf', so the next test will be to stimulate it with signal, I've setup a signalgen file to simulate a 60-2 trigger starting at 200 rpm, moving to 1000 rpm, sweeping up to 7500 down to 1000 and back to 7500.
Download and unzip this:
http://www.vems.co.uk/VEMSTrigger/60-2SigGen.zip
Then you'll need to wire a audio plug from the PC speakers or laptop to the crank sensor input directly - make sure that the signal goes to the signal pin, but that the ground goes to the ground cluster.

Did you try switching to coil-type to see ifit registers rpm (though not correct)? If it shows rpm, then go and buy that VR sensor that I mentioned earlier in this thread.

I'll spend some time on it after work tonight and will report back what I find out.

Thanks!

Mike

OK, status as of today:

- Changed primary_trigger to 1 (no change)
- Changed Primary Trigger Settings Type to Coil (no change)
- Ran signalgen.exe from Rob, saw trigger errors but no RPM.  Noted intermittend flashing of injector test LEDs.  Changed polarity of trigger signal, saw no errors, RPM signal, or flashing LEDs).
- Inspected VEMS genboard V3.3, noted R30 is present.  This conflicts with instructions on the wiki (http://www.vems.hu/wiki/index.php?page=GenBoard%2FManual%2FInputTriggerHardWare (http://www.vems.hu/wiki/index.php?page=GenBoard%2FManual%2FInputTriggerHardWare)

Have photos of the board if needed.

Also, noted the board is labeled V3.3 on the topside, but V3.4 on the bottom?  Is this normal/important?

Your help is greatly appreciated.

Thanks,

Mike

Remove R30.

Yep ,

remove R30,

I have also just had a board were if was soldered in place..


/Skassa

Update 4-5-09

Removed R30, still no signal when cranked using either multi-tooth or coil type settings.

Connected signal generator from PC and saw erratic RPM readings on MegaTune (jumps) when the volume was nearly at max level and set to coil type, rising edge and standard polarity (+  to + and - to -). No readings when polarity is reversed.

No trigger errors were displayed on MegaTune during the test.

Test LEDs for most injectors would occasionally flash but cylinders 1, 2 and 3 don't seem to flash at all. No coil LEDs would flash.

Changed settings in table h[2] labeled "settings that has to be 0" to IGN

Test LEDs for most coils began to flash intermittently but cylinders 7 and 4 never seem to flash.

The MegaTune manual indicates that a small amplifier is needed to generate enough voltage for a VR test.  Is this the same requirement to test VEMS correctly and possibly eliminate the erratic/intermittent readings and outputs?

Any additional tests or settings to check?

What else needs to be done to rule out a hardware problem with my ECU?

If I'll need a different VR sensor, any recommendations (make and model of car found in the U.S. or part number) that will fit in my mount that has a 1/2" ID hole?

Does anyone have a known working configuration for a V-8 that is close to my configuration that I can use as a better base line to build from?

Ideally, I'd like to post all of the particulars of my engine, EFI configuration and wiring and then download the custom config.txt and tables.txt that would maximize my configuration and fine tune from that point.

Any and all help would be appreciated as my wife's patience is wearing thin with me and the project!

Thanks,

Mike

Rob,

Any ideas / feedback on this situation?

Thanks in advance!

Mike

When I test using the signal gen I do it through an amplified pair of speakers and usually need it up at 3/4 volume.

As you are seeing erratic RPM with the signalgen its showing more activity than with the crank sensor.

I've never had any problems using a Magnetti Marelli SEN-8D sensor but I dont know if they'll be common in the US.  I've also used stock Ford so any thing in the scrap yard that has 36-1 using EDIS or newer should work.

Can you move the sensor so that its closer to the trigger wheel?  We had someone with no RPM the other day and they found that the guy who assembled the engine had used too great a gap between the sensor and the trigger.

First I would like to say HELLO EVERYBODY my name is Richard! It's my first post here :)

MTracing I had similar problem to your,and after hours spent on searching in the internet and playing with scope,i removed R30,R57 and put short instead of C31.That cured all of my triggering problems.Hope it will help to you.

cheers Richard

Thanks, with first posts like that you're welcome here ;D

Thanks guys!  I'll try these changes over the weekend and report back.

Take care.

Mike

Some updates:

Last night Mike and I grabbed the scope and chased the PC synthesized 60-2 waveform from the laptop headphone jack all the way to the LM1815. 

Result:  the output of the LM1815 (pin 10 (late note: I was checking Pin 10 based on the LM1815's datasheet, now that I found the V3.3 schematic I see I should have chosen pin 12..doh)) can be seen here (signal looks overdriven but that's a result of the camera's exposure settings...still, 2Vpp clearly visible)  (http://scirocco.dhs.org/cheapassron/mt/4-18-09%20pics/MT%20at%20LM1815%20pin%2010%20out%20small.JPG)

Some notes:
- Found a bad RCA patch cable was attenuating the waveform from the laptop to the VR sensor cable.  Replaced it.  Now, Megatune shows an erratic RPM only when the PC volume is way low, like at 2/10 or so.  Above that, RPM reads 25550 with no ign or inj LED activity.

If anyone can offer any input regarding the components on the board, there are some high res pics here:
http://scirocco.dhs.org/cheapassron/mt/4-18-09%20pics/

Hypothesis: I think we have a config problem!  Why?  Because with the input amplitude very low, the LM1815 output wigs out (erratic output on pin 10), and the VEMS processor reacts accordingly by firing inj and ign outputs in some related sequence...so a signal is getting there...now onto telling the processor how to handle it correctly...

Observations, comments, redirects, etc all very welcome.

Thx for the continued support,

Ron
(MT's helper boy)

Quote from: ryniobl on April 17, 2009, 03:53:45 PM
...i removed R30,R57 and put short instead of C31.That cured all of my triggering problems....

Thanks - this eliminates the one-shot circuit, right?  (and the VR pullup).  How did your pin 12 signal look before and after this?

Thx

Ron

Okay, try this:

http://www.vems.co.uk/VEMSInstalls/VemsMT1.0.73.60-2.zip

It works fine on a 60-2 trigger, its 4-cylinder though, but good for cranking tests.
Download the firmware AND the configs and tables from here in the usual way, then test.  It might be an idea if it works to extend it to work on an 8cylinder, and to patch your wideband setup, required fuel etc.

Good luck

Rob

Here's where we got last night:

- After borrowing a known good VEMS with a known good 60-2 config, we determined that the hardware was OK.  Got the same results on both units after transferring config and tables to Mike's unit. 

- Both triggered fine when driven by the Signal Gen program.

- Neither triggered when we cranked the engine (Electromotive VR sender and wheel, 1.2Vpp sine-ish wave output, measured at the ECU).

Noticed odd DC bias on the EC36 pin for Trigger 01, 2.8VDC on Mike's unit (with nothing connected and with VR connected), compared to ~.5Vpp on the borrowed unit...was wondering if this is preventing a 0V crossover thus no LM1815 output???  (Odd that when inputting the Signal Gen waveform, the signal crossed 0V therefore no DC bias - the PC was probably forcing the issue).  Is this a red herring?

We won't get to work on it for a week or so but could try a few caps to absorb the DC voltage.  Or go to a VW sender as recommended by GRMRacer and others....

More thoughts welcome!

Ron
helper boy

Using a cap to filter DC is not good as the signal will get screwed, the changing frequency of the trigger will make stable triggering impossible.

A slight pull-up on the VR input is not unusual with noisy triggers we usually increase the pull-up voltage, you are seeing a negative voltage on that line when you 'scope it don't you?

No, on Mike's unit the whole wave is above 0V.  The borrowed unit (Brian's) has less of a DC bias, but we saw no triggering with it either.  I'd have guessed that it'd cross 0V, but we didn't scope it. 

BTW since we got the borrowed unit, we went with the proven config in it vs following the letter of your suggestion above.  We had that on tap but ran out of time.  I figure we got the gist of it though.

Thx again,

Ron

Mike sourced another VR sensor (spec'd for mid-90's VW Jetta III, ABA block), got 2Vpp and and a nice looking waveform, but no triggering on his unit.

Next steps are to run the same test with the borrowed unit, then (depending on the result), run a 'cheater' cable to provide the signal to the ECU but bypassing the premade harness.

Seems the DC bias may be an issue after all.

Will keep posting updates for posterity.

Ron

Things weren't making sense.  Both the borrowed unit and Mikes would trigger just fine on the new config and PC speaker synthesized .wav file input, neither would work with Electromotive or VW sensor.  So we went back to basics and created a cheater wire that bypassed the entire harness supplied with the unit.

Presto, signal.

Dissected the harness a bit and found what I think is some very questionable wiring, in that the VR signal (-) and shield were one and the same.  Therefore, either VR sender was hooked up to a wire going nowhere.  Look closely at pic, the black and blue wires are cut off flush.  Maybe it rang out OK because the shield contacted the cut-off wire?  Just a guess, but it did ohm out fine, hence the head scratching.

Why it worked with the PC speaker and not the VR sender I have no idea.

(http://scirocco.dhs.org/cheapassron/MT/P1010352a.JPG)

We'll get that mess cleaned up and begin configuring!

Thanks for all the help so far,

Ron

That's good, but exercise caution, while I've never been over happy with the shield being the negative wire its never been a problem before.  And make sure that you tie the grounds in correctly - the signal ground is connected to the ground cluster directly through that shield.

Shielding connected to signal ground is common practice on OEM vehicles. But of course they must end in a wire going to sensor ground on the ECU. Ending nowhere is no good :)

UPDATE:

After reworking the factory VEMS harness to connect the ground wires with the shield wires at the ECU end, it seems to have solved the problem! VEMS can see the crank trigger signal and I'm getting an RPM reading on Megatune.

I'm moving on configuring the injectors and coils. Look for a post soon.

Thanks for all of your help!

Mike

Quote from: ryniobl on April 17, 2009, 03:53:45 PM
First I would like to say HELLO EVERYBODY my name is Richard! It's my first post here :)

MTracing I had similar problem to your,and after hours spent on searching in the internet and playing with scope,i removed R30,R57 and put short instead of C31.That cured all of my triggering problems.Hope it will help to you.

cheers Richard

Apologies for digging up an old thread, but what does R57 and C31 do?  The wiki only had us remove R30 for v3.3 primary VR, but didn't mention the next 2...

They set the timing (pulse width) for the rpm output of the LM1815 (U11) Variable Reluctance Amplifier chip, what's called an RC timing circuit in electronics.  The LM1815 filters the VR signal then sends clean pulses to the Atmel microcontroller.  So basically, the RC combination sets the length of the pulse that the Atmel microcontroller sees for every tooth of the crank wheel.

According to the LM1815 datasheet, the output pulse width is:
PW = 0.673 x R x C

Which means in the schematic:
PW = 0.673 x 75kΩ x 1nF = 0.050 ms = 50 us

But in my 3.5 board R57 is 33kΩ, so:
PW = 0.673 x 33kΩ x 1nF = 0.022 ms = 22 us

Ideally, to minimize spurious triggering, you set the pulse width to shortest time that one tooth actually passes the VR sensor.
For 60-2 trigger wheel and 10,000 max rpm:
Tooth pulse time = (1 / 10000 rpm) * (60 sec/min) * (1 rot / 120 'teeth') = 50 us

For 36-1 trigger wheel and 7,000 max rpm:
Tooth pulse time = (1 / 7000 rpm) * (60 sec/min) * (1 rot / 72 'teeth') = 120 us

If you're seeing a noisy rpm value (jumps up), increasing the resistor value of R57 so that the PW fits your max rpm may improve it. But the datasheet recommends only setting it to a max 150 kΩ.

You can download the LM1815 datasheet here: http://www.national.com/ds/LM/LM1815.pdf

Wow that is much more detailed than what I was expecting!  Thank you so much for the explanation.  I do see the ocassional RPM spikes, although I very much need to set up the audio plug bench test to make sure it is not my VR hardware.  Good thing rescue kit 1 comes with a few 7502s in case I need to apply a fix (I have 60-2 with max rpm ~7500)

Hi guys, been a while since i posted,
got a prob with my setup, (here we go again they say)
Convereted to wasted spark (thanks to dnb's help on the msq) but we went to fire her up for the first time today and while cranking got no rpm signal being detected in MT,
and nothing on the timing light,
i have the config from the ecu on the laptop and will upload later once its charged up,
any other info you need?
my firmware version is 1.0.73

here is the config from the vems,
http://www.capriracing.co.uk/vems/config.txt

And the .msq
http://www.capriracing.co.uk/Zipfiles/4.6v8.zip

First things first, if you put a DVM on AC and put the probes across the VR and Ground pins (EC36-pin26 and EC36-pin27)
When cranking you should see 100 to 200mV

ok mate will check that tomorrow as the car is 15miles away in a workshop :-(
any other tests i can do? while i am there?
if there is or isnt that reading?

cheers for the reply Rob.

The "angular width of tooth" looks to be 0.00 on your config.  It should be 10.0

I suspect the change of firmware version between my car and yours has caused this to reset...  This should get you some RPM...

Then you need to calibrate "TDC after the trigger" (currently 80.0) to what you need so your crank advance reads right on the timing lamp.

cheers Dave,
what should angular width of missing tooth be? as that is also 0 i just noticed.

QuoteThen you need to calibrate "TDC after the trigger" (currently 80.0) to what you need so your crank advance reads right on the timing lamp.

this is the value i change to get the timing light to flash at tdc while its cranking over yeah?

Also has any other settings changed from when you sent me the msq mate?
like knock settings etc.
I had to use a spark map from a friend as the spark hex table was blank when i opened the msq from you.
i will get there in the end :D

They love to change the names of things in the MSQ files don't they... ;) 

When we both use the same firmware it will be a lot easier!!

well changed the settings in the msq as advised by dnb, and did the test as per rob suggested,

got no reading on the DVM while cranking mate,

if you set the DVM to volts and check across the pins you get 4.40 (ish) volts with crank sensor disconected, and 0.18 volts with it connected,

any other ideas?
i have the ecu here with me now in case you needed me to check the board for anything that may be missing etc,

cheers for the help as always guys,


Shot of the front and back of the board incase theres something missing,
is that the ignition drivers with the silver backs?
If so should i not have 8 of them?
(http://www.capriracing.co.uk/vems/board1.jpg)

(http://www.capriracing.co.uk/vems/board2.jpg)

just reading about on the vems wiki,
should i have any jumpers on these pins?

(http://www.capriracing.co.uk/vems/board3.jpg)

(http://www.capriracing.co.uk/vems/board4.jpg)

You only need 4 ignition drivers for the coils since you're running wasted spark.  You have 6, so not a problem.

Not sure where to go on the crank sensor yet...  Will have a think!

ok m8 thanks,
this is all thats stopping us from driving the car now and running the new engine in,

i gather i dont need anything on them jumper pins then?

I guess I wasnt clear when I said about the DVM test, this needs to be measured with the plug removed from the ECU - so we can read what voltages are being generated by the VR sensor.

What trigger type was your previous distributor setup?

If I remember correctly it was a Hall effect output from the dizzy. 

Tony - unless you've converted the ECU to VR (will post link to instructions when I find it), the chances are the trigger is not actually getting in to the ECU.  What circuitboard version do you have?  Is it 3.2 3.3... etc?

Firstly may i say thanks rob for sorting my login prob,

yes it was hall effect mate,
And jago was converting the ecu to vr while he was doing the p259 and adding the second trigger for a later date,
so any diagrams etc that shows what im looking for on the board will help as will then know if it has been set to VR,

the board is v3.3

thanks guys,

This should do you:

http://www.vems.co.uk/VEMS/InputTrigger.html

Rob

cheers for that rob,
i may leave this bit to an expert as im ok soldering but when it comes to small components on a board i may cock it up,
i noticed in the link the pic shows 6 jumper pins and my board has 12,
im trying to get hold of jago to take a look at the board have printed off the pics etc in the link,

is my board set out different to the link pics?
and will the map sensor need removing, (or the pipe) to get to what needs looking at)?
while the ecu is in bits any one point me to a diagram of what it will look like if its set up for dual knock sensors?
(http://www.capriracing.co.uk/vems/board5.jpg)

(http://www.capriracing.co.uk/vems/board6.jpg)

(http://www.capriracing.co.uk/vems/board7.jpg)

You've got a 3.3 board and the pics were of a 3.1 or 3.2 but the resistor and jumpers around the VR sensor chip are still the same.

I'll see if I have an old dead 3.3 board at home that's setup for Hall or VR and we can see what we can see.

Have a search on here for signalgen its a tool in the tools package that makes a .wav file that you can use to test the board by playing it from your soundcard into the VR sensor plug.

Cheers mate,
if you do have a board to look at that would be cool.
i cant get to the car until the weekend now as the owner of the workshop is at work,
and i go back to work monday so its going to be a weekend thing again unless i get the car trailered home.,
Still waiting on Jago to get back to me regarding having a look at the board to see if he set it up correctly.

just got back from picking the ecu up from Jago,
and he confirmed its set up for VR on primary and secondary trigger,
and its set up for dual knock as well,

off over the workshop in a min to test the sensor as rob said with the test meter, the correct way this time  ::) :-[

If there is no reading from the sensor upon testing is it dead? as was new from trigger wheels.
or is it to do with the distance from the trigger wheel?
if so what should the gap be?
cheers

put the test meter on the sensor,
hope this is the correct setting.
(http://www.capriracing.co.uk/vems/board8.jpg)
when cranking over the display reads 02.4

still no reading on the rpm gauge in MT or any sign of life at the plugs,

two clicks anti-clockwise should do you thats 200mV AC

ah ta lol
will try again tomorrow then, but i think its working

Quote from: [email protected] on September 02, 2009, 01:03:22 AM
First things first, if you put a DVM on AC and put the probes across the VR and Ground pins (EC36-pin26 and EC36-pin27)
When cranking you should see 100 to 200mV

ah that would be my fault cos you said AC mate lol

Just spoke to the guys where the cars sat and they said no probs will test it again in the morning,
but they said they dont think the sensor is the prob cos an out put was detectedfrom the sensor with the DVM.
If i can't get this sorted by sunday i may have to get someone to price me up checking the board out if poss.
or double checking the msq as this is whats holding us up now and the car needs to be moved asap (been in the workshop since may 09)

armed with the correct DVM settings :-[
we set to work testing the sensor,
at first all we got was OL on the test meter which indicated Over Limit,
so we decided to space the sensor off the trigger wheel and started to get a reading on the DVM

with it spaced this far,
(http://www.capriracing.co.uk/vems/board10.jpg)

We got a reading of:
(http://www.capriracing.co.uk/vems/board9.jpg)

i gather that readin is ok and means the sensor is ok.

I would try and close that gap up a bit.  It's working but not quite strong enough.  I normally use a feeler gauge to setup a CAS, not a ruler :p That should be in the region of 500mV at least really.

-Gavin

oh ok Rob told me between 100 and 200 mv though lol.

is the trigger wheel to close to the pulley?
as been told on my v8 forum that it is,
(http://v8forum.co.uk/images/newengine/trig.jpg)

Nope, that should be fine.  Seen similar work, like slots machined into the balancer. Only true way to tell would be to scope it

Rob knows the VEMs well, but if you can get a stronger signal by just a quick tweak, worth a shot :)  Most OEMs have a fairly high output at cranking and a narrow clearance of about 0.5-1mm.  If it has a higher output, more likely to trigger (and also helps to give a signal when the starter is less than healthy and reluctant to turn the engine over nice and fast!)

Not saying this is your problem, just providing an educated guess!  Also, not sure if this has been said but make sure the polarity is right for the sensor.  This caused me no end of grief in the past, had to do a trigger log and use that funky perl script to find that out. Or you could just try swapping the wires round lol.

Good luck!

-Gavin

ta mate,
i'll adjust to around 500 then,

have swapped the wires, but will try it again.

still no joy,
So now i think its time the ecu got looked at properly,
Rob or Dnb either of you two fancy taking a look please,
i know you didnt do the recent board mods but running out of ideas now,
the msq was done by dnb so doubtful thats at fault, the sensor is giving a signal as previously tested by your instructions,
Jago was going to try and come over to take a look at the car today (he text saying bit busy but will try)but never heard from him by 7 tonight so came home, now im at a loose end getting car done for this month now..

Do you have a scope of the sensor readout at the sensor, and ecu, and chip?
This must be addressed and you need to be 100% sure that the sensor is perfect before assuming that the ecu is faulty.

if i had a scope mate i would,
this is where having to rely on people come in to play :(
regarding the ecu,
it was converted from hall to VR back in jan 09 and i have had no way of testing it until recently when we went over to wasted spark,
thats why i want Rob or dnb to check the board to see if the modifications done in Jan are right, or if something is wrong. (missing from board)
the only test i can do at present is what Rob said with the DVM,

There could be a problem with the MSQ.  I am not sure that the firmware you have works without a camsync.  (Based on stuff I found on the wiki while researching 1.1.59)

I am going to put together a firmware and MSQ based on what is currently in the TVR.  The NOS functions will not be there, but that's a small issue compared to running the car (and I'll have 1.1.59 working by the time you need NOS anyway).  This should allow you to get an RPM signal.  I will host it in the usual place.

I have a scope and everything, but I'm a little far away to be of much use. :(  (Unless you can think of a way to make the area surrounding Newbury attractive to my good lady and daughter for a few hours... ;) )

Try this: http://www.aqyz05.dsl.pipex.com/cap_rpm_test.zip

what version is that .msq you sent mate?
as my firmware version is 1.0.73 at the mo.
cant get back to the car now until the weekend,
which is a night mare as i now only get two days a week to test anything :-( (saturday and a sunday)

Did you try the signalgen thing?  That's the first thing I'd be doing if you sent it to me.

The MSQ and firmware are 1.1.46.  You will need to download the appropriate Megatune distribution too.

Hi Rob no mate as this old slap of a laptop has no sound card,
bought it faulty and never needed sound for doing the tuning on the car,
maybe its an excuse to talk the mrs into me getting a new one :D

Cheers Dave off hunting for it,
is there a link to what i need to dload on the forum anywhere?

thanks again for the help guys,
just itching to fire this new engine up :-)

i can find
1.1.44 and 1.1.47
not 1.1.46 point me in the right direction please.

I really meant 1.1.44.  Sorry!

did you dload off the forum mate?
or somewhere else?

I think so...  Can't remember now :(

right downloaded 1.1.44 from sambas post in software,
that capri test .msq you posted Dave,
is that just to test the crank trigger no other settings? e.g car wont run on that msq.

That's right - the fuel pump and coils are disabled.  (There is a spark map, so it would "simply" be a case of switching on the fuel pump and coil drivers.)

have been informed Jago is going over to the capri this saturday,
he is taking his scope etc over, (fingers crossed it runs)
What do i need to get him to test while he is over,?
and how to test what ever i need to test,
i can print it off and take with me in the morning,

cheers guys.

well at last jago has mangaed to get over to the car,
put his scope on the trigger and it gave a perfect signal he said,
And he said the trigger and wiring up to the ecu is not at fault,
he has taken the ecu back with him to see what maybe the fault, or if he did miss anything whne converting it,
also just to test the setup uploaded the new firmware dave and still no trigger with the trigger msq you did,
Will keep you posted as Jago hopes to get the ecu back to me before next weekend, so we may av some sparks at last :)

we have life,
well sort of,
now got rpm on MT when cranking,
the car tries to fire, but is very rough as if only on a couple of cylinders,
tested all leads while cranking, with a plug, all fired bar two plugs,
ch36 on the ec36 is dead,
placed the wire from ch36 to ch35 changed config, all 8 plugs now firing,
have got no1 at tdc, with timing light,

have got the msq, config and dlog of trying to start, it does say on vems view when looking at the dlog trigger errors,
just wondered if someone could throw some light, but the ecu was the fault in the end, not sure what jago did but she is getting triggers now,

will upload the files in a few moments.

thanks guys,.

Here we go :-)

http://www.capriracing.co.uk/capri09.zip

also when i did the config dload the tables.txt was empty.

Oh... the tables files is what I needed to see - the trick is to leave the window open, tables will download and then close the download window.

it said at end avr says hello
that not the end then?

im using 1.1.44 firmware too.

also just looking at the audit log file,

i have this:

  WARNING(03): Value from option list "h2d2" = "INVALID" not found.
   WARNING(03): Value from option list "h2d6" = "INVALID" not found.
   WARNING(03): Value from option list "boost_conf_pwm" = "INVALID" not found.
   WARNING(03): Value from option list "launch_out_conf_speed" = "INVALID" not found.

Warning Details
---------------

   WARNING(03) means that the value expressed in the file for the
               constant was not found one of the options listed in the
               current configuration.  The constant was not altered, so
               you probably want to look more closely at this one and
               see what caused the mismatch.

i changed like i said ch36 to ch35 as no spark was on two leads on same coil pack, (cylinders 8 and 5)

fink i found the problem,
on h2 table ignition outputs i got two settings blank, doing a screen print.
would this be the trigger errors?

(http://www.capriracing.co.uk/vems/screen.gif)

hope this works,
managed to get tables to dlaod after about an hour,

http://www.capriracing.co.uk/vems/tables.txt

Just an update, and hopefully Dave (dnb) will update whats been done,

But Dave has the ecu running on his test bed now, was a R30 ressistor on the board that should of been removed when it was converted to VR from Hall triggering.

A BIG thank you to Dave,
He popped in on his trip over here today to drop the ecu off and endded up working on the capri with me,
after a bit of tinkering the car is running,
and sounds awsome,
He is a top man cheers mate,

we did have a prob of the trigger wires needed swapping again,
and the map sensor pipe had come off the ecu and made her run mega rich and on half the cylinders :D
but after that was refitted it was well sweet. :)

To be fair, it was at least 5 cylinders - slightly more than half ;)

Looking forward to seeing the tuned version now :)

cant wait mate,
been told how to overcome the alternator prob,
so will do that this weekend before the cam is broken in,
Oh and the tach channel was disabled, so changed that on the msq, so hopefully that will work now,
divider set to 8 yeah???

I think 8 is right.  I'd just keep changing it until it is right... ;)

:D