On the Internet and in many technical exchange groups, I often see some netizens asking for help. If the UG post-processing error is reported, a screenshot will be posted, such as this:
NX post-processing error, a large part of the alarm number is this 1770002, and then you can see that the event name is MOM_drill
No matter how specific it is, I can’t see it. In fact, I don’t see the cause of the problem. I didn’t say it. I told you that there was an error in the UG post-processing. So even if you ask for help, you can’t help you.
So, I’m here to teach friends who don’t have UG post-processing production technology how to view the specific information of post-processing alarms.
1. If it is our own NX post-processing and can be opened with the UG post-processing builder, we will tick √ in post-processing—[Output Settings]—[Display Error Details].
In this way, when you deal with errors after UG programming, you can see the detailed error information, as shown in the following figure:
2. If the UG post-processing cannot be opened with the constructor (such as downloaded from the Internet), you can also directly open the UG software system log file to view the specific alarm information, as shown in the following figure:
NX menu-[Help]-[Log File].
After opening, we first pull to the bottom of the log page, and then flip up a bit, you can also see the detailed alarm information in the log file.
With this detailed error message, you can basically see where the source code has a problem during post-processing. Like the above error report, the message is that the code in the loop cancellation is incorrect. Specifically, this variable is not declared. After we declare this variable, we eliminate the error.