Topic Sponsor
Performance, Tuning, and (LEGAL) Racing Post discussions about increasing performance, capabilities, and racing. ****WARNING**** Street racing or illegal activities will be removed and potential bans will be handed out.
Sponsored by:
Sponsored by:

palm beach dyno tuned today.

Thread Tools
 
Search this Thread
 
Old 03-30-2019, 11:23 AM
  #31  
Senior Member
Thread Starter
 
malloy's Avatar
 
Join Date: Mar 2019
Posts: 351
Received 337 Likes on 122 Posts
Default

i agree and until I view the logs i really don't know. thanks all... side note was that my truck was the talk of the track. the stock exhaust really gave it the sleeper effect. I spanked a fox body pretty bad and he put on the whole burn out smoke show, loud exhaust,etc...
Old 03-30-2019, 12:25 PM
  #32  
Senior Member
Thread Starter
 
malloy's Avatar
 
Join Date: Mar 2019
Posts: 351
Received 337 Likes on 122 Posts
Default

So looking at the logs my trucking was shifting all over the place but never exceeded 6300. I already sent the logs over to the tuner.
Old 03-30-2019, 01:06 PM
  #33  
Ezekiel 25:17
iTrader: (1)
 
UNBROKEN's Avatar
 
Join Date: Dec 2016
Location: Houston
Posts: 4,239
Received 2,371 Likes on 1,215 Posts
Default

Bump those up to 7300 and go run a mid 11....that’ll leave everyone scratching their heads. lol
Old 03-30-2019, 01:12 PM
  #34  
Senior Member
 
TX-Ripper's Avatar
 
Join Date: Apr 2016
Location: SE Texas
Posts: 1,713
Received 428 Likes on 336 Posts

Default

Originally Posted by UNBROKEN
Bump those up to 7300 and go run a mid 11....that’ll leave everyone scratching their heads. lol
^^^
Old 04-15-2019, 09:36 PM
  #35  
Senior Member
 
hotrod_renegade's Avatar
 
Join Date: Feb 2015
Location: MANtana
Posts: 116
Received 42 Likes on 19 Posts

Default

Nice numbers, I just ordered a remote tune from PBD as well. Quick question, were you on the Whipple tune before you had PBD tune it? Reason I ask is I'm having an issue returning the truck to stock after tuning it with the Tomahawk that comes with the whipple kit. I contacted whipple and their response was "the tomahawk programmer will not allow you to return the truck to stock, you have to send us your PCM to do that." Rob with PBD said to update my SCT BDX which would force a stock file and then try and load a tune. Well now it won't even recognize the truck and gives me a "DFL Commlink command failure" and I can't do anything with it. Do you know if they had any issues like that with your truck? Or has anyone else had this issue?
Old 04-15-2019, 09:39 PM
  #36  
Senior Member
 
TX-Ripper's Avatar
 
Join Date: Apr 2016
Location: SE Texas
Posts: 1,713
Received 428 Likes on 336 Posts

Default

Originally Posted by hotrod_renegade
Nice numbers, I just ordered a remote tune from PBD as well. Quick question, were you on the Whipple tune before you had PBD tune it? Reason I ask is I'm having an issue returning the truck to stock after tuning it with the Tomahawk that comes with the whipple kit. I contacted whipple and their response was "the tomahawk programmer will not allow you to return the truck to stock, you have to send us your PCM to do that." Rob with PBD said to update my SCT BDX which would force a stock file and then try and load a tune. Well now it won't even recognize the truck and gives me a "DFL Commlink command failure" and I can't do anything with it. Do you know if they had any issues like that with your truck? Or has anyone else had this issue?
any reason you don’t want to have them use the whipple tune as a base file and keep the whipple bypass logic?
Old 04-15-2019, 09:46 PM
  #37  
Senior Member
 
hotrod_renegade's Avatar
 
Join Date: Feb 2015
Location: MANtana
Posts: 116
Received 42 Likes on 19 Posts

Default

Originally Posted by TX-Ripper
any reason you don’t want to have them use the whipple tune as a base file and keep the whipple bypass logic?
Well I was hoping the BDX would recognize the whipple tune as the stock file and then I could just load tunes and datalog normally from there, but that hasn't been the case. I'm getting different answers from PBD and whipple, so I guess next step is to contact SCT...? I'm starting to wonder if it's something on their end now. I'm at a loss, thought maybe somebody else on here had come across the same deal.
Old 04-15-2019, 09:52 PM
  #38  
Senior Member
 
TX-Ripper's Avatar
 
Join Date: Apr 2016
Location: SE Texas
Posts: 1,713
Received 428 Likes on 336 Posts

Default

Originally Posted by hotrod_renegade
Well I was hoping the BDX would recognize the whipple tune as the stock file and then I could just load tunes and datalog normally from there, but that hasn't been the case. I'm getting different answers from PBD and whipple, so I guess next step is to contact SCT...? I'm starting to wonder if it's something on their end now. I'm at a loss.
you are currently on a ford race os aka the whipple tune.

sct is not compatible with the whipple tune.

You “have to” read the tune with a hptuners mpvi2 and send that to pbd.

it has to be ready with a mpvi2, will not work any other way.

then you can either buy credits and tune with your mpvi2 or buy a ngauge and they can give you tunes for that.

sct gets sold or goes on the self.

Last edited by TX-Ripper; 04-15-2019 at 09:55 PM.
Old 04-15-2019, 10:40 PM
  #39  
Senior Member
 
BadCon's Avatar
 
Join Date: Jul 2018
Posts: 1,037
Received 366 Likes on 250 Posts
Default

Originally Posted by hotrod_renegade
Well I was hoping the BDX would recognize the whipple tune as the stock file and then I could just load tunes and datalog normally from there, but that hasn't been the case. I'm getting different answers from PBD and whipple, so I guess next step is to contact SCT...? I'm starting to wonder if it's something on their end now. I'm at a loss, thought maybe somebody else on here had come across the same deal.
I tried to return my custom tuned Roush truck back to stock with my SCT GTX so I could update the GTX, and while it successfully loaded my stock Roush tune, I could not reload my custom tune. It had somehow unmarried itself, and an error with the new logic in the GTX and BDX devices (they can be married only once) led to the device thinking I was trying to tune another vehicle with a different vin and strategy code, which meant the tune never loaded, leaving me stuck with a base Roush file a fully upgraded non compatible fuel system....it ****ing sucked.

Called SCT, and after some remote trouble shooting they sent me a new GTX. Since you returned to stock and now can’t load the custom tune, your issue might be similar to mine.

So call SCT

Last edited by BadCon; 04-15-2019 at 10:43 PM.
Old 04-24-2019, 11:56 AM
  #40  
Senior Member
 
hotrod_renegade's Avatar
 
Join Date: Feb 2015
Location: MANtana
Posts: 116
Received 42 Likes on 19 Posts

Default

Originally Posted by TX-Ripper
you are currently on a ford race os aka the whipple tune.

sct is not compatible with the whipple tune.

You “have to” read the tune with a hptuners mpvi2 and send that to pbd.

it has to be ready with a mpvi2, will not work any other way.

then you can either buy credits and tune with your mpvi2 or buy a ngauge and they can give you tunes for that.

sct gets sold or goes on the self.
Not true. Five minutes on the phone with SCT and they were able to force the stock file back onto the device. Plugged the device back into the truck and returned to stock over the Whipple calibration. From there it works just like normal and you can load a base file from a shop of your choosing and proceed forward with datalogging, revisions, etc. Just an FYI for those that may run into this same issue using an SCT device. Saved me $500 (or more) by sticking with the BDX vs. going the hptuners route, and also saved me time and freight costs not having to send my PCM to Whipple. Sorry to have hijacked this thread, but I got the answer I needed and found there are other ways around the Whipple calibration for aftermarket tuning with PBD or whoever for anyone else looking to do the same.

Originally Posted by BadCon
I tried to return my custom tuned Roush truck back to stock with my SCT GTX so I could update the GTX, and while it successfully loaded my stock Roush tune, I could not reload my custom tune. It had somehow unmarried itself, and an error with the new logic in the GTX and BDX devices (they can be married only once) led to the device thinking I was trying to tune another vehicle with a different vin and strategy code, which meant the tune never loaded, leaving me stuck with a base Roush file a fully upgraded non compatible fuel system....it ****ing sucked.

Called SCT, and after some remote trouble shooting they sent me a new GTX. Since you returned to stock and now can’t load the custom tune, your issue might be similar to mine.

So call SCT
Exactly what I did, those guys had me fixed up in no time. The original stock file from the truck was actually still on the BDX so they didn't have to send out a new programmer. Just reloaded the stock tune to the device so I could return the truck to stock over the whipple cal and went about my business!

Last edited by hotrod_renegade; 04-24-2019 at 12:00 PM.


Quick Reply: palm beach dyno tuned today.



All times are GMT -4. The time now is 11:26 PM.