506 replies to this topic

[Ferret-Simpson]

Psygoo - It's a serial WACOM driver. SERIAL.

WACOM still produce MAC OS X drivers for their Wacom tablets, go on www.wacom.com and download the thing.

Scott - Just finishing a download, will test it in about half an hour.

Works perfectly! Now, about that multitablet support. . . .

[psygoo]

Ferret-Simpson, on Mar 9 2007, 01:05 PM, said:

Psygoo - It's a serial WACOM driver. SERIAL.

WACOM still produce MAC OS X drivers for their Wacom tablets, go on www.wacom.com and download the thing.

Scott - Just finishing a download, will test it in about half an hour.

Works perfectly! Now, about that multitablet support. . . .

I know that, but Wacom dont have OSX
driver for Volito 1&2 and PenPartner 1&2

I just wish to have Absolute motion on my pen...

[Ferret-Simpson]

If they're USB, you'll probably have to live with it. The TabletMagic program only supports serial protocols.

[Scott Lahteine]

Quote

If they're USB, you'll probably have to live with it. The TabletMagic program only supports serial protocols.

It is unfortunate that Wacom doesn't even support some of their older USB tablets. Someone may eventually create a Mac driver for these discontinued models, but it won't be me. USB drivers are quite different from a driver like TabletMagic due to their dependence on Apple's HID framework. As I understand it, the part of an HID driver that Mac OS X hooks into has to be written as a kernel extension. Alas, even if I started on such a project, it would be at least a year before I had anything publishable - especially given my obligations to other projects.

[Scott Lahteine]

Ferret-Simpson, on Mar 6 2007, 07:02 PM, said:

After sending the first "*/r" on 19200 baud the system freezes. It's not the system's hardware, it just had a new motherboard and Khashoggi's daemon manages fine...

Hi Ferret-Simpson...

I wonder if you would do me a favor and try starting the TabletKhashDaemon (kkTabletDaemon?) in Terminal and tell me what it prints. This will tell me whether or not Kashoggi's custom-build is attempting to send "*" to the tablet or not, and give me some guidance as to whether I should continue to pursue the idea that some tablets don't like to be queried.

Also, did you try the TabletPC custom-build of TabletMagic that I posted a few days ago? It doesn't send any kind of query to the tablet, so if that's what's causing your system to kernel-panic, this one should hold up.

I'm going to post a new version soon that includes an extra set of controls (in the Extras pane) only on Hackintosh systems. These controls can be used to turn off tablet-querying and to set custom tablet scale values for experimentation. These scale values are saved to preferences and will be applied when a TabletPC digitizer is detected.

[Scott Lahteine]

Posted another new build, TabletMagic 2.0b8rc6 with the following changes:

• Added a "Don't Query" checkbox and Scale Override edit-fields to the Extras tab
  
• Added support for system buttons 3, 4, and 5
  
• Added a -F argument to the daemon which "Forces" TabletPC at 19200
  
• The daemon now adjusts to resolution changes

For those who experienced kernel panicking, I suggest you go to the Extras tab and make sure "Don't Query" is checked before starting the daemon. This adds the "-F" parameter to the daemon's startup parameters, and this will persist when the daemon is started automatically at boot time.

This version doesn't do logging.

Paringas, you mentioned you were seeing no tilt data. So far I have no information about tilt support in TabletPCs, so I haven't included any support for it. A log file showing a range of tilt values would be very helpful. If you still have the -tpc build of rc5, that version does produce a log file.

I included two text fields in the Extras tab where you can enter custom values to override the tablet scale values. Hopefully you can find some values that work with your TC4200. However, without knowing more about how to query a tablet for its internal scale it's not possible for TabletMagic to determine the correct values automatically.

Enjoy!

Edited by Scott Lahteine, 11 March 2007 - 07:20 AM.

[Ferret-Simpson]

As I said, the "Silent" build works perfectly. RC5 I think?

Screen Bounds: (0, 0) - (1023, 767)

[PORT] serial0
Error opening serial port /dev/cu.serial0 - Resource busy(16).
Can't open serial port "/dev/cu.serial0".

[PORT] Bluetooth-PDA-Sync
[SENT] "0\r"
[SENT] "*\r"
[ERR ] Timed Out!

