Incomplete download of HOBO scraped data by KiDAT

[Patrick Larson]

RVCA has a scraper routine that downloads data from the HOBOlink website for 5 HOBO RX3000 and U30 dataloggers. The process often fails to take all of the data into the hot folder despite the files being up to date. There is mention elsewhere of a driver being developed for HOBO devices that might solve this but, if not, does anyone have any suggestions on how to grease the passage of the data through KiDAT?

[SteveWKISTERS]

Hi Pat,

After reviewing the files you sent, it appears that KiDAT is not converting files that use a timestamp that is different than expected. At some point through the Hobo file the timestamp switches to a new format, and KiDAT ignores these values.

I believe Holly Evan's post on the Hobo ProTemp Logger solves this issue. She recommends forcing a download in 24 hour time to standardize the timestamp throughout the file. See below.

Hi,

The issue is with exporting from the HOBOware. Need to identify 24-hour time format in the Export settings under Preferences. If this isn't done then the exported file flips back and forth between formats / doesn't always recognize the date time stamp as a date.

- Holly Evans

[Patrick Larson]

This is what I just sent to Steve via email. I don't know what is happening with the time dropping the seconds but it doesn't seem to be causing a problem for WISKI (time format appears to have changed going September to October):

09/30/2018         10:00:00 PM       1.20
09/30/2018         11:00:00 PM       0.20
10/01/2018         12:00:00 AM      0.20
10/01/2018         01:00:00 AM      0.00
10/01/2018         02:00:00 AM      0.00
10/01/2018         03:00:00 AM      0.00
10/01/2018         04:00:00 AM      0.00
10/01/2018         05:00:00 AM      0.00
10/01/2018         06:00:00 AM      0.00

The script formats the date as "MM/dd/yyyy HH:mm:ss". How it gets to be AM and PM from that I don't know but it does.And that is in the data not at the end where the problem we are having is the data is not up to date..

[SteveWKISTERS]

Changing the timestamp format can have unintended consequences - WISKI may catch some values, but likely won't recognize all of them and you may end up with truncation. You need to figure out how to get your timestamp values into 1 consistent format with the script that you're running.

Has anyone else run into this problem before? See attached CSV screencap as an example. About halfway though the timestamp shifts from a String with values in 24 format to a Number/Date in non-24 time (although it's displayed in 24 hour time).

Steve with KISTERS