Those pressure readings do not look like my earlier model Bamboo at all. I get a pretty linear changes of between 0-160. Its pretty hard to get readings much above that.
All the logs emailed so far for newer Bamboo's like to use values of 24, 88, 8, and sometimes various values between 60-80. Nothing indicating a linear report of pressure as you initially touch and then press harder is showing up in logs. So at best, you guys are getting a boolean touching/not touching and the not touching part isn't working perfect. Hmmm, wonder why they changed the packet format? Chris On Sun, May 1, 2011 at 12:39 PM, Catalin Balan <laserbeam...@gmail.com> wrote: > I've had another round with evtest just to see what happens in real > time. Also please note that I do not know how the driver works and I > am using what Chris said to give you some more detailed data (If I > can). > > Those 0s happen when I lift my finger. This explains why when I press > the second finger while the first one is on the tablet it does not > jump. The only reason I find makes sense why it jumps when I press > down the finger, is that it remembers it's last 0, because the > coordinates seem normal when I press my finger down (at least so I > hope, I am looking at X and Y). In relative mod > > Since pressure seems to be the problem, I ran another test here: > pressureLight.txt contains the output of evtest when I pressed softly > close to the top left corner of the tablet. > pressureHard.txt contains the output of evtest when I pressed way > harder close to the same area of the tablet. > > Both files contain 2 different test runs (appended) with 1 finger press each. > > I did this test because I thought there wasn't pressure support for > touch, and as far as I can see... there are no major differences > between the 2 files. Also note that I tried to vary my pressure > hugely... I barely touched the tablet for pressureLight tests, while > the tablet bent slightly during pressureHard tests. > > I have also tried doing: > xsetwacom set "Wacom BambooPT 2FG 4x5 Finger touch" Threshold 2047 > (which I think is the maximum value), and the cursor still moves at > the slightest presses. No change with 27, 87, 89, 400, 500 and 1000 > either (random numbers of course). > > One last thing about the tests. For some reason X didn't get reported > in some of them. I did short presses (a bit longer than taps), but > shouldn't X appear in all of them?? > > Hope this helps. > > On Sun, May 1, 2011 at 17:35, Chris Bagwell <ch...@cnpbagwell.com> wrote: >> Hi all, >> >> Thanks for sending in data so fast. It is helpful. At least it >> pinpoints to kernel side issue. So the evtest output is easier to >> talk to. >> >> I see in all the samples sent in (both xorg.0.log and evtest), that we >> sometimes get a packet with X/Y coordinates at [0,0] at times that >> pressure is non-zero. >> >> Event: time 1304228221.687840, -------------- Report Sync ------------ >> Event: time 1304228221.711826, type 3 (Absolute), code 58 (?), value 64 >> Event: time 1304228221.711832, type 3 (Absolute), code 53 (?), value 0 >> Event: time 1304228221.711832, type 3 (Absolute), code 54 (?), value 0 >> Event: time 1304228221.711836, type 3 (Absolute), code 0 (X), value 0 >> Event: time 1304228221.711836, type 3 (Absolute), code 1 (Y), value 0 >> Event: time 1304228221.711837, type 3 (Absolute), code 24 (Pressure), value >> 64 >> >> That will cause your jumps big time. Those "(?)" are multi-touch >> versions of X/Y/Pressure. I guess your repo has older evtest that >> doesn't know those names yet; but thats ok. >> >> Also, I notice in everyone's evtest and Xorg.0.log files, that the >> pressure seems to be reporting oddly in general. I see what look >> like magic values of 24 and 88 being sent alot. Probably, Wacom >> didn't want to increase the packet length on these newer Bamboo's and >> needed to encode the 4 (or more?) fingers by sending multiple packets >> with something in pressure to tell which finger report it is. >> >> We will need someone that doesn't mind hacking on kernel drivers to >> figure this out. I'm not sure I can do much more without access to >> hardware. >> >> I know Ping is not available for a while. Perhaps Jason can find some >> info on any possible packet format changes? >> >> Barring that, we'll just need to reverse engineer the packet data ourselves. >> >> Chris >> > > > -- > Cătălin Bălan > http://thescrambledbit.wordpress.com > I do know everything, just not all at once. It's a virtual memory problem. > ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
