A marking robot

Technical Field

The present invention relates to a robot, and in one particular form, to a mobile or moveable robot that can behave in a particular way in response to the particular surface upon which the robot is placed and the robot's position on that surface, and in another particular form, to a mobile or moveable robot adapted to mark a particular surface.

CO-PENDING APPLICATIONS

Various methods, systems and apparatus relating to the present invention are disclosed in the following co-pending application filed by the applicant or assignee of the present invention simultaneously with the present application: <patcit id="pcit0001" dnum="WO2004077341A"><text>WO 2004077341</text></patcit>.

Background Art

Principles of mobile robotics are described in detail in <nplcit id="ncit0001" npl-type="b"><text>Dudek, G., and M. Jenkin, Computational Principles of Mobile Robotics (Cambridge University Press, 2000</text></nplcit>) and <nplcit id="ncit0002" npl-type="b"><text>Nehmzow, U., Mobile Robotics: A Practical Introduction (Springer Verlag, 2000</text></nplcit>). Practical mobile robot construction is described in detail in <nplcit id="ncit0003" npl-type="b"><text>Wise, E., Applied Robotics (Prompt Publications, 1999</text></nplcit>) and<nplcit id="ncit0004" npl-type="b"><text> McComb, G., The Robot Builder's Bonanza, 2nd Edition (McGraw Hill, 2001</text></nplcit>).

The present invention is not limited to use requiring a netpage. However, a netpage is now described to assist the reader in understanding the nature of the invention. A netpage consists of visible graphic data intended for human interpretation, as well as substantially invisible (or at least inconspicuous) netpage coded data intended for machine interpretation. The netpage coded data identifies, at each of at least a given density of points on the netpage, the identity of the netpage and the two-dimensional coordinates of the point. The given density is typically of the order of a few millimeters. A netpage sensing device incorporates an optical sensor and a decoder for netpage coded data. When placed in a position to sense netpage coded data, the netpage sensing device is able to determine the identity of the netpage and its own position relative to the netpage from a purely local snapshot of the netpage. Whereas the netpage coded data only directly encodes position to a certain precision (e.g. of the order of a few millimeters), the netpage sensing device can determine its position and orientation relative to the netpage to greater precision (e.g. of the order of a few micrometers) based on the alignment, rotation and perspective distortion of the coded data in its field of view.

Note that the distinction in a particular coding pattern between page identity (i.e. netpage id) and point coordinates is merely a functional distinction. An actual coding pattern may utilize any mixture (or hierarchy) of region identifiers and coordinates, ranging from a pure coordinate code where the coordinate space spans a multitude of pages, through to a pure identifier code where a page contains a multitude of identified regions. In the preferred coding, as described above, the coding pattern contains a multitude of identified regions, each containing a range of coordinates, and each conveniently corresponding to the size of a page. Note also that the size of a page is itself not fixed, and may correspond to the size of a sheet of paper (e.g. Letter/A4, Tabloid/A3, etc.), or to the size of the surface of an arbitrary object.

If the scale of the netpage coding pattern is increased (e.g. so that the given point density is of the order of centimeters or decimeters or larger), then the required imaging field of view grows accordingly. However, the precision with which the corresponding netpage sensing device can determine its precision and orientation relative to the netpage is a function of the device's imaging resolution, not the size of its field of view. It is therefore possible, given sufficient resolution, to determine position and orientation to arbitrary precision, independent of the scale of the netpage coding pattern, subject of course to normal optical imaging constraints such as diffraction limit.

A netpage may be printed onto a surface, such as the surface of a sheet of paper, using a netpage printer. Printing may take place in bulk, or on demand. The graphic data is typically printed using visible inks, such as cyan, magenta, yellow and black inks. The coded data is typically printed using an invisible ink such as an infrared-absorptive ink, or using a low-visibility ink.

More generally, the graphic data may be printed or otherwise deposited on or in the surface by any suitable device or process, and the coded data may be printed or otherwise deposited on or in the surface by any suitable process. The two devices and/or processes may be entirely unrelated, and need not operate simultaneously. It is within the scope of the present invention that the pattern of the coded data is represented in any way that allows it to be sensed, e.g. optically, magnetically, chemically, etc.

