Is There A Way To Verify G68 Is Active?
Close
Login to Your Account
Likes Likes:  0
Results 1 to 8 of 8
  1. #1
    Join Date
    Nov 2018
    Country
    UNITED STATES
    State/Province
    Utah
    Posts
    24
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    1

    Default Is There A Way To Verify G68 Is Active?

    I'm using the probed location of two bores to find the rotation for my G68, which I call at the beginning of my program. I've observed that the group 50 active code(while running) shows what's contained in my R variable. However, in the program below, the value changes part way through. When I single block, it seems to be at N180 and I can't figure out why.

    The angle is small enough that it isn't visually perceptible so I'm hesitant to continue running without having any way to verify the WCS rotation is still working.

    Doesn anyone know a way to verify this on NGC while running? 2016 Haas Minimill. Thanks


    %
    O01001 (Outer 1/2"-13)
    (Using G0 which travels along dogleg path.)
    (T3 D=0.25 CR=0. TAPER=45deg - ZMIN=-0.06 - chamfer mill)
    (T4 D=0.25 CR=0. TAPER=140deg - ZMIN=-0.04 - spot drill)
    (T5 D=0.187 CR=0. - ZMIN=-0.25 - flat end mill)
    (T6 D=0.372 CR=0. - ZMIN=-0.8 - form mill)
    (T7 D=0.5 CR=0. - ZMIN=-0.25 - reamer)
    (T10 D=0.4219 CR=0. TAPER=135deg - ZMIN=-1.0124 - drill)
    N10 G90 G94 G17
    N15 G20
    N20 G54 (Calling for G68);
    N25 (Code for Co-ordinate rotation)
    N30 #10000=ATAN[[ #5242-#5222]/[#5241-#5221]]
    N35 G68 X0. Y0. R#10000
    N40 G53 G0 Z0.

    (Spot 6)
    N45 T4 M6
    N50 S4667 M3
    N55 G54
    N60 M8
    N65 G0 X-5. Y5.
    N70 G43 Z0.8 H4
    N75 G0 Z0.2
    N80 G98 G82 X-5. Y5. Z-0.04 R0.2 P30 F23.615
    N85 G80
    N90 G0 Z0.8

  2. #2
    Join Date
    May 2019
    Country
    UNITED STATES
    State/Province
    Montana
    Posts
    30
    Post Thanks / Like
    Likes (Given)
    19
    Likes (Received)
    18

    Default

    G68 should be looking at #189 for the angle. So:

    IF #189=0 THEN whateveryouwanttodo

    At the end of the program, go #189=0, then reset it at the beginning of each cycle.

  3. #3
    Join Date
    Nov 2018
    Country
    UNITED STATES
    State/Province
    Utah
    Posts
    24
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    1

    Default

    Quote Originally Posted by 360427 View Post
    G68 should be looking at #189 for the angle. So:

    IF #189=0 THEN whateveryouwanttodo

    At the end of the program, go #189=0, then reset it at the beginning of each cycle.
    Thanks I'll singleblock that and see what happens. Any idea why it has to be that one specifically?

  4. #4
    Join Date
    Jul 2016
    Country
    UNITED STATES
    State/Province
    Indiana
    Posts
    232
    Post Thanks / Like
    Likes (Given)
    2
    Likes (Received)
    31

    Default

    #189 is where the probe result is stored. G68 doesn't use it unless you tell it to.

    What's on line n180?

  5. #5
    Join Date
    Nov 2018
    Country
    UNITED STATES
    State/Province
    Utah
    Posts
    24
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    1

    Default

    Quote Originally Posted by friesen View Post
    #189 is where the probe result is stored. G68 doesn't use it unless you tell it to.

    What's on line n180?
    Oh my bad. The correct line is N80. I'll get to that line and single block twice with(seemingly) nothing happening. Presumably one for G98, and one for G82? On the second press of cycle start, that active code I'd previously been watching changes from what I had in my rotation variable (R#10000) to the R value in the G82 (R0.2), which seems to remain for the rest of the program.

  6. #6
    Join Date
    May 2019
    Country
    UNITED STATES
    State/Province
    Montana
    Posts
    30
    Post Thanks / Like
    Likes (Given)
    19
    Likes (Received)
    18

    Default

    Quote Originally Posted by TheWolfOfWalmart View Post
    Thanks I'll singleblock that and see what happens. Any idea why it has to be that one specifically?
    Yes, it's due to my poor reading comprehension. The way you have this written, you would use #10000 in my example, not #189. This doesn't check if G68 is active, but by resetting it to zero at the end of the program, it will tell you if the probe ran and, in fact, dumped a number in to #10000.

  7. #7
    Join Date
    Jan 2014
    Location
    Temecula, Ca
    Posts
    2,646
    Post Thanks / Like
    Likes (Given)
    1210
    Likes (Received)
    3462

    Default

    Don't know about the NexGen control, but on mine, hit the CURNT CMDS button until the active codes page come up. It'll show you if G68 or G69 is active. Are you sure #10000 isn't getting cleared or overwritten? Try using #120

  8. #8
    Join Date
    Nov 2018
    Country
    UNITED STATES
    State/Province
    Utah
    Posts
    24
    Post Thanks / Like
    Likes (Given)
    21
    Likes (Received)
    1

    Default

    Quote Originally Posted by 360427 View Post
    Yes, it's due to my poor reading comprehension. The way you have this written, you would use #10000 in my example, not #189. This doesn't check if G68 is active, but by resetting it to zero at the end of the program, it will tell you if the probe ran and, in fact, dumped a number in to #10000.
    Ha ha gotcha. I can confirm a number is making it into that variable. I've gotten other ops for the same part running under the same G68 rotation to work(with the expected number remaining in both active codes and the correct variable.) There is just something weird about the canned cycle line...G68 in the NGC manual doesn't mention anything about canned cycles though so I'm lost.


Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •