Hello Guest it is July 20, 2019, 02:39:24 PM

Author Topic: G53 oddity  (Read 9371 times)

0 Members and 1 Guest are viewing this topic.

Offline Hood

*
  •  25,849 25,849
  • Carnoustie, Scotland
    • View Profile
Re: G53 oddity
« Reply #10 on: January 05, 2011, 07:32:41 AM »
I have simulated the Home switches and get as far as the Slab page but wonder whether there should be any inputs active?
I am really crap at VB so will have to take time to try and study this, will have a look when I get home tonight.
Hood

Offline tmead

*
  •  62 62
    • View Profile
Re: G53 oddity
« Reply #11 on: January 05, 2011, 07:54:23 AM »
Yes, the 'find clamp' button in version 20 had the following commented out:

'  Code "G0 G53 Z-1"            ' preparatory move of Z in machine coords
'  Hold
'  Sleep(100)
'  Answer=MsgBox("OK ?",0)

The G0 G53 Z-1 was the original, with a call to the 'Hold' subroutine, which is a While/Wend loop.
The extra Sleep 100 was added just in case, and didn't change the action
The messagebox was an extra debug attempt just to separate out the code segments and isolate the issue.

Tim

Offline tmead

*
  •  62 62
    • View Profile
Re: G53 oddity
« Reply #12 on: January 05, 2011, 08:04:24 AM »
Shouldn't need any other inputs at all.

To simulate the issue (or not !) you shouldn't need any other inputs, as it occurs before the sensing is active. It may get confused later in the script when G31 is called, although if no probe is connected it should either interpret that as a sensor failure or failure to detect, both of which are trapped in the code.

If no driver is installed you need to press the 'simulate' button on page 1 to set it to ignore the sensing, as G31 doesn't work on development machines without the driver.

Tim

Offline Hood

*
  •  25,849 25,849
  • Carnoustie, Scotland
    • View Profile
Re: G53 oddity
« Reply #13 on: January 05, 2011, 08:54:33 AM »
Ok heres wat I see here, because I dont have a machine I obviously dont see the axis moving so I have added OEM DROs 83,84,85 to the main page so that I can see the DROs counting.
I press initialise button and Z moves, I simulate the home switch and Z zeroes then Y and it does the same then X.
 X and Y then get set to  minus 1 but Z stays Zero. Slab/Disc message comes up I press Slab and the page is displayed, press Find Clamp and Z moves to G53 Z-1 then I get message box asking for OK. I press Ok and X and Y move to minus 2.

Is that the part where its going wrong or do you see X and Y move at the same time as Z is going to G53-1?
Hood

Offline tmead

*
  •  62 62
    • View Profile
Re: G53 oddity
« Reply #14 on: January 05, 2011, 10:00:45 AM »
Yep, that all looks as expected, except you didn't get the spurious movement in X and Y during the Z movement to -1 (machine). The OK message was just part of my debugging to try to isolate what was going on.

It does the same on my code development laptop too, moving to around x = -300 y = -500 (machine coords)

If you press the Interrupt button as it is performing the movements it will stop at the end of a completed sensing pass. Subsequent presses of the Find Clamp button work exactly as you describe on the machine and development laptop, without the large movement right across the table and back, which is very strange.

I really don`t undersntand now !

Tim

Offline Hood

*
  •  25,849 25,849
  • Carnoustie, Scotland
    • View Profile
Re: G53 oddity
« Reply #15 on: January 05, 2011, 10:10:52 AM »
I will try again when I get home and see if I get the problem or if it works.

Do you possibly have any plugins or brains enabled which could affect things?
Hood

Offline tmead

*
  •  62 62
    • View Profile
Re: G53 oddity
« Reply #16 on: January 05, 2011, 10:30:12 AM »
nope, the system is a squeaky clean, fresh install, never been used for anything else.

I've looked for brains, tool offsets and have pulled out hair trying to track this down. Hadn't thought of plugins though, but definitley haven't run any on purpose. I'll check on that. Strange that two machines would have the same issue though....

Interestingly - if I run the button script from the code window (edit button script) and single step through, it works exactly as expected.

I'm just fortunate that this doesn't break anything. and is therefore a bit on an intellectual curiosity. There are other points in the cycle where an unexpected X / Y move would be costly.

Tim

Offline Hood

*
  •  25,849 25,849
  • Carnoustie, Scotland
    • View Profile
Re: G53 oddity
« Reply #17 on: January 05, 2011, 10:46:15 AM »
What exact version of Mach are you using?

Hood

Offline tmead

*
  •  62 62
    • View Profile
Re: G53 oddity
« Reply #18 on: January 05, 2011, 10:54:57 AM »
development laptop is 3.043.022, machine PC is 3.042.025

Both are showing the same issue. However, the $64 000 question is: what will happen when I install the screenset on the production machine at realease 2.42 ? Now anyone that can answer that really deserves a fresh carrot !

Tim

Offline Hood

*
  •  25,849 25,849
  • Carnoustie, Scotland
    • View Profile
Re: G53 oddity
« Reply #19 on: January 05, 2011, 11:01:32 AM »
Ok I was using 040 I think, will try with the versions you have when I get home.
Hood