A netpage disposed on a surface is backed by a description of that netpage stored in a computer system, indexed by the netpage id. When a netpage sensing device interacts with a netpage, the sensing device forwards the details of the interaction to the computer system for interpretation with reference to the stored netpage description. The forwarded details typically include the decoded netpage id and the decoded position of the sensing device relative to the netpage. The details may also consist of a stream of netpage ids and positions. When the netpage sensing device is in the form of a writing implement or stylus, and the stream is therefore representative of motion of the writing implement or stylus relative to the netpage, the stream is referred to as digital ink. The netpage sensing device then typically incorporates a contact sensor, and is configured to begin generating the stream when it comes into contact with the surface, and cease generating the stream when contact with the surface is broken. Each digital ink stream delimited by a contact event and a loss of contact event is referred to as a stroke. The computer system retrieves the netpage description corresponding to the netpage id embedded in the stroke, and interprets the stroke with respect to the semantics of the netpage description. For example, if the netpage description describes a text field with a specific position and extent, the computer system may determine whether the stroke intersects the text field, and if so may interpret the stroke, in conjunction with other strokes similarly assigned to the text field, as handwritten text, and attempt to convert the strokes to a string of identified characters. If the netpage description describes an action zone (also referred to as a hyperlink) with a specific position and extent, the computer system may determine whether the stroke intersects the zone, and if so may interpret the stroke as invoking the action, which may in turn cause the computer system to send a corresponding message to another application associated with the action. Alternatively, a netpage stroke is forwarded directly to an application which is specific to the netpage id embedded in the stroke.

If the netpage sensing device incorporates a marking nib or printing device, then the computer system typically associates digital ink input from the device with the corresponding page by storing the digital ink in a persistent manner, indexed by the netpage id. In this way the digital ink can be reproduced when the page is re-printed, and can be searched.

A netpage sensing device in the form of a stylus and pen is described in co-pending <patcit id="pcit0002" dnum="WO0072230A"><text>PCT application WO 00/72230</text></patcit> entitled "Sensing Device, filed 24 May 2000; and co-pending US application <patcit id="pcit0003" dnum="USSN09721893A"><text>USSN 09/721,893</text></patcit> entitled "Sensing Device", filed 25 November 2000. A netpage sensing device in the form of a viewer is described in co-pending <patcit id="pcit0004" dnum="WO0141046A"><text>PCT application WO 01/41046</text></patcit> entitled "Viewer with Code Sensor", filed 27 November 2000.

Various netpage coding schemes and patterns are described in co-pending <patcit id="pcit0005" dnum="WO0072249A"><text>PCT application WO 00/72249</text></patcit> entitled "Identity-Coded Surface with Reference Points", filed 24 May 2000; co-pending <patcit id="pcit0006" dnum="WO0284473A"><text>PCT application WO 02/84473</text></patcit> entitled "Cyclic Position Codes", filed 11 October 2001; co-pending US application <patcit id="pcit0007" dnum="USSN10309358A"><text>USSN 10/309358</text></patcit> entitled "Rotationally Symmetric Tags", filed 4 December 2002; and Australian Provisional Application <patcit id="pcit0008" dnum="AU2002952259"><text>2002952259</text></patcit> entitled "Methods and Apparatus", filed 25 October 2002.

<patcit id="pcit0009" dnum="US2002158955A"><text>US2002/158955</text></patcit>, for example, describes a floor printer. The printer is robotically controlled and incorporates a marking device. It is described that tracking the location of the floor printer may be optimized by using a magnetic or UV-detectable grid on the floor.

<patcit id="pcit0010" dnum="US6116707A"><text>US6116707</text></patcit>, for example describes a robotic plotting system in which a robotic plotter having a printhead is placed on a substantially flat horizontal surface, upon a recording medium, and is directed across the medium by ranging signals transmitted to the printhead from the periphery of the recording medium.

Disclosure Of Invention

A robot adapted to operate in association with an interface surface having printed thereon coded data indicative of an identity of the interface surface and a plurality of reference points of the interface surface, the robot comprising: <ul id="ul0001" list-style="none"><li>movement means to allow the robot to move over the interface surface;</li><li>a sensing device for sensing at least some of the coded data and for generating indicating data indicative of the identity of the interface surface and a position of the robot on the interface surface;</li><li>communication means for transmitting the indicating data to a computer system running a computer application, and for receiving movement instructions and marking instructions from the computer application; and,</li><li>a marking device adapted to selectively mark the interface surface in response to the movement instructions and marking instructions received from the computer application.</li></ul>

Preferably, the marking device is at least one pen, or the like, attached to or held by the robot.

Alternatively, the marking device is at least one printhead attached to or held by the robot.

Preferably, the marking device is selectively moveable into and out of contact with the interface surface.

Alternatively, a characteristic of the marking device is determinable from a barcode on the marking device.

Preferably, a characteristic of the marking device is determinable from a solid-state memory associated with the marking device.

Alternatively, a characteristic of the marking device is determinable from a hyperlink on the interface surface.

