Need help on new SF3 programmer on Revs per mile
Need help on new SF3 programmer on Revs per mile
I have bought a SF3 programmer from troyer performance and i am waiting on my custom tunes, but so far with just the canned tunes it shifts alot better and just seems to be a better ride. I have put in the 87 octane tune and changed my gear ratio to 4.56 gears an tried to change my rev per mile to get my speedo and odometer correct but no luck, i have entered the rev per mile that i figured out from the website glenn at troyer gave me and also did some searching on the net and it all matchs up to 560 rev per mile and it is 20to 30 MPH off on the speedo and on stock setting it is only 5 MPH off, i have 37x13.5x18 mickeythompson baja MTZ tires. What the hell is going on does anyone know or has had this problem.
I guess the first dumb question is: Do you have 4.56 gears? 
Based on the specifications from Mickey Thompson's website, the O/D on those tires is 36.8" which yields a rev/Mile closer to 548, not 560. This is a minimal difference though and wouldn't account for 20-30 MPH off.

Based on the specifications from Mickey Thompson's website, the O/D on those tires is 36.8" which yields a rev/Mile closer to 548, not 560. This is a minimal difference though and wouldn't account for 20-30 MPH off.
I guess the first dumb question is: Do you have 4.56 gears? 
Based on the specifications from Mickey Thompson's website, the O/D on those tires is 36.8" which yields a rev/Mile closer to 548, not 560. This is a minimal difference though and wouldn't account for 20-30 MPH off.

