MembersPage/MagnusKarlstrom (2007-04-25 21:29:49)

My plan is to install v3.3 on a Porsche 944 -83. My idea is to place the the genboard in a empty motronic box and use as much as possible of the original wire harness. I guess one of the bigger problem I will have to deal with is the

trigger system 2 VR-sensors

I understand it is a version of the "auditrigger". The engine will be using the stock motronic distribiuter to start with.


070425

First update in almost a year, not very good of me...

Anyway, I had the car running last year but with some kind of trigger problem around 6000 rpm. I used firmware 1.0.36 and the 'standard modifications' with bigger C40, shorted R162 and 14k pullup for the 'crank home' signal. C103 problem is also taken care of and I changed R57 to allow higher rpm if needed.

Trying to fix the problem I tried a resistor network to feed back a part of the disturbance signal in opposite phase but it didn't help at all since I didn't get the signals to cancel each other as expected. (The sensors are probabaly not placed in such a way so it is possible) The engine was running but got trigger errors once the rpm was over idle speed.

My next step was a firmware update to 1.1.12 and the latest suggested modifications to the HW according to the InputTrigger/AudiTrigger page. Right now it is not working a all... I get a rpm reading while cranking but it does not want to fire like it should. I have to studie more about the latest auditrigger info.


No one who knows anything about the triggersettings for the auditrigger?


060504

I have trouble understanding how to set up all trigger settings for my configuration. I'm using firmware 0.36.

This is my current config.txt, it has a lot of strange things and errors lets focus on the things that will give me a stable trigger and correct rpm reading in Megatune.

http://www.vems.hu/files/MembersPage/MagnusKarlstrom/config/mcd.txt

I guess these are the lines to put focus on, correct?

divider=02

alternate=11

rpmk[0]=0B

rpmk[1]=B8

config11=30

config12=30

config13=00

primary_trigger=C3 ????

secondary_trigger=99 ????

tooth_wheel=82

trigger_tooth=00

another_trigger_tooth=41

crank_minper=30

tooth_wheel_twidth1=01 ????

tooth_wheel_twidth2=FF ????

cam_sync_r_edge_phase=03 ????

cam_sync_f_edge_phase=03 ????

reset_engphase_after=05 ????

toothrel_normal=FF ????

toothrel_missing=FF ????

I think we need ONE good page that explaines all trigger related settings in the config.txt, I can't be the only one who don't understand it...


060331

The MAP/TPS issue was due to some errors in the config.txt. With help from msnordic I found the Alpha-N/Speed-Density Blendning under Extras in menu and changed from 25500 rpm to 0 rpm. That fixed the MAP problem.

The other problem:

Code version does not match signature in vemsv3.ini

Expected "VEMS v1.0. 12x12 kpa=2,1

Received "VEMS v1.0. 12x12 kpa=F,F

was fixed by downloading the config.txt from the board and remove the last strange line which caused an error and generate the config again and upload it.

I have been looking at this and when I use download-config.bat it takes a very long time to perform the download and the result i corrupt. The last lines of the config are:

boost_conf=FF

boost_targetoffs=FF

boost_minpressure=FF

boost_pid_kp=FF

bip_b

_ywFhaoFkfF=ro_fop

With mcd in the terminal it works fine and the config can be generated without errors :-)

The only strange thing at the moment is the firmware upload problem, it only works once in a while and only after board has been without power for some time.

Maybe it sees RPM signal (depending on trigger setting and trigger HW) ? If so,you need the "f" option with prog.pl (or megaloader) so it enters BootLoader even if "engine running" (use with care; eg. fuelpump and ignition coils unpowered if possible). But since I have a working firmware uploaded I don't care to much about it right now.

Now it's time to get back to the trigger again. Hopefully I will soon be able to bring the car to Ă–rebro so I can do some tests on it.


060329

I get an error then starting Megatune, it says:

Controller code version does not match signature in vemsv3.ini

Expected "VEMS v1.0. 12x12 kpa=2,1"

Received "VEMS v1.0. 12x12 kpa=F,F"

The F,F explains things. It seems like a configuration issue (the kpa_conf=FF currently in effect is meaningless; admittedly I didn't know that it results in such interesting and confusing show, maybe Dave Brul will give it some test and maybe make it default to some less surprising default behavior for bad config).

It is a bit hard to tell if all the other readings are okay since I don't have sensor hooked up to the board. Battery voltage and TPS are however okay.

A very strange this is that the MAP value is following the TPS value!

No LCD.. yet..

Manmll returns:

RPM:0000 W00SFFI00

58 -00 c0000 i0000

clt:-40C adv:+00

0000 iac:040 122

kpafac=7D

kpaoffs=80

Can't find any errors here, ground is connected, +5V is stable, flyback is not connected since I haven't installed any injector drivers yet. (My first priority has been to get a working and stable trigger while cranking. Flyback, injectors, coil etc. are the last things before trying to start)

060328 first update since the dinosaurs left us...

Problem again

After moving to an other city and some other stuff I thought it was time to make some progress with the VEMS project. Downloading a new version of the firmware and Megatune felt like a good start, specially since the firmware now has support for the trigger on my car.

After having some problem with the firmware upgrade due to 50Hz disturbance triggering the LM1815 circuit I finally managed to figure that out with some help from Emil (using 'f' option to megaloader or prog.pl I guess). The board was upgraded to 036 and config files uploaded with some warning and an error.

I started Megatune and at a first look it looked okay, but it was not. The map value is not behaving normal at all, it starts at 0 and then slowly climbs to ~140 kPA shows no response to blowing and sucking in the hose to the MPX sensor. This worked okay before I started the upgrade. The MPX sensor also seams okay since the output voltage changes with the pressure.

My next step was to try to upload the firmware version I previously used but that didn't help, the map value is still crazy. It also took me many tries before I managed to upload the firmware despite that the trigger inputs now are shorted to prevent disturbances. The upload process fails at a random point and reports an error writing a word. After many tries and leaving the board disconnected for a while I finally managed to upload the 036 firmware and config again, but the map value is still crazy.

That is wrong with this board? Didn't it like to move from FinspĂĄng to Ă–rebro? I did :)


0510xx

Problem is probably solved! :) I replaced the xtal before I checked my mail and this page and that seems to have solved the problem. I made some comments below.

Serial cable and power cable has been attached to the board for some initial testing before soldering more parts to the board. The only problem is that it does not work the way it should.

Strange, because boards go through testing, during which all the supplies (7 or 8 including the max232 -8V), the ISP, the serial communication, the WBO2 pump circuit is tested.

Once you get it starting it will stay alive until you remove power for a few minutes. 5V supply is always okay and the reset signal goes to high every time you apply power.

Q: What to do next?

A very nice offer, hopefully I don't need a new board now.

0509XX


The parts has arrived and everythings looks fine. Delivery was very quick! :)