6395 and async and sync
Thread Starter
Junior Member
Joined: Mar 2005
Posts: 97
Likes: 0
From: Sweden
Car: El camino 70 ss
Engine: corvette lt1 94
Transmission: 4L60E
6395 and async and sync
What does the async to sync threshold and sync to async threshold vs map/rpm do (diffrent values in bjym to my bjlk).
I think my cam and rear end ratio(3.08) vs trans 0.70 is the pain in the *** for fuel mil(or my foot).
Going to try change the shift points and lockup to higher mph/rpm
to see if it lower the dc a bit
I think my cam and rear end ratio(3.08) vs trans 0.70 is the pain in the *** for fuel mil(or my foot).
Going to try change the shift points and lockup to higher mph/rpm
to see if it lower the dc a bit
Last edited by honken; Dec 7, 2005 at 10:37 AM.
Those thresholds determine when the injector firing scheme switches from synchronous (injectors fire alternately with each DRP) to asynchronous (injectors fire simultaneously at 40 cycles per second) and vice-versa. In my experience with this PCM, those thresholds have no bearing on fuel economy or drivability. Some $0D bins only use synchronous mode at idle and asynchronous off idle with no issues. HTH
Supreme Member
iTrader: (2)
Joined: Jan 2002
Posts: 9,962
Likes: 5
From: Moorestown, NJ
Car: 88 Camaro SC
Engine: SFI'd 350
Transmission: TKO 500
Axle/Gears: 9-bolt w/ 3.23's
I think its 80 Hz since thats the speed the loop updates the PW, not that it really matters for the topic at hand.
Im not quite sure why they switch to async when off idle using all those threasholds but Id say its to spread the firings out and increase the available firing time since a lower percentage of time will be needed for opening/closings. You could probably just use sync firings most of the time. With the old computers, async was used so the ecm could withold firings if the PW was too low but IIRC, thats no longer the case. Id have to go back and see for sure.
Im not quite sure why they switch to async when off idle using all those threasholds but Id say its to spread the firings out and increase the available firing time since a lower percentage of time will be needed for opening/closings. You could probably just use sync firings most of the time. With the old computers, async was used so the ecm could withold firings if the PW was too low but IIRC, thats no longer the case. Id have to go back and see for sure.
Supreme Member
iTrader: (1)
Joined: Jan 2002
Posts: 4,432
Likes: 1
From: garage
Engine: 3xx ci tubo
Transmission: 4L60E & 4L80E
Has anyone verified that it ever goes into async mode?
I only see aynce being necessary for AE when it needs "to be done quick" or when big fuel injectors are used. The factory never used real big injectors though.
I only see aynce being necessary for AE when it needs "to be done quick" or when big fuel injectors are used. The factory never used real big injectors though.
Senior Member
Joined: Oct 1999
Posts: 6,621
Likes: 2
Car: 91 Red Sled
Axle/Gears: 10bolt Richmond 3.73 Torsen
Originally posted by junkcltr
Has anyone verified that it ever goes into async mode?
I only see aynce being necessary for AE when it needs "to be done quick" or when big fuel injectors are used. The factory never used real big injectors though.
Has anyone verified that it ever goes into async mode?
I only see aynce being necessary for AE when it needs "to be done quick" or when big fuel injectors are used. The factory never used real big injectors though.
I don't see async being necessary... ever...
To do AE, just add it to the final pulse width. If the pulse width gets so high that the injector is static then the remander is carried over to the next pulse width.
Honestly, I think the guys programming the TBI ecm/pcm's might not have been the brightest bunch of guys. From the looks of the code vs other code I'd say they weren't getting much help from the smart ones
. Either that or there was a conspiracy to keep TBI from EVER becoming a hot rod solution.In reality there is very little if any measurable difference between using async vs sync so long as the calculations are done correctly and the same amount of fuel is delivered.
Maybe, just maybe, the later TBI pcm's used async off idle to get rid of the AE async vs sync missing fuel problem
. Either they knew it was there and decided it would just be easier to run in full async OR they didn't know it was there and were beating their heads against the wall until somebody made a robust choice to run async all the time. Last edited by JPrevost; Dec 8, 2005 at 08:00 PM.
FWIW it is only the V-6 applications, TBI and CPI, that go asynch immediately off idle from what I have seen. The V-8 TBI applications stay in synch til around 2k RPM and about 85 kPa MAP. That would kinda tend to disprove the "spreading out the firings" theory as there is 25% less DRP's/RPM, hence 25% less firings per RPM with a V-6. The AE routines seem to work well although I cannot say the same for the calibrations (MAP AE is seriously lacking in the cals) even though it is asynch so I cannot, for the life of me, figure out why GM did this. Maybe they were just lazy.
Trending Topics
Supreme Member
iTrader: (1)
Joined: Jan 2002
Posts: 4,432
Likes: 1
From: garage
Engine: 3xx ci tubo
Transmission: 4L60E & 4L80E
I really don't know much about this stuff. At 1000rpm it would be about 20ms between DRP on a V6. Done quick would be adding fuel for AE at a rate of 12.5ms instead of 20ms. That is "done quick". Not fact, just my theory.
Thread Starter
Junior Member
Joined: Mar 2005
Posts: 97
Likes: 0
From: Sweden
Car: El camino 70 ss
Engine: corvette lt1 94
Transmission: 4L60E
I lookt at my 94 bjlk 6395 vs 95 bjyk bin 7427 (350 lo5).
Async to sync fuel rpm thresh = bjlk 1200 rpm (2000 rpm bjyk).
sync to async fuel rpm thresh = bjlk 1300 rpm (2100 rpm bjyk).
Async to sync fuel map thresh = bjlk 45.78 kpa (81.20 kpa).
Sync to async fuel map thresh = bjlk 51.68 kpa (87.11 kpa).
This is the only async and sync values thats diffrent.
Async to sync fuel rpm thresh = bjlk 1200 rpm (2000 rpm bjyk).
sync to async fuel rpm thresh = bjlk 1300 rpm (2100 rpm bjyk).
Async to sync fuel map thresh = bjlk 45.78 kpa (81.20 kpa).
Sync to async fuel map thresh = bjlk 51.68 kpa (87.11 kpa).
This is the only async and sync values thats diffrent.
Joined: Mar 2000
Posts: 1,692
Likes: 1
From: Corona
Car: 92 Form, 91 Z28, 89 GTA, 86 Z28
Engine: BP383 vortech, BP383, 5.7 TPI, LG4
Transmission: 4L60e, 700R4, 700R4..
Axle/Gears: 3.27, 2.73
It kind of seems opposite to me - are you sure there isn't a mistake in the .ecu or .xdf?
Typically Async would be used at low loads, not high.
Has anyone measured the PWs with an oscilloscope to see if it's correct?
Typically Async would be used at low loads, not high.
Has anyone measured the PWs with an oscilloscope to see if it's correct?
Originally posted by RednGold86Z
It kind of seems opposite to me - are you sure there isn't a mistake in the .ecu or .xdf?
Typically Async would be used at low loads, not high.
Has anyone measured the PWs with an oscilloscope to see if it's correct?
It kind of seems opposite to me - are you sure there isn't a mistake in the .ecu or .xdf?
Typically Async would be used at low loads, not high.
Has anyone measured the PWs with an oscilloscope to see if it's correct?
Supreme Member
iTrader: (2)
Joined: Jan 2002
Posts: 9,962
Likes: 5
From: Moorestown, NJ
Car: 88 Camaro SC
Engine: SFI'd 350
Transmission: TKO 500
Axle/Gears: 9-bolt w/ 3.23's
I have verified that it does indeed work as said above via hacking the code.
The only reason I can see is to increase the available PW at high RPMs while allowing for use of injectors small enough to give reasonable PWs at low loads/idle. In the older stock fbody tbi cals, the DC was in the low 90's, so theres definatly evidence that they where trading off DC at high rpms for DC at idle. Having async frees up a few more percent at high rpms.
The only reason I can see is to increase the available PW at high RPMs while allowing for use of injectors small enough to give reasonable PWs at low loads/idle. In the older stock fbody tbi cals, the DC was in the low 90's, so theres definatly evidence that they where trading off DC at high rpms for DC at idle. Having async frees up a few more percent at high rpms.
Originally posted by dimented24x7
I have verified that it does indeed work as said above via hacking the code.
The only reason I can see is to increase the available PW at high RPMs while allowing for use of injectors small enough to give reasonable PWs at low loads/idle. In the older stock fbody tbi cals, the DC was in the low 90's, so theres definatly evidence that they where trading off DC at high rpms for DC at idle. Having async frees up a few more percent at high rpms.
I have verified that it does indeed work as said above via hacking the code.
The only reason I can see is to increase the available PW at high RPMs while allowing for use of injectors small enough to give reasonable PWs at low loads/idle. In the older stock fbody tbi cals, the DC was in the low 90's, so theres definatly evidence that they where trading off DC at high rpms for DC at idle. Having async frees up a few more percent at high rpms.
Thread
Thread Starter
Forum
Replies
Last Post






