random question to see if anyone else has ever thought about this. after many revisions, the BIN I'm running on my L98/T56 combo with a modified intake is working well for me almost all the time. The most annoying problem is that about once every 5 hours of drive-time, there will be a slight, isolated hesitation when accelerating due (possibly) to an AE issue. that's fine and well, and I could certainly do some data logging to capture it and tune it out, etc. The complication is that I might have to datalog for days and days on end until the problem occurs, keeping a notebook in the car and wires dangling around everywhere, etc., what a hassle. Thus, the topic of this post: has anyone ever created a permanent data logging setup? The setup I'm imagining (which I'm sure doesn't exist) is a small device which plugs directly into the ALDL port. It has two connectors: 1) a two pin connector that a momentary switch can be plugged into. The switch is mounted somewhere in the car. The user can press this switch as a flag to indicate "something interesting just happened". 2) a USB or RS232 or some type of data transmission port the device would constantly monitor the ALDL data stream, caching perhaps 150 frames of data in memory at all times, round-robin style. When the user presses the momentary switch, the last 150 frames in memory would be written to some sort of data file / data stream, then a flag line is written ("button pushed"), and then the next 150 frames of data as well. The device would have enough memory to capture a dozen or so such "events". When the device is full, it either stops capturing further events, or emits a beep, or a red LED illuminates, etc. After collecting a few events, you read the data off the device, and can use the data to help identify what occurred and what to do about it, etc. thoughts?

I had an old scan tool with a circular buffer in it. Along with a large red button mounted on a base that connected to the scan tool. The idea was to drive around until the engine glitched and you smack the button. It saved the data leading up to the button smack and some after it.

I actually gave it to someone, never got a chance to try it out.

Don't know what is available today. My latest creation allows for a marker to be placed in the data log. Just tap the space bar to insert it.

RBob.

That's a great addition, Bob, wish we had that in TP RT (or ScannerPro, provided I ever get it to link up...)

MonteCarSlow's NVSRAM board could probably do that nicely with some code work.

Not a bad idea... neither is fixing TP RT or SP to reognize some type of marking action in a log (like hitting the spacebar) so you could quickly zero back in on a particular area of the log.....

It may not do you much good but I read there is a simillar tool in Log works 2, the software that comes with the LC-1 WB cable. I haven't tried it to see how it works.

Only problem with Logworks is you aren't getting the ECM datastream like with DM or TP