Suggestion : configurable X Y Z axis in oscilloscope mode

[JeremyPERFORMANCE]

Hello guys,
I was logging some cyl accel value on a V8 + rpm.
The logging is very good, but one step in my wf is to export CSV data and import them into a logviewer.
It could be just awesome to have the possibility to attribute axis properties for selected pids because in my case, i have 9 PID, 1 with his properties, and 8 sharing the same properties but on different "line", making it very hard to compare the cyl 1, 2, 3, etc !
I have access to a lot of Mustang and would love to help you adding this feature by any mean !

Thanks guys !

[oldtinfords]

Hello guys,
I was logging some cyl accel value on a V8 + rpm.
The logging is very good, but one step in my wf is to export CSV data and import them into a logviewer.
It could be just awesome to have the possibility to attribute axis properties for selected pids because in my case, i have 9 PID, 1 with his properties, and 8 sharing the same properties but on different "line", making it very hard to compare the cyl 1, 2, 3, etc !
I have access to a lot of Mustang and would love to help you adding this feature by any mean !

Thanks guys !

Tuning software like PCMtec or HPtuners is your answer.
There's too much time & money involved in developing & adding what you're suggesting to an application that isn't aimed at the tuning market. This is the same reason why tuning programs don't crossover into the types of programming that FORScan, IDS, FJDS & FDRS do.

Tuning providers have spent hundreds of thousands of dollars & spend several years developing their platforms to tune & datalog pids & display as tables with axis. The method of getting the data can require a totally different routine which would then need to be implemented for every PCM type. Cost vs reward when tuning software already does this, makes it very unlikely that it would ever happen.

[JeremyPERFORMANCE]

Thanks for your answer.

I use both of the tools you're mentionning, they are very great tools. You're not totally in the true side for diag features. In fact, with HPTuners, you have a quick access to useful ECU diag command included in Ford tools for ex (DTC reading and clearing, Freeze frames, adaptations clearing, speedo adjustments, etc)

I tuned a LOT of Ford, and ForScan is (a loving) part of my workflow. I also suggest it to a lot of people for the extreme precision and stability when dealing with Ford cars. I think its the best tool for coding and diagnostics Ford cars. Part of diag is data analysis, and editing axis could be really really helpful ^^.

Anyway, its interesting to see there is different perspective of what is ForScan built for.

Cheers, mate !