Apnea Board Forum - CPAP | Sleep Apnea
O2 import DST > ST 1:14am happened twice - Printable Version

+- Apnea Board Forum - CPAP | Sleep Apnea (https://www.apneaboard.com/forums)
+-- Forum: Public Area (https://www.apneaboard.com/forums/Forum-Public-Area)
+--- Forum: Software Support Forum (https://www.apneaboard.com/forums/Forum-Software-Support-Forum)
+--- Thread: O2 import DST > ST 1:14am happened twice (/Thread-O2-import-DST-ST-1-14am-happened-twice)



O2 import DST > ST 1:14am happened twice - dgconder - 11-03-2024

Unfortunately my cpap session started at 1:14 am DST last night. The problem is there were actually two 1:14 am times because we were coming off DST and transitioning to ST. Normally I would just use the adjust time feature for this. If I pick 1:14 am it internally chooses 1:14 Standard time. I need the first one. If I pick 00:14 it picks Daylight Savings time. So I am coming in an hour early or an hour late with the O2 integration. I wonder if there is some way to temporarily modify my computers system time or something to fool this import into putting the data in the right place?


RE: O2 import DST > ST 1:14am happened twice - Crimson Nape - 11-03-2024

Not knowing what oximeter brand you are using makes this an impossible to answer question. If it is a Viatom/Wellue then the binary source (cellular or PC acquired) is another factor.
- Red


RE: O2 import DST > ST 1:14am happened twice - dgconder - 11-03-2024

(11-03-2024, 12:32 PM)Crimson Nape Wrote: Not knowing what oximeter brand you are using makes this an impossible to answer question.  If it is a Viatom/Wellue then the binary source (cellular or PC acquired) is another factor.
- Red

I am using data files imported to sp02 format from a contect sensor. I believe the API to import directly from the o2 device or from data file is the same. I have looked at these files with a hex editor. They appear binary on nature. I did see a python script someone wrote to export sp02 to csv. I might be able to export the data to css and edit it. But even if I could, I still feel like I might be up against the same limitation of import into OSCAR. your thoughts?


RE: O2 import DST > ST 1:14am happened twice - Crimson Nape - 11-03-2024

OK, in the Oximetry Wizard is the option to specify a starting time and date.  Have you tried this? Also, a CSV file will not be of any benefit to import into OSCAR.
- Red


RE: O2 import DST > ST 1:14am happened twice - dgconder - 11-03-2024

(11-03-2024, 02:03 PM)Crimson Nape Wrote: OK, in the Oximetry Wizard is the option to specify a starting time and date.  Have you tried this?  Also, a CSV file will not be of any benefit to import into OSCAR.
- Red

As I explained in my initial post, I am familiar with the starting date and time specifier. the problem is the there are essential two instances of 1:14 am today on Nov 3rd. the first one being 1:14 Daylight savings time and the 2nd being 1:14 Standard time. This is because we transitioned from DST to ST last night. I also explained that when I use 1:14 it select Standard time. If I select 00:14 it selects Daylight savings time. These two times are actually two hours apart.


RE: O2 import DST > ST 1:14am happened twice - dgconder - 11-03-2024

(11-03-2024, 11:30 AM)dgconder Wrote: Unfortunately my cpap session started at 1:14 am DST last night. The problem is there were actually two 1:14 am times because we were coming off DST and transitioning to ST. Normally I would just use the adjust time feature for this. If I pick 1:14 am it internally chooses 1:14 Standard time. I need the first one. If I pick 00:14 it picks Daylight Savings time. So I am coming in an hour early or an hour late with the O2 integration. I wonder if there is some way to temporarily modify my computers system time or something to fool this import into putting the data in the right place?

I found a work around to this issue. I went into my computers time and date settings, I left the same timezone selected but told the computer my area does not practice DST. It did not change anything because we went off of DST today. I was then able to import the data and sync it with the apap data. Now that it is imported I should be able to set it back and not have any issues.