Patent Description:
Automated or robotic power tools such as robotic lawnmowers are becoming increasingly more popular. In a typical deployment a work area, such as a garden, the work area is enclosed by a boundary with the purpose of keeping the robotic lawnmower inside the work area. Alternatively or additionally to the boundary wire, many robotic work tools are arranged to operate and navigate using a satellite navigations system, such as GNSS or GPS. The robotic work tool may also or alternatively be arranged to operate or navigate utilizing a beacon-based navigation system, such as UWB, or through combined systems such as RTK.

<FIG> shows a schematic view of an example of a typical work area <NUM>, being a garden, in which a robotic work tool <NUM>, such as a robotic lawnmower, is set to operate.

The garden contains a number of obstacles, exemplified herein by a number (<NUM>) of trees (T), a stone (S) and a house structure (H). The trees are marked both with respect to their trunks (filled lines) and the extension of their foliage (dashed lines). The garden is enclosed by a boundary wire <NUM> through which a control signal <NUM> is transmitted by a signal generator <NUM> housed in a charging station <NUM>, the control signal <NUM> generating a magnetic field that can be sensed by the robotic work tool <NUM>. The garden may also comprise or be in the line of sight of at least one signal navigation device such as a beacon(s) or a satellite(s) (not explicitly shown in <FIG>, but shown and referenced <NUM> in <FIG>).

The use of satellite and/or beacon navigation (as examples of signal navigation) enables for a boundary that is virtual, in addition to or as an alternative to the boundary wire <NUM>. A virtual boundary <NUM>' is indicated in <FIG> by the dotted line. From hereon there will be made no difference between the boundary being defined by the boundary wire <NUM> or as a virtual boundary <NUM>' and the boundary of the work area <NUM> will hereafter simply be referred to as the boundary <NUM>, unless otherwise specifically mentioned.

It is widely recognized that since the magnetic boundary is physical it is regarded as being a more sae alternative, and one that does not require any virtual maps to be made of a work area. In many situations a wire-based boundary is therefore preferred.

In the example of <FIG>, there is a further or second work area 105B - as opposed to the first work area 105A. This work area is also bounded by boundary 120B. The second boundary 120B may be provided through a boundary wire, or through a beacon or satellites.

As most beacons have a limited range, and as most boundary-based systems also have a limited size, it is known to enlarge a work area, by using two work area 105A and 105B, the two thus forming a larger work area <NUM>. This also allows for one and the same (set of) robotic work tool(s) to operate in two different work areas.

Therefore a second work area 105B is shown in <FIG>.

However, in prior art solutions, there are problems in how the robotic work tool crosses from one area to another. For boundary wire based systems, it is basically only possible to cross if the control signals <NUM> used in both systems are the same so that the robotic work tool does not sense the crossing. This also requires that the two adjacent work areas are side-by-side.

If not, the robotic work tool will prevent itself from crossing the boundary as is indicated in <FIG>, by the robotic work tool <NUM> stopping by the boundary 120A.

<FIG> shows a similar situation, but for overlapping work areas, where the overlap is referenced 105A/B. Here, a robotic work tool <NUM> may even get stuck in the overlapping area 105A/B as it has to cross a boundary wire to get out of it, which it will prevent itself from doing.

The patent document published as <CIT> discloses a robotic working tool system comprising a signal generator a robotic work tool, the signal generator including a signal pick-up and a controller, the controller being configured to receive information from the signal pick- up sensor, the information indicating an environment; determine a control signal to be used based on the information indicating the environment; cause the selected control signal to be generated and transmitted to the robotic work tool for controlling the operation of the robotic work tool.

Thus, there is a need for an improved manner of enabling a robotic work tool to easily operate in multiple work areas <NUM>.

It is therefore an object of the teachings of this application to overcome or at least reduce those problems by providing a robotic work tool system as defined by appended claim <NUM>.

In some embodiments the controller is further configured to travel along a transport path to the crossing zone.

In some embodiments the crossing zone is located in the second work area.

In some embodiments the controller is further configured to travel along a transport path from the crossing zone into the second work area.

In some embodiments the controller is further configured to travel along the transport path from the crossing zone to a second crossing zone in the second work area.

In some embodiments the controller is further configured to operate in a transport mode while travelling along the transport path.

In some embodiments the controller is further configured to determine that the robotic work tool is in the crossing zone based on a position of the robotic work tool and a known location of the crossing zone.

In some embodiments the controller is further configured to determine that the robotic work tool is in the crossing zone based on a sensing of the first boundary and/or the second boundary.

In some embodiments the crossing zone is in range of the beacon.

In some embodiments there is a first crossing zone in the first work area and a second crossing zone in the second work area, wherein the first crossing zone in the first work area is connected to the second crossing zone in the second work area by a transport path.

In some embodiments the robotic work tool further comprises a satellite signal navigation sensor and wherein the controller is configured to travel along the transport path connecting the first crossing zone in the first work area and the second crossing zone in the second work area navigating based on satellite navigation.

In some embodiments the robotic work tool is configured to ignore the second boundary when operating in the first domain mode.

In some embodiments the robotic work tool is configured to ignore the first boundary when operating in the second domain mode.

In some embodiments the robotic work tool is configured for operating in a work area comprising an uneven surface, where objects are of a similar appearance to the surface and/or overhanging obstacles.

In some embodiments the robotic work tool is a robotic lawnmower.

It is also an object of the teachings of this application to overcome the problems by providing a method for use in a robotic work tool system as defined by appended claim <NUM>.

Other features and advantages of the disclosed embodiments will appear from the following detailed disclosure, from the attached dependent claims as well as from the drawings. All references to "a/an/the [element, device, component, means, step, etc.]" are to be interpreted openly as referring to at least one instance of the element, device, component, means, step, etc., unless explicitly stated otherwise.

The invention will be described in further detail under reference to the accompanying drawings in which:.

The disclosed embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which certain embodiments of the invention are shown. Like reference numbers refer to like elements throughout.

It should be noted that even though the description given herein will be focused on robotic lawnmowers, the teachings herein may also be applied to, robotic ball collectors, robotic mine sweepers, robotic farming equipment, or other robotic work tools where a work tool is to be safeguarded against from accidentally extending beyond or too close to the edge of the robotic work tool.

<FIG> shows a perspective view of a robotic work tool <NUM>, here exemplified by a robotic lawnmower <NUM>, having a body <NUM> and a plurality of wheels <NUM> (only one side is shown). The robotic work tool <NUM> may be a multi-chassis type or a mono-chassis type (as in <FIG>). A multi-chassis type comprises more than one main body parts that are movable with respect to one another. A mono-chassis type comprises only one main body part.

It should be noted that even though the description herein is focussed on the example of a robotic lawnmower, the teachings may equally be applied to other types of robotic work tools, such as robotic floor grinders, robotic floor cleaners to mention a few examples where a work tool should be kept away from the edges for safety or convenience concerns.

It should also be noted that the robotic work tool is a self-propelled robotic work tool, capable of autonomous navigation within a work area, where the robotic work tool propels itself across or around the work area in a pattern (random or predetermined).

<FIG> shows a schematic overview of the robotic work tool <NUM>, also exemplified here by a robotic lawnmower <NUM>. In this example embodiment the robotic lawnmower <NUM> is of a mono-chassis type, having a main body part <NUM>. The main body part <NUM> substantially houses all components of the robotic lawnmower <NUM>. The robotic lawnmower <NUM> has a plurality of wheels <NUM>. In the exemplary embodiment of <FIG> the robotic lawnmower <NUM> has four wheels <NUM>, two front wheels and two rear wheels. At least some of the wheels <NUM> are drivably connected to at least one electric motor <NUM>. It should be noted that even if the description herein is focused on electric motors, combustion engines may alternatively be used, possibly in combination with an electric motor. In the example of <FIG>, each of the wheels <NUM> is connected to a common or to a respective electric motor <NUM> for driving the wheels <NUM> to navigate the robotic lawnmower <NUM> in different manners. The wheels, the motor <NUM> and possibly the battery <NUM> are thus examples of components making up a propulsion device. By controlling the motors <NUM>, the propulsion device may be controlled to propel the robotic lawnmower <NUM> in a desired manner, and the propulsion device will therefore be seen as synonymous with the motor(s) <NUM>.

The robotic lawnmower <NUM> also comprises a controller <NUM> and a computer readable storage medium or memory <NUM>. The controller <NUM> may be implemented using instructions that enable hardware functionality, for example, by using executable computer program instructions in a general-purpose or special-purpose processor that may be stored on the memory <NUM> to be executed by such a processor. The controller <NUM> is configured to read instructions from the memory <NUM> and execute these instructions to control the operation of the robotic lawnmower <NUM> including, but not being limited to, the propulsion and navigation of the robotic lawnmower.

