My computer is misbehaving, so I'm going to upload these from a few days ago. Perhaps one of you gents could run them through the program and chart them? Ok maybe not.... Says its not an accepted file type

 

What are the file types and sizes? They must be under 5 MB to be uploaded.

I'll PM you my email address and if you like you can send them to me and I will chart them for you.

 

Sent sir, and i thank you. Trying to sus out the reason for my service light. Hoping to rule out hpop.

 

Thanks for sending me the files via email in an effort to make your data logs viewable by the community.

The issue is that when you exported the data logs in order to chart and post them, they were exported in the .fsl file extension. Coincidentally, this is not an approved file extension on the FTE, which is why you received that error. I am unaware of any method to convert a .fsl file to a .csv file without utilizing the FORScan program. Maybe Jeff ( @BWST ) has stumbled upon one...

In an effort to make your data logs and charts viewable by the community, I would ask that you open the FORScan Lite app or FORScan on your laptop, whichever way you recorded the data logs and export them as a .csv file. Once you have done that, you can either chart them yourself using the PID Charting Tool or email the .csv files to me again and I will chart and upload them here. I see one of the files is 10.5 MB, so it will be too large to upload as a single file, but if you broke it into 3 files you could upload the entire document. Or, you could trim the fat in the data log if you know what you are looking for and upload the meat of the data log.

If you are unfamiliar with how to export the files as a .csv, no worries! Jeff has taken a lot of time and effort to lay out the process with pictures and comments at the link below.

Link: FORScan + FORScan Lite: Class Tutorial Q&A

I hope this helps and I am available for help here or via email if you need it.

 

Ok... i cannot, so far anyway, fogure out how to convert my incorrect fsl files, to csv files. So for starters, i took a new idle scan after taking the kids to sunday school..

Incidentally, i reflashed my hydra this morning, too.. after a talk i had with AA the other day. He told me i had my order incorrect. Had to pull high idle off slot one and replace with daily driver. So im curious if that will make any differences, too.

 

The order of the tunes will not affect the running condition of the selected tune. It is not recommended to put an abnormal running condition tune like high idle or mo start in position one as that could be the default tune the Hydra resets to in the event power is removed from the system.

I will chart the .csv file you provided ASAP and post it here. Now you know how to export the data logs as .csv.

 

AA told me that position 1 is referenced for the changes made, for all other loaded tunes, so it needs to be a drivable tune.

Yes, i had to change the file save type. Wasnt a big deal, thankfully. Just didnt realize i needed to do it, when i was saving those the other day.

I did tell you , a few months back i would make learning the save feature my next forscan task. Just wish i could have done it sooner. But summer schedule is quite hectic for me, and the old girl barely got used.

 

A couple of notes going forward...

• Your ICP is set to Kpa in the data log and should be set to PSI.
• You have a few erroneous data points that could be removed, like MAP hz.

The data log and chart do not seem to reflect any adverse running conditions, but now you have a way ahead. I have attached the chart as an attachment and as an image below.

 

My settings are set to imperial, and other points are in psi... i have not been able to get the icp to change values. No idea why.

 

How to change the unit of measurement is detailed in the link I posted in post #4. Unless things have drastically changed of course.

I "think" there is a universal setting as well as individual PID settings to change the unit of measurement. Having them wrong on the data log is not a game stopper though. In order to change kpa to PSI, each cell in that row must be multiplied by .145.

This would be the same for others that are being logged differently than the PID Charting Tool is expecting.

I hope this helps.

 

I've had to use FSL to create the csv file from the original data. Sounds like you've got it now, @kd5zll . What codes did you read? With that SES light, there should be some.

 

i rescanned my idle. Have not figured out how to convert, as of yet.
codes were for boost, wastgate, and hpop pressure to high/low. AA is double checking my tunes, the boost related codes should be turned off already, i suspect the hpop code is whats popping.
that being said, he told me ive been shifting a couple hundred to low, so im gonna have to drive consciously amd reprogram my habits. Which may help. At least somewhat.

 

Can you open one of your fsl files in FORScan, then save it out again as a CSV? I'm pretty sure I've done that.

That P1670 is curious. On a running truck, it might be an intermittent wiring issue. Is the wire bundle over the driver's valve cover in good shape - not chaffing on the valve cover? Might be worth checking continuity through the harness from the IDM to the UVCH connections while wiggling it. Try a buzz test and see if any additional codes pop.

That P1211 can be ok on tunes that use alot of fuel pulse width, if you're happy with the performance. I get that code from time to time, even with the Adrenaline HPOP, in a 65hp tune with my tired injectors.