WAh, starting w the highest end model ... I don't think anyone in sg own this first, you need to get one and review it for us!
One 700 series review on Robotreviews.com already stated that there isn't significant improvement compared to Roomba 500 series with Aerovac 1.
And the new owner will exercise his 30 days trial return after testing 4 cycles.
I would have thought the Aerovac 2 bin being focused on the 2 ends of bristle brush is a good thing, but HEPA being much thicker (multi-layered), probably reduces suction. And also, since Aerovac 2 bin suction isn't directed at mid section of bristle brush, I guess bristle brush will have coiled hair in the middle.
The only thing I like is the new shielded brush bearings. But Aerovac 1 bin already resolved hair/fur issues with existing bristle brush. So new shielded brush bearings doesn't seem like such a perk.
Roomba 500 with 2 Lighthouses
- allocates fixed cleaning time 25 mins per Lighthouse regardless of area. In reality, it's difficult to split home into equal portions factoring in built-in cabinets, beds, etc.
- tends to die-off at Area 3 when battery grows old and cannot deliver minimum 80 mins. This die-off without docking (for say 5 hrs until user realises) will accelerate battery death
Roomba 700 with 2 Lighthouses
- improvements that I hope to see, but unconfirmed if already implemented by iRobot
i) Remember when battery last died, record down run time, eg. 70 mins
ii) Reserve 10 mins to look for dock, divide remaining run time by 3, eg. (70 - 10)/3 = 20 mins
iii) Allocate each Lighthouse area max of 20 mins
iv) Adaptive learning: If Roomba finds out that Area 2 or Area 3 is much larger than Area 1, it'll re-allocate cleaning time "stealing" a bit from the smaller areas.
eg. Area 1: 10 mins, Area 2: 20 mins, Area 3: 30 mins
Target outcome: whole house gets equal attention even as battery delivers less & less run time
Possible setback: What if user wants Area 1 to be as thoroughly cleaned as Day 1 when battery was brand new, and that Area 3 is insignificant even if not cleaned at all
Possible solution: Introduce an option such as (A) "Adaptive Clean Mode" vs (B) "Fix Clean Mode", where (A) is the adaptive time allocation & (B) is the fixed time allocation