RE: CMS50D+ import issues
Hi moarZs -
The direct import protocol built into OSCAR was written for the prior CMS-50 firmware version. The CMS-50 manufacturer has updated the communication parameters in version 2.0 and it no longer is capable of a direct download. You will need to find a way to obtain the SpO2 file to use with OSCAR.
The firmware is burned in at the factory without any provision to update it thereafter.
-
Red
05-29-2021, 03:34 PM
(This post was last modified: 05-29-2021, 04:42 PM by pholynyk.
Edit Reason: Added result of web search
)
RE: CMS50D+ import issues
Thank you for digging out that device ID. Here is what I find in the Linux list of USB IDs:
28e9 GDMicroelectronics
0189 GD32 DFU Bootloader (Longan Nano)
As you can see, 28e9:028a is not included. This will probably make support difficult, but not impossible.
ETA: Just to make life interesting, I can't find a website for GDMicroelectronics
At the moment, the only solution is download the Windows software and use it to create an SpO2 file. This is less than satisfactory for Linux and Mac users.
Apnea Board Monitors are members who help oversee the smooth functioning of the Board. They are also members of the Advisory Committee which helps shape Apnea Board's rules & policies. Membership in the Advisory Members group does not imply medical expertise or qualification for advising Sleep Apnea patients concerning their treatment.
RE: CMS50D+ import issues
(05-29-2021, 01:57 PM)Crimson Nape Wrote: Hi moarZs -
The direct import protocol built into OSCAR was written for the prior CMS-50 firmware version. The CMS-50 manufacturer has updated the communication parameters in version 2.0 and it no longer is capable of a direct download. You will need to find a way to obtain the SpO2 file to use with OSCAR.
The firmware is burned in at the factory without any provision to update it thereafter.
- Red
Thanks for the reply. I'd like to confirm we are talking about the same versions.
The wizard has an option for CMS50D+/E/F and for CMS50Fv3.7+/H/I or CMD50D+v4.6
The oximeter I expressly ordered to use with OSCAR (having consulted the information in the wizard and on this forum beforehand) is the
contec CMS50D-BT
hardware version 2.0.0
software version 2.0.1
Do you still maintain I will not be able to pull recordings straight from OSCAR?
Thanks for the advice.
RE: CMS50D+ import issues
(05-29-2021, 03:34 PM)pholynyk Wrote: Thank you for digging out that device ID. Here is what I find in the Linux list of USB IDs:
28e9 GDMicroelectronics
0189 GD32 DFU Bootloader (Longan Nano)
As you can see, 28e9:028a is not included. This will probably make support difficult, but not impossible.
ETA: Just to make life interesting, I can't find a website for GDMicroelectronics
At the moment, the only solution is download the Windows software and use it to create an SpO2 file. This is less than satisfactory for Linux and Mac users.
Thanks for the reply.
Can you please state the exact model oximeter you are successfully using with OSCAR 1.2.0 on linux?
Do you know if using this Windows Sp02 software via Wine is possible?
I saw some python scripts and other tools on GitHub for a slightly more "native" approach to pulling recordings from these oximeters.
Do you have any experience with them? Would you know what the simplest and most reliable solution for my oximeter would be?
Thanks for your input!
RE: CMS50D+ import issues
I've tried Wine and Windows 10 & 7 in VirtualBox. The USB-serial connection would never complete to allow for downloading. I hope you have better results.
The CMS-50 people somehow changed their version numbering system. From all appearances, it looks like they went back in the numbering. The newer firmware has been on the market for about a year.
There is an Android app that advertises it can read the Bluetooth signal from CMS-50 models. However, its approval rating is lower than my credit score. I would not hold out hope on that one.
Using the term, linux app for cms-50 oximeters, returned some possibilities. I would need to play with them before any recommendation can be made.
I hope that you may find or stumble across a resolution to this.
- Red
RE: CMS50D+ import issues
The version 2 CMS50F is the newer version - makes no sense, I know. So yeah if yours is using the version 2 hardware and firmware, it won't work. I have an older CMS50E as well as a new CMS50F, one works, the other doesn't.
RE: CMS50D+ import issues
(05-30-2021, 09:00 AM)Crimson Nape Wrote: I've tried Wine and Windows 10 & 7 in VirtualBox. The USB-serial connection would never complete to allow for downloading. I hope you have better results.
The CMS-50 people somehow changed their version numbering system. From all appearances, it looks like they went back in the numbering. The newer firmware has been on the market for about a year.
There is an Android app that advertises it can read the Bluetooth signal from CMS-50 models. However, its approval rating is lower than my credit score. I would not hold out hope on that one.
Using the term, linux app for cms-50 oximeters, returned some possibilities. I would need to play with them before any recommendation can be made.
I hope that you may find or stumble across a resolution to this.
- Red
Sorry, but I'm still not making any progress. I dug out a dusty old computer with win10 on it and am not able to get Sp02 Assistant to find/connect to the oximeter even though it shows up via USB under devices. (no clue how to get bluetooth to work but that isn't important unless there is a way to do it on linux) I tried installing the latest driver from this year on silabs website but it makes no difference. Isn't there a simpler way to just dump all recordings from the oximeter? Having a windows computer just to install Sp02 Assistant which I don't want or need just to dump the data that oscar needs seems kind of ridiculous. I tried searching for linux solutions as you suggested but they are either for other combinations of equipment, or outdated, or incomplete, etc... Somebody on here must be using this oximeter on linux..? I could really use some more advice.
RE: CMS50D+ import issues
You will need to use, Smart Device Assistant 3.1.0.1, instead of SpO2 Assistant. This is because of the newer comm parameters of the CMS-50 are not in SpO2 Assistant. Most users report that there is a web address inside the oximeter's box for downloading this piece of software.
RE: CMS50D+ import issues
OK, thanks for the heads up. I was able to download that app in another thread. The installer registers an oldschool ocx resource file but otherwise looks identical to the other app.
Anyway, I was able to pull the recordings from my oximeter with this version
