February 20, 2019, 11:33:54 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: You may have to login twice the first time,  but we don't know why - Erm I mean it's a security thing yeah that's it - security.
  Home Help Search Login Register  
  Show Posts
Pages: 1 2 [3] 4 5 ... 173
31  Screen Tablet malarky / Tablet Conversion to USB / Re: Waxbee on Windows 10 on: May 10, 2016, 03:51:38 AM
The precision of the tablet has a limit and the software should handle this somehow. A single stroke is composed of points but physically, it is a "solid line" (curved). If the software does not handle recreating the original curve that means you can reproduce the same problem with any top tablet, just use a higher resolution image! 

In other words, the precision of the tablet is compensating for the software not doing its "job" really. I see you tried even with LazyNezumi which should have helped.

Long Shot:  What if LazyNemuzi can only stay within the emulated tablet's resolution?  What if we picked the highest resolution tablet (when emulating) to give LazyNezumi more "precision" when interpolating values to return to the system?
32  Screen Tablet malarky / Tablet Conversion to USB / Re: How to "install" WaxBee converter on Arduino Pro Micro, clones or any ATmega32U4 on: May 09, 2016, 08:29:27 AM
Okay, I have a new version of WaxBee (0.16) that uses "build variants" to reduce the size of the .hex file. In other words, I compiled like 8 versions with various features turned ON and OFF. (like you'll can't interface an ADB board and a serial board at the same time), or you'll never going to see any of the "Debug" messages when the console is disabled. That sort of thing. So the WaxBeeConfig automatically "picks" the right one depending on the selected feature. I could tweak this more, but most of the typical scenario should fit under 28K (i.e. using the AVR stock 4K bootloader).

I ordered a couple of Pro Micro "clones" to test them out. They were more like 4$+0.50 shipping, but still the cheapest board for this CPU. I ordered 2 because I am always affraid I get a broken one. The Teensy 2.0 is now at 16$US + shipping. I was looking to see if we could use the Teensy LC (very powerful CPU at 11.65$+shipping) but it is not 5v tolerant and would thus only work for the ISDV4 case -- given it is a completely different architecture, this will take me more than a weekend for sure.

I am happy with my WaxBee release - hopefully I did not introduce any regressions.  Tongue

33  Screen Tablet malarky / Tablet Conversion to USB / Re: Waxbee on Windows 10 on: May 09, 2016, 08:06:04 AM
This pen looks OK. Probably you simply need to "tune" it.  There are tiny potentiometers behind the button.  Be extremely careful with removing the plastic -- I broke a few of those.  There are posts that tells how to dismantle it. (just hard to search).
34  Screen Tablet malarky / Tablet Conversion to USB / Re: Announcement : ADB Intuos converter v0.1-beta on: May 08, 2016, 05:21:33 PM
In the HID spec a tablet is named "Digitizer". Yes, the spec probably support most if not all features (absolute position, pressure and I can even see X/Y Tilt). You can check it out here:

Now does it work in practice is another question. Grin

EDIT: I think it supports the Wacom-style orientation too (named "twist") -- Some wacom report the "hovering distance" of the pen from the board which I am not sure how to report that (like for doing airbrushing?)
35  Screen Tablet malarky / Tablet Conversion to USB / Re: Waxbee on Windows 10 on: May 08, 2016, 01:39:16 AM
Just saw from another post in this forum that they got the Intuos2 working on Windows 10 !   The driver they use has some glitches but appear to work for the most part.
36  Screen Tablet malarky / Heyaaaalpppp / Re: Interfacing a TabletPC digitizer on: May 07, 2016, 11:21:42 PM
The GND signal is what I am talking about.  We say "grounding" but it is not in the shield-protection sense but rather talking about "signals". Just connect it to the GND wire/pin/whatever is in the same "connection" (not sure how your setup looks like).

