Miranda
Forum Replies Created
-
Here’s the basic workflow to follow:
1. Download and unzip the files
When you download the project, it’ll come as a zipped folder.
Right-click → “Extract All” so you can access everything inside.2. Decide which route you’re taking
- If you want to learn and tweak things → open the project file in your software
- If you just want to run the job → use the G-code file
3. If using the G-code (USG)
- Open your control software (like UGS)
- Connect to your machine
- Load the correct G-code file (each file usually matches a specific bit or step)
- Set your zero:
- X/Y = lower left corner of your material
- Z = top of material
- Run the job
4. Important:
Most projects use multiple files (one per tool). That means:- Run first file (example: pocketing)
- Change the bit when prompted
- Re-zero Z only (not X/Y)
- Run the next file
A couple beginner tips that will save you headaches:
- Always double-check your material size matches the project
- Run an air pass first (lift the bit and simulate the cut)
- Stay near the machine for your first few runs
- Don’t rush; setup is everything in CNC
-
Thanks for the detail, that helps.
First, the “No Processor Selected” issue when using “Add Processor” is usually just a quirk of how that window behaves. For your machine (Genmitsu 4040-PRO MAX), you don’t need to add anything custom, you can skip that entirely and just use:
- grbl (mm) or
- grbl (inch)
Those are the correct post processors for your machine.
Now, the bigger issue is this message: “Trial version of the software can only save toolpaths…” That’s the key. This isn’t a post processor problem, it’s a software limitation.
What that means:
- The trial version will only let you export toolpaths from their built-in sample files
- Any file you downloaded (like your Kentucky design) won’t export until the software is activated
So here’s what to do:
If you’re just testing:
- Open one of the included tutorial/sample files
- Select grbl (mm or inch) on the right side
- Export should work fine
If you want to run your Kentucky carve:
- You’ll need the full version of the software to generate toolpaths from that file
Good luck!
-
Hey Michael,
The trial only allows you to save toolpaths from their included sample files, which is why it’s blocking you when you try to use Easel as your post processor.
So here’s the deal:
You don’t necessarily need to buy the full version right this second to keep moving forward.
Instead, you’ve got two solid options:
First option: stick with the workflow using the provided files.
If you’re following along with the course projects, those are designed to work within the system and help you learn the process step-by-step. The key focus right now is understanding the workflow, not the specific post processor.Second option: upgrade when you’re ready.
If you want to start running your own toolpaths (like what you’re trying to do with Easel), then yes you’ll need the full desktop version of VCarve to export those properly.Good luck!
-
The good news is the course files are meant to work across different machines and software setups, and we do have members using a wide range of CNCs successfully, not just the exact machines shown in the lessons.
That said, what you’re describing sounds less like a project file issue and more like a machine/control communication issue. But before you reach out I would check a couple things.
-Make sure the downloaded file was extracted fully before opening it in your software.
-Confirm the job setup matches the playbook exactly, especially material thickness, Z-zero set to the top of material, and XY zero/datum set to the lower-left corner on the projects that call for that. Several of the project playbooks use that exact setup, and they also recommend simulating the toolpaths before exporting and running an optional air pass before the real cut.
-Also make sure you’re exporting with the correct post-processor for your machine/controller workflow. The playbooks do call out using the machine’s correct post-processor when exporting toolpaths.
If the cut is repeatedly pausing, throwing errors, or needing to be resumed 20 times, that’s the point where I’d stop chasing the project file and have Sienci confirm the communication side, sender setup, and correct post for the LongMill MKII. That sounds like the fastest path to getting you running cleanly.
-
For Lesson 2 (the Bit Organizer project), you do need a 1/8″ upcut bit for the small detail pocketing toolpaths. The 1/4″ downcut handles the larger pockets and profile cuts, but the 1/8″ upcut is what gives you those clean, tighter detail cuts.
-
Here’s how to approach it inside VCarve:
First, set up your job exactly like the playbook outlines:
– Job size: 12″ x 7″
– Material thickness: Measure your walnut and enter the real number
– Z-zero: Top of material
– XY zero: Lower-left cornerThen recreate the same three toolpaths:
Pocketing
Use your 3/4″ bowl and tray bit and create a pocket toolpath for the tray recess. Match the depth shown in the design and preview it carefully.Engraving
Use a 60° V-bit and create a V-Carve toolpath for the flag details.Profile Cutout
Use your 1/4″ downcut and create a profile toolpath to cut out the outer shape. Add tabs just like you normally would in VCarve. -
With V-carving, the depth isn’t controlled by the “max depth” the same way a pocket or profile toolpath is. The depth is actually controlled by the width of your vectors and the angle of your V-bit. If the letters or design aren’t wide enough, the bit physically can’t go any deeper, even if you set the max depth to 0.7″.
That’s why you’re seeing about 1/8″ deep. The geometry of the design is limiting it.
A few things to check:
First, confirm your Z-zero is set to the top of the material. In our projects (like the Welcome sign), we always zero to the top of the material before running the V-carve toolpath . If Z-zero were off, you’d usually see inconsistent carving depth, but since your Welcome Home sign worked well, your zeroing is likely fine.
Second, look at the font or logo thickness. Thicker, bolder fonts will carve deeper because the V-bit has room to drop lower. Thin script fonts will always be shallow.
Third, what degree V-bit are you using? A 60° bit will cut deeper than a 90° bit for the same width. A 30° bit will actually cut shallower unless the design is very wide. Bit angle makes a big difference.
