1.) Version of Configuration Tool being used: 2.7.10324
2.) Model Number of Unit, PV750, Pv450, etc: PV450
3.) Operating System: Windows 7 64-bit
4.) Clear and accurate instructions so we may recreate and troubleshoot the issue. (See Below)

Good Morning,

We have both "Add timestamp if hardware supports a Real Time Clock" and "When out of space, delete old log entries instead of sending error." checked in our configuration.

On my end, the log will stop logging if it reaches 134mb on a PV450 (max datalogger limit in PowerVision set to 131mb), and does not successfully export when attempted (if you reset power and try again, you will be able to export some of the log, but not all.)

Looking at what I was able to retrieve from my last test. (see reset comment above) I retrieved 175735 entries of data that were the "beginning" of the log file. And 1 line that to me seems like it was from the very end (the time stamp is almost 2 hours different than the previous line)

Any ideas what may be the cause of this?

Thanks!

Sorry, I missed this. I thought you were working with someone already on this internally

I don't know of any reason why the log would be failing as you describe. We have fixed a few things in our internal builds if you would like to test those. Alternatively if you want to send me a test to demonstrate the issue, I can have the developer look at it and see what's failing.