Post Wiki

Most of the time, just like any other type of error, look to the log to see what went wrong. There should be an explanation.

Here at Cimquest, we don't often run into errors updating, because in general we watch the error log and fix it as we go. But sometimes, we might miss an error now that the log isn't opening as a separate text file, like it used to, when things go wrong. So users can easily miss important update problems and what you commonly will get is a someone asking why a post won't update without any warning messages indicating what went wrong.

What's happening in this case, 99% of the time, is the text section did not covert properly when moving from 2017 up. In 2018, the text section was converted to xml. If the 2017 file had a problem converting to xml, the entire post update just fails, with no warning. Most other failures have a warning so this one is most assuredly from the text section conversion.

Finding what went wrong is the next question. Often, its a tag that's missing. Either the opening tag, or the end tag.

this was the issue in the last one that came up. The end tag was missing in 2017 so it wouldn't update to 2020. It was missing [CTRL_TEXT_END] at the end

More commonly, though, it happens when someone takes a V9 file or prior and updates from that. V9 and before did not have a txt section. They had a separate txt file. So if a post is really, really old it doesn't even have this section at all so once you get to 2017, it looks great, but one more version and it breaks. If this is the case, just grab the text section from a generic CNC 2017 post and dump it into the 2017 file before updating further and all will be well with the world.

Mach Sim can have a couple issues when updating. There are no good log files, so I just have a few things I check when some one says they are having trouble when updating MachSIM.

Some things we've run into:

Problem : CL File warning

If you see anything with a CL File warning, it will look something like this:

it comes from having 2 nc outputs in one simulation.

Solution : Only simulate one .nc output at a time

This is the only issue I know of for MachSIM that does not involve setup or updating.

Keep in mind, just like when you run an update on a .pst that is already up to date, if you update a file that doesn't need it, you won't see it show up in the folder you are updating to. This is especially true of Mach Sim. A lot of the files in the machine folder will not make it, because they don't need updating.

Also, PY might be sending the most current version anyway, so it might not need updating. Since the MachSim only contains the pst/psb files, NOT the machine files, they can be backwards compatible. So if you've updated a 2020 file to 2021 when PY already had the post in 2021, the new MachSim folder you've created may be missing the pst/psb files!

Rather than updating the whole mach sim folder, it might be a good idea to just copy the updated pst and psb files into the original MachSIM folder to avoid these issues altogether.

The name of the folder MUST match the .pst file. Also, if the image file has a different name, it won't have an image in the simulation window. That one's not critical, but good to know

Post External check box will not show if Folder does not match .pst name

Make sure Folder name, .pst file and image files all have the same name

This warning is tough to fix only because the user will never call this a watermark. They will say “I'm getting a warning in my MachSim to contact my reseller.” Or maybe some mention of a license required to run MachSim. So if you hear this, its the watermark error. It looks like this:

The warning states : “Post Processor License Required. Please contact your Reseller for a license.”

I don't think of this as a watermark, but that's that PY calls it.

This issue might just be a nuisance with the ugly red warning, or it could mean the machine is not lining up when running simulation. Best thing to do, is make sure its not there, so we know everything is kosher.

To do that we need to run the Postability “patch.” Keep in mind, they call it a patch, but it really is a full install that CANNOT be installed over the current version. Believe me…I've tried… Instead, delete any stand alone machsims that exist, and install this one.

Here are the steps:

- Go into Add/Remove programs, and REMOVE any stand alone MachSIM programs you see there.

- Delete folder location C:\Program Files\Mastercam 2021\Mastercam\simulator_std_alone (or similar) if it exists. If not, continue on to the next step.

- Download the latest MachSIM patch from Postability. They send us the latest one every version or so. Find the latest patch here under “Mastercam 2021 patching links” : https://wiki.post-hq.com/doku.php?id=procedures:postabilityphone&do=

- Once the patch is downloaded on the users machine, Run the .exe AS ADMINISTRATOR

- During install, you must choose a new installation path. Postability suggests “C:\Program Files\Mastercam 2021\Mastercam\simulator_std_alone.” I have used this path with good results as long as it doesn't already exist.

- Finish the install.

-Open up a file with toolpaths on it and the correct post loaded up and Hit Simulate in Mastercam

- Make sure the External Post button is checked

- Hit the Simulate button and hopefully when simulation opens, the watermark will be gone.

Here is what you need to know about Moduleworks and Post Linked Machine simulation for Mastercam 2022 and beyond.

Who's affected
Clients using post linked machine simulation and the external post button in machsim. Dealer licenses should continue to function as they had in previous mastercam versions.

What happens
External post will be unavailable in 2022, and each new MC version, without a patch install first, then a license update. this is one patch per mastercam PC, and one license code per mastercam PC, per sim!

How does that work?
Postability has given us a patch linked below to install first, and also a list of license codes which are in a linked document below.

First install the below linked patch file while all instances of mastercam are closed on the client computer:

Machsim service pack MC2022

The first document below lists all the moduleworks license keys we currently have for individual clients of Cimquest.

1. You can look up a license key by client in this document and provide it to the client when they start running mastercam 2022
2. The initial batch of keys we received had an expiry, which Postability did not know about, we are replacing all the keys with new ones that will never expire as we receive them.
3. Note: there can be multiple keys for one client if the client has multiple mastercam licenses. The key for the MC license currently being run will have to be supplied/installed. - The client needs to run each mastercam license, and install the key individually for each MC license they have.
4. We don't have license keys for every client that is using machsim, as not all clients are active with Postability / IHS maintenance
   - If the client is not in the document list, the post department needs to handle getting a license key for that client
   - Any client on at least limited level cimquest maintetance will be approved. Post department will order without checking with sales rep. These keys will change if customer's licenses changes.

No post or machsim files need to be exchanged to enable 2022 machsim. Just 1. install above patch, 2. install code below

1. We obtain the code, and give it to the client.
2. When the license is not in the below list, please contact the post department as client maint renewals may need to happen behind the scenes.
3. Please see this page if evaluating eligibility in Post Dept: Determine if a maintenance renewal can be provided at no charge

Machsim License Keys MC2022+

The 2nd document is general info about how to apply the license:

Machsim - External Post Licensing MC2022+