According to another aspect the invention provides a system for marking an interface surface, the system comprising: <ul id="ul0002" list-style="none" compact="compact"><li>the interface surface, having printed thereon coded data indicative of an identity of the interface surface and a plurality of reference points of the interface surface; a robot according to the invention; and,</li><li>a computer system running a computer application, the computer system being in communication with the robot, and the computer application being adapted to receive the indicating data and to transmit movement instructions and marking instructions to the robot.</li></ul>

According to a further aspect the invention provides a method of marking an interface surface, said method comprising: <ul id="ul0003" list-style="none" compact="compact"><li>providing an interface surface having printed thereon coded data indicative of an identity of the interface surface and a plurality of reference points of the interface surface;</li><li>providing a robot according to the invention;</li><li>the robot sensing at least some of the coded data and generating indicating data indicative of the identity of the interface surface and a position of the robot on the interface surface;</li><li>the robot transmitting the indicating data to a computer system running a computer application;</li><li>the robot receiving movement instructions from the computer application;</li><li>the robot receiving marking instructions from the computer application; and</li><li>the robot selectively marking the interface surface.</li></ul>

Preferably, the robot marks the interface surface while stationary or moving.

Brief Description Of Figures

<ul id="ul0004" list-style="none"><li><figref idref="f0001">Figure 1</figref> shows a plan view and two elevations of a mobile robot 230 according to a preferred form of the present invention;</li><li><figref idref="f0002">Figure 2</figref> shows a plan view and two elevations of the internal mechanical structure of the mobile robot 230 of <figref idref="f0001">Figure 1</figref>;</li><li><figref idref="f0003">Figure 3</figref> shows a layout of an interactive printed chess board 250 according to a preferred form of the present invention;</li><li><figref idref="f0004">Figure 4</figref> shows a block diagram of a mobile robot controller 200 and its associated peripherals, according to a preferred form of the present invention;</li><li><figref idref="f0005">Figure 5</figref> shows a communication flow between the mobile robot 230 and associated networked entities; and</li><li><figref idref="f0006">Figure 6</figref> shows an application context class diagram, in UML notation, for a robot control application according to a preferred form of the. present invention.</li></ul>

Modes For Carrying Out The Invention

The following modes are described in order to provide a more precise understanding of the subject matter of the present invention. In the figures, incorporated to illustrate the features of the present invention, like reference numerals are used to identify like parts throughout the figures.

Robot With Code Sensor

A mobile robot is typically an electro-mechanical device incorporating a controller and a steerable propulsion system. It may incorporate sensors for reacting to its environment. For example, it may incorporate one or more contact sensors so that when it bumps into an obstacle it can take remedial action such as reversing and proceeding in a different direction. A more sophisticated mobile robot may have access to a map of its environment, and may navigate from one point to another with reference to the map. It may also create a map of its environment during its explorations, either via its contact sensors, or via a more sophisticated sensory or vision system. Principles of mobile robotics are described in detail in <nplcit id="ncit0005" npl-type="b"><text>Dudek, G., and M. Jenkin, Computational Principles of Mobile Robotics (Cambridge University Press, 2000</text></nplcit>) and <nplcit id="ncit0006" npl-type="b"><text>Nehmzow, U., Mobile Robotics: A Practical Introduction (Springer Verlag, 2000</text></nplcit>), Practical mobile robot construction is described in detail in <nplcit id="ncit0007" npl-type="b"><text>Wise, E., Applied Robotics (Prompt Publications, 1999</text></nplcit>), and <nplcit id="ncit0008" npl-type="b"><text>McComb, G., The Robot Builder's Bonanza (Second Edition, McGraw Hill, 2001</text></nplcit>).

The robot 230, a preferred form of which is illustrated in <figref idref="f0001">Figure 1</figref> and <figref idref="f0002">Figure 2</figref>, is a mobile robot incorporating a differential drive system steered by an on-board controller 200 and is hereinafter refered to as a netpage robot. The drive system includes a pair of DC motors 206, with each motor coupled to a wheel 208 via a gearbox 207. Each motor is controlled by a motor controller 205, such as a discrete or integrated H-bridge to provide direction and braking control, and a pulse-width modulator to provide speed control. The drive system may alternatively utilize a pair of stepper motors 206, in which case each motor controller 205 generates the appropriate pulse sequences to control the speed and direction of its corresponding stepper motor. A castor 209 provides a third point of support for the robot. The robot incorporates a platform 211 to which the motors and gearboxes are attached, and which is itself attached to the robot housing 210 (shown enclosing the robot in <figref idref="f0001">Figure 1</figref> and in outline in <figref idref="f0002">Figure 2</figref>). The platform 211 also supports the main PCB 212 which holds the controller 200 and other electronic components.

