@Ben - DIYPNP hardware latency?
#1
Thread Starter
Elite Member
Joined: Mar 2006
Posts: 1,558
Total Cats: 105
From: Schwarzenberg, Germany
@Ben - DIYPNP hardware latency?
Hi Ben, (I adress this to you as you might have the best access to the data),
have you found that you need to set the (ignition) hardware latency with the DIYPNP and the 99/00 Miata - maybe at your or the DIYautotune-shop-car?
I will try to scobe it at my engine, when it is up and running again in April. Just wanted to check out some other data...
Thanks
have you found that you need to set the (ignition) hardware latency with the DIYPNP and the 99/00 Miata - maybe at your or the DIYautotune-shop-car?
I will try to scobe it at my engine, when it is up and running again in April. Just wanted to check out some other data...
Thanks
#7
If those cars have properly tuned spark maps, then I would not go back and remove C27, since you've tuned around the latency as your commanded advance will be greater than actual. If you then pull C27, your timing will advance more at higher rpm, which might cause det.
The newest version of the microsquirt module is coming without C27 installed.
The newest version of the microsquirt module is coming without C27 installed.
#11
I warned about delays in the trigger signal in some thread about discussion of filters.
FWIW A "2 pole" RC filter will filter out high frequency noise better than a single pole filter for a given delay.
This is why it's good to have 2 values for setting timing errors in the software:
Basically for "y-intercept" and one for slope.
You set all timing to 10*, then you adjust the first value to get the correct timing with a light at idle, and the other at some high RPM say 5000 RPM. There is slight interaction so you repeat.
FWIW A "2 pole" RC filter will filter out high frequency noise better than a single pole filter for a given delay.
This is why it's good to have 2 values for setting timing errors in the software:
Basically for "y-intercept" and one for slope.
You set all timing to 10*, then you adjust the first value to get the correct timing with a light at idle, and the other at some high RPM say 5000 RPM. There is slight interaction so you repeat.
#12
You'd want to remove C30 if it's there.
Jason, MS2 does what you describe.
Important to note, there is a difference between hardware latency and software latency.
I warned about delays in the trigger signal in some thread about discussion of filters.
FWIW A "2 pole" RC filter will filter out high frequency noise better than a single pole filter for a given delay.
This is why it's good to have 2 values for setting timing errors in the software:
Basically for "y-intercept" and one for slope.
You set all timing to 10*, then you adjust the first value to get the correct timing with a light at idle, and the other at some high RPM say 5000 RPM. There is slight interaction so you repeat.
FWIW A "2 pole" RC filter will filter out high frequency noise better than a single pole filter for a given delay.
This is why it's good to have 2 values for setting timing errors in the software:
Basically for "y-intercept" and one for slope.
You set all timing to 10*, then you adjust the first value to get the correct timing with a light at idle, and the other at some high RPM say 5000 RPM. There is slight interaction so you repeat.
Important to note, there is a difference between hardware latency and software latency.
Thread
Thread Starter
Forum
Replies
Last Post
Mikel
MEGAsquirt
4
09-28-2015 04:46 PM