Operations Manager Question

[Jim at Gentex]

This is weird and probably has an obvious answer.

Why is my Operations Manager greyed out, and how do I make it active?

I just installed 2018 on a different workstation, opened a file on the network, and tried to regen and post the toolpaths, but the ops manager is not responding.

What am I doing wrong?

[Guest]

Are you on a Nethasp?

If so, did you get a message about a license not available?

if so again, have you checked to make sure you are pulling the correct license?

[Jim at Gentex]

No it's a local USB hasp.

The file opens, and I can do anything else except use the operations manager.

As I said, it appears to be greyed out like it is inactive.

There are toolpaths there, I just can't select them, backplot them, or post them. :OldForumHeadscratch:

I tried closing the file and reopening, and closing Mastercam and reopening but it's the same deal.

[Pete Rimkus from CNC Software Inc.]

The only time I've seen this is if you're using a local HASP that does not have a license for the product used to create the toolpaths in the active group.

For instance, I opened a part containing Mill operations using a HASP with only Design enabled, and I can neither select, nor post, not backplot the operations.

But I get warning messages about not have the correct license.

 

The other possibility might be that even though you've got a local hasp plugged in, your registry might be saying 'look for a nethasp' ... so you might not have access to the products that you think you do

Edited August 31, 2017 by Pete Rimkus from CNC Software Inc.

[gcode]

try this

make sure the correct machine def can be seen on this machine

open a fresh copy of MC2018

Load the correct machine definition

now try opening the file that's giving you trouble

[Leon82]

Does 2018 still use the hasp manager? We always had to switch ours on new installs of x9 to the net hasp

[Jim at Gentex]

On ‎8‎/‎31‎/‎2017 at 4:01 PM, gcode said:

try this

make sure the correct machine def can be seen on this machine

open a fresh copy of MC2018

Load the correct machine definition

now try opening the file that's giving you trouble

^^^^^This^^^^^^^^^

The default machine def was loaded when I opened the troublesome file.  I changed it to the correct def and all is well. 

Thanks, G