History of MembersPage/MattiasSandgren/SaabQuattro
Older Newer
2008-03-21 19:51:50 . . . . 237.198.8.81.ac-net.se [Will try another TS diode for flyback]
2008-03-19 21:52:29 . . . . 237.198.8.81.ac-net.se [Replaced with MC33151D, works good on the test bench]
2008-03-19 21:33:26 . . . . 237.198.8.81.ac-net.se [Updating]
2008-03-19 15:24:21 . . . . MembersPage/MattiasSandgren [Will replace FET drivers to inverting.]
2008-03-19 10:37:04 . . . . 3e70d6f3.adsl.enternet.hu [fetdriver type]
2008-03-19 01:01:55 . . . . 237.198.8.81.ac-net.se [Injector output problem - what to blame?]
2008-03-18 23:31:38 . . . . h150n3c1o261.bredband.skanova.com [Showstopper bug - injector hardware?]
2008-03-18 22:33:51 . . . . MembersPage/PelleWallberg [box problem.. updating]
2006-10-14 19:38:51 . . . . MembersPage/MarcellGal [more note on adaptive hyst]
2006-10-14 05:44:48 . . . . MembersPage/PeepPaadam [Answer to Q regarding VR sensor and coil-type trigger.]
2006-10-13 22:33:48 . . . . MembersPage/MattiasSandgren [Inductive Volvo sensor for this trigger wheel?]


Changes by last author:

Changed:
----

This car uses Genboard v3.2 #204 that has seen use in a Volvo PV : MembersPage/MattiasSandgren/VolvoPV $FlgChr1$FlgChr< It never worked quite ok on that car, blew a few injector FETs and drivers.. long story. Emil sent the board off to be repaired with new FETs and FET drivers, and it was never tested with anything connected to a FET after that. Gustav bought the board and tested it on his SAAB, ignition only, and it worked very well.

When it was time to try injector it didn't turn out too well. As soon as the power is turned on, the injector outputs go active by default, instead of the normally inactive state. The function is inverted and the PA0 - PA07 pins are all set high (5.0 VCC).

What seems ok:

* Injector FETs

* FET drivers

** On the board right now : LM5111-1M (double non-inverting)

* Configuration (no injector outputs in use)

* Firmware (1.0.36 and 1.0.73 were tested)

What was never clear was the relationship between :

* Genboard hardware (FET drivers)

* Bootloader (that loads the VEMS firmware)

* VEMS firmware (application)

From what we (Mattias and Pelle) have deduced, one simply must have a firmware/application compiled for the type of FET driver on the board, this information is only given by the information that is compiled into the firmware/application.

What confused me a bit was that this was not what Jörgen said, he meant that the firmware/application took it's information about the FET drivers from the bootloader, so one simply had to have the correct bootloader to match the hardware to make the firmware/application work as supposed to. It isn't currently like that but was maybe true for the first Genboard versions.

Engine specifications
Changed:
The bootloader sets the outputs to safe defaults depending on what FET drivers are mounted. That's all it does, and implies that the firmware/application must have the information about the FET drivers compiled in as well to treat the outputs correctly.

We will replace the non-inverting drivers with regular inverting drivers (that are supported by VEMS firmware/application code).

* 4 cyl, 16 valve DOHC

* Standard B202 Saab block

* Stock head, slightly ported

* Cams from T16

* Large turbo

* Fuel of choice is E85

Engine management specific information

* Ford Motorsport 1600 cc/min injectors

* 18 V TS diode used on flyback

* Distributor ignition

* MSD 7AL CDI box

* Dual solenoid Bosch IAC valve

* Coolant fan relay

* Water pump relay (radiators in the trunk)

Changed:
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.

2008-03-19
Changed:
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?
Engine was started with fuel injection for the first time, VEMS Genboard only controlled ignition and datalogged earlier and carburators were used.
Changed:
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? $FlgChr2$FlgChr< 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?

Idle air valve seemed to work quite ok, but needs lots of tweaking of course. It could handle the coolant fan current draw just fine.
Added:
At idle the car needs only 1.0-1.1 ms pulsewidth from the injectors. We suspect we have poor control, injectors are big but Emil suggests trying another 18V TS diode in series with the one we already have.
Changed:
lackad_2006.jpg
lackad_2006.jpg

----

The story of Genboard v3.2 #204

It has seen use in a Volvo PV : MembersPage/MattiasSandgren/VolvoPV $FlgChr3$FlgChr> It never worked quite ok on that car, blew a few injector FETs and drivers.. long story. Emil sent the board off to be repaired with new FETs and FET drivers, and it was never tested with anything connected to a FET after that. Gustav bought the board and tested it on his SAAB, ignition only, and it worked very well. $FlgChr4$FlgChr> When it was time to try injector it didn't turn out too well. As soon as the power was turned on, the injector outputs went active by default, instead of the normally inactive state.

We have replaced the non-inverting drivers with regular MC33151D inverting drivers (that are supported by VEMS firmware/application code).