r/prusa3d • • 1d ago Bravo

Announcement Prusa Connect Local - Out now!

Post image
573 Upvotes

Hello all;
Have you ever wanted to use Prusa Connect, but without relying on an online service?

  • No cloud?
  • Keep your data on your own systems?
  • Monitor your printers locally, even when offline? If you said yes to any or all of these, we’re happy to announce Prusa Connect: a local server you can run on your own system to manage your Prusa printers and the data connected to them. You can install it on Windows, Linux, macOS, or even a Raspberry Pi. Give it a try!

All the information is here:
https://www.prusa3d.com/p/connect/connect-local/


r/prusa3d • • 9d ago

Announcement Contest - Print of the Month - November 2026

Post image
28 Upvotes

Our October Print of the Month contest was a blast! We always love seeing the incredible projects, upgrades, and creative builds coming off your build plates. Jump in this month for your chance to win an Original Prusa MK4S kit in the raffle, plus 1050 Prusameters each for our 3 selected top prints!

Show off anything you’ve printed recently! The MK4S kit is up for grabs in the raffle again, meaning one lucky winner is taking home a brand-new machine to put straight to work on their next project!

Raffle Winner – October 2026

Congratulations to our October raffle winner: u/GP_3D! Keep an eye on your DMs for details on how to claim your prize!

Don't forget to catch our monthly community stream (1st Thursday of every month on YouTube at 19:00 GMT+1) to hang out with the team and watch the draws live (watching live is optional, you can still win if you're offline!).

October Prusameter Winners

Here are our top three featured prints from October:

All Prusameter rewards will be distributed within the week.

How to Enter New to the contest? Here is how to get involved:

  1. Post your print (anything printed using a Prusa machine).
  2. Apply the "Print of the Month" flair to your post.
  3. Give credit to the original model and designer.
  4. Drop your Printables handle in the post so we know where to send your Prusameters.
  5. Designer Exception: Don't own a printer? Link a real MAKE of one of your models hosted on your Printables account.

Contest Rules

  • All qualifying posts submitted between the 1st and last day of the month are entered.
  • We review all entries at month-end and announce winners at the start of the next month.
  • One raffle entry per Reddit/Printables account (though feel free to share multiple prints!).
  • Raffle Eligibility: Accounts must be at least 1 month old with posts reaching 10+ upvotes (high-effort posts from new accounts may be approved at moderator discretion).
  • Low-effort, duplicate, or spam submissions will be removed and disqualified.
  • The raffle is drawn live during our monthly community stream on the first Thursday of the month (19:00 GMT+1).
  • Note: Winning photos may be showcased across our official social channels to highlight our amazing community!

We can't wait to see what you're printing this month!


r/prusa3d • • 8h ago

The joys of printing tall things

Post image
53 Upvotes

r/prusa3d • • 11h ago

Printing 60A TPU with 2.20mm Recreus filament.

32 Upvotes

I wanted to show people saying « Bambulab understands everything with 2.85mm TPU filaments » that 2.20mm is enough to print 60A TPU at 6mm3/s without issue.

I bought 2.20mm nozzle from Recreus combined with their 2.20mm filament (60A and 70A), installed their profile, reduced idler tension screws at maximum loaded the filament and hit print.

Nothing more than filament sensor magnet mod to help passing it through the sensor. I loaded the filament through the regular PTFE route and that’s it.

Drying the filament will help with stringing, and keeping a 5mm3/s max flow will probably get even better results (chimney was printed too fast), but it’s crazy how easy it was to print such a soft filament.

I will put some pics in comments after a little cleanup

EDIT: Wow, video quality is way crappier than the original one.


r/prusa3d • • 14h ago

Prusa Connect local must be reachable by a 20-byte hostname/IP

46 Upvotes

TL;DR: You probably need to be able to connect to your prusa connect local host by IP.

I set up Prusa Connect Local like I do all my services: behind a reverse proxy that terminates https, accessible by https://prusa.home.mycooldomain.com. The connect service itself works fine, and it will happily create a prusa-printer-settings.ini that looks like this to load up into the printer:

[service::connect]
hostname = prusa.home.mycooldomain.com
port = 443
tls = 1

