Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.
Use your display name or email address to sign in:
I’m a bit confused here….
Mastercam is a great product but the post is locked up.
So you purchased Esprit, which has the flaws you mentioned, and may need an expert Esprit programmer to drive it.
Only when something doesn’t post properly, you will find that Esprit posts are just as locked up as Mastercam.
If editable post are the concern, choose Partmaker. I can make a 13 axis, 3 channel control dance like Fred Astaire on meth.
The flaw is thinking that any cam system has specific posts right out of the box for a machine 20 years behind the times.
You did buy a post specific for your machine, right?
Why would to not want a post catered to EXACTLY how you want a tool change to happen. This is a simple post mod, and You never have to worry about it again.
It’s not a hack. It’s having a cam system do exactly what you want it to do.
All you see with returning the userdomain environment variable is the NETBIOS domain name.
Check the %userdnsdomain% to see the DNS domain. This will show you the fqdn suffix.
The mode 2 "NameSamCompatible" result in the MP query is for backwards compatibility to NT4.0, Win 95/98 environments.
The fact that mode 9 "NameDnsDomain" doesn't return tells me there is an issue with the top level domain suffix, or you are really in a workgroup, not domain.
You can go into control panel -> System and see the Domain and suffix as it is connected.
That is what I would expect to see from Jeremy. That is why he is only getting the output for mode 2, IMO.
Then, the only way would be to parse the user name out of the local SAM name, or create a domain controller to handle naming conventions.
Edit: or to join an existing domain.
Yes, we have Misc reals set up for SGI. M255 is default if we don't enter a value. That way we can control for every op.
This is for our Pro 3. Pro 5 uses different values. Still in the M250's, but different.
We turn the spindle on the same for a rigid tap as any tool, then handle the M135 in PTAP.
Here is my PTAP postblock for my makino:
ptap$ #Canned Tap Cycle
pdrlcommonb
#RH/LH based on spindle direction
if rigid_tap, pbld, n$, "M135", *speed e$ #Rigid Tapping
if use_pitch = 0,
[
pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl,
prdrlout, *feed, strcantext, e$
]
else,
[
if met_tool$, pitch = n_tap_thds$ # Tap pitch (mm per thread)
else, pitch = 1/n_tap_thds$ # Tap pitch (inches per thread)
pcan1, pbld, n$, *sgdrlref, *sgdrill, pdrlxy, pfzout, pcout, pindexdrl,
prdrlout, *speed, *feed, !feed, strcantext, e$
]
pcom_movea
Gives this output:
N530T53
(10-32 CUTTING TAP)
M6
M11
G0G54.1P1G90B0X-1.0824Y-5.4004S1600M3
M10
M255
M8
M26
G43Z8.H1
T126
(TAP 10-32 HOLES)
G0G90
M135S1600
G84Z7.135R7.685F50.
X1.1876
X3.4576
Y-6.6004
X1.1876
X-1.0824
G80Z8.
............
Our A61's don't use M29. They use M135. They are Pro 3. But same with our F5 with Pro 5. That is how our post works too. Have never had issues.
This is from the book.
This was all well before he left. in 2013. But I'm pretty sure he didn't direct the individual to save the sim session and upload to You tube.
But who is Partmaker's CEO (or AD's now), makes no difference. The policy is set.
We do not allow any proprietary info out the door for support purposes.
eMastercam - your online source for all things Mastercam.
Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.