Preview — not yet launched. MyRobotDoc is online early so owners and reviewers can read it. Pages are still being checked against their sources, so details may change.

Independent guides for robot mower owners

Not affiliated with or endorsed by any device manufacturer. All trademarks belong to their respective owners.

← All guides

known-issue

LUBA 2: fault 1300/1303 ("poor positioning status") — at least two different causes

Models covered
LUBA 2 (base/2024 and AWD 1000)
Affects
RTK station — not the app or robot body
First reported
22 April 2024
Last updated
7 September 2026
Status
Open

RTK station — not the app or robot body. See our app vs. firmware vs. RTK guide if you're not sure which one you're dealing with.

What this page is: fault 1300 is an officially-documented code (see the fault-codes reference; Mammotion's manual just says "positioning status is poor, wait for the robot to reposition itself"), but that generic text doesn't explain why it keeps recurring for some owners. Three independent LUBA 2 owners in the same thread hit it for what look like at least two different reasons: one confirmed by Mammotion's own moderator, one apparently fixed by a firmware update, one still unexplained. Find the case closest to your own setup below.

The codes

1300 ("Schlechter Positionierungsstatus" / poor positioning status) is documented in Mammotion's manual. 1303 ("Roboter setzt das integrierte RTK-Modul zurück und versucht die normale Positionierung wiederherzustellen" / the robot resets its integrated RTK module and attempts to restore normal positioning) is not documented anywhere in Mammotion's manuals; two of the three owners below saw 1300 and 1303 together1.

Confirmed cases

Parked under a solid-roofed structure — signal blocked, per Mammotion's own moderator

A LUBA 2 parked roughly a meter under a covered terrace to keep it dry hit this error. A Mammotion moderator active in the thread diagnosed this directly: a solid terrace roof blocks satellite signal entirely, and the mower will "protest" with exactly this error. The moderator's own mower sits under a plastic-roofed or wood-with-roofing-felt garage instead, which lets signal through1. If your mower is sheltered under something opaque (concrete, dense tile, metal), that's the first thing to change.

Resolved after a firmware update, despite similar sheltered parking

A LUBA 2 AWD 1000 parked partly under a thin wood overhang initially hit the same 1300 error, its owner suspecting the same shelter-blocking cause. After updating to firmware 1.11.511.381, the error stopped appearing entirely, despite the mower's parking location not changing1. This doesn't rule out a partial signal-visibility factor (a thin wood roof blocks less than solid terrace concrete), but the timing is specific enough to note: if you're on an older build than 1.11.511.381, updating is worth trying before assuming your shelter is the problem.

Unresolved: daily recurrence with no shelter at all

The identical 1300 (and 1303) codes appeared every day at the start of mowing on a third mower parked fully in the open: 5 meters from the RTK antenna, original LUBA roof, antenna fixed in place. No shelter-blocking explanation applies here, and the thread doesn't record a resolution for this case1.

No single cause explains every report above. This is a starting index, not a diagnosis. If you're hitting 1300/1303: first check whether your mower or its charging dock sits under anything solid overhead (a real terrace roof, not a garden umbrella) and try a more RF-transparent shelter or the open sky; if that's not it, check for a pending firmware update; if neither helps, treat it the same as the third case above and let us know what you find, especially if you can confirm a fix.
Advertisement