Messages

11

General Mach Discussion / new hardware same problem

« on: March 06, 2015, 06:50:00 PM »

Are you sure you don't have metric ball screws?  I pulled my hair out for days on my Italian made machine before I figured out the screws were 25mm per turn and not 25.4.  Just something to check.

12

Mach4 General Discussion / Re: Needing help with Wizards

« on: March 04, 2015, 04:38:23 PM »

the BoltCircle has a function in it to write data to the .ini  file. For the time being, I sidestepped that whole operation, but left the function in the code in case I want to go back and tinker with that.

I also decided to side-step it.  It's another can of worms and if I need it, I'll open it.   

As you may have already found out, you can pre-populate your wx.wxTextCtrl fields by setting something in the "value" box in wxFormBuilder.  I found this to be an acceptable compromise.

Wx *seems* to have its own library as the commands and syntax are different from straight Lua. It is a challenge to start with an existing wizard and reverse engineer the structure.

I got a book about a year ago called "Cross-Platform GUI Programming with wxWidgets" by Julian Smart (and others) from Amazon for about $10 used.  It's not a good book, but the info is in there.  It has helped me, but dang they made it difficult to use (It uses lengthy paragraphs instead of bullet points and bold letters. .)

Also, I have a text file with a list of wxLua functions that I thought I got on this forum but I'll be darned if I can find it again.  I will attach it to this message.

Good job on the wizard.

13

Mach4 General Discussion / Needing help with Wizards

« on: March 02, 2015, 12:26:13 PM »

The bolt hole wizard included in mach4 shows how to write to the ini file, if I remember correctly.

14

G-Code, CAD, and CAM discussions / Re: How do I pause for part removal? (newbie)

« on: February 26, 2015, 07:10:33 PM »

M1 is OPTIONAL stop.  It will only stop if the OPTIONAL box is ticked.  If it is not ticked then the program will not stop.  M0 is stop with no option to turn it off.  Don't ask me how many times I got screwed by that before I learned where to use which one.  M1 is good if you have a program that you might want it to stop in places during code this run, but maybe the next run you don't want it to stop, so you untick the option.  If you want it to stop for sure, every time you run the program, use M0.

Both of them will continue to run when hit Cycle Start.

15

Mach4 Toolbox / Spindle WarmUp Wizard

« on: February 17, 2015, 04:13:36 PM »

Here is a wizard to make the code to warm up a spindle.  Place this mcs file in the Wizards folder for M4 and use it from the Wizards pull-down menu.

16

Mach4 General Discussion / Mach4 Build 1900 released

« on: July 18, 2014, 07:00:22 PM »

Hear ye, hear ye!  http://www.machsupport.com/wp-content/uploads/2014/04/Mach4Hobby%20Installer-1900.exe

17

Mach4 General Discussion / M4 Build 1872 is out

« on: June 30, 2014, 03:39:04 PM »

New release! 

I dont know if it overwrites the macros and whatnot that you've worked so hard on before now, so back it up first. 

18

General Mach Discussion / Re: Need Help

« on: June 08, 2014, 12:30:19 PM »

Show us a bit of the gcode that is giving you problems.  Is it a million little segments that make up the arc? That's been trouble for me before.

19

Mach4 Toolbox / Re: IsStill example (M4 version of IsMoving)

« on: June 07, 2014, 09:12:35 PM »

Bug has been reported here -->  http://www.machsupport.com/forum/index.php/topic,27119.msg193580.html#msg193580

20

Mach4 General Discussion / IsStill is still wonky

« on: June 07, 2014, 09:09:30 PM »

There was talk of IsStill being fixed for the "next release" (1817) here --> http://www.machsupport.com/forum/index.php/topic,27254.msg192453.html#msg192453

But IsStill is still having issues. 

This works

Code: [Select]

inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst, "g91 g1 x1") --execute gcode
while (mc.mcCntlIsStill(inst)==1) do  --loops through this while an axis is moving
    mc.mcCntlSetLastError(inst, "axis in motion") --do this while axis is moving
end  --ends the loop
mc.mcCntlSetLastError(inst, "axis is stopped")  --continues here after axis is done moving
mc.mcCntlGcodeExecute(inst, "g90") --execute gcode

This does not.  Only difference is the last line.

Code: [Select]

inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst, "g91 g1 x1") --execute gcode
while (mc.mcCntlIsStill(inst)==1) do  --loops through this while an axis is moving
    mc.mcCntlSetLastError(inst, "axis in motion") --do this while axis is moving
end  --ends the loop
mc.mcCntlSetLastError(inst, "axis is stopped")  --continues here after axis is done moving
mc.mcCntlGcodeExecute(inst, "g91 g1 y1") --execute gcode

It doesn't crash, but it becomes unresponsive as if it was moving the axis (although I dont think it gave the error message during the function), but nothings happening on the DROs.