Updating SCT BDX tuner.

[SuperPete]

So, I have SCT BDX, been using it for some time, I see that updates comes up every time I plug in to my PC.
Been reading that in order to update it I have to return in stock setting? What is that mean? Put car back to stock? BDX back to stock?
Thank you

 

[ZSHO]

I have the X4 and that would suggest to return the device to stock settings! Z

On the X4 you should download (device updater) from sct and hookup the device and select automatic update and get it up to speed.
I'm hoping others will chime in..

 

[SHOdded]

I have never returned the X4 or X3 to stock while updating software, never had a problem.  Here, I am talking about the SCT software, not the tune.

Now if there is a tune update available, the prudent thing to do is to return the vehicle to stock.  To do that, make sure the X4/BDX/etc is uptodate on the SCT software/firmware first.  Return the vehicle to stock.  THEN download the tune to the vehicle.

 

[SuperPete]

Ok, so every time I get new tune from Matt, I need to return vehicle to stock, then update?

 

[SHOdded]

You don't HAVE to, it is an extra step that is a good precaution to take, and the SCT recommended way.  Really, you are overwriting one tune with another, whether the previous tune came from Ford or from your vendor.  Still, better safe than sorry.

Some advice in this thread from people who have BTDT -
https://www.fordgt500.com/threads/sct-dont-do-this.81362/post-1157730

 

[FiveLeeter918]

Ok, so every time I get new tune from Matt, I need to return vehicle to stock, then update?

I personally always recommend returning to stock before updating. If you brick the handheld, you'll need to send it to SCT for unlock, and then you'll lose connection with your pcm and it'll require having the PCM reflashed by Ford (2 hours of labor) to return to factory.

It's an extra step but saves a lot of headache, especially with how buggy these things are since the EPA got involved.

 

[MKS Tom]

 

[TopherSho]

LOL *this*

I have personally had my 2015 SCT handheld brick on update of the SCT handheld.  They (SCT) opened a TeamViewer session on my Windows box and unbricked it and reset the marry bit.  Not a big deal.

I have also had issues in the past where a return to stock and re-apply the same tune solved weird wastegate issues on a incremental tune update... (btw i have had dozens of Brad tunes and never had this issue)

 

[Macgyver]

Ok, so every time I get new tune from Matt, I need to return vehicle to stock, then update?

I personally always recommend returning to stock before updating. If you brick the handheld, you'll need to send it to SCT for unlock, and then you'll lose connection with your pcm and it'll require having the PCM reflashed by Ford (2 hours of labor) to return to factory.

It's an extra step but saves a lot of headache, especially with how buggy these things are since the EPA got involved.

Once you have all your tunes on the handheld and it acts or does what it should.. You car is not being worked on. Why bother to update the handheld to the latest revision when it is "Working as Intended" ?

I can understand the flash to stock for sure and then flash to a new tune.

 

[FiveLeeter918]

Ok, so every time I get new tune from Matt, I need to return vehicle to stock, then update?

I personally always recommend returning to stock before updating. If you brick the handheld, you'll need to send it to SCT for unlock, and then you'll lose connection with your pcm and it'll require having the PCM reflashed by Ford (2 hours of labor) to return to factory.

It's an extra step but saves a lot of headache, especially with how buggy these things are since the EPA got involved.

Once you have all your tunes on the handheld and it acts or does what it should.. You car is not being worked on. Why bother to update the handheld to the latest revision when it is "Working as Intended" ?

I can understand the flash to stock for sure and then flash to a new tune.

Depending on how old your handheld is, we've often seen issues trying to datalog because the firmware has not been updated.