The netpage robot has a wireless communications link to a host computer system. It utilizes a radio transceiver 189 (e.g. operating according to a short-range standard such as Bluetooth, or a longer-range standard such as GSM, GPRS or other CDMA variant). Alternatively it may utilize an infrared transceiver (e.g. operating according to the IrDA standard). It is powered by a rechargeable battery 139.

When placed on a netpage, the netpage robot 230 determines, via its in-built netpage sensor, the id 50 of the netpage and its own position (and orientation) 221 relative to the netpage. It then reports this information to the host computer via the communications link. The netpage sensor incorporates infrared illumination LED(s) 131, an area image sensor 132, and optics 135 including an infrared filter, aperture and focussing optics. The robot detects contact with a surface via contact switch 194, or alternatively by successfully sensing and decoding the surface coding pattern.

The robot has a unique id 220 which it communicates to the host and which identifies it uniquely among netpage robots. The robot is responsive to a command 222 from its host to move to a specified position on a specified netpage. When the robot reaches its target position it reports its arrival to the host. Because the robot receives continuous position information from its netpage sensor, it is able to navigate with absolute accuracy, without the cumulative errors which plague odometry systems (due to such things as wheel slip and inaccurate kinematic modelling), and therefore without the need to include more sophisticated position-correction mechanisms.

To allow the robot to move with maximum efficiency, a movement command is usefully specified in terms of a polyline or piece-wise curve. This allows the robot to follow a multi-segment path without slowing to a stop between segments. The robot may also be responsive to overlapped commands, where it is able to receive and buffer one or more new commands before completing a current command. In the case of a polyline, the robot may optionally be instructed to interpolate a smooth curved path through the vertices of the polyline.

Commands to the robot may specify speed, or the robot may be allowed to choose its own speed according to its capabilities and the complexity of the path. If the speed is specified, then the polyline (or piece-wise curve) may contain a number of speed specifications (e.g. at each vertex), which are interpolated by the robot.

The size of the netpage robot may vary from small (e.g. millimeter or centimeter scale) to large (e.g. decimeter or meter scale). The netpage coded data pattern may be scaled to match the scale and intended applications of the robot. However, a single coded data pattern scale may be used across the full range of robot scales.

Page-Driven Robot Behavior

For the purposes of the following discussion, the game of chess is used for illustrative purposes. Note, however, that the principles are general and apply to games other than chess, and to applications beyond games.

The netpage chess board 250, as shown in <figref idref="f0003">Figure 3</figref>, may be pre-made or may be printed on demand using a netpage printer. The board incorporates a playing area 254, consisting of an 8x8 checkerboard pattern, as well as additional areas and controls. When a netpage robot is placed on the netpage chess board, it initially reports its own position and orientation and the netpage id 50 of the netpage chess board to the host computer. The page server 841 on the host computer identifies the chess application associated with the netpage id of the netpage chess board (or associated with a zone of a field embedded in the netpage description associated with the netpage id), and forwards all robot input to the chess application. The host computer also forwards robot control commands from the chess application to the robot. The chess application may be local to the host computer, or may be executing on a different computer on a local-area or wide-area network (e.g. the Internet).

Since chess involves sixteen pieces, the chess application receives sixteen initial position reports from sixteen participating robots. If it receives less than sixteen initial position reports then it can signal an error to the user, e.g. via an audible or printed output. If it receives more than sixteen initial position reports, then it can instruct the redundant robots to move off the chess board. The chess application assigns each robot the role of one of the sixteen chess pieces, and instructs each robot to move to its starting position. The chess application must plan each robot's path to avoid collisions with other robots. For chess, a simple heuristic consists of the following: <ul id="ul0005" list-style="bullet" compact="compact"><li>assign each back-line (i.e. non-pawn) role to the nearest robot</li><li>assign each front-line (i.e. pawn) role to the nearest remaining robot</li><li>move to its starting position any robot not yet in its starting position which has an un-obscured straight-line view of its starting position</li><li>repeat until all pieces are properly positioned or no more pieces can be moved</li><li>move any remaining pieces using two-part moves</li></ul>

Clearly more sophisticated algorithms are possible, many of which result in more rapid positioning.

The user makes a move by picking up a robot and placing it at a new position. The robot reports its new position to the chess application. If the move is the first move of a game then the "color" of the robot determines whether the user has chosen to play as white or black. Each robot ideally incorporates some kind of display 186 to indicate which role it has been assigned (e.g. white queen or black king). The display may be in the form of a small alphanumeric LCD showing an alphanumeric representation of the role, or a monochrome or color bit-mapped LCD or OLED showing an icon of the role. The robot is responsive to a command from the host (i.e. from the chess application via the host) to program the content of the robot's display. The robot may have multiple displays. For example it may have one display on its top and another on its face. Its entire visible surface may be completely covered by one or more displays, allowing a semi-three-dimensional icon to be displayed on the robot