Could not initialize tablet.

Fatal Error: No Wacom Tablet Found!

Excuse the use of Bluetooth, the Tablet itself is busy. Those are the first sent commands.

[paringas]

feedback:
1. works only if i tick "don't query"
2. middle click works - thank you very much
3. less lagging in the testing pane.
4. all the mapping/calibration issues are the same.

must haves:
1. addition of the calibration function ala windows/windows mobile
2. managing the interface so the mapping function is only related to multi-monitor setups/mouse mode.
3. pressure "sensitivity"/scaling setting.
4. "press and hold" functionality ala windows/windows mobile with the inclusion of the side switch.

optionals:
1. mouse mode

once all of these are in (including all the compatibility issues) - it's a done job.

ps. starting to doubt the tilt as it might require a special pen.

Edited by paringas, 11 March 2007 - 01:52 PM.

[Ferret-Simpson]

No, not a special pen, a special tablet. The digitiser itself has no tilt support. Hence why you can't use a tilt pen on say. . . an Ultrapad. (Lucky, I can use my TabletPC pens on my UD 8))

[Scott Lahteine]

Ferret-Simpson, on Mar 11 2007, 12:53 PM, said:

[PORT] serial0
Error opening serial port /dev/cu.serial0 - Resource busy(16).
Can't open serial port "/dev/cu.serial0".

The rc6 build should do everything just the same as the "silent build" rc5-tpc. But it looks like something already has the serial port in this attempt... maybe you're already running another daemon, and maybe it's suspended? If you give it another shot it ought to be able to open and connect. If the serial port still won't open I can try messing with the serial initialization code. I hope I can fix your kernel panic issue, that just shouldn't happen at all.

[bubba129]

alright first off please dont yell at me.  I decided to try this program out I tried TabletMagic 2.0b8rc6  just on the off chance it would work... and to my amazment it recognized something.  when I enable Tabletmagic it says Tablet: ISD V4.0 (TabletPC) now I am surprized by this because I have a gateway CX2724 wich uses a Finepoint digitizer.  Now I cant do anything with it and I would really like to see it work so is there anyone that can help.

[Ferret-Simpson]

Scott, you're not reading my posts properly!

RC5 WORKS!!!!!!!!!

I know the serial port says it's busy, TabletMagic is using it. But it sends the same commands to bluetooth as it does to the internal serial.

[paringas]

bubba129,

go to mapping tab and press "more" a few times for the left square so the selected area's all covered.
then play with the setting for the right rectangle to marginally correct the calibration.
have a read through inkwell's help.
everything should work.

[bubba129]

paringas, on Mar 13 2007, 01:45 AM, said:

bubba129,

go to mapping tab and press "more" a few times for the left square so the selected area's all covered.
then play with the setting for the right rectangle to marginally correct the calibration.
have a read through inkwell's help.
everything should work.

Thanks for responding to my post, now I did as you said and I pressed the more button under mapping but still nothing when I use my pen it doesnt do anything.  and as for the tip to look at the inkwell help is there something specific I should look for.  Sorry I am a noob with this tablet stuff.

EDIT: OK something strange if I unplug my bluetooth dongle it doesnt find any tablet

Edited by bubba129, 13 March 2007 - 02:15 AM.

[Scott Lahteine]

Ferret-Simpson, on Mar 12 2007, 10:56 PM, said:

Scott, you're not reading my posts properly!
RC5 WORKS!!!!!!!!!

Actually I did know that rc5-tpc worked for you, but rc5-tpc is just a hack. It only works because it assumes there's a TabletPC digitizer on the first serial port and never sends any queries. (It also writes a log file continuously, which slows the driver and fills your hard drive.) Knowing that rc5 worked only confirms that it's the serial write() or the serial flush() that is causing your kernel panic.

My test versions are leading somewhere, so please be patient. I need to test each step in the initialization process until I know what's causing your kernel panic and paringas's bad mapping. I won't consider the driver worthy until it can definitively identify any digitizer or tablet and obtain the proper tablet scale values. We still have a long way to go to reach that point.

Quote

I know the serial port says it's busy, TabletMagic is using it. But it sends the same commands to bluetooth as it does to the internal serial.

