____  
  / __ \ 
 | |  | |
 | |  | |
 | |__| |
  \____/ 
         
         

 ___   
(  _`\ 
| | ) |
| | | )
| |_) |
(____/'
       
       

 _   _ 
( ) ( )
| `\| |
| , ` |
| |`\ |
(_) (_)
       
       

 __  __
 \ \/ /
  \  / 
  /  \ 
 /_/\_\
       

         
         
  #####  
 ##      
  ####   
     ##  
 #####   
         

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:
'''Trigger related page for MembersPage/EricN''' '''truck is a 6 cyl. I am firing cop coils and using a distributer mounted trigger wheel. Tooth count is dependent on what sensor I get working''' Board is a v3.2 serial number=110 MembersPage/EricN/Trigger/Optical Going to try this for now. *so much for that idea. MembersPage/EricN/Trigger/Vr This page hopefully all garbage. I cant get the input trigger to stop cutting out (happens at any rpm all the way to redline) no matter what I try. ---- '''OPTICAL TRIGGER DROPS OUT LIKE VR DOES''' Built an optical trigger. 6 teeth, set to coil type ignition. Use rising or falling edge makes no difference. Use filtering or not, makes no difference. Trigger drops out at any rpm (tested up to 4000) is worse at low speed. Loose fuel pump, injectors and ign. Used signal generater, run at 250 to 500 rpm according to lcd. Fuel relay cuts out in the same manner. Tested signal at atmega128 pin 29, looks clean. Is there anything config related that could cause vems to cut out? Keeping in mind the test bench has no sensors hooked up at all, just a input trigger and fuel pump relay. * fuelcut_min_kpa-0 * fuelcut_max_kpa-ff * TPS > 60% (at cranking, that is RPM / 100 <= cranking_thres ) * firmware version ? an upgrade might help **1.0.23, I have used every single version since 1.0.14 and it is identical. * MegaTune log could help http://www.vems.hu/files/EricN/datalog200604072201.xls ** strange format (not xls). However, it can be opened as tab separated csv (just some numbers show as dates). Perfer real xls format. ***Odd, it works fine for me. Will do another and repost. ** it can be verified that RPM drops to 0 immediately in 2 cases (first it's just one line! stays that way on the second occasion) '''Trigger dropped out at least 10 times, only 1 showed up, second occasion was me letting go of the drill before disabling the log, signal drop is extremely quick'''. Time does not fall back or advance. It's unlikely to be comm error. Engine state changes from 3 to 0 at the same time. Wheel error '''=0'''? * mcd,mct (always needed to reproduce): **[http://www.vems.hu/wiki/index.php?page=MembersPage%2FEricN%2FConfig mtt and mcd] * are the GND and (at least 3) GND5 signals all connected ? ***2 GND and 4 GND5 wires, only load is the fuel pump relay running on an injfet channel. * InputTrigger/TriggerLog could provide more insight into the pattern the ECU sees (problem at missing tooth, or random). Save to a file and upload via file manager (DocsPage bottom). Pasting does not work, because characters are garbled. That is what I get for a trigger log. Counted 15 relay clicks as this happened. I can not figure out for the life of me how to make it into real numbers. I assume I need to do something like this line-'''print report: perl bin/binary.pl < toothtimes.bin > toothtimes.txt''' but I am doing something wrong because it isnt working. Here is another one I did when the ecu was in the truck and I was running a 24-1 vr sensor http://www.vems.hu/wiki/index.php?page=MembersPage%2FEricN%2FTrigger%2FVr but again, dont know how to change it into that table.
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.