Make sure you do not mix up which signal is which (can get quite confusing) -- and labels can be written in "reverse" sometimes (Wacom often reversed the silk markings in some serial boards - not talking ISDV4 boards here, but the *-R models).  That is why I always talked about the serial driver chip pinout and never the silk markings next to the internal connector (when there was one).
37  Screen Tablet malarky / Heyaaaalpppp / Re: Interfacing a TabletPC digitizer on: May 07, 2016, 07:14:09 PM
About the power:  For an ISDV4 -- you probably won't need 500mA of power -- the board will pull something under 100mA (like 80mA) -- I say probably because I never measured yours of course. Only a couple others I had around here.  I mean, the old and huge 12x18 inches UD and Intuos2 serial board with leds et al do not really exceed 100mA either!

Your SOT-223 is going to work and is probably a better part anyway.

Now the tricky part: why it suddendly decides to stop... ISDV4 are much simpler to deal with -- they have nearly zero configuration and uses a steady serial port speed (the UD/Intuos2 boards starts at 9600 baud then you tell them to go to a faster speed -- if you screw up something and gets desynchronized, you won't talk to the same speed and hence "loose connection" until you reset).

Now I will just dump what I saw from experience, I have no idea if it applies to you.
Not a big change but MAYBE you are running into a RTS and possible DTR handshake problem thingy -- especially if those pins are not connected (these are inputs) -- that would mean they are "floating" -- floating means that it can go high or low depending on...  mood.  Grin   Well maybe after 30 seconds the "mood" changes? lol.  Make sure those are grounded -- Here I mean on the side of the tablet.  Can you take a picture of your device connector and point what is what -- I do not even recall if those HAVE RTS and/or DTR to start with !!  Note that these are the handshake pins going towards the tablet that will "halt" the bytes going out if high. There are other handshake pins (DSR/CTS) going the other direction (outputs) (which we don't care, they should be left unconnected -- as we do not really need to be "handshaked" -- well, potentially yes if this is hooked to the PC directly, but at these low speeds, I am sure your Linux system will handle/buffer everything without loosing anything, and if it ever does loose a byte it will resync on the next packet anyway!).

38  Screen Tablet malarky / Tablet Conversion to USB / Re: GD-1218-R windows 10 issues on: May 07, 2016, 06:31:11 PM
Wow! great news!  I keep thinking Intuos2 does not work on Win10 - but even if not perfect, it is actually much better than nothing!

In case someone is searching the driver, I got this link from the japanese Wacom site:
39  Screen Tablet malarky / Tablet Conversion to USB / Re: Converting Wacom UD-1212-R from Serial to USB on: May 07, 2016, 06:19:25 PM
UD-1212-R is a nice tablet.

Is there a specific name for the "mac-compatible" mini-DIN connector?  You said most of them are of the "wrong type".   I'm asking in case someone else wants to search for this part. You mentioned aliexpress, can you get a little more specific? How can one distinguish one over the other when search for one?
40  Screen Tablet malarky / Tablet Conversion to USB / Re: Waxbee on Windows 10 on: May 07, 2016, 05:58:49 AM
Aspect Ratio

Typically your tablet is "mapped" to your screen. Well, surprise, surprise, your screen also has an aspect ratio! (16:9 for FullHD screens for instance).  The Intuos 5 S is 16:10.  Your UD-1218-R tablet is 3:2 -- matches photography but not screens and newer Wacom boards. (which tend to be 16:10 or 16:9 like screens nowadays). Matched ratios is a very common issue and the Wacom driver has a setting to "correct it" automagically.  Well... there is no magic: it will render *inactive* a portion of the tablet to "fit" (exactly the same for fitting an image to your desktop screen). But it will do so thinking your physical tablet is an Intuos 5 S -- not a UD-1218-R!  So although the setting in the Wacom driver is a good thing, it is not enough. We should "match" the Intuos 5 S using a similar mechanism:  cut out another portion of the tablet on top!

Aspect Ratio in WaxBee

We saw that the X has more resolution, so we will use that as the base and "reduce" the number of Y lines to match. That means the we will cut at the top and at the bottom.

To fit 18x12 in 16:10 ratio (i.e. 31496/19685 ratio):

18 / 31496*19685= 11.25 inches -- loosing 0.75in in total (or 0.375 inches at the top and bottom).

To achieve this we need to map the emulated Y coordinates to a smaller portion of the UD-1218-R vertical position.(this can be done by modifying your template).

On the UD-1218-R we have a total of 30480 lines -- if we remove 0.75 inches worth of lines or 30480 / 12 * 0.75 = 1905 (952 at the top and 953 at the bottom), in other words, instead of mapping the full 0 to 19685 range -- we map from 952 to 18732 -- effectively "cropping" our active area.

In summary your virtual tablet (that 100% matches the Intuos 5 S ratio) now is:

18 x 11.25 inches active area @ 1749.8 lpi -- ( 31496 x 17780 lines )

Aspect Ratio in Wacom driver

If your screen is a 16:10 -- (like 2304 x 1440 pixels for example) the story ends here -- your screen ratio perfectly matches the Intuos 5 S ratio.

If your screen is a 16:9 (most popular these days), then using the Wacom settings to "fix" the ratio will do more "damage". Here we have nothing to do, but we can compute what is going to happen. (in yet another post).  

In the meantime here's a picture of the ratio cutting that will happen.  The red part is what we will fix within the WaxBee configuration to "match" the Intuos 5 S, and the blue part is what the Wacom will do on top of it (if your screen is 16:9).

41  Screen Tablet malarky / Tablet Conversion to USB / Re: Waxbee on Windows 10 on: May 07, 2016, 04:16:48 AM
Even with the high resolution per inch of the Intuos5 S, (actually it is "double" your tablet) the big difference in size of your board beats the total number of lines. In other words you will not have the maximum resolution your board can deliver (until we come up with a bigger emulation which would instantly make it better). But not to worry, it will still appear to work correctly -- actually, I believe you will not notice it. Let me demonstrate this with some numbers:

Let's do some math anyway to see what we are talking about here:

UD-1218-R| 12 in| 18 in| 2540| 45720| 30480
Intuos 5 S| 8.8 in| 5.5 in| 5080| 31496| 19685

So if we take the number of X lines of the Intuos 5 S and divide it by the active area size (X) of the UD-1218-R, that should give us the resulting LPI on the X axis: (also we do this on the Y axis)

X: 31496 lines / 18 in = ~1750 lpi
Y: 19685 lines / 12 in = ~1640 lpi

So you will 'loose' ~31% (x axis) and ~35% (Y axis) of your original resolution of 2540 lpi. (~1750 lpi and ~1640 lpi respectively)

Still pretty good afterall
lpi stands for "Lines Per Inch" -- similar to DPI -- Dot Per Inch for a printer. Well the laser printer next to me can't go over 1200 dpi and I typically only print at 600 dpi. I mean, we are talking splitting a single inch into more than a *thousand*. We are talking drawing with a hand, not with a printer!  I do not know why Wacom go insane by bragging all this super-high-definition, I see not much point frankly.

Aspect Ratio

The other issue is the aspect ratio difference. Although it is "close" there is like ~110 lpi difference between the X and the y. That means the "dots" will not be "square". Again it might work and you might never notice it (this one probably more noticeable: drawing a circle would look a little bit squashed). Again, this is fixable but probably at the cost of dropping active area on the side - at least in one axis (or maybe two depending on the WaxBee setup AND settings in the Wacom driver).

Next post will do the math for rectifying the aspect ratio to perfect 1:1 square pixels.
42  Screen Tablet malarky / Tablet Conversion to USB / Re: Waxbee on Windows 10 on: May 07, 2016, 03:36:36 AM
Horray ben!  Now just missing are pictures of your setup.  You have a Wacom UD-1218-R board?  That's a beast and is a great board. It once was a "dream" board.  Grin

If you got as far as flashing a CPU and trying other HID stuff, you are F-A-R from a novice sir. Sorry to say. A novice won't know that "HID" is not a verb in past tense about being concealed written in uppercase.

First some mechanical questions:

1- In case you thought about it, how do you see your Leostick fit in the picture? I see the stick has a "Male" type USB connector, that means it can plug directly into a computer. That might also mean that you might not put it inside the Wacom board.  
2- Are you ok with opening the Wacom and do some soldering (or maybe you already did all that?) -- (sorry if I missed earlier posts).
3- Did you want to re-use that Leostick for other purposes?  (being able to re-install it)?
4- Not sure if you knew but you can use the USB 5V to power your board (through the leostick) and thus let go of the bulky UD-1218-R power supply brick. Now THAT is awesome -- Welcome to the new millenium my *little* board! For that to work you *need* to solder.  
5- if you do not want to open the Wacom board and perform surgery, you will need to get more parts (connectors) -- which will cost more obviously

Second how do you flash this and which .hex was it?  

Did you mention you flashed WaxBee with the Intuos2 UD1218 template? I saw that the leostick bootloader takes 2K (which leaves 30K for WaxBee+template) -- which is great news. In comparison, the stock AVR bootloader takes 4K and the Teensy one takes 0.5K (which makes it more awesome but also why so many people are having issues setting up WaxBee in non-Teensy boards). Did you use a "stock" WaxBee .hex file or it was a custom build (maybe from someone else) to make it "smaller" (there are ways to make it smaller by removing the unused emulation pieces for instance -- but it is rather annoying to do since you need to setup the whole avr-toolchain compiler since this was not done using Arduino. (Arduino is very popular and easy to setup but it is also sadly one of the worst tool for programmers that do this for a living).

Third the emulation for Windows 10

Probably the way to go here is to emulate the Intuos5.  The emulation is a bit rough but the basics works. I am just worried that the Intuos5 device we currently emulate succesfully is a small board I believe.  It will "work". We should do the math if we will loose resolution.  The newer devices have much more precision, so we might get lucky.
43  Screen Tablet malarky / Heyaaaalpppp / Re: Back to business, Tablet PC digitizer to Teensy issues on: May 06, 2016, 03:05:47 PM
What is your tablet model exactly? What template have you picked?  You said you run Windows 8.1 -- some Wacom drivers for Intuos2 does not always work there -- have you installed the correct Wacom drivers?  Have you tried the Intuos5 emulation?  (there might not be a ready-made template for your tablet, but I can help with that).
44  Screen Tablet malarky / Heyaaaalpppp / Re: [SOLVED] Hardware and firmware question on: May 06, 2016, 03:02:03 PM
Seems like a lot of people is hitting that 4K bootloader issue. I should really get into building a solution to fit 28K instead of 31.5K...

Good that you solved your issue. Sorry for all the inconvience! Hope you are enjoying your tablet!
45  Screen Tablet malarky / Heyaaaalpppp / Re: Interfacing a TabletPC digitizer on: May 06, 2016, 02:57:08 PM
Hello Pesho et al, maybe I can be of any help?  I've done ISDV4 conversion before  Grin

The only (typical) difference between a "real" teensy and clones is just the bootloader code. I assume the clone has a similar external crystal like the teensy?  If not then that could be one reason. But if the CPU model is the same, then it is the same. There are no "AVR clones" (AFAIK).

Can you take close up photos of your setup?

Why do you need 500mA? Maybe that is your issue?  Like it starts doing things and the tablet (or whatever you are powering?) suddendly eats lots of current, voltage drops and something browns-out? (i.e. Brown-out is a state that makes chips go bezerk - typically happens when the voltage gets out of range -- a well know technique to "break" through security features...).

Yes, Linux drivers still work fine with serial tablets! No real need for USB emulation on Linux. This is mostly for Windows (and Mac OSX).
Pages: 1 2 [3] 4 5 ... 173
Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!