CSE does not recognize the standard drilling cycle format (seperate lines with comments).
20 CYCL DEF 200 DRILLING
Q200=2 ;SET-UP CLEARANCE
Q206=250 ;FEED RATE FOR PLUNGING
Q202=5 ;PLUNGING DEPTH
Q210=0 ;DWELL TIME AT TOP
Q203=+20 ;SURFACE COORDINATE
Q204=100 ;2ND SET-UP CLEARANCE
Q211=0.1 ;DWELL TIME AT DEPTH
21 L X+10 Y+20 FMAX M99
22 L X+10 Y+15 FMAX M99
CSE will recognize the following shorthand from the OOTB post (all in one line, no comments):
CYCL DEF 200 DRILLING Q200=2 Q201=-15 Q206=250 Q202=5 Q210=0 Q203=+20 Q204=100 Q211=0.1
Can someone please provide the modifications required in the MCF/CCF CYCL_DEF_200 Metacode to recognize the standard (seperate lines with comments) format.
Thank you for your help.
CSE driver for heid from OOTB NX 11.0.1 and Python parser recognize it, no problem, Ihave tested it for measuring cycles.
Thank you for your reply.
The Measuring cycles may be working but the Drilling cycles are definitly not working.
I get a Parse error after reading '20 CYCL DEF 200 DRILLING'
Do you mean the Probe Cycles (500-589) in the OOTB HeidenhainTNC.CCF file?
If so where did you get the "TCHPROBE5XX" subprograms?
Can you provide an example of the "Python Parser"?
I wrote it that way, and it works in CSE.
24 CYCL DEF 200 DRILLING ~
Q200=3 ;SET-UP CLEARANCE ~
Q201=-13.0919 ;DEPTH ~
Q206=757.38 ;FEED RATE FOR PLNGNG ~
Q202=13.0919 ;PLUNGING DEPTH ~
Q210=0 ;DWELL TIME AT TOP ~
Q203=0 ;SURFACE COORDINATE ~
Q204=12 ;2ND SET-UP CLEARANCE ~
Q211=0 ;DWELL TIME AT BOTTOM
sorry for my late response. I was on longer vacation.
Maybe this is not longer an issue but I will write it also for other user who struggle with that.
In general on Heidenhain HMI the displayed NC Code is formated. The displayed NC Code looks in some cases different to the real NC code on the file system. The CYCLE DEF code is a very good example to show this. When you export the NC Code you will see the ~ when the parameters are line by line, or the other way around the controller will not accept the NC code if the ~ is missing in parameter lines. Sure you can also write it in one line without a ~.
At the end there is only one customization needed --> change the Postprocessor to output the correct NC code or write it manually.
In addtion a small techtip from my side. If you have a challenges like this on other controllers you have to modify the parser. This is not part of the MCF/CCF. The MCF/CCF includes the controller logic but not the "alphabet" or the grammar rules for the NC Code.