text:
Are you in the United States?
Visit our U.S.A. & International site for relevant pricing, distribution and product availability information.Go to StarTech.com
USB 3.1 (10Gbps) Single-Bay Dock for 2.5"/3.5" SATA SSD/HDD
Dock your 2.5" or 3.5" SATA drive over high performance USB 3.1 with UASP
Product ID: SDOCKU313
- Access data from one 2.5 or 3.5" SATA SDD/HDD over ultra-fast USB 3.1 Gen 2
- Access drives at full speed with support of SATA I, II and III (up to 6 Gbps)
- Top-loading design with built-in ejection button for easy drive access
- UASP support for enhanced performance
- Supports large drive capacity of up to 6TB
- Multi-function LED indicators
- Backward compatible with USB 3.0, 2.0 and 1.x
Unleash the power of USB 3.1 Gen 2 (10 Gbps) with this single-drive docking station. It supports both 2.5" and 3.5" form factors for solid-state and hard drives, with a high drive capacity of 6TB.
Harness the speed of USB 3.1 Gen 2
USB 3.1 Gen 2 gives you greater bandwidth and speed with file transfer rates of up to 10 Gbps - twice the speed of USB 3.0 (USB 3.1 Gen 1) technology. It lets you leverage the high performance of the latest SSDs and hard drives, while alleviating bottlenecks in your data transfers.
Top-loading design for easy drive access
It's never been easier to dock and swap drives from your desktop computer or laptop. Simply insert your drives into the top loading slot, with no tools or trays required. The HDD ejection button allows fast and simple drive removal.
Convenient compatibility
The docking station comes with a USB Type-A to B cable, providing backward compatibility with your existing USB 3.0, 2.0 and 1.x devices. It also supports UASP for enhanced performance.
The SDOCKU313 is backed by a StarTech.com 2-year warranty and free lifetime technical support.
- Perfect for system builders and IT professionals who need quick access to drives for imaging
- Back up data quickly to an external drive for archiving
- Transfer data from one hard drive to another
- Easily take backup data to an offsite location for safekeeping
Product Numbers
Ingram Mexico
UPC Code
Technical Specifications
|Warranty Information
|2 Years
|Bus Type
|USB 3.1 Gen 2
|Chipset ID
|ASMedia - ASM1351
|Compatible Drive Types
|Drive Installation
|Drive Size
|2.5in & 3.5in
|USB 3.1 Gen 2
|Number of 2.5 inch bays
|Number of Drives
|4Kn Support
|Max Drive Capacity
|Currently tested with hard drives up to 6TB at 7200 RPM
|Maximum Data Transfer Rate
|10 Gbps
|TRIM Support
|Type and Rate
|USB 3.1 Gen 2 - 10 Gbit/s
|SATA III (6 Gbps)
|UASP Support
|Drive Connectors
|1 - SATA Data & Power Combo (7+15 pin) Receptacle
|Host Connectors
|1 - USB 3.1 USB Type-B (9 pin, Gen 2, 10 Gbps) Female
|OS Compatibility
|OS independent; No software or drivers required
|Special Notes / Requirements
|Windows 7 and earlier Windows versions do not support TRIM with USB to SATA devices.
|LED Indicators
|1 - Power & Activity
|Center Tip Polarity
|Input Current
|Input Voltage
|Output Current
|Output Voltage
|Plug Type
|Power Consumption (In Watts)
|Power Source
|AC Adapter Included
|Operating Temperature
|5°C to 35°C (35°F to 95°F)
|Storage Temperature
|-20°C to 50°C (-4°F to 122°F)
|Physical Characteristics
|Product Height
|2.5 in [6.4 cm]
|Product Length
|5.7 in [14.5 cm]
|Product Width
|3.6 in [92.7 mm]
|Weight of Product
|13.8 oz [392 g]
|Packaging Information
|Package Height
|6.7 in [17.1 cm]
|Package Length
|3.6 in [91 mm]
|Package Width
|6.4 in [16.3 cm]
|Shipping (Package) Weight
|26.8 oz [758 g]
|What's in the Box
|Included in Package
|1 - USB 3.1 HDD Dock
|1 - USB 3.1 A to B cable - 40.5 inches
|1 - Universal Power Adapter - 50 inches (cable)
|4 - Power Adapter Plugs (NA,EU,UK,ANZ)
|1 - Quick Install Guide
Related Products
USB 3.1 (10Gbps) Dual-Bay Dock for 2.5"/3.5" SATA SSD/HDDs
Dock two of your 2.5" and 3.5" SATA drives over high performance USB 3.1 Gen 2 with UASP
USB 3.1 (10Gbps) Enclosure for 3.5" SATA Drives
The high-speed, high-capacity data storage solution you've been waiting for – with USB 3.1 Gen 2
USB 3.1 (10 Gbps) Enclosure for 2.5" SATA Drives
Get ready for ultra-fast USB 3.1 Gen 2 data storage using your 2.5" SSD or HDD
USB 3.1 (10 Gbps) Tool-Free Enclosure for 2.5" SATA Drives
Get the faster speed of USB 3.1 Gen 2 in a lightweight and portable storage solution
USB 3.1 (10Gbps) Adapter Cable for 2.5" SATA Drives
Connect a 2.5" SATA SSD/HDD to your computer using this USB 3.1 Gen 2 ultra-portable cable
USB 3.0 to SATA Hard Drive Docking Station for 2.5/3.5 HDD
Enable fast, swappable access to your 2.5in or 3.5in SATA hard drives, through USB 3.0
USB 3.0 SATA Hard Drive Docking Station SSD / HDD with integrated Fast Charge USB Hub and UASP For SATA 6 Gbps - White
Dock your 2.5" or 3.5" SATA SSDs/HDDs and add USB Fast Charge Capacity in a stylish white docking station
USB 3.0 SATA III Hard Drive Docking Station SSD / HDD with UASP
Dock your 2.5in or 3.5in SATA III SSDs/HDDs over USB 3.0 with UASP
USB 3.0 Dual Hard Drive Docking Station with UASP for 2.5/3.5in SSD / HDD – SATA 6 Gbps
Dock two 2.5" or 3.5" SATA III SSDs/HDDs over USB 3.0 with UASP
eSATA / USB 3.0 Hard Drive Duplicator Dock – Standalone HDD Cloner with SATA 6Gbps for fast-speed duplication
Clone a 2.5in/3.5in SATA drive without a host computer connection, or dock the drives over USB 3.0 or eSATA for easy access
USB 3.1 (10Gbps) Single-Bay Dock for 2.5"/3.5" SATA SSD/HDD
Dock your 2.5" or 3.5" SATA drive over high performance USB 3.1 with UASP
1m (3ft) Certified SuperSpeed USB 3.0 A to B Cable - M/M
Connect your USB 3.0 devices with this high-quality USB 3.0 certified cable
SATA to 2.5in or 3.5in IDE Hard Drive Adapter for HDD Docks
Use your 2.5in or 3.5in IDE hard drives in a SATA HDD Docking Station
mSATA SSD to 2.5in SATA Adapter Converter
Convert an mSATA SSD into a 7mm high 2.5in SATA 6Gbps Open Frame SSD
M.2 SSD to 2.5in SATA Adapter Converter
Convert an M.2 SSD into a 7mm high 2.5in SATA 6Gbps Open Frame SSD
3.5in Silicone Hard Drive Protector Sleeve with Connector Cap
Provide protection against shocks/impacts to a 3.5in hard drive
2.5in Silicone Laptop Hard Drive Protector Sleeve with Connector Cap
Provide protection against shocks/impacts to a 2.5in hard drive
2.5in Anti-Static Hard Drive Protector Case - Black (3pk)
Provides safe handling and anti-static protection for most 2.5in hard drives
Product Support
- Firmware.zip Version: 160310.b1.33.00
Data Sheets
Frequently Asked Questions
Before You Buy
Yes, this device supports the TRIM command. If the OS issues a TRIM command, the command will be passed to the connected device.
To determine if your hard drive will work in this device, on the product page, click the Technical Specifications tab, and do the following:
- Make sure that the device supports the storage size of your hard drive. If the storage size of your hard drive is larger than what the device was tested with, the hard drive will likely still work with the enclosure.
- Confirm that your hard drive uses the same interface type as the device. For example, IDE, SATA, or M.2.
- Make sure that the device supports the physical size of your hard drive, such as 2.5 inches or 3.5 inches.
- Verify that the power consumption of your hard drive doesn't exceed the power output of the device. If you're using multiple hard drives, make sure that the combined power consumption of all of the hard drives doesn't exceed the power output of the docking station.
USB 3.1 is the most recent version of the USB (Universal Serial Bus) standard for connecting computers and electronic devices. It is capable of data transfer speeds up to 10Gbps, and while it can use the USB-C connector type, it can also use a variety of other connector types. To achieve USB 3.1 transfer speeds, your USB host connection, cables, and device must all support USB 3.1. USB 3.1 is also known as USB 3.1 Gen 2 (10Gbps).
USB 3.0 is capable of data transfer speeds up to 5Gbps. USB 3.0 is also known as USB 3.1 Gen 1 (5Gbps).
USB 3.1 is backwards compatible with USB 3.0 and USB 2.0, except in the following scenarios:
- USB-B 3.1 cables are not compatible with USB-B 2.0 ports.
- Unless you use an adapter, USB-C ports or cables will not work with USB-A or USB-B ports or cables.
- Devices that require USB 3.1 transfer speeds of 10Gbps might not work with USB 3.0 or USB 2.0, or you might experience lower transfer speeds and impacted performance.
- Bus-powered USB devices that requires more power than what USB 2.0 can provide are not compatible with USB 2.0.
For products related to this article, click here.
To transfer data at speeds of 10Gbps, you need to confirm that the following components in your setup support USB 3.1:
- The USB host connection
- The USB cable
- The USB device and any subcomponents (for example, a hard drive docking station and the hard drives in the docking station)
Note: USB 3.1 is also known as USB 3.1 Gen 2 (10Gbps). Devices that support USB 3.1 should have the USB 3.1 symbol on them. If the USB 3.1 symbol does not appear on your USB source or device, refer to the information provided by the manufacturer to confirm whether the USB source or device support USB 3.1.
The included USB cable for this USB 3.1 Gen 2 device has been tested and verified to perform at USB 3.1 Gen 2 speeds of 10Gbps.
How to
To confirm that Windows detects your USB device, complete the following:
- Press the Windows key+R, type devmgmt.msc, and press Enter.
- In Device Manager, under the appropriate heading, confirm that your expansion card is listed and that there isn't an exclamation mark next to it. For example, a USB controller card would be under Universal Serial Bus controllers.
Your USB device is listed according to the name of the chipset. To determine the name of the chipset of your USB device, navigate to www.StarTech.com and look on the Technical Specifications tab for your product.
To confirm that the Mac OS detects your USB device, complete the following:
- Click the Apple icon.
- Click About This Mac.
- Click More Info or System Report.
- Under the appropriate heading, confirm that your USB device is listed and that there isn't an error. For example, a network card would be under Ethernet Cards.
You may need to refresh the System Information page after you plug in your device. To do so, press Command + R with the System Information page open.
Your USB device is listed according to the name of the chipset. To determine the name of the chipset of your USB device, navigate to www.StarTech.com and look on the Technical Specifications tab for your product.
- The drive may be damaged. Test with a known-working drive, or test the drive directly to a PC.
- The operating system on the computer may not support reading and writing to the file system on the docked hard drive or SSD. Remember, Windows cannot read Mac or Linux file systems. Also, macOS can read but not write to NTFS drives.
- If the drives came from a RAID (Redundant Array of Independent Disks), they would not be accessible in our docking stations.
- If the drive uses 4Kn sectors, check the technical specifications of the docking station, and ensure it can read 4Kn drives.
When you troubleshoot issues with a hard drive dock or duplicator, there are some quick tests that you can complete to rule out potential problems. You can test to make sure that the following components are working correctly and are not the source of the issue:
- IDE, SATA, and eSATA cables
- Hard drives
- Hard drive dock or duplicator
To test your setup components, try the following:
- Use the cables, hard drives, and hard drive dock or duplicator in another setup to see if the problem is with the components or the setup.
- Use a different cable, hard drive, and hard drive dock or duplicator in your setup to see if the problem persists. Ideally, you should test a component that you know works in another setup.
When you test the hard drive and hard drive dock or duplicator, it is recommended that you do the following:
Note: For a hard drive duplicator you may need to switch the device to PC mode (if available).
- To check Disk Management, press the Windows key + R, type diskmgmt.msc, and press Enter. Check to see if your hard drive is listed.
- Do one of the following:
- If the hard drive is listed with unallocated space, the hard drive needs to be reformatted. Right-click unallocated and click New Simple Volume. Follow the on-screen instructions to complete the reformatting.
Note: Formatting a hard drive erases all of the data on it. Make sure that you back up all of your data before you reformat the hard drive.
- If the hard drive is listed as healthy but does not have a drive letter, for example, C:, right-click healthy and click Change Drive Letter and Paths. Click Add, assign a drive letter, and click OK.
Note: A formatted hard drive will not show up in Computer or My Computer until it has a drive letter assigned to it.
This docking station allows the hard drive to enforce its own power state, as opposed to enforcing a power state that keeps the hard drive active at all times. Since most newer hard drives have low-power energy conservation modes, this will cause the hard drive to enter an idle state if it is not used for a certain amount of time.
If your setup components support USB 3.1 but you are experiencing slower transfer speeds than you expected, consider the following:
- A USB host connection with multiple USB 3.1 ports might not be able to support 10Gbps on each port simultaneously.
- The type of port on a device does not determine whether the device is capable of USB 3.1 speeds. A USB-C port might not support USB 3.1 speeds, while USB-A and USB-B ports might support USB 3.1 speeds.
- Any other devices that you include in your setup, such as an older hard drive in a USB 3.1 enclosure, might create a point of congestion and slow down transfer speeds.
To confirm the functionality of your USB host connection, its ports, and any other devices in your setup, refer to the information provided by the manufacturer.
Note: USB 3.1 is also known as USB 3.1 Gen 2 (10Gbps). Devices that support USB 3.1 should have the USB 3.1 symbol on them. If the USB 3.1 symbol does not appear on your USB source or device, refer to the information provided by the manufacturer to confirm whether the USB source or device support USB 3.1.
You should not upgrade your device's firmware if you do not have any issues with the functionality of your device. The only time you should consider an upgrade is if you are experiencing a problem with the device, and you have confirmed that the firmware addresses this problem. You can confirm this is the case by reviewing the documentation included with the firmware or by consulting with our Technical Support team. Incorrectly upgrading firmware can result in diminished performance so it is best to contact StarTech.com if you would like to perform this operation.
Hard Drives
Windows 10
Before you can access a new or formatted drive in your operating system, you need to initialize it first and then create a partition on the drive. A partition defines an area of the drive to use for storing data. The partition uses a file system (for example, ex-FAT, NTFS, and so on).
Initialize a drive
Note: You typically only need to initialize a drive if the drive is new. If you cannot find an uninitialized drive in Disk Management, skip the following steps and try to partition your device.
Press the Windows key + R, type compmgmt.msc, and click Run to open Computer Management.
Navigate to Disk Management.
When prompted to, initialize your disk(s). If you are running Windows® 7 or later and are using a drive larger than 2TB, initialize the disk(s) with GPT. If you are running an earlier version of Windows, initialize the disk(s) with MBR. For more information, visit the following FAQ: https://www.startech.com/support/faqs/technical-support?topic=hard-drives#mbr-vs-gpt.
Click OK.
Create a partition in a drive
Note: The following steps create an NTFS partition that uses the entire drive space. To use a different file system, select a different option in step 6.
Right-click Unallocated or RAW volume, and select New Simple Volume.
In the New Partition Wizard, click Next.
Select Primary partition.
Leave the partition size set to default, and click Next.
Assign a drive letter or leave it set to the default, and click Next.
Enter the following settings to format the partition:
- In the File System field, enter NTFS.
- Set the Allocation unit size to Default.
- In the Volume label field, enter <your name/reference>.
- Select the Perform a quick format check box.
- Clear the Enable file and folder compression check box.
- Click Next > Finish.
The new drive should appear in Windows Explorer.
Mac OS
Before you can access a new or formatted drive in your operating system, you need to initialize it first and then create a partition on the drive. A partition defines an area of the drive to use for storing data. The partition uses a file system (for example, HFS+, ex-FAT, NTFS, and so on).
Initialize a drive
Mac OSX detects a drive that needs to be initialized and automatically prompts you to initialize the drive. If you are prompted to initialize the drive, click Initialize. If you are not prompted to initialize the drive and you cannot find the drive in Finder, you will need to create a partition on the drive.
Create a partition on a drive
Note: The following steps create an HFS+ (Mac OS Extended (Journaled)) partition that uses the entire drive space.
To create a partition on a new drive, complete the following:
Open Finder.
Navigate to Applications and click Utilities.
Open Disk Utility.
Select the new drive and click the Partition tab.
Click Options and verify that it is set to GUID Partition Table.
Enter a name for the partition.
Click Partition.
The drive should now be accessible in Finder.
For products related to this article, click here.
Compliance and Safety
Compliance Letters
Safety Measures
- If product has an exposed circuit board, do not touch the product under power.
- If Class 1 Laser Product. Laser radiation is present when the system is open.
- Wiring terminations should not be made with the product and/or electric lines under power.
- Product installation and/or mounting should be completed by a certified professional as per the local safety and building code guidelines.
- Cables (including power and charging cables) should be placed and routed to avoid creating electric, tripping or safety hazards.
* Product appearance and specifications are subject to change without notice.


text:
Getting Past The Hurdles Of Micropayments
from the neat deptMuch of the press coverage around Flattr, the "social payments" startup, focuses on the fact that it was founded by Peter Sunde, who is perhaps better known for being the (former) spokesperson for The Pirate Bay. I have no doubt that this is a big reason why the company got a lot of its initial attention, but I think what's a lot more interesting is that this is one of the first "micropayment" platforms that actually tries to get around the historical problems of micropayments for content. There have been lots of micropayment companies out there, and almost all of them failed -- and it wasn't difficult to see why. First, they underestimated the "mental transaction costs" that micropayments entail. Just making the decision if something is worth paying for is a huge "cost" for users. Second, they heavily underestimated the "penny gap," which is the effort that it takes to get someone to go from "free" to paying even a penny. Next, it's an attempt to fight the basic economics of what supply and demand is pushing for the content be priced at. And, finally, required micropayments make it very hard to promote that content via word of mouth or sharing.
Many have tried to tackle the problem of micropayments by assuming that the only real problem is the lack of a clean and easy design. Undoubtedly, a clean and easy design makes it easier to use micropayments, but doesn't tackle all of the other issues. And it's that part that makes Flattr interesting to me, in that it actually tries to get past some of those issues. MediaEvolution recently did a short video interview with Peter about Flattr, where he explains the basic concept:
In other words, if you agree to put in $10/month, you'll always spend $10/month no matter how many things you "Flattr." It's just that the amount each thing you Flattr depends on how many you click. So if you click on 10 things, each will get a dollar. If you click on one hundred, each will get ten cents. So, there's no more mental transaction costs or penny gap, once someone has been convinced to sign up for Flattr (which is, yes, still an issue to consider).
The other neat thing that Flattr has done is to effectively set its own site up as something like a "Digg with money." Just to see what happens as an experiment, we've set up Flattr here on Techdirt. You should see the Flattr button to the left of each blog post for now. It looks kind of like a Digg This button, that shows a counter of how many people have "Flattr'd" that story. I don't expect a huge number of folks to Flattr any particular story -- especially since the service is still in private beta, but there is some interesting potential here. One of the complaints people had about Digg was how it got gamed. If Flattr could get widespread usage, it could potentially become a more useful sort of "Digg" because people actually have money riding on who they vote for. I think this aspect of the site is still a bit underdeveloped, but it has some potential.
Since Flattr is still in private beta, we do have a bunch of invites to hand out to folks, if you want them. If you're interested in getting an invite, please use our contact form with the subject "Flattr Invite." We don't have unlimited invites, of course, so first dibs will go to folks who are already Techdirt Insiders (so make sure to mention that in your email request). After that, it'll be first come, first served.
There are some others in this space as well. In the US, there's a company that's been around a bit longer called Kachingle, which Mark Glaser from PBS just wrote about, including an interview with Kachingle's CEO. Conceptually, the two are very similar. Kachingle seems to focus more narrowly on journalism/blog sites, whereas Flattr is for all sorts of content. Kachingle also has a set price: everyone has to pay $5/month, unlike Flattr which lets you choose how much you want to spend per month (in euros, for now). Also, Kachingle doesn't seem to be doing anything Digg-like (yet).
It's also interesting to note that both are big in Europe. With Flattr, this isn't as surprising, seeing as the company is in Sweden, but apparently Kachingle is big in Germany, despite being a US company. As always, I'm still not convinced that "donation" models are really that sustainable, and I've always been skeptical of "micropayments" in general. However, I find both of these attempts to be at least worth watching, as they seem to try to get around the usual hurdles associated with these models.
Filed Under: business models, micropayments, peter sunde
Companies: flattr, kachingle

