Oscar Crash to desktop on SP02 import

[WallyPepper]

New to Oscar, new to Apnea Board. Not new to tech, CPAP, software troubleshooting. Here is the issue I am seeing:

When importing Viatom/Wellvue data into Oscar I get an imediate crash to desktop. Happens every single time. Happens after a reboot.

The System I am working on is a Windows 11 Version 23H2


Oscar is version 1.5.3+master-7267dafa

I currently have 4 days of ResMed Airsense 10 data imported. Last night I used a Wellvue SA-10AW finger pulse oximeter. The data appears to be intact if I use ViHealth (Android) or O2 Insight Pro (Windows). ViHealth version number is 2.75.9, and O2IP is version 1.8.9. One thing I noticed is that O2IP copies the ViHealth data without the .dat extention and ViHealth has the .dat extention. Both files, PC and Android are byte-for-byte identical.

With the Oscar Debug window open during the import two lines appear for a second before the crash, they are:

Code:

699651: Debug:    ViatomLoader::Open( "D:/Documents/O2 Insight Pro/DATA/20240617224258" )
699651: Debug:    "D:/Documents/O2 Insight Pro/DATA/20240617224258" Unrecognized DB version number in Viatom data file 769

Please note, that if I attempt to load the .dat file, the first line changes to reflect the added file extension, otherwise the message is identical.

The Windows Application log shows the follwoing application error:

Code:

- System
 - Provider
  [ Name]  Application Error
  [ Guid]  {a0e9b465-b939-57d7-b27d-95d8e925ff57}
  EventID 1000
  Version 0
  Level 2
  Task 100
  Opcode 0
  Keywords 0x8000000000000000
 - TimeCreated
  [ SystemTime]  2024-06-18T16:16:31.4000544Z
  EventRecordID 96302
  Correlation
 - Execution
  [ ProcessID]  26188
  [ ThreadID]  32704
  Channel Application
  Computer Stark
 - Security
  [ UserID]  S-1-5-21-2802756685-4210610644-3695681220-1001

- EventData
 AppName OSCAR.exe
 AppVersion 1.5.3.0
 AppTimeStamp 661bdc08
 ModuleName OSCAR.exe
 ModuleVersion 1.5.3.0
 ModuleTimeStamp 661bdc08
 ExceptionCode c0000005
 FaultingOffset 000000000009fbe8
 ProcessId 0x1aa0
 ProcessCreationTime 0x1dac19a5e00d2df
 AppPath C:\Program Files\OSCAR\OSCAR.exe
 ModulePath C:\Program Files\OSCAR\OSCAR.exe
 IntegratorReportId 3b714d23-31cf-4ce7-aa68-e49ba98783c2
 PackageFullName  
 PackageRelativeAppId  

I have uploaded both files in a .zip to my google drive but cannot post a link until I have 4 posts.

[Crimson Nape]

That model is not listed as a recording oximeter. Only the SleepU, O2Ring, and Checkme are the only ones I am aware of that produce a proper file. Please send the files here: Dropbox Upload Request

Have you verified your OSCAR installation file's checksum to validate a non-corrupt file?
- Red

[Crimson Nape]

Update to my previous post; If it is the ($89) Oxylink, then it does not produce a valid oximeter file, since it only records in real-time to a connected device.
- Red

[WallyPepper]

First a correction, it is a Wearpulse, but essentially a Wellvue/Tiatom clone or rebrand.  It is listed as, Viatomtech SA-10BW Continuous Pulse Oximeter.

No it is not a realtime recorder, although it can do realtime but doesn't record at the same time only to the ViHealth app. It is specifically designed as a continuous recorder, able to hold 8-10 hours of data recorded at once every second. It is weird that neither Wearpulse nor Tiatomtech show it on their websites, but it is available on Amazon.

The Amazon page lists it as a Continuous Pulse Oximeter Fingertip (Amazon item number B0C3QHBLSV)

Regardless of whether or not this oximeter ever has support, but I hope it will, Oscar shouldn't just crash to desktop when it encounters an 'unrecognized db version'.

I will upload the files via the dropbox instructions you provided.

[WallyPepper]

Forgot to mention, it can store multiple sessions as it has an approximate 80 hour memory capacity.

And a clarification, it will do realtime collection directly to the ViHealth app. If you use that mode it doesn't create a data file on the device itself. So you must decide before hand if you are using the ViHealth app or not while sleeping. I choose not to then upload the data direcly to O2 Insight Pro with their pretend USB cable.

[Crimson Nape]

The data file is not Viatom/Wellue compatible. It doesn't contain the 40 byte preamble header information. It only has a 10 byte header, and most of those are zeros.
- Red

[Gyrotechnix]

I am having the same issue with my Wellue O2Ring.  I have the following configuration.

Windows 10
Oscar 1.5.3
iOS 17.6.1
VIHealth 2.30.86

I have followed the steps in the Oscar instructions to import the SPO2 data, but I am getting the unrecognized dB error also.  Is there a way to fix this issue?  I can't get the binary files to attach.

[Crimson Nape]

Hi Gyrotechnix! -
By chance, is your oximeter a O2Ring-S? If so, Viatom redesigned the datafile for this model. The OSCAR source code has the updated for this model and will be in the next release. Currently, no release date has been set. In the interim, you can download the source code and build a version yourself.
- Red