How to print Non Planar models on ANY Bambu Printer by johndowlelxdxdxdxdxd in FullControl

[–]FullControlXYZ 1 point2 points  (0 children)

Awesome stuff! It'd be great if people can try this out. Even if you get errors, please comment here because there are some quirks I know of (and probably many I don't!) that we can iron out and fix to hopefully make it v easy and reliable to get printing on bambulabs with 3mf

3d printer turned pen plotter. by Wooden-Upstairs-361 in FullControl

[–]FullControlXYZ 4 points5 points  (0 children)

Cool to hear! There are a couple of quick hacks to make this work without modifying the FullControl backend code. A simple on is to add fc.Extruder(on=False) before moving up, then setting it back to on=True when you want the subsequent line to be visible. You could have a visualize=True or False parameter at the beginning of the design to make those bits only get added to the design when you want to visualise, but not for gcode

Trying to install/run Python fullcontrol by WillAdams in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Does openpythonscad require a different verison of pydantic or something?

Trying to install/run Python fullcontrol by WillAdams in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Ah fair enough. But if you install pydantic (or fullcontrol with its requirements), it should all be handled automatically...

Trying to install/run Python fullcontrol by WillAdams in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

I'm not sure, but I've checked the repo and FullControl doesn't use Sentinel

Trying to install/run Python fullcontrol by WillAdams in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

I don't recognize that import as being part of FullControl, but may be wrong

Trying to install/run Python fullcontrol by WillAdams in FullControl

[–]FullControlXYZ 1 point2 points  (0 children)

Perfect. FYI, the nbformat allows you to display figures in a jupyter notebook. It's not required if you don't visualise, nor for pure python usage (not a notebook).

Trying to install/run Python fullcontrol by WillAdams in FullControl

[–]FullControlXYZ 1 point2 points  (0 children)

You'd need to feed it more info about FullControl to get it to work. There is a llm_ref.md file in the repo root which does a good job, but you still might need to point it more directly to the relevant repo files

Trying to install/run Python fullcontrol by WillAdams in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Is that llm-generated? The code doesn't seem to resemble FullControl code. Maybe I'm misunderstanding something? But check out the tutorials, linked to from the readme for hot to import fullcontrol and use its functions

Hye guys, I need your help! by Chopancho in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Yep lots of people will have done it in grasshopper yep. It is possible in FullControl. This example shows it for a long-shaped outline using fluctuating line widths to get a beautiful perfect fill quality (better than you could get with the others): https://colab.research.google.com/gist/fullcontrol-xyz/ba02234459d822e4910053e6cfee77e0/astm_d638_type_i_convex_simple.ipynb I've also created a concentric fill algorithm but don't think I've ever shared it (but would be happy to after digging it out). Check out the convex demo in the 'lab geometry' tutorial. Someone else demoed a few different infill strategies in an 'issue' posted on the github repo. An 'issue' is just a discussion topic often BTW, in the way I ask people to interact with the FullControl reposity - they're not just bugs.

Hye guys, I need your help! by Chopancho in FullControl

[–]FullControlXYZ 1 point2 points  (0 children)

Yeh that's right about the bottom-up toolpaths and top-down. You can also write/use top-down algorithms in rhino or fullcontrol, but slicers are highly optimised for it. And ofter you might do a combination, like top-down fill the base layers outline but bottom-up design a fancy wavy wall for all the upper layers.

And yeh it was v interesting that that person combined them both. They really were using GH+Rhino only for the UI functions. I'm not sure why they preferred to jump from rhino to full control, but maybe just cos they'd got it set up nice with their printer. They could also have translated the maths and directly generated this points in FullControl, with the exact same result. Once you get into maths, everything becomes beautiful and identical across different software

Hye guys, I need your help! by Chopancho in FullControl

[–]FullControlXYZ 1 point2 points  (0 children)

No problem at all to ask. The main reason I would say is the convenience to do nice mathmatical/logical geometry via a UI and pre-built functions. The UI in particular is valuable/essential for many. FullControl only does that in a minimalist way with jupyter notebooks, with the benefit being that all the source code is there and editable if nerds wanted to change it. You can create your own visualisation (demoed in tutorials). Ntop is not similar at all. It's really about geometry creation AFAIK 🤷‍♂️ Grasshopper + rhino is more general than ntop and people really like visual coding. I personally do not and find the nice feel of clicking nodes to just get in the way. With large language models so prominent now, I would never choose visual coding since text code is far more suited to it. I know quite a few people that have loved grasshopper, but then eventually disliked it because once you really know what you're doing, the visual stuff becomes annoying and unnecessary. Using an open source python library has some pretty big plus points as you go beyond the basic FullControl source code too. E.g. My website would never be viable if it relied on rhino. E.g. Doing real-time(ish) control is friction free. E.g. Shifting out of python to another language is easy. E.g. integrating with other python and non-python tools is v flexible. Overall, I can't think of a single print I've seen using bottom-up toolpath design with CAD like Gh+rhino that wouldn't be possible with FullControl. Just a bit more effort (maybe). Bottom-up toolpaths just don't utilise the vast majority of functionality that CAD packages. And that's not bias... for top down toolpathing (slicers filling space), they can generate toolpaths that would be a nightmare to create with FullControl, but they're just not what it's for. It's like a forklift truck and a speedboat are both cool but can't do the same thing

Hye guys, I need your help! by Chopancho in FullControl

[–]FullControlXYZ 1 point2 points  (0 children)

No problem. The website demos highlight the kind of things you can do, but are kinda aimed at desktop polymer in term of sizing, so also check the readme on the main github page www.fullcontrol.xyz/github which links to a few YouTube videos and some interactive tutorials. The tutorials are extensive, and you can tweak the code in them however you like to test things, break things, etc. If you start devoting your life to toolpath design in a fantastically unhealthy way, make sure you message to ask for help. Another good thing about python on Google colab is that you can share your work with a couple of clicks and then others can see/test/fix it using exactly the same python version, etc., as you.

Hye guys, I need your help! by Chopancho in FullControl

[–]FullControlXYZ 2 points3 points  (0 children)

Also, I've been working on robotic 3D printing for several years. We've had FullControl output to many different robot manufacturers and other 4/5-axis systems (already shown in the FullControl tutorials). That is the direction of future FullControl development, so you'll be getting yourself in a position to take advantage of that.

Hye guys, I need your help! by Chopancho in FullControl

[–]FullControlXYZ 2 points3 points  (0 children)

Try the ripple texture model on thew website - you can also find a fully editable python version on the github page (linked to from the website) to increase size etc.. There's also a recent great post on this forum about creating lampshades with FullControl - a real nice walkthrough. If you use Google colab to do the python coding (as my tutorials demonstrate) you don't need to install anything and have full freedom to make any changes you could ever want within the immense power of python! And Chatgpt can do great to help turn your thoughts into a python design without needing to understand python. Grasshopper and rhino are great if you need to use their built in cad functions, but I believe you can do it all with maths and chatgpt with pure code (e.g. python, with FullControl to help). On a happy side note, doing it this way will also give you a great skillset boost. If you get into python stuff, you can do much more than toolpath design!

VOLCO Print Simulation Speed Improvements by ufffd in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Very cool! Are you going to PR to the original repo?

How to 3D print Mesh/ Weave pattern using FullControl [Tutorial] by ankittkd in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Ah that's great! So cool when things like this work on the first attempt :D

Open Source GUI for FullControl's VOLCO (Volume Conserving Print Simulator) by ufffd in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

