Hondata

Before downloading the beta I was experiencing zero problems on my v3 s300. But after updating the software I began to have datalogging issues which took a couple days to figure out. If I have the "on-board datalogging" option turned "on" then the datalog corrupts on its own but with the "Onboard datalog" deactivated I can record my datalogs just fine with the laptop. I attached a datalog to show you what I mean.

Is there any way you can provide me with a link so that I can download the 2.4.5 software meanwhile a patch is released? I really need my onboard datalogging to function, thanks

Have you uploaded your calibration to the ECU since you have upgraded?

Yes and plenty of times too. I had to hide the laptop at the track yesterday and datalog with that instead of relying on the onboard datalogging. When I drove back home I tried it again with the "ON board datalogging" activated and it wasn't reading correctly. The car runs good and even shows the correct values on my phone(blutooth) but for some reason it corrupts the datalog.

I attached another datalog

Please provide your calibration so that we can test this here.

Here's my calibration.

thanks

I have the 'On-board Datalogging' disabled but if you ENABLE it then it will corrupt the datalog when the ECU starts recording based on 'engine parameters'.

Works ok here. You must upload your calibration again using 2.5.0 and delete any datalogs on the s300. Other things I notice:
Your wideband input on analog input 0 has no conversion. I see are using D14 for the wideband input, but if you have anything connected to AN0 you need to fix the analog input conversion.
The o2 sensor input has an offset of -0.8V. This means that something is not right with the wideband wiring. A 0.8v offset means it is not going to be consistent or accurate.

I deleted the old datalogs on the ecu with the 2.4.5 software and it fixed the problem.

Not sure why my analog input is like that. I must have been messing with it and left it like that by accident.

Thanks

Just to add, I experienced the same issue after upgrading to 2.5. There was an older onboard log on my ecu that seemed to corrupt any calibration I uploaded to the ecu. Clearing all datalogs on the ecu +erasing the s300 and uploading the calibration again fixed this issue for me.