FullControlGCode

Following on from my 2-week comment (https://www.reddit.com/r/FullControl/comments/11efnyv/script_release_eta/jadzheq?utm_medium=android_app&utm_source=share&context=3), it's now time to tell me to hurry the heck up!

It won't be released tomorrow, but I have put in a proper stint of work over the last two weeks and it's pretty much there now. I have a meeting with my co-developer tomorrow to go through it. I'll update in the next few days!

Quick update on the spanky new version of FullControl

An experienced software engineer has slowly dragged my head out of the sand to teach me a million different software engineering things and make sure FullControl is done properly - it's been a slow process, but definitely best for FullControl in the long run. 

We've recently been developing ways to make sure people can share and access designs in a professional way. Things are looking awesome - far beyond what I thought would be possible when I began working on the new FC. We're also making sure:

- people who don't do coding can use FC easily

- people who do like coding can use it to its full potential

- people who LOVE coding can

Question: "Hi there, I have two questions about your program. Do you need Excel installed on your computer to run it and can it be run on a Mac?"

Answer: Yes you need it installed (although a python version currently being developed) I think it can run on a Mac yep

My answer: Use the extrusion width parameter (box) in FullControl. There are parameters for speed, width and height. They can all be equations.

Eoverride is more complicated... it sets the extrusion value for each segment in the whole mathematical curve (i.e. the exact value of E to write in the GCode for each G1 command), which means it doesn't allow FullControl to automatically calculate E based on segment length. It overrides the normal process of FullControl using width x height x length to calculate volume (and convert from mm3 to mm of feedstock filament if your printer uses those units for E)

My answer: I haven't got a worked example, but I have now added a very brief example on the tutorials page on my website.

Basically, set the range for 't' in Desmos to be the same as the range of Tval you set in FullControl. Reproduce the Desmos equations for X and Y in a format that Excel understands in FullControl (with its COS and SIN functions, etc.) Set the Z equation in FullControl to be 0 or something. 0 would mean you're printing the whole equation at a height of 0. Then just set extrusion width and height, make sure you use enough 'segments' to give a reasonably smooth curve. And it should all work! Clear any description data in unused cells. And make sure you try a simple equation

If you'd like to help develop FullControl, please let me know ([email protected]).

Professional programming skills are obviously valuable, but there a lots of other things that are important (e.g. software testing, website development, etc.). Or you may have relevant expertise for future versions of FullControl (e.g. 5-axis printing expertise, laser cutting or laser AM expertise, etc.). So don't be shy!

I want to keep FullControl completely free and open source, and ultimately improve additive manufacturing in industry, research and garages/sheds.

FullControl is super powerful, but pretty complicated to use, so this subreddit will hopefully allow people to discuss their problems and give advice.

I (Andy Gleadall) am gradually creating tutorial videos for the functions I've added to FullControl (http://fullcontrolgcode.com/tutorials), but those tutorials can't go into all the details of each feature type or they'd be too long. So ask for clarification, etc., here.

Also, there are some functions of FullControl that are kind of hidden away. Sometime because they're complicated and confusing to explain, sometimes because the VBA code for them is a kind of hack-job that might interfere with oth