The controller <NUM> in combination with the electric motor <NUM> and the wheels <NUM> forms the base of a navigation system (possibly comprising further components) for the robotic lawnmower, enabling it to be self-propelled as discussed under <FIG>,.

The controller <NUM> may be implemented using any suitable, available processor or Programmable Logic Circuit (PLC). The memory <NUM> may be implemented using any commonly known technology for computer-readable memories such as ROM, RAM, SRAM, DRAM, FLASH, DDR, SDRAM or some other memory technology. The robotic lawnmower <NUM> may further be arranged with a wireless communication interface <NUM> for communicating with other devices, such as a server, a personal computer or smartphone, the charging station, and/or other robotic work tools. Examples of such wireless communication devices are Bluetooth®, WiFi® (IEEE802. <NUM>1b), Global System Mobile (GSM) and LTE (Long Term Evolution), to name a few.

The robotic lawnmower <NUM> also comprises a grass cutting device <NUM>, such as a rotating blade <NUM> driven by a cutter motor <NUM>. The grass cutting device being an example of a work tool <NUM> for a robotic work tool <NUM>. As a skilled person would understand the cutter motor <NUM> is accompanied or supplemented by various other components, such as a drive shaft to enable the driving of the grass cutting device, taken to be understood as included in the cutter motor <NUM>. The cutter motor <NUM> will therefore be seen as representing a cutting assembly <NUM> or in the case of another work tool, a work tool assembly <NUM>.

The robotic lawnmower <NUM> further comprises at least one (signal) navigation sensor, such as an optical navigation sensor, an ultrasound sensor, a beacon navigation sensor and/or a satellite navigation sensor <NUM>. The optical navigation sensor may be a camera-based sensor and/or a laser-based sensor. The beacon navigation sensor may be a Radio Frequency receiver, such as an Ultra Wide Band (UWB) receiver or sensor, configured to receive signals from a Radio Frequency beacon, such as a UWB beacon. Alternatively or additionally, the beacon navigation sensor may be an optical receiver configured to receive signals from an optical beacon. The satellite navigation sensor may be a GPS (Global Positioning System) device or other Global Navigation Satellite System (GNSS) device. In embodiments, where the robotic lawnmower <NUM> is arranged with a navigation sensor, the magnetic sensors <NUM> as will be discussed below are optional. In embodiments relying (at least partially) on a navigation sensor, the work area may be specified as a virtual work area in a map application stored in the memory <NUM> of the robotic lawnmower <NUM>. The virtual work area may be defined by a virtual boundary.

In the examples that will be discussed herein the navigation sensor is a satellite navigation sensor, such as GPS, GNSS or a supplemental satellite navigation sensor such as RTK.

The robotic lawnmower <NUM> also comprises deduced reckoning sensors <NUM>. The deduced reckoning sensors may be odometers, accelerometer or other deduced reckoning sensors. In some embodiments, the deduced reckoning sensors are comprised in the propulsion device, wherein a deduced reckoning navigation may be provided by knowing the current supplied to a motor and the time the current is supplied, which will give an indication of the speed and thereby distance for the corresponding wheel.

For enabling the robotic lawnmower <NUM> to navigate with reference to a boundary wire emitting a magnetic field caused by a control signal transmitted through the boundary wire, the robotic lawnmower <NUM> is, in some embodiments, further configured to have at least one magnetic field sensor <NUM> arranged to detect the magnetic field and for detecting the boundary wire and/or for receiving (and possibly also sending) information to/from a signal generator (will be discussed with reference to <FIG>). In some embodiments, the sensors <NUM> may be connected to the controller <NUM>, possibly via filters and an amplifier, and the controller <NUM> may be configured to process and evaluate any signals received from the sensors <NUM>. The sensor signals are caused by the magnetic field being generated by the control signal being transmitted through the boundary wire. This enables the controller <NUM> to determine whether the robotic lawnmower <NUM> is close to or crossing the boundary wire, or inside or outside an area enclosed by the boundary wire.

In some embodiments, the robotic lawnmower <NUM> is arranged to operate according to a map of the work area <NUM>, <NUM> (and possibly the surroundings of the work area <NUM>) (referenced <NUM> in <FIG> and onwards) stored in the memory <NUM> of the robotic lawnmower <NUM>. The map may be generated or supplemented as the robotic lawnmower <NUM> operates or otherwise moves around in the work area <NUM>, <NUM>.

