Mick, thanks for the response.

I did try many different variations in the start trigger fields... no luck.

It's not that much of a bother to add the blank line, I already have it open to check it anyway.

Thanks

In case anyone else encounters this problem, here is a simple work around.

It seems that both MXC comm and Cimco were ignoring the very first line of the code

and after much experimentation, simply adding a blank line ahead of the post made

the controller recognize the program number properly.

I don't know if this is a bug or something specific to my set up, but... that's where I ended up.

Hello, first time here.

I recently upgraded to Windows 7 and have installed Mastercam 6 x64.

The install is fine, and migration of existing operations and posts are as need be.

Previously I was using a third party CNC communication software (NcWare CncCom) to

Interface with our machine, Komo vr512 with G.E. Fanuc Series O-M.

The NcWare program does not support 64 bit operating systems so I am trying to use

Mastercam’s communication interface.

I am successfully able to transfer files to the Fanuc however, by default, Mastercam does not transfer

the file number assigned in post, or the Fanuc does not recognize how Mastercam is transmitting the file number.

On the “send” screen within Mastercam Editor, the file number displays correctly, eg. 4201.kmo, but after

transfer, Fanuc displays file as O0001. Subsequent files transferred from Mastercam all default to O0001,

resulting in an error on Fanuc.

Same goes in Cimco.

First line of code is Oxxx, and transfers fine with old computer and CncComm.

I am wondering if there is a parameter within the default machine for Fanuc Om.xml that can be changed

to recognize or name the file as posted.

Any help would be appreciated.

Thank you.

Philip