Does this really work?Quote:
Originally Posted by macca_779
http://www.hptuners.com/help/index.h...editor_rtt.htm
VE tuning with just the +- keys?
Printable View
Does this really work?Quote:
Originally Posted by macca_779
http://www.hptuners.com/help/index.h...editor_rtt.htm
VE tuning with just the +- keys?
Funny that this was just brought up again as I just had an idea on how to implement a system like HPTuners RTT without the need of a custom OS that uses supposed unused memory.Quote:
Originally Posted by Chunx
My idea is that currently we have the Bi-di controls which are great and I tend to use delta timing quite a bit. But how about a customisable table built into the scan tool that works as a look up table for the Bi-Di's. I'll use timing as the example as this is what I use the bi-di's mainly for. Now ignoring all the modifiers that are applied to B5913, most of the time the data in this table is what we are working for. The way I see it is if the software is logging dynamic cyl air and RPM we have the axis's of a spark table and live lookup is possible as it always has been when cross referencing to the tune tool. Now if you were to fill this said table with a copy of B5913 or whatever you want, couldn't the software have the ability to apply this data to the bi-di's directly and control the forced timing option. The beauty part would of course be that the numbers in this table are only a look up table external of the PCM and thus changes to it can be applied in real time with the engine running. You could perform multiple pulls tweaking it and when your done copy it over to the tune file and apply the cal.
I think it would be a very useful addition and would require no revisions to an operating system for it to work. What do you guys rekon.
[edit] I just had another thought about this and naturally a forced timing MAP does have some negative implications for areas like idle and DFCO.. So on top of my previous idea how about a feature where on the lookup table you have areas selected where the software could disable bi-directional control automatically. Then only when in the segments which you want live look up of a forced value would the bi-di's be invoked and the subsequent lookup values applied.
It is something that is was available in EFILvie V5. When we brought out RR support, we dropped support for the bidi controlled spark and fuel maps because RR was so much better.
Maybe we can re-instate it in version 8, but it would not be a high priority in the version 8 roadmap.
Regards
Paul
Yes, I liked those features in V5.
I know many people I have discussed this with would really appreciate the addition. Especially from a marketing perspective it would really put the competition back another notch
Has any more progress been made on the accel enrichment tables. Even if it was limited to the COS it would help the FI guys out.
This is something that is practically a must for us SD FI guys.Quote:
Originally Posted by 5.7ute
To re-iterate the need... I went back to MAF today because I was tired of the lean stumble in SD.Quote:
Originally Posted by dc_justin
A real quick stab was yielding a full 1/2 second delay before the engine would respond. My wife's not been allowed to drive my truck as a result cause she has a tendency to rapidly stab the throttle and the last thing I need is for her to damage something.
how about being able to open LS1edit and HPtuner files?:nixweiss:
or would that be way too much to ask.;)
They have their own proprietary encryption.
There's also a mutual understanding between all parties... "you don't crack ours, we won't crack yours".
Yes, that's a little bit on the "far-away" side of way too much.Quote:
Originally Posted by mr.prick
Regards
Paul
Yeah, what Joe said. :nixweiss:Quote:
Originally Posted by joecar
Or re-phrased, you don't publicly release our format that you've already hacked, and we won't publicly release your format that we've already hacked.
Paul
Any news on this yet Blacky?Quote:
Originally Posted by 5.7ute
Yeah...that help out immensely Mick.
Transient fuelling!
time to bump this thread.
for RTACS,
i would like to be able to set the update frequency per table
instead of having a general setting.
also i am wondering if it would be possible to make a COS
for GEN3 (fbody/ybody) that could work with 58X reluctor.
Quote:
Originally Posted by hquick
x2 on the transient fueling.
is it possible to speed up the loading of logged data?
large log files take an eternity to filter/load.
Yes, currently (in V7) it is all done with disk buffers (long story - don't ask). V8 uses in memory buffers which is orders of magnitude faster.Quote:
Originally Posted by mr.prick
For a comparison, the V7 re-plot of 50,000 frames can take 5-10 seconds. On the same machine, a re-plot in V8 of 50,000 frames is less than 1/10th of a second.
Regards
Paul
Since the advent of CAN or LAN it's getting harder to swap an E38, E67, or even an E40 into an old "junk" without using aftermarket guages and bypass the A/C circuit.
I notice on GM's performance controller they have an oil and alternator light, not sure about cruise and A/C turn on signal.
One thing I suppose we can do is find the O.S. of their performance controller and have it flashed in.
Thanks for listening, you guys rock!
John
How about defining/adjusting "hot mode" tables for T42,43?
Also T43 missing tables for keeping Tap up/ Tap down "in gear"...NO overide.
Thanks guys, I know this takes time!
Cheers, John
How about being able to manually hide selected cells in a map.
Right click menu or hot key.
+1 With the climate down here, this is an addition that is needed badly. :sly:Quote:
Originally Posted by ssvolvo
Just throwing this out there, any way to have the software scan for supported controllers when issuing a read (or write, that'd be even cooler) command and then read both the ECM and TCM out back to back? Maybe even have a dialog box pop up asking for save location and filename BEFORE the read so you are guaranteed a pair of untouched stock files. That would save some time and keep people from asking why they cant tune the trans. Of course keep the existing flash commands so if you have the trans setup perfectly and are tweaking the engine you dont have to flash both, just wondering if this could be added easily (or at all).
But if not I can dream right? :)
Can Milli-volts (mV) be added to the NBO2 PIDS? (imperial/metric)
I know it can be done with a calc.pid making it somewhat frivolous,
but why not.
You can add a custom unit for the HO2Sxx PIDs so that when you press Enter on FlashScan's keypad it changes between V and mV.Quote:
Originally Posted by mr.prick
To make mV one of the preset custom options for all PIDs with V units, you can add mV to the file:
\ProgramData\EFILive\V8\EFILive.ini (Vista)
or
\Documents And Settings\All Users\Application Data\EFILive\V8\EFILive.ini (2K/XP)
by adding an entry in the [Unit Conversions] section like this:
0110=V mV 0 1000 0.000000 N
Be aware that file (EFILive.ini) may get overwritten during a future update. Currently it is set to not be overwritten but that may change in future.
Regards
Paul
This is one reason I asked.Quote:
Originally Posted by Blacky
It's not a big deal but in the scan tool GM.HOSxx is in volts only
and in the tune tool O2 switch point {B4105} is in mV. :)
Good point, that got overlooked. They really should be the same units.Quote:
Originally Posted by mr.prick
Paul
While you can't select the data file folder name during the install, you can change it once the software is installed.Quote:
Originally Posted by Wolfie
Use the Scan Tool menu: Edit->Properties->Folders and highlight the "Logged Data" item. Then click the [Browse] button to select a different folder.
You can also double-click on some items ("Logged Data" item included) to toggle the "remember last folder option".
Regards
Paul
Log filenames based on tune filenames...
e.g.
if tune filename is 12212156_0007.tun, then successive log filenames will automatically be:
12212156_0007_0000.efi
12212156_0007_0001.efi
12212156_0007_0002.efi
12212156_0007_0003.efi
12212156_0007_0004.efi
. . .
. . .
I use SyncToy v2.0 and an external HD to keep things sync'd and for back up.
When I adjust or make a new file I'll Bluetooth the files between my 2 laptops or copy from the EHD, I'm too cheap to buy a USB transfer cable.
:offtopic:
What about my idea in post #1?
How About a RPM/MAP IBPW table were we could adjust the IBPW directly (Like VE).
Paul, we briefly touched on this a few years back I think regarding the dynamic calculations used by the PCM.
98 tigershark:devil_2::master::nuke::throw:
PS: Free licenses would also be nice!
Just a quick one to express a new idea. Yesterday I was playing around with a car with poor idle quality. Eventually nutted the issue out to be shot o2 sensors causing a super rich idle. During the troubleshot I used the DVT's a fair bit to adjust IAC, Timing and lastly Fuel to see the reaction with fuel turning out to be the problem. During this testing I wasn't really taking much note of the data as the trims were fine and I was just observing the nature of the car. The thought came to mind that having the DVT's available via the V2 would be a handy addition. What do you guys think? Is it feasible to incorporate the controls into the V2 firmware.
Ryan
Working on it...Quote:
Originally Posted by macca_779
:)
Paul
Thats a swell idea!!!:thumb_yello:Quote:
Originally Posted by macca_779
Paul any future thought for bringing this back in for V8. It really would be a very attractive feature to have and one that I would use extensively. I do have a RR. But for the most part the work I'm doing on other peoples cars doesn't warrant the time for me to fit and remove it.Quote:
Originally Posted by Blacky
Brilliant. Thats great news.Quote:
Originally Posted by Blacky
I will be re-investigating adding that feature to V8, sooner rather than later.Quote:
Originally Posted by macca_779
Paul
I will use that alot...:cheers:Quote:
Originally Posted by Blacky
DVT in standalone V2...:cheers:
me x2