When you load this up into the printer, though, it can only store the first 20 bytes of the hostname, and it fails to connect. There's a slightly-less-than-clear section in the example config.yaml that explains this:

 # The origin printers dial, written into the prusa_printer_settings.ini the
    # add-printer page offers. Default empty, which uses the address the page
    # was opened on. Set it when printers reach this server by another name,
    # for example https://shop.example.net. The hostname must fit the 20 bytes
    # a printer stores, unless it ends in prusa3d.com, and must not be a
    # loopback name such as localhost: on a printer that is the printer itself.
    # printer_address: ""

I ended up exposing the port that the container is running on and just letting the printer connect over HTTP by IP address on the LAN, which isn't ideal. I have another, shorter domain I could use just for this but it's not set up for acme DNS challenges to get ssl certs for internal services the way I do for my other homelab services.

Prusa, please lets figure out a straightforward way to support https domains longer than 20 characters.


r/prusa3d • • 5h ago

Core One INDX Callibrations - Lower Temps?

9 Upvotes

So I've been using PrusaSlicer 3 exclusively since I did the INDX upgrade, mostly because I want to get my workflow aligned.

With PS3 has come plugins which are great, especially some of the community callibrations. I've been using them a lot (needed to modify the one on marketplace using Claude as it wasn't printing the first layer at the correct height, but still incredibly handy) and my print quality is now at a level I didn't think would be possible unless I tuned my filaments and I was too lazy for that jazz.

Anyway, one thing I've noticed is that consistently on the temperature calibration towers that I get the best print quality at temperatures which are very near the low end. Has anyone else seen this? Is it an artifact of the temperature towers? Seems pretty consistent with PLA and PETG so far.

It does seem to tie in with stringing and oozing on some prints so I think it might be legit, but wanted to sound out the majority.

Also, I cannot believe PrusaSlicer went as long as it did without the ability to generate calibration print automatically. They are so handy and take like an hour per filament.


r/prusa3d • • 9h ago

What’s the proper way to handle spool runout with OpenPrintTag?

17 Upvotes

Spool runs out of filament, I replace it, but now it has a new OPT and the printer doesn’t write “empty” for the old one. And when the print ends it now complains about being unable to write to the old spool (because it was replaced, duh!) Did I mess up?


r/prusa3d • • 10h ago

Question/Need help Prusa USS Drybox's potential design flaw?

Thumbnail
gallery
15 Upvotes

A week ago I was swapping spools on one of my USS Dryboxes when one of the latches (next to the access port for desiccant) split the middle. At the time I assumed that maybe I force it somehow, and while it is most definitely "broken", I can still latch the box... so that's what I did and didn't think much of it.

It didn't sit well with me, so I eventually decided to inspect my other dryboxes. So:

  • All of my dryboxes have plastic stress marks on the "side latches" (the ones next to the moisture sensor and the access port for desiccant).
  • One of my other dryboxes access port side latch has a "hairline crack" that hasn't split yet.
  • All the other latches appear fine.
  • The access port side latch always has the bigger stress marks.
  • The stress marks and the cracks appear on consistent places: always slight "below" the middle.

So the question is, have you guys noticed this happening on your dryboxes? If you do have these, is it on the side latches too or somewhere else? This might be a known problem and I just found out now.

The humidity in the box as been slowly creeping up so I will most likely shelf this box for now :/


r/prusa3d • • 13h ago

Prusa Connect Local - Almost solves all my issues.

24 Upvotes

Some of you may remember my post from the other day frustrated with my new printer but also frustration towards Prusa Link and the lack of local control, well maybe I should have just waited because I’ve got Connect Local installed and it kinda solves a lot of the issues I had, it even let’s you send gcode directly to the printer which is amazing but there’s one omission and I can’t understand why they chose this.

