-
Welcome!
This is a new forum we have started to help you get all of your technical questions answered. If you have a question, please click the “New Discussion” button and ask away!
With so many experienced CNCers, we’re hoping this turns into a great resource for everyone to share information and get quick feedback on their technical challenges with their CNC.
Andy will also be in here from time to time answering questions, but please first just ask the entire community as you’ll likely get a quick response.
Enjoy!
-
9 Replies
-
Are the manuals mentioned in the intro hardcopy or downloads? If so where are they located?
-
They can be found under the materials tab in each unit. They are digital, but you could download and print them if you wanted to.
-
Hey everyone,
I just signed up for the course and am working through the first quick-start U.S. States project (I picked Tennessee since that’s home). I was able to get a successful cut, but I ran into a few things I’m unsure about—likely tied to my specific machine setup.
For context, I’m brand new to CNC, though I do have experience with laser engraving and general woodworking. I wasn’t able to get a Shapeoko, so I’m running a TwoTrees 6050. Vectric had a machine profile for it, which helped. The manufacturer recommends Candle, but it felt pretty outdated, so I’m using Universal Gcode Sender (UGS).
A few questions:
1. Tool setup / bit size confusion
My machine came with only 1/8″ bits. I updated the tool configuration in Vectric, and it seemed to take, but the tool still shows as 1/4″ in places.
– Is that just a labeling issue, or does it affect the actual toolpath/gcode output?
– How can I verify that Vectric is truly calculating toolpaths using 1/8″ and not 1/4″?
2. Spindle control via gcode
When I load the file into UGS, I have to manually start the spindle—there’s no automatic start in the gcode.
– Is that expected with this kind of setup, or am I missing a post-processor or setting that should include spindle commands?
2a. Units behavior (metric vs imperial)
I created the file in inches, but once loaded, the controller appears to switch units—my jog increments jump from 1mm to 1″.
– Has anyone with a TwoTrees machine seen this behavior?
– Is this something controlled by the gcode header or the controller itself?
3. Material thickness / scaling issue
I tested both 1/2″ and 3/4″ stock, but the cut didn’t go all the way through. On the 1/2″ piece, I still had about ~1/16″ left.
Also, when previewing in Vectric, the design showed up much smaller (~3″ x 1″) than what was demonstrated in the video.
– This makes me suspect a metric vs imperial mismatch somewhere—either in the file or machine setup.
– Any suggestions on where to check or standardize units across Vectric, post-processor, and controller?
Overall, this was a great intro project and I’m excited to keep going—I just want to get my machine dialed in early so I don’t compound issues later.
Appreciate any insight!
Bryan
-
Hey Bryan,
1. Here’s what to check:
Open each toolpath individually → click Edit → look at the tool assigned there. Confirm it actually says 1/8″ and not an older 1/4″ tool.
Then run the toolpath preview. If your inside corners, slot widths, or small details look tighter than a 1/4″ cutter could physically fit, that’s a good sign it’s calculating with the 1/8″.
The Vectric-based projects later in the course always have you review and simulate toolpaths before exporting for exactly this reason.
So short version: if the toolpath itself says 1/8″, you’re good—even if some database naming looks weird.
2. This sounds like a machine/controller integration issue rather than a course workflow issue.
Since every machine and controller behaves a little differently, the best next step is to reach out to TwoTrees support or check their controller documentation for spindle relay / PWM support and firmware configuration. They’ll know whether your board supports spindle commands like M3/M5 and whether additional wiring or firmware settings are needed.
Metric vs. Imperial
Most often this comes from one of three places:
- Job setup units in Vectric
- Post-processor output
- Controller firmware interpretation
The quickest way to isolate it:
Open the exported gcode and look near the top:
-
G20= inches -
G21= millimeters
That tells the controller what units the file is using.
Also, UGS may automatically update jog increments based on the active gcode units—which would explain exactly what you’re seeing.
3. This one usually comes down to one of three things:
A. Actual material thickness vs software thickness
Always measure the board, don’t trust nominal lumber dimensions. Our Vectric playbooks call this out on every project: measure your actual material and update thickness in software if needed.B. Z-zero accuracy
If Z-zero is even .040–.060″ high, you’ll leave exactly the kind of onion skin you described.In the course we always zero to the top of material after any air pass or tool change.
C. Units mismatch
And honestly, because you also mentioned the design preview being tiny, this is the one I’d suspect first. That’s a huge clue.If the project should be around ~10–12″ wide but is showing ~3″, something is almost certainly scaling due to mm/in conversion.
I’d check these in order:
- Vectric Job Setup → confirm inches
- Re-import project file and confirm it doesn’t ask to scale on import
- Verify post-processor matches your controller
-
Check gcode header for
G20vsG21
My gut says you’ll find the mismatch there.
Hope that all helps,
Miranda
-
Thanks for the quick and thorough reply—seriously appreciated. That helped a lot and confirmed a few of my suspicions.
TwoTrees support has been a bit hard to reach (I usually have to go through my supplier, MatterHackers, to get a conversation started), but I’ll follow up with them. Like you mentioned, there may be a straightforward way to include spindle start in the gcode. If not, manually starting it isn’t a big deal and honestly fits well with doing a final check before running the job.
I also dug into another Vectric video on toolpaths and tooling, and that cleared up my bit size issue. Turns out it was user error—I hadn’t actually applied the change (the button was lower in the panel than I expected). Once I fixed that and measured my material more accurately, things improved quite a bit. I had assumed 1/2″, but it was closer to 9/16″, and updating that made everything cut correctly.
On the scaling issue, I still haven’t found the exact setting to switch between metric and imperial globally, but I agree—it definitely seems like that’s where the mismatch is happening. In the meantime, I was able to scale the vectors directly and get the state closer to the intended ~8″ size.
One thing I’ll say already—I like that the course is pushing me to explore and troubleshoot a bit. With a different machine, I’ve had to dig in more than expected, but it’s building confidence quickly.
Really glad I jumped into this course. On to the next project!
-
Hello All, I just ordered my very first CNC Router today and purchased the Kick Start Package to help me get off on the right foot. I have no CNC programming experience even though I work in the Aerospace Machining World as a Quality Engineer. I am eager to learn and get good at my projects. I purchased the Genmitus CNC Router 4040-PRO. Looking forward to my 1st Kick Start lesson soon as it arrives.
-
Hi William, I am new to cnc routers and just starting. I also have a Genmitsu 4040 pro that is new to me. I look forward to learning alongside everyone else.
-
Hey Mark, nice to meet you. I had to buy a dedicated laptop for my router. Now that I have that and have hopefully downloaded everything properly, I can plug into the router and get started. I am not very computer literate. Fingerz crossed.
-
William, great you just need to get in there and start playing with it. I’m 72 years old and somewhat intimadated but it’s getting easier as I go. I’m on a free trial of Millmage (lightburn) right now and getting a few projects under my belt. Good luck you can do it!
Log in to reply.