VERICUT Users' Forum

Due to relentless spammers, we are no longer automatically accepting new forum registrations. If you wish to register for this forum, please send an e-mail to: info@cgtech.com

You are not logged in.

#1 2017-08-29 10:57:56

paehv
Senior Member
From: Eindhoven, Netherlands
Registered: 2005-01-17
Posts: 167
Website

Heidenhain ~ command not processed

Simulating Heidenhain probing cycles is almost driving me crazy

In my existing controller (based on Hei530.ctl from some version back) I try to get the probing cycles going.
For good reasons I can't update to the latest Hei530.ctl from the cgtech library.

What happens is that on the TCH PROBE line the correct probing cycle is called, but NONE of the following Q parameters get set.
Because the word ~ is set as > Special > Contiuation, I would expect that the whole cycle block would be interpreted as one block, but is is still treated as seperate lines???

5  L  X+50  Y+50  Z+100 R0 FMAX
6  TCH PROBE 431 MEASURE PLANE ~
    Q263=+10   ;1ST POINT 1ST AXIS ~
    Q264=+3    ;1ST POINT 2ND AXIS ~
    Q294=-4    ;1ST POINT 3RD AXIS ~
    Q265=+45   ;2ND PNT IN 1ST AXIS ~
    Q266=+3    ;2ND PNT IN 2ND AXIS ~
    Q295=-25   ;2ND PNT IN 3RD AXIS ~
    Q296=+46   ;3RD PNT IN 1ST AXIS ~
    Q297=+42   ;3RD PNT IN 2ND AXIS ~
    Q298=-4    ;3RD PNT IN 3RD AXIS ~
    Q320=+2    ;SET-UP CLEARANCE ~
    Q260=+100  ;CLEARANCE HEIGHT ~
    Q281=+2    ;MEASURING LOG

I've set the ~ word as Special > Continuation
In the events there is the SetPreProcessorType macro with override 6

When I load the Hei530.ctl from the V8.0.3 library, It reads all belonging Q parameter when entering the TCH PROBE line

I'm sure that there must be antother setting that i'm missing.
Any ideas?


Patrick Delisse
KMWE Aerospacehttps://www.kmwe.com
(Vericut V9.5, Siemens NX2206, Campost)

Offline

#2 2017-08-29 20:31:40

DaveF
Senior Member
From: Valencia, CA
Registered: 2005-08-20
Posts: 304

Re: Heidenhain ~ command not processed

Hi Patrick,
I don't know anything about Heidehain, but Perhaps ..

If ; is set as begin comment, it may  be reading the ~ as just part of a message.


Dave Frank
Aerospace Dynamics International, PCC
Valencia Ca
"Where else can you have this much fun,.......and get paid???."

Offline

#3 2017-08-30 05:27:39

paehv
Senior Member
From: Eindhoven, Netherlands
Registered: 2005-01-17
Posts: 167
Website

Re: Heidenhain ~ command not processed

Thats what the SetPreProcessorType macro with override 6 should take care off.

<quote>
SetPreProcessorType
Function — MISCELLANEOUS
Status — ACTIVE
Comment — Added V7.0.2
Inputs —
Text: Not Used
Value: Use to specify the type po preprocessor
0 = No preprocessor used (Default)
1 = Preprocessor to parse blocks of Siemens 3T type data.
2 = Preprocessor to parse blocks of MAKA BWO C900 type data.
3 = Preprocessor to parse blocks of Elexa E580 (and E560) data.
4 = Preprocessor to parse blocks of Bosch Rexroth Indramotion MTS data.
5 = Preprocessor to parse blocks of Siemens 840D data
6 = Preprocessor for Heidenhain data
Controls what type of preprocessor is required to translate NC code to a more standard

Value = 6: For “TCH PROBE” and “CYCLE DEF” statements, comments are stripped out.
For “TCH PROBE 0.0”, Statements like: “TCH PROBE 0.0 REF. PLANE Q1000
X+” are converted to: “TCH PROBE 0.0 X+1000”
<endqoute>


Patrick Delisse
KMWE Aerospacehttps://www.kmwe.com
(Vericut V9.5, Siemens NX2206, Campost)

Offline

#4 2017-09-02 18:48:05

MustaphaC
VERICUT Specialist
From: Le Mans, France
Registered: 2004-10-14
Posts: 130
Website

Re: Heidenhain ~ command not processed

Hi Patrick, I can recommend you start from the latest library control, it has many standard HH probing cycles supported, including TCH PROBE 431. Also see samples "hei530_probing_....vcproject"


Mustapha

Offline

#5 2018-10-05 16:18:40

Vericut_McAtee
Senior Member
From: Fryeburg, Me.
Registered: 2011-07-17
Posts: 88

Re: Heidenhain ~ command not processed

When time permits! I need to work on the probing for our hei530_probing. I'm hoping to get some great info / insight for this thru this thread.

Offline

#6 2018-12-18 07:47:27

paehv
Senior Member
From: Eindhoven, Netherlands
Registered: 2005-01-17
Posts: 167
Website

Re: Heidenhain ~ command not processed

I did get it going by having the post to output an extra comment line after the cycle witch tells Vericut to start simulating the cycle.

5  L  X+50  Y+50  Z+100 R0 FMAX
6  TCH PROBE 431 MEASURE PLANE ~
    Q263=+10   ;1ST POINT 1ST AXIS ~
    Q264=+3    ;1ST POINT 2ND AXIS ~
    Q294=-4    ;1ST POINT 3RD AXIS ~
    Q265=+45   ;2ND PNT IN 1ST AXIS ~
    Q266=+3    ;2ND PNT IN 2ND AXIS ~
    Q295=-25   ;2ND PNT IN 3RD AXIS ~
    Q296=+46   ;3RD PNT IN 1ST AXIS ~
    Q297=+42   ;3RD PNT IN 2ND AXIS ~
    Q298=-4    ;3RD PNT IN 3RD AXIS ~
    Q320=+2    ;SET-UP CLEARANCE ~
    Q260=+100  ;CLEARANCE HEIGHT ~
    Q281=+2    ;MEASURING LOG
7  ;EXECUTE PROBE 431

The TCH PROBE cycle is read line for line by Vericut and the Q variables are set
Line 7 (;EXECUTE PROBE 431) call the cycle by using a simple substitute command (Replace ;EXECUTE... by CALL...)


Patrick Delisse
KMWE Aerospacehttps://www.kmwe.com
(Vericut V9.5, Siemens NX2206, Campost)

Offline

Board footer