I just saw your question to me kota. I've sent an email requesting that you send your files to our tech support office. Email bounced back. Please contact our tech support office support at inhousesolutions.com with a copy of your post and a description of your problems. And please update your profile email so that we can contact you.

eMastercam.com was born today in year 2000!

Search for X+ http://www.gmccs.de/index.php?page=downloads.php

You should be able to use Mpmaster for the 4-Axis as well. Have you tried that?

I believe on the 2GB RAM version of M65, 256 MB of the video ram is from the card, another 256 MB is stolen from the computer's RAM, for a total of 512 MB video RAM.

And the UTENSILI block can be left blank from a posting standpoint, which the editor on the control will fill in after the fact.

Most Biesse posts use the Tool name field string in the Define Tool, parameters tabe to populate the ST1="" callout.

http://www.emastercam.com/ubb/ultimatebb.p...ic;f=1;t=025154

http://www.emastercam.com/ubb/ultimatebb.p...ic;f=1;t=025154

Just for the record, I didn't say Mastercam would run... Just pointing out that HASP drivers for 64bit exist.

Any new drivers for the HASP would be first available here: http://www.aladdin.com/support/hasp/hasp4/enduser.asp http://www.aladdin.com/support/hasp/enduser.asp

Thanks for the plug James. I'm forced here to admit that Brett, Chris, and now Russell are all responsible for pushing Mpmaster forward.

We have Mpmaster variations for both the standard Hurco, and the ISNC. Your dealer can request these posts from us.

It's not part of the install. Visit http://www.camaix.net/c-hook_downloads_v10.html

The CAMAIX post reads a '.par' file that I assume is created by the CAMAIX GUI post builder. We are not using this technique. If you search our sample 3/4-Axis post for '#machsim' you will see the necessary postblocks and sections that are necessary to output the .SIM file that is used by the machine sim product. To set up a machine, you need STL files to represent members of the machine, and an XML file that describes how they are connected.

I'm not using those codes in my post. What documentation are you using?

I'd think that if you're having WCS issues, it would relate to the model's STL passed along to machsim, not with the code.

I've been down the 'smash setup sheet into the post' route before. Setup sheets linearize arcs, do long-handing drilling, and a bunch of other simplifications that would need to be done in a more complicated manner to work in the context of a post, without breaking the post.

Not easy. I've kicked this around several different ways over the years. Right now they best I have is that when you 'post', you actually run a setup sheet (.SET) style that outputs nothing, but writes the time estimate per tool or per op, and total to a buffer. The it launches your actual post, which reads the buffer, kicks out the values as comments in your NC file, then deletes the buffer at the end of posting.

Corrected.

old_new_sw : 0

Welcome back!! In these parts, we're not allowed to use "toolpath" and "engineer" in the same sentence...

quote: That's just MESSED up!!!! [Curse] Wrong in every way, because that opens up the door for having to be charged again for a post for every new release of software.We don't do this, and I totally see your point, however I do see that there may be some wisdom in it. Since I don't know how my X2 post is going to run in X3, if I tied the working X2 post to X2, it gives me the ability to edit in necessary X3 changes when a customer contacts me. If I don't do that, and there are problems that can't be anticipated... You see my point? At least I get a chance to apply mods during the update to X3. Now charging for that service is another thing entirely.

Yeah - xmlconverter.exe does the trick.