subset: commoncrawl


text:
Rolex Farr 40 Worlds Day Four
Farr 40 worlds: Plenty for Plenty
Plenty (Alex Roepers, USA) won the Rolex Farr 40 world championship on Sydney's Manly offshore course today with clever, conservative sailing for a third and a second in the last two races while his two closest opponents fell out ofcontention with early errors.
Plenty won the 11-race series, conducted by Royal Sydney Yacht Squadron, with a total 34 points from the Australian champion Transfusion (Guido Belgiorno-Nettis) 38 and Struntje Light (Wolfgang and Angela Schaefer, Germany), 44.2.
The concluding two races were sailed in a 16-18 knot nor'-easter, that raised a short chop on a moderate seaway, over four-lap windward-return courses on the offshore Manly Circle.
Flash Gordon (Helmut and Evan Jahn, USA), which had gone into the day equal second with Transfusion, dropped out of contention at the start of race 10, when she was judged to be over the line early and took some time to thread back to re-start.
Transfusion, from a good start with speed towards the pin end of the line, led around all marks to win from Estate Master (Martin Hill), which held second place around all marks, with Plenty third.
The win moved Transfusion from four to two points behind Plenty going into the last race.
Plenty, however, with clever starting strategy, knocked Transfusion out of contention soon after the start of race 11. After manoeuvring to the leeward end of the line away from Transfusion, Plenty sailed back in the last minute to plant directly under Transfusion as the fleet took off on starboard tack.


text:
Welcome to my collection of Linen Post Cards. When I was a child in the 50s my eccentric aunt Hannah sent Linen Post Cards to our house from her adventures. The simple watercolor effect they have gave me many hours of daydreams from her travels. I hope I can share a few with you. Yes cards and daydreams.
Aug 1, 2020
Greetings from TOPEKA
Subscribe to: Post Comments (Atom)


text:
Running. And gin. What else do you need?
Join us for a group running tour to celebrate London's long-term thirst for gin.
We'll play gin-themed games, explore London's various gin crazes and fascinating history and uncover the famous gin palace over a gentle 10k route.
Ends with a well-deserved gin and tonic on us, from one of our favourite palaces.
This tour is for steady runners - the pace will be about 1 hour 15 minutes for 10k running speedy (a gentle jog) with plenty of breaks for gin trvia on the way. We have other speeds available (Beginner, Speedy and Rapid, available on EventBrite).
With your ticket you get:
A fun gin-themed running tour with a great guide
A well-deserved gin & tonic
Bag drop
A great evening and new gin palaces/facts to tell your friends about.
"Thank you for a fab fun! Definitely worth the trip down from Yorkshire!" Laura, Yorkshire
"Fantastic. Excellent Course. Great run for all abilities! Look forward to doing another event soon" Andrea, Surrey
"Our guide was fab. The gin run was an unexpected treat of an evening. Can't wait to do more runs with Secret London Runs." Julia, London


