Differences

This shows you the differences between two versions of the page.

--- mp:versions [2021/03/11 17:54] – [Troubleshooting Updates] sonya
+++ mp:versions [2022/11/24 15:59] (current) – russell
@@ Line 8: / Line 8: @@
 Here is a list of the versions:
+= 25\\
+= 24\\
 = 23\\
 = 22\\
@@ Line 39: / Line 40: @@
 updates 2017 thru 2019\\
 updates 2018 thru 2020\\
+updates 2019 thru 2021\\
+updates 2020 thru 2022\\
 Here is an example:
@@ Line 44: / Line 47: @@
 Say you want to update an X7 post up to 2021.  First, you can open 2017 and run your update.  Then you can update your 2017 post to 2020.  Then you can get it to 2021.
-===== Troubleshooting Updates =====
-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.
-The post team doesn't often run into errors updating, because in general we watch the error log and fix it as we go.  But users, and sometimes the tech team, 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 tech guy 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 some one takes an 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.
-==== Troubleshooting MachSIM updates ====
-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 I've run into:
-=== - Not all files made it to the new folder. ===
-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.
-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.
-=== - Folder/.pst/image files Don't have the same name ===
-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
-=== - Watermark ===
-I don't think of this as a watermark, but that's that PY calls it.  If you see the red warning when running machsim, find the latest email from PY.  Just search your personal email for Watermark and you should find it pretty quickly.  They always email us when they've updated the watermark, so the latest email from them should have the latest link to get this fixed.

Post Wiki

User Tools

Site Tools

Differences

Page Tools