Hello Guest it is April 27, 2024, 07:49:09 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 »
21
the easiest way is to set the button state to 0 "of the opposite button" when the selected toggle button is pressed by using scr.SetProperty calls.

examples are in the screenset code I posted. -> click on the MdiDro, On Modify Script.

22
Mach4 General Discussion / Re: Order of tabs in a window
« on: July 05, 2015, 10:11:52 AM »
Hi Pedio!  Yep...you can do it in the screen tree manager. You have to take the other tabs before jogging and drop them to the end (or below jogging).

23
Mach4 General Discussion / Re: Line following (tracing)
« on: July 05, 2015, 10:02:49 AM »
Couldn't you just trace the outline and export the DRO values in a comma separated value spreadsheet format? Then import them into CAD to replicate the outline? WTF it's 8 am on Sunday and I am thinking already, arrghhhh...(but I secretly love this sh!t)

24
Mach4 General Discussion / Re: 2nd window
« on: July 05, 2015, 09:55:20 AM »
gonna need to learn wxLua programming buddy!

I may just figure it out for ya!  ...but then you wouldn't learn anything...but I'd be helping someone...(this is the little devil vs angel conversation on my shoulders)

sh!t...I don't know if I'm hungover or still drunk at 8 am...

maybe I should put myself in MA ...Mach4 Anonymous  :o

25
just delete the LED and replace it with a toggle button. Toggle buttons have a lot of features that you may want.

26
Mach4 General Discussion / Re: Custom DRO script
« on: July 03, 2015, 03:41:48 PM »
maybe try [ if boardZero == 0 then scr.SetProperty ('name of your DRO', 'Value', '0.0000') end ] in the PLC?

wait a sec...I had trouble using a macro call to change a global variable value and then have the PLC scan and execute a function based on that global variable's value. For me, I couldn't get the PLC to recognize the macro's global variable value change. I know I might of just confused you but I think I know what you are talking about...I don't think the above example would work but you can try. Hmmm, this is a puzzle. Because when you call the macro and start movement you will have to wait until the movement is complete until resetting the DRO to zero. If not, lua will reset the DRO to zero before the movement is complete if you use the scr.SetProperty call in the macro at the end. A possible solution would be to time your movement (say it takes 90 seconds to do what you want).

so, your macro would start by declaring the function, execute gCode, wx.wxSleep(90), scr.SetProperty ('name of your DRO', 'Value', '0.0000') end. This would put lua into a sleep state until the movement is complete (based on timing) then reset your DRO. All within your macro and proceed to execute the next block. Try that technique.


27
Mach4 General Discussion / Re: tool height probing
« on: July 03, 2015, 03:24:40 PM »
local hsig = mc.mcSignalGetHandle(1,inst, ProbeSignal,mc.ISIG_INPUT11)

above line doesn't look right....if you want the handle to ISIG_PROBE is should be:

local hSig = mc.mcSignalGetHandle (inst, mc.ISIG_PROBE)

if mc.mcSignalGetState (hSig) == 1 then do something end


--on a side note, once I finish moving and reassemble my machine and equipment, I'll work on this for you....pending, I can get G31 working for me.


28
Here is the screenshot and the screen set with the embedded code. Add, modify, delete, PLAY :)
Still working through G53 incremental commands. Mach4 doesn't allow G00 G91 G53 move. "Cannot execute G53 incremental". I'll figure a way.
All moves are G00. If you want a G01 option, just let me know.

--josh

29
Mach4 General Discussion / Re: Mach4 Executing Gcode from LUA
« on: July 01, 2015, 02:36:29 PM »
try using:

if state == 1 then mc.mcScriptExecute (inst, "m12.mcs", 0) end

30
I would just use G91 for an increment move. I'll post a screen shot soon with the screen set. I kinda want to have only one DRO input with the option for:
a. Work Coordinates      Default movement from user's G54 offset
b. Machine Coordinates  G53
c. Absolute jog              G90
d. Increment jog           G91
e. Axis selection             X, Y, Z, A

or just 3 basic DRO inputs for X, Y, Z axes....idk


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