PCMtec

[K4fxd]

Anyone heard from Mark? I don't know what Island he is on.

Sponsored

 

[Grimreaper]

Heads up for future users.

Roush/whipple file needs to be fresh flashed using what ever procal/tomahawk. If hptuners has read/flashed even if stock roush/whipple, it needs reviewed before full support. Roush flashing is one and done. Have to buy another $400 tune voucher from roush to be able to reflash with roush rdt 2534 software. Whipple should be easy enough to flash with tomahawk. get a pcmtec read before using other software

Using an na based OS for boost losses the infered SIP, bypass logic and pin reassignments for baro and iat2 to name a few. Roush adds baro sensors to gen2s now. Tb control looks different in logs and zero bypass flutter and surge compared to a na OS.

Talk on here has been very promising of what they plan to offer and wanted to be apart of that. Hopefully it will get sorted in the future

 

[K4fxd]

I think @engineermike got his whipple tune supported.

 

[K4fxd]

Roush adds baro sensors to gen2s now.

Do you have a read of one of these Roush tunes? HPT format is fine.

 

[Grimreaper]

Do you have a read of one of these Roush tunes? HPT format is fine.

Yes I'll email you in a bit

 

[Grimreaper]

I think @engineermike got his whipple tune supported.

He did but had to flash back to stock with whipple software before they could work with it. Not just returning to stock with hpt/sct/ngauge etc

 

[K4fxd]

He did but had to flash back to stock with whipple software before they could work with it.

Just tossing it out there.

Have you asked Roush to resend your calibration? I would think if you give them your name and VIN they would.

 

[Grimreaper]

I appreciate the extra thought on it. I have.

Only free reflash is if approved by warranty and need a valid warranty reason run through their warranty dept

 

[Rolls]

Heads up for future users. Believe there's a go/no go boundary to keep in mind that is not advised of in advance.

@Rolls , you guys should be very clear about what you are capable of supporting. Especially if charging for access to even see the software/ files/read bins etc. I can find no mention of unsupported bins for the mustang's or in relation to hptuners. Odd you guys can use sct devices as a delivery method though. Have credits and paid access to a tool that dosen't work at this point. Zero logging/table adjust etc.

Roush tunes are not supported and suspect whipple is in similar boat for gen2. No boosted OS present in their repository. Unsure if the $3k shop version provides something that allows these boosted OS to work and to be modified.

Roush/whipple file needs to be fresh flashed using what ever procal/tomahawk in order for them to consider supporting. If hptuners has read/flashed even if stock roush/whipple, they can't work around. Roush flashing is one and done. Have to buy another $400 tune voucher from roush to be able to reflash with roush rdt 2534 software. Whipple should be east enough to flash with tomahawk.

So pick your tuning platform in advance. Hptuners software is free and plenty of roush cals floating around their repository/ forums. You can see what you are buying before you buy. Hptuners has support for roush/ford performance (na/boosted)/ whipple etc.

Using an na based OS for boost losses the infered SIP, bypass logic and pin reassignments for baro and iat2 to name a few. Roush adds baro sensors to gen2s now. Tb control looks different in logs and zero bypass flutter and surge compared to a na OS.

Talk on here has been very promising of what they plan to offer and wanted to be apart of that. Hopefully it will get sorted in the future

Since releasing ProTuner there has been overwhelming demand for Whipple/Roush support from primarily DIY users and as such we have added support as the files come in, there were 5 boosted whipple strategies available in our repository at the time of your post. As these files are not available via Ford we must source these files from the customer.

Previously we could add support for any Whipple/Roush file in 24 hours turn around if a stock read if provided (it literally takes us 5 minutes once we get the file). The hold up on anyone getting supported added was due to no stock file being provided.

I've since talked to the team and we have decided that we will add support for Whipple/Roush operating systems even if a stock file is not sent in, the downside of this is you lose the red/blue different to stock colours, and you cannot use the custom operating system wizard until we get a stock read. The stock read must be done via flashing with the tomahawk/rdt then read via our software to ensure it truely is the original file.

