The issue Phillip describes above is a backwards compatibility issue between Vectric versions 11/12 and version 9. Versions 11 and 12 have several additional commands and variables available in their post processors that do not exist in version 9, and several of those items are in my post processor developed under version 11 Vectric.
I am working with Phillip on a reduced feature version of my post processor that will support the older versions of Vectric. To avoid further confusing this thread which is for versions 11 and 12 of Vectric, if you would like a version 9 post processor when finished, please DM me so I can send it to you or start a new thread for version 9 if there is enough interest for that.
Just answered my own question. Loaded the file into Carbide Motion and it had no problem with it. Curious that the extension shows as *.nc in the Post Processor drop down box.
Ran the file and everything works fine. A question though. The Spindle warm-up process was unexpected. Is this a standard best practices that I have not been aware of?
Sure be glad to answer your questions. Just for background, I am a 60+ years woodworker but only 2 year CNC’er so a reative newbie myself, so, here goes:
Simple answer, Yes, Carbide Motion loads either .gcode or .nc file extensions, and has for several years. The .nc in the title of the PostP is a carryover from the default version Vectric included in the software, and I just decided to continue it without modifying that aspect. My limited historical knowledge is that CNC began in the industrial community and those larger machines used file extensions such as .nc and .tap as well as some other not so common ones. I’m sure there are others with more GRBL and other expertise that can provide more historical info than I can.
Regarding the 1-minute warmup as a best practice workflow, yes that is correct. Up through version “d” of my post processor I had not added it. But I got a few requests from other users to add it as a best practice. I do still use the CM built in Quick Action of a 3-minute warmup to ensure lubrication is well distributed in the Spindle before putting cutting stress on it when I first turn the machine on. So, my quick 1-minute warmup is a bit of an insurance policy to protect the lifespan of the Spindle as a best practice throughout the day as I use the machine.
Hi Allen. Curious thing this morning. I made a file for surfacing my spoiler board which would require me removing the Bitsetter once the machine had measured the bit. I expected I would have time to remove it when the spindle went through it’s warm up procedure. Surprise, no warm up. Went straight to cutting. Fortunately the start point was at the far corner so I was able to remove the Bitsetter. Did I do something wrong? Does the warm up not happen when the machine is first used in the day?
Thanks.
Short answer, no, a file generated with version 7f must go through the one-minute warmup everytime the file is run. Without looking at your gcode file it sounds like the file was generated by some other post processor.
If you open the gcode file with Notepad or some other text editor, the second line of the file will state the version of PostP of mine that generated the file. Here is a snippet of the beginning of a typical file:
(Material Size: 8.000in-x, 6.000in-y, 0.750in-z)
(VECTRIC POSTP: Carbide Motion ATC inches *.nc, v7f)
G20
G90
(Toolpath: First Tool Change, Tool#301, V-Bit {90 deg 0.5 inches} #301)
M6 T301
(Toolpath: Move Spindle to safe Z to avoid workholding)
G53G0Z-0.197
Or if you want, send me your gcode file and I will take a look at it for you.
Yeah, I hear ya, I debated that myself when I made version 7e, but the old maintainability engineer in me decided to error on the side of preventive measure. And unfortunately there is no easy query branching ability in the GRBL/Shapeoko/Gcode software that I am aware of.
The other option is to take version 7f and delete out the warmup routine lines and save it as a new version. But then that would mean regenerating the gcode file in Vectric, which would be more time than one-minute. So it is a trade off issue in my opinion, and I decided to go with preventive measure.
You’re right. Was testing the Processor that came with the software. Didn’t realize that even if yours was set to default, it still had to be selected if it was not the most recent used.
If you have been following this thread, a few days ago Phillipmcb reported that his
Vectric Aspire version 9.5 was error halting on loading when he tried to use my
post-processor I had developed for use with Vectric version 11 and 12.
I researched the issue and found that several commands and variable values
used by Vectric version 11 and later do not exist in version 9 and earlier.
Luckily I was able to find an older version of the Vectric editing guide on their forum
that I used to identify the differences. Also, Phillip agreed to do testing for me with
the modified version since version 11 was the oldest version I have.
So, that testing is done and have a working version of my post processor for
Vectric version 9.5, and earlier too hopefully, (the editing guide seems to suggest
it should work back to version 5 but I have no way to test and verify that).
Next issue was what to call/number it. I decided since it is a backwards compatible
version, to label it backwards alphabetically, so starting as version z.
For example, if you have a Spindle/VFD, my post-processor version 7g is now the
latest for use with Vectric version 12.5. Therefore my post-processor version
7z would support Vectric version 9.5. The README_FIRST file in the attached
zip file goes into more detailed description on the different versions for both
Trim Router and Spindle/VFD. The zip file contains a bundle of all the latest
versions.
Thanks again to Phillip for helping me out with version z development.
