Need a "flagging" tool/option
#1
Need a "flagging" tool/option
Ive been tuning lt1s for about 2 years. Still learning things, but you know what would be the GREATEST tool imaginable...a flagging tool of sorts.
So when you are logging in freescan or dataMaster you could mouse click at anytime during the log, and it would mark or "flag" that frame. In that way, you could be driving along, feel a hesitation/cam surge whatever, and flag the exact time and readings when it occured.
Would make tuning SO much easier. You wouldnt have to try and watch the laptop and drive at the same time (common we have all done it).
Who wants to try a hack, it cant be that hard to implement. I dont know much about programming, but freescan would be the easier of the two i think. Just add an extra column to the CSV output and continuosly output '0' to it. When mouse/button is clicked, change the output to '1' or something like that. Holding the button would keep changing the next frame, and the next until released.
So when you are logging in freescan or dataMaster you could mouse click at anytime during the log, and it would mark or "flag" that frame. In that way, you could be driving along, feel a hesitation/cam surge whatever, and flag the exact time and readings when it occured.
Would make tuning SO much easier. You wouldnt have to try and watch the laptop and drive at the same time (common we have all done it).
Who wants to try a hack, it cant be that hard to implement. I dont know much about programming, but freescan would be the easier of the two i think. Just add an extra column to the CSV output and continuosly output '0' to it. When mouse/button is clicked, change the output to '1' or something like that. Holding the button would keep changing the next frame, and the next until released.
#6
Re: Need a "flagging" tool/option
FreeScan is in C++, AND i found the complete code...
http://cvs.sourceforge.net/viewcvs.py/freescan/#dirlist
Common comuter guys....
http://cvs.sourceforge.net/viewcvs.py/freescan/#dirlist
Common comuter guys....
#10
Re: Need a "flagging" tool/option
Found this...
LNK1104: Cannot open file nafxcwd.lib
This error sometimes occurs when a project uses a class from the MFC but
the project settings don't explicitly tell the link editor to look in the MFC
libraries.
Go to Project --> Settings (Build --> Settings in Visual C++ 4.0). On the General tab check the box that says "Use MFC in a Shared DLL".
This error sometimes occurs when a project uses a class from the MFC but
the project settings don't explicitly tell the link editor to look in the MFC
libraries.
Go to Project --> Settings (Build --> Settings in Visual C++ 4.0). On the General tab check the box that says "Use MFC in a Shared DLL".
#12
Re: Need a "flagging" tool/option
The Ease scanner has that.
It has 6 F keys, each is a different color marker so while your recording you can hit a key and inject a color marker as many as you want and then when replaying the color markers show up so you instantly find the points of time you wanted.
Via the graph mode which shows 6 graphs at once the color markers show in each and if you do not want to see those markers you can turn then off.
It has 6 F keys, each is a different color marker so while your recording you can hit a key and inject a color marker as many as you want and then when replaying the color markers show up so you instantly find the points of time you wanted.
Via the graph mode which shows 6 graphs at once the color markers show in each and if you do not want to see those markers you can turn then off.
Originally Posted by atljar
Ive been tuning lt1s for about 2 years. Still learning things, but you know what would be the GREATEST tool imaginable...a flagging tool of sorts.
So when you are logging in freescan or dataMaster you could mouse click at anytime during the log, and it would mark or "flag" that frame. In that way, you could be driving along, feel a hesitation/cam surge whatever, and flag the exact time and readings when it occured.
Would make tuning SO much easier. You wouldnt have to try and watch the laptop and drive at the same time (common we have all done it).
Who wants to try a hack, it cant be that hard to implement. I dont know much about programming, but freescan would be the easier of the two i think. Just add an extra column to the CSV output and continuosly output '0' to it. When mouse/button is clicked, change the output to '1' or something like that. Holding the button would keep changing the next frame, and the next until released.
So when you are logging in freescan or dataMaster you could mouse click at anytime during the log, and it would mark or "flag" that frame. In that way, you could be driving along, feel a hesitation/cam surge whatever, and flag the exact time and readings when it occured.
Would make tuning SO much easier. You wouldnt have to try and watch the laptop and drive at the same time (common we have all done it).
Who wants to try a hack, it cant be that hard to implement. I dont know much about programming, but freescan would be the easier of the two i think. Just add an extra column to the CSV output and continuosly output '0' to it. When mouse/button is clicked, change the output to '1' or something like that. Holding the button would keep changing the next frame, and the next until released.
#13
Re: Need a "flagging" tool/option
Thanks for the reply, but i just checked out the price list for EASE scan. I about fell over. lol. I think it would be cheaper to hire a programmer to fix FreeScan than it would be to buy the Ease scan
#14
Re: Need a "flagging" tool/option
Originally Posted by atljar
Thanks for the reply, but i just checked out the price list for EASE scan. I about fell over. lol. I think it would be cheaper to hire a programmer to fix FreeScan than it would be to buy the Ease scan