(11-28-2015 10:34 AM)happydreams Wrote: Keeping the linux thread alive...
(11-28-2015 10:34 AM)happydreams Wrote: I now have a CMS50F. V3.8. Can't seem to import data into SH.
I got a Veridian 11-50DP (on sale at Costco online) which except for the case color, looks like a clone of the CMS-50D.
Supplier # 19's website says the Windows software is called SPO2 Review. The Veridian software is called SPO2 Review or SPO2 Assistant Review. The software copies the recorded data over USB to a csv file with two comma separated values: SPO2 and Pulse. The csv file is good for importing into other tools (e.g. Excel), while SH needs the spoR file. The SPO2 Review software interface is so odd, that I returned an almost identical model to Amazon a couple of years ago assuming that downloading had quit working. The software apparently only downloads if the device is showing the recording sub-menu.
I think there is a good chance that all of these oximeters use the same protocol / data format, so fixing SleepyHead for one oximeter will fix it for all. Though my Veridian reports Ver4.6 at power on.
Windows users shouldn't get too complacent, since the Veridian customer service person said the software doesn't support Windows 8 or 64 bit processors (my Windows 8, 32/64 bit hybrid tablet works OK, though. YMMV). The Windows software may be turning into a zombie, something nearly impossible for open source software that enough people are willing to support (this forum seems like enough people).
(11-28-2015 10:34 AM)happydreams Wrote: $ uname -r
Also available: 4.0.0-2-amd64 and 4.2.0-1-amd64.
(11-28-2015 10:34 AM)happydreams Wrote: This should have the driver mentioned already built in. The previous link shows only a 3.x driver and mentions it is now being maintained at kernel.org.
$ /sbin/modinfo cp210x -F version
But there isn't any version tag for the kernel on disk:
$ /sbin/modinfo cp210x -k 4.2.0-1-amd64
If I enter:
$ lsmod | grep cp210x
cp210x 21155 0
usbserial 32061 2 ftdi_sio,cp210x
usbcore 128741 12 xhci_hcd,ehci_hcd,usb_storage,usbhid,btusb,ath3k,uvcvideo,usbserial,ftdi_sio,cp210x
So it looks like the cp210x driver module is loaded and attached to usbserial.
(11-28-2015 10:34 AM)happydreams Wrote: When the CMS50F is plugged in I get:
Bus 001 Device 003: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
Bus 003 Device 084: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP210x UART Bridge / myAVR mySmartUSB light
We match except we plugged into different USB ports.
(11-28-2015 10:34 AM)happydreams Wrote: $ dmesg shows
[ 2443.073710] usb 1-2: new full-speed USB device number 5 using xhci_hcd
[ 2443.203682] usb 1-2: New USB device found, idVendor=10c4, idProduct=ea60
[ 2443.203690] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2443.203694] usb 1-2: Product: CP2102 USB to UART Bridge Controller
[ 2443.203697] usb 1-2: Manufacturer: Silicon Labs
[ 2443.203699] usb 1-2: SerialNumber: 0001
[ 2443.204848] cp210x 1-2:1.0: cp210x converter detected
[ 2443.205164] usb 1-2: cp210x converter now attached to ttyUSB0
[4064646.536264] usb 3-126.96.36.199: FTDI USB Serial Device converter now attached to ttyUSB0
[4064649.144984] usb 3-188.8.131.52: usbfs: interface 0 claimed by ftdi_sio while 'brltty' sets config #1
[4064649.145745] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
[4064649.145770] ftdi_sio 3-184.108.40.206:1.0: device disconnected
[4065300.720019] usb 3-220.127.116.11.2: new full-speed USB device number 84 using ehci_hcd
[4065300.811942] usb 3-18.104.22.168.2: New USB device found, idVendor=10c4, idProduct=ea60
[4065300.811948] usb 3-22.214.171.124.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[4065300.811951] usb 3-126.96.36.199.2: Product: CP2102 USB to UART Bridge Controller
[4065300.811954] usb 3-188.8.131.52.2: Manufacturer: Silicon Labs
[4065300.811957] usb 3-184.108.40.206.2: SerialNumber: 0001
[4065301.960024] USB Serial support registered for cp210x
[4065301.960109] cp210x 3-220.127.116.11.2:1.0: cp210x converter detected
[4065302.032160] usb 3-18.104.22.168.2: reset full-speed USB device number 84 using ehci_hcd
[4065302.125178] usb 3-22.214.171.124.2: cp210x converter now attached to ttyUSB0
[4065302.125215] usbcore: registered new interface driver cp210x
[4065302.125217] cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
[4065306.451733] usb 3-126.96.36.199.2: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1
[4065306.452356] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[4065306.452386] cp210x 3-188.8.131.52.2:1.0: device disconnected
We match except for a conflict with the FTDI USB serial driver; I guess I'll have to test without the FTDI device plugged in for now. Maybe there is some hotplug magic to resolve this conflict.
(11-28-2015 10:34 AM)happydreams Wrote: SH cannot find the oximeter. "Could not detect any connected oximeter devices."
I also got the "Could not detect any connected oximeter devices." message.
I'd expect different code would be needed in Linux to access file /dev/ttyUSB0 rather than a COMM port in Windows.
However I was able to import files generated by running 'SPO2 Assistant Review' under Windows. Getting the oximeter session start time from the cpap session start time didn't work; it used a date in the 'next' (after noon) day in the future. If I manually enterred the cpap session start time the SPO2 and pulse graphs were aligned closely.
(11-28-2015 10:34 AM)happydreams Wrote: No boxes checked in Oximetry Wizard.
I didn't notice any checkboxes in Oximetry Wizard.
(11-28-2015 10:34 AM)happydreams Wrote: Any simple things I may have overlooked?
$ /sbin/modinfo cp210x -F version
Import spoR data from Windows into SleepyHead
(11-28-2015 10:34 AM)happydreams Wrote: Or things to look for?
$ screen /dev/ttyUSB0
You may have to change permissions on /dev/ttyUSB0 (e.g. add self to the dialout group) and guess the baud rate (9600 or max?)
Be sure to read 'man screen' for the arcane exit command key sequence.
If it works you'll next want the API for the oximeters or we can start digging through the source code.
(11-28-2015 10:34 AM)happydreams Wrote: I chose the 3.7+ version to import.
3.7+ version of what software?