News:

When asking for technical help at the very least let us know the version of firmware you are running.
Cliff's Calibration (Mapping) Guide is a MUST READ: http://www.vemssupport.com/forum/index.php/topic,97.0.html

Main Menu

primery hall and secondary vr trigger problem

Started by andreNL, October 24, 2010, 05:19:39 PM

Previous topic - Next topic

andreNL

Hello, after the wbo problem next come up.

My setup consist of a aluminium pouly with 23 holes drilled in
And fitted with neodium magnets. These are north/south pole
Facing the standard webshop hall sensor.
Sensor is connected to 36-25 grond 26 trigger 27 5+ volt.
SJ2, jp2, jp7 shorted. R56 removed, r30 is 10k.
VR Wiring ok, with ground connected to ground
VR voltage is 190mv connected to 18-12
Soldered the extra lm1815 and shorted sj7.

Is it possible hall is not reacting to the magnets?
Why is the vr not showing in trigger log?
How does vems know vr is connected to 18-12?
Is r30 to high?
Cheers andré


andreNL

Well i figured out i have a unipolar hall sensor wich needs to see

the south side of the magnet. So i take the pouly of tomorrow and change the magnets. Same time i dubbel check if the sensor is situated at the right position. I Hope of this fixes the problem and the VR starts working too.

andreNL

#2
Did some trouble finding update.
Connecting a led between hall 36-27 and grnd gave a rpm reading in vemstune so i figure vems board is ok for reading signals at the 36-27 hall trigger connection.
Checked Connecting wire for connection and twist. Plus ground and signal.
Ok checked hall sensor wire and Connector for twistings ok
Then i checked the sensor magnet allining it was couple mm out :(  also half the magnets arent working because of the wrong side ( north side) facing the sensor.
I checked the sensor connecting the 5v + and grnd and fitting a led between signal and grnd. Using a spare magnet showed the sensor was working nicely.

andreNL

#3
Well i have a nice clear signal from the primary Hall signal
but the secundary isnt working at all.
checked the wiring and polarity all ok,
i have 200mv at EC 18-12 pin and extra LM-1815 installed and sj7 shorted.
Sensor is original sensor wich senses 3th cilinder ignition on a 3 cilinder engine.
I made shore the signal is not sigenaling simultaniously with Hall signal.
??? ???
Any ideas please?
cheers andre

edit: http://www.vemssupport.com/forum/index.php/topic,431.msg4245.html#msg4245
The thing to keep in mind with the LM1815 VR sensor is that it triggers when a positive voltage crosses 0 and goes negative.

i check this tomorrow because i thought it goes negative and then positive.

andreNL

Didnt go wright, my LED stopped blinking.
tried to switch my fan and check light but didnt turned on.
happily i still can communicate with the board.
so i think i blew TPICA6259 ordered a new one TPICA6259DW-4 hope its the right one.

Is there a way to check second trigger working and rule out a faulty sensor?
only thing i can think of is noise, but the wire is shealded.

mattias

#5
What engine is this?
Why are you not using conventional sensors and trigger wheels?

Who made the wiring harness and does it follow the rules set in the User Guide?
http://www.vems.hu/wiki/index.php?page=MembersPage/PhatBob/UserGuide

You should use latest VemsTune and firmware, and the triggerlog feature. At least get a cheap oscilloscope.

andreNL

Quote from: mattias on October 29, 2010, 12:38:04 PM
What engine is this? Its a Daihatsu GTTi 3 cilinder twincam turbo engine.

Why are you not using conventional sensors and trigger wheels?
Because the original poulie is verry heavy and the new one is made out of aluminium, the secondary trigger is the standard trigger fitted in de distributor housing like a toyota's triggers.
It had a wheel with 3 theeth representing evry cilinder ignition tdc stroke.
I cut 2 teeth off and use the number 3 cilinder teeth to set vems to zero.

Who made the wiring harness and does it follow the rules set in the User Guide?
http://www.vems.hu/wiki/index.php?page=MembersPage/PhatBob/UserGuide
I made the harness and only used PhatBob guide aswell as all the other Wiki information on the vems website to build the loom and board. its amaizengly fun todo, but sometimes makes me said because of the amount of problems wich has to be tackled.

You should use latest VemsTune and firmware, and the triggerlog feature. At least get a cheap oscilloscope.
i use Vemstune and the triggerlog, for firmware i use 1.1.78, i believe 1.1.82 is the latetst one but thats a developers version. 1.1.78 is the users reconmended last published stable version, and it works well.

thanks for the reply  :D cheers andre  ::)


mattias

#7
1.1.74 and 1.1.81 are the latest recommended firmwares, see the "released" tag.
http://www.vems.hu/wiki/index.php?page=GenBoard%2FUnderDevelopment%2FFirmwareChanges

I'm not sure I ever used 1.1.78 but it should work to make triggerlogs (it's the first version to support it).

You should be ok with having only 3 steel/iron teeth (not stainless steel) on the damper and the Honeywell GT1 Hall sensor. It doesn't require magnets to work and is made for this application. This makes it easier to place the cam sync sensor so that it doesn't race with the primary trigger teeth. Another idea for you : I made a 6-1 trigger for a 3-cyl 2-stroke snowmobile engine last year, that means wasted spark for you but doesn't require a cam sync sensor.

Avoid VR sensors if you can, for a custom build you need to know what you're doing with proper signal conditioning. Some odd signals are not really compatible with the zero crossing detection of the LM1815, but can be made to work with some modifications.

andreNL

Ok thx, i did some research because i didn't know how a vr works

and how vems works with the signal. A vr creates a ac current with a higher voltage and frequency with increasing rpm.
Vems conditions this signal for the lm 1815 to.work with and prevent it from damaging.
I need to find out the frequnecy and voltage generated at low medium and high rpm and condition those values according to the lm 1815 specifications.
Doing a test with the pc soundcard tonight see if i can get some values to work with .
Cheers and thx for your support.