Skip to main content
Jun 15, 2025 7:18 AM UTC
Acknowledged

Add a search function (Ctrl+F) to the menu for playing the toolpath (Manufacturing)

Related products:Creo Parametric

1. What version of the software are you running?
Creo11

 

2. What is the problem?

An offer to the CREO developers to add a search function to the menu of playing the toolpath by NCL-file (Manufacturing). This function is very useful for postprocessor developers and search for specific strings of NCL-file in the play menu.


The problem is in the analysis of the postprocessing result.
After postprocessing the ncl file and subsequent analysis of the *.lst file, it is sometimes extremely difficult to find the problematic CL record found in the *.lst file in the toolpath playback interface (graphical representation of the trajectory).

For example: It is necessary to examine the CL-record in the *.lst-file after postprocessing
2321>GOTO /-24.61144,20,-75.18996,0,1,0
which is presented by the postprocessor as a sequence of blocks:
2321 2322 2301 CC X12.632 Y108.216$
2321 2322 2302 C X-24.611 Y75.19 DR-$

It is necessary to find this CL-record
2321>GOTO /-24.61144,20,-75.18996,0,1,0
when playing back the CNC program and track the position of the tool graphically relative to the workpiece.

If the toolpath player had a CL-record search, then in the CTRL+F window you could enter the phrase: GOTO /-24.61144,20,-75.18996,0,1,0

 

sstavruk_0-1749971618705.png

+ Ctrl+F

 

I don't think this is that hard to do, and for large NCL files it would be very useful!


3. Are you using a workaround? If yes, please describe it.
Yes, we do. We save the CL file, and then manually find a similar entry in the trajectory player window for a very long time.

 

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
See p N2.


5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)
This problem increases the time it takes to find postprocessor errors by 300…500%. The number of users depends on the number of workstations at the customer’s enterprise: from 4 to 100 workstations.

 

1 reply

Community Manager
Jun 17, 2025 11:44 AM UTC
Status changed to: Acknowledged

Thank you @sstavruk for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.