Hi,
I'm not familiar with the CAD/CAM package you are using.
I will relate what I have seen with Mastercam with which I am more familiar.
When you first generate a toolpath in Mastercam it saves it in a special file format, from memory, ***.mcam.
Even if you could open and read this file it would not mean much. It contains codes that are native to Mastercam.
This file needs to be processed by a post processor file. When that happens the ***.mcam code gets converted
into Gcode for your machine, ***.nc. Note that if you had two machines, one a Mach machine and the other a
Marzac say. You would use exactly the same ***mcam file to generate the Gcode for each machine, but you would
use a Mach3 post to get Mach3 compatible code or use a Marzac post to get Marzac compatible Gcode but both
rely on the same toolpath described by ***.mcam
The problem you are describing could be three different things.
It may be that the CAD/CAM package is producing its own native toolpath code, similar to ***.mcam described
above. It is not Gcode, and will not load into any Gcode machine. It will have to be post processed before it becomes
Gcode.
Can you be 100% sure that the raw output of Q-cad/cam is being post processed?
Another possibility it that the Gcode that is being generated by the post processor is being stored as a ***.nc file, or
a ***.gcd file or some other file extension that Machs Gcode interpreter does not understand despite the file containing
normal Gcode.
May I suggest using Notepad++ or a similar text editor to open the file and see if it has ordinary Gcode ASCII text within
it? It might be as simple as renaming the file to something that Mach recognizes or you can alter Mach to accept a file
with an unusual extension.
The last possibility is that the post processor is producing bad code. For instance in Mach compliant code a line number
starts with an 'N' followed by the line number, N155, for example. If the post processor omits the leading 'N' then
Mach will baulk.
It is for this reason that I asked you to post a sample of the code.
You are going to have to try 'Open With:' until you find a means of reading/editing or copying the Gcode within the file.
Craig