cover rep 1 was having issues with date, it was reseted and lost date and time and collected a bunch of info with the wrong time. any way we can still use that info?
**Hi Esleyther,
Attached are downloaded data from YOU from Aug 9-Aug 28th.
Also, there was a gap in YUO from July 9-21. The data you have is not sufficient for the whole gap, but perhaps you could consider tracking the time going backwards. I collected the data on the 21st and the data was still counting forward. If the timespan is continuous, perhaps we could pair the latest date recorded from the CC1 node with the day/time I pulled the data for the other nodes. Just a thought.**
cover rep 1 was having issues with date, it was reseted and lost date and time and collected a bunch of info with the wrong time. any way we can still use that info?
**Hi Esleyther,
Attached are downloaded data from YOU from Aug 9-Aug 28th.
Also, there was a gap in YUO from July 9-21. The data you have is not sufficient for the whole gap, but perhaps you could consider tracking the time going backwards. I collected the data on the 21st and the data was still counting forward. If the timespan is continuous, perhaps we could pair the latest date recorded from the CC1 node with the day/time I pulled the data for the other nodes. Just a thought.**