Since releasing ProTuner we have added support for 7 boosted Whipple operating systems and 4 Roush boosted operating systems that have been added. Another 2 were added in the last 10 minutes.

We have a huge benefit in this regard that our operating system support generation is entirely automated and takes less than a few minutes to run per file. It takes us longer to reply to the support ticket than it does to add support to the software, this support is all done via our web back end as well, you don't require a software update to get the added supported.

We also have a complete stock file repository that can be browsed in the software for free, you do not need to go scouring forums to find stock files like other products.

Here is a subset of the boosted operating systems that are already available via our repository and have been for several weeks. The last two are MY20/MY21 control pack strategies (NA).

Any Whipple/Roush files that we have added support for where a stock file was not sent in will not show up in our repository/calibration list, they will however be able to be licensed/edited and flashed.

This discussion is best continued on our forums, I've made a link here to list which operating system have been added.

Here is a list of all the control pack/roush/whipple cals we support as of today. The files marked as "no" for stock file will not show up in the repository, you will however be able to read license them. There are 7 more Roush strategies being added as we speak which will show up in the stock file repository shortly

https://forum.pcmtec.com/topic/1835-whipple-roush-control-pack-support/

@Grimreaper Your Roush strategy has just been added and is now supported. Please be aware that Roush have obfuscated your spark tables in your specific operating system. I do not believe any other software products support this calibration for this reason. We will reply to your support ticket as well.

Please be aware that we have never advertised support for 3rd party custom operating systems. We have since clarified this on our website.

Here is a list of supported whipple/roush/ford racing strategies as of 30-08-23. You can see the Map Sensor column which indicates if the strategy has the roush harness added.

 

[Grimreaper]

We are making some progress. Ill check the support ticket this evening. Thank you.

298 is gen3.
1791 is gen2.

There were no boosted gen2 strats when i posted. I think your mixing the gen3 in with the searches in the repository

Map sensor alone is not enough to locate a boosted os.
Roush gen2 is maf based, some will have baro, some will not. Added after few years of kits shipping.
Roush gen3 is Sd based from F150 structure ive been told. Map sensor and no maf
Whipple gen2 is maf based. Tunes all usually say baro sensor is presnt but have not seen one with the sensor physically present.
Whipple gen3 is maf based, gen3 ecu has built in baro sensor, have not seen whipple add additional map sensors.

 

[Rolls]

Are you able to take this discussion to the support ticket so we can action it appropriately. As I said earlier roush support was never marketed or advertised and even had a disclaimer on the website.

We will work on this mapping for you however I want everyone to be aware this not a representation of the oem strategy support. We have over 3000 fully mapped oem strategies without any issues.

Roush employ obfuscation in some of the 15-17 tunes and as such scramble the spark tables as seen above. This is not a mapping issue. We will work on the descrambling today for this tune. This form of obfuscation is only in a few OSIDs from 15-17 from Roush and not in any others.

 

[Gen3javi]

I cannot figure this out. When I compare the tunes, one has idle messed up one is rock stable, nothing stands out. There are only 4 things different.
1 is I raised the idle RPM from 700 to 800.
Spark is different but only at WOT
I changed a shift point in the trans.
I changed the OP intake cam timing at WOT.

I even changed the idle speed back and it still floats.

Now I understand Lund telling people it is mechanical. But I know this is tune related because the revision before this one runs perfectly.

What 2 tunes are you comparing?

 

[K4fxd]

What 2 tunes are you comparing?

The same tune with minor adjustments. Say REV 1 works perfectly and REV 2 had issues. I couldn't find the problem but something got corrupted.

 

[Rolls]

The same tune with minor adjustments. Say REV 1 works perfectly and REV 2 had issues. I couldn't find the problem but something got corrupted.

Tunes don't get corrupted. Can you post the two files on our forum and we can see if there is anything else in the binary that you can't see that could be changed.

 

[K4fxd]

I will If I saved it.

Sponsored