text:
Patent application title: Estimating relative nib position from images captured at different orientations
Paul Lapstun (Balmain, AU)
Kia Silverbrook (Balmain, AU)
Tobin Allen King (Balmain, AU)
Silverbrook Research Pty Ltd
IPC8 Class: AG06F3033FI
USPC Class:
Class name: Computer graphics processing and selective visual display systems display peripheral interface input device stylus
Publication date: 2013-03-28
Patent application number: 20130076702
Sign up to receive free email alerts when patent applications with chosen keywords are published SIGN UP
A method of estimating a position of nib of a pen relative to an optical
sensor removably mounted on the pen. The optical sensor captures at least
two images of a coded surface when the nib contacts the coded surface.
The images are captured with the nib at a same position on the coded
surface and the pen at different orientations relative to the coded
surface. From a perspective distortion of the coded surface in each
image, an estimated rotation and viewing distance for each image are
estimated, and from the estimated rotations and viewing distances, the
position of the nib relative to the optical sensor is estimated.
1. A method of estimating a position of nib of a pen relative to an
optical sensor removably mounted on the pen, said method comprising the
steps of: capturing, using the optical sensor, at least two images of a
coded surface when the nib contacts the coded surface, the at least two
images being captured with the nib at a same position on the coded
surface and the pen at different orientations relative to the coded
surface; determining, from a perspective distortion of the coded surface
in each image, an estimated rotation and viewing distance for each image;
and estimating, from the estimated rotations and viewing distances, the
position of the nib relative to the optical sensor.
2. The method of claim 1, comprising the steps of: generating a line for each rotation using a corresponding estimated rotation and viewing distance; intersecting the at least two lines generated; and estimating, from at least one point of intersection of the lines, the position of the nib relative to the sensor.
3. The method of claim 1, wherein the coded surface comprises position coding data.
4. The method of claim 3, wherein the position coding data is defined by a plurality of tags, each tag encoding the position of the tag on the surface.
5. An electronic pen comprising: a body; a nib at one end of the body for contacting a coded surface; an optical sensor removably mounted on the body for capturing images of the coded surface; and a processor configured for estimating a position of nib relative to the optical sensor from at least two images of the coded surface, the at least two images being captured with the nib at a same position on the coded surface and the pen at different orientations relative to the coded surface: determining, from a perspective distortion of the coded surface in each image, an estimated rotation and viewing distance for each image; and estimating, from the estimated rotations and viewing distances, the position of the nib relative to the optical sensor.
6. The electronic pen of claim 5, wherein the processor is configured for: generating a line for each rotation using a corresponding estimated rotation and viewing distance; intersecting the at least two lines generated; and estimating, from at least one point of intersection, the position of the nib relative to the sensor.
[0001] The present application is a continuation of U.S. application Ser. No. 12/649,303 filed Dec. 29, 2009, which is a continuation of U.S. application Ser. No. 11/488,832 filed Jul. 19, 2006, now issued U.S. Pat. No. 7,649,523, which is a continuation of U.S. application Ser. No. 09/722,172 filed on Nov. 25, 2000, now issued U.S. Pat. No. 7,091,960 all of which is here incorporated by reference.
[0002] The present invention relates generally to a sensing device for capturing interactions with and movement relative to a surface, and more particularly, to a sensing device attachable to a stylus or marking implement such as a pen, pencil or eraser.
[0003] Various methods, systems and apparatus relating to the present invention are disclosed in the following patents filed by the applicant or assignee of the present invention on Nov. 25, 2000:
[0004] The disclosures of these co-pending applications are incorporated herein by reference. Various methods, systems and apparatus relating to the present invention are disclosed in the following patents filed by the applicant or assignee of the present invention on Oct. 20, 2000:
[0005] The disclosures of these co-pending applications are incorporated herein by reference. Various methods, systems and apparatus relating to the present invention are disclosed in the following patents filed by the applicant or assignee of the present invention on Sep. 15, 2000:
The disclosures of these co-pending applications are incorporated herein by reference. Various methods, systems and apparatus relating to the present invention are disclosed in the following patents filed by the applicant or assignee of the present invention on Jun. 30, 2000:
[0006] The disclosures of these co-pending applications are incorporated herein by reference. Various methods, systems and apparatus relating to the present invention are disclosed in the following patents filed by the applicant or assignee of the present invention on 23 May 2000:
The disclosures of these co-pending applications are incorporated herein by reference.
[0007] Self-contained pen-like devices have been described which mark a surface while simultaneously capturing their own movement relative to the surface. Some such devices sense their own movement using embedded accelerometers. Others sense their own movement by detecting information which is machine-readably encoded on the surface. In this latter category, see for example U.S. Pat. No. 5,477,012, U.S. Pat. No. 5,652,412 and PCT application WO99/50787.
[0008] Since these pen-like devices typically include an integral marking means, they support only a limited set of marking modes or styles.
[0009] In accordance with an aspect of the present invention, there is provided a method of estimating a position of nib of a pen relative to an optical sensor removably mounted on the pen, said method comprising the steps of:
[0010] capturing, using the optical sensor, at least two images of a coded surface when the nib contacts the coded surface, the at least two images being captured with the nib at a same position on the coded surface and the pen at different orientations relative to the coded surface;
[0011] determining, from a perspective distortion of the coded surface in each image, an estimated rotation and viewing distance for each image; and
[0012] estimating, from the estimated rotations and viewing distances, the position of the nib relative to the optical sensor.
[0013] Features and advantages of the present invention will become apparent from the following description of embodiments thereof, by way of example only, with reference to the accompanying drawings.
[0014] Preferred and other embodiments of the invention will now be described, by way of non-limiting example only, with reference to the accompanying drawings, in which:
[0015] FIG. 1 is a schematic of a the relationship between a sample printed netpage and its online page description;
[0016] FIG. 2 is a schematic view of a interaction between a pen with an attached netpage code sensor attachment, a netpage printer, a netpage page server, and a netpage application server;
[0017] FIG. 3 is a schematic view of a high-level structure of a printed netpage and its online page description;
[0018] FIG. 4a is a plan view showing a structure of a netpage tag;
[0019] FIG. 4b is a plan view showing a relationship between a set of the tags shown in FIG. 4a and a field of view of a netpage sensing device;
[0020] FIG. 5a is a plan view showing an alternative structure of a netpage tag;
[0021] FIG. 5b is a plan view showing a relationship between a set of the tags shown in FIG. 5a and a field of view of a netpage sensing device;
[0022] FIG. 5c is a plan view showing an arrangement of nine of the tags shown in FIG. 5a where targets are shared between adjacent tags;
[0023] FIG. 5d is a plan view showing the interleaving and rotation of the symbols of the four codewords of the tag shown in FIG. 5a;
[0024] FIG. 6 is a schematic view of a tag image processing and decoding algorithm;
[0025] FIG. 7 is a perspective view of a netpage code sensor attachment according to the present invention, attached to a pen;
[0026] FIG. 8 is a perspective view of the netpage code sensor attachment attached to a capped pen;
[0027] FIG. 9 is a perspective view of the netpage code sensor attachment;
[0028] FIG. 10 is a perspective view of the underside of the netpage code sensor attachment;
[0029] FIG. 11 is an exploded view of the netpage code sensor attachment;
[0030] FIG. 12 is a cross section of the netpage code sensor attachment;
[0031] FIG. 13 is a perspective view of the PCB and optics block of the netpage code sensor attachment;
[0032] FIG. 14 is a schematic block diagram of a controller for the netpage code sensor attachment;
[0033] FIG. 15 is a schematic view of a netpage code sensor attachment optical path;
[0034] FIG. 16 is a flowchart of a stroke capture algorithm;
[0035] FIG. 17 is a schematic view of a raw digital ink class diagram;
[0036] FIG. 18 is a perspective view of the netpage code sensor attachment housed in a base according to the present invention;
[0037] FIG. 19 is a plan view of the netpage code sensor attachment housed in the base;
[0038] FIG. 20 is a side elevation of the netpage code sensor attachment housed in the base;
[0039] FIG. 21 is a front elevation of the netpage code sensor attachment housed in the base;
[0040] FIG. 22 is a cross section of the netpage code sensor attachment and base, with the attachable sensing device housed in the base;
[0041] FIG. 23 is a schematic view of the calibration of point nib geometry; and
[0042] FIG. 24 is a schematic view of the calibration of spherical nib geometry.
[0043] Note: Memjet® is a trademark of Silverbrook Research Pty Ltd, Australia.
[0044] In the preferred embodiment, the invention is configured to work with the netpage networked computer system, a summary of which is given below and a detailed description of which is given in our co-pending applications, including in particular applications U.S. Ser. No. 09/721,893, U.S. Ser. No. 09/722,142, U.S. Ser. No. 09/575,129 and granted U.S. Pat. No. 6,428,133. It will be appreciated that not every implementation will necessarily embody all or even most of the specific details and extensions described in these applications in relation to the basic system. However, the system is described in its most complete form to assist in understanding the context in which the preferred embodiments and aspects of the present invention operate.
[0045] In brief summary, the preferred form of the netpage system employs a computer interface in the form of a mapped surface, that is, a physical surface which contains references to a map of the surface maintained in a computer system. The map references can be queried by an appropriate sensing device. Depending upon the specific implementation, the map references may be encoded visibly or invisibly, and defined in such a way that a local query on the mapped surface yields an unambiguous map reference both within the map and among different maps. The computer system can contain information about features on the mapped surface, and such information can be retrieved based on map references supplied by a sensing device used with the mapped surface. The information thus retrieved can take the form of actions which are initiated by the computer system on behalf of the operator in response to the operator's interaction with the surface features.
[0046] In its preferred form, the netpage system relies on the production of, and human interaction with, netpages. These are pages of text, graphics and images printed on ordinary paper or other media, but which work like interactive web pages. Information is encoded on each page using ink which is substantially invisible to the unaided human eye. The ink, however, and thereby the coded data, can be sensed by an optically imaging pen and transmitted to the netpage system.
[0047] In the preferred form, active buttons and hyperlinks on each page can be
[0048] clicked with the pen to request information from the network or to signal preferences to a network server. In one embodiment, text written by hand on a netpage is automatically recognized and converted to computer text in the netpage system, allowing forms to be filled in. In other embodiments, signatures recorded on a netpage are automatically verified, allowing e-commerce transactions to be securely authorized.
[0049] As illustrated in FIG. 1, a printed netpage 1 can represent a interactive form which can be filled in by the user both physically, on the printed page, and "electronically", via communication between the pen and the netpage system. The example shows a "Request" form containing name and address fields and a submit button. The netpage consists of graphic data 2 printed using visible ink, and coded data 3 printed as a collection of tags 4 using invisible ink. The corresponding page description 5, stored on the netpage network, describes the individual elements of the netpage. In particular it describes the type and spatial extent (zone) of each interactive element (i.e. text field or button in the example), to allow the netpage system to correctly interpret input via the netpage. The submit button 6, for example, has a zone 7 which corresponds to the spatial extent of the corresponding graphic 8.
[0050] As illustrated in FIG. 2, the netpage pen 101, a preferred form of which is described in our co-pending application U.S. Ser. No. 09/575,174, works in conjunction with a netpage printer 601, an Internet-connected printing appliance for home, office or mobile use. The pen is wireless and communicates securely with the netpage printer via a short-range radio link 9.
[0051] The netpage printer 601, preferred forms of which are described in our co-pending applications U.S. Ser. No. 09/722,142 and U.S. Ser. No. 09/693,514, is able to deliver, periodically or on demand, personalized newspapers, magazines, catalogs, brochures and other publications, all printed at high quality as interactive netpages. Unlike a personal computer, the netpage printer is an appliance which can be, for example, wall-mounted adjacent to an area where the morning news is first consumed, such as in a user's kitchen, near a breakfast table, or near the household's point of departure for the day. It also comes in tabletop, desktop, portable and miniature versions.
[0052] Netpages printed at their point of consumption combine the ease-of-use of
[0053] paper with the timeliness and interactivity of an interactive medium.
[0054] As shown in FIG. 2, the netpage pen 101 interacts with the coded data on a printed netpage 1 and communicates, via a short-range radio link 9, the interaction to a netpage printer. The printer 601 sends the interaction to the relevant netpage page server 10 for interpretation. In appropriate circumstances, the page server sends a corresponding message to application computer software running on a netpage application server 13. The application server may in turn send a response which is printed on the originating printer.
[0055] The netpage system is made considerably more convenient in the preferred embodiment by being used in conjunction with high-speed microelectromechanical system (MEMS) based inkjet (Memjet®) printers, for example as described in our co-pending granted U.S. Pat. No. 6,428,133. In the preferred form of this technology, relatively high-speed and high-quality printing is made more affordable to consumers. In its preferred form, a netpage publication has the physical characteristics of a traditional newsmagazine, such as a set of letter-size glossy pages printed in full color on both sides, bound together for easy navigation and comfortable handling.
[0056] The netpage printer exploits the growing availability of broadband Internet access. The netpage printer can also operate with slower connections, but with longer delivery times and lower image quality. The netpage system can also be enabled using existing consumer inkjet and laser printers, although the system will operate more slowly and will therefore be less acceptable from a consumer's point of view. In other embodiments, the netpage system is hosted on a private intranet. In still other embodiments, the netpage system is hosted on a single computer or computer-enabled device, such as a printer.
[0057] Netpage publication servers 14 on the netpage network are configured to deliver print-quality publications to netpage printers. Periodical publications are delivered automatically to subscribing netpage printers via pointcasting and multicasting Internet protocols. Personalized publications are filtered and formatted according to individual user profiles.
[0058] A netpage printer can be configured to support any number of pens, and a pen can work with any number of netpage printers. In the preferred implementation, each netpage pen has a unique identifier. A household may have a collection of colored netpage pens, one assigned to each member of the family. This allows each user to maintain a distinct profile with respect to a netpage publication server or application server.
[0059] A netpage pen can also be registered with a netpage registration server 11 and linked to one or more payment card accounts. This allows e-commerce payments to be securely authorized using the netpage pen. The netpage registration server compares the signature captured by the netpage pen with a previously registered signature, allowing it to authenticate the user's identity to an e-commerce server. Other biometrics can also be used to verify identity. A version of the netpage pen includes fingerprint scanning, verified in a similar way by the netpage registration server.
[0060] Although a netpage printer may deliver periodicals such as the morning newspaper without user intervention, it can be configured never to deliver unsolicited junk mail. In its preferred form, it only delivers periodicals from subscribed or otherwise authorized sources. In this respect, the netpage printer is unlike a fax machine or e-mail account which is visible to any junk mailer who knows the telephone number or e-mail address.
[0061] Each object model in the system is described using a Unified Modeling Language (UML) class diagram. A class diagram consists of a set of object classes connected by relationships, and two kinds of relationships are of interest here: associations and generalizations. An association represents some kind of relationship between objects, i.e. between instances of classes. A generalization relates actual classes, and can be understood in the following way: if a class is thought of as the set of all objects of that class, and class A is a generalization of class B, then B is simply a subset of A. Each class is drawn as a rectangle labelled with the name of the class. It contains a list of the attributes of the class, separated from the name by a horizontal line, and a list of the operations of the class, separated from the attribute list by a horizontal line. In the class diagrams which follow, however, operations are never modelled. An association is drawn as a line joining two classes, optionally labelled at either end with the multiplicity of the association. The default multiplicity is one. An asterisk (*) indicates a multiplicity of "many", i.e. zero or more. Each association is optionally labelled with its name, and is also optionally labelled at either end with the role of the corresponding class. An open diamond indicates an aggregation association ("is-part-of"), and is drawn at the aggregator end of the association line. A generalization relationship ("is-a") is drawn as a solid line joining two classes, with an arrow (in the form of an open triangle) at the generalization end. When a class diagram is broken up into multiple diagrams, any class which is duplicated is shown with a dashed outline in all but the main diagram which defines it. It is shown with attributes only where it is defined.
[0062] Netpages are the foundation on which a netpage network is built. They provide a paper-based user interface to published information and interactive services. A netpage consists of a printed page (or other surface region) invisibly tagged with references to an online description of the page. The online page description is maintained persistently by a netpage page server. The page description describes the visible layout and content of the page, including text, graphics and images. It also describes the input elements on the page, including buttons, hyperlinks, and input fields. A netpage allows markings made with a netpage pen on its surface to be simultaneously captured and processed by the netpage system.
[0063] Multiple netpages can share the same page description. However, to allow input through otherwise identical pages to be distinguished, each netpage is assigned a unique page identifier. This page ID has sufficient precision to distinguish between a very large number of netpages.
[0064] Each reference to the page description is encoded in a printed tag. The tag identifies the unique page on which it appears, and thereby indirectly identifies the page description. The tag also identifies its own position on the page. Characteristics of the tags are described in more detail below.
[0065] Tags are printed in infrared-absorptive ink on any substrate which is infrared-reflective, such as ordinary paper. Near-infrared wavelengths are invisible to the human eye but are easily sensed by a solid-state image sensor with an appropriate filter.
[0066] A tag is sensed by an area image sensor in the netpage pen, and the tag data is transmitted to the netpage system via the nearest netpage printer. The pen is wireless and communicates with the netpage printer via a short-range radio link. Tags are sufficiently small and densely arranged that the pen can reliably image at least one tag even on a single click on the page. It is important that the pen recognize the page ID and position on every interaction with the page, since the interaction is stateless. Tags are error-correctably encoded to make them partially tolerant to surface damage.
[0067] The netpage page server maintains a unique page instance for each printed netpage, allowing it to maintain a distinct set of user-supplied values for input fields in the page description for each printed netpage.
[0068] The relationship between the page description, the page instance, and the printed netpage is shown in FIG. 3. The printed netpage may be part of a printed netpage document 45. The page instance is associated with both the netpage printer which printed it and, if known, the netpage user who requested it.
[0069] In a preferred form, each tag identifies the region in which it appears, and the location of that tag within the region. A tag may also contain flags which relate to the region as a whole or to the tag. One or more flag bits may, for example, signal a tag sensing device to provide feedback indicative of a function associated with the immediate area of the tag, without the sensing device having to refer to a description of the region. A netpage pen may, for example, illuminate an "active area" LED when in the zone of a hyperlink.
[0070] In a preferred embodiment, each tag contains an easily recognized invariant structure which aids initial detection, and which assists in minimizing the effect of any warp induced by the surface or by the sensing process. The tags preferably tile the entire page, and are sufficiently small and densely arranged that the pen can reliably image at least one tag even on a single click on the page. It is important that the pen recognize the page ID and position on every interaction with the page, since the interaction is stateless.
[0071] In a preferred embodiment, the region to which a tag refers coincides with an entire page, and the region ID encoded in the tag is therefore synonymous with the page ID of the page on which the tag appears. In other embodiments, the region to which a tag refers can be an arbitrary subregion of a page or other surface. For example, it can coincide with the zone of an interactive element, in which case the region ID can directly identify the interactive element.
[0072] Each tag contains typically contains 16 bits of tag ID, at least 90 bits of region ID, and a number of flag bits. Assuming a maximum tag density of 64 per square inch, a 16-bit tag ID supports a region size of up to 1024 square inches. Larger regions can be mapped continuously without increasing the tag ID precision simply by using abutting regions and maps. The distinction between a region ID and a tag ID is mostly one of convenience. For most purposes the concatenation of the two can be considered as a globally unique tag ID. Conversely, it may also be convenient to introduce structure into the tag ID, for example to define the x and y coordinates of the tag. A 90-bit region ID allows 290 (˜1027 or a thousand trillion trillion) different regions to be uniquely identified. Tags may also contain type information, and a region may be tagged with a mixture of tag types. For example, a region may be tagged with one set of tags encoding x coordinates and another set, interleaved with the first, encoding y coordinates.
[0073] In one embodiment, 120 bits of tag data are redundantly encoded using a (15, 5) Reed-Solomon code. This yields 360 encoded bits consisting of 6 codewords of 15 4-bit symbols each. The (15, 5) code allows up to 5 symbol errors to be corrected per codeword, i.e. it is tolerant of a symbol error rate of up to 33% per codeword. Each 4-bit symbol is represented in a spatially coherent way in the tag, and the symbols of the six codewords are interleaved spatially within the tag. This ensures that a burst error (an error affecting multiple spatially adjacent bits) damages a minimum number of symbols overall and a minimum number of symbols in any one codeword, thus maximising the likelihood that the burst error can be fully corrected.
[0074] Any suitable error-correcting code code can be used in place of a (15, 5) Reed-Solomon code, for example a Reed-Solomon code with more or less redundancy, with the same or different symbol and codeword sizes; another block code; or a different kind of code, such as a convolutional code (see, for example, Stephen B. Wicker, Error Control Systems for Digital Communication and Storage, Prentice-Hall 1995, the contents of which a herein incorporated by cross-reference).
[0075] One embodiment of the physical representation of the tag, shown in FIG. 4a and described in our co-pending application U.S. Ser. No. 09/575,129, includes fixed target structures 15, 16, 17 and variable data areas 18. The fixed target structures allow a sensing device such as the netpage pen to detect the tag and infer its three-dimensional orientation relative to the sensor. The data areas contain representations of the individual bits of the encoded tag data. To maximise its size, each data bit is represented by a radial wedge in the form of an area bounded by two radial lines and two concentric circular arcs. Each wedge has a minimum dimension of 8 dots at 1600 dpi and is designed so that its base (its inner arc), is at least equal to this minimum dimension. The height of the wedge in the radial direction is always equal to the minimum dimension. Each 4-bit data symbol is represented by an array of 2×2 wedges. The fifteen 4-bit data symbols of each of the six codewords are allocated to the four concentric symbol rings 18a to 18d in interleaved fashion. Symbols are allocated alternately in circular progression around the tag. The interleaving is designed to maximise the average spatial distance between any two symbols of the same codeword.
[0076] In order to support "single-click" interaction with a tagged region via a sensing device, the sensing device must be able to see at least one entire tag in its field of view no matter where in the region or at what orientation it is positioned. The required diameter of the field of view of the sensing device is therefore a function of the size and spacing of the tags. Assuming a circular tag shape, the minimum diameter of the sensor field of view 193 is obtained when the tags are tiled on a equilateral triangular grid, as shown in FIG. 4b.
[0077] The tag image processing and decoding performed by a sensing device such as the netpage pen is shown in FIG. 6. While a captured image is being acquired from the image sensor, the dynamic range of the image is determined (at 20). The center of the range is then chosen as the binary threshold for the image 21. The image is then thresholded and segmented into connected pixel regions (i.e. shapes 23) (at 22). Shapes which are too small to represent tag target structures are discarded. The size and centroid of each shape is also computed.
[0078] Binary shape moments 25 are then computed (at 24) for each shape, and these provide the basis for subsequently locating target structures. Central shape moments are by their nature invariant of position, and can be easily made invariant of scale, aspect ratio and rotation.
[0079] The ring target structure 15 is the first to be located (at 26). A ring has the advantage of being very well behaved when perspective-distorted. Matching proceeds by aspect-normalizing and rotation-normalizing each shape's moments. Once its second-order moments are normalized the ring is easy to recognize even if the perspective distortion was significant. The ring's original aspect and rotation 27 together provide a useful approximation of the perspective transform.
[0080] The axis target structure 16 is the next to be located (at 28). Matching proceeds by applying the ring's normalizations to each shape's moments, and rotation-normalizing the resulting moments. Once its second-order moments are normalized the axis target is easily recognized. Note that one third order moment is required to disambiguate the two possible orientations of the axis. The shape is deliberately skewed to one side to make this possible. Note also that it is only possible to rotation-normalize the axis target after it has had the ring's normalizations applied, since the perspective distortion can hide the axis target's axis. The axis target's original rotation provides a useful approximation of the tag's rotation due to pen yaw 29.
[0081] The four perspective target structures 17 are the last to be located (at 30). Good estimates of their positions are computed based on their known spatial relationships to the ring and axis targets, the aspect and rotation of the ring, and the rotation of the axis. Matching proceeds by applying the ring's normalizations to each shape's moments. Once their second-order moments are normalized the circular perspective targets are easy to recognize, and the target closest to each estimated position is taken as a match. The original centroids of the four perspective targets are then taken to be the perspective-distorted corners 31 of a square of known size in tag space, and an eight-degree-of-freedom perspective transform 33 is inferred (at 32) based on solving the well-understood equations relating the four tag-space and image-space point pairs (see Heckbert, P., Fundamentals of Texture Mapping and Image Warping, Masters Thesis, Dept. of EECS, U. of California at Berkeley, Technical Report No. UCB/CSD 89/516, June 1989, the contents of which are herein incorporated by cross-reference).
[0082] The inferred tag-space to image-space perspective transform is used to project (at 36) each known data bit position in tag space into image space where the real-valued position is used to bilinearly interpolate (at 36) the four relevant adjacent pixels in the input image. The previously computed image threshold 21 is used to threshold the result to produce the final bit value 37.
[0083] Once all 360 data bits 37 have been obtained in this way, each of the six 60-bit Reed-Solomon codewords is decoded (at 38) to yield 20 decoded bits 39, or 120 decoded bits in total. Note that the codeword symbols are sampled in codeword order, so that codewords are implicitly de-interleaved during the sampling process.
[0084] The ring target 15 is only sought in a subarea of the image whose relationship to the image guarantees that the ring, if found, is part of a complete tag. If a complete tag is not found and successfully decoded, then no pen position is recorded for the current frame. Given adequate processing power and ideally a non-minimal field of view 193, an alternative strategy involves seeking another tag in the current image.
[0085] The obtained tag data indicates the identity of the region containing the tag and the position of the tag within the region. An accurate position 35 of the pen nib in the region, as well as the overall orientation 35 of the pen, is then inferred (at 34) from the perspective transform 33 observed on the tag and the known spatial relationship between the pen's physical axis and the pen's optical axis.
[0086] The tag structure just described is designed to allow both regular tilings of planar surfaces and irregular tilings of non-planar surfaces. Regular tilings are not, in general, possible on non-planar surfaces. In the more usual case of planar surfaces where regular tilings of tags are possible, i.e. surfaces such as sheets of paper and the like, more efficient tag structures can be used which exploit the regular nature of the tiling.
[0087] An alternative tag structure more suited to a regular tiling is shown in FIG. 5a. The tag 4 is square and has four perspective targets 17. It is similar in structure to tags described by Bennett et al. in U.S. Pat. No. 5,051,746. The tag represents sixty 4-bit Reed-Solomon symbols 47, for a total of 240 bits. The tag represents each one bit as a dot 48, and each zero bit by the absence of the corresponding dot. The perspective targets are designed to be shared between adjacent tags, as shown in FIGS. 5b and 5c. FIG. 5b shows a square tiling of 16 tags and the corresponding minimum field of view 193, which must span the diagonals of two tags. FIG. 5c; shows a square tiling of nine tags, containing all one bits for illustration purposes.
[0088] Using a (15, 7) Reed-Solomon code, 112 bits of tag data are redundantly encoded to produce 240 encoded bits. The four codewords are interleaved spatially within the tag to maximize resilience to burst errors. Assuming a 16-bit tag ID as before, this allows a region ID of up to 92 bits. The data-bearing dots 48 of the tag are designed to not overlap their neighbors, so that groups of tags cannot produce structures which resemble targets. This also saves ink. The perspective targets therefore allow detection of the tag, so further targets are not required. Tag image processing proceeds as described above, with the exception that steps 26 and 28 are omitted.
[0089] Although the tag may contain an orientation feature to allow disambiguation of the four possible orientations of the tag relative to the sensor, it is also possible to embed orientation data in the tag data. For example, the four codewords can be arranged so that each tag orientation contains one codeword placed at that orientation, as shown in FIG. 5d, where each symbol is labelled with the number of its codeword (1-4) and the position of the symbol within the codeword (A-O). Tag decoding then consists of decoding one codeword at each orientation.
[0090] Each codeword can either contain a single bit indicating whether it is the first codeword, or two bits indicating which codeword it is. The latter approach has the advantage that if, say, the data content of only one codeword is required, then at most two codewords need to be decoded to obtain the desired data. This may be the case if the region ID is not expected to change within a stroke and is thus only decoded at the start of a stroke. Within a stroke only the codeword containing the tag ID is then desired. Furthermore, since the rotation of the sensing device changes slowly and predictably within a stroke, only one codeword typically needs to be decoded per frame.
[0091] It is possible to dispense with perspective targets altogether and instead rely on the data representation being self-registering. In this case each bit value (or multi-bit value) is typically represented by an explicit glyph, i.e. no bit value is represented by the absence of a glyph. This ensures that the data grid is well-populated, and thus allows the grid to be reliably identified and its perspective distortion detected and subsequently corrected during data sampling. To allow tag boundaries to be detected, each tag data must contain a marker pattern, and these must be redundantly encoded to allow reliable detection. The overhead of such marker patterns is similar to the overhead of explicit perspective targets. One such scheme uses dots positioned a various points relative to grid vertices to represent different glyphs and hence different multi-bit values (see Anoto Technology Description, Anoto April 2000).
[0092] Decoding a tag results in a region ID, a tag ID, and a tag-relative pen transform. Before the tag ID and the tag-relative pen location can be translated into an absolute location within the tagged region, the location of the tag within the region must be known. This is given by a tag map, a function which maps each tag ID in a tagged region to a corresponding location. A tag map reflects the scheme used to tile the surface region with tags, and this can vary according to surface type. When multiple tagged regions share the same tiling scheme and the same tag numbering scheme, they can also share the same tag map. The tag map for a region must be retrievable via the region ID. Thus, given a region ID, a tag ID and a pen transform, the tag map can be retrieved, the tag ID can be translated into an absolute tag location within the region, and the tag-relative pen location can be added to the tag location to yield an absolute pen location within the region.
[0093] The tag ID may have a structure which assists translation through the tag map. It may, for example, encoded cartesian coordinates or polar coordinates, depending on the surface type on which it appears. The tag ID structure is dictated by and known to the tag map, and tag IDs associated with different tag maps may therefore have different structures.
[0094] Two distinct surface coding schemes are of interest, both of which use the tag structure described earlier in this section. The preferred coding scheme uses "location-indicating" tags as already discussed. An alternative coding scheme uses "object-indicating" (or "function-indicating") tags.
[0095] A location-indicating tag contains a tag ID which, when translated through the tag map associated with the tagged region, yields a unique tag location within the region. The tag-relative location of the pen is added to this tag location to yield the location of the pen within the region. This in turn is used to determine the location of the pen relative to a user interface element in the page description associated with the region. Not only is the user interface element itself identified, but a location relative to the user interface element is identified. Location-indicating tags therefore trivially support the capture of an absolute pen path in the zone of a particular user interface element.
[0096] An object-indicating (or function-indicating) tag contains a tag ID which directly identifies a user interface element in the page description associated with the region (or equivalently, a function). All the tags in the zone of the user interface element identify the user interface element, making them all identical and therefore indistinguishable. Object-indicating tags do not, therefore, support the capture of an absolute pen path. They do, however, support the capture of a relative pen path. So long as the position sampling frequency exceeds twice the encountered tag frequency, the displacement from one sampled pen position to the next within a stroke can be unambiguously determined. As an alternative, the netpage pen 101 can contain a pair or motion-sensing accelerometers, as described in our co-pending application U.S. Ser. No. 09/721,893.
[0097] An embodiment of the present invention, in the form of a sensing device for coded surfaces, attachable to a stylus or a marking device such as a pen, pencil or eraser, will now be described. The attachable sensing device is hereinafter referred to as a code sensor attachment or code sensor, as appropriate.
[0098] The code sensor attachment, when attached to an implement such as a stylus or pen, effectively transforms the implement into a netpage stylus or pen. The code sensor attachment senses the force exerted on the surface by the implement's nib, senses the movement of the implement relative to a netpage-encoded surface, and transmits the resulting digital ink to a netpage base station.
[0099] A first embodiment of the present invention will now be described with reference to FIGS. 7, 8, 9, 10, 11, 12 and 13. The code sensor attachment, generally designated by reference numeral 1010, includes a housing 1026, in the form of a plastic molding, which defines an interior space for mounting code sensor components. The housing 1026 also has projecting grip areas 1018 which allow a user to comfortably grip the code sensor. The housing 1026 receives a chassis molding 1032 which in turn receives, via opposed slots, a PCB 1034. A cover 1028 is secured to the end of the housing 1026. The cover 1028 is also of molded plastics, and is formed from semi-transparent material to allow the user to view status LEDs 116 mounted at the end of the PCB 1034. The cover 1028 also provides an aperture for the optics block 135 mounted on the PCB 1034.
[0100] A metal clip 1020 is secured to the housing 1026 at the opposite end to the cover 1028. The clip is held in place by a pre-stressed flexing metal arm 1024 which engages a slot on the underside of the housing 1026. The metal clip 1020 flexibly grips an implement such as a stylus or pen. A rubber pad 1030 is attached to the interior surface of the metal clip 1020, providing a highly frictional and somewhat compressive seat for the held implement. The metal clip 1020 accommodates a range of implement diameters.
[0101] Any number of alternative methods may be used to attach the code sensor to the implement. For example, an elastic weave strap with Velcro fastening; a pivoting or separate clamp plate securable via a nut and bolt assembly; a pair of pivoting and sprung clamp plates; or a jubilee clip arrangement securable via a tightening screw.
[0102] When the code sensor attachment is attached to an implement, the user grips the code sensor by the grip areas 1018, i.e. typically between thumb and forefinger. The projecting grip areas 1018 of the housing 1026 define an interior space large enough to accommodate the implement without contact. The implement, which is held by the metal clip 1020, is allowed to pivot slightly with respect to the housing 1026 when its nib is pressed against a surface, by virtue of the flexibility of the flexing metal arm 1024 of the metal clip 1020. A finger 1022 projecting from the metal clip thereby moves relative to the end of the PCB 1034, where an LED 143 illuminates it and a photodiode 144 captures the intensity of the light it reflects. While the interior of finger's surrounding cavity has low reflectivity, the finger is coated to make it highly diffusely reflective. The intensity of light reflected by the finger gives an indication of the displacement of the finger and thereby gives an indication of the force exerted on the nib. The finger 1022 has a triangular profile so that the reflected light intensity varies linearly with displacement.
[0103] An infrared LED 131, mounted on the PCB 1034, provides infrared illumination of netpage tags on the surface, while an image sensor 132, also mounted on the PCB, images the tags. A radio frequency (RF) chip 133, containing analog RF transceiver components, and a controller chip 134 for controlling operation of the code sensor, are also mounted on the PCB. An optics block 135, formed from molded clear plastics, is mounted on the PCB on top of the infrared illumination LED 131 and the image sensor 132. It projects illumination from the LED 131 onto the surface and projects images of the surface onto the image sensor 132. A replaceable 3V battery 1036 is seated on the PCB. A flash memory 147, containing controller software, identity and configuration information, and a DRAM 148 of typically 512 KB capacity, are also mounted on the PCB.
[0104] The code sensor attachment 1010 of this embodiment of the invention is specifically arranged to detect coded data recorded on a surface for use in sending instructions to a computing system. Such coded data includes location tags printed on the surface in infrared absorptive ink. Each printed location tag includes encoded region identity data which identifies an identity of a region on the surface in which the tag is printed (e.g. if the tag is printed on a sheet of paper this data may identify the sheet of paper), and location data identifying a location of the tag within the region. The location tags also include target structures which allow their detection and enable calculation of the three-dimensional orientation of the pen relative to the surface on which the tag is printed (e.g. tilt with respect to the surface). The tag may also contain various control data.
[0105] The code sensor attachment 1010 is arranged to determine the position of the image sensor 132, and thereby the position of the nib, by imaging, in the infrared spectrum, an area of the surface in the vicinity of the nib. It records the location data from the nearest location tag, and is arranged to calculate the distance of the image sensor 132, and thereby the distance of the nib, from an imaged location tag. The controller chip 134 calculates the orientation of the pen and the nib-to-tag distance from the perspective distortion observed on the imaged tag.
[0106] Control data from the location tag may include control bits instructing the code sensor to activate its "active area" LED (one of the status LEDs 116). Thus, a region on the surface which corresponds to the active area of a button or hyperlink may be encoded to activate this LED, giving the user of the code sensor visual feedback that the button or hyperlink is active when the nib passes over it.
[0107] Movements made relative to a surface with an implement which has an attached code sensor are typically captured as a series of strokes. A stroke consists of a sequence of time-stamped pen positions on the surface, initiated by a pen-down event and completed by a subsequent pen-up event. The pen force can be interpreted relative to a threshold to indicate whether the pen is "up" or "down", or can be interpreted as a continuous value, for example when the pen is capturing a signature. The sequence of captured strokes is hereinafter referred to as "digital ink". Digital ink can be used with a computing system to form the basis for the digital exchange of drawings and handwriting, for on-line recognition of handwriting, and for on-line verification of signatures.
[0108] Utilizing the RF chip 133 and antenna 112 the code sensor can transmit the digital ink data (which is encrypted for security and packaged for efficient transmission) to the computing system.
[0109] When the code sensor is in range of a receiver, the digital ink data is typically transmitted as it is formed. When the code sensor moves out of range, digital ink data is buffered within the code sensor and can be transmitted later. The DRAM 148, if 512 KB, can hold digital ink of approximately 12 minutes' duration.
[0110] The various operations of the code sensor attachment 1010 will now be described in more detail in the following sections.
[0111] As discussed above, the controller chip 134 is mounted on the PCB 1034. FIG. 14 is a block diagram illustrating in more detail the architecture of the controller chip 134. FIG. 14 also shows representations of the RF chip 133, the image sensor 132, the status LEDs 116, the IR illumination LED 131, the force sensor LED 143, and the force sensor photodiode 144.
[0112] The pen controller chip 134 includes a controlling processor 145. Bus 146 enables the exchange of data between components of the controller chip 134. Flash memory 147 and a 512 KB DRAM 148 are also included. An analog-to-digital converter 149 is arranged to convert the analog signal from the force sensor photodiode 144 to a digital signal.
[0113] An image sensor interface 152 interfaces with the image sensor 132. A transceiver controller 153 and baseband circuit 154 are also included to interface with the RF chip 133 which includes an RF circuit 155 and RF resonators and inductors 156 connected to the antenna 112.
[0114] The controlling processor 145 captures and decodes location data from tags from the surface via the image sensor 132, monitors the force sensor photodiode 144, controls the LEDs 116, 131 and 143, and handles short-range radio communication via the radio transceiver 153. It is typically a medium-performance (˜40 MHz) general-purpose RISC processor.
[0115] The processor 145, digital transceiver components (transceiver controller 153 and baseband circuit 154), image sensor interface 152, flash memory 147 and 512 KB DRAM 148 are integrated in a single controller ASIC 134. Analog RF components (RF circuit 155 and RF resonators and inductors 156) are provided in the separate RF chip 133.
[0116] The image sensor is typically a CCD with an approximate resolution of 215×215 pixels (such a sensor is produced by Matsushita Electronic Corporation, and is described in a paper by Itakura, K T Nobusada, N Okusenya, R Nagayoshi, and M Ozaki, "A 1 mm 50 k-Pixel IT CCD Image Sensor for Miniature Camera System", IEEE Transactions on Electronic Devices, Volt 47, number 1, January 2000, which is incorporated herein by reference) with an IR filter. Alternatively, it may be a CMOS image sensor, and may be integrated with the controller ASIC 134.
[0117] The controller ASIC 134 enters a quiescent state after a period of inactivity when the code sensor attachment doesn't detect contact with a surface. It incorporates a dedicated circuit 150 which monitors the force sensor photodiode 144 and wakes up the controller 134 via the power manager 151 on a pen-down event.
[0118] The radio transceiver communicates in the unlicensed 900 MHz band normally used by cordless telephones, or alternatively in the unlicensed 2.4 GHz industrial, scientific and medical (ISM) band, and uses frequency hopping and collision detection to provide interference-free communication.
[0119] As discussed above, the optics are implemented by a molded optics block 135. The optics implemented by the optics block 135 are illustrated schematically in FIG. 15. The optics block comprises a first lens 157 for focusing illumination from the infrared LED 131, a mirror 158, a beam splitter 159, an objective lens 160 and a second lens 161 for focusing an image onto the image sensor 132. Axial rays 162 illustrate the optical path.
[0120] The optical path is designed to deliver a sharp image to the image sensor 132 of that part of the imaged surface which intersects the field of view cone, within required tilt ranges. The primary focusing element is the objective lens 160. This is also used in reverse to project illumination from the IR illumination LED 131 onto the surface within the field of view. Since it is impractical to place both the image sensor 132 and the IR LED 131 at the focus of the objective, a beam splitter 159 is used to split the path and separate relay lenses 157 and 161 in each path provides refocusing at the image sensor 132 and the IR LED 131 respectively. This also allows different apertures to be imposed on the two paths. Alternatively, separate optical paths may be provided for illumination and image capture.
[0121] The edges of the image sensor 132 act as the field stop for the capture field, and the capture path is designed so that the resulting object space angular field of view is as required (i.e. just under 20° for the application of this embodiment--see later). The illumination path is designed to produce the same object space field of view as the capture path, so that the illumination fills the object space field of view with maximum power and uniformity.
[0122] The IR LED 131 is strobed in synchrony with frame capture. The use of focused illumination allows both a short exposure time and a small aperture. The short exposure time prevents motion blur, thus allowing position tag data capture during pen movement. The small aperture allows sufficient depth of field for the full range of surface depths induced by tilt. The capture path includes an explicit aperture stop 191 for this purpose.
[0123] Because the image sensor 132 typically has a strong response throughout the visible and near-infrared part of the spectrum, it is preceded by an infrared filter 163 in the capture path so that it captures a clean image of the tag data on the surface, free from interference from other graphics on the surface which may be printed using inks which are transparent in the near-infrared.
[0124] When the nib is in contact with a surface the code sensor determines its position and orientation relative to the surface at 100 Hz to allow accurate handwriting recognition (see the article by Tappert, C, C Y Suen and T Wakahara, "The State of the Art in On-Line Hand Writing Recognition" IEEE Transactions on Pattern Analysis and Machine Intelligence, Vol 12, number 8, August 1990, the disclosure of which is incorporated herein by reference). The force sensor photodiode 144 is utilized to determine, relative to threshold value, whether the pen is "up" or "down". The force may also be captured as a continuous value, as discussed above, to allow the full dynamics of a signature to be verified, for example.
[0125] The code sensor determines the position and orientation of its nib on the surface by imaging, in the infrared spectrum, an area of the surface in the vicinity of the nib. It decodes the nearest tag data and computes the position of the nib relative to the location tag from the observed perspective distortion on the imaged tag and the calibrated and known geometry of the implement, the attached code sensor, and the code sensor's optical path. Although the position resolution of the tag may be low, the adjusted position resolution is quite high, and easily exceeds the 200 dpi resolution required for accurate handwriting recognition (see above reference).
[0126] As an alternative to locating and decoding tags at the required motion tracking rate (e.g. 100 Hz), it is possible to locate and decode tags at a significantly lower rate (e.g. 10 Hz), and instead use inter-frame correlation techniques to track motion. In this approach, pairs of successively captured frames are compared to identify common patterns and, from their inter-frame displacement, a motion vector. This approach can break down if tilt varies rapidly. It is therefore important to model the rate of change of tilt and to locate and decode tags at a corresponding rate. Alternatively, rapid tilt change can be accommodated within an inter-frame correlation scheme if the scheme actively tracks features such as tag targets from one frame to the next. The advantage of inter-frame correlation techniques is that they are less compute-intensive than full tag decoding. They may also be used with lower-resolution or smaller captured images.
[0127] As mentioned above, movements made relative to a surface with an implement which has an attached code sensor are typically captured as a series of strokes. A stroke consists of a sequence of time-stamped pen positions on the surface, initiated by a pen-down event and completed by the subsequent pen-up event. A stroke is also tagged with the region ID of the surface whenever the region ID changes, i.e. just at the start of the stroke under normal circumstances. As discussed above, each location tag includes data indicative of its position on the surface and also region data indicative of the region of the surface within which the tag lies.
[0128] FIG. 16 is a diagram illustrating location tag and stroke processing in the code sensor. The pen controller 134 starts with an empty stroke (at 164). It then continuously samples (at 165) the nib force via the force sensor photodiode 144, checking for a pen-down state (at 166). If the pen is in a pen-down state, the pen controller 134 captures (at 167) an image of the surface, locates (at 168) a tag in the captured image, decodes (at 169) tag data from the tag, infers (at 170) the pen position and orientation relative to the surface, and appends (at 171) the position data to the current stroke data. On detection of a pen-up event, i.e. on detection (at 172) of a pen-up state after a pen-down state as indicated by the presence of a non-empty stroke, the pen controller 134 encrypts (at 173) the stroke data and transmits (at 174) the stroke data via the RF chip 133 and antenna 112, to the computing system. It then starts with another empty stroke (at 164).
[0129] Assuming a reasonably fast 8 bit multiply (3 cycles), the processing algorithm uses about 80% of the processor's time when the pen is active.
[0130] If the code sensor is out of range of a computing system to transmit to, then it buffers digital ink in its internal memory. It transmits any buffered digital ink when it is next within range of a computing system. When the pen's internal memory is full the pen ceases to capture digital ink and instead flashes its error LED 116 whenever the user attempts to write with the implement which has the code sensor attached.
[0131] FIG. 17 is a diagram illustrating the structure of the raw digital ink transmitted from the code sensor to the computing system. Digital ink which is buffered in the code sensor when it is working offline is stored in the same form as digital ink which is transmitted to the system.
[0132] When the code sensor connects to the computing system, the controller 134 notifies the system of the pen ID, nib ID, current absolute time, and the last absolute time it obtained from the system prior to going offline. This allows the system to compute any drift in the pen's clock and timeshift any digital ink received from the code sensor accordingly. The code sensor then synchronizes its real-time clock with the accurate real-time clock of the system. The pen ID allows the computing system to identify the code sensor when there is more than one pen being operated with the computing system. Pen IDs may be important in systems which use the pen to identify an owner of the pen, for example, and interact with that owner in a particular directed manner. In other embodiments this may not be required. The nib ID allows the computing system to identify which nib is presently being used. The code sensor attachment may include a user interface allowing the user to select a nib color and/or style which matches the characteristics of the implement to which the code sensor is attached. The computing system can vary its operation depending upon which nib is being used. For example, if a marking nib is being used the computing system may defer producing feedback output because immediate feedback is provided by the ink markings made on the surface. When a stylus nib is being used, the computing system may produce immediate feedback output.
[0133] At the start of a stroke the pen controller 134 records the elapsed time since the last absolute time notified to the system. For each pen position in the stroke, in the form of a raw pen position 177, the controller 134 records the x and y offset of the nib from the current tag, the x, y and z rotation of the pen, and the nib force. It only records the tag ID if it has changed, in the form of a tag change 178. Since the tag frequency is significantly smaller than the typical position sampling frequency, the tag ID is constant for many consecutive pen positions, and may be constant for the entire stroke if the stroke is short.
[0134] Since the code sensor samples its position and orientation at 100 Hz, pen positions in a stroke are implicitly clocked at 100 Hz and do not need an explicit timestamp. If the code sensor fails to compute a pen position, e.g. because it fails to decode a tag, it must still record a pen position to preserve the implicit clocking. It therefore records the position as unknown, in the form of an unknown pen position 179, allowing the computing system to later interpolate the position from adjacent samples if necessary.
[0135] Since the 32-bit time offset of a stroke has a finite range (i.e. 49.7 days), the code sensor optionally records an absolute time for a stroke, in the form of a time change 176. This becomes the absolute time relative to which later strokes' time offsets are measured.
[0136] Since the region ID is constant for many consecutive strokes, the pen only records the region ID when it changes, in the form of a region change 180. This becomes the region ID implicitly associated with later pen positions.
[0137] Since a user may change the nib between one stroke and the next, the code sensor optionally records a nib ID for a stroke, in the form of a nib change 175. This becomes the nib ID implicitly associated with later strokes.
[0138] Each component of a stroke has an entropy-coded prefix. A 10 mm stroke of 1 second duration spans two or three tags, contains 100 positions samples, and therefore has a size of about 5500 bits. Online continuous digital ink capture therefore requires a maximum transmission speed of 5.5 Kbps, and offline continuous digital ink capture requires about 40 Kbytes of buffer memory per minute. The code sensor's 512 KB DRAM 48 can therefore hold over 12 minutes of continuous digital ink. Time, region and nib changes happen so infrequently that they have a negligible effect on the required transmission speed and buffer memory. Additional compression of pen positions can reduce transmission speed and buffer memory requirements further.
[0139] Each raw stroke is encrypted using the Triple-DES algorithm (see Schneier, B, Applied Cryptography, Second Edition, Wiley 1996, the disclosure of which is incorporated herein by reference) before being transmitted to the computing system. The pen and computing system exchange session keys for this purpose on a regular basis. Based on a conservative estimate of 50 cycles per encrypted bit, the encryption of a one-second 5500 bit stroke consumes 0.7% of the processor's 45 time.
[0140] The combined geometry of the code sensor attachment and the implement to which it is attached is somewhat constrained by the requirements of the optics. An alignment tool is therefore provided in the form of a base 1110 which simultaneously receives the code sensor attachment 1010 and the implement 1012, allowing the former to be attached to the latter in a controlled manner. The base 1110 is illustrated in FIGS. 18 to 22.
[0141] The base consists of a base molding 1112, a metal pivot shaft 1114, an paired levers each consisting of a grip 1116 and an arm 1118. The paired levers wrap around the pivot shaft 1114 with the arms 1116 projecting inwards to form a guide which marries with the longitudinal slot in the code sensor attachment's metal clamp 1020. The base molding is arranged to receive the code sensor attachment 1010 vertically, guided by the lever arms 1116.
[0142] Once the code sensor attachment is seated in the base, application of force to the lever grips 1118 forces the lever arms 1116 apart, thus opening the metal clamp 1020 and readying it for receiving the implement 1012. When the implement is inserted vertically through the open clamp 1020, it decends until its nib rests on the internal floor of the base molding. The base molding holds the code sensor attachment in a slightly elevated position with respect to the floor, ensuring an ideal distance from the code sensor attachment's optics 135 and the implement's nib.
[0143] Releasing the lever grips 1118 allows the clamp 1020 to close, firmly attaching the code sensor attachment 1010 to the implement 1012. The implement can then be removed from the base, with the code sensor attached, ready to be used.
[0144] The base 1110 helps ensure gross calibration of the code sensor optics. Fine calibration can then be performed as follows. The geometry is as defined in our co-pending application U.S. Ser. No. 09/575,154 (docket no. NPT001US).
[0145] The geometry of a pen can be automatically calibrated by determining how the sensed viewing distance varies with sensed pen orientation. This can be useful when the geometry is not known a priori, such as when the code sensor attachment has just been attached to an implement.
[0146] Assuming a point-like rather than curved nib, the geometry is defined by a three-dimensional vector from the viewpoint to the nib. Assuming, as before, that the optical axis and the nib lie in a known pitch plane, calibration involves sensing the surface at two different pitch values, determining the lines of intersection between the pitch plane and the surface at these pitch angles, and then determining the point of intersection of these lines. The point of intersection is the point of the nib.
[0147] FIG. 23 shows sensor space with the viewpoint E at the origin and the point of the nib A at point (S, D), where D is the viewing distance and S is the distance from the nib to the center of the field of view window at zero pitch.
[0148] Two lines L1 and L2 indicate the surface at different pitch angles θ1 and θ2 respectively.
[0149] Once the surface has been imaged at a particular pitch angle, the pitch angle θ and viewing distance I can be inferred from the imaged tag in the usual way.
[0150] Lines L1 and L2 are then defined by:
z=-y tan θ1+I1
z=-y tan θ2+I2
[0151] Solving for y and z gives the intersection point of the two lines, i.e. the point of the nib:
S=y=(I1-I2)/(tan θ1-tan θ2)
D=z=(I1 tan θ2-I2 tan θ1)/(tan θ1-tan θ2)
[0152] The radius R of a spherical nib can be determined by sensing the surface at three pitch angles rather than two, as described below.
[0153] FIG. 24 shows three lines L1, L2 and L3 indicating the surface at three different pitch angles. L1 and L2 intersect at PA, while L2 and L3 intersect at PB. Line LA starts at PA and has a direction given by the average of the vectors N1 and N2 normal to L1 and L2 respectively. Similarly, line LB starts at PB and has a direction given by the average of the vectors N2 and N3 normal to L2 and L3 respectively. Lines LA and LB intersect at K, the center of the spherical nib. The minimum distance from K to any of lines L1, L2 and L3 gives the desired radius R.
[0154] The convex hull of an arbitrary three-dimensional nib shape can be approximated by sensing the surface at a number of pitch and roll angles. Each pitch, roll and viewing distance triplet uniquely defines a 3D half-space, and the intersection of a collection of such half-spaces approximates the convex hull. The larger the number of orientations at which the surface is sensed, the more closely the intersection approximates the convex hull.
[0155] Because the pitch and roll ranges of the pen are limited, the shape of the nib can only be determined within these ranges. However, since these ranges also define the operating ranges of the pen, they allow the nib shape to be determined to the extent required to model the interaction of the nib with the surface within the operating ranges of the pen. This modeling is what is required to precisely track the motion of the nib, as well as to model the shape of the stroke produced by the nib at various orientations.
[0156] The calibration technique does not allow the shape of a concave nib to be determined. However, cavities in a nib only affect stroke shape, and not nib motion.
[0157] Although the inference of the pen transform as described in the co-pending application U.S. Ser. No. 09/575,154 (docket no. NPT001US) only takes into account a spherical nib, it can be extended trivially to take into account an arbitrary nib shape defined by an exact or approximating polygon.
[0158] After attaching the code sensor attachment, the user calibrates the resulting geometry in conjunction with a special netpage which informs the system that calibration is taking place.
[0159] We turn now to alternative embodiments of the coded data and the code sensor attachment.
[0160] In a first alternative embodiment, the coded data is indicative of an identity which is data identifying the substrate. This enables the code sensor to identify the substrate, such as whether the substrate is a particular type of document or whether the substrate forms part of another object. Of course, since with this embodiment the tags are indicative of the characteristics of the surface and not the location of the tags relative to the surface, separate means are required for sensing movement of the apparatus relative to the surface.
[0161] In a second alternative embodiment, the coded data is indicative of an identity which is data indicative of the tag type. The code sensor can then identify whether the tag represents an object of interest rather than a position on the surface. For example, if the tag represents an object and corresponds to a user interface input element (e.g. a command button), then the tag can directly identify the input element.
[0162] A suitable separate movement sensing means for use with the alternative embodiments includes a pair of orthogonal accelerometers 190 mounted in a plane normal to the code sensor axis. The accelerometers 190 are shown in FIG. 14 in ghost outline.
[0163] The provision of the accelerometers enables this embodiment of the code sensor to sense motion without reference to surface tags, allowing the tags to be sampled at a lower rate.
[0164] The acceleration measured by the accelerometers in each of the X and Y directions is integrated with respect to time to produce an instantaneous velocity and position.
[0165] Since the starting position of the stroke is not known, only relative positions within a stroke are calculated. Although position integration accumulates errors in the sensed acceleration, accelerometers typically have high resolution, and the time duration of a stroke, over which errors accumulate is short.
[0166] Instead of providing accelerometers to sense motion relative to the surface, alternative motion sensing means may be provided. Such means include motion sensing means which includes an optical sensor which cooperates with the surface to generate signals indicative of movement of the optical sensor relative to the surface, motion sensing means which includes at least two contacts arranged to contact the surface and sense movement in two orthogonal directions, or any other suitable motion sensing means for sensing movement relative to a surface.
[0167] The present invention has been described with reference to a preferred embodiment and number of specific alternative embodiments. However, it will be appreciated by those skilled in the relevant fields that a number of other embodiments, differing from those specifically described, will also fall within the spirit and scope of the present invention. Accordingly, it will be understood that the invention is not intended to be limited to the specific embodiments described in the present specification, including documents incorporated by cross-reference as appropriate. The scope of the invention is only limited by the attached claims.
Patent applications by Kia Silverbrook, Balmain AU
Patent applications by Paul Lapstun, Balmain AU
Patent applications by Tobin Allen King, Balmain AU
Patent applications by Silverbrook Research Pty Ltd
Patent applications in class Stylus
Patent applications in all subclasses Stylus
User Contributions:
Comment about this patent or add new information about this topic: