Messages

121

Mach4 General Discussion / Re: Screwie Louie mcLua scripting for screwie lua learning

« on: June 02, 2015, 12:53:06 AM »

Heck yah! Thanx Daniel.

--josh

122

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: June 02, 2015, 12:47:51 AM »

Has anybody noticed when entering and exiting Edit Screens their "Main tabs" panel keeps dropping from the top by a value of 6 then 26 then 36 or something whereas you have to constantly resize and format your panels? Just wonderin...

123

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: June 02, 2015, 12:45:10 AM »

Way to go Mr. Stallings! PMDX to the rescue! Now that's what I call customer service 

124

Mach4 General Discussion / Re: need a little bit of help

« on: June 02, 2015, 12:43:09 AM »

I was thinkin....you think it's wise to dive into the mc.mcMotion functions? Whats up with the "Cycle planner" anywho? I gather it is communication with the motion controller and the core whereas, the motion controller reports (by motor counts) to the core the position of the mill and then the core updates the data on Mach GUI. I wonder if we can control this or is this strictly OEM afforded functions...hmm, idk. And another thing, the screw mapping functions...is that a way to do our axis calibration? I think so, we just have to code it. It seems easy. I just want to know if it is for axis calibration or not. Ok, I'm talking too much. Later Daniel!

--josh

125

Mach4 General Discussion / Re: Lua Gcode calls and screenLoadScript sigLib communication help...

« on: June 02, 2015, 12:30:13 AM »

Thanx for answering! I appreciate it...load screen, plc...but what about the signal script? Is the signal script only created to handle external IO events by passing them to/from the load screen? I put a signal reference table into the plc and the signal script didn't like that at all....it started crying ) So I put the signal reference table back into the load screen and the signal script did not give a nil error. Just curious, that's all. I think the plc's job is to monitor internal signals and functions calls (am I close?). Btw, I have been through the toolbox like 1000 times and it is really starting to click. Thanx for sharing and educating all of us!

--josh

126

Mach4 General Discussion / Re: Lua Sizer Confusion tying Sizer to Panel

« on: June 02, 2015, 12:22:26 AM »

I just took a look at wx.FormBuilder and wizards and lua panels and bears oh my!; yesterday. Yep. I'm down to about 3 hours of sleep per night now, and my girlfriend gets pissed at me when I jump outta bed at 8am just to program and play with the mill. Haha! So the whole putting DRO overlays on top of the tool path generator idea didn't work out so great for me...which led me to dig deeper. From a snapshot, most of the code is about autosizing and basic functions. After a bit it should become all familiar like anything and best of all the windows can be templated. Poppabear posted in the tookit a template for frames and panels that eliminate the 3d boarder and establish a template like I am talking about. But hey, take my opinion with a grain of salt. I just glanced at it. Speaking of the toolbox...man, there is some great stuff going on in there! After looking at the dates, I feel like I'm late for the party )

--josh

127

Mach4 General Discussion / Re: need a little bit of help

« on: June 02, 2015, 12:08:20 AM »

Nice! I'm impressed...I couldn't get a while or a repeat loop (even with a break) to work for me, just kept freezing the GUI as button scripts are 'ran as events'. I just figured I'd start using wx.wxMessageBox to break up the chunks. I finally got all kinds of movement in on a button script now by breaking it up with the message box (all kinds of mc.mcCntlMdiExecute and mc.mcJogVelocityStart functions going on without racing) for multiple phases in the auto tool button without G31. I was using the message box to prompt the user and when a movement phase was complete, the user just hit ok. This would signal Lua to execute the next chunk in the script. If you don't mind, I'd like to try the while loop with wx.wxMilliSleep combo. Nothing like automation! ...man, I love this stuff! Below is a what I mean, this is just a snippet. I agree with BR549, smart dude. The machine works for us (Period!)

--josh

Code: [Select]

gCode = "G0 G90 G54 G17 G40 G49 G80\n"
gCode = gCode .."G53 Z0.0\n"
gCode = gCode .."G53 X14.0 Y0.0\n"
gCode = gCode .."G53 X12.0 Y1.0\n"
mc.mcCntlMdiExecute(inst, gCode)
mc.mcSignalSetState (hSigOZero, 1)
wx.wxMessageBox ("Next:  Probe table.")

mc.mcJogSetRate (inst, 2, 40)
mc.mcJogVelocityStart (inst, 2, -1)
mc.mcSignalSetState (hSigOZero, 1)
if inputZero ==1 then mc.mcJogVelocityStop (inst, 2)end
wx.wxMessageBox ("Next:  Goto Tool Setter Position.")

128

Mach4 Toolbox / Re: wxLua Debugging Module for Screen designers and Macro/Wizard makers

« on: June 01, 2015, 10:01:54 AM »

Oh man, this sounds cool. I gotta try this out later! Thanx!

129

Mach4 General Discussion / Re: Jogging/Pendant Interface-What is the best way? Ramblings

« on: May 30, 2015, 08:20:07 PM »

Yah, I do enjoy how Mach 4 is layed out and the abilities the NFS gives up to make our own screen sets. Was playing with the screen tree manager today and a blank screen set. Full screen tollbooth display with Lua panel overlays for data information. Good point about the bitmap button! While playing around I found myself thanking Mr. Barker for including those pre defined actions in the drop down menu 99% of the time. It's just that 1%...haha. The lua panel, is open source code to change GUI things. But nevertheless I'm lovin Mach 4 and Lua. Thanx!

130

Mach4 General Discussion / Re: Jogging/Pendant Interface-What is the best way? Ramblings

« on: May 30, 2015, 02:40:10 PM »

Yes! For example...how would I write code for an LED where there is no way to put my code in to change the state of the LED. The only options are the ones provided from the drop down menu. Don't get wrong. I think it is a great feature provided by NFS. I just want an LED to change state based on my requirement in Mach 4.

Nevermind. I answered my own question I think.

1. I would code for a condition and set state to true or false and return the state to a temp register.
2. Use the above script to emulate an IO device and us mc.IOfunctions to map to it and point to the temp register as it's own register
3. Then assign an output to the emulated IO device.

that could be a pain just to get an LED to blink based on my condition