There is a new software 3.019.
Three critical notices:
Cranking fuel now based on VE not injectors PW so you need to adjust the Cranking tables first. It is a big chance that the engine will start with default 100%
The log files saved with the previous versions will not read correctly with this version.
The calibration of WBO circuit should be performed again. Disconnect the sensor, select LSU 4.9 or 4.2 in WBO options and then use WBO calibration tool from tools/menu. The calibration value appears in the Logbook and it should be around 4000
with corrections. so warmup corrections also helps.
The only difference is that lambda target for cranking is defined in cranking parameters not in fueling/lambda target
Not tested 019 yet, but with 018 lambda does not wake up until something like 30 secs after engine fires up. I have set heater always active.
I hope I can post logs after this weekend.
Lambda target is a part of fule dose calculations. If you have proper value of lambda for given lambda target, then you can just change the lambda target to get desired lambda.
So lambda target is not connected to lambda sensor. Lambda sensor is required if you want to use short term trim to adjust fuel dose in the closed loop.
And if you want to measure lambda during cranking, you need to use option Heater always active, turn ignition on, wait when the sensor heats up and lambda starts to show lean, and then cranking.
But it is not advised to use Always active heater in normal engine use, as it will break the sensor sooner or later.
i am missing gearcut options. and in flat shift i am missing gearcut time ??
no idea how to make that with fuction.
i did see i need to use fuction to use analoge CAN signal.
i do have Canbus DBW control so thats good for DCT and PDK and 8HP.
but the gearcut would be nice thanks !
Ow and i found a bug !
When you try to use analogue can signal for custom ignition table axis,
you cannot give 5 volt in or 5000mv in ??? how do we calibrate axis ??
50 = 5volt ?? or ?? bug in software ?
and a request.
i have target RPM on canbus. how do i make the ecu adjust Rev limiter to target rpm ??
in maxx ecu this is very easy. in ecumaster its almost impossible even in pro8
another nice thing would be to use target rpm for blip table for rev matching.
no idea how to setup.
now i use canbus Dbw as blip and make tuning in gearbox controller.
if we can adjust rev limiter to target rpm, if we overblip it hits rev limiter. or 200 rpm above target rpm.
same for upshift. when the gearbox start disconnecting clutch, target rpm is set.
and engine ecu cuts sparks to slow engine down, so clutches have less load.
very nice feature. works perfectly with maxx ecu. no possibilty in ecumaster.
Gear cut - it will be implemented in next month from scratch with fully closed loop control
Flat shift - flat shift is a strategy for conventional throttle to allow change gears with he throttle pedal fully pressed. It allow the RPM to drop for defined Cut off rpm and eventually keep them if the driver doesn’t release the clutch.
I’m not sure if I understand you about custom correction. When I choose analog input I can enter any value between 0 to 5V in the axes definition. Could you show me reproduction as it sounds like a bug ?
Btw. there is a bug with custom ignition correction tables in current version (Y axis interpolation doesn’t work). It is already fixed and will be released next week.
To add custom Rev limiter target over CAN seems to be easy. I add log channel CAN-BUS Rev limiter target. It will be normally 200000. So using custom CAN you can override this value and control rev limiter. In the case of message timeout this value will be 20.000 again. I add it for next build.
Hi, yes ignition correction axis can analoge 0-5 volt. no decimals. something is off.
the flat shift i use it now to creat a “DSG Fart” using it for 4 to 6ms during shift. (v2.169)
but when we have new gearcut, it will probably all work out fine.
about canbus revlimiter, there should be posibility to activate with a can switch.
so i can activate during Blip or Cut from in gearbox ecu.
as target RPM is send out faster and longer then the revlimiter should be active.
but another solution would be custom Axis on the custom revlimiter table
now we have rotary switch option. if i can put canbus signal there and calibrate
or canbus analogue signal, that should work perfectly.
thats even little adjustment.
then i can choose what the rev limiter should be for target RPM.
example how 1 gearbox ecu uses canswitchboard adress to communicate with emu black :
there is something strange with custom can stream.
i try to send canswitch 1-12 on canstream to id 700 offset o to 7
for switch 1 to 8.
but not all of them work. i imported the settings from v2 canstream file.
and in dashboard if i select a dashboard does custom canstream reading and sending work now ? as there whas a problem in v2. (dont have dash now in this car)
