Timing calculation on CA18

Vetal · Post by **Vetal** » Fri Jul 06, 2007 9:20 pm

OK, after 10+ hours spent doing runs and analysing logs, I can confirm that:
a) knock ignition map changes don't affect torque/power
b) reported igniton is affected by knock map; changing main map doesn't influence reported timing

GZ@hybridka · Post by **GZ@hybridka** » Sat Jul 07, 2007 8:52 am

So then in other words what you are saying is that Nistune reported timing value does not directly correspond to actual ignition timing?

Have you done any checking with a timing light as well?

I am only remotely familiar with this system only having looked at the code itself. The timing value I see that Nistune reports appears valid.

From your description though it would seem that perhaps the code version you are using works differently than others (as Matt mentioned there are a few, I think in another post) and different from the version I am reviewing perhaps.

PM me a copy of the binary you are working with (original, pre-nistune) and ill have a look.

Vetal · Post by **Vetal** » Sat Jul 07, 2007 9:21 am

Yes this reported timing apparently doesn't correlate with real ignition timing.
I'll post you the bin when I get to other PC

Vetal · Post by **Vetal** » Sat Jul 07, 2007 10:09 am

PM sent

Vetal · Post by **Vetal** » Mon Jul 16, 2007 1:54 am

I've copied regular ign map to knock map, and reported timing is now corelated with map, +6 degrees

Vetal · Post by **Vetal** » Fri Aug 31, 2007 8:04 pm

Any news on this?

Matt · Post by **Matt** » Sat Sep 01, 2007 2:31 am

Sorry no news on this yet. This is in my 'investigate' list but currently at the moment im running through the bug list trying to fix up higher priority issues like logging at this stage

Dont know where Gabe has gone and if he has a change to look at the binary file that you posted

When I get a CA18 ECU back on the bench again, will look into these bunch of queries together and also knock detection

Matt · Post by **Matt** » Fri Mar 14, 2008 2:29 pm

There is a separate thread on this covering the timing reported by NIStune

viewtopic.php?p=2508&highlight=#2508

Vetal · Post by **Vetal** » Fri Mar 14, 2008 8:29 pm

Saw this. But didn't really understand what should I do?

Matt · Post by **Matt** » Sat Mar 15, 2008 1:58 am

See thread above for details (updated tonight)

Okay I think i've got the correct memory address for this now

Display - Consult RAM trace
Address 100F
Length 1
Ageout 20
Tick decimal
Click start

Timing ~= 110 - displayed value - 4

Now this does require a firmware update to correct the address to display.

But since quite a few boards have this in them already I was just thinking that I might be able to directly query this address just for CA18 ECUs and override the currently displayed value. See what I can do in the next few days...

Vetal · Post by **Vetal** » Sun Mar 16, 2008 7:42 am

Will keep watching

Matt · Post by **Matt** » Wed Mar 19, 2008 11:20 pm

Please no more posts to this thread. Its been fixed with a software workaround (see bug thread)

viewtopic.php?p=3098#3098