Sorry, it wasn't clear to me whether you were posting the output from the Kashi daemon or rc6 in your earlier post, or what you were trying to point out. And it wasn't clear to me that "it sends the same commands to bluetooth..." referred to the Kashi daemon. It took some effort, but now I see what you were saying.

bubba129, on Mar 12 2007, 10:28 PM, said:

I decided to try this program out I tried TabletMagic 2.0b8rc6  just on the off chance it would work... and to my amazment it recognized something.

If you're using rc6 - which is a test version only - you need to go to the "Extras" tab in the preferences and uncheck "Don't Query." When this checkbox is enabled the driver simply assumes there's a digitizer on the first serial port it finds. So you have to disable that option to get a meaningful result.

Now, from what you say about your bluetooth dongle it sounds like your system may not be recognizing the digitizer's serial port. Did you hack the Apple16x50ACPI.kext file as described in this post by paringas? That hack is required to get the built-in digitizer to show up in Mac OS X as a POSIX serial port.

Edited by Scott Lahteine, 13 March 2007 - 08:13 AM.

[bubba129]

Scott Lahteine, on Mar 13 2007, 08:08 AM, said:

Actually I did know that rc5-tpc worked for you, but rc5-tpc is just a hack. It only works because it assumes there's a TabletPC digitizer on the first serial port and never sends any queries. (It also writes a log file continuously, which slows the driver and fills your hard drive.) Knowing that rc5 worked only confirms that it's the serial write() or the serial flush() that is causing your kernel panic.

My test versions are leading somewhere, so please be patient. I need to test each step in the initialization process until I know what's causing your kernel panic and paringas's bad mapping. I won't consider the driver worthy until it can definitively identify any digitizer or tablet and obtain the proper tablet scale values. We still have a long way to go to reach that point.
Sorry, it wasn't clear to me whether you were posting the output from the Kashi daemon or rc6 in your earlier post, or what you were trying to point out. And it wasn't clear to me that "it sends the same commands to bluetooth..." referred to the Kashi daemon. It took some effort, but now I see what you were saying.
If you're using rc6 - which is a test version only - you need to go to the "Extras" tab in the preferences and uncheck "Don't Query." When this checkbox is enabled the driver simply assumes there's a digitizer on the first serial port it finds. So you have to disable that option to get a meaningful result.

Now, from what you say about your bluetooth dongle it sounds like your system may not be recognizing the digitizer's serial port. Did you hack the Apple16x50ACPI.kext file as described in this post by paringas? That hack is required to get the built-in digitizer to show up in Mac OS X as a POSIX serial port.

Thanks for your help.  Unfortunatley I do not have windows installed and do not see how I can get the 7/8 character name in device manager without it.  So I guess when I get home tonight I will install windows.  So with that which version should I install I have XP and Vista?

[Scott Lahteine]

bubba129, on Mar 13 2007, 12:28 PM, said:

So with that which version should I install I have XP and Vista?

XP will suffice.

It will be interesting to see whether you can get this to work, and whether the Finepoint tablet uses the same communication protocol. I've heard one report of success on a Gateway M275, but this hasn't been independently confirmed.

[bobo2211]

does not work with my tc4400, don't know why

[paringas]

bobo2211 and all others who's tablets don't work after fixing the required kext:

1. go to Extras tab and click "kill daemon" there so that the status says "Daemon not running"
2. tick "Don't query" in Extras tab and try starting daemon again.
3. go into Testing tab and see if the numbers are alive as you move your pen around the screen.
4. if they are alive but your mouse pointer isn't matching with the tip of the pen, follow instructions i suggested to bubba129 six posts up.

good luck.

a shame that this forum doesn't like the idea of having the first post always displayed on every page of the thread with all the updated info on links/features/instructions/etc...

Edited by paringas, 14 March 2007 - 02:23 AM.

[bubba129]

Alright well I am sorry to say that I cannot get my finepoint to work.  I reinstalled Windows XP got the 7 characters that I needed (FPI2004) entered it into the file, added a tool into startup items and now I see serial 0 in tabletmagic but nothing is found.  I just want to say thanks and keep up the good work I will keep my eye on this thread and test new releases.