wierd datalogging with CM and 486
wierd datalogging with CM and 486
I finally got my Toshiba T4500 (486) hooked up to my '88 Corvette and did some logging at the dragstrip and on the drive home. When I got home and copied the log files to my desktop, the files were a mess. There were huge gaps in the data samples. I would have samples from about 0 to 3 seconds, every tenth, but then no sample till 30 seconds. It would sample a few points, then a huge time gap again. I was running through Windows 3.1 and from/onto the floppy ( I had just gotten the computer to work, so hadn't gotten HD set-up). Is this a unique problem or have others experienced this? Was it due to running from / writing to the floppy drive? Was it due to running through windows? Any insight would really be appreciated. I could email ya the log files. Thanks
Supreme Member
Joined: Jul 1999
Posts: 1,577
Likes: 0
From: Baton Rouge, LA, USA
Car: 87 T/A
Engine: 441 SBC 12.5:1 0.680" Lift
Transmission: T-56
Axle/Gears: 4.10 TruTrac Moser 9"
Yeah, floppys gonna kill you on speed.
One thing you might want to do is to set the defaults parameter for datalogging to 'A)bbreviated' datalog and not 'F)ull'. You might be able to keep up that way. But the floppy's still gonna kill you.
As far as running out of Windows, you were probably OK. I'd say it's the full log option combined with floppy writing, a deadly cocktail to slow your logging.
What's happening is that the program is waiting for the data to be written to the disk. I'll put an option in there so folks can specify the interval of datalogging. If they set it to zero, the logging frequency will be a little slower (about 7-8Hz), but there will be no skips. It'll also work the PC drive. Or, just log every 30 seconds and have little gaps here & there.
One thing you might want to do is to set the defaults parameter for datalogging to 'A)bbreviated' datalog and not 'F)ull'. You might be able to keep up that way. But the floppy's still gonna kill you.
As far as running out of Windows, you were probably OK. I'd say it's the full log option combined with floppy writing, a deadly cocktail to slow your logging.
What's happening is that the program is waiting for the data to be written to the disk. I'll put an option in there so folks can specify the interval of datalogging. If they set it to zero, the logging frequency will be a little slower (about 7-8Hz), but there will be no skips. It'll also work the PC drive. Or, just log every 30 seconds and have little gaps here & there.
Supreme Member
Joined: Jul 1999
Posts: 1,577
Likes: 0
From: Baton Rouge, LA, USA
Car: 87 T/A
Engine: 441 SBC 12.5:1 0.680" Lift
Transmission: T-56
Axle/Gears: 4.10 TruTrac Moser 9"
Well, you'll probably have some small gaps for now, but it should be much better...
Thread
Thread Starter
Forum
Replies
Last Post




