m210 info dosen't work

Bug #1017705 reported by petRUShka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
m210
Medium
a

Bug Description

info command doesn't work. But dump and convert work perfect.

% m210 info
m210: failed to get information: response waiting timeouted
error: info failed

The pen is Ritmix DP-205BT.

% lsusb | grep Peg
Bus 003 Device 003: ID 0e20:0101 Pegasus Technologies Ltd. NoteTaker

P.S. By the way I added ArchLinux package for AUR for your m210 package: http://aur.archlinux.org/packages.php?ID=60332

Revision history for this message
a (tuomasjjrasanen) wrote :

Hi and thanks for reporting this.

Is `m210 info?` failing constantly or just sometimes?

It should not be a device incompatibility problem, since the error message indicates that the device is not sending any report when queried for general information..

Changed in m210:
importance: Undecided → Medium
milestone: none → 0.9
assignee: nobody → Tuomas Jorma Juhani Räsänen (tuomasjjrasanen)
status: New → Incomplete
Revision history for this message
Gunther Schulz (gunther-schulz) wrote :

Hi

had the same issue on a SilverCrest DGP 1000-R

Dump and convert did work though.
After some debugging found the solution - changing the 3 byte from 0x28 to 0x42, here the patch:

diff -uNr ./src/libm210/dev.c ../m210-0.8_mod/src/libm210/dev.c
--- ./src/libm210/dev.c 2013-10-22 23:26:38.621657363 +0200
+++ ../m210-0.8_mod/src/libm210/dev.c 2013-10-22 23:25:07.605653755 +0200
@@ -464,7 +464,7 @@
   /* Check that the response is correct. */
   if (response[0] == 0x80
       && response[1] == 0xa9
- && response[2] == 0x28
+ && response[2] == 0x42
       && response[9] == 0x0e) {
    break;
   }

Revision history for this message
a (tuomasjjrasanen) wrote :

Thanks Gunther! I'll add that to model-specific quirks.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers