Sometimes, writing out the post line like this can make for a cumbersome logic and also not permit to re-use the info in some other location in the post. I would prefer to create a new post block alltogether and call it up on the outputted post line ... something like this: phood #Hood Adjustement Height if mi4$ = 1, "E=TLLEN" #Auto height adjustement if mi4$ > 1, *mi4$ #Custom height And access this information in the posted line as Paul had it before: n$, "XG0", pfxout, pfyout, pfzout, phood, *feed, *speed, *t$, *zclear, strcantext, e$ It makes it much easier to read, easier to re-use the "phood" post block somewhere else and also isolates the programming logic in one area. Also, if needed, easier to copy from 1 post to another. This also allows commenting the new post block for futur reference (we do forget things years down the road!) Hope this helps!

Turk, Ron has it on the mark. I used to be a college teacher in mechanical engineering, self taught in all CAD/CAM/CNC stuff. After a few years, the challenge of learning new stuff was fading so I decided to start my own business. No steady pay, no insurance, vacations, medical leave, office, equipment, co-workers ... nothing but a leap of faith in my ability to make it work. Became a Mastercam reseller for about 8 years where I learned a lot of CAD/CAM/CNC stuff, but also in HR, finance, managing people, negotiating with customers and so on. If you're job security lies in your own abilities, I beleive you're on the right track. If you depend on others for a living - it can fall short on very little notice. BTW, never had a 5 axis machine to "play" with on a day to day basis but I've trained many, done posts for many, banged my head on the wall a few times, but all in all, always managed to figure things out. Have luck with your search ...

The variables allow you to have the output to dynamically change according to there values. You could also assign this macro with addresses and call it out like this: M98 P9999 A0 B0 C4 D3 L0 M0 N4 P3 Each value assigned to an address could be used in the macro. Hope this helps!

Make sure that the NCI filename, program number and program name are the same for each operation.

Well then that explains it: Z2.6 - Z.6 = Z2.0 This is where the error is coming from. You could try returning the machine to it's home before calling a new coordinate system (G91G28Z0). How are you writing your subprogram? What's the Z value in your G56, G57... values?

Make sure you don't end with a G91 move in your sub-program. You should just make sure and add a G90 to the line immediatly after the sub call, ie, G0 G90 Z2.6

Did you try this out ...!!!

How about something like this? Haven't tested but use with caution! % #101=0 (X POSITION) #102=0 (X COUNTER) #103=4 (X SPACING) #104=3 (X QTY) #105=0 (Y POSITION) #106=0 (Y COUNTER) #107=4 (Y SPACING) #108=4 (Y QTY) G54 #106=0 (Y COUNTER SET) N1 (RETURN FROM Y INCREMENT) IF [#106 EQ #108] GOTO 20 (REACHED Y QTY - END LOOP) #102=0 (X COUNTER SET) N5 (RETURN FROM X INCREMENT) IF [#102 EQ #104] GOTO 10 (REACHED X QTY - END LOOP) G52X#101Y#105 M98P1000 #102=#102+1 (INCREMENT X COUNTER) #101=#101+#103 (ADD X SPACING) GOTO N5 N10 (END X LOOP) #106=#106+1 (INCREMENT Y COUNTER) #105=#105+#107 (ADD Y SPACING) GOTO N1 N20 (END Y LOOP) M30 %

John, I'm not having the problem ... just trying to find a solution for ziko1. Seasons Greetings!!!

You guys are a Cimco Reseller and Mastercam Reseller. You should check to see if you are running cimco from Mastercam's Common directory or trying to run a standalone version of cimco V5 using a licence file... Try getting this solved to start with.

Can you determine if the NetHasp is licenced to your computer ... if not, that means that the PC is not licenced to run Cimco.

Is your Mastercam Hasp installed on your computer when you get this message?

If all other code is the same, why not just ask a question when posting to select correct machine and modify the output accordingly. This makes it much more easier if you are to change anything else along the way ... just 1 post to edit. My 2%

C'est exacte, ils viennent de Windsor tout près de Richmond!!!

Anyone else have this bug??? CNC software guys???

Look into a cabled/wireless DNC system. A lot depends on how many machines, distances between PC and machines and also plans for futur expansion. For now, you seem to have 8 machines (if my math is correct). RS-232 cabling from PC to machine should not exceed 300 ft. If using this type of cabling, I recommend using sheilded cabling to hinder any interference. Another solution is putting an RS-232 HUB on the shop floor with RS-232 drop downs to each machine. To combine Ethernet capable machines and some that might not have this capability, you could string Ethernet cables from your PC to a hub on the shop floor and from there ethernet cable to each machine. Moxa has some NPort5110 converters that will convert a TCP/IP address into a COM port. This will allow you to use standard cabling all across the shop. We often use DIGI Acceleport XEM or CX modules for direct RS-232. You can also put in a PCI multiport card in the PC (Rocketport, Startech, ...). Wireless is another route, instead of using ethernet cables you would use a wireless bridge ... and at the machine use the Moxa units. As far as software is concerned, we are in a Mastercam forum so many are already use to using the Cimco Edit software supplied with Mastercam. Cimco DNc-Max will handle many transfer protocoles and needs pertaining to your transfer needs. Take a look at the documentation at there website http://www.cimco-software.com If you need more info, send me an e-mail ... Hope this helps ...

Why not just write out a custom macro ...

I'm getting an invalid argument error ... works fine in X2 and looks good in Excel when reading the CSV file format. Have a good day Mike!

Is anyone else having problems bringing in level sets created in X2? Thanks

Anyone having problems with Level Sets created in X2 when brought into X3 - invalid argument error?

I would recommend starting off with a Mpmaster post from this site. Tweaking can be done after that, but all in all, it will be a good basis. Regards

Exactly, it will populate in the buffer file and you can read them out when needed.

I'll give a shot at an answer for the z_min/z_max: During execution of the post, the pwrtt section is being called out first, before the first operation is being output to the post. It runs thru all operations and gets info for tooltable, tool planes, and x,y,z min/max limits by calling ptravel and writes out the info by calling pwritbuf5. After this parsing is done, ptravel is re-called from the psof section. hope this helps...

Don't forget that the geometry being used must NOT contain any splines. Arcs and lines are OK. Salut!

Did you check to see if you have the 2D/3D button set to 2D?