Dutch Omrom M10-IT can't be red
xychix opened this issue · comments
I've got an issue reading my omron in VirtualBox (debian) under OSX.
Usb device is connected and shows up in LSusb so I assume my virtual machine is setup correctly.
My build process:
sudo apt-get install swig python-dev cmake build-essential cmake-data libusb-dev swig libusb-1.0-0 libusb-1.0-0-dev
mkdir ~/git
cd ~/git
git clone http://github.com/brettviren/libomron
cd ~/git/libomron
git submodule update --init
mkdir -p ~/opt/omron-build
cd ~/opt/omron-build/
cmake ~/git/libomron
#change CMakeCache.txt:57 to CMAKE_C_FLAGS:STRING=-I/usr/include/libusb-1.0
make
make DESTDIR=~/opt/omron install
lsusb | grep Omron
#Bus 001 Device 003: ID 0590:0028 Omron Corp. HJ-720IT Pedometer / Blood Pressure Monitor HEM-7080IT-E
cd ~/opt/omron-build/bin$
sudo omron_790IT_test
Continuing as root the result is:
# export OMRON_DEV=/dev/bus/usb/001/003
root@:~# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 003: ID 0590:0028 Omron Corp. HJ-720IT Pedometer / Blood Pressure Monitor HEM-7080IT-E
root@:~# ls
root@:~# cd /home/USERUSER/
git/ opt/ .python/ src/ .vim/
root@whm:~# cd /home/USERUSER/opt/omron
omron/ omron-build/
root@whm:~# cd /home/USERUSER/opt/omron-build/bin/
root@whm:/home/USERUSER/opt/omron-build/bin# ls
omron_720IT_test omron_790IT_test
root@whm:/home/USERUSER/opt/omron-build/bin# ./omron_790IT_test
Found 1 omron 790ITs
Opened omron 790IT
xomron_get_command_return: read_result_result -7 < zero
Device serial: ??sq?
omron_get_command_return: read_result_result -7 < zero
Device version:
omron_get_command_return: read_result_result -7 < zero
AJR data count: 117
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
what can I do do deliver more diagnostics?
Just notice this might be the same as #12
Time to get this fixed :) will start reading code.
All help / hints are welcome.
Left the code running for a while and noticed some sort of screensaver ??? a o rotating over the screen...
# ./omron_790IT_test
Found 1 omron 790ITs
Opened omron 790IT
omron_get_command_return: read_result_result -7 < zero
Device serial: ??k?
omron_get_command_return: read_result_result -7 < zero
Device version:
omron_get_command_return: read_result_result -7 < zero
AJR data count: 111
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
omron_get_command_return: read_result_result -7 < zero
nothing new there.
Will start installing X and will install wireshark as well. Not sure if github can handle pcap files but as we mailed today already I'm sure I'll get the files to you :)
apt-get install xfce4 xorg wireshark
modprobe usbmon
..... LOL .....
wireshark running this happens:
root@:/home/USERUSER/opt/omron-build/bin# modprobe usbmon
root@:/home/USERUSER/opt/omron-build/bin# ./omron_790IT_test
Found 1 omron 790ITs
Opened omron 790IT
Device serial: M7080IT 207J
Device version: 0310100000J
AJR data count: 2
01/01/2028 01:26:57 SYS: 123 DIA: 65 PULSE: 71
01/01/2028 02:02:13 SYS: 133 DIA: 67 PULSE: 61
Weekly info:
Evening[0 26/12/2027] = sys:123 dia:65 pulse:71.
root@:/home/USERUSER/opt/omron-build/bin#
yes I know time isn't yet set correctly
When the M10 was in 'error' mode because I was typing while measuring also the readout when wrong:
but picked up without intervention.
# ./omron_790IT_test
Found 1 omron 790ITs
Opened omron 790IT
^[omron_get_command_return: read_result_result -7 < zero
Device serial: ???q?
omron_get_command_return: read_result_result -7 < zero
Device version:
AJR data count: 12
01/01/2028 01:26:57 SYS: 123 DIA: 65 PULSE: 71
01/01/2028 02:02:13 SYS: 133 DIA: 67 PULSE: 61
01/01/2028 21:37:49 SYS: 154 DIA: 76 PULSE: 91
01/01/2028 21:38:31 SYS: 135 DIA: 74 PULSE: 65
01/01/2028 21:39:18 SYS: 132 DIA: 81 PULSE: 63
01/01/2028 21:44:59 SYS: 119 DIA: 72 PULSE: 67
01/01/2028 21:47:15 SYS: 124 DIA: 74 PULSE: 71
01/01/2028 21:49:27 SYS: 107 DIA: 61 PULSE: 71
01/01/2028 21:50:48 SYS: 77 DIA: 44 PULSE: 77
01/01/2028 21:52:20 SYS: 111 DIA: 76 PULSE: 73
01/01/2028 21:53:19 SYS: 112 DIA: 80 PULSE: 74
01/01/2028 22:02:12 SYS: 153 DIA: 136 PULSE: 65
Weekly info:
Evening[0 26/12/2027] = sys:124 dia:81 pulse:71.
edit: later it still gives problems, however it seems
rerunning
insmod usbmon
solves the issue. Might it have something to do with an initialization?