Hello Guest it is April 27, 2024, 05:18:12 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Screwie Louie

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 »
41
Mach4 General Discussion / Re: tool height probing
« on: June 30, 2015, 04:17:22 AM »
Could be Dan. G31 commands and execution may just be mapped to the Probe input....vs. Input XX. Good looking out. I bet you're right! By the way, how old is my New Zealand friend? I'm 37...16 yrs in military service (federal acquisitions and contracting). But, I think I know what I actually want to do now after retirement...

42
Mach4 General Discussion / Re: Activate input
« on: June 30, 2015, 04:03:27 AM »
could be mach machine state....changing the state if possible? This may sound like a simple solution but everybody and every machine is different. This is a neat puzzle....

43
hold on a sec...I need to work on the increment DRO (I am using both the absolute and increment  coordinates G90/G91 at the same time...let me work this through)

I think I double posted...can a moderator delete the repeat post please?

Dude, this is soooo gonna work!

What's up Pedio? I sware you meant Pedro but Pedio? I think of PedioBear....lol! just kidding. Don't kick my ass...

44
This is in response to a request by Pedio. He would like to input a number value into a DRO and have the axis jog to that position instead of going to the MDI input page, writing the block and pressing Cycle Start. I believe his intent is to maximize time efficiency by jogging to a known position from his home page. ie "Enter value, press enter" => axis jogs to desired position. This example is simple without error checking or safety checking (ie. rc values, is axis homed, or is Z axis clear before movement, etc) To implement direct input into a DRO as a text box I will do my best to describe the instructions below. By the way, this was a great idea! Thanx Pedio (If you don't mind, I would like to add this feature to my Blackout Screenset --which is open code for everyone to use, edit, play, add their own features, repost, etc....) You guys are gonna be like "That's it?!?!?" Yep, gotta love m4! I demonstrate a mc.mcCntlMdiExecute function to jog to an absolute coordinate position (G90) and then using mc.mcJogIncStart function call instead of mc.mcCntlMdiExecute G91 command. Hope this helps!

Absolute Position:[/color]
1. Operator -> Edit Screen
2. Add DRO --to wherever you would like for this MDI input to be
3. DRO properties are: DRO Code = Blank, Editor = Keypad
4. On Modify Script =
           local inst = mc.mcGetInstance()
           local gCode = ""
           local Xmove = scr.GetProperty('droXMdiAbs', 'Value')

           Xmove = tonumber(Xmove)
           if Xmove == nil then Xmove = '0' end
           gCode = gCode ..string.format("G0 G90 X%.3f\n", Xmove)

           mc.mcCntlMdiExecute (inst, gCode)

Incremental Movement:[/color][/color]
1. Operator -> Edit Screen
2. Add DRO --to wherever you would like for this MDI input to be
3. DRO properties are: DRO Code = Blank, Editor = Keypad
4. On Modify Script =
           local inst = mc.mcGetInstance()
           local Xmove = scr.GetProperty('droXMdiInc', 'Value')

           Xmove = tonumber(Xmove)
           if Xmove == nil then Xmove = 0 end
           mc.mcJogIncStart (inst, 0, Xmove)

[/color]
That's it folks! I'll post some screen shots below in the next post to help you guys visualize the concept. It's pretty cool. Pedio had a great time-saving idea.

--josh
  

45
Mach4 General Discussion / Re: tool height probing
« on: June 30, 2015, 02:49:06 AM »
Do you have all your registers set up? ie. TS_XPOS defined in the Register plug-in?

47
Cool, thanx Dan!

48
I'll take her on vacation to New Zealand and leave her with you. Then I can actually get some work done then  ;D

49
Mach4 General Discussion / Re: Activate input
« on: June 30, 2015, 01:07:30 AM »
Got this to work in the sim, whereas the DRO's will not move and the button will let you toggle the input signal without actually moving the axis.

Button Down Script:
     local inst = mc.mcGetInstance()
     mc.mcSignalSetState (mc.mcSignalGetHandle (inst, mc.ISIG_JOGXN), 1)
     mc.mcJogVelocityStop (inst, 0)

Button Up Script:
     local inst = mc.mcGetInstance()
     mc.mcSignalSetState (mc.mcSignalGetHandle (inst, mc.ISIG_JOGXN), 0)

50
or write a macro using mc.mcAxisSetPos function call...

"Set the position of the axis by changing the current Fixture offset."

Try both functions and see which one is best for ya.    mc.mcAxisSetPos or mc.mcAxisSetMachinePos

the macro would be called after each iteration, resetting your axis back to 0 in your work coordinates.

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 »