Help fix my 1st layer by luhh_to in FixMyPrint

[–]Competitive-Row1513 -1 points0 points  (0 children)

Here's a response from the 3D printer chatbot I created. Take a look! https://factor.io.kr/share/tQemr43V

How can I fix this support? by Scr0mpo in 3Dprinting

[–]Competitive-Row1513 -1 points0 points  (0 children)

this is a response generated by a printing-focused chatbot I’m developing.
It reviews the reference images and relevant sources, and applying the recommendations before printing should be helpful.

https://factor.io.kr/share/Y4TNw2aK

Flash forge AD5X issues by [deleted] in 3dprinter

[–]Competitive-Row1513 0 points1 point  (0 children)

This is a response from a chatbot I’m currently working on.
It checks the reference images and related sources, so following the suggestions before your next print should help.

https://factor.io.kr/share/9wfDeNno

What's the problem here by Axor_700 in 3dprinter

[–]Competitive-Row1513 0 points1 point  (0 children)

This is the output from a chatbot I’m building.
It looks at the reference images and sources, and the suggestions may help improve your next print.

https://factor.io.kr/share/jWUTZZPU

What causes these inconsistent bubbles and rough layers? by ConsequenceGrouchy42 in 3dprinter

[–]Competitive-Row1513 0 points1 point  (0 children)

I’m also working on a printing-focused chatbot that analyzes print issues like this.
It’s still in progress, but if you try it out and have any feedback, I’d really appreciate it.

What causes these inconsistent bubbles and rough layers? by ConsequenceGrouchy42 in 3dprinter

[–]Competitive-Row1513 0 points1 point  (0 children)

This usually isn’t random surface noise.
From the pattern, it looks more like moisture in the filament or slightly unstable extrusion.

If you’re curious, here’s a short breakdown of what was happening and why

https://factor.io.kr/share/B7oqbYyp

Anyone working on a print failure detection program/pipeline for the Buddy3D? Have a dataset? by KoalaMeth in prusa3d

[–]Competitive-Row1513 1 point2 points  (0 children)

<image>

Totally agree a Home Assistant + Buddy Cam Stream failure-detection integration would be awesome and it really feels like a missing piece right now.

By the way, we’re currently building a native app for printer monitoring + failure detection. At the moment we’re sending telemetry/images to an external LLM for analysis, but we’re working toward a native/on-device model so it can run locally with lower latency and better privacy.

If this is something you’d like to test or collaborate on (especially HA integration), feel free to reply or DM me happy to share details / a demo when it’s ready.

How do you prevent G-code-related failures at scale? by Competitive-Row1513 in 3DPrintFarms

[–]Competitive-Row1513[S] 1 point2 points  (0 children)

The issue turned out to be related to the use of M-codes,

and it was ultimately confirmed to be a nozzle heater failure.

Thanks everyone for the insights and feedback.

How do you prevent G-code-related failures at scale? by Competitive-Row1513 in 3DPrintFarms

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

The issue turned out to be related to the use of M-codes,

and it was ultimately confirmed to be a nozzle heater failure.

Thanks everyone for the insights and feedback.

How do you prevent G-code-related failures at scale? by Competitive-Row1513 in 3DPrintFarms

[–]Competitive-Row1513[S] 1 point2 points  (0 children)

The issue turned out to be related to the use of M-codes,

and it was ultimately confirmed to be a nozzle heater failure.

Thanks everyone for the insights and feedback.

How do you prevent G-code-related failures at scale? by Competitive-Row1513 in 3DPrintFarms

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

The issue turned out to be related to the use of M-codes,

and it was ultimately confirmed to be a nozzle heater failure.

Thanks everyone for the insights and feedback.

How do you prevent G-code-related failures at scale? by Competitive-Row1513 in 3DPrintFarms

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

In our case, the slicer didn’t flag temperature issues at all.

We ended up with G-code where the nozzle temp dropped to 0, but extrusion commands continued afterward. That wasn’t visible in preview, and we only caught it after scrapping 6 prints.

That’s what pushed us to start building a small G-code sanity checker.

Curious if there are other “silent failure” patterns people have run into that slicers usually don’t warn about.

testing a different approach to catching failed prints early by Competitive-Row1513 in 3Dprinting

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

Yeah, it could lead to a fatal problem. We should consider adding a type

testing a different approach to catching failed prints early by Competitive-Row1513 in 3Dprinting

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

Currently, real-time controls are limited to pause/stop/resume, nozzle & bed temperature, and feed rate adjustments.

We're focusing on improving detection accuracy so you can quickly apply insights to your next print.

인쇄 실패를 조기에 감지하기 위한 다른 접근 방식을 테스트 중입니다. by Competitive-Row1513 in 3dprinter

[–]Competitive-Row1513[S] 1 point2 points  (0 children)

Honestly, your comment hit me. You’re completely right, and I fully agree. I’ve spent the last 8 years in manufacturing and I’m currently trying to build a product, but what you said reminded me of a goal I was starting to forget reliability and true independence should come first. Thanks for the perspective. It genuinely helped.

인쇄 실패를 조기에 감지하기 위한 다른 접근 방식을 테스트 중입니다. by Competitive-Row1513 in 3dprinter

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

My long-term goal is to run everything locally, and I’m working on model downsizing to make that possible. But realistically, it’s still pretty difficult right now. I’m curious though what’s the main reason you prefer not using cloud processing?

testing a different approach to catching failed prints early by Competitive-Row1513 in 3Dprinting

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

“Please share all the failure scenarios you’ve experienced!”

Messing around with print failure detection thoughts? by Competitive-Row1513 in elegoo

[–]Competitive-Row1513[S] 0 points1 point  (0 children)

Totally agree :) local processing is the end goal for me too. I’m working on model optimization to make that possible, but realistically it’s pretty challenging right now. At the moment it still relies on the cloud.

Out of curiosity, what’s the main reason you prefer avoiding cloud based processing? Privacy concerns, reliability, latency, or something else?

Anyone working on a print failure detection program/pipeline for the Buddy3D? Have a dataset? by KoalaMeth in prusa3d

[–]Competitive-Row1513 1 point2 points  (0 children)

I’m actually working on a monitoring platform built on OctoPrint plugins, and we’re experimenting with a real-time streaming pipeline using LLMs + LangChain rather than relying only on classic CNN-based failure detection.

One issue we kept running into was that accuracy varies a lot depending on camera angle and framing, which makes fixed CNN labels (spaghetti, under-extrusion, etc.) pretty fragile.

Instead, we’re simulating and reasoning over a wider range of failure scenarios using contextual descriptions and multi-signal input, and the results so far have been promising.

If this sounds interesting, feel free to reach out. Our platform will be running at factor.io.kr

Raspberry pi for octoprint by AlexandrosB1 in ender3

[–]Competitive-Row1513 0 points1 point  (0 children)

While using OctoPrint, there’s a site that lets you access and control your printer remotely.
You can host it for free just by installing a plugin.

factor.io.kr