Enabling data logging causing issues

[90civichillclimber]

When I enable data logging my ecu losses sensor data for a split second at random times. It’s completely random data as well. I’ve seen 998psi of boost and 55000 rpm for example. It sets error codes for that split second as well then they disappear. Could be any where from 5 to 12 error codes but I can read them quick enough. When data logging is disabled it seems to not happen. I thought it was my s300 board so I bought a new s300 in a refurbished ecu from Burton racing. I have the same issue with it. Changed obd0 to obd1 jumper harnesses. Same issue. Switched the ecus into 2 other cars. Same issue. It seemed to start happening when I updated smanager to version 2.8.5.0. Serial on the one s300 is 64956
Any help would be appreciated

[Spunkster]

Are you referring to on-board datalogging?

[90civichillclimber]

Yes. When I enable on-board logging. When it’s disabled everything seems to work correctly

[Spunkster]

Are you using the on-board datalogging or are you just datalogging with a laptop?

[90civichillclimber]

I’m trying to use the onboard logging during races. It seems to data log fine when using the laptop

[90civichillclimber]

As soon as I check the box to enable on board logging the issues start. I can watch them in real time with the realtime update checked. Just with the key on engine off it’ll do it. If you uncheck the box the issues stop. As soon as you check it again the issues start.

[Spunkster]

Try downloading the most recent version of software from the website and upload your calibration to the ECU using that version and see if that resolves the issue.

[90civichillclimber]

Ok. Yeah I tried to update to the newest software. I even completely uninstalled everything first. Same issue. As a last ditch effort before buying a Haltech elite, I bought a new laptop. Downloaded smanager and the drivers. Connected to the s300 and reloaded the tune. Started the car. Everything was working correctly. So, I enabled the onboard logging. No issues right away like before. I left it running for 5 minutes with no issues. Uploaded the tune to my old s300. Same thing. It’s all working now. Looks like the issue was in my old laptop. It’s about 10 years old I’d say.

[90civichillclimber]

The problem is back. I tried onboard data logging through the ac switch and psp switch. Also with engine parameters. As soon as it starts logging the s300 starts seeing bad data and the car will run poorly. I turned on board off again with smanager and the the problem went away. If I record with the laptop, it works correctly. The only way I’ll be able to datalog is with the laptop plugged in and recording at this point. Both ecus and s300s have this problem.

[Spunkster]

Are you using resistor or non-resistor type spark plugs?

[90civichillclimber]

bkr9eix

It’ll mess up even if it’s just key on engine off

[90civichillclimber]

I have managed to catch one of the blips with error codes in a log

[90civichillclimber]

It’s around the 28 sec mark. Sitting and idling when it happened. Onboard data logging with the ac switch as input

[90civichillclimber]

Another issue has popped up. Occasionally after I upload a change and turn the car off the tune reverts back to a base map type tune and I have to upload my tune again.