u/turnerm05

I hear a mechanical/plasticky creaking/popping noise on my front wheels when they are turning. Is this normal?

Got my X430 setup this morning and put it through it's paces. This is being used on a well manicured St Augustine lawn in Texas. I'm cutting at 3.75" (tried 4" but it just mostly pushed the grass over... may need to go lower). I've also got a Lymow One still in rotation while I see if the X430 is right for my yard.

I'm running on nRTK for now, but may switch to RTK if needed. So far, it doesn't appear to be necessary, although finding a suitable docking location was more difficult than anticipated. Compromises were made BUT... I really do love the concept of the more streamlined setup and the ability to drive around to find good signal is very much appreciated and it shows the maturity of the company and the solutions they deliver. Well done!

I'm going to give the X430 the benefit of the doubt for it's first cut and judge final cut quality after it's maintained the yard for a week. Given the power and the actual steel blades of the Lymow, I usually just run it once or twice a week on command versus setting it on a schedule as it will cut through just about anything and doesn't care about longer grass... at all. Since the X430 is intended to be used differently (maintaining vs cutting) I want to see how it does this week now that I've got the yard very well-manicured. I'll run it on Sunday, Tuesday, Thursday, and Saturday.

I've got Edge Sense and Traction Control enabled. I'm not overly impressed with the Edge Sense. It's not awful but it's not great either. It seems to zig zag quite a bit while trying to find the edge. I think a better solution here is what Lymow has chosen to do and that's to follow the EXACT path taken while mapping. This allows you to overlap the edges where it makes sense which cuts down on follow-up trimming. It does a reasonable job as-is but I'd love to see an option to follow the mapped path (even if it requires the use of RTK).

The battery is a beast! I could've gone with one of the smaller Navimow options to be honest. I've only got around 5,500 square feet of lawn to mow and I suspect this thing isn't going to get much below 50% while covering my entire yard! That's a great improvement coming from Lymow.

The cutting paths are... odd... but seem effective. It seems to leave some spots uncut which is odd since they are shown as uncut on the map (seems like it would go back and get those areas). I think this is likely due to areas that it thinks have obstacles. Hopefully letting it run through a full weekly cycle with changing mow directions will fully solve that. Not passing too much judgement here yet.

I DO wish they'd allow us to set blade/disc RPM and mower speed separately. Given my lawn... I'd keep the RPMs on max and slow the mower down a bit to get the best possible cut quality. I also feel like the mower can't truly cut at 4" height (at least on St Augustine) because the disk and the mower body seem to lay the grass down too much at higher cut heights to be truly effective. As mentioned, I'm current mowing at 3.75" but may need to drop down lower but I want to see how it does for a full week before playing with the settings too much.

For a mower that advertises cutting at 4", the back of the mower sure drags the grass pretty hard at those heights! I've seen it bog down a few times but it always got itself loose.

