what do you think the V1 or V2 needs or should have
in upcoming software updates.
i would like to be able to hide selective cells (right click hide cell)
Printable View
what do you think the V1 or V2 needs or should have
in upcoming software updates.
i would like to be able to hide selective cells (right click hide cell)
for a completely new idea: how about having black box logging on a V2 unit? ;)
lol...
That's crazy, you can't do that! :notacrook::nixweiss::cheers::DQuote:
Originally Posted by redhardsupra
oh thats coming soon.:grd: :DQuote:
Originally Posted by redhardsupra
I'll drink to that!Quote:
Originally Posted by redhardsupra
:beer:
The good news is the problem :bash: that has been delaying the BB logging implementation was fixed yesterday.
The bad new is... there is no bad news for a change. Except that BB logging is still overdue.
But at least its all downhill from here.:notacrook:
Regards
Paul
The tables used in EFILive are getting a full rewrite. Setting cell attributes such as "hidden cells" on non-rectangular areas of user-selected cells is high on the list.Quote:
Originally Posted by mr.prick
Regards
Paul
sweet i know there are more ideas out there.Quote:
Originally Posted by Blacky
how about in addition to min/max/avg we also get standard deviation for this group of values?
Leave him alone until BB logging is out, remember I'm going to the Nurburgring in 12 days and Neeeeeeeed the logging function :master:
:wave:
I'll get my coat ;)
Jim
So hows AutoCal going? I have a friend who wants a tune but wants to be able to switch back to stock when his girl drives it...
Guys, please keep in mind that the development cycle of V7 is going to start to wind down over the next few months. It's time we totally updated the software for a whole new look and feel, but still trying to maintain what everyone is used to. I mean, it will still be EFILive but there is going to be many changes (for the better we are sure).
Of course if early on in the development cycle our beta testers start to call it EFILive Vista, then we might need to rethink everything ;)
We welcome suggestions for V7 enhancements because it's not like that product will be ignored once V8 is done, but much of our focus will be toward V8. Given this is our 3rd year (I think) with V7 we have learned a lot about what people want and how to make things work better and more efficient, especially in a workshop environment.
Version 8 is going to be very open as far as it's internal runnings, so no longer is it going to be built around how GM (esp the LS1) does things. This will make any future enhancements fast and easy to implement.
There is some idea's up on the white board for Version 8 that are going to leave people who tune for a living in awe on how simple it is going to make things, features we just can't get in to V7.
Ahh, so who needs a break anyway, back to it!.
Cheers,
Ross
AutoCal is being used as the development platform and original test bed for BB logging. I've got to say the AutoCal unit makes a very cool BB logging device - but with its much larger screen, FlashScan will be even better.Quote:
Originally Posted by ScarabEpic22
Regards
Paul
My beta drive is tingling! Now if I could just get things under control at work so I can get back to tuning...
One feature that the competition has which I would really like is Real time tuning using a standard PCM. I know we have access to Roadrunner, but for some of us the investment is a large one. For those that tune on the road a feature like this would be invaluable. We have Bidirectional controls to adjust fuel and spark, which is great and all. But being able to use a tune file to control bidirectional control on a larger scale would be fantastic.
who has that?Quote:
Originally Posted by macca_779
did i waste my money on the V2! :eek:
HPT has that, it uses a "unused" region of the PCM's dynamic memory to store information, which in my mind is not a good idea because it's hard to know if the PCM really does not use that region of memory.Quote:
Originally Posted by mr.prick
$0.01
:)
Any way to turn off the ignition on the e38 (Corvette) automatically after a "write" to the PCM?
Wrong forum-- all the standard deviates (and a few non-standards) are over on HPT.Quote:
Originally Posted by redhardsupra
You need to try to talk to a shop that has used both, it's not all it's cracked up to be.Quote:
Originally Posted by macca_779
Cheers,
Ross
??Quote:
Originally Posted by eboggs_jkvl
What do you need to do now?
you know sometimes when i read a car i forget to save a copy of the stock file, is there any way that i could activate a window to pop up after the read process to ask me to save/name the file that i just read. so i would have a copy of the original stock file before i start to modify it
Thanks, :notacrook:
Not to sound like a broken record as I have mentioned it before but here goes...
While using the RR, I have found the need to actually save most logs not necessary any more. Furthemore, having to go thru the routine of the whole Cancel/Save bit just to clear the data off the scanner gets old after a while.
I'd really like to be able to clear the data while the scanner is running.
I know I am just spoiled rotten having the ability to do everything in realtime.
As for the other product's realtime capabilities...I was not impressed.
The RR is the real deal and well worth the money.
How about the capability to start and stop logging and/or recording with a small hand held unit that either plugs into a USB port, or operates wireless. That way you wouldn't have to look or reach over to the laptop keyboard while driving at ill-advised speeds on public highways. (Not that I would ever do that.)
I would like to be able to play snakes and other games on my V2 when not tuning with it ;)
How about a user-friendly way to create and edit calc pids? I always make at least one mistake first time whenever I create one.
Paul, I sent you a long list of ideas i think a while ago, whatever happened to that? I should have a lot of free time soon, so if you need help with developing some weirder bits and pieces I'd like to help.
I'm pretty much done with E40/E38/E67 tuning (properly!) so that'd be a HUGE seller if we got it implemented right in the software. Let's do something cool!
A means to dynamically place a "bookmark" while BB logging.
Bi-Dir controls available in BB mode.
How about a way to access the BCM to add / toggle non-factory features. I know of people in the trailblazer ss community that swap the steering wheel and clock spring out of the 1ss to access the DIC features found in the 3ss. The way to enable this is thru the BCM and only(i think) with a tech2 tool.:bash:
IMO, this would be a nice feature.
would love to see 0-60 timer and 1/4 mile in the scanner options ,looks prity easy to add
I want to see a 0-60 time and a quarter mile calculator too. It seems like it would be easy to calculate distance and then you already have speed.
Then who would need a dragstrip and I wouldnt see why it would not be a perfect way to test changes and tuning changes.
And then have a seperate window that would graph the delievered torque and calcualted horsepower. I guess all you would need to know is your weight.
actually getting acceleration from speed is nowhere near as simple as basic physics would have you believe. the biggest problem stems from resolution. if you have your speed in mph, you will only see a gain if you make at least one mph improvment. if you're going for small changes, you wont see it. if you have two intervals where the speed happens to be like 81.1 and 81.9, you'll see 0 acceleration, which is just not true.
if you want to measure acceleration, i recommend using a single
gear pull in a range where you dont have traction problems and where air resistance isn't significant either. so for a normal 6sp fbody 2400-6000rpm in 3rd works well. take a bunch of measurements, know what your average time is, and then make changes, see how much that time changes. this method works. in one long night (27 runs!) i managed to drop a time in that interval for my friend's car from 10.2 to 8.7secs. this is the best 'area under the curve' measurement i found. you can also divide it up into intervals so you know which changes where made biggest improvment or loss.
oh, another trick: for stuff like that measure least PIDs you can, so you can increase the sampling frequency.
High resolution is the key...
Power = m * v * dv/dt
dv/dt requires high resolution (high sampling rate) of v in order to be accurate; and mulitplying by v makes it worse.
For example, the G-Tech runs at something like 100+ samples/s...
Our PCM's Fast mode 10 frames/s just doesn't give enough resolution for accurate differentiation/integration.
If you log just one pid (VSS) in Dynamic mode, you may get 40 frames/s, accuracy will be better, but it's still not enough (not to mention you won't have many other pids).
Just a thought-- At some point additional "features" get in the way of the original purpose of a program. FlashScan is a scanning/tuning package not a vehicle data aquisition program. Some of the accelerometer-based systems currently available do a fairly good job of computing 0-60 and quarter-mile times and they're reasonably priced. I think there are much more important scanning/tuning issues to be addressed, especially since GM now seems to think that every vehicle needs a unique ECM and/or operating system. I think Paul and Ross are doing a kick-ass job and we should minimize diversions that take time and focus away from tasks that have much higher priorities.
the point of this thread is to give the manufacturer some feed back from it`s costumers and maybe help with future improvement that users want.
and maybe point out some things that are lacking .
http://forum.efilive.com/showthread....ht=problem+7.4
well, if we're going broad ideas, then i want scatter plots, trendlines, and histograms in bar form, not just numbers. also charting any arbitrary functions on top of data would be nice, along with plotting distributions of residuals between data and the fitted model.
being able to display more than one piece of data in a cell would be great. you do it already on the charts, where i can see current/min/max/avg, if i could do that in the histograms that'd really make my life easier.
color coding cells based on some other variables would be good too. ie cells with a large std dev of data in that cell should be highlighted to identify trouble spots.
and i want a pony :)
Here's what I would like...
2 independent sequence id's for file name use:
tun filename: xxxx_<seq1>
log filename: xxxx_<seq1>_<seq2>
where the <seq1> in the log filename tracks the <seq1> in the tun filename,
and <seq2> resets back to 0000 whenever <seq1> goes to a new value.
i.e. so when you save a tun with a sequenced filename, the subsequent log filenames will match the tun filename.
I use the colour coding (MIN to MAX) in the maps in Scan tool to ensure that I've hit all the cells enough times. When driving looking at colours is much better and quicker then trying to read the numbers.
Is there a way to tell the Scan tool that if the cell count is above a certain number it's reached the MAX? That way with the pic below I could set the number to 100 and will be able to see the smaller cell counts with better colour contrast.
http://nqhsvls-1.com.au/images/main....cell-count.jpg
keep the ideas coming maybe someone is watching:D