And now Prusa, of all companies, is the first consumer 3D printing vendor to offer subscriptions if you want more storage space or better video streaming?? https://subscription.prusa3d.com/

This sounds like a great way to generate rather limited income but alienate a lot of longstanding users. How does this align with your "you buy it, you own it, no strings attached" marketing message? Yes, I get it, users still own their printers and basic functionality remains free (for now). But can we talk about "mixed messages" for a moment?

IMG_0602

vielleicht stelle ich mich ja etwas blöd an, aber ich hatte es so verstanden, dass mit der Einführung des Core One + auch für den normalen Core One die automatische Öffnung und Schließung des oberen Ventilationsgrills eingeführt wurden.

Das Update hatte ich vor langer Zeit gemacht und seitdem auch schon wieder öfters gedruckt. Der Drucker befindet sich somit auf dem neuesten Stand.

Leider kann ich es jedoch nicht beobachten, dass er selbstständig den Ventilationsgrill öffnet und schließt. Habe ich dahingehend etwas falsch verstanden oder muss man noch irgendwo was aktivieren? Ich habe die Einstellung durchsucht und konnte weder im Slicer noch am Drucker selbst nichts finden.

Für Ideen, was ich noch machen könnte, wäre ich sehr dankbar.

Vielen Dank für Eure Bemühungen!

I have an XL 5-tool, currently with two 0.4mm Obxidian 500 high-flow nozzles, two 0.4mm Obxidian high-flow nozzles, and a 0.6mm Obxidian high-flow nozzle. I have a general preference for printing with PETG, and I'm hoping to play with the UltraGlow and PC-CF filaments as well.

I had been having significant problems with all varieties of PETG filament buildup around nozzles, that buildup causing printhead crashes with prints, buildup dropping onto prints and creating a raft of weird problems both structural and aesthetic, problems with gaps in layers where filament extrusion wasn't "gripping" to the underlying and adjacent print layers, and a significant amount of time and effort and filament reels being wasted in pursuit of "good enough".

I had tried all of the advice, from manipulation of the temperature of extrusion, significantly lowering the feedrate of filament, significantly lowering the printhead speeds, changing the fill types to avoid crossing, varying the extrusion percentage, lots of playing with retraction and wipe and Z-move settings. Nothing was giving me similar results to what I had been getting when I first assembled the printer, and everything was having similar problems. Reverting firmware didn't help either.

As it turns out, one of the few configuration items I did not play with was the "Pressure Advance" parameter, that is in the M572 GCode setting.

Following the suggestions here: https://www.printables.com/model/641490-prusa-slicer-pressure-advance-test I set up the test print with a range of parameter from 0.01 through 0.30 in a couple of prints. For my setup, the HF500 nozzles were looking best with M572 values in the 0.08 to 0.09 range, and looking noticeably poor in the 0.05-0.06 range, and from 0.12 upwards. This was using dried Prusament PETG in the SignalWhite flavour.

Checking the "Custom GCode" for the filament profile, I had seen that in the code there, if the nozzle was advertised as 0.04mm, that the value for Pressure Advance was being set at 0.53.

Setting that value in the custom code section to 0.09, and running a print through one of the normal slightly-modified print profiles that I had previously been having lots of trouble with, I ended up with a print that completed without blobs, that had a consistent surface finish, and that had a nozzle that was free of filament. I was really surprised at the difference this made..

Changing the parameter for other PETG filaments that had poor results previously, allowed similar high standards of completed test prints. 

I effectively have a printer that (assuming no bed adhesion issues, but that is another story!) is pretty much guaranteed to give me a print output that is what is expected, and without the problems that were present.

I am _happy_ now.

I've ordered the INDX upgrade for my CoreOne and I'm curious if my old nozzles are compatible with the INDX system or it uses different nozzles.

Does anyone have an answer? Thanks!

No matter what I've tried so far, it consistently fails "rew X-Axis u/50 mm/s", landing above the target <182,192> range.

1902.452s X-Axis Started

1902.555s enqueueing "G28 X I D P"

1902.555s X-Axis home single axis

1902.653s endstops hit: X:-1.76 Y:-3.16

1902.757s endstops hit: X:2.40 Y:-3.16

1902.788s X:180.40 Y:-3.16 Z:4.00 E:0.00 Count X:18040 Y:-316 Z:1600

1902.988s fwd X-Axis u/50 mm/s

1902.988s X:180.40 Y:-3.16 Z:4.00 E:0.00 Count X:18040 Y:-316 Z:1600

1907.004s endstops hit: X:-7.44

1907.054s X:-7.44 Y:-3.16 Z:4.00 E:0.00 Count X:-744 Y:-316 Z:1600

1907.054s X-Axis measured length = 188.239990mm out in range <182.000000,192.000000>

1907.088s rew X-Axis u/50 mm/s

1907.088s X:-7.44 Y:-3.16 Z:4.00 E:0.00 Count X:-744 Y:-316 Z:1600

1911.104s endstops hit: X:180.40

1911.154s X:180.40 Y:-3.16 Z:4.00 E:0.00 Count X:18040 Y:-316 Z:1600

1911.154s X-Axis measured length = 193.279999mm out of range <182.000000,192.000000>

I I've tried loosening/tightening the belt, using the belt tuner app, but I can only get the X-Axis measured length to vary by tiny amounts.

487.468s X-Axis measured length = 193.429993mm out of range <182.000000,192.000000>

1070.794s X-Axis measured length = 193.279999mm out of range <182.000000,192.000000>

1574.927s X-Axis measured length = 193.289993mm out of range <182.000000,192.000000>

1911.154s X-Axis measured length = 193.279999mm out of range <182.000000,192.000000>

Can anyone advise what I'm missing? Thanks in advance.

Any help is greatly appretiated!