<FIG> shows a robotic work tool system <NUM> in some embodiments. The schematic view is not to scale. The robotic work tool system <NUM> of <FIG>, corresponds in many aspects to the robotic work tool system <NUM> of <FIG>, except that the robotic work tool system <NUM> of <FIG> comprises a robotic work tool <NUM> according to the teachings herein. It should be noted that the work area shown in <FIG> is simplified for illustrative purposes but may contain some or all of the features of the work area of <FIG>, and even other and/or further features as will be hinted at below.

As with <FIG>, the robotic work tool is exemplified by a robotic lawnmower, whereby the robotic work tool system may be a robotic lawnmower system or a system comprising a combinations of robotic work tools, one being a robotic lawnmower, but the teachings herein may also be applied to other robotic work tools adapted to operate within a work area.

The robotic work tool system <NUM> comprises a first work area 305A and a second work area 305B. In some embodiments, the work areas have a charging station <NUM> which in some embodiments is arranged with a signal generator (not shown explicitly but seen as part of the charging station and referenced <NUM>) for providing a control signal (not shown explicitly but seen as part of the charging station and referenced <NUM>) through a boundary wire <NUM>.

The robotic work tool system <NUM> may comprise or be arranged to utilize at least one signal navigation device <NUM>. In the example of <FIG> two options are shown, a first being at least one satellite <NUM> (only one shown, but it should be clear that a minimum of three are needed for an accurate three <NUM> dimensional location). The second option being at least one beacon, such as an RTK base station (or beacon) or a UWB beacon <NUM>'A, <NUM>'B (only one shown for each work area).

The work area <NUM> is in this application exemplified as a garden, but can also be other work areas as would be understood. As hinted at above, the garden may contain a number of obstacles, for example a number of trees, stones, slopes and houses or other structures.

In some embodiments the robotic work tool is arranged or configured to traverse and operate in a work area that is not essentially flat, but contains terrain that is of varying altitude, such as undulating, comprising hills or slopes or such. The ground of such terrain is not flat and it is not straightforward how to determine an angle between a sensor mounted on the robotic work tool and the ground. The robotic work tool is also or alternatively arranged or configured to traverse and operate in a work area that contains obstacles that are not easily discerned from the ground. Examples of such are grass or moss covered rocks, roots or other obstacles that are close to ground and of a similar colour or texture as the ground. The robotic work tool is also or alternatively arranged or configured to traverse and operate in a work area that contains obstacles that are overhanging, i.e. obstacles that may not be detectable from the ground up, such as low hanging branches of trees or bushes. Such a garden is thus not simply a flat lawn to be mowed or similar, but a work area of unpredictable structure and characteristics. The work area <NUM> exemplified with referenced to <FIG>, may thus be such a non-uniform work area as disclosed in this paragraph that the robotic work tool is arranged to traverse and/or operate in.

In the below several embodiments of how the robotic work tool may be adapted will be disclosed.

Returning to the robotic work tool <NUM> being in the first work area 305A, but also being able to operate in the second work area 305B. The robotic work tool <NUM>, or rather the controller <NUM> of the robotic work tool <NUM> is configured to operate in two (or more) domain modes, where each domain mode is associated with a work area. As shown in <FIG>, the controller <NUM> is thus configured to operate in a first domain mode associated with the first work area 305A, in which first domain mode, the controller is configured to operate according to the first boundary 320A, and in a second domain mode associated with the second work area 305B, in which second domain mode, the controller is configured to operate according to the second boundary 320B. In some embodiments, the robotic work tool <NUM> is configured to ignore the second boundary 320B when operating in the first domain mode. In some embodiments, the robotic work tool <NUM> is configured to ignore the first boundary 320A when operating in the second domain mode.

The first boundary 320A is in some embodiments associated with a first control signal 325A, that the controller is thus configured to sense with magnetic sensors <NUM> and operate according to when in the first domain mode. Alternatively or additionally, the first boundary 320A is in some embodiments associated with a first beacon <NUM>'A, that the controller is thus configured to sense with navigation sensor <NUM> and operate according to when in the first domain mode.

Likewise, the second boundary 320B is in some embodiments associated with a second control signal 325B, that the controller is thus configured to sense with magnetic sensors <NUM> and operate according to when in the second domain mode. Alternatively or additionally, the second boundary 320B is in some embodiments associated with a second beacon <NUM>'B, that the controller is thus configured to sense with navigation sensor <NUM> and operate according to when in the second domain mode.

