That wouldn't help me here in Melbourne :unsure:
Printable View
That wouldn't help me here in Melbourne :unsure:
One thing I that I got tempted with last year was a "Dynamic Fuel Load" PID for the E38 ( and others might like it as well... )
I've been looking at dynamics for a while now and really would like to know what the ECM is calculating the dynamic fuel load at. Using other things, like IBPW, Exhaust AFR, etc doesn't really work well as I have a pretty good feeling that all the calculations are "additive", meaning that the DFL is always changing by different amounts, depending on temp, RPM, MAP, airflow and throttle open / close. Add to all that, the fact that the exhaust readings are delayed by different amounts depending on airflow makes it quite hard to tell what is going on.
I know it's a bit of messing around, but a DFL PID would be really great.
Next up is an Android / iPhone version of ScanTool that can chart log files, maybe even with a virtual dash....
Simon
LS1B and T42 tables for transmission in-gear pressure.
How about....
In ScanTool, to zoom the chart data, you hold <CNTRL> and scroll the mouse wheel.
Scroll up = zoom in, scroll down = zoom out.
Simon.
And to add to that....
When altering chart properties, such as the scale max / min for a given PID, it would be good if it was saved with the chart. Currently if you swap PID's then the default scale settings are used.
Another one for ScanTool.
It would be great to be able to set a "limit line" in the charts so you can scroll through and find data around particular values. My idea is that you could click at the top or bottom edge of a chart and drag into the data area. This would bring a line down, parallel to the top/bottom with a small data box that showed the chart PID value that corresponded to the position of the line. When you release the mouse, the line stays where is is but the data box disappears.
Simon
The ability to vary the CAN node number of the V2 unit so that OBDII gauges could run concurrently with V2 scanning. Not sure if this is possible, but it would be good.
Plus, the ability to read/record and put together/assemble CAN messages for transmission on the CAN. i.e. message that tells ECM that handbrake/ebrake is on so Crank Learn will run.
Dont like the chances, but gotta ask!
Happy Easter to y'all!
Another for ScanTool.
When highlighting a section of a log, we get the minimum, maximum and average values for the displayed PIDs. It would be good to either...
- also have the difference between the max/min values listed
or- have the option to toggle the average display between average and difference (perhaps a right click option)
Simon
I like the difference/range between max/min values... :cheers:
Full support for custom PIDs - add a dedicated form/interface for creating/editing/managing custom PIDs; it would be bitchin in the PIDs (F8) folder-tab to have the ability to right-click on a custom PID, and in the context menu have an option to edit that PID in a trick winform (rather than having to futz with the calc_pids file).
A pet aggrivation - I moved the EFILive folder from My Documents to a flash drive, because I use the software on multiple computers, and when EFILive is started and cannot find any folders (defined in Properties --> Folders) the software just craps-out. It would be nice that instead of throwing an exception and giving up that EFILive will at least still load so I can go to the Properties menu and update those folder locations.
The DTV (Bi-directional control interface) is clumsy to me, too many checkboxes & "safeties" to click & unclick.
Mr. P.
Another pet-peeve - changing units in the tuning tool is very cumbersome; can you support changing units when looking at the table?? i.e. when displaying {3647} it would be awesome if a person could click on the "Units" textbox and be able to instantly toggle the chart/display between Lambda/EQR/AFR; likewise be able to click on the light-blue chart row/column headers and be able to instantly toggle between metric/SAE. As it is now, I cuss to myself and have to close my work, use the Edit menu item & Configure Display Properties option - my way would be more 'direct' and not require loosing train of thought to configure the tool.
Mr. P.
I think keep in mind with these suggestions most of them will never see the light of day in V7 tune/scan, many of these requests or peeve's are known and are addressed for the V8 software development.
Mr.P, how would the DVT control be handled better? Most of the double check boxes are safeties are imposed by the way the ECM processes the DVT's, in other words, you have to tick box A to enable box B or the ECM will refuse your request.
As long as they're on the cards somewhere, I'm happy ;)
Seems like a calculated PID editor is popular, see screen shot for what it will be like.
Note: The V8 software is still under development and won't be released for some time yet.
Regards
Paul
No Prob - trust me I totally understand real-world SDLC!
DVT controls - I actually have a lot of ideas, that would best be 'visually' communicated; I will make an effort to set-aside time and draft something in Visio. The CHIEF problem with the V7 DVT GUI is that the controls are waaaaay too far apart from each other - in real-world testing, this means you have to (using a mouse touchpad on a laptop no less!) drag the cursor from one quadrant of the screen all the waaaay over to the opposite corner/quadrant of the screen etc; in real-life use I find I have to do a lot of clicking, dragging, 'mousing', visually scanning the screen to try and locate the next relevant control (click target). I have to make the mouse cursor "cover a lot of screen real estate" to operate controls, and this is not bad unless you are limited to using only a 14" laptop with a touchpad (or worse, the tiny thumb/joystick) and it just adds clumsiness when you are doing it live (under time pressure). Not knocking what is already there, it's functional but this (the DVT GUI) is a difficult design problem, because it is an interface that will be used in real-time.
YES! Everyone's life will be happier when you don't have end-users screwing with config files lol.
This might seem overkill, but I will mention it -
One of the most popular things guys on this forum do is to share custom PIDs, and PID selections. At the moment with V7, you cannot share a custom PID - in other words, you cannot "email" someone a custom PID that they can double-click on and it just gets "incorporated" into EFILive; that would be a handy-as-hell feature IMO. The bigger thought is - not only to make a software product that allows and individual to tune their own vehicle, but now (in V8?) to make a software product that easily lets persons in the EFILive community to share "bits and pieces"; V7 does allow this already (chart files, etc). So I would also extend this thinking to PIDs in V8, somehow break the PIDs from being defined/captured in a single text file into a folder of tiny text files (one per custom PID) that can easily be published/emailed between users. That way when a contributor like Joecar or WeathermanShawn writes a tutorial, they are not burdened with the formidable job of having to walk a complete n00b through the process of using Notepad to edit the PIDs config file PLUS how to write the metadata description for the PID itself PLUS how to incorporate that PID into the PIDs being monitored... ad nauseum... It would greatly help the community if the person writing the tutorial just said "click HERE and this custom PID will be imported into EFILive!"
Mr. P. :)
Appreciate your comments, very well said. Both ideas you've described above are very important to the V8 design and development.
The V7 scan tool configuration was never really designed, it just sort of expanded along with each new software update and each new added feature.
Because V8 is a green fields development project we are able to capture the configuration in such a way that it will be a relatively simple process to share Scan Tool PIDs, dashboards and other configurations.
The same goes for the config in the Tune Tool.
I know what you mean about the DVT controls being used in real-time and the difficulty of using the mouse while sitting in a vehicle with limited space and limited input options.
Your ideas on making it easier to use are most welcome... :)
Regards
Paul