The chess application may chose to position the moved robot more centrally in its square, to allow more uniform navigation of other robots. It may also normalize its orientation, so that it is always facing the opposition. If the move is illegal, or if the user mistakenly moves an opposing piece, then the chess application can issue a spoken warning (e.g. via the robot's speaker 204, display 186, or status LED(s) 116) and reverse the move. If a piece is accidentally placed off the board, then the chess application can once again issue a warning.

The chess application then computes its responding move, and instructs one or more of its robots to move accordingly. Chess-playing algorithms and software are described in detail in <nplcit id="ncit0009" npl-type="b"><text>Pawlak, R.J., Chess Software Sourcebook (Treehaus Books, 1999</text></nplcit>) and <nplcit id="ncit0010" npl-type="b"><text>Heinz, E.A, Scalable Search in Computer Chess: Algorithmic Enhancements and Experiments at High Search Depths (Morgan Kaufmann, 1999</text></nplcit>).

The user can also play against a remote human opponent, in which case each local move by the user is tracked by the chess application, and is mirrored, under chess application control, by the corresponding remote piece.

In the case of pieces which are allowed to move despite being hemmed in, such as knights, or pieces which are allowed to move diagonally, such as bishops and queens, the chess application may temporarily move offending robots out of the way, irrespective of their color. It may also temporarily move robots off the playing area 254, e.g. during castling. The chess application maintains a map of the chess board for navigation purposes. This may be the same map it uses for game-playing purposes, or separate from it. When the user captures an opposing piece s/he simply places the piece off the playing area. When the chess application captures an opposing piece (i.e. one of the user's pieces), it instructs the piece to move off the playing area. The chess board includes an area 251 for out-of-play pieces of each color. The chess application can automatically move a piece captured by the user to the out-of-play area, irrespective of where on the board the user places the piece after capture. If the chess board is upset and some pieces lose their places, then the chess application can automatically return each piece to its proper place. Alternatively the chess board can include a &lt;resume&gt; zone (not shown) which, when activated by the user with a piece (or other netpage sensing device), can instruct the chess application to return each piece to its proper place. To allow the user to resign, the chess board includes a &lt;resign&gt; zone 253 which, when activated by the user with a piece (or other netpage sensing device), or specifically with the resigning king, signals the chess application that the user is resigning. The chess application signals that it is resigning by moving its king off the playing area, or specifically to its own &lt;resign&gt; zone. The board also includes a &lt;new game&gt; zone 252 which, when activated by the user with a piece (or other netpage sensing device), signals the chess application to abandon the current game and set up a new game. There may be multiple &lt;new game&gt; zones corresponding to different levels of game-play by the chess application, e.g. ranging from beginner through intermediate to advanced.

When a pawn reaches the opposing back line and is transformed into a queen, the chess application reassigns the role of the robot, and updates the robot's display(s) accordingly.

The netpage robot bay holds a number of netpage robots. The surface of the bay is netpage position-coded to allow robots to navigate into and within the bay under host control. The bay incorporates a netpage sensor which allows it to detect when and where it is placed on a netpage, and a communications link to the host computer which allows it to report the id of the netpage it is placed on and its own position and orientation relative to the netpage. When the bay is placed on a netpage on which one or more netpage robots are located, the host computer can automatically instruct the robots to enter the bay. To this end the bay has a gentle ramp at its entry which a netpage robot is able to navigate. The chess board (or bay, or both) may also include a &lt;gather&gt; zone which, when activated by the user with a piece (or other netpage sensing device), signals the host to gather the robots in the bay.

The netpage robot bay incorporates a battery charging circuit for re-charging the batteries of the robots in the bay. The bay has an external power connection, and may incorporate a larger storage battery for offline operation. A robot may be automatically re-charged in the bay, or may re-charge in response to a re-charge instruction from the host.

The netpage robot may additionally incorporate a directional contact sensor, allowing it to detect and report to the host the presence of any unexpected obstacles. Such obstacles are "netpage-invisible" if they do not themselves incorporate netpage sensors or do not report their presence (and position) to the host. Any netpage robot is by definition netpage-visible and can therefore not become an unexpected obstruction.

To support games such as checkers which allow pieces to be stacked, the netpage robot is designed to be stacked. To this end its top surface is surrounded by a rim which is designed to mate with the undercarriage of another robot (this detail is not included in <figref idref="f0001">Figure 1</figref> and <figref idref="f0002">Figure 2</figref>).

To support games such as checkers and go which only involve two kinds of pieces, the netpage robot may incorporate a simpler display or indicator system (such as an LED or a two-color LED), which can indicate which of the two roles the robot has been assigned.

There are many alternatives to the architecture described above, i.e. where a host computer mediates communication between robots and a (possibly remote) chess application. For example, one of the robots may be automatically designated as the master robot for the duration of the game (or longer), and may download the chess application for execution on its embedded processor. In this case the master robot controls the slave robots. As another example, the robots may act as peers, and may each download the chess application (or parts of it) and execute it collaboratively, communicating directly among themselves.

The key feature of the netpage robot system architecture is that the behavior of a collection of one or more robots derives from the particular netpage on which they are placed. When placed on a chess board the robots behave as chess pieces; when placed on a checkers board they behave as checkers pieces; etc. This is enabled by the netpage id (either directly or indirectly) identifying the application, the application controlling the robots (either remotely or embedded), and the robots navigating absolutely using the netpage position coding.

Marking Robot

The netpage robot may incorporate a marking device for marking a surface such as a paper surface. The marking device is under robot control, so that the robot can turn marking on and off in a position-dependent way. This may be effected using a digitally-controlled marking device 195 such as a Memjet^™ printhead, or with a more traditional pen which can be moved into contact with the surface under robot control. The robot can support multiple colors via a multi-color printhead, or via multiple printheads, or via multiple colored pens. Suitable linear printheads are described in co-pending <patcit id="pcit0011" dnum="WO0189839A"><text>PCT applications WO 01/89839</text></patcit> entitled "Ink Jet Printhead Having a Moving Nozzle with an Externally Arranged Actuator", filed 19 October 2001, <patcit id="pcit0012" dnum="WO0189844A"><text>WO 01/89844</text></patcit> entitled "Ink Jet Printhead Nozzle Array", filed 24 May 2000. Suitable circular printheads are described in co-pending <patcit id="pcit0013" dnum="WO0234531A"><text>PCT application WO 02/34531</text></patcit> entitled "Printhead for Pen", filed 19 October 2001.

Multiple robots can also be used, each carrying a differently-colored pen. These can be controlled sequentially or simultaneously to draw different parts of a multi-colored drawing.

When the user inserts a new pen cartridge into a robot, the robot may automatically determine the color of the pen by decoding a barcode on the surface of the cartridge, or by reading a value from a solid-state memory embedded in the cartridge. Alternatively, the user may activate a color-coded netpage hyperlink using the robot (or other netpage sensing device), thus notififying the computer system and/or corresponding application of the robot's new pen color. A palette of such color-coded hyperlinks may be provided on a separate general-purpose netpage or may be incorporated into the design of an application-specific netpage.

The marking robot may incorporate one or more printheads with a significant width, e.g. of the order of the diameter of the robot itself (as shown in <figref idref="f0002">Figure 2</figref>). This allows the robot to draw lines with subtle structure, such as varying width and varying color texture. It also allows the robot to operate in raster mode, as opposed to (or in addition to) the vector mode described so far. In raster mode the robot can transfer a two-dimensional image to a surface in a single sweep, or build up a larger image in multiple sweeps. The source image may be a bit-mapped image such as a photograph, or it may be a set of vector strokes, e.g. corresponding to handwritten text. Reproducing handwritten text in raster mode may be significantly faster than reproducing it in vector mode, particularly if the height of the text is less than the width of the printhead(s). In raster mode the computer system (or the robot) keeps track of exactly which parts of the source image have been transferred to the surface, allowing the robot to transfer the image to the surface without gaps or overlaps between successive sweeps.

The marking robot, in addition to being responsive a command from its host to move to a specified position on a specified netpage, is also responsive to a command from its host to draw a line of a specified color while moving to the target position. As before, the host mediates communication between the robot and an application which is specific to the netpage (or netpage region) on which the marking robot is placed. The host may hide the drawing functions of the robot behind a line-drawing interface which it presents to the application. The application is then unaware of how the drawing functions are implemented. The robot may directly support the drawing of curved lines, i.e. during movement along curved paths, or the application (or host) may approximate curved lines by instructing the robot to draw a succession of shorter straight-line segments.

The line-drawing interface, or the robot itself, may be responsive to PostScript drawing commands (refer to Adobe Systems Incorporated, <nplcit id="ncit0011" npl-type="b"><text>PostScript Language Reference (3rd Edition, Addision-Wesley 1999</text></nplcit>).

When the marking robot marks a netpage, the markings persist as part of the netpage in the usual way. In this way they become persistent, reproducible, and searchable.

Applications of the marking robot include (but are not limited to): pure plotting of drawings, particularly where it is impractical for the user to utilize a large-format printer, but it is practical for the user to obtain a large-format pre-netpage-coded "blank"; collaborative markup, where each participant's contribution, typically hand-drawn or handwritten with a netpage pen, is robotically mirrored on each of the other participants' "work-in-progress" netpages; and system feedback in the absence of a page-oriented printer.

Remote Conferencing And Collaborative Markup

As described in the context of the chess application, when the user places one or more robots on a collaborative markup netpage the corresponding collaborative markup application can automatically assign each of the robots to represent one of the remote collaborative participants. If names, icons and/or photos representing the participants are available, then this information can be displayed on the robots. In the limit case, each robot's display can act as a video conferencing display for the remote participant it represents, i.e. continuously displaying video of the remote participant captured remotely via a video camera and transmitted over the network. The robot may also usefully incorporate a speaker 204 for relaying the remote participant's voice, and a microphone 201 for capturing voice input. The microphone may also be provided separately, e.g, attached to the host computer (or to the relay - see below).

A remote conferencing netpage application is described in co-pending <patcit id="pcit0014" dnum="WO0102940A"><text>PCT application WO 01/02940</text></patcit> entitled "Method and System for Conferencing", filed 30 June 2000. A collaborative document markup netpage application is described in co-pending <patcit id="pcit0015" dnum="WO0102939A"><text>PCT application WO 01/02939</text></patcit> entitled "Method and System for Collaborative Document Markup", filed 30 June 2000.

Mirroring Robot Movement

In the same way that a netpage robot can mirror the movement of a remote user's netpage pen, a robot can mirror the movement of a remote robot. The remote robot may be under direct or indirect user control, i.e. it may be being moved by the user's own hand, or it may be being moved under interactive computer control. For example, in an interactive tank game being played by multiple remote participants, each user may control their local tank via a graphical user interface on a PC. The tank may include a video camera for capturing a tank's-eye view of the game environment, and the video can be shown on the user's PC display together with various tank navigation controls. Alternatively the video can be shown on a conventional television set receiving the video wirelessly from the tank, independently of the computer system. In this case the user can also control the tank via a printed netpage tank control user interface and a netpage stylus, i.e. without any direct interaction between the user and a PC.

Each user may have an additional local tank robot representing each remote user's tank. Each such tank simply mirrors the corresponding remote tank's movements, under the control of the network-resident tank game application.

The robots may have a game-specific shape (such as the shape of a tank), or may be generic. They may also be general-purpose robots which can be inserted into low-cost game-specific bodies (e.g. tanks) for the purposes of specific games.

Motion Recording And Playback

As mentioned above, a user may directly move a robot, i.e. by hand, and have the movement mirrored by a remote robot. The user may also instruct a robot to record a hand-specified movement, and then have the robot replay the recorded movement. Recording (and playback) may be initiated by depressing a button on the robot, or by providing a control input through some other interface, such as by designating a &lt;record&gt; zone (or &lt;playback&gt; zone) on a netpage with a netpage sensing device (including the robot itself), or by specifying a command by other means, such as keyboard or mouse input to a computer system.

Motion recording and playback may be provided as a generic function of the host computer system, or may be provided by specific applications. In either case recording and playback rely on already described mechanisms. Hand-specified motion may optionally be subject to smoothing by the computer system before playback, and a robot may also be instructed to follow a path at a different speed to the varying speed associated with the original hand-specified motion.

Robotic Viewer

A netpage viewer is a device which, when placed on a netpage, provides a registered interactive view of elements of the page underlying the viewer. The viewer incorporates a netpage sensor for determining its own position and orientation relative to the netpage, and to allow it to obtain interactive content specific to the page from the netpage system. A netpage viewer is described in co-pending <patcit id="pcit0016" dnum="WO0141046A"><text>PCT application WO 01/41046</text></patcit> entitled "Viewer with Code Sensor", filed 27 November 2000. A netpage viewer incorporating a printer is described in co-pending <patcit id="pcit0017" dnum="WO0141045A"><text>PCT application WO 01/41045</text></patcit> entitled "Viewer with Code Sensor and Printer", filed 27 November 2000.

A netpage viewer is usefully augmented with robotic capabilities, to allow the viewer to mirror movement of a remote viewer, or to allow the viewer to display remote netpage pen input on its display, wherever the input may appear on the page. The robotic netpage viewer will move to the area of the page where input is occurring, to allow the input to be displayed in registered fashion. This is particularly useful in a collaborative markup context as described above. The user may at any time move the viwer to a different part of the page to view earlier markup. If the viewer incorporates a printer, then remote (and local) markup can be simultaneously (and persistently) transferred to the underlying physical page.

Robot Controller

<figref idref="f0004">Figure 4</figref> shows a block diagram of the robot controller 200 and its associated peripherals. The integrated controller chip incorporates a processor 145 connected to a number of other components via a shared bus 146, including a working memory 148 (such as an SRAM). An off-chip non-volatile memory 147 (such as a flash memory) holds the fixed robot program and other persistent data. The controller includes a parallel interface for controlling the motor controllers 205, status LED(s) 116, and illumination LED(s) 131, and for sensing the optional contact switch 194. It includes a serial interface for communicating with a host computer (and/or other robots) via the radio transceiver 189, and for controlling the optional printhead 195. It includes an image sensor interface 152 for the netpage sensor's image sensor 132, an optional display interface 185 for the display 186, an optional ADC 202 for the microphone 201, and an optional DAC 203 for the speaker 204.

Robot Communication Flow

<figref idref="f0005">Figure 5</figref> shows a possible communication flow between a netpage robot 230 and associated networked entities in the context of the netpage system.

When the robot is placed on a netpage, its goal is to notify its presence to a corresponding robot control application 804, and begin receiving commands from the application. The robot typically has short-range wireless connectivity with a relay device 44, which itself typically has longer-range network connectivity to netpage system servers via wired LAN, WAN or a longer-range wireless link. The relay device may be a mobile phone, as described in co-pending <patcit id="pcit0018" dnum="WO0072286A"><text>PCT application WO 00/72286</text></patcit> entitled "Relay Device", filed 24 May 2000; an interactive netpage printer, as described in co-pending <patcit id="pcit0019" dnum="WO0242894A"><text>PCT application WO 02/42894</text></patcit> entitled "Interactive Printer", filed 26 November 2001; etc.

The robot transmits its initial position report to the relay, including its robot id 220, the netpage id 50 of the page on which it finds itself, and its position (and orientation) 221 on the page. The relay is able to determine, with reference to one or more id servers 12, the server id 53 of the page server 841 which "owns" the page description of the page. Alternatively, the robot may itself be able to determine the server id 53 from the id server(s) 12, transparently via the relay 44. The robot may also implicitly incorporate the relay function if it has its own longer-range network connectivity.

The relay (or robot) then forwards the position report to the page server 841. The page server in turn determines which application 804 to forward the position report to. In the general netpage scheme, this consists of hit-testing the robot position against the various interactive elements embedded in the description of the page. For the purposes of robot control, all robot movement is usefully forwarded directly to the application without further interpretation by the page server. It is also possible to dispense with the page server entirely, and forward a robot position report directly from the robot (or relay) to an application as identified by the id server(s),or even as identified directly by the page id 50 embedded in the original page. Note that while the ids used in the netpage system are typically described as "pure" ids which do not support routing per se, it is also possible, for example, for these ids to be partial or complete Internet Protocol (IP) addresses, either in 32-bit (IPv4) or 128-bit (IPv6) form, thus directly supporting routing.

The application 804 eventually receives the robot position report by one of these mechanisms, and then interprets the position report with reference to the layout and semantics of the page identified by the page id 50. Since the application may be specific to a particular page layout (e.g. to the chess board), it may be able to assume the layout and simply use the page id to index a particular instance (e.g. a particular in-progress chess game). The application is then able to send commands 222 directly (or indirectly) to the robot, and receive further position input from the robot.

As mentioned earlier, there are many possible variations on this architecture, including downloading application logic into one or more robots, and distributed peer-to-peer robot control.

Application Context Class Diagram

<figref idref="f0006">Figure 6</figref> shows a generic application context class diagram, in UML notation, for a robot control application. The overall context 260 (e.g. corresponding to the chess application) includes a number of individual instances 261 (e.g. corresponding to individual chess games), each of which includes a number of robot roles 262 (e.g. corresponding to individual chess pieces' roles). The context also includes a number of known robots 263, each of which may optionally have been assigned a role 262. Each instance 261 is indentified by an instance id 265. The instance id may correspond to the netpage id of the corresponding page, or may correspond to a transaction id, embedded in the page description of the corresponding page, which gets forwarded to the application during robot interactions. Each role 262 is identified by a role id 266, and has a status 267 (e.g. indicating whether a chess piece is still in play or has been captured). Each robot 263 is identified by a robot id 220, i.e. the robot id of the corresponding physical robot 230, and a current position 269 derived from the most recent position 221 reported by the robot.