Not that I know of - it is not possible to exclude / filter for those. You may be able to trace $P_GG[1] which would tell you the index number of the G code active in group 1, but have not tested this yet.
Another update: I’m sorry, but it is not possible to suspend the trace while in G0. In Operate, It is possible to trace the current G Code by group with the variable /Channel/State/aGG[u1,1]. This will return an integer value for the active G code in the group. The integer to command conversion is in the Programming Manual-Fundamentals. In new versions, it is in Chapter 17 (Tables), 17.4 (G Commands). G0 will have a value of 1, G1 will have a value of 2. This can let you manually work out the on/off part condition. If your version of Operate supports saving .csv files, this data manipulation could be handled in Excel or LibreOfficeCalc.
Thanks for the great video it was very informative. You went over how to automatically trigger traces, but is there a way to automatically trigger the saving of the trace file? I'd like to save multiple trace files during a longer machining run automatically. Is there a way to do this?
Great tutorial. Was desperately looking for Trace usage... Thanks for posting. Can you also give tips on how to get Trace data to an external PC for real time monitoring. thanks in advance
It depends on the vintage of your software and the update frequency you are looking for. There are several possible solutions. Please contact your local Siemens office.
Thanks! do you know if I could avoid trace during G00 steps? (I'm interested in finding max torque/currents during machining)
Not that I know of - it is not possible to exclude / filter for those. You may be able to trace $P_GG[1] which would tell you the index number of the G code active in group 1, but have not tested this yet.
Another update:
I’m sorry, but it is not possible to suspend the trace while in G0.
In Operate, It is possible to trace the current G Code by group with the variable /Channel/State/aGG[u1,1]. This will return an integer value for the active G code in the group. The integer to command conversion is in the Programming Manual-Fundamentals. In new versions, it is in Chapter 17 (Tables), 17.4 (G Commands). G0 will have a value of 1, G1 will have a value of 2. This can let you manually work out the on/off part condition. If your version of Operate supports saving .csv files, this data manipulation could be handled in Excel or LibreOfficeCalc.
Thanks Well Explained
Thank you~If I want to trace and record 5 axis(XYZAB) position,velocity and torque at the same time,are these possible?
To the best of my knowledge you can
Thanks a lor for all this information! I aprecciate it a lot! 😬
Welcome
Thanks for the great video it was very informative. You went over how to automatically trigger traces, but is there a way to automatically trigger the saving of the trace file? I'd like to save multiple trace files during a longer machining run automatically. Is there a way to do this?
You can click save trace when the trace is done.
Great tutorial. Was desperately looking for Trace usage... Thanks for posting. Can you also give tips on how to get Trace data to an external PC for real time monitoring. thanks in advance
It depends on the vintage of your software and the update frequency you are looking for. There are several possible solutions. Please contact your local Siemens office.