Ha my CS classes wanted us to use Crimson Editor, hasnt been updated in 5+ years now and the project is dead. Switched to Notepad++ 2 years ago, really like its versatility.
Printable View
Ha my CS classes wanted us to use Crimson Editor, hasnt been updated in 5+ years now and the project is dead. Switched to Notepad++ 2 years ago, really like its versatility.
Allow the engine oil pressure calc pid to show up for Camaro/Firebird (so we don't have to artificially enter a Corvette VIN).
Scantool chart data highlighting/selection -> Tunetool table cells highlighting
currrently this has a limit of 100 frames
can this be made a user option (to select how many frames) (the user is responsible for any slowdown resulting from setting this to greater than 100);
can there be other options, such as highlight the table cells where the local maximum/minimum occur in the highlighted/selected chart portion (rather than highlighting cells from just the first 100 frames);
other options regarding this that I have not yet thought about... :doh2: i.e. that you may have.
Can we add the tool bar options to the conversions tab?
Linear Fill, Smoothing or user defined custom labels.
Can we see about adding B9021 minimum transient p/w.......(Minimum injector pulsewidth during transient conditions
This table has been shown to limit the minimum pulsewidth in some operating systems.) or it's equivalent parameter to the 1mb PCMs???? My OS is 12587603 and i would like to have this option. Or could it be added to the corresponding COS3????
Thanks
Corey
After doing some black box logging and opening the log in the scan tool, I would like to be able to open a pid file to add calculated pids to my log (Like for calc.ve). It won't let me do this after there is data in the log file.
You can add calc_pids to a log provided the prerequisite pid(s) were logged.
They can also be set to open automatically in the V8 software w/BBL.
Like mr.prick said, you can add calc pids after a log was taken (if it contains the prereq. pids), and you can save them into the log.
Yeah, it's just annoying to have to add like 8 of them, especially since some of them depend on previous calculated pids. I can save the pid file, but can't open the pid file when there's already data in the log.
You can pre-select calculated PIDs for black box logging so that they are already added to the file when you load it into V7.Quote:
Originally Posted by nevinsb
See image below...
Regards
Paul
Thanks Blacky! I'll give that a try.
Sorry if this may have been mentioned before, or perhaps it exists and I just haven't figured out how to do it. I'm still a raw newbie at this.
I find that when I am viewing playback of a log file, that I may want to jump to an anomalous value that I believe may be in the data. Somewhere.. So being able to search the data based on a value (above, below, range) would be extremely helpful. And yeah, I'm pretty sure it would be pretty tough to program something like this that would suit ANY data stream.
That feature is included in the new V8 Scan Tool design.Quote:
Originally Posted by Rich Z
Meanwhile in V7, you can create a calculated PID in V7 that returns 0 for "in-range" data and 1 for out of range data and then manually scan through the log file to see where the calc PID is 1 or 0.
For example, the calc PID below returns 1 when the spark is >25 and 0 when it is <=25.
Attachment 14314
The calc PID is defines like this:
RegardsCode:# ==============================================================================
# File details
# ------------
#
# This section defines various details about the file format.
*FILE
#Parameter Value Description
#---------- ---------------- ---------------------------------------------------
VERSION 7.1.1 File version
DECSEP . Decimal separator used in this file
# ==============================================================================
# Units
# -------------------
# See sae_generic.txt for more information on the *UNITS section
*UNITS
#Code System Abbr Description
#-------- ---------- -------- -------------------------------------------------------------
None None "" "No units"
# ==============================================================================
# Add slot definitions here
# --------------------------------
# See sae_generic.txt for more information on "SLOT" formats
#
#Units Low High Fmt Expression
#------------ ------------- ------------- ---- --------------------------------------------------------------
*CLC-00-001
None 0.0 1.0 .0 "Iff({SAE.SPARKADV}>25,1,0)"
# ==============================================================================
*PRN - Parameter Reference Numbers
# --------------------------------
# See sae_generic.txt for more information on the *PRN section
#
#Code PRN SLOT Units System Description
#------------------------- ---- ------------ ---------------- ---------------- ------------------------------------------
CALC.SPARK_HIGH F400 CLC-00-001 None Performance Spark Montior
Paul
Thanks for the reply, but I hope version 8 does this search automatically. To be quite honest, MANUALLY searching through a log playback for that trigger would be no more helpful than just scanning through looking for the event itself I am interested in. I would only be looking at a different line in the display.
Yes. :)Quote:
Originally Posted by Rich Z
OK, now how about the log file playback controls themselves in version 8? Will it have the capability of starting or resuming playback (forwards and backwards) from any point in the file, or will it be limited as it is in version 7 with ONLY being able to start at the beginning of the file? For instance, putting in a note in the file position while paused would be helpful, and then later on being able to jump immediately to that point and then resuming playback (again forwards or backwards) at that point would be helpful. While manually scanning through a log file it would be helpful to be able to resume (or even start) playback at any point in the file.
Thanks.
I saw that request earlier but I can't understand why it is something that would be useful? What extra information can you obtain by playing back the file that you can't obtain simply by looking at (and/or scrolling through) the charts?Quote:
Originally Posted by Rich Z
The only reason a playback option exists at all is so that we can show unattended demo charts scrolling across the screen when the software is on display at trade shows. I can't think of any other use for the playback mode.
If there is some reason that playback to/from preset points is useful then I'd happily incorporate it into the software.
Regards
Paul
OK, suppose I want to scan through a log and find a point where I want to just have the log "play" while viewing the interrelationships between the various traces? Well, that WAS interesting. Well, let me see that again. Oops, have to start over from the BEGINNING. Hmm, that section was 10 minutes into the drive, so I guess I can go get a drink in the next 9 minutes. Yeah, I can set a note at the spot I want to make note of, but once I jump directly to that point, then what? Matter of fact, I can see where setting a point A and a point B and continually looping through that segment would be helpful.Quote:
Originally Posted by Blacky
Also I want to take video of certain sections of the logs for instructional purposes if I want to demonstrate to people on my own forum about how the results of a scan can show what is REALLY going on with the engine's sensors and controls. Right now this would be downright painful to try to do. Heck, did you see my thoughts on being able to convert a log file playback to a video file? I'm surprised that people who teach this stuff have beaten down your doors asking for it. The log playback function gives us the ability to display information from sensors in real time. I find a lot of value in that I can see things HAPPENING in real time, which means while the display is in motion. Watching some values ramp up or ramp down in relation to one or more values causing such changes is invaluable in understanding what is really going on. Heck, I've got a problem with the IAT sensor or harness that is spiking the detected incoming air temperature. It's downright instructive watching how a fault like this affects other parameters concerning the performance of my engine.
Heck, I don't know, maybe I'm the only one who thinks that scanning through the logs is an incredible learning tool. That is why I am taking the time to LEARN the scan tool before jumping into tuning. My perception of this is that tuning without understanding what you are doing or seeing BEFORE you make the first table change is much like shooting in the dark, then waiting to see if you hear something yelp that it got hit. Everything going on in the engine based on what controls tell it to do, and what sensors detect are happening because of those controls, as a flow of data that this tool allows us to view AS IT HAPPENED during the logging session. To me, that data means a whole lot more if I am watching it happen as that flow, and not simply static images snapped along the way. Log files are going to have segments that are more interesting and telling than others, some being intermittent based on hapstance, and others simply because the driver changed the values of the controls to make those changes. So having a manner to get to them quickly, and play ONLY those sections would be a benefit to someone reviewing all the data being displayed.
Have you ever processed raw video files to paste segments together? Only the rawest of newbies think that their entire video is worth watching from beginning to end. You cut out the fluff and things that aren't pertinent and interesting by jumping to those sections you want to include in your presentation and extracting them into your final cut. Any video software that had the limited controls of EFILive for viewing the video (the equivalent of the data displayed in log files) would drive someone trying to use that software insane. Heck even the most rudimentary video processing software (like Windows Movie Maker) will resume play from any point you select on the timeline.
Can I be the only one who sees the value of using EFILive's data logging for diagnostic purposes? Isn't this what everyone does when they log files after making tuning changes?
IMHO....
You can replot & scroll the log forward then crop the section orQuote:
Originally Posted by Rich Z
filter out frames you want/don't with a calc_pid based on frame number.
PHP Code:#Units Low High Fmt Expression
#------------ ---------- ----------- -------- --------------------------------------------------------------
*CLC-00-004
Frame 0 99999 .0 "frame()"
#Code PRN SLOT Units System Description
#--------------------------------- ----------- ------------------- --------------- -------------------- -------------
CALC.FRAME F004 CLC-00-004 Frame Conditions "Frame Number"
Quote:
Originally Posted by Blacky
IMO
Playback (forward or backward :hihi:) is frivolous when you can record, filter, cut & paste.
This seems to be a case of not knowing what can be done with the software. :angel_innocent:
And this is better and easier than just having the controls programmed into this tool? :laugh:Quote:
Originally Posted by mr.prick
This will get you what you want until then. :blahblah:
Well then, in that context, thank you for your help.Quote:
Originally Posted by mr.prick
Hi Rich,
Most of us manually move the chart inspector/cursor back/forth thru the chart when analyzing a log...
if you wanted to to play segments of the log, then you could crop each segment and save to a new file (one segment at a time), this would then let you integrate with your video(s).
Yes, I have been doing that as well, but when scanning through a LONG log file just looking for anything that looks *different*, it's quite tedious that way. Maybe when I am more familiar with this stuff I won't feel like I need to look at EVERYTHING, or will know exactly where I need to look for something. But right now, I just don't know what is "normal" and what is not. So I am presuming the longer I look at log files, eventually SOME of the stuff will have to be considered as normal, and the stuff that is not normal will become more apparent to me.Quote:
Originally Posted by joecar
Ooh, I've got another one....
I'm looking at a log file, and want to look at ONLY the relationship between two of the values being tracked. Sure would be nice to have a way to QUICKLY hide the tracks I don't want to see at the moment. Something like right clicking on the trace or the label and just being able to select "hide" and then being able to make it visible again as needed. Kind of like when looking at multiple parallel audio clips you can mute any track separately.
Just a thought....
Sure would be simple that way. Right click and have a list of all PIDS in log then click the ones you want to see! Simple! That is the way TunerPro RT is set up...
In the V8 scan tool you can do just that. Just right click on the PID in the chart and select "Options->Show PID" to hide/show the PID.Quote:
Originally Posted by Rich Z
Regards
Paul
Is it safe to start learning the V8 Scan Tool? I've never touched it.
My understanding is V8 is going to replace all V7.5 stuff?
The V8 Scan Tool will open/display existing V7 log files. It doesn't support pass-thru scanning yet.Quote:
Originally Posted by EagleMark
The charts are fully operational, the gauges and maps are still under development.
Regards
Paul
Suport for Dodge gas engines,
any chance of this happening?
:angel_innocent: :w00t: :coool: :drool: :Eyecrazy: :D:cucumber: :hihi: :cheers: :grin: :rockon:
None
Mike, did you get a Hellcat...?Quote:
Originally Posted by mr.prick
SRT8 :w00t:
Diesel has all the fun. :doh2:
I thought about buying an SRT-8 300 myself a few times especially now ours get the 8 speed, but I just can't bring myself to jump the GM ship. And your final statement isn't quiet true, the 3.0L Eco-Diesel in my garage remains stock after 2 years with no chance it'll ever be tuned, sometimes we have to pick our battles and some aren't worth taking the fight to (not saying that about the SRT-8).
all as well.
i know the new stuff is getting harder to crack.
fyi
the 8 speed torqueflight is nice. :angel_innocent:
Actually the new Chrysler ECM's (from about early 2015 I think) are a pull apart to tune job due to the security levels in them, so yeah it is heading down the euro computer path.
Have you see the 'gear selector' for the 8 speed in the 300? So dumb.
One small change that I would like to see is that I want to be able to pull another 60 deg. of timing with the nitrous monitor in COS5. I'm using the base spark park/neutral table to pull timing and the nitrous monitor to control fuel but it would be great to do this in one place as well as any speed and rpms above 4800 rpms. I would think changing the limit from -20 would be simple enough. You could call it the nitrous monitor/anti lag function and put another feather in your hat!
Sorry, LS1 Custom OS's will not be modified again from what they are.
Typical... So will V8 ever be done? Or is that just a pipe dream?
Why is it typical?Quote:
Originally Posted by greasess
The LS1 custom OS's were written 10 years ago and have been running stable ever since. It makes no sense for EFILive to go back and spend months rewriting them to add additional functions that a handful of people have requested over the years. I don't think people realise just what is involved and the time and resources it takes to do it and to be frank there would be no financial incentive to do so. This flows down to other custom OS's we've written in the past on older platforms (both Gas and Diesel), once they are stable we are very reluctant to ever touch them again.