I created an IMPORT.EXE for CNC90 last year, which seemed to work OK. But I managed to destroy the CNC controller before I got to use it properly, and ended up retro-fitting with LinuxCNC.
If anyone is interested, I can dig it out and post here?
I found my files, and I've attached the import.exe and the import.c source code. (To compile for DOS, I used TurboC which I managed to find on the net somewhere.)
This import function takes a single G-code file and creates the necessary files in the SRG and TAB folders, and adds to the INDICE.PRG file which the index file of all the files.
The source G-code file needs to be in a CNC90-type style, e.g.:
G71X1220Y700Z14.75T00N47L44
G150(VOLUTO MAST)
etc.
so your post-processor should output what CNC90 is expecting.
The first two lines are used to extract the X,Y,Z dimensions of the stock, and the comment on the second. G71 and G150() are required, the rest is calculated(T=tool, N=number of file lines, L=number of G-code lines).
IMPORT.EXE needs to go in the CNC90 folder. The command needs two parameters: source G-code file, and destination file name.
The source G-code file should be in one of the following directories: "C:", "C:\CNC", "C:\CNC\CNC90", but you may also add a custom directory path in a file called IMPORT.INI
The units are hard-coded as millimeters (sorry), as I never got around to deriving it from the input file.
I went through all the binary files to get the format to match what was existing on my machine, so there are a couple of bits that are hardcoded, which I hope are universal but you may get different results on your machine.
I'm happy to answer any questions, or compile a custom IMPORT.EXE if needed.
EDIT: I forgot to mention that there should be an environment variable called DIRSOR that points to the output directory, CNC90 should have set this up in DOS, e.g. "C:\CNC90\MOD1\SORG", but you will have to add it manually if the import script has an error "Usage Error - Cannot find output directory"
Last edited by HueyHQ; 12-22-2019 at 05:08 PM.
Reason: Added note about DIRSOR
Sorry, I did not see your question until just now.
You need to add two parameters: the source G-code file, and the name of the file as it appears in CNC90. The source needs to follow the DOS 8.3 filename format, and the destination can be up to 11 characters, which CNC90 then breaks down into DOS 8.3 filename format.
You also need the first two lines in your G-code file:
G71 X???? Y??? Z??? T00
and
G150(YOUR COMMENT GOES HERE)
In the first line, no spaces allowed. G71 is a CNC90 code, and the dimensions of your stock for X/Y/Z can be integer or float. I can't remember what T00 is, but the N?? and L?? are the total number of lines, and the number of G-code lines, and can be omitted as the import.exe will add those.
Like I said, I never got the chance to use this on the machine, only testing in DOSBox, so there may be a few things I get wrong.
With regard to adding the DIRSOR environment variable in DOS, the CNC90 *.bat files should set these up at startup, but I found that DIRSOR was missed.
Using SET will display the current variables, and SET [variable=[string]] will add it. Here is an example of my machine: C:\>set
PATH=Z:\
COMSPEC=Z:\COMMAND.COM
BLASTER=A220 I7 D1 H5 T6
ROOT=C:\CNC\CNC90
WORKDIR=C:\CNC\PTP1000
DIRCOMUNIC=C:\CNC\CNC90\MOD1\TMP\
VDISK=C:\CNC\CNC90\MOD1\TMP\
INTMSG=96
DIRSOR=C:\CNC\CNC90\MOD1\SORG\
DIRCMP=C:\CNC\CNC90\MOD1\COMP\
DIRLST=C:\CNC\CNC90\MOD1\LISTE\
USER=C:\CNC\CNC90\MOD1\USER\
DIRLING=C:\CNC\CNC90\LINGUE\
DIRTMP=C:\CNC\CNC90\MOD1\TMP\
EXEC=C:\CNC\CNC90\GO_CNC90.EXE
ROOTCAD=C:\MATCNC90
INIT=C:\CNC\CNC90\MOD1\PTPSYS
Hi Cne
I know this is a old thread but I would be interested how you did this my email. peachtreecabinets@gmail.com
I am struggling with an old alberti with ptp400
Hello, thanks for this thread. I’am the same need as rigmorcat.
I have a old Alberti Edit2000 with PTP400 on windows XP.
Maybe you have finded a solution ?
Reply with Quote
Re: Uploading to CNC90 - How?
