Donmatteo
FRF Addict
4. That’s the stock size I believe. I would wait for some else to confirm. Ive never had to change it.Thanks Don. But what the heck would I put in for 37’s??
Disclaimer: Links on this page pointing to Amazon, eBay and other sites may include affiliate code. If you click them and make a purchase, we may earn a small commission.
4. That’s the stock size I believe. I would wait for some else to confirm. Ive never had to change it.Thanks Don. But what the heck would I put in for 37’s??
Thanks. That’s what thought.Yes the 315's are the stock 35" tires
Update?I have Forscan setup on a 2013 MBP with Catalina using VirtualBox and one of these free VMs from MS: https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/ OBD2 device has to be assigned to pass-through to VM, but it seems to work.
So far it works, but I've only read from the truck. Have NOT written anything yet, still trying to make sure I'm 100% certain how the UI of Forscan works.
Assuming it actually works writing to it, this is a 100% free solution for MacOS, no Windows license required. The Windows VM only last 90 days before you have to download another, so be sure to copy any backups to host machine's hard drive.
Hey guys I didn't see on the spreadsheet where you can adjust for different tire size (37")
Can someone point in the right direction ?
Thanks
Thanks for the clarification LivitupTire size is set in the BCM module. Use the link on row 61 of my BCM spreadsheet here to calculate the correct value to use for your 37's: https://docs.google.com/spreadsheets/d/1uDSQ1Z5a2Wt8-kjrSiVSlDFGFHnfeuhb3RTMVz95730/edit#gid=0
After you change the tire size you'll likely get the wrench on the cluster so then you need to run the PCM Relearn procedure (first item in the programming icon screen of FORScan) and if a TCM relearn procedure is listed for you in the programming screen then run that also to remove the wrench.