Timing calculation on CA18
Moderator: Matt
-
- Posts: 112
- Joined: Wed May 03, 2006 5:51 pm
- Location: Id, USA
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.
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.
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
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
There is a separate thread on this covering the timing reported by NIStune
viewtopic.php?p=2508&highlight=#2508
viewtopic.php?p=2508&highlight=#2508
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...
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...
Please no more posts to this thread. Its been fixed with a software workaround (see bug thread)
viewtopic.php?p=3098#3098
viewtopic.php?p=3098#3098