Machsupport Forum
Mach Discussion => Mach4 General Discussion => Topic started by: poppabear on May 02, 2014, 09:29:59 AM
-
User Configurable 1-4 tool path views in a tool path group example.
Jason, and I had wanted to do this a while back in flash, but m3 would not allow it.
But it is Do-able in M4, this screen set has just the "Program Run" page (tab), tool path group done, but you could mod it for the other Tabs/Toolpath views.
I added a "User Cfigs" tab in the "notebook" area of the lower screen, when you press the
"cfg toolpath views" button, each press of the button, cycles through they screen view layout types:
Single view, Horizontal view, vertical view, 3 view, 4 view.
the script uses heavy table work.
The attached screen set is called: Mach4UserMod1v1.set
Let me know what you think!!
Scott
-
This is real nice Scott. Next thing would be allowing setting "Jog Follow" independently for each view.... ;)
Dan
-
Dan,
Open that screen and look at the code behind that "Cfg Toolpath View" button......
After getting an eyeful of it, by all means please add the code to do that jog follow............ hehhehee
then re-post the updated/improved screen!!!
Scott
-
LOL...I am not a programmer, Scott. Could barely do VB, let alone this whole new to me LUA thing...
Not asking you to do this. Appreciate all your input anyway!
Dan
-
I do like it, cool work Scott
-
Took 25 minutes to add, ya got to love it?
thanks again Scott
-
........ by all means please add the code to do that jog follow............ hehhehee
then re-post the updated/improved screen!!!
;D
Man ... you guys are gifted. More valuable now than ever.
I for one really appreciate you generosity and consideration.
Thanks,
Russ
:)
-
Way to go Craig, you edited that in while I was posting.
THANKS !
Russ
-
ok Craig, now you have to post the screen with the jog follow......
I never even thought about adding something like that, since I never even use it...
Here is a fun one for you or some other enterprising guy.... Add the "Multi-tool path" button and tool path screens to the OTHER 4 pages.... :) :) :)
not complex just time consuming detail work,
Scott
-
LOL...I am not a programmer, Scott. Could barely do VB, let alone this whole new to me LUA thing...
me neither...... I just learned it by trying it, failing, trying again....etc. till it started working.....
I am LOV'N wxLua sssssooooooooo much bettter than VB, and really, the way the core is done, there are VERY few things,
you even NEED a plugin for (other than hardware interfaceing), and then even then, you can access your hardware/plugin via mc.*********x calls, it is just TOO FREAKING COOL...
Scott
-
Not sure I understand the Jog Following and just what you are referring too. Sometime I'm a little dense. :-[
But I did plan on adding your scripting features it to at least the Tool Path page.
I do like the way your script formats the four panes, I just needed to add them & name them 11 thru 14
pretty damn straight forward. Once the script runs it takes care of the formatting.
Again Great Job Scott
-
Hey Craig,
I had already added TP 11-14 in the code, and those TP object, did they NOT show up in the screen I put up?
I downloaded my screen from this site, and I do see those tool path objects in there....
so, can I ask what you mean....
Thank you for the chops as well.
I think we should make this screen set a "Community" screen, where people can add features, wizards, pages what ever then after what they add is debugged. They could repost it back up, and tell what they added, and how to use it if required.
I.E. Probing routines, (to include tool touch offs), etc.
Scott
-
Id taken your script and put it in the screen.set I am developing for mach4
So I had to add the 4 screens in my set
Kind of why I posted a screen capture to show the changes to the first Tab I had made.
I hoped that that with some of the examples I have posted others would feel more at ease with the screen designer and attempt some of thier own features. Having a Like Minded community will make the launch faster and more fun for all to get up to speed. While also creating a universal screen.set, functional for all.
Still trying to get my head wrapped around the Probing and how to use mc.mcMotionCyclePlannerEx()
does not show up on the LuaCalls list and debugging is giving me Errors.
message:
Got a socket error trying to read. Address '192.168.254.84'. Port 25541.
I would think probing scripts that get called on button presses to the mc.mcCntrlMdiExecute() or mc.mcCntlLoadGcodeFile()
-
GUYS could you do a BUTTON that emulates a probe trip. I would like to test probing (;-)
I have tried but cannot do the LUA thing. It is about a mile above my abilities, been trying about a year now between SheetCam and Mach4 . NOTTA going to happen.
(;-) TP
-
Worked on the Tool Path tab this morning
And note, the two pages are independent of each other so you can have different display groups and viewing orientations on each page.
that is a sweet job Scott
-
GUYS could you do a BUTTON that emulates a probe trip. I would like to test probing (;-)
I have tried but cannot do the LUA thing. It is about a mile above my abilities, been trying about a year now between SheetCam and Mach4 . NOTTA going to happen.
(;-) TP
Well... this is not possible. In Mach 4, the motion controller handles the probe input. There is a signal that is "lit up" (digitize I think) but it is more for diagnostics than anything. The core does not actually do anything with the signal during a probe move. However, it will prevent you from starting a probe move if it is high. But the core will not stop the motion upon a state transition. That is the motion controller's responsibility. The Sim plugin doesn't "simulate" probing at this time.
Steve
-
Thanks Steve, SO would it be possible to release the LPT driver for further testing ?
(;-) TP
-
ok, put the para port stuff in its own thread, lets keep this thread about screen stuff, and doing stuff in screens
scott