V3 Studio 3.065 (new software 3.065b available)

Yes it is possible. Probably next week there will be new V2 build I try to incorporate the change.

2 Outputs. G8 and G16 to a Smart Double Fire 4 Post Dual Coil Pack.

Just ignore the warning message and red color. Also make sure you dont select wasted spark as a mode. In wasted spark mode it pairs automaticaly outputs based on firing order.

The warning message here is a bug. It will be fixed for next build.

Ah okay I just updated from 3.064 to 3.065 and the functions are now available for flat shift. Thanks for your response.

hi Jadzwin
do you think you will be Abel to add the rotary switch under the boost target limits > rotary limit .
to a lot of us this will be a much easy way to set up the boost when using the rotary switch

look forward to hearing from you

Upgraded my classic yesterday, what an improvement in idle control and accell enrich. The Tune display no longer autopopulates the 9 data slots below the lambda/target bars. Is this intended behavior? Obviously not a big deal but it was more convenient when it did.

There used to be a log channel that listed active fuel corrections, I can’t find it anymore. Can this be added again?

Ditto for ignition corrections.

There are such log channels for both ignition and fuel

I think legs and I were referring to the graph view of the logs, but given how many possible corrections there are, I can see why the old v1 way of reporting the corrections on the graphs wouldn’t work in v3. We’ll just need to have those tables open when looking for which correction is being applied.

I was, but this makes sense. I’ve been trying to figure out why my idle injector pw keeps changing very slightly every second or so, and was looking for a graph that i could match with the pulse width changes. But with how many corrections there are its probably not reasonable to have graph channel for it.



Peep the difference between Tps voltage and analog 6. Depending on what i choose as main signal input The voltage changes. Override DC was checked :white_check_mark: I think this is a bug

It is not a bug. This is intentional behavior to ensure that the TPS channel always displays the TPS sensor voltage. If you use the TPS input as a PPS input, then that voltage will be visible on the PPS channel instead.

Thankyou, that makes sense.

Can we get MAF logging input table on the next update?

Thanks

Updated today. Successful removal of the ignition output conflict pop up window. Thank you :blush: