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

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

  _____ 
 |  ___|
 | |_   
 |  _|  
 |_|    
        

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

   ____ 
  / ___|
 | |  _ 
 | |_| |
  \____|
        

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:
Testing the v3.3 units purchased recently (#316, #317, #328 & #360) with this: http://www.mmcompsys.com/download_zone/6_sensors/SEN.pdf Magnetti Marelli sensor - which is a common sensor used by the likes of Omex and MM themselves. Its resistance was measured at ~620 Ohms. * A scope trace shows a good AC signal ~(+/-10V) on VR InputTrigger ** measure the input signal mean value, in DC setting. Eg. if the signal just slighly goes under 0V (eg. minimum is -20mV) for some reason, that would explain all. A '''scope in AC mode does not show this'''. *** Voltage measured at 9.2VAC, 0VDC * same config (from MembersPage/JimW/ExampleConfig ). ** please issue the (Man) mdv, mdV, mcd and mct '''for each''' and save the result, and publish. Very important to see the config that was actually read back *** Results are here [http://vems.hu/www.vems.co.uk/VEMSInstalls/Unit317Result.txt Unit 317] [http://vems.hu/www.vems.co.uk/VEMSInstalls/Unit328Results.txt Unit 328] [http://vems.hu/www.vems.co.uk/VEMSInstalls/Unit360Results.txt Unit 360] * all have been loaded with firmware v1.0.23 and the * verify firmware integrity (eg. prog.pl without "w" option) '''for each''' *** All verified ok, no errors * if you unclamp any ** check resistor ad LM1815 pin7 (first check that it exists, than maybe measure resistance, should be 100..180k) *** 360 measured as 180K ** with scope, '''measure on LM1815pin3 and LM1815pin12'''. DC mode is needed to see if signal goes below GND *** Pin 3 0.0->0.3v Pin 12 0.5->0.7v ** check LM1815pin5: (the 3-pad SMD jumper) isn't it connected (solderblob) to either GND or +5V ? It shouldn't, and it's unlikely to explain anyway. ** don't clamp it unless the problem has been identified and fixed * #316 (primary&secondary VR) and #328 (VR primary/Hall Secondary) read the engine speed perfectly * #317 & #360 show no engine speed ** there has never been a problem with primary trigger with assembled controllers earlier (they get tested, with appr +-5V signal, lower than yours), so 2 out of 4 is extremely surprising, suggests another round of careful testing and reporting details. ** publish a few seconds of the serial-output after ''Man mdf01 mdkff'' when the trigger signal is applied. This reveals if the trigger gets input. *** Logs are here [http://vems.hu/www.vems.co.uk/VEMSInstalls/Unit317.log Unit 317 output] [http://vems.hu/www.vems.co.uk/VEMSInstalls/Unit328.log Unit 328 output] [http://vems.hu/www.vems.co.uk/VEMSInstalls/Unit360.log Unit 360 output] ---- After Emil's suggestion I took a VR sensor with a 500 Ohm impedence and wired it to the EC36 plug on my bench. Testing on a known working unit (316)I set the primary trigger type to coil and put the sensor on a mains adaptor, it gave a value constant reading of around 1500rpm. One of the suspect units was then tested with the same settings and there was no reading (0000rpm)
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.