It should be noted that any combination of how a boundary is defined and how it is sensed is possible and within the scope of this application's teachings.

This enables the robotic work tool to operate freely within the first work area 305A and be undisturbed by the second work area's boundary 320B.

In order to allow the robotic work tool to cross safely between the two work areas <NUM>, the robotic work tool is configured to determine that it is in a crossing zone referenced Z in <FIG>, and as the robotic work tool determines that the robotic work tool is in the crossing zone, the robotic work tool switches from one domain mode to another. For the example of <FIG>, when the robotic work tool <NUM> is thus in the crossing zone Z, it may switch from the first domain mode to the second domain mode. The first domain mode allowed the robotic work tool to navigate to the crossing zone inside the first work area 305A operating according to the first boundary 305A, and the second domain mode enables the robotic work tool to leave the first work area 305A and continue operating in the second work area 305B according to the second boundary 320B.

The crossing zone Z thus indicates a point or area where it is safe to switch from operating according to one boundary to operating according to another boundary.

In some embodiments, the robotic work tool is configured to store a location of the crossing zone in the memory <NUM>, and to navigate towards the crossing zone, using any known and available navigation technique. In some such embodiments the robotic work tool is thus configured to determine that it is in the crossing zone, based on determining the location of the robotic work tool and comparing it to the location of the crossing zone.

In further some such embodiments, the robotic work tool is configured to navigate towards the crossing zone along a transport path TP. The transport path may be a pre-specified path, or it may be a path that has been travelled previously. IN any case, the transport path is assumed to be safe for the robotic work tool to travel along as regards to avoiding obstacles and/or having a good reception of some boundary or other navigation means so as to avoid escaping or getting lost.

In some embodiments, the robotic work tool is configured to determine that the robotic work tool is in the crossing zone by comparing the reception of the two (or more) boundaries 320A, 320B. If both boundaries are reliably received, as in that they are received at a signal level and/or quality where they can be determined correctly, the robotic work tool determines that it is in a (safe) crossing zone. For overlapping work areas, the whole overlap may thus be a crossing zone Z.

<FIG> shows an example where the boundaries 320A, 320B are based on boundary wires. <FIG> shows a similar example, but where the boundaries are based on other navigation techniques, such as based on signals from beacons <NUM>'A, <NUM>'B. It should be noted that even though <FIG> only shows one beacon (or reference station) for each work area, more may be present. As pointed out in the above, a beacon may be a UWB beacon (or other beacon) or a base station for use with a RTK system. In the example of <FIG>, the range of the first work areas beacon <NUM>'A is indicated RA and the range of the second work areas beacon <NUM>'B is indicated RB. To allow the robotic work tool <NUM> to cross from the first work area 305A to the second work area 305B, a crossing zone Z (or several) may be arranged in area(s) where signals are reliable received from both the first beacon(s) <NUM>'A and the second beacon(s) <NUM>'B, i.e. within range of both the first beacon(s) <NUM>'A and the second beacon(s) <NUM>'B. As shown in the example of <FIG>, the crossing zone Z is inside a work area, where no specified further transportation path is needed. As is also shown (as an alternative, which is not covered by the appended claims, or addition) in the example of <FIG>, the crossing zone Z maybe outside a work area, where a specified further transportation path may be needed for guiding the robotic work tool <NUM> inside the work area being crossed over in to. The transport path guiding a robotic work tool <NUM> into a work area, may in some embodiments simply be that the robotic work tool is aware of the boundary of the work are and navigates into it using any available navigation technique. The transport path guiding a robotic work tool <NUM> into a work area, may in some embodiments, be a path that is (as discussed above) known to be reliable.

<FIG> shows an example similar to the examples of <FIG> and <FIG>, but in the example of <FIG>, the first boundary 320A is based on beacons <NUM>'A sensed by the navigation sensor <NUM> and the second boundary 320B is based on a boundary wire sensed by the sensors <NUM>. This example serves to show that a combination of boundaries is possible, and the domain mode may thus also include indications of which sensors to use for detecting a boundary.

<FIG> shows a further example where two work areas 305A and 305B are not adjacent one another. In some such embodiments, each work area 305A, 305B has a crossing zone Z', Z" which are connected by a transport path TP. In such embodiments, as the robotic work tool <NUM> intends to cross from a first work area 305A to a second work area 305B, the robotic work tool <NUM> is configured to propel itself to the first crossing zone Z' (i.e. the crossing zone of the first work area 305A). As it is determined that the robotic work tool is in the first crossing zone, the robotic work tool travels along the travel path to the second crossing zone Z"(i.e. the crossing zone of the second work area 305B).