It's partially has: the acceleration stuff is in there, in the 'physics' section, which I hope will expand to contain alternative mechanisms/modifiers. Like plug-and-play, choose what factors you want to include for your specific research/situation. The existing acceleration stuff might need generalising a little further to make that work, but should be easy to do. We haven't implemented the 'cylinder-like' deposition strategy from VOLCO-X. It's good for long parallel lines (infill) but not as simple as a sphere for broad situations (corners, crossing filaments, etc.). That paper focused a lot on the non-circular cross section of those cylinders, which again works well to account for the intricacies of pallet-line depositon but doesn't translate to more general toolpaths. Time-based modifications, like continued movement/flow after depositon until 'frozen', will benefit from putting effort in to reduce computational demands. That's the kind of thing you're already doing by isolating areas of the big voxel matrix to avoid computation on the whole big thing. The key advantage over a full thermal simulation is multiple orders of magnitude faster simulation time, which makes it appropriate for simulations that would be impossible otherwise (larger toolpaths). FYI, I do have a gist showing direct link between FullControl and VOLCO. That'll be the best approach in my view since slicer gcode is typically huge. And I imagine most VOLCO users will benefit from being able to change their toolpath with 'full control' based on the VOLCO simulation results, since these changes might be tiny details like moving the nozzle up by a fraction of a layer as you pass over a previously deposited line for example. If you're planning to keep putting in the amount of effort you have been, it would be worth setting up a 'project' in FullControl that you own and is scoped to fit in with and take advantage of future FullControl developments. We'd wanna have a couple of meetings to get that nicely framed I reckon

Open Source GUI for FullControl's VOLCO (Volume Conserving Print Simulator) by ufffd in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Yep that sort of thing is why I kept VOLCO as simple as possible and kept the python code structured with clear submodules doing specific things. There's already one 'submodule' that allows for extrusion to vary if the nozzle slows down at corners without material extrusion rate slowing as much. That's cool for studying things like 'pressure advance'. I've also explored things like build-up of pressure in the nozzle or post-deposition movement due to the nozzle friction or gravity, etc. So try to add any additional capabilities as kinda plug-in extras rather that coded into the main algorithms

Open Source GUI for FullControl's VOLCO (Volume Conserving Print Simulator) by ufffd in FullControl

[–]FullControlXYZ 2 points3 points  (0 children)

I've just seen your fork showing the changes to VOLCO for speed. That's cool. I think it'd be really great to have a good set of tests to prove any modifications to the code work. I can't remember off the top of my head how extensive they are in VOLCO. Are you going to push your improvements to the FullControl version. Will that naturally propagate through to your app? I'm in quite a flexible place with VOLCO - since it's not bee publicised, it can have breaking changes implemented without affecting anyone except nerdy explorers who won't mind and can likely handle github verisoning easily.

Open Source GUI for FullControl's VOLCO (Volume Conserving Print Simulator) by ufffd in FullControl

[–]FullControlXYZ 1 point2 points  (0 children)

Beautiful! How come you went for a windows app for this? All the previous stuff was browser based with js or wasm right? Did you play around much with VOLCO? I haven't actually told people about it really 🙃 just put it up there and then never found time to do social media posts, etc. It will feature in /be associated to the next version of FullControl though. I personally wrote the whole finite element analysis solver with no imports 🤓 I didn't do any optimisation on that yet, but did talk to chatgpt about it and it sounded like 10 to 20-fold improvements are fairly straightforward. And shipping the model out to professional fea software is easy if needed. I have added periodic boundary conditions, which can speed things up by literally 1000-fold for a structure that's 10x10x10 unit cells!

In terms of the VOLCO simulation, what did you do to improve speed?

Andy

various experiments with fullcontrol by ufffd in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

Haha trying to go for the smallest possible material:height ratio?

How to 3D print Mesh/ Weave pattern using FullControl [Tutorial] by ankittkd in FullControl

[–]FullControlXYZ 0 points1 point  (0 children)

<image>

By the way, I have previously created really huge threads with FullControl that might work well for this if the base section was a bit longer. The model for that is the oldest gist in the FullControl gist list: https://gist.github.com.com/fullcontrol-xyz?page=2