Hi, my name is Andreas Grimm from Camaix. Camaix has originally developed the machine simulation which has now been taken over by Moduleworks and is part of Mastercam now. Just for your information: Camaix has recently developed a fully-integrated solution for Gcode verification for certain types of controls and machines which is working with Mastercam machine simulation. Please check on www.camaix.com. We also supply time limited test versions for supported machines. The price is far below of what you have to pay for VeriCut.

Hey guys - it would appear there are two issues being discussed here - one being general issues with lathe in more "generic" functionality such as main to sub-spindle transfer and sub-spindle functionality and the more "advanced" functionality of Mill/ turn and synchronizing of multiple turrets with main and or sub spindle. And I realize that what I am about to recommend does not answer all the frustrations discussed but I suggest you take a look at sync lathe from Camaix as that is attempting to address the issue of multiple turret synchronization currently in MasterCAM and address this by uses currently 2 streams of POSTED code and combines it with machine simulation and collision checking to insert wait and sync codes where applicable and user control. Your feedback would be highly appreciated and welcomed. http://www.camaix.intrameld.net/downloads/..._Level1_VX4.exe

Nice work Al.

Hi All, I am looking to update a V9 c-hook to X3 and X4 - I am missing the original V9 SDK specifically the files chooks.h and ncbase.h - ideally I would like to get hold of the complete V9 SDK for reference purposes - thanks in advance

contact your reseller .... just kidding Bryan - sounds like a .dll hang up - do you have any other operations already built on the part or is this the first op ?

http://www.camaix.net/SyncLathe_en.html This is a very new product from Camaix - it is actually synchronizing g-code.

Hi Bill, This is a version 9 Maintenance Release - 0105 stands for the release date of January 2005. You would have to have be on maintenance to receive that release.

Version is shown as 1,0,0, 1 dated dec 14th 2005 - and File version at top shown as 10.1.3.30

Roger thanks for the reply this post is a protected post at this point- here is the fatal error warning I get 23 - 27 Feb 2006 10:21:54 PM - A line is too long in the post file. This condition makes it impossible to continue! 24 - 27 Feb 2006 10:21:54 PM - Line number - 17460

Trying to update Mill V9 post to VX and it keeps crashing the updatepst chook - any tips out there for what may make this happen ?

V9 is based upon proven technology going back close to 20 years - VX is a complete rebuild using more "modern" software development technologies - for existing users including myslef V9 is at the end of the day ;reliable - VX is more powerful in the long run but it was built for the future in mind and will take some time to be as reliable

CAP Technologies peut etre ?

Have discovered this is a post "issue" and has been addressed in upcoming MR1

If I am not mistaken the EIA/ISO may have been an option - it is worth verifying with Mazak whether they were purchased with the machine. Mazatrol Post Processors are also available for Mastercam.

jnicely 1. does the control hae 2 x RS232 ports - if so then the second port is normall used for eia/iso upload download. 2. the dnc option should appear next to cmt i/on the screen. 3. what made you update from camware to mc ?

no dice mate thats the first thing I tried -this works fine in V9 is there a new limit on number size ? I cant beleive there would be - maybe a new setting somewhere if I write it as neg_constant : 42949672.96 for example with or without a format statement it comes out

Trying to update a post from V9 to VX I have a constant set like so below. neg_constant : 4294967296 Problem is the new post wont read it because it has two many digits or too big - it is truncated by post to 999999999.999999999 therefore not allowing logic to work correctly downstream any ideas why this is happening ?

Has anyone seen an issue with canned grooving in V9MR0105? With canned cycles a 60000 flag is meant to be output at beginning and end of roughing sequence in the NCI file - but in grooving I only see one. Definately one for the post gurus here.

OOps missed your last thread. ..duh

Bubba Sounds likes its overheating