##### ## ## ## ## ##### ## ##
____ / ___| \___ \ ___) | |____/
## ## ## ## ## ## ## ## ######
###### ## ## ## ## ##### ## ####
_ ( \ | ( | | | | | | | (____/\ (_______/
IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now. Visit Preferences to set your user name Summary of change: My plan is to make the RadioBoard to be real, look also VemsFrontier/Bluetooth I got Volvo Amazon with B20. ---- I mounted a 36-1 toothwheel to crank from Ford (it's like [http://www.bowler.fslife.co.uk/pressedtriggerwheels.jpg this]) and Honeywell GT101 hall sensor. I set air gap to 1.2mm, connected sensor to 9v battery and 10k pull-up resistor to output. When I manually rotate the engine dvm showed near 0v when tooth was near the sensor and 9v when no tooth, like it should. I even tried to rotate engine faster and I saw good pulsing with scope. I started the engine (currently coil trigger, v2 genboard) output was most of the time low. Frequency should have been ~600Hz idle but it was only ~60Hz or less! I tried to move sensor closer (much less than 1mm) to toothwheel and away from wheel 2mm or more. No help, signal was the same. So I moved sensor as far as about 4-5mm and it started to work! GT101 sensor specs says air gap 1.02-2.03mm. Now it's atleast double. I did try power sensor from adjustable power supply and also tried 1k pull-up resistor. Neither did help. Sensor is mounted so when no tooth it has no metal in front of it and when tooth is front of it metal is much over sensors centerline. Sensor has built in capacitor between vcc/gnd. Why? Should I use it like it work (~4-5mm away from triggerwheel) or what should I do? ''It's hard to give advice in this matter, one thing is sure and that is that the trigger wheel is not suitable for a GT sensor. But I have used the GT sensor a lot and have used it far outside it's specifications with good and bad results. What I do know is that the sensor is self adjusting, you'll notice this if you put a piece of steel in front of it at 1mm distance and then move it to 7mm distance. It will go high for a while and then selfadjust to see the steel again I think this is what happens with the trigger wheel you have, it sees the solid disk for some reason, probably because there is not enough material in the trigger teeth. Moving the sensor further from the solid disk in the axial direction (of the crank) could help. I'm pretty anal about triggers and I can only advice you to make sure that it behaves predictable at all rpms before you start loading the engine. I have seen very expensive failures because of non consistent trigger arrangements. If you choose to make a new trigger wheel you should know that the GT1 sensor does not work well with trigger made up of large raised areas with smaller lower areas as a trigger wheel made by drilling holes. This is because of the self adjusting feature.'' Thanks, this was helpful (I got sleep that night). Triggerwheel is welded to crank pulley, so my plan is to change GT1 to something else and I have one M12 threaded hall sensor to be tested. This sensor also has some adjusting feature, but it's magnet is much weaker and I table tested and it has some hysteresis (I think) but it does not adjust much (if at all). Is this wheel originally made to be used with VR sensor? My system is even now only fuel, so I tested GT1 with about 5mm distance. While cranking LCD (and Fluke&scope) sees signal, LCD says ~200rpm which is correct but engine did not start, I think there was no fuel at all? I also saw from scope that there are some false triggering. I didn't remember to watch Wxx on lcd, if there is false triggering Wxx grows and genboard does not give fuel, right? My conf was pretty much this, could someone confirm these: <code> primary_trigger=01 # multitooth, (rising edge at the processor) secondary_trigger=02 # Cam sync disabled trigger_tooth=01 # 01*6 degrees after when the missing tooth is detected, tooth_wheel=23 # 36-1 another_trigger_tooth=12 # also fire 18 teeth (180 degrees) later than trigger_tooth (for 36-1 wheel) # If you cannot get it to fire # (check the injector supply, # test flyback with DVM diode mode, etc etc...) # try to start over with a working config # such as MembersPage/MarcellGal/EngineSwap # and change only above (trigger-related config) values first # => use the config variables below from the working config (shouldn't matter for this setup, but better be safe). crank_minper=40 # anything from 01 to 50 is fine. If measured event-period (that is every 180degrees for a 4-cyl) is shorter than this, it's considered and error. tooth_wheel_twidth1=03 # Cam sync only? (3 engphase units) tooth_wheel_twidth2=06 # Cam sync only? (6 engphase units) reset_engphase_after=D8 # Cam sync only (216 engphase units) </code> GenBoard can be trigged with 2 (evenly spaced) trigger pulses on cam (1 triggerpulse per crank rev). In fact most mazda-BP are triggered this way, eg. MembersPage/Fero. D-jetronic distributor has 2 extra triggers without advance (I'm thinking connecting them in parallel). These can be used as coil-type primary-trigger (for either fuel or spark or both). I tried quickly these 2 extra triggers (yes evenly spaced) in parallel triggering genboard controlling fuel only, before that my genboard v2 was trigged from the coil (divider=02), so with divider=01 engine started. Only thing is the rpm reading, now there is twice less triggers so rpm is half what it used to be? Another thing what I'm wondering is how (in config) can only 1 trig/rev be used for spark (2 spark/rev) when using coil-type, eg. primary_trigger=07? I have no config line in mind that makes coil setup sparking twice, not in v2 but not in v3 too. My plan is for sure 36-1, but I need to make a new hall sensor bracket first. This 1 trig/rev would be an easy way to start planning spark (1 coil and distributor), if it's just possible. Later wasted spark. Optional: Add document to category: Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.