OSE $12P Teaser

[Holden202T]

its just to get the wideband readings in the data stream ....

i'm not sure about others, but for me i had my wideband controller connected to a datalogger which also had rpm pulse and map sensor setup on it ... this was the only way i could log wideband data that would allow me to cross reference the map and rpms to then change the right point on the VE table ....

so now its all there in the one device meaning i no longer need my datalogger and i can tune the WOT regions of the map where the narrow band doesn't log blms for.....

also means i can see what the computer is doing and the wideband at the same time ....

i guess if people were keen enough to write the code it could be used to tune while you drive but at the moment its just another sensor in the ALDL stream!

[antus]

looks like its working great on 4 cylinder too

[delcowizzid]

sweet the GEM a runner again

[VL400]

Thought I would just give a quick update of whats happening with the code. Have been testing a new 3D lookup routine that can take a 16bit row argument (the factory one is 8bit arguments only), this means a single table that goes from 400-8800RPM will be used. This is instead of the two spark tables (400-2400RPM and 2400-7200RPM) and 4800RPM limited tables like normal $12 code, this should make tuning a little easier.

$12 Pro Extra Features Over OSE $12S...
- Spark Output For All Ref Angles Between 0-90deg
- ID Memcal Number Of Cyl
- 4, 6 or 8 Cyl
- Added Knock Counts And Current VE To ALDL Mode 1 Message 0 In Bytes 45 and 46
- VS or VR Anti-theft Option
- Wideband Integration - Raw 0-5V Wideband A/D Is In L00A6 And Part Of Message 0
- Map Switch Function Using B9
- Instant Fuel Economy Changed So Its 0L/100kms When Stationary (not 100% accurate as fuel is being consumed still, makes it look better on screen)
- Rev Limit Functions Include Soft Touch Rev-Limit
- Closed Throttle VE
- Ignore Knock Counts
- 16 Bit 3D Lookup for extended tables




Lots more to come, will keep you updated

[Holden202T]

this means a single table that goes from 400-8800RPM will be used. This is instead of the two spark tables (400-2400RPM and 2400-7200RPM)

don't you mean VE not spark ?

does the table go up in the same increments the same as the two tables, ie. 200rpm increments till 2400 then up by 400rpm increments ? i assume it would otherwise the 8800 rpm table in 200 increments would be MASSIVE!

good to see your slowly getting there with it, will be a good full feature bin when its done!!

[VL400]

yeah that one! haha

400RPM increments from 400-8800RPM, having a table with 200RPM increments for part and 400RPM for the rest is possible but am limited to the overall number of entries in the table (around 256) - could prob make this limitation bigger though.

[delcowizzid]

thankyou thankyou thankyou LOL ive allways hated those double VE tables they just piss me off good to see them gone you the man.

[Holden202T]

one VE table will work a hell of alot better with all the histograms in scanner pro too

i don't think the lack of lower rpm resolution is going to make that much difference to the way the engine performs either .... bring it on

[VL400]

I still have to test it properly but have removed the table size limitation, so the VE can have the 200RPM breakpoints below 2400RPM and then 400RPM from 2400RPM to 9600RPM.

What breakpoints would people like to see for the spark advance and target AFR tables? Target AFR with 400RPM breaks should be fine, but would spark benefit from the higher resolution 200RPM breaks below 2400RPM? I have not had a proplem with 400RPM but if anyone has tuning experience please share your thoughts!

[Holden202T]

i'd like them all to match .... i've never understood why one table has say 85 and 95 kpa then another table doesn't ....