For the client windows - it wold be nice to be able to set width of the columns in the windows independently of the window size. i.e. for the coil setup there is no need the first column (spark distribution) to be that wide, while the 2nd column (Coils) could be wider. It’s useful when putting multiple windows in same desktop. Thank you.
Hi,
Can we get flat shift gear cut time like in v2 ??
used it for dsg fart under WOT… 
something else.
where do you define parameter torque reduction request ?
on v2 you could scale the cut percentage in relation with MAP.
now it says torque reduction request ??? where and how is this defined ??
then another issue, gearbox is gear is send on canbus.
target gear is send on canbus
parameters gearbox, i set to canbus
how do i define the ratios then ? when i want to use rev matching ?
i can set up everything in gearbox controller but i dont want that.
i want to set everything up in black. and just send shift up and down.
or shift and current gear target gear. let black do the rev matching.
in v2 gearbox gave variable blip. works fine.
and gearshift cut is given depending om map sensor value and shift up flag.
my scope log doesn’t show anything why? I can’t make it work
I raised it but to no avail
You need your trigger setup working and sync so that scope shows you something. Without trigger = no sync = no scope = no engine running because the emu doesn’t know where the engine’s at.
If it sometimes starts with waisted spark that could mean that the primary trigger is sometimes giving signal but secodary is not there to get sync.
Correct me if I’m wrong.
Is there a way to get a scope without sync? Or is scope only possible when sync happened?
Charge temp table…what about making this table just as a function of airmassflow like lambda delay? Would make it easier to handle and safe some memory.
Would in general make more sense since this function is actual depending on airmassflow.
Jadzwin, can you hepl me? I try two different DQ500 software on V3, but problem present. I can’t speed up, the transmission doesn’t want to shift down.
I
Qualcuno sa darmi indicazioni su settaggio camme sync vr6 golf ?
There is no need to sync. There just must be any trigger signal on crank or / and cam inputs.
So if your scope shows nothing then probably the input configuration is not correct
We are discussing it as it seems to be very good idea.
But we need to make tests how it perform in real world first
Please show your torque table. Also you can try to put 5 or 10 into torque losses table.
Also here there is an message from someone with DQ500 that say it works much better than with V2. Please try to contact this person.
TB make wired noises while oscilate…it could be eliminated by friction factor map but i need one more colum on X axis 
Also should be ignored but why there is no deadband settings like in PRO?
The deadband will be introduced in version 3.030 this week.
I’ve just suggested solution just for now.
The noise is not a problem, it just sounds weird 
Sometimes, when working offline, it happens that when I open a project and go to the graph log and want to load saved log, the channels displayed are not the ones I was expecting to see.
I could not replicate that at this moment, so from top of my head in the screen below I’ve seen at least:
- CAM 2 VVT instead Ignition angle (as intended and seen on the screen below)
- MAP readings instead TPS
- Analog something instead CAM sync trigger tooth or was it instead Idle Valve DC?
Please let me know if you find any reproduction of it. Once or twice I had a feeling that some channels are different that should be, but I have no reproduction
Would that be possible to add “Disable when no RPM” in EWG function?
Been working on V3 couple of months and got most things Ironed out including idle with ignition PID and airflow PID but have found that when my OEM coolant fan comes on it’s throwing off the closed loop and it’s not as good as it is when fan is off. I can’t find it in the software, is it possible to add a % increase to the Active State Airflow when the coolant fan is activated, on V2 I ran between Coolant fan 5-7% DC Correction.
Think I also found a bug in the logging values - Idle air PID correction value doesn’t read less than 0% on the log. It continues to read a positive value but drops below zero on the axis.
Screen shot attached shows 0, prior to it positive values and after it the values increase again but the graph drops below 0
According Idle Air PID correction you found a bug with PID out min clamped to 0.
The result is the PID airflow correction will never be negative.
It will be fixed for next version