When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I think i may have it figured it out as far as the .csv is concerned, but need to confirm everything before i make that exclamation. I have found that the file does indeed save as .csv when i tell it to, just unable to email it from the phone. I found the files after i plugged my phone into the laptop, but i do not think i had the app set to correctly save it and when i uploaded it into the PID chart it only put everything in column A1 instead of filling in a workbook. I have since ensured that the app is set to save as comma delimited, and will try again tonight. There were way too many data points for me to even try to decipher which number was supposed to go where. If it refuses to upload in to the PID tool in multiple columns, i may have another issue to figure out. Will be back tonight!
I finally got it to work. Still unable to email as a .csv from iPhone, but i was able to save as .csv, hook it to the laptop, pull the file from the phone and email it from there.
So this is just a super short test run verifying i could get it to work, let me know what you guys actually need to see as far as length is concerned.
Regarding the iPhone, I assume the .csv file wants to save in the “files” app. Can you go into that app and email from there after saving?
Just a thought. I haven’t worked with FORScan but have also had to jump through hoops to get certain files to play nice with Apple devices.
I actually got it to work. I had to save it (would not open a prompt when trying to email it), then attach it to the laptop and pull if off the phone that way. I attached the PID chart (super short WOT) on my last post.
EOT is reading pretty high (244-251*) - grab EOT, not EOTV, to get the correct reading. I see 119* or so in the raw data, so it's ok.
Also strange is the MAT (34*) is reading lower than IAT (58*), - that's weird. MAT should track higher than IAT, and vary with boost. Do you have a code for this sensor? Try unplugging the MAT and doing another log - see how it drives.
Agree your boost is low, but your rpm is low as well. Could you log a WOT run and see how things look? Let the rpm climb to 2800-3000 between shifts.
I believe I do get an IAT code. P0113 IIRC... also pretty sure previous owner unplugged it and let it hang after a 6637 install. Not 100% certain on the MAT location, my google-fu is not strong today apparently. Could you point me in the right direction for that?