The app itself is best in breed (and I've tried a LOT of mowers/apps). Well done here.

I personally feel like the future of these mowers (for my situation at least) is actual mower blades like the Lymow uses and the upcoming Terramow will use. But I'll see if the X430 can do well enough on a regular schedule.

I DO feel like this will be a mower that I can trust to be fully autonomous. If so, and IF it does well on it's schedule this week then we may have a winner. I suspect that I'll keep the Lymow in rotation most for edge mowing and clean-up when necessary.

I pulled the trigger on the X430 from Amazon with the current sale pricing. I’m very curious to see how it performs on my thick St Augustine grass in comparison to my Lymow One which is doing a great job (but with some trade offs).

My question though is this… I have a crushed gravel path that’s approximately 48” wide with stone borders that goes from the front right corner of my house around to the side and eventually through a gate (I do not need to mow beyond the gate). Can I put the dock there and give it a defined path from the yard to the dock (along the literal crushed gravel pathway)? It would have to back out of the dock and proceed backwards down the path for 15ish feet before getting to the yard so that it can turn around and start working.

I’m guessing that this won’t work because it will want to back out of the dock and then turn around immediately but I don’t think it will have enough room, even with its tight turning radius, given the stone borders on the path.

I pulled the trigger on the X430 from Amazon with the current sale pricing. I’m very curious to see how it performs on my thick St Augustine grass in comparison to my Lymow One which is doing a great job (but with some trade offs).

My question though is this… I have a crushed gravel path that’s approximately 48” wide with stone borders that goes from the front right corner of my house around to the side and eventually through a gate (I do not need to mow beyond the gate). Can I put the dock there and give it a defined path from the yard to the dock (along the literal crushed gravel pathway)? It would have to back out of the dock and proceed backwards down the path for 15ish feet before getting to the yard so that it can turn around and start working.

I’m guessing that this won’t work because it will want to back out of the dock and then turn around immediately but I don’t think it will have enough room, even with its tight turning radius, given the stone borders on the path.

I'm not certain if this is just a Model X thing or if it's a pervasive issue across all vehicles but...

It seems to me that FSD does a reasonably good job of identifying the appropriate speed limit using it's visual recognition. Sure, it misses a few here and there but in general... it's good enough.

However, FSD seems to choose it's speed off of the map data more often than choosing it's speed off of the speed limit visual recognition. I mean, it's VERY obvious... I'll be on a road in a 50mph speed zone on hurry going 60mph. A speed limit sign is presented for 45mph, the sign changed on the screen to match but FSD doesn't slow down at all. Then, about 2 miles later it will abruptly slow down to 49mph as if it just saw a new posted speed limit. I think what's actually happening is that the map data is indicating that the speed limit dropped which is what the car is reacting to.

Another scenario... I'm on the interstate in a 70mph zone going 82 on hurry. We come up to a construction zone where the limit drops to 60mph. In THIS situation, FSD will recognize the sign and slow down... but then a mile or so later it resumes going 82mph even though no posted sign is present to indicate the increase in the limit. Again, I think FSD is reacting to map data instead of what it's picked up visually. A few miles later, another speed limit sign shows a 60mph zone... FSD slows down but a mile or so later it speeds right back up. So on and so forth.

Why can't they figure this out? It seems like some basic logic that uses map data, visual speed recognition and traffic flow could easily solve this.

Prove
Me
Wrong

The current behavior of 14.3.3 when people (or bikes or golf carts, etc) are waiting at a crosswalk is a little sketchy. It pauses and then resumes and pauses which generates a lot of confusion as the people think you are pausing to let them go and just when they start moving, FSD tries to go.

It's a tough situation but it just needs to pick a plan - let them go or don't. But don't flip back and forth!

Anyone else seeing this?

Perfect scenario today. Had to leave work while it was pouring rain. Had my dog with me...

Figured I'd test out Summon in about the only scenario that it's useful to me and it actually worked brilliantly!! Pulled the car right to the curb, popped open the falcon wing door from the app and my dog jumped in. I got loaded up and only minimal rain hitting me (had an umbrella of course).

It's just one test but this is the first time summon has actually worked for me in a scenario that I need it to work. The other times I've tried it just randomly stops in THE most awkward position ever and I have to do the run of shame to rescue it while looking like a jackass.

'26 MX with about 9,000 miles of which 99% are with FSD.

Got the software update last night and just drove 250 miles on it (The Woodlands to Fort Worth) and it seems fine to me. Speed profiles seem better. I was in Hurry the whole time and it was going about 10-12 over on average which it could (no traffic stopping it). I had to intervene once for navigational reasons (it was going to miss a tricky split of the highway).

Following distance seemed good to me but I didn't personally have any issues with follow distances on prior versions. I was just hoping that it didn't increase the distance so much that people were constantly cutting me off on the interstate... no issues observed.

Speed control seemed a lot better than prior versions. I stayed in Hurry the whole time. On prior versions it seemed that I was constantly playing with speed profiles to get the car to adjust.

HOWEVER... this seems to be an ever-present issue no matter the version. But I'm not sure if it's just the MX/S issue or if the Y/3 also have it. I've noticed that the car seems to peg speed to whatever the map data is regardless of what the cameras pick up and display on the screen. Either that or it just blatantly doesn't slow down consistently with speed limit changes. In my MX specifically.... if I'm going through a construction zone on the interstate and there is a sign indicating that the temporary speed limit is 60 (instead of 75) FSD will appropriately change the display to show 60mph and sometimes it will slow down appropriate but then it quickly speeds back up and also changes the displayed speed limit back to 75. It shouldn't do this until it sees a new sign indicating the speed limit has increased but it seems to let the map data override what the cameras have actually seen... which defeats the purpose. And sometimes it won't even attempt to slow down for the temporarily lower speed limits. In THESE situations I usually have to change the profile down to chill or even sloth just to force me into the far right lane behind some traffic to regulate my speed. This needs to be addressed.

Otherwise... 14.3.2 seems very capable. I haven't tried ASS yet but will do that later this week.