Anyone have success working with FullControl gcode?

You can do some really interesting things with full control gcode but it is generated outside of the bambu slicer. The fullcontrol website can output gcode to throw on a SD card but I have not been able to get a successful print from it. Typically the print starts above the bed but I cant seem to figure out how to avoid this myself.

My goal is to test around with it and then try to make some vase models using fullcontrol.

https://fullcontrol.xyz

3 Likes

You will need to look at the gcode generated from the Bambu Studio to get the proper start and end gcode. Or look at the Machine GCode in the printer profile.

1 Like

I learned how to get the printer to print it, by storing the GCODE onto an SD card and running it from the printer. I had to load the filament - as there’s no filament loading done by the GCODE.
So my steps were…

  • create the model (I ran this at 200%, with very low fan, on the cool bed) - make sure you use the FullControl ā€œBambuLabX1ā€ printer setting!,
  • download/save the GCODE onto the sd card (root level was fine)
  • add the glue to the cool bed - these models have very low adhesion - so be warned!
  • use the HOME button to home the printer.
  • use the controls to load the filament into the nozzle (so that one can use the controls to squirt it out).
  • Run the GCODE, as is.

As I said, adhesion is low - the model started rocking at the one point where the bed is moved down for each layer - there are NO retractions - so it prints … very differently from using BambuStudio.

2 Likes

Is there an obvious reason why it’s not feasible to have FullControll generate the GCode and then edit that GCode with Bambu’s load and unload GCode? So basically just copy and paste the beginning and end of a standard Bambu GCode to the code generated by FullControl?

BambuStudio is more about compiling models into GCode, rather than converting Code to models. PrusaSlicer offers to GCode into an obj file, but then that gets sliced all over again, and it loses all the benefits of raw GCode.

Needless to say, GCode models are … niche. It’s pretty cool to be able to print them at all - and, if I knew enough of it, it should be easy enough to turn on the extruder, etc. But I just use the code as generated by FullControl - it doesn’t get touched by BambuStudio.

I did try unzipping a simple 3mf (which has the GCode in it), replacing the print section, re-md5 the whole thing, and … it didn’t really work for me.

To be frank, I was amazed I got the model above to print! It’s pretty weird - all the settings which Studio does are pretty cool.

I think a more possible approach would be for BambuLabs to incorporate fullcontrol into Studio altogether… After all, the basic primitives are pretty much ā€˜draw a line (at this heat, this temperature, this width, this thickness) from here (in 3d) to here (in 3d)’ (with cutting/retraction/etc functions on top). - and, while it’s not visible at the model level, the preview should be able to show it - and that would allow for us coders not to have to get close to the GCode itself - which is doing stuff that I don’t really want to have to deal with.

If you put it into Bambu Studio, send the print, cancel the print, then go into your recent prints you can select the one from FullControl and then choose which filament color. Worked for the pin support challenge.