Benachrichtigungen
Alles löschen

Printing with Prusa PETG-CF on Core One  

  RSS
DMartin
(@dmartin)
Active Member
Printing with Prusa PETG-CF on Core One

How do I get the printer to recognise a PETG-CF bgcode file produced by Prusa slicer?  I did select in the slicer "Prusament PETG Carbon Fiber".  But the printer firmware doesn't have a matching filament type it seems.   (I am using a hardened nozzle. )

Veröffentlicht : 11/11/2025 8:10 pm
Walter Layher
(@walter-layher)
Noble Member
RE: Printing with Prusa PETG-CF on Core One

You can add a user profile for the filament on the printer menu with the temperature specs for nozzle, bed and probing temperatures and an appropriate name. Somewhere in the filament menu, manage filaments, or something like that.

Veröffentlicht : 11/11/2025 9:39 pm
hyiger
(@hyiger)
Prominent Member
RE: Printing with Prusa PETG-CF on Core One

The matching filament type is simply "PETG" 

Veröffentlicht : 11/11/2025 9:43 pm
DMartin
(@dmartin)
Active Member
Themenstarter answered:
RE: Printing with Prusa PETG-CF on Core One

 

Posted by: @hyiger

The matching filament type is simply "PETG" 

Maybe, but isn't that going to have the wrong temps for PETG-CF?  Perhaps I can go and change them, but then that messes up any standard PETG I want to print?

Veröffentlicht : 11/11/2025 10:06 pm
hyiger
(@hyiger)
Prominent Member
RE:

 

Posted by: @dmartin

 

Posted by: @hyiger

The matching filament type is simply "PETG" 

Maybe, but isn't that going to have the wrong temps for PETG-CF?  Perhaps I can go and change them, but then that messes up any standard PETG I want to print?

The temperature the filament prints at is set in PrusaSlicer for your filament profile, not the printer firmware. The firmware temperature is only used for load/unload/purging filament etc. Otherwise you can create a custom filament setting. However the set of filament types in the Filament properties in PrusaSlicer is fixed. So if you create a PETG-CF filament in firmware, it will trigger a "wrong filament" loaded warning that you have to manually ignore. It's just better to set it to PETG. 

Diese r Beitrag wurde geändert Vor 3 days von hyiger
Veröffentlicht : 11/11/2025 10:39 pm
Walter Layher
(@walter-layher)
Noble Member
RE: Printing with Prusa PETG-CF on Core One

I did create custom profiles some time ago for PCTG on my printers. This previous posting has photos of the menu screen for this:

Veröffentlicht : 11/11/2025 10:43 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Printing with Prusa PETG-CF on Core One

 

Posted by: @hyiger

 

Posted by: @dmartin

 

Posted by: @hyiger

The matching filament type is simply "PETG" 

Maybe, but isn't that going to have the wrong temps for PETG-CF?  Perhaps I can go and change them, but then that messes up any standard PETG I want to print?

The temperature the filament prints at is set in PrusaSlicer for your filament profile, not the printer firmware. The firmware temperature is only used for load/unload/purging filament etc. Otherwise you can create a custom filament setting. However the set of filament types in the Filament properties in PrusaSlicer is fixed. So if you create a PETG-CF filament in firmware, it will trigger a "wrong filament" loaded warning that you have to manually ignore. It's just better to set it to PETG. 

@hyiger, this isn't correct (added bold section above) .  It looks like a fixed list in the slicer but you can add your own.  Just click into the 'dropdown' and you can type.

However Id agree with the just use PETG as the temps used for loading etc will be perfectly fine for the filament.

Veröffentlicht : 12/11/2025 7:26 am
DMartin
(@dmartin)
Active Member
Themenstarter answered:
RE: Printing with Prusa PETG-CF on Core One

Thanks all, that's very useful.  Building on what you've done I think I might have cracked it - with one provisio (see later).

There are 2 parts to the equation, the printer firmware and the slicer. For success, the printer needs the slicer's BCCODE reference to the filament to match the printer's.   As far as I can see it's the name used that's important, eg "PETG" on both sides.  So ... the slicer has a "PETG Carbon Fiber" preset but if you go to the ADVANCED tab you'll see the name is "PETG".  You can overwrite that name (I used "PETG-CF") with a different name.   Then ... on the printer go to the filament menus -> Manage -> Edit,  go to an unused @xxxx name and edit it, changing (in this case) the name to "PETG-CF".  Obviously you can copy the bed and nozzle temps from the slicer preset here too. 

Then  I think we are good to go, with separate PETG and PETG-CF presets/profiles on both slicer and printer.

The one proviso that occurs to me is that if Prusa update slicer presets (as I assume they do occasionally), I don't know if the PETG-CF preset that I edited would get updated (although the only change was the name changed to PETG-CF from PETG).

 

 

 

Veröffentlicht : 12/11/2025 8:21 pm
hyiger
(@hyiger)
Prominent Member
RE: Printing with Prusa PETG-CF on Core One

 

Posted by: @neophyl

 