Based on the specifications from Mickey Thompson's website, the O/D on those tires is 36.8" which yields a rev/Mile closer to 548, not 560. This is a minimal difference though and wouldn't account for 20-30 MPH off.
I noticed the same thing with mine and here is a quote from the SCT website.
IMPORTANT NOTICE REGARDING X3 & SF3 Power Flash Devices sold prior to July 25th, 2008:
SCT has recently updated the firmware for all X3 & SF3 devices. These devices now have different firmware that will effect all future updates for your device.
--------------------------------------------------------------------------------
X3 devices part #3000 sold after July 25th, 2008 will now only be used for custom tuning and will no longer contain pre-loaded tunes. The SF3 device part #3015 will hold 3 custom tunes and will ship with pre-loaded tunes as in the past.
--------------------------------------------------------------------------------
If you have purchased an X3 device part #3000 or SF3 device part #3015 prior to July 25th, 2008, your device is now considered an SF3 device part #3015, even though the device stickers may state it is a part #3000. When updating your device with any future firmware or tune revisions, you must use the SF3 part #3015 device updates or you will receive an error when updating the device.
--------------------------------------------------------------------------------
Devices sold after July25th, 2008 should use the matching firmware for the part number on the device sticker.
IMPORTANT NOTICE REGARDING X3 & SF3 Power Flash Devices sold prior to July 25th, 2008:
SCT has recently updated the firmware for all X3 & SF3 devices. These devices now have different firmware that will effect all future updates for your device.
--------------------------------------------------------------------------------
X3 devices part #3000 sold after July 25th, 2008 will now only be used for custom tuning and will no longer contain pre-loaded tunes. The SF3 device part #3015 will hold 3 custom tunes and will ship with pre-loaded tunes as in the past.
--------------------------------------------------------------------------------
If you have purchased an X3 device part #3000 or SF3 device part #3015 prior to July 25th, 2008, your device is now considered an SF3 device part #3015, even though the device stickers may state it is a part #3000. When updating your device with any future firmware or tune revisions, you must use the SF3 part #3015 device updates or you will receive an error when updating the device.
--------------------------------------------------------------------------------
Devices sold after July25th, 2008 should use the matching firmware for the part number on the device sticker.
Last edited by slmartin.71; Jan 22, 2009 at 10:06 PM.
Well, the quote from SCT is as clear as....!
I dunno, laford. You've got a HUGE error in the speed. As ASEMechanic says, though, even changing to 548 rev per mile isn't going to get you anywhere near the ballpark. You've got somewhere in the neighborhood of a 30+% error in speed. You didn't say if it was indicating too fast or too slow. If you are indicating too slow, it's because the PCM thinks your tires are smaller than they really are. You'd need to increase their circumference - which reduces the number of revs per mile by about 30% or, down to 392. If you're indicating too fast, you'd need to increase the revs per mile to about 728.
Both of these are ridiculous figures. I think there is something wrong with the programmer or, you are making some small (but significant) mistake when you are entering the revs number. Since I don't have an XCal, I can't give you better advice than this.
Actually, I can: Get Troyer on the phone and have them "talk" you through the setting up of this data through the XCal as you do it on your truck. That way, both you and they would know if you are doing it right.
If Troyer is as reputable as I think he is, TP will do this with you. I KNOW Bill (ASEMechanic) at PHP would do it for a Gryphon, so, give it a try.
- Jack
I dunno, laford. You've got a HUGE error in the speed. As ASEMechanic says, though, even changing to 548 rev per mile isn't going to get you anywhere near the ballpark. You've got somewhere in the neighborhood of a 30+% error in speed. You didn't say if it was indicating too fast or too slow. If you are indicating too slow, it's because the PCM thinks your tires are smaller than they really are. You'd need to increase their circumference - which reduces the number of revs per mile by about 30% or, down to 392. If you're indicating too fast, you'd need to increase the revs per mile to about 728.
Both of these are ridiculous figures. I think there is something wrong with the programmer or, you are making some small (but significant) mistake when you are entering the revs number. Since I don't have an XCal, I can't give you better advice than this.
Actually, I can: Get Troyer on the phone and have them "talk" you through the setting up of this data through the XCal as you do it on your truck. That way, both you and they would know if you are doing it right.
If Troyer is as reputable as I think he is, TP will do this with you. I KNOW Bill (ASEMechanic) at PHP would do it for a Gryphon, so, give it a try.
- Jack
Last edited by JackandJanet; Jan 22, 2009 at 10:32 PM. Reason: Small clarification
Well, the quote from SCT is as clear as....!
I dunno, laford. You've got a HUGE error in the speed. As ASEMechanic says, though, even changing to 548 rev per mile isn't going to get you anywhere near the ballpark. You've got somewhere in the neighborhood of a 30+% error in speed. You didn't say if it was indicating too fast or too slow. If you are indicating too slow, it's because the PCM thinks your tires are smaller than they really are. You'd need to increase their circumference - which reduces the number of revs per mile by about 30% or, down to 392. If you're indicating too fast, you'd need to increase the revs per mile to about 728.
Both of these are ridiculous figures. I think there is something wrong with the programmer or, you are making some small (but significant) mistake when you are entering the revs number. Since I don't have an XCal, I can't give you better advice than this.
Actually, I can: Get Troyer on the phone and have them "talk" you through the setting up of this data through the XCal as you do it on your truck. That way, both you and they would know if you are doing it right.
If Troyer is as reputable as I think he is, TP will do this with you. I KNOW Bill (ASEMechanic) at PHP would do it for a Gryphon, so, give it a try.
- Jack
I dunno, laford. You've got a HUGE error in the speed. As ASEMechanic says, though, even changing to 548 rev per mile isn't going to get you anywhere near the ballpark. You've got somewhere in the neighborhood of a 30+% error in speed. You didn't say if it was indicating too fast or too slow. If you are indicating too slow, it's because the PCM thinks your tires are smaller than they really are. You'd need to increase their circumference - which reduces the number of revs per mile by about 30% or, down to 392. If you're indicating too fast, you'd need to increase the revs per mile to about 728.
Both of these are ridiculous figures. I think there is something wrong with the programmer or, you are making some small (but significant) mistake when you are entering the revs number. Since I don't have an XCal, I can't give you better advice than this.
Actually, I can: Get Troyer on the phone and have them "talk" you through the setting up of this data through the XCal as you do it on your truck. That way, both you and they would know if you are doing it right.
If Troyer is as reputable as I think he is, TP will do this with you. I KNOW Bill (ASEMechanic) at PHP would do it for a Gryphon, so, give it a try.
- Jack
Trending Topics
I received a message from SCT that they passed it on to the calibration department and i will have to wait until the next updated tune version to get it corrected, and that was about the tire size and speedo they never even said anything about the tune options. They are saying that it will only take one option at a time it will not save more than one. I am so fed up i sent glenn with troyer a email and told him to let me know if they started on my custom tunes yet because if not i will probally return the programmer, the reason i bought the thing was to get my tires and speed correct and the reason i went with troyer was because i would be able to run the canned tunes until my custom tunes came in. I could have went with anyone and just waited 8 to 10 weeks for custom tunes.