In some embodiments the robotic work tool <NUM> is configured to determine that the robotic work tool <NUM> is in a crossing zone based on comparing the current position of the robotic work tool <NUM> with a known location for the crossing zone Z.

In some embodiments the robotic work tool <NUM> is configured to determine that the robotic work tool <NUM> is in a crossing zone based on sensing surrounding signals such as the boundary 320A, 320B.

In some embodiments, the robotic work tool <NUM> is configured to switch from the first domain mode as it determines that the robotic work tool is in the first crossing zone. The robotic work tool <NUM> is configured to switch to the second operating mode and may navigate along the transport path using any available navigation technique. The second domain mode will allow the robotic work tool to enter the second work area, while not stop the robotic work tool <NUM> from leaving the first work area.

In some such embodiments, the robotic work tool <NUM> is configured to switch to a transport mode, where the robotic work tool is configured to navigate regardless of the boundaries 320A, 320B. This allows the robotic work tool to both exit and enter any work area. In such embodiments the robotic work tool <NUM> is configured to switch to the second domain mode as the second crossing zone is reached.

In the example of <FIG>, the robotic work tool travels along the robotic work tool based on the navigation sensor <NUM>, receiving signals from the satellite <NUM> and/or form any of the beacons <NUM>'A, <NUM>'B.

This enables automated transport of a robotic work tool between two work areas, possibly even when the work areas are bounded by boundary wires.

In some embodiments, the robotic work tool is configured to deactivate the work tool <NUM> when travelling along a transport path.

<FIG> shows a flowchart for a general method according to herein. The method is for use in a robotic work tool as disclosed herein. The method comprises the robotic work tool <NUM> being in a first work area 305A and operating <NUM> in a first domain mode according to a first boundary 320A. The robotic work tool <NUM> determines <NUM> that the robotic work tool is in a crossing zone Z and in response thereto switches <NUM> domain mode and operates <NUM> in a second domain mode according to a second boundary 320B in a second work area 305B.

In some embodiments the robotic work tool <NUM> is configured to determine <NUM> that it is to cross from the first work area 305A to the second work area 305B and in response thereto travel <NUM> to the crossing zone Z, possibly along a transport path.

In some embodiments, such as when the crossing zone is not inside the second work area 305B, the robotic work tool <NUM> is configured to travel <NUM> from the crossing zone Z, possibly along a transport path, to the second work area 305B. In some embodiments, the robotic work tool <NUM> travels <NUM> along the transport path to a second crossing zone in the second work area 305B.

In some embodiments the transport path is realized through a guide wire that emits a magnetic field (when in use) that may be sensed by the robotic work tool <NUM>.

Claim 1:
Robotic work tool system (<NUM>) comprising a first work area (305A) bounded by a first boundary (320A), a second work area (305B) bounded by a second boundary (320B), and a robotic work tool (<NUM>) comprising a controller, wherein
the robotic work tool system (<NUM>) further comprises a boundary wire (<NUM>) marking one or both of the first and the second boundary and the robotic work tool (<NUM>) further comprises a magnetic sensor (<NUM>), and/or
the robotic work tool system (<NUM>) further comprises a beacon (<NUM>) marking one or both of the first and the second boundary and the robotic work tool (<NUM>) further comprises a navigation sensor (<NUM>);
wherein the controller is configured to:
operate in a first domain mode in the first work area (305A) according to the first boundary (320A) and
operate in a second domain mode in the second work area (305B) according to the second boundary (320B),
wherein the controller is further configured to operate in a domain mode for one or both of the first or second work area according to the magnetic sensor sensing a magnetic field emitted from the boundary wire (<NUM>) and/or according to the navigation sensor sensing a signal emitted from the beacon (<NUM>), and wherein the robotic work tool system (<NUM>) is characterized in that the controller is further configured to allow the robotic work tool (<NUM>) to navigate to a crossing zone (Z) inside the first work area (305A) operating in the first domain mode according to the first boundary (320A), determine that the robotic work tool (<NUM>) is in the crossing zone (Z) and then switch from the first domain mode to the second domain mode and to leave the first work area (305A) operating based on the second domain mode and continue operating in the second work area (305B) according to the second boundary (320B).