Back to MembersPage/NanassyPeter
Ok,here is a datalog of how my ECU behavies under IGNITION ON only.I realyzed this problem long ago:PW and sparks drops to zero suddenly and goes back to normal cranking mode.Note that i do nothing ,no cranking or anything else.
any solutions would be appretiated.
- I have no solution for the problem, but I have the same thing but only seen PW goes zero. I must check my logs for spark drops. And if I remember correctly the same PW zero effect can be seen on LCD.
So far,so good,i uploaded 044FW and did a try,looks like works great.Further testing needed tough.Thanks for the fast response!
//pnanassy
Pending
- MAT ignition retard.
- custom oil temp/pressure gauge with V3.3 and LCD
should check the relevant page, IIRC these are not yet implemented
GenBoard/UnderDevelopment/StagedInjectors
- 5 primary injectors, driven sequentially
- and another 5 staged. (note: 2 free injector drivers on this 5cyl engine, because fuelpump switched from an injector channel as well). Document the flowrate of injectors - the ratio of primary and secondary is very important because it must be configured
We have 10 Audi S3/TT high impedance (14ohm) 420ccm "shorty" injectors.So basically we run the same in the staged group as in the sequential "main" injector group.
- Possibly 5 connected (while the FET and EC36xx pin would be happy to drive 5 injectors, highz or properly configured lowz, but this could abuse the flyback.
- or 2+3 split. This is recommended. It's OK to switch them simultaneously though, like h[0]=xx xx xx xx xx xx xx 60 where 60 (decimal 96) is sum of 20 and 40 (decimal 32 and 64) to switch injF and injG (see GenBoard/Manual/DigitalOut/Table)
Sorry ,this section is totally chinees for me....
Please explain it a bit more.
Is it possible to configure fuel pump out to another "thing",to have all 8 injector FETs? How this works on a V8 engine ,where all 8 injectors have to be driven independently?
- I have 8 separately driven injectors with the fuel pump fed separately. See MembersPage/DavidBlades/FanTest for my config.
Anyway,is there any difference between:
1 inj FET driving 2 injectors
VS.
1 inj FET driving 3 injectors??
What injector behaviour can i expect if i drive 2 injectors from 1 inj FET,this way i do not need staging,all injectors will work all the time.There is NO NEED for lean idle,this is a race project.Im basically looking for options here....
A: We have driven 3,4 and 5 high-z injectors on the same outputs on a few cars. With the powerflyback board you will most likely have no problem with driving those high-z injectors in pairs. They aren't too big. //Emil
How can i insert the new ALS functions (MembersPage/GaborRacz/NewAlsLaunchAndOthers) in the 1.0.30firmware and Megatune??
Q
I still experience some unwanted EGO behaviour sometimes,the EGO correction just switches off (no correction at all),even tough it would be needed!
Please tell me which MegaTune variable to set and which direction??And what is this all about?
1.0.35
Firmware 1.0.35 (compile for testing: read: never released) got phased out (almost immediately after uploading) in favor of 1.0.36, since an accidental testing line prevented 1.0.35 to switch off fuel pump "config.engine_off_delay" after engine stall (eg. an accident).
Note: I think you control fuelpump with p259ch5, NOT with P259/6.
Serial port / cable problem suspected, as this are the same tools that have been in use for a while. If your tables were corrupted during upgrade, you can try to generate the config and upload the .mtt files through Hyper Terminal instead. When you do next upgrade, run the included bat files in the order described in README . //Emil
Hi Emil,
i uploaded my mtt files (made by Marcell) through Bray Terminal.
And yes,i use a USD=>Serial adapter cable, bought 2 different types (not pl2303 type from WebShop!). Unfortunately trashgrade windows drivers are very common, and often the cables are trash too (like the cypress-m8 type). There are plans to make MegaTune communications more robust with trash cables. Until than, use good cable.
The firmware upgrade and verification uses checksums and warns even today if there are any problem.
NOW THIS IS nerve-wrecking:
IAC - make a subpage for your IAC, it's scattered through several pages
- in 1.0.35 (experimental) the Idle valve cliks like crazy!!!!
Just make a proper report with:
- your PWM solenoid connection
- firmware version
- the mcd/mct dumps as well (mcd at least with 2 different IAC speed settings, as it's vital in your case).
This allows checking your config and reproducing (maybe in the experimental testing snapshot you used, MegaTune doesn't set the right iac variables ? iac config changed). Taking note of the above takes 15 minutes. Without publishing the above, you're wasting your time, noone will be able to help you efficiently.
- See EasyTherm on how to hexpatch the airden into any firmware in 2 mins.
- I have used stock Audi idle valve (AAN) with same (same as 1.0.35? this is a contradiction) firmware (connected to INJFET), and it controls idle very nicely
- IAC actuator speed set to 5.
- Valve needs quite high DC%, some 50%ish needed to open it even a little bit. IAC REF table is set to 50..90% across the temperature range
Miska,DC depends on how your throttle body is set (i dont want to run the IAC vale when engine is warmed up).
- AFAIK there is NO reasonable report from anyone (this is no report either, as it lacks basic information too). Where is the Fero report you refer to?
IAC frequency changed from very high to configurable
IAC wasn't noisy with 1.0.30, but i had resolution problems. In 1.0.35 (with unpublished config!!!) it's noisy and does NOT work
- Before, IAC ran at a very high frequency (this or DC is what the Audi IAC wants).
- after request (mostly from BMW guys: starting an Audi-BMW war here, hehe :-) the iac speed was made configurable
- the Audi solenoid is also very noisy, if it's driven at too low frequency it will tick very loudly. Maybe the problem is misconfiguration (maybe MegaTune vemsv3.ini - remember this is experimental - or usage: when you write the minimum required info, it's gonna be easy to tell)
HW change should NOT be needed - so go the proper route first and publish the required stuff (see mcd/mct above). Besides, (but remember, config first!), this is you can try ...
If you have powerflyback, Jörgen recommends trying an external (BY399 or Schottky) diode with enough current rating for the solenoid (around 2A for most Audi IAC's, 4-5A for the A8 engines IAC). The powerflyback makes the solenoid close quicker which is the exact opposite of what we want for the IAC. Even if you don't have powerflyback I recommend using the Schottky flyback diode on the solenoid as it has a fraction of the voltage drop of our normal low voltage flyback. -Jörgen
Don't use non-released firmware unless you know what you are doing!. There are no known problems in 1.0.36. The only things we know for sure from the above:
- you're using trash cable
- forget to apply your temperature calibration
- and seem to claim things without publishing even the minimum required info (eg. config!).
Strange that you get these problems with your serial adaptor. It's well known in the industry that USB cables cause problems, but not to this extent.
- 1, Please check that your config was uploaded correctly after the upgrade, with mct/mcd, or check in megatune that all the IAC settings are sane. Serial problems during download and upload of config can cause a lot of headache. I'll pick up a USB->serial converter and try the tools at home using this. I recommend Hyper Terminal for Manmcd/mct and mtt transfers when you get problems with the bat-files. If you dont get this straight, i recommend that you disable IAC and set idle on your throttle body instead until you can sort the IAC settings out.
- 2, The temp sensors are off because of the new firmware testing release doesnt contain your custom patched temp scaling. (Marcell, could you please patch 1.0.36 for him again, with the same calibration and upload?)
- 3, We do our best to test firmware before sending them out for release, these last 2, 1.0.35 and 36 are testing firmware's and not fully released. I will personally try this firmware on a BMW Turbo tonight. Only slight changes from 1.0.34 that this bmw is running already. I am though not able to test IAC output tonight, as we never use that in our racecars here.
Ok,thanks.
I have 2 of this shitty cables,and after an hour of suck!n,i installed cable #2.with this,the upload of firmw.36 went smooth,and then i uploaded my mtt's.i also looked into MT and everything was fine.IAC can be disabled of course,but to be honest,i need some validation that it works fine.
Good to know that it worked better with the other cable, are they branded, so you can warn other people for the non working cable?
Since 1.0.34 (that i tried in car without problems), the only change is that it now is less likely to leave coil active if loosing trigger at high RPM.
Also minor changes to megatune .ini. As i wrote before, will report as soon as i load this into a car. This BMW is 80 km away, so i likely cant report until approx 24.00 tonight.
//Emil
We installed the direct inputs of Launch and ALS.It worked fine for weeks,but now sometimes (1 from 30 trys) the pressed ALS switch just SHUTS DOWN the ECU!!!
Whats happening?
Happened only 2 times,and i had to concentrate on driving away,and since then i couldnt reproduce the sympthom
It's likely a wiring problem, because ALS activation hasn't been observed to shut down ECU.
Actually, "shut down" is only possible if it's a wiring problem.
If it's a firmware problem, it could reboot but not shut down.
Refining what "shut down" means in this case:
- LCD backlight goes off ?YES
- this indicates there is a HW (likely wiring) problem. The LCD backlight is NOT controlled by the processor so if it goes off, it indicates that power was cut or shorted
- can you measure DC voltage on EC36-pin28 (5V) ?
- Does that drop to 0V when button pressed ? => if so, a clear indication of HW (wiring) issue
- can you measure DC voltage on the ALS button ?
- if it ever goes above 5V or below -0.5V, that can kill the AVR (so it shouldn't happen).
- megatune communication goes away ?NO (not 100%sure)
- When button pressed, engine stopped immedately.
- But does it start immediately even while button is pressed ?
- Or it stays in "blackout" and only starts when button released ?
- fuel pump relay output ?
- other outputs ?
suspect:
- 5V is pulled to GND too strong (a short between 5V and GND ?)
- what is the pullup resistor value ?10k
- what is the GND return point of the switch ?Sensor GND
- cable-length ? approx. 1m
- any noisy lines nearby, like ignition ?NO
If the problem is GND noise, a 5V1 zener (red-black SOD80 small cylinder with endcaps in rescue2 kit) parallel with the switch for "transient protection" purpose, between GND and switched input could help:
- marked (black circle) goes to switched input
- the other (non-marked) cap goes to GND, EC36pin26
Closer to the EC18pin.. (ALS input) should be preferred.
However, if wired right, this "transient protection" zener shouldn't be necessary.
---
During the Boostcontrol runs i experienced some weird injector correction behaviour.Forunately we made logs so furher investigation is easy.
here the log:
see it at 9037.410 sec.
Here you can see that PW is immediatly dropping from 11.7 to 7.4
WHILE ENGINE IS AT FULL LOAD!!!!
This is completely not acceptable.
EGO limits were plus/minus 3%,and EGO was switched off at full load,with RPM and TPS 'switches'.
I experienced it constantly right after starting the engine,so it might be associated with EGO swithing on.