CHAMBER TEMPERATURE!!!! They still don’t report it anywhere, there’s even an option in the settings to set a target temperature but yet I can’t see what temperature it actually is :(. Prusa, fair play this is a great step in the right direction and is making me consider keeping the printer but please just let me see what my chamber temperature is without using your cloud app!

If I’m being an idiot and have missed something, please let me know but I can’t see it anywhere.


r/prusa3d • • 4h ago

Broken bits?

Thumbnail
gallery
4 Upvotes

Our Core One L was running an overnight print job and one of the prints disconnected from the bed. We found these small plastic pieces on the bed and under it on the printer floor. The printer now has a buzzing vibration sound. Any idea what this may have broken off of?


r/prusa3d • • 55m ago

Question/Need help Prusaslicer: How can I add a height of more than one layer to the brim of supports?

Post image
2 Upvotes

How can I add a height of more than one layer to the brim of supports?

The brim of my supports always stick to my plate and they are a real pain to get off. Is there a setting somewhere to add a few more layers?

Thanks!


r/prusa3d • • 1h ago

Online Update for Connect Local - How do I connect to it?

2 Upvotes

It says to "Pair this server with the Beta Portal". I clicked it and am getting to a website I can't access. How do I automatically update Connect Local?

Or is there a fancy command I can run on my machine? I am running it on Linux, not in a Docker container (should I do that??).

Cheers! 🙂


r/prusa3d • • 1h ago

Question/Need help Software support for MMU3 vs INDX

2 Upvotes

I see a lot of sentiment that the hardware is great but the software support for INDX is lacking. I’m curious how/if that extends to the mmu or not.

I just cancelled my indx order because I eventually felt the price, time spent upgrading, and the lack of software intuitiveness just didn’t justify the purchase for me right now. That said, the mmu may be better for me for a good while.

For those that went from MMU3 to INDX, how is the software support for MMU3 in comparison to INDX? Did you find software support for mmu3 better as of right now? Does that extend to prusaslicer 3?


r/prusa3d • • 4h ago

INDX Batch 8 update

3 Upvotes

Good news at least for me, i got a shipping update: "Date of dispatch:11/18/2026"


r/prusa3d • • 21h ago

CNC Kitchen's INDX review casually referenced this Core One Klipper port, but apart from the Github page I can't find a single mention anywhere of it actually getting used.

Thumbnail
github.com
70 Upvotes

My Core One+ arrived last week so I'm not quite ready to volunteer as a guinea pig, but if this works as promised, I'll buy an overpriced RPi in a heartbeat.

While I'm not fussed about Klipper vs. Marlin 2.0 in general so long as my prints are decent, I'd give my left nut to get Fluidd back as my primary interface.


r/prusa3d • • 22h ago

Panda breath for core one

Thumbnail
gallery
65 Upvotes

I saw that someone printed a side panel for the panda breath. Well after some modifications to their files, I thought it was good enough to send over to send cut send to have it cut out of 1.5mm metal.

It fits!

Now to print brackets and bolt it all up!

Original design:

https://www.printables.com/model/1742102-panda-breath-for-prusa-core-one


r/prusa3d • • 14h ago

Layer shifts and homing failures after XL+ upgrade

Post image
13 Upvotes

Hi, I'm hoping someone here can help me make sense of this. Here's the full timeline:

Background: I'm an early Prusa XL owner. My original extruder started throwing extruder motor errors and heatbreak thermistor communication errors, which were diagnosed as a connection issue with the Dwarf board. Rather than repair, I decided to buy the XL+ upgrade kit (which cost nearly as much as a Snapmaker U1 on sale...).

The upgrade: I performed the upgrade two days ago and everything went smoothly: 5 new extruders, new belt, new PCCF parts, firmware 8.0.1.

First print: PETG using the new XL+ profile. Flawless, fast, perfect.

Then I updated to 8.0.2, and things went downhill:

  • Second print (PLA): layer shifts almost from the first layer, plus homing problems. Sometimes it fails to find the endstop, sometimes it won't calibrate the X or Y axis.
  • Full factory reset + full calibration: same issue. Constant homing problems, layer shifts from the start of the print.
  • Extensive troubleshooting in between (with Prusa support involved): multiple belt calibrations, frame squareness checks, pulley checks, I counted the belt teeth on both axes, verified the tightness of the pulley screws, and applied fresh lubrication. No change.
  • Reverted to firmware 6.10.3: same issue.

I've attached a photo of a print where you can clearly see the layers drifting away, one after another. Something is wrong and the reference point keeps shifting with each layer.

After another conversation with Prusa support, their suggestion is to replace both core XY motors. I'm pretty frustrated by this, as that's yet more money on top of an already expensive upgrade, especially since both motors worked perfectly fine before. If the original motors are too weak for the new belts, that's something Prusa should address, not something the customer should pay for!

So, my questions: What would you try next? Has anyone seen this kind of behavior after the XL+ upgrade?


r/prusa3d • • 1d ago Bravo

Found my old external drive from architecture school… recovered 1300 low poly miniature people models and here they are for free !

Thumbnail
gallery
229 Upvotes

A few months back I posted here about an old external drive I found from my architecture school days, with a few hundred low poly miniature people on it. A lot of you grabbed them, so thanks for that.

Since then I kept digging through old backups and found more of them. The collection is now at around 1300 figures.

This time I didn’t just dump the files. I went through the whole lot: removed the duplicates and the broken meshes, fixed what needed fixing, and then rescaled every single figure into eight separate scales, from 1:18 all the way down to 1:200.

So you don’t have to touch the scale slider at all, you just pick the folder for the scale you’re working in.

The scales and roughly how tall the figures come out:

- 1:18 at 96 mm, for display pieces and action figure dioramas
- 1:24 at 72 mm, G scale railways and bigger dioramas
- 1:43 at 40 mm, diecast car scenes and O scale
- 1:50 at 35 mm, architectural models and construction scenes
- 1:64 at 27 mm, S scale and 1:64 layouts
- 1:87 at 20 mm, HO railways, the one most people want
- 1:100 at 17 mm, architectural massing models
- 1:200 at 9 mm, urban planning and skyscraper models, better on resin

Poses are the usual architecture library stuff: standing, walking, sitting, squatting, kneeling, leaning, lying down, groups and couples. There’s also construction workers, car mechanics, a welder, a photographer, soldiers, kids and list goes on.

All photos here were taken by me, and by people who downloaded the pack and shared their results with me. Thanks to everyone who sent one in !

Here's the link!
Printables

Free, same as before. Give them as much use as I did !


r/prusa3d • • 1d ago

Prusa Connect Local is here — running in Docker with 3 simulated printers - this is very cool!

Thumbnail
gallery
59 Upvotes

Prusa released the first public beta of Connect Local, and I had to see if I could get it running on my Unraid server.

Built the Docker image from their GitHub source, deployed it through Docker Compose, and had the web interface running without much trouble. They even included a printer simulator, so I spun up virtual versions of my actual lineup: a 5-tool XL, CORE One+, and CORE One L.

All three are connected and reporting temperatures, filament, and status. Haven't moved any of my actual printers over yet. I want to spend some time comparing it with the cloud version first.

A few things that caught my attention: local storage and print history, a REST API, support for Authentik/OIDC, and a surprisingly configurable setup wizard. I'm also planning to put it behind Traefik.

Still very early beta, but pretty cool to see Prusa offering a self-hosted alternative.

GitHub: https://github.com/prusa3d/prusa-connect

UPDATE: How I installed Prusa Connect Local on Unraid with Docker Compose and simulated printers

For anyone interested in trying this themselves, here's how I got Prusa Connect Local running on Unraid, including the printer simulator.

This uses Prusa Connect Local v0.1.0-beta.1, the first public beta released November 17, 2026.

I built both Docker images locally from the official GitHub repository and deployed everything through the Unraid Docker Compose Manager plugin. The same approach should work with standard Docker Compose on other Linux systems.

The deployment consists of four containers:

  • Prusa Connect Local: The main application and web interface.
  • XL simulator: A virtual Prusa XL.
  • CORE One simulator: A virtual CORE One.
  • CORE One L simulator: A virtual CORE One L.

These are simulated printers, so you can explore the application without moving your real printers away from cloud Prusa Connect.

Step 1: Clone the official repository

SSH into your Unraid server and create a directory for Prusa Connect.

I'm using Unraid's standard /mnt/user/appdata location. You can adjust this if your appdata share is stored elsewhere.

mkdir -p /mnt/user/appdata/prusa-connect
cd /mnt/user/appdata/prusa-connect

git clone https://github.com/prusa3d/prusa-connect.git source

cd source
git checkout v0.1.0-beta.1

Official repository:

https://github.com/prusa3d/prusa-connect

Step 2: Build the Prusa Connect Docker image

The repository includes an application Dockerfile.

From the source directory, run:

docker build \
  --build-arg BUILD_VERSION=0.1.0-beta.1 \
  -f docker/server/Dockerfile \
  -t prusa-connect:0.1.0-beta.1 .

This builds the application image locally.

Step 3: Build the printer simulator

Prusa includes a Go-based printer simulator under tools/printersim.

I built it as a separate Docker image so I could run multiple virtual printers alongside the application.

While still in the repository's source directory, create a new Dockerfile:

nano Dockerfile.simulator

Paste:

FROM golang:1.26.11-trixie AS builder

WORKDIR /app
COPY . .

RUN CGO_ENABLED=0 GOOS=linux GOARCH=amd64 \
    go build -o /printersim ./tools/printersim

FROM alpine:3.22

RUN apk add --no-cache ca-certificates

COPY --from=builder /printersim /usr/local/bin/printersim

USER 10001:10001

ENTRYPOINT ["/usr/local/bin/printersim"]

Save the file, then build the image:

docker build \
  -f Dockerfile.simulator \
  -t prusa-printersim:0.1.0-beta.1 .

You can verify the simulator and see the supported printer models with:

docker run --rm \
  prusa-printersim:0.1.0-beta.1 -models

Supported models include XL, CoreOne, CoreOneL, MK4S, MINI, and several others.

Step 4: Create persistent application directories

The application needs persistent storage for its configuration, databases, and files.

BASE="/mnt/user/appdata/prusa-connect"

mkdir -p "$BASE"/{config.d,data,files,storage,tmp}

Set ownership for the application's writable directories:

chown -R 10001:10001 \
  "$BASE/config.d" \
  "$BASE/data" \
  "$BASE/files" \
  "$BASE/storage" \
  "$BASE/tmp"

The application uses UID/GID 10001:10001.

The original config.yaml from the cloned repository will be mounted read-only, while the remaining directories provide writable persistent storage.

Step 5: Create the Docker Compose stack

In Unraid, open the Compose tab, create a new stack named prusa-connect, and edit the Compose configuration.

Here is the complete Compose file, configured for three virtual printers.

services:
  prusa-connect:
    image: prusa-connect:0.1.0-beta.1
    container_name: prusa_connect
    restart: unless-stopped
    pull_policy: never

    ports:
      - "8095:8080"

    volumes:
      - /mnt/user/appdata/prusa-connect/source/config/config.yaml:/config/config.yaml:ro
      - /mnt/user/appdata/prusa-connect/config.d:/config/config.d
      - /mnt/user/appdata/prusa-connect/data:/data
      - /mnt/user/appdata/prusa-connect/files:/files
      - /mnt/user/appdata/prusa-connect/storage:/storage
      - /mnt/user/appdata/prusa-connect/tmp:/tmp

    security_opt:
      - no-new-privileges:true

    cap_drop:
      - ALL

    read_only: true

    healthcheck:
      test: ["CMD", "/prusa_connect", "core", "healthcheck"]
      interval: 30s
      timeout: 5s
      retries: 3
      start_period: 30s

    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "5"

  simulator-xl:
    image: prusa-printersim:0.1.0-beta.1
    container_name: prusa-sim-xl
    restart: unless-stopped
    pull_policy: never

    command:
      - -url
      - "http://prusa-connect:8080"
      - -model
      - XL
      - -serial
      - XL5T
      - -count
      - "1"
      - -cameras=false
      - -print-time
      - 5m

    depends_on:
      prusa-connect:
        condition: service_healthy

  simulator-core-one:
    image: prusa-printersim:0.1.0-beta.1
    container_name: prusa-sim-core-one
    restart: unless-stopped
    pull_policy: never

    command:
      - -url
      - "http://prusa-connect:8080"
      - -model
      - CoreOne
      - -serial
      - COREONEPLUS
      - -count
      - "1"
      - -cameras=false
      - -print-time
      - 5m

    depends_on:
      prusa-connect:
        condition: service_healthy

  simulator-core-one-l:
    image: prusa-printersim:0.1.0-beta.1
    container_name: prusa-sim-core-one-l
    restart: unless-stopped
    pull_policy: never

    command:
      - -url
      - "http://prusa-connect:8080"
      - -model
      - CoreOneL
      - -serial
      - COREONEL
      - -count
      - "1"
      - -cameras=false
      - -print-time
      - 5m

    depends_on:
      prusa-connect:
        condition: service_healthy

A few notes about the Compose configuration:

  • The application is accessible on port 8095. Change this if it conflicts with another container.
  • pull_policy: never ensures Docker uses the locally built images.
  • All three simulator containers communicate with the Prusa Connect service over the Compose network.
  • Each simulator has its own model and serial prefix.
  • The simulator is configured to use a five-minute simulated print duration.
  • Simulated cameras are disabled.
  • The application uses persistent storage and a read-only root filesystem.

You can remove the simulator containers entirely if you only want the main application.

You can also create additional simulators by duplicating an existing service, changing its name, printer model, and serial prefix.

Step 6: Start the Compose stack

From Unraid's Compose tab, select the new stack and click Compose Up.

If using standard Docker Compose from the directory containing the Compose file:

docker compose up -d

Verify the containers:

docker ps --filter "name=prusa"

You should see:

prusa_connect
prusa-sim-xl
prusa-sim-core-one
prusa-sim-core-one-l

The Prusa Connect container should report healthy once initialization completes.

To check the application logs:

docker logs prusa_connect --tail 50

To check the simulators:

docker logs prusa-sim-xl --tail 30
docker logs prusa-sim-core-one --tail 30
docker logs prusa-sim-core-one-l --tail 30

Step 7: Complete the initial setup

Open a browser and navigate to:

http://YOUR-UNRAID-IP:8095

The initial setup wizard should appear.

I selected the Advanced Setup option to explore the available configuration settings.

My choices included:

  • Create a local administrator account.
  • Require users to sign in.
  • Require administrator approval before new printers can join.
  • Enable persistent file storage and print history.
  • Disable automatic application upgrades because I'm managing the Docker images manually.
  • Disable optional diagnostic uploads.
  • Leave the application's built-in TLS disabled for the initial local deployment.

Once the setup is complete, you'll reach the main dashboard.

Step 8: Approve the simulated printers

The three simulator containers should begin communicating with Prusa Connect.

Because I enabled printer approval, each virtual printer initially appeared as a pending registration.

After approving them, all three were connected and visible in the Printers section.

I renamed my simulated printers:

  • XL
  • COREOne +
  • COREOne L

The simulator currently uses the CoreOne model for my virtual CORE One+, since there's no separate CoreOne+ model identifier in the available models.

Also, although I selected the XL model, I haven't verified whether the simulator supports all five individual toolheads.

Note about connecting physical printers

This setup uses Docker bridge networking, which means local network discovery (mDNS/DNS-SD) may not reach physical printers on your LAN.

The simulated printers work because they communicate directly with Prusa Connect over Docker's internal network.

If you plan to connect physical printers, you'll need to make sure they can reach the server from their network. Depending on the printer's firmware and available configuration options, this may involve manually specifying the server address, configuring DNS, or adjusting Docker networking.

Printers on separate VLANs may also require additional firewall rules or discovery configuration.

I haven't tested physical printer connectivity yet, so this guide only confirms the application and simulated printers are working.

Step 9: Explore the interface

At this point, you should have Prusa Connect Local running with three simulated printers.

My virtual printers appear connected, show idle status, and report simulated temperatures and filament information.

The application includes a surprising number of features for an initial beta:

  • Dashboards and printer monitoring.
  • Print job tracking and history.
  • File uploads and local storage.
  • User management.
  • API credentials.
  • Server health and diagnostic information.
  • An extension marketplace.

The marketplace already lists official extensions for Fleet stats, Materials, 3MF projects, printer logs, Parts, and Server slicing.

Final thoughts

Everything has been running surprisingly well for a first public beta.

The server reports healthy, all three simulated printers are connected, and the web interface has considerably more functionality than I initially expected.

I'm keeping my physical printers connected to cloud Prusa Connect for now, while I experiment with the local version.

Next on my list is testing simulated print jobs, the extension marketplace, and the API.

Hopefully this helps anyone who wants to experiment with Prusa Connect Local without changing anything on their actual printers.

Official repository: https://github.com/prusa3d/prusa-connect

Version tested: v0.1.0-beta.1


r/prusa3d • • 1d ago

Local Connect + more!

55 Upvotes

Love it! They just dropped a big bomb, in da face of people complaining about pricing and let's just get the cheapest crap out there. You want real privacy, openess and quality products, here they are: https://www.youtube.com/watch?v=wuoaQA5HGOU


r/prusa3d • • 20h ago

AI New User Interface Design

Thumbnail
gallery
11 Upvotes

Over the last few days I’ve been working with Claude to design a new touchscreen interface for my CORE One INDX. I now have a working build, based on firmware 8.0.1 with several custom screens, flashed on my printer and running.

This is purely a UI pass. The underlying firmware code is unchanged, so the printer’s motion, thermal and safety logic all behave as stock.

I’d love your thoughts, and I’m open to requests for screens or features you’d like to see.

Heads up before you try this yourself: the printer only accepts Prusa-signed firmware out of the box. To flash an unsigned build, you have to break the small “appendix” seal on the xBuddy board. Prusa says breaking the seal won’t void your warranty, but they disclaim liability for any damage or harm a printer with a broken seal may cause. Only flash firmware from sources you trust, and read through what you’re installing. prusa3d

What’s in this build

Everything is based on Prusa’s stock firmware v8.0.1. Only the screens changed, and the motion, thermal and safety code is untouched.

New or reworked screens

  • Home tool rack: 8 tiles under the header, one per tool. Each shows the tool number, a colour swatch if one was set when loading, and the filament name (or “--” if empty). The selected tool has an orange outline, switched-off tools are dimmed, and tapping a tile opens that tool’s screen. The six stock buttons stay, shifted down to clear the footer.
  • Printing screen with a tool strip: all tools visible while a print is running.
  • Pre-print tool mapping: a screen for checking which tool is assigned to which filament before you start.
  • Tool detail: a per-tool page that reuses the stock screen, with plainer-language rows.
  • INDX health and calibration: toolchanger status that’s normally scattered across menus, in one place.
  • Calibration recovery: a screen for when tool-offset calibration fails.

Design constraints I worked within

  • Each screen has to fit in a fixed 4,400-byte memory block on INDX printers, so the rack is one custom-drawn widget rather than dozens of buttons and labels.
  • Home’s background jobs are preserved: USB insert/remove handling, one-click print of the newest file, and the Wi-Fi credentials check.
  • The changes only apply to INDX builds, and other printers keep the stock layout.

r/prusa3d • • 1d ago

Prusa Connect Local is now in open beta... looks like

Thumbnail
github.com
129 Upvotes

Prusa Connect is a server for your 3D printers that you run yourself. It is a single Go binary with the web app inside, built for Linux, Windows, macOS and the Raspberry Pi. Download it, start it on any computer you have, and open it in a browser.

  • No cloud. Your printers connect to your own server over your own network, and people sign in with accounts that live on that server.
  • Your data stays with you. Accounts, printers, print history and print files are kept on the machine the server runs on.
  • Not only Prusa. The driver for Prusa printers is built in. Drivers add printers of other makers, and anybody can write one.
  • Open to your own tools. A REST API, live events and MQTT give other programs the same data the web app shows.

Warning

Prusa Connect is in public beta. The releases are 0.x pre-releases, and the configuration, the API and the extension SDK can still change from one release to the next. Back up your data before you update.

You can't use Connect Local and Connect Cloud at the same time btw


r/prusa3d • • 1d ago

INDX 100k club

Post image
52 Upvotes

Made it into the 100k club. Anyone else here? Been running basically 24/7 since I built this in early August.

It's a workhorse. Super happy with this machine, making great parts constantly.


r/prusa3d • • 1d ago

Maintenance for Prusa Connect Local is live in the marketplace (probably the first extension, therefore "yay")

42 Upvotes

Huge Update: https://www.reddit.com/r/prusa3d/comments/1xyn0nv/comment/19st2f54la2hs/

Hi everyone,

My extension Maintenance is now live in the marketplace:

https://plugin-marketplace.prusa3d.com/connect/extensions/com.github.aux.singlergold2.maintenance

It is probably the first community extension for Prusa Connect Local, so here is what it does in a nutshell: it counts the print hours of each printer and tells you when a maintenance task is due.

https://imgur.com/p7eOtNj

Every printer gets its own Maintenance tab with its counter, the hours since the last check, and the tasks that are due. You type the printer's own counter in once, as 343 or 14d 7h, and from then on both counters move with every print. A CORE One starts with the schedule from the Prusa Knowledge Base: 200 hours for axes, belts, fans and extruder, 600 for the connectors, 90 days for the rail, 5000 hours for a hardened steel nozzle.

The Maintenance page in the sidebar holds one schedule for the fleet, Done asks before it starts the next interval, and a dashboard card shows what is due across all printers.

https://imgur.com/PR9l08y

The per-tool hours come from the G-code of finished prints, .gcode and .bgcode, and are meant as an indication, not a measurement. Each tool can be reset after a nozzle change.

Source, issues, and the manual install:

https://github.com/SinglerGold2/maintenance

If someone here runs a CORE One with INDX, I would love a look at whether the split across several nozzles looks plausible; I could only test it on a single-tool machine.