How to Make Directories on an Intermac CNC Machine

• 1
  What matters before you start
• 2
  What a directory means on an Intermac CNC machine
• 3
  Plan the folder tree before you touch the controller
• 4
  Move files to the Intermac CNC machine without losing them
• 5
  Checks that catch directory problems early
• 6
  How to make directories on an Intermac CNC machine
• 7
  Directory rules and what each one prevents

On an Intermac router, a directory is not just a place to store files. It is the address the controller uses to find a program when the operator selects a job at the console. The machine software scans a defined root folder, lists what it finds, and ignores anything outside that tree. If a file sits two levels too deep or in a folder the controller never scans, the operator sees an empty list and assumes the file is missing.

Most confusion comes from mixing two ideas: the folder structure on the office PC and the folder structure the Intermac CNC machine expects. They can look identical on screen and still fail, because the controller reads a specific root path, often on an internal drive or a mapped USB volume. A directory plan that respects that root is what makes files appear reliably.

Depth and width both matter. Three levels is usually enough: a top folder for material or customer, a second folder for the job or batch, and the program file itself. Going wider than that creates duplicates. Going deeper pushes the full path past the length the transfer window can display, and truncated paths are a common source of silent read failures.

Keep the naming plain. ASCII letters, digits, and underscores only. Spaces cause problems on some controllers, and accented characters fail outright. A folder called JOB_1042 will always be safer than one called Job 1042 – Oak top.

• 1
  One root, one treeDecide the program root once and never place jobs outside it.
• 2
  Three levels maximumMaterial or customer, job, then the file.
• 3
  Plain ASCII namesLetters, digits, and underscores only.
• 4
  Path under 64 charactersShort names keep the whole path readable on the console.

Write the tree on paper first. Start with the root the Intermac CNC machine actually scans, then add one folder per material family or customer, then one folder per job number. This takes five minutes and saves an hour of searching later. If two operators share the machine, agree on the tree in writing before either one creates a folder.

The second decision is where files come from. Programs may be written offline in CAD/CAM, exported as ISO or a machine-specific format, then copied across. Each of those steps can rename the file. Check the exported name against the folder name before transfer, because a mismatch between job number and program name makes traceability impossible once parts are cut.

Decide early whether the working copy lives on the machine or on a network share. Machines that read from internal storage are faster and immune to a pulled cable. Machines that read from a mapped share are easier to update but fail when the network drops. Neither is wrong; mixing both without a rule is what causes duplicate programs with the same name and different geometry.

Finally, reserve one folder for scrap and one for archived jobs. Moving an old job into archive keeps the active list short, which matters when the console list runs to hundreds of entries and the operator has seconds to pick the right one.

• 1
  Write it downA one-page tree agreed by all operators prevents duplicate folders.
• 2
  Check exported namesConfirm the CAM export name matches the job folder before copying.
• 3
  Pick one source of truthInternal storage or network share, not both for the same job.
• 4
  Archive old jobsKeep the active list short enough to scan at the console.

USB transfer is still the most common route on shop floors. Format the stick with a file system the controller reads, usually FAT32 for older controllers. Copy the job folder as a whole rather than individual files, so the structure arrives intact. Eject the stick properly on the PC; a half-written folder is the worst kind of failure because it looks complete in the file browser.

Once the stick is in the machine, open the controller file window and walk the tree yourself. Do not trust the folder icon. Open each level until you see the program file with the expected size and date. A file that shows 0 KB or a date from last year is the wrong file, no matter what the name says.

If the controller offers both internal and external storage, copy from the stick to internal storage before running. Running directly from removable media works, but a bump or a power dip during a long cycle can interrupt the read. Internal storage also keeps the program available after the stick goes back to the office.

After the first part is cut, compare the program header against the drawing revision. Directory work is only finished when the file that ran is the file the engineer released. Keep a paper or digital log of job number, folder name, and program revision for every setup.

• 1
  Copy folders, not loose filesThe structure is part of the job.
• 2
  Eject properlyA half-written folder looks fine and reads as empty.
• 3
  Open every levelCheck size and date, not just the file name.
• 4
  Copy to internal storageLong cycles should not depend on a stick staying seated.

Before a job runs, compare the folder list on the PC and the machine side by side. Count the folders at each level. A missing folder at level two is easy to spot this way and almost invisible if you only check the file name. This check takes under a minute and catches the most common transfer error.

Watch for duplicate job numbers with different revisions. If JOB_1042 exists twice under different top folders, an operator will eventually run the older one. Delete or archive the superseded folder the same day the new revision is released. A short rule like one job number, one folder prevents this entirely.

Name folders in a way that survives a backup and restore. Backup tools sometimes change case or strip special characters. Plain uppercase names with underscores come back unchanged. If your shop restores a drive after a failure, this is the difference between a working tree and a week of rework.

Finally, keep the controller clock correct. File dates are used to pick the newest revision during a quick check, and a wrong clock makes an old program look new. A two-minute clock check at the start of each shift is cheaper than a scrapped panel.

• 1
  Compare both sidesPC and machine folder counts should match at every level.
• 2
  One job, one folderArchive the old revision the day the new one is released.
• 3
  Backup-safe namesUppercase ASCII survives most backup and restore tools.
• 4
  Set the controller clockWrong dates make old programs look current.