CMS 50D+ no USB connection win10 "device not found"

I have had my CMS 50D+ for over 5 years. I haven't used for about 2 years and now I need to do some night recording to check again.

Since then I have got rid of my win XP and Win 7 computers. I install software and I can see the usb device connect in win 10 on com 7 but it live and recorded data ( red and green ) its shows device not connected. My CMS seems to be working well - new batteries etc. Is this a bad cable or unit or is not compatible with new win 8 and win 10?

Thanks

The only thing I know to help is to make sure you have the USB that came with the device. For some reason it requires that one and not just any USB.

Your NEW computer is WinDozes 10, likely 64 bit, it doesn't play well with 32 bit programing, and many other things, Welcome to the wonderful world of Windows 10, making the world obsolete one O.S. at a time. Jim

OkyDoky wrote:The only thing I know to help is to make sure you have the USB that came with the device. For some reason it requires that one and not just any USB.

yes its the correct cable and it comes up as Ubabrt in settings

Goofproof wrote:Your NEW computer is WinDozes 10, likely 64 bit, it doesn't play well with 32 bit programing, and many other things, Welcome to the wonderful world of Windows 10, making the world obsolete one O.S. at a time. Jim

I have an older win 7 laptop in my garage , I'll give that a shot

paradiddle wrote: Is this a bad cable or unit or is not compatible with new win 8 and win 10?

Have you checked if the manufacturer has a driver to add compatibility?

I'm using the CMS 50D+ with Win 10 and have no issues.
you do need to have the power turned on for the CMS 50D+ to connect.
If you purchased it 5 years ago you may not have the latest software version installed.
You can get the manual and
You can download the latest version of SPO2 review V 1.5 and SPO2 assistant V 2.4 from cooper Medical
http://www.pulseoxstore.com/content/manuals-downloads

Goofproof wrote:Your NEW computer is WinDozes 10, likely 64 bit, it doesn't play well with 32 bit programing, and many other things, Welcome to the wonderful world of Windows 10, making the world obsolete one O.S. at a time. Jim

Windows 10 has no issues running 32bit applications.

The issue here is a device driver which originally didn't support Win10. There is an updated driver that works with Win10 you can download as indicated above.

jtravel wrote:I'm using the CMS 50D+ with Win 10 and have no issues.
you do need to have the power turned on for the CMS 50D+ to connect.
If you purchased it 5 years ago you may not have the latest software version installed.
You can get the manual and
You can download the latest version of SPO2 review V 1.5 and SPO2 assistant V 2.4 from cooper Medical
http://www.pulseoxstore.com/content/manuals-downloads

Thank you for the link, last time I looked it was older, I gave up, my Win 7 machines failed, so I got a laptop b windows 10 64 bit, the new software works, the CSM50E is failing but still works battery is failing and display isn't bright as it used to be, but working, thanks. Jim

Did you ever get a solution to this?? I Have a Win10 laptop and just installed the drivers from the link above, and still the same "Device not found" result. Works on my old Vista box, and I have the correct cable that came with it. Unclear if the OP ever got it working with Win 10.

TIA

JH

johnshenry wrote: ↑

Wed Mar 07, 2018 9:26 pm

Did you ever get a solution to this?? I Have a Win10 laptop and just installed the drivers from the link above, and still the same "Device not found" result. Works on my old Vista box, and I have the correct cable that came with it. Unclear if the OP ever got it working with Win 10.

TIA

JH

fixed with ver 1.5 software

http://www.pulseoxstore.com/content/manuals-downloads

Differences between our CMS devices and your earlier efforts may make these comments worthless. I would be interested to know if you too can repeat your procedure after it fails the first time and have success the second time around.

I have the same problem with the CMS50I I got to replace my first one after the battery died in about 28 months. I never had the "Device Not Found" come up with the old/earlier unit, but it comes up about 2/3 of the time now with the new unit. It gives that message when I run the (same) software that came with the 50I to pull in and open the file using the Query search item. If it doesn't fail then it often does so when I click on the current day's file among all the others in my patient file. Almost every time I run the query a second time the file comes up perfectly all right.

In other words, everything seems to be normal until it fails when I run the query to find the file OR I try to open the file the query finds the first time. In either case, running the query the second time brings up the file so I can click to open it and do so with all seeming OK. Upon starting the second time around I will be presented with the Connect icon, which I then ignore, go to Files and then select to find (and then will run) the query for the most recent day.

Initially I thought the cable connection could be bad and fiddled with it upon failure. Then I found that a second attempt would produce results without touching the device.

I too have W10, but had long used my CMS device with no W10 problem.

I would try the latest version 1.5. I just fixed mine 2 nights ago as I was having sleep trouble and wanted to check the o2 and total time. It fixed mine as I tried to use the install disc and I guess its just too old.

The USB cable that comes with the CMS50D+ is not simply a USB cable - it contains a USB-to-RS232 serial converter. This is why the fat end is so fat. On my Win10 64 the device appears as a "Silicon Labs CP210x USB to UART Bridge" and generates a virtual COM port (COM4, in my case). The SpO2 Review software then starts polling the available COM ports, waiting to see which one would respond to the CMS50D+ protocol. The Windows device driver got automatically installed on my machine either with the installation of the SpO2 software or from the Windows Update repositories, and is dated 7/21/2010, ver. 6.1.0.0. It works just fine. I have additional USB-to-RS232 serial converters on my machine, and another one that is continuously connected is from FTDI (there are just a handful of manufacturers) and is not conflicting. I can see it being polled when I run the SpO2 Review software but both devices work well together. That is not always the case.

Sometimes two serial devices would conflict with each other. Other times an OEM version of the driver would not work with the specific hardware. The best bet is to try and identify the problem by isolating it: first, whether it is a conflict, or the CMS50 hardware, or the converter, or the software. Then, see if you can find exactly what is wrong with the module. Maybe start with just plugging in the converter cable and see if the COM port shows up and is identified properly. Then, try to find out whether the device communicates through the port (this may be tough). Then, see if the software can communicate with the device; I'm using the latest version. I'd suspect the most an incorrect driver or some corrupt settings left behind one. Sometimes, plugging in the cable before having the right driver could introduce those bad settings. A malfunctioning device or converter is not something that is worth fixing (just buy a new CMS50). We know the software works (it is 32-bit, but that is not an issue), so not much else to look for.

McSleepy

Solution for windows users.... it has been determined that a windows update (build 1803) has disabled the cp210x driver. Silicon labs has issued a fix. If you google "Silicon Labs cp210x driver" you will find Silicon Labs new cp210x driver. You need to down load and apply this driver for your usb to connect to your device