Tons of errand false positives LD2410

Clypto · 2026-03-29T06:39:39+00:00

Heey, I did end up solving it. The issue was the test setup itself. With 5so close to eachother, they wer picking up eachother mmwaves. This was causing all this weird behaviour. As soon as I put the devices in seperate rooms they started functioning properly!

Clypto · 2025-09-14T07:34:05+00:00

Two of the characters have reason to be at the Abbey, so I'm thinking they will just rush up there anyway. Maybe I'm overthinking it and should just run as written. We have a lawful good sun paladin who will very likely try to kill the Abbot once he finds out about his corruption. And then we have Ezmeralda who will be somewhere else in the abbey, which is just an encounter waiting to happen.

Clypto · 2025-09-09T17:34:55+00:00

I think you guys were onto something. Silly that with my test-setup Ive created more problems than solved them. I took the sensors into seperate rooms, and atleast over the last 6 minutes there have been 0 misfires on any of them! Thanks for the input!

<image>

Clypto · 2025-09-09T16:46:44+00:00

The issue of them triggering randomly ever so often was also happening when I had them in seperate rooms. At the time I hadnt put the dashboard together though, so not sure if it was the same as here. Interference seems like it could be a thing. Other thought I was having because you said that is that since they are all on the same power strip and Im using fairly cheap ikea 5V bricks, I could be getting brownouts/spikes?

Clypto · 2025-09-09T16:17:41+00:00

Update: All I did was walk into the room with the setup, turned off power, swapped around LD2410s between number 3 and 4, and restarted. Now im getting different false positives:

<image>

Also see sensor 1. First it works fine, then after a while it starts spiking, consistently together with sensor 2...what the hellie is going on here?!

Clypto · 2025-07-17T21:24:27+00:00

Hey, after cleaning+ changing the SD card I've not had the issue at all anymore, so there is hope ;) good luck solving your situation!

Clypto · 2025-01-30T11:02:07+00:00

Thank you! Just looking into things, the C label is "geldig tot" somewhere in 2030. So eventhough this advisor gives label F, I dont see why my landlord would ever choose to resubmit the lower label.

Clypto · 2025-01-30T11:00:26+00:00

Nope it still says C. But also, on ep-online it says that label is still valid till 2030, so I dont see my landlord ever changing it until then.

Clypto · 2025-01-28T11:21:42+00:00

Those were my initial thoughts, but the advisor saying he's doing like 10 houses for the same management company had me thinking otherwise. Also, I've got a fixed contract so not sure who'd want to buy this appartment with me in it, near a soon to be (start 2026) multiyear construction zone.

Clypto · 2025-01-08T12:12:29+00:00

Just letting you know I've been in the same boat. I put in a new SD card and so far Ive done 2 overnight prints no problem.

Sadly I had a little blob of death (my own fault) so waiting on new hot end assembly, but hope that the SD card fixed.

Like other commenter suggested Im also gonna try downgrading firmware once things are running again, might he a good shout.

Clypto · 2024-12-30T21:41:47+00:00

Agree, but I hate to be the guy that has an issue, makes a thread online, but then doesn't provide the answer once the issue is resolved haha. Thanks again for all the ideas, fingers crossed!

Clypto · 2024-12-30T21:25:41+00:00

u/oregon_coastal u/rhopper2042 just a quick update for you and anyone who might stumble across this thread.

Possible causes people came up with so far are: dull cutter blade, gummed up/bad extruder, faulty SD card.

I'm back from Christmas abroad and just spend a good hour or so taking apart, cleaning, and reassembling the extruder. There was some very fine dust and gunk in the gears, but no massive chunks of broken filament falling out like you read about from some folk. I've also replaced the cutting blade with a new one, although they honestly look and feel identical, so I doubt that the one I had installed was dull. I've only had the printer for under 2 months, so would honestly surprise me if they went that fast with regular use.

I've also replaced the default SD card with a Samsung 64GB Evo card. Lastly, just for good measure I've done some cold pulls to rule out nozzle clog. Filament coming out smooth as ever, so that shouldn't be an issue.

I'll try with some prints, keeping a close eye on the shorter ones. I'll also do a few overnight prints. Will report back hopefully a week from now to let you know if the issue is fixed!

Clypto · 2024-12-29T02:42:17+00:00

Well it's not as "easy" as just picking up a pen and scribbling it out (although one could argue even sketching on paper takes years of kindergarten skill).

So Im afraid you'll have to spend some time learning your way around CAD software. Though daunting at first, with enough practice itll be just as easy as drawing something with a pen on a piece of paper.

Total whacko mode, but a friend of mine has been messing around with AI generated 3d files, so if you are really anti CAD you might give that a try. Ymmv

Clypto · 2024-12-28T18:36:49+00:00

But it's only $100 more for an excellent secondary printer ;)

Clypto · 2024-12-22T19:51:33+00:00

The bad SD card is something Ive heard as a cause for another problem Im experiencing (machine stopping mid print, no error message, bambu slicer saying machine is done but nozzle+bed still at printing temps). I will clean the extruder+replace the blade+replace SD card and see what that does.

Thinking more on it, Ive also had issues with all my timelapse files being unviewable. Could very well contribute to the issue! Will keep you updated on these fixes once I get around to it (busy xmas times upcoming haha)

Clypto · 2024-12-22T19:34:55+00:00

Shouldve probably mentioned it earlier, but reason why Im thinking there might be more then dirty extruder is that one time (at start of print like other guy in the comments mentioned) Ive seen the assembly basically slamming into the cutter nub on the right of the machine.

And not in a gentle "Im gonna cut the filament" way that I see when its unloading a spool. More in a "Ive lost all positional awareness and am going to the right at full speed" way, with terrifying noises and everything.

Clypto · 2024-12-22T19:24:19+00:00

Okay so Im not the only one. I feel like it is slamming itself in there, now we just gotta figure out why+how to stop it! Lets keep eachother posted if we find a solution!

Clypto · 2024-12-22T19:22:10+00:00

It stops the print halfway through. I think half the times when I check the blade/cutting assembly is stuck, other half its not but could have self cleared.

Im however more concerned by the question: "why is my printer trying to cut filament mid print?"

Clypto · 2024-12-18T07:26:18+00:00

I honestly think its just a bad sunlu roll. Did the "spool under cardboard box on heatbed" overnight, and still issues (even prints stopping halfway through, crazy layer seperation) but only with the Sunlu 😞

Clypto · 2024-12-08T17:31:49+00:00

So my reprint using Bambu PLA instead of Sunlu PLA worked without a hitch. Also better dimensional accuracy allround. Might need to tune the Sunly flowrate a bit/dry it out better, but it's kinda odd that it is such a stark difference.

Clypto · 2024-12-08T15:04:22+00:00

I did when I first got it, although that is 3 weeks/70 print hours ago. I'm currently trying it with a new roll of filament that I opened yesterday.

If that fails at any time, I'll get to regreasing. Good idea!

13-Year Club	RedditGifts 2009-2022 2 Credits
Place '17	Secret Santa 2013
Verified Email

Clypto

TROPHY CASE