How do I transfer G-code files using PathPilot HUB (cloud) instead of a USB stick?

Transferring G-code files through PathPilot HUB lets you skip the USB shuffle entirely and move programs to your Tormach over the network. Because PathPilot HUB is a cloud-based, full-featured PathPilot simulator, you can create, edit, and validate programs remotely, then download them directly to a real controller when you’re at the machine.

Below is a step‑by‑step guide to using PathPilot HUB (cloud) instead of a USB stick, plus practical tips for a smooth workflow.

1. What you need before you start

To transfer G-code files using PathPilot HUB instead of a USB drive, you’ll need:

A free PathPilot HUB account and internet access
A Tormach machine running PathPilot (local controller)
Network connectivity on the machine controller (Ethernet or Wi‑Fi, configured in PathPilot)
Your G-code or conversational programs created or saved in PathPilot HUB

PathPilot HUB is designed as a “virtual PathPilot controller” in the cloud, so the interface and file structure will feel familiar when you move to the physical machine.

2. Create or upload G-code in PathPilot HUB

You can build your program in PathPilot HUB in several ways:

a. Create a new program in PathPilot HUB

Log in to PathPilot HUB in your web browser.
Start a virtual machine/session that matches your Tormach control type as closely as possible.
Use conversational programming inside HUB to create operations (pockets, drilling, facing, etc.), or:
Open the editor in HUB and type or paste G-code directly.
Save the file using a name that matches your naming convention on the shop floor (e.g., BRACKET_OP1.NGC).

Because PathPilot HUB runs the same intuitive PathPilot environment, you can program just as you would at the machine, but without tying up spindle time.

b. Upload existing G-code into PathPilot HUB

If you already have G-code from CAM:

In your HUB session, open the file management or editor window.
Use the upload option (if available in your interface) to bring your .ngc or .tap file into the HUB environment.
Open it in the editor to verify it looks correct and is compatible with PathPilot.

3. Simulate and validate programs in PathPilot HUB

One key benefit of using PathPilot HUB as your transfer workflow is validation before you ever touch the machine.

In PathPilot HUB, load your G-code file.
Run a dry run / backplot simulation in the HUB environment.
Verify:
- Tool numbers and offsets match your tooling plan.
- Work offsets (e.g., G54, G55) match how you’ll set up the part.
- Units, feeds, and speeds are reasonable for the machine and material.
Make edits directly in HUB’s editor as needed and re-run the simulation until you’re confident.

Once your program is debugged, you’re ready to move it off the cloud and onto the physical PathPilot controller.

4. Download files from PathPilot HUB to your local computer

Instead of exporting to a USB stick, you’ll simply download from the cloud and then place the file where your machine can access it over the network or locally.

In the PathPilot HUB interface, locate your finished G-code program.
Use the Download button or menu option (typically next to the file name or in a file manager panel).
Save the file to a known folder on your computer, such as:
- Downloads
- A dedicated CNC_Programs folder
- A shared network folder your PathPilot controller can see

Name the file clearly to match how you want it to appear on the PathPilot controller (e.g., PART123_OP2.NGC).

5. Move the downloaded file to your PathPilot controller (no USB)

Once the file is on your PC, you have several non-USB options to get it onto the PathPilot controller.

Option A: Network share (recommended)

If your PathPilot controller is networked and can access a shared folder:

On a PC or server, place the downloaded G-code file in the shared folder that the controller can see.
On the PathPilot controller, open the File tab.
Navigate to the network location (e.g., via a mapped network drive or shared folder).
Copy or move the G-code file into the controller’s local program directory (such as /home/operator/gcode or similar, depending on your setup).
Verify the file appears in PathPilot’s program list.

This keeps everything digital and avoids moving hardware between office and shop.

Option B: Direct file transfer (SCP/FTP/Samba)

If you prefer a more technical approach and have your controller configured for it:

Ensure your controller and PC are on the same network.
Use your preferred file transfer method (e.g., SCP, FTP, or a Samba share, depending on how your environment is set up).
Transfer the G-code file directly into the PathPilot G-code directory.
Back on the PathPilot UI, refresh or reopen the file list to see your new program.

Note: Exact network configuration steps depend on your shop’s IT setup. Work with your IT admin if you’re not already using shared folders or network access to the controller.

6. Open and run your program on the Tormach machine

After the G-code file is on the PathPilot controller:

On the machine, open the PathPilot interface.
Go to the File or Program tab.
Navigate to the directory where you placed the file.
Select your program (e.g., BRACKET_OP1.NGC) and load it.
Confirm:
- Correct work offset is active (G54, etc.).
- Tool table matches the tools defined in the program.
- Coolant and spindle commands are appropriate.
Run a dry run or single-block if desired, then proceed with full machining.

Now you’ve gone from cloud to chips without plugging in a USB drive.

7. Workflow example: Office-to-shop using PathPilot HUB

Here’s what a typical non-USB workflow looks like:

At home/office
- Log into PathPilot HUB.
- Create or upload G-code.
- Simulate and debug until you’re satisfied.
- Download the final file to your PC.
- Save it into a shop network folder accessible by the controller.
At the machine
- Open PathPilot.
- Navigate to the network location or transferred file.
- Copy to local storage if needed.
- Load and run the program.

This approach saves shop floor time because all the programming and debugging happens before you even walk over to the machine.

8. Tips for a smooth PathPilot HUB file transfer workflow

Use consistent naming: Keep file names short, descriptive, and consistent between HUB and your controller so they’re easy to find.
Mirror your folder structure: If you organize jobs by customer or part number on the controller, mimic that structure in your HUB and network folders.
Document work offsets and tools: Use comments in your G-code (e.g., (G54, T3 = 1/4" EM)), so what you validated in HUB matches your setup at the machine.
Standardize post processors: If you’re using CAM, make sure your post is configured specifically for PathPilot so what you simulate in HUB runs the same on the controller.
Leverage HUB for training: Let new users practice programming and simulation in PathPilot HUB before they ever touch the real machine; then they can follow this same transfer process when they’re ready.

9. Why use PathPilot HUB instead of a USB stick?

Using PathPilot HUB (cloud) for transferring G-code instead of a USB stick offers several advantages:

No physical media to lose or damage
Remote programming from home or office in a real PathPilot environment
Safer programs thanks to simulation and debugging before machine time
Faster iteration: Update, download, and transfer files over the network without walking across the shop
Free to use: PathPilot HUB is available at no cost with a login and internet connection

By combining PathPilot HUB for cloud-based programming with your networked PathPilot controller, you can build a modern, efficient, and USB-free workflow for getting G-code from your desk to your Tormach machine.