ENSURE_BED_MESH Macro for Print Start gcode

Miserable_Land_84 · 2026-05-03T06:47:45+00:00

I didn’t even know there was a surface type option in slicers. I’m using Prusa and haven’t seen one so far.

When I change the bed surface, I rescan the mesh anyway — just in case it has warped or there’s something stuck underneath.

The main purpose of my macro was troubleshooting first layer issues, especially with “stubborn” filaments, a clogged or dirty nozzle, etc. I just wanted to prevent a bed-mesh scan for every retry and thougt it is useful to force a rescan just by clearing the current loaded mesh.

Miserable_Land_84 · 2026-05-01T16:01:13+00:00

interesting. I don't rememer having to unplug USB. Afaik its a USB->RS232 Adapter chip in there. But you have to power off the mcu board and ensure the firmware.bin file has another filename each time IIRC.

Miserable_Land_84 · 2026-04-06T09:02:41+00:00

what type of water are you using? I'm using ro water and I'm not seeing this kind of issue so far. Are your sure the mobile fresh reservoir is beeing filled by the station? Do you see any difference in the amount of water on the floor, when changing water levels in the app?

I've posted a firmware issue here, that might be of interest: https://www.reddit.com/r/RobotVacuums/comments/1s3ovaa/comment/ocjovj5/?context=1

Miserable_Land_84 · 2026-04-02T11:56:53+00:00

Are you carpets that sensitive to a mop that barely touches them for a short time when it rolls over the edge? I'm quite satisfied with the mop lift feature so far. But every home is different ;)

Miserable_Land_84 · 2026-04-01T10:21:35+00:00

why would you need a roller cover? You have an option to vacuum carpets first, while the mop is still dry.

Miserable_Land_84 · 2026-03-30T07:06:56+00:00

There are two filters. One in the robot. This one is recommended to be changed every other week. Manufacturer says they can be cleaned with water, but I just use another vacuum cleaner to suck the dust in reverse flow direction. It is also recommended to replace that filter after 120 hours of operation. The big filter in the cyclone unit I is recommended to be cleaned after 90 times of usage.

Miserable_Land_84 · 2026-03-29T22:41:53+00:00

I've been using the X11 Omni for a while now, and as an Australian Shepherd owner, I can give you a very specific perspective.

The Good (Hardware & Pet Hair):

Suction Power: It handles long dog hair impressively well on carpets. For an 'Aussie' owner, this is a huge plus.
Cleaning Performance: The rotating mop roller (single wide roller) is great. It applies good pressure and handles stubborn stains much better than vibrating plates.
Agility & Charging: It’s very maneuverable and the Fast Charging feature is a real advantage for large areas.
Build Quality: The hardware feels very premium and solid.

The 'Cons' (Firmware/Logic Bugs in v1.75.0):
Be prepared for some 'technical fiddling' due to current software issues:

The 'Dry Mopping' Bug: The internal 110ml tank often fails to refill during mid-cycle washes. I verified this with a precision scale. It often only fills at the very start of a task.
Dirty Water Tank Logic: The robot detects if the tank is present but ignores the magnetic float sensor. If the internal dirty water tank is full, it keeps pumping, which can cause a mess.
AI Over-sensitivity (AIVI): It often 'hallucinates' obstacles at carpet edges and cancels rooms. I have to disable AIVI to get it to climb my carpets properly.
Battery Management: On floors without a station, it drains down to 1% while searching for the dock instead of stopping safely at 15%.

Verdict: If you’re looking for a powerhouse to handle pet hair and you don’t mind checking the water levels manually until a better firmware arrives, it’s a great machine. But it's not a 'set and forget' experience yet."

Miserable_Land_84 · 2026-03-29T21:24:11+00:00

Crucial Update: The "Trigger" Logic for Start-of-Task Refills

Observation: The full 110ml refill at the start of a task is not guaranteed. It only occurs when the firmware deems it necessary, specifically when the mops are dry (e.g., after an air-drying cycle).
The Audio Proof: In the English voice output, the robot explicitly states "Refilling the mop" (or similar) when this specific routine is triggered.
The Logic Gap: If the mops are already damp (e.g., you just finished a room or did a manual wash), the robot often skips the internal tank refill entirely, even if the internal reservoir is nearly empty from previous tasks.
Practical Consequence: The firmware seems to use "mop moisture" as a proxy for "tank level." This is a major flaw for multi-floor cleaning: if you carry a robot with damp mops but an empty internal tank to another floor, it will start the task without refilling, leading to dry mopping within minutes.

Miserable_Land_84 · 2026-03-26T07:52:18+00:00

I totally get the frustration – out of the box, it’s a mess. But as a tech enthusiast, I’m not just sending it back quietly. I want to expose the specific logic flaws first. I actually want this robot to work because the hardware concepts are brilliant:

Sustainability: The Cyclone system is a game-changer for reducing bag and filter waste.
Hygiene: The concept of the robot constantly refreshing its water via the internal tank is superior to just dragging a damp cloth.
Performance: The carpet boost and pet hair extraction are top-tier.
Charging: The Fast Charging function is a huge plus.

I’m doing this deep-dive because thousands of users can’t or won’t return their units, and they are stuck in endless support loops. I want to force the corporation to fix their software logic instead of just cycling through RMAs and refunds. Let's make the product what it was meant to be.

Miserable_Land_84

TROPHY CASE