NefMoto

Currently having issues logging a particular car. It drops communication halfway through, loses comms for a second, etc. Dropped sample rate down to 15, and cut the k-line to run direct. Still not logging properly. Setup is default for the ecu file. Wondering who's seen this, and what you did to fix it?

Sometimes I can only get 5-6 samples a second on about 30 logged variables on my jetta's ecu, any higher and it will start logging a few samples and then just timeout.  I've never had it cut out after about 5 seconds into logging though.

I have had two different mbox S4s that did this.  But adding a direct line fixed it.  Check your obd plug, I have found the "clamping" of the female connectors inside the car side plug can be flakey.  I literally just bend them in a little and then it gets a better contact, issue solved.

This is needed practically every other car with tuning subarus.

on my gti I found that connecting @ the highest baud possible like 115k or something, 50 samples per sec, logging 28 variables and it fails twice in a row then connects and stays connected indefinitely until I hit ctrl-c. Instead of the periods(.) that shows that it is logging I get upper and lower case "O""o" 's
I do this after the engine is running.

Before going with these settings me7logger was straight up shotty at best in connecting for me..

Read the README

It was the HDD registering a shock and shutting down :P

Good to hear that you got it sorted.

Still interested in the next one.

I'll send it over :)

Thanks again for the help.

yea thanks, after opening it up in notepad it showed a whole run on document lol I opened it up in notepad++ and its perfectly readable.

I knew the o's and ! meant something was up but with these settings it logs on the third try everytime. How off/inacurate could the logs be like this?

not sure if it matters in this situation but I make sure the clock sync option is also selected.