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

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

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

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

 _    _ 
( )  ( )
`\`\/'/'
  >  <  
 /'/\`\ 
(_)  (_)
        
        

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:
---- This car uses Genboard v3.2 #204 that has seen use in a Volvo PV : MembersPage/MattiasSandgren/VolvoPV \\ It never worked quite ok, blew a few injector FETs and drivers.. long story. But Gustav tested it on his SAAB, ignition only, and it worked very well. But now it was time to try injectors. That didn't turn out so good. As soon as the power is turned on, the injector outputs go active. The PA0 - PA07 pins are all set high (5.0 VCC). What seems ok: * Injector FETs * FET drivers * Configuration (no injector outputs in use) * Firmware (1.0.36 and 1.0.73 were tested) We discovered the pull-down R153 was missing on this board (!) and we added (10K) and the pull-up R154 (also 10K) was removed. In the schematic that is how it should be. R153 acts as a pull-down to ground for output pin OC0 which is kept low. We cleared EEPROM - factory restored, then did basic configuration. But as soon as power was applied the outputs were active. If the processor RESET line was set (active low) the outputs were active until we fixed the mixup with R153/R154. We tried our own short and very basic code to test the injector outputs. We got the same behaviour as with the VEMS firmware from the outputs when we explicitly set the corresponding output to be an output (not input) and set it high. As we don't have the source code we can't tell what the other pins are set to. We suspect a hardware issue, that we can't pin-point. At the same time the schematic reveals only OC0 and PA0-PA7 and these seem to behave like they should with our own code. So no other pins or components should pose a possible problem. Right? What does the VEMS firmware do wrong that we do right? Still the firmware can't be blamed, it works on other boards, but the methods used seem to have the wrong effect on this board. ''' Early boards like this one used non-inverting FET drivers. Is this a case of the wrong boot loader used with the wrong firwmare? ''' \\ What information does the bootloader contain? What is the correct bootloader version to use for this board? What does the firmware know or assume about the FET drivers state and function? What to blame? We're sorry we can't describe the problem better, we could produce a lot of measurements and tests but all we have seen looks alright. ---- This trigger wheel (2 teeth on iron/steel disc)is in use, works fine. http://savarturbo.se/stuff/images/gustavs_saab_quattro/trigger_skiva.jpg ---- Here is the car, work in progress, just painted after all body and chassis work: http://savarturbo.se/stuff/images/gustavs_saab_quattro/lackad_2006.jpg
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.