Roland@pcmtec

Darryl should be able to dig it all up for msg200 as he is looking into that now to attempt to mask the alarms.

I never even bothered to check the manuals. The fact they show the CANID is very interesting. I assumed they wouldn't cover that level of detail at all! I bet that it is incomplete though.

"because if you send 0x200 to a cluster it will stop many warning lamps from working correctly, and will silence the Alarm. Speaking of the Alarm - Roland, this may be a way to silence any alerts that happen while your displaying the CustomOS Selection on the cluster" Nice find! We were going to mask the alarms individually, but this might be even simpler!

https://it.slashdot.org/story/19/06/02/0042209/ask-slashdot-what-to-do-when-your-certificate-authority-suddenly-revokes-your-cert 150+ other companies had their certs revoked by commodo in the same go. You should write an article about the sad state of software signing certs, anti virus and false positives.

Lots of crappy heuristic engines out there. https://www.virustotal.com/gui/file/a0e37e7c165c00abbde30f62e5bdd93e86f1d002bc3c34c1dcdba8e5e2b9921b We had our certificate revoked due to the packer we used to use causing too many false positives. Commodo are a bunch of pricks and bulk revoked certs that had false positives against them without contacting the companies in question. The fact most of these engines mark all packed exes as malicious is absurd, what is even more absurd is they whitelist your exe by just emailing them. So that means if I was writing a virus, I could just email all the companies to get it whitelisted. Other than known widely distributed exploits anti virus is useless.

Only the F6 manual BA had independent VCT. This can be converted to a BTR auto but not a ZF. You'd need the HAAT3VC strategy (check the common strategies thread). You are on your own with this kind of job. Lots of messing around and prepare for a christmas tree of fault lamps. Definitely possible, but not something we can tell you how to do.

Have you read the HOWTO guides? Regarding open loop fuel control read this guide. These cars only have a narrow band sensor so there is only closed loop fueling at 1.0 lambda, every other figure will be open loop only and will mean the speed density and injector slopes need to be perfectly dialled in, if they are not then the figure in the base fuel lambda table will not match what is actually happening in the engine. Read all of the HOWTO guides, these questions should be able to be answered from these.

SCT sometimes causes a checksum error. I'm not sure why. Often you'll find the VID block has been wiped as well so double check that.

If it is tuner locked with our software it will say so specifically. Some other tuners do their own thing to tuner lock the PCM which could also cause a checksum error.

Basically if the car starts and runs fine it is usually safe to ignore it, it was most likely the result of whoever tuned it previously.

No one is going to have any information on this. You'll have to learn to disassemble the code if you want to know more. That message is sent to the TCM and I suspect will be critical for shifts to work properly. Mess with the torque tables in the PCM and see how they change, that should give you some idea how it is made up.

Yeah obviously you would't send a car out like that, but it is a very quick test to determine if it really is knocking. Even if its running 13.5 AFRs it shouldn't knock if you retard timing that much.

How did you go @scotty ?

Pull 10 degrees out of the whole map and let me know if it still tries to pull timing. If only 1 injector is blocked your AFRs will look fine, you'll only pick it up via knock detection or individual cylinder EGTs.

Old engines and built engines with forged pistons that rattle at idle are notorious for it but that doesn't mean it isn't legitimate. You could have a blocked injector etc. Just to confirm if you take 7 degrees out of the entire spark map, does it go away? If you stick a screwdriver on the block and rest your ear on it whilst its on the dyno, can you hear anything?

Territory should be close to identical to the sedan, but if its a BF it won't have the tables/scalars you mentioned.

Thanks @finnigan001 once the beta is closer to complete we will continue with catagorising all the items as there is ~4000+ variables you can log. This really helps.

Closed loop is PID control which is completely different. What the Ford has is open loop + and on/off controller which is the over/underboost thresholds. Closed loop is only used when you are within a few kpa of setpoint and it will use a PID controller to keep it there, unless your desired boost matches very closely what you see in open loop exactly chances are it won't activate.

Which strategy and what version of the editor do you have? BF does not have these tables I believe from memory.

Just drop the duty cycle to 0% during a shift, that will stop it spiking.

Updated the guide to cover the new wizard that is available in the beta.

0x623 byte0 engine capacity in litres x 10 byte1 engine code (some hard coded number for the engine type) (maybe auF2531?) byte2 auF2552 byte3 NA/Turbo etc byte4 TCM Calibration level auF1692 0x640 byte0 axle type eg FWD/RWD/AWD auF2193 byte1&2 = axle ratio as a float converted to a short (16bit) scaled between 0x333 to 0xFFAD Byte3&4 = same as above but the VID axle ratio instead I believe scaled in the same range Byte5 = Torque split (AWD vehicles) to front axle. I believe this changes for AWD vehicles Byte6 = some bit field for number of gears and car model Byte7 = null 0x650 byte0 CAN ID byte1 = byte0 of msg 623 rest of this looks the same as msg 623 just offset by one byte

So set the limits out of range. Eg make the underboost threshold very low. Why don't you want to use it? It helps spool the turbo at part throttle much faster. You can just change the underboost duty cycle. There is a scalar which will have 1 in it, change it to 0.6 for 60% duty when in underboost if you want.

Extra spark retard will cause a boost spike. The FGs have a wastegate adder for spark retard to pull back the duty cycle. This will stop a boost spike, someone else on here commented in a thread about it.

I believe Ford didn't trust it either. From what I can see no turbo car has it enabled by default.