@hyiger, this isn't correct (added bold section above) .  It looks like a fixed list in the slicer but you can add your own.  Just click into the 'dropdown' and you can type.

Wasn't aware of that, thanks. Most UI's would make it more obvious that a combobox was editable. 

Veröffentlicht : 12/11/2025 8:24 pm
hyiger
(@hyiger)
Prominent Member
RE:

 

Posted by: @dmartin

The one proviso that occurs to me is that if Prusa update slicer presets (as I assume they do occasionally), I don't know if the PETG-CF preset that I edited would get updated (although the only change was the name changed to PETG-CF from PETG).

As long as you don't detach from the system preset. If you wish to detach, i.e. you don't want Prusa changing your settings, then in Filaments Dependencies section, you can  click on "Detach from system preset" on the right. 

Veröffentlicht : 12/11/2025 9:14 pm
DMartin
(@dmartin)
Active Member
Themenstarter answered:
RE: Printing with Prusa PETG-CF on Core One

 

Posted by: @hyiger

 

Posted by: @dmartin

The one proviso that occurs to me is that if Prusa update slicer presets (as I assume they do occasionally), I don't know if the PETG-CF preset that I edited would get updated (although the only change was the name changed to PETG-CF from PETG).

As long as you don't detach from the system preset. If you wish to detach, i.e. you don't want Prusa changing your settings, then in Filaments Dependencies section, you can  click on "Detach from system preset" on the right. 

 

Ah, like that!  Excellent, thanks.  

Veröffentlicht : 12/11/2025 9:18 pm
Mercur12
(@mercur12)
Trusted Member
RE:

I never made any filament-assignments at my printers. I think this is obsolete. All Filament-settings (temperature, speed etc) are already in the G-code-file build from the slicer by specifiing the filament-settings (profiles from prusa or by your own).

Right ?

Diese r Beitrag wurde geändert Vor 1 day von Mercur12
Veröffentlicht : 13/11/2025 6:52 pm
Walter Layher
(@walter-layher)
Noble Member
RE: Printing with Prusa PETG-CF on Core One

Basically, yes. But if you try to print with a filament type that is only known to PrusaSlicer and not to the printer, e.g. PCTG, you'll get an error "wrong filament type" or something like that. You can skip the error, of course. Or you can create a profile on the printer if you intend to use the filament type regularly afterwards and want to avoid skipping the error every time.

Veröffentlicht : 13/11/2025 7:27 pm
hyiger
(@hyiger)
Prominent Member
RE: Printing with Prusa PETG-CF on Core One

 

Posted by: @mercur12

I never made any filament-assignments at my printers. I think this is obsolete. All Filament-settings (temperature, speed etc) are already in the G-code-file build from the slicer by specifiing the filament-settings (profiles from prusa or by your own).

Right ?

Filament assignment at the printer does two things:

  1. Sets a nominal nozzle and bed temperature for loading, unloading and purging the filament. This is completely independent of what is being printed. 
  2. Creates a safeguard against slicing for the wrong type of filament. That is, you loaded PLA, told the printer it's PLA but sent it g-code for PETG. 

Presumably, once OpenPrintTag is fully available, manually setting this should not be needed. I just attach my spool and the printer is automatically setup. Of course, manual intervention will still be needed for spools that don't have a RFID tag. 

Veröffentlicht : 13/11/2025 7:34 pm
Walter Layher
(@walter-layher)
Noble Member
RE: Printing with Prusa PETG-CF on Core One

Also, with a pre-existing profile you have the ability to pre-heat the printer (which is good practice for some filament types) with the correct temperature for this filament and load the filament with the correct nozzle temperature.

Veröffentlicht : 13/11/2025 7:35 pm
Mercur12
(@mercur12)
Trusted Member
RE: Printing with Prusa PETG-CF on Core One

Ok, pre-heat is an argument (thx Walter). 

During the last 3 years I never had this message ("wrong filament type" or something like that). But from the beginning, i own a MMU3.

Is that the difference, that this message is only shown in Non-MMU configuration ? 

Veröffentlicht : 14/11/2025 7:08 am
Mercur12
(@mercur12)
Trusted Member
RE: Printing with Prusa PETG-CF on Core One

I#m sorry,  but the edit of my post was cut of. So here is the complete post. Bad that I can't delete the other post.

Okay, preheating is a valid point (thanks @Walter), and protective measures are another (thanks @Hyiger).

I've never seen this message ("wrong filament type" or something similar) in the last three years. But I've also never specified the filament type in the printer. I've owned an MMU3 from the beginning, though.

Is the difference that this message only appears in the non-MMU configuration?

Otherwise: If you define the filament type in the printer (from the predefined types) and specify a different type in the G-code, the message is correct.

However, if you don't specify a type in the printer, there's no conflict.

The printer firmware doesn't automatically check the filament type if it's not explicitly specified.

Aside from the points mentioned above, I think the problem is user-generated.

Veröffentlicht : 14/11/2025 7:27 am
Teilen: