Roland@pcmtec

The binary is always there after a read but the server will build all the parameters for it if you are not licensed.

Only workshop version can view files that have never been licensed previously. If you have the workshop version use calibration tools - > populate unlicensed file.

Very clever idea.

I'm far from an expert here but from the black ones I pull out at 220,000kms they look brand new in comparison. 0.78 is quite rich but without a wideband it's anyones guess. I would definitely confirm the afr. Will cost you $50 to get someone to weld a bung in your dump pipe and you can set it up permanently. Make sure it's 11 o clock so no moisture sits in it, also at least 30cm from the turbo so you don't cook it. How much timing are you running at peak torque and redline? If it's conservative you could lean it out and see how it goes.

iridium will be better. Copper don't last long enough. Also drop the gap lower to 0.6 with a proper tool (or pay them to do it for you) How rich are you running? This will make the spark more likely to "blow out". Also coils, are they originals? I suspect you will be getting a random miss on any of the 6. Do you have a photo of the old plugs?

They do a misfire test and will log a Dtc if it occurs. This will only pick up a severe consistent miss on the same cylinder though. We might be able to log the actual values used though. Are you trying to diagnose a specific problem?

Yeah swapping the entire cal is always going to be a recipe for trouble. Best to compare/merge everything manually. If you know the vehicle came out in exactly the same configuration as a turbo. Eg you have a ZF NA sedan and you know that sedan was available as turbo, then you can reprogram the ABS using IDS in some cases. But if the vehicle for example is a BTR NA sedan and there was never a turbo BTR sold, you will not be able to reprogram the ABS module and will be forever stuck with an ABS/DSC fault. Even if the vehicle was sold as a turbo if you are not already an expert at using IDS this is a recipe for a big headache as the combination of stability control, braking distribution, hill descent control that the vehicle came out with may never match up with the calibration you choose. IMO just convert your existing strategy/calibration to turbo instead using the compare feature by comparing to another strategy of the same vehicle base.

Providing you find a strategy that is similar from the same vehicle.

Yes, you just won't have the boost solenoid depending on what PCM you have.

Check out the conversions thread and take it to someone who has done it before. Ix the car originally came with a 6 speed ZF in it you can do it. 8 speed will never happen.

If you have pro or workshop you can use the stock calibration wizard under calibration tools.

Yes we will probably just remove the feature entirely as the timeout adds up to 5 minutes for some reason I believe.

During a flash read/write I would expect to see some faults occur as the PCM is in test mode (basically like it is unplugged and blocks comms to all the modules). Just plugging the tactrix in without it being attached to a laptop I would not expect to see faults though I've never actually seen a late model Falcon whilst it has been flashed (someone else can confirm what happens). Can you confirm if the tactrix is plugged in without being plugged into a laptop if this occurs? The faults should all clear after a flash however, I can't see any actual issues that will cause you grief here. DTC reset only works on a limited number of vehicles in PCMTEC. We will look at finishing this as part of the datalogging project. Forscan is a great tool for DTC reading and key recoding, so I would recommend continuing to use it for these items. It also supports a large range of vehicles as well.

You can now browse the strategies yourself via Calibration Tools -> Show Calibration List if you have the workshop version of the software.

Confirmed from someone who does swaps. You just need to flash in a petrol strategy over the top. It will have all the hardware you need.

Fairly sure you can but no guarantees. I will message a few people who might have tried for you.

No estimates. We can get held up for 3-4 weeks at a time with support and other feature requests. So it is basically impossible to give realistic time frames. 1 month or 12 months depending how things go. Eg we had the basics working back in early November then spent the last 2 months doing QA and getting 0.75 released so we didn't touch datalogging at all over that period.

Can you press help - > upload log files? Doesn't look like it came through for some reason. Cheers

Fantastic. I'll let you know when we have a new beta available that will support partial write on this flash type.

For anyone who missed it, the new release is out which includes the gear calculator.

Just left you a voice message if you can give me a buzz back when you are free. Cheers

Does it write with partial write unchecked without an issue? I will coordinate a time with you for some more testing.

Use Darryl's parameter file he posted up earlier.

Actually it appears you can do dual maps on all Mk1s, there are just a few limitations in the size and number of tables such as adding cam timing to the dual maps. Everything else is allowed.

Boost by gear is available on all operating systems. The only custom os restriction is the fg mk1 cannot have dual maps. However if you are not running the 5r55 5 speed auto there is a alternative calibration that cns be loaded into the mk1 fg that will allow dual maps.