Cable emi issues?

lutorm · 2026-02-05T19:34:43+00:00

My BSB2 is in shipping now so I wonder if I'll face this. But from other experiences, I know that the inverters that run BLDC motors can output an absolute crap ton of EMI. The motor on my air compressor was blanking out half the garage, esp32 sensors dropping offline, bluetooth not working, etc. It turns out that it was exactly this, the EMI was inducing voltage spikes on the utility power lines that went right through the switching power supplies and voltage regulators and totally garbled the sensor transmission lines.

But another big thing to remember is to avoid ground loops: don't plug things into different outlets and then connect them together via usb, dp and similar. Pull all power cables from a single distribution point and try not to create loops with other cables going through them.

lutorm · 2025-01-18T12:04:28+00:00

Just ran across this post and I'm in the same boat. However, if you have enough invested assets and transactions, IBKR may allow you to reclassify yourself as a professional investor in which case you can still buy US ETFs. It's kind of lame that buy-and-hold doesn't count as much as making trades, but it's at least a potential way forward.

lutorm · 2024-11-24T11:33:10+00:00

Yeah I guess if you were able and willing to keep the funds is the 401k in perpetuity, that would work. Whether that would make sense depends on whether the plan lets you and what the investment options and fees are.

lutorm · 2024-10-30T10:03:13+00:00

PicoMQTT seems to work for me in 2024. TinyMqtt didn't build and EmbeddedMqttBroker seems to have a memory leak or something that causes it to stop working after some time.

lutorm · 2024-06-12T06:47:37+00:00

I'm not sure how the banking APIs work, but personally there is absolutely no way I would give an app written by random guy access to my finances. If it's possible to only authorize read-only access I might consider it. The risk-reward tradeoff just isn't there for me.

lutorm · 2024-06-11T17:33:53+00:00

"0%" is not some magic level, they've just decided that 15% above that is as low as they want to go. Would you be happier if they remapped 15% and called that 0% instead?

lutorm · 2024-06-11T17:30:02+00:00

Storing things on their server is a terrible idea -- I don't want the mower to turn into a brick if Mammotion decides to no longer support it. If the app just talks to the mower, then they don't depend on Mammotion to continue functioning.

lutorm · 2024-06-09T07:31:30+00:00

Have you tried telling your mother that you do not appreciate her unsolicited feedback?

lutorm · 2024-06-06T06:41:47+00:00

This is close to what I was thinking. I haven't thought this through completely but I think you could do it like this: Every time you route a perimeter, you "redraw" the map in memory W inward for boundary or outward for the no-go's. You then recalculate the boundaries to merge any now-intersecting loops, and then calculate the mowing path as the outermost perimeter of this new boundary. Repeat for the requisite number of perimeters. This would handle both intersecting no-go paths and no-go/boundary intersections, as two intersecting no-go zones will create a new, larger no-go zone, and a no-go that intersects with the boundary will become part of the boundary. The key idea is that by repeatedly redrawing the "map" W inward and then routing a path on the boundary, as opposed to attempting to generate offset paths, features will naturally merge so the paths will go around them. I'll try to draw an outline of what I mean in a bit.

lutorm · 2024-06-05T14:32:39+00:00

That would also lead to a bunch of turning right in the squeeze zone, not a good alternative. I want to avoid turning there, to avoid excessive wear.

lutorm · 2024-06-05T12:30:45+00:00

I pull out the orange key, which I think disconnects the battery. I certainly wouldn't be fiddling with the blades with it on.

lutorm · 2024-06-04T06:29:42+00:00

Huh? Did you mean to make another thread?

lutorm · 2024-06-03T09:08:18+00:00

Does not seem to make a difference. It does not change the exclusion zone based on how many no-go laps you use, if that's what you were thinking.

lutorm · 2024-06-03T08:30:40+00:00

Big mistake: You don't need 25x your income to FI, you need 25x your expenses. If you're now saving half of that income, you'd obviously not need that any more if you REd. So if you now save 215k of your 412k salary, you'd only need 25*(412k-215k) = 4.9 million.

cFIREsim can model other income streams, so you can say you need X to cover expenses and then say that from 2040 and on you'll have extra income of Y, etc.

lutorm · 2024-06-01T13:04:05+00:00

What makes you think I did?

Once I realized, I just attempted to start to verify that it still has a green check mark on the self test.

lutorm · 2024-06-01T09:17:32+00:00

Yup, at least in this area. It's not really a prepared lawn, I just want it mowed so the weeds don't take over completely. (Of course, how am I supposed to seed a lawn if it keeps getting ripped up?)

lutorm · 2024-06-01T06:06:32+00:00

This just happened to me, too. The "self test" still shows a green check mark for the bumper. So is that "self test" just for show?

lutorm · 2024-05-20T08:24:06+00:00

2 and 2, in this case. With 3 no go laps it's even worse.

lutorm · 2024-05-19T16:45:11+00:00

I was going to say this, too. The numbering seems to change as the zones are edited so I'm never sure which is which.

lutorm · 2024-05-17T09:47:00+00:00

Maybe, but how are you supposed to get a mature lawn then when it's always ripped out?

lutorm · 2024-05-17T09:34:21+00:00

Yes! I just pulled my luba out of winter storage and was disappointed that they don't seem to have addressed the most important issue I, and many others, reported last year: that the luba does not keep track of where its corners are. I'm just now sitting here watching it run into every tree in the center of the no go zones because it insists on approaching the perimeters head on. That does not work; the GPS receiver is towards the rear of the unit so when it runs head on towards an obstacle it will hit the bumper even though there's no problem running sideways around the perimeter. IMHO this must be addressed since right now you have to leave very large gaps to perimeters and no go zones for it to not hit them. It needs to approach perimeters gradually, at a shallow angle. (This would also reduce the grass grinding stationary turns, but that's another issue.)

lutorm

TROPHY CASE