I have the hulog data logging interface, and Im using freelog. Im getting really slow readings. my computer has an amd 1.2 ghz possessor and 224 mb of ram. what can I do to speed it up?
-
spin city -
get more ram. lol.
Shit sounds slow.
You have all the settings as they should be? Baud rate should be 38400, set latency to 1.
CrzyTuning now offering port services -
yea, I'm getting a reading about every second or 2. lol. how do I know how many milliseconds between readings if I minimize free log? is that saved to the log anywhere?spin cityComment
-
On the Wideband tab, under the settings, make your hits box lower.
Disable the last check box in that same tab."enable quad cell averaging"
Besides that, the only way you'll get faster readings is by getting a faster computer, lol.
I don' think freelog has the option to mess with the refresh/sample rate.
CrzyTuning now offering port servicesComment
-
i wouldnt think that your computer is what is making it slow, I mean the information coming through is that of a voice modem is it not?
"You've done more threatening prescription drugs..."
"the character of a man can be judged by how he takes his criticism"
"Quoting yourself is like, masturbation" -StarchlandComment
-
Yeah. If the computer cannot sample the data and process it will be slow.Gary A.K.A. Carter
[sig killed by photobucket]Comment
-
according to task manager the program is only using 5k memory. it eats up all the cpu resources it can. the buad rate under usb serial port properties was 9600 under device manager. according to everything I see in device manager, the usb devices are in com4 and when I select com4 in freelog it logs data from the ecu, but loopback and sanity test fail on com4. this computer isnt that great but I think it should do better than a 1400 ms interval between data sets. im going to try to set the braud rate to match and see if that works.spin cityComment
-
yeah maybe check around with your settings and maybe look into drivers,etc.
Im just thinking the information flowing out of a diagnostic port from a piece of equipment from 1992 is tripping your computer up, then something is up at the computer end.
"You've done more threatening prescription drugs..."
"the character of a man can be judged by how he takes his criticism"
"Quoting yourself is like, masturbation" -StarchlandComment
-
yea, i didn't install any driver. maby that is the problem.spin cityComment
-
you need to set your baud rate to 38400
CrzyTuning now offering port servicesComment
-
I updated the drivers and messed around with a bunch of settings and still no luck. this computer is a pos. if I look for a new laptop what should I look for to have a decent speed while logging? what setups are you all using and what kind of speed are you all getting with data logging?Last edited by dbsharp; 10-05-2007, 03:10 PM.spin cityComment
-
did you try doing it in safe mode or something. Shit i dunno it doesnt seem right to me.
"You've done more threatening prescription drugs..."
"the character of a man can be judged by how he takes his criticism"
"Quoting yourself is like, masturbation" -StarchlandComment
-
Laptop speed has a huge impact on how fast you datalog.
But you shouldn't need any drivers for datalogging with a hulog/hondalog cable. I didn't(maybe I already had the drivers since I also have moates burn1, and it all comes in one folder).
But yea, baud rate NEEDS to be at 38400, latency set to 1. Try com1. If it's being used, use it anyways.
I'm currently using a pos laptop too. Not sure how fast it is really, but I get decent logs.
Make sure you don't have your anti virus running, or anything else.
CrzyTuning now offering port servicesComment
-
woohoo! new laptop on the way. I assume that a intel duo 2.0 ghz possessor and 2 gigs of ram should do the job.spin cityComment
Comment