You have to be careful when you are inside a function and then execute another function. Sometimes you get stuck inside the function and don't know it which is what this error really means. If you can reproduce it please send us the steps so we can keep it from happening. We've caught most of them but there may be a few functions that still let you go into another funciton before completing something else and we can fix those when we find them.

Glenn, Can you get us a few of those files? I'm not sure what would be causing this on the 64bit side and the V9 files should come in. I've brought many V9 file in on my X64 system out of our database and never a problem. What method are you using to convert them up? Do they come in one at a time?

It sounds like you want to change all the peck drill operations to a straight up drill operations or some other drill operation, correct? There is no way to mass edit the drill operation type of a bunch of operations. Each operation would need to be edited singularly. Editing common parameters is for well, editing common parameters. Different drill cycles have different parameters so changing just the cycle type isn't always going to work and you need to account for something that would also allow for changing the drill operation type as well as the specific drill parameters and even the custom parameters. I know it's drilling and I'm sure it is considered simple, but take the same concept to changing all 3D HST toolpaths selected to another type, changing the type would most like cause the need to change toolpath specific parameters - not that it is impossible but it would considerably add to the complexity of edit common params. One thing you can do is to change one of the peck drill operations inside the operations manager and then regen. Now copy the parameters from that operation over each peck drill operation. I'm sure that you will need to change other parameters as well but this might help you from having to change say 100 ops and only change 10 or so. Worth looking at to see if this would help you With that said, it does sound like an interesting feature request and I will be glad to log it into our database for you.

If you have V9 files that do not open in X6, please send them in to [email protected] and if they are crashing, make sure to send in the crash report. X6 will open V9 files and this should be looked at. V9 is no longer supported but that doesn't mean we can't check to see what is going on in X6 for you.

You may also need to edit the nethasp.ini file to specify the server address. Launch NhaspX.exe and click the nethasp radio button and then the Read button. This will force it to search the server for a nethasp. Like I mentioned you may want to edit the .INI file to specify the address of the server. Information on the nethasp.ini settings can be found in the MCAMX6_Administrator_guide.pdf found in your documentation folder.

Keith, I am checking on your issue now and using your file I can somewhat duplicate your issue however I get mixed results. Seems like it works sometimes and not others. I made a new file and it works perfect. Not blaming your file, but I am wondering what is different. I noticed you have VTL and all custom tools types and I'm wondering if you do the same thing with a stock non custom tool if it does the same thing. My part had no customer tools and was on a horizontal. I'm going to keep digging around here to see if I can pin it down. Feel free to send me any more information or files to [email protected].

There is an option in the MAstercam applet that allows you to choose your file open dialog style. For X6 it is a little different due to the vista/Win 7 styles but the options are there.

Peon, I understand you are busy but if you can take a minute or two to send me up a Z2G file of the part showing the arc issues and gouge I will get someone to give it a look over and see what is going on. Without the part I will chase my tail trying to duplicate this I bet.

Smirk, I am not experiencing the same behavior with the level manager dialog that you are seeing. It always opens in the last location I left it so it seems to be working correctly on my system. The dialog positions are written to the registry and if your other dialogs are coming up in the correct location then your registry permission should be fine. How about your view manager? Does it stay in the last place you had it open? If so and it's only the level manager we can try to edit the registry and see what is going on with it. If none of your dialogs are remembering their positions then it would point to a registry permission issue. Could be a security tool not letting it edit the registry as well. As far as the toolpath icons for HS toolpaths goes, We had numerous request about them and this change that allows for having individual toolpath type defaults now. I will pass along your comments to our PM team.

If you have the previous release of X6 15.0.3.28 you will need to uninstall it and then install the 15.0.4.3 version. There are no issues with previously created X6 files. BenK, can you be more specific as to what issue with re-selecting lathe geometry? There was a fix to the Pick off, cut off feature where it was losing the point data on operations and that HAS been fixed.

Thanks Rickster. I've searched the database and can't find anything that fits your description. I also had the developer take a look and see if he found anything and he came up blank as well. I'm going to drop you a PM and you can email me back direct. This way I can make sure this is logged, it can be duplicated and get it on someone's radar.

Hockey Guy, do you mean the link doesn't work at all or the file that gets downloaded doesn't work. I received an email from a user mentioning that Acrobat can't open the file and this was sent to our web guy for review. My web guy says try it again. They republished the file and it works find here. Rockster, I am searching the database now to see what I can find. Thanks for the info and I'll see if I can chase something down for you.

Rickster, seeing I have no clue what you are talking about I would say that CNC isn't fixing this issue. I'm sure you reported so can you share the bug number with me so I can follow-uo? Thanks!

we are testing the fixes now and hope to have everything back up and running next week.

Thanks JP. We normally don't do any modifications to the InHouse Posts but I'm sure InHouse will have some updates available if they are not already. You can get the updated MP documentation portfolio from your reseller and it explains what is needed to support this new feature. It's not much at all but the POCO feature presents data to the NCI a little differently and MP and the post need to know that this data is in the NCI.

yes that is a new option in X6. Requires some post mods though.

Sorry CamMan1, I should have stated OUR developers but I was typing like a mad man to get something posted. Good news is we are testing a fix for the default issue now, still waiting for word on the others.

Sorry for being late to the game here all, but I have been out of town on vacation and just getting caught back up on these issues. We ran into a couple of issues that we didn't like in the X6 release and wanted to take a quick look at them so we disabled the downloads. The issues we are looking at are: 0 value for vertical arc entry in Optirough Toolpaths is causing the tool to hit the part. 0 was valid and working in X5 MU1. Entering a small vertical arc value makes the tool clipping the part go away. Problem using the parameter save function inside a toolpath corrupting your default file - Seems to be only when using the updated defaults function inside the toolpath parameter page of a 3d HST toolpath. If you are using X6 just back up your default files in case you updated them by mistake in X6 and they get corrupt. Even if they get corrupt, you can still continue creating the toolpaths you will just see a error dialog every time the defaults are accessed - just click through it. When selecting geometry that has points from some toolpaths (facing, circle mill, etc) using Pickoff / pull/cutoff feature in X6, the points are being lost in the original operations and the ops dirty dirty. You have to add the point geometry back in or do not select the points during geometry selection. X6 file association is broken - causes X6 files to not be associated to the X6 functions - ie - double clicking on a MCX-6 opens X6 but with a blank file and not the part you double clicked on. You can manual edit the registry to fix this one. We are looking into what is required to fix these and determining if a patch is sufficient or if we need to re-release the X6 installs. I will post again as more information becomes available. Sorry for the inconvenience at this time. If you have X6 downloaded and running, keep on going - these issues are isolated to specific areas. Jim

Sorry for being late to the game here guys, but I have been out of town on vacation and just getting caught back up on these issues. We ran into a couple of issues that we didn't like and wanted to take a quick look at them so we disabled the downloads. The issues we are looking at are: 0 value for vertical arc entry in Optirough Toolpaths is causing the tool to hit the part. 0 was valid and working in X5 MU1. Entering a small vertical arc value makes the tool clipping the part go away. Problem using the parameter save function inside a toolpath corrupting your default file - Seems to be only when using the updated defaults function inside the toolpath parameter page of a 3d HST toolpath. If you are using X6 just back up your default files in case you updated them by mistake in X6 and they get corrupt. Even if they get corrupt, you can still continue creating the toolpaths you will just see a error dialog every time the defaults are accessed - just click through it. When selecting geometry that has points from some toolpaths (facing, circle mill, etc) using Pickoff / pull/cutoff feature in X6, the points are being lost in the original operations and the ops dirty dirty. You have to add the point geometry back in or do not select the points during geometry selection. X6 file association is broken - causes X6 files to not be associated to the X6 functions - ie - double clicking on a MCX-6 opens X6 but with a blank file and not the part you double clicked on. You can manual edit the registry to fix this one. We are looking into what is required to fix these and determining if a patch is sufficient or if we need to re-release the X6 installs. I will post again as more information becomes available. Jim

Sorry for being late to the game folks, but I was out of town on vacation and just getting back into things here. We have the developer looking into the issue and it does have to do with the vertical arc entry being set to zero. Not sure why yet but we are looking at it and figuring how ho to provide a fix. That fix could be a patch or a re-release of X6. More to come as I get details. Jim

10/31 is the maintenance date in X6 and we are really pushing hard to have the release ready no later then 10/31. That doesn't mean a package shows up on your door step by then, but electronic downloads of the official release should be available by then.

-2 is potentially a valid NCI value for fr$ which means Rapid feedrate - usally come sout on the G0 moves in the NCI. It can also be -1 which means unchanged from previous move. That is why we created the fr_pos$ feedrate variable which always carries the actual value of feedrate and it will never be -1 & -2. Seeing this is in Drilling I'm pretty sure it isn't dealing with the rapid move that is present before the 81 NCI lines and that is why a feed of -2 is coming out but seeing I don't have the post and part file I'm just taking an experienced guess.

IS the feed value of 20 correct? multiplying by -1 will only change the sign which is fine if the value itself is correct. what is fr$ formatted for? fs and fmt assignments are what I am taking about.

now search your post to see where fr2 is getting it's value. It's not a predefined variable so there is some place in the post where in assignment occurs so go track it down.

Find out what variable is being used to output the Feed in the drill cycle postblock and trouble shoot from there. IF using fr$ try using fr_pos$.