Originally Posted by svtf1417
Well I remember a couple times we stayed up past 10pm while you had control of my computer and trying to get this thing not to freeze up and I stumbled across a method that helped me out and hasnt stopped, but I know computers are all different.
1) Your going to need to have your laptop hooked up to the Xcal and the Xcal plugged into the OBDII port with the key on run.
2) Open Livelink, then open your saved livelink configuration. DONT connect to the vehicles ECU.
3) Go to commands and click "Configure Datalog Items". This will bring up all your PID's that your datalogging and the catagories will be expanded if your using a PID in that section.
4) Pick a PID that already has a check mark by it, un-check it, then re-check that same box and hit OK. In the bottom left it should say Setting Up or configuring or something along those lines.
5) Set up your analog equations and anything else you would normally do.
6) Enjoy datalogging again!
Again, this may not work for everyone but I encourage people having freezing issues to try it. I was sick to death of spending 4-5 hours a night in hopes that I might get Tom ONE WHOLE DATALOG a night.
I read what you posted in the knock sensor thread but didn't understand what you meant, but this made it wery clear thanks for putting it into steps. Luckily the past few data logs i have done have gone ok with only a couple of freezes in them, nothing like i was having last week. I'm sure the problem will come back eventualy though and I'll be sure to try this. Do you do this every time you data log? I have been trying to connect to the ECU where you said not to in step 2. Lately seems like ever since this issue popped up it says that it does not match my ECU, but loads the list anyways and will still data log (well at least for a minute). Step 6 Is the part i realy miss, before these issues me and Tom would get 2-3 datalogs a night sent back and forth and now i'm lucky to get in 1.