Welcome, Guest. Please login or register.
Did you miss your activation email?
May 02, 2016, 02:25:18 PM

Login with username, password and session length
Search:     Advanced search
* Home Help Search Calendar Links Login Register
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 »
21  Mach Discussion / Mach4 General Discussion / Re: G31.1, G31.2, G31.3 working? on: May 30, 2015, 11:49:52 AM
I've been playing with the probing code posted by Brian on the Yahoo group. It works fine and you have control of how the data in the output file is formatted - comma separated, having XYZ prefix before the coordinates, omitting particular axis, etc. For your convenience, here is the orginal code Brian posted:

function M401()
inst = mc.mcGetInstance();
    -- create the wxFrame window
    mainframe = wx.wxFrame( wx.NULL,          -- no parent
                        wx.wxID_ANY,          -- whatever for wxWindow ID
                        "Mach4 Bolt Hole Wizard", -- frame caption
                        wx.wxDefaultPosition, -- place the frame in default position
                        wx.wxDefaultSize,     -- default frame size
                        wx.wxDEFAULT_FRAME_STYLE ) -- use default frame styles

    -- create a panel in the frame
    panel = wx.wxPanel(mainframe, wx.wxID_ANY)--We are not going to show it but we need to have this to use the File dialog

local file = wx.wxFileDialog(panel, "Select Probe File", "", "", "Text files (*.txt)|*.txt|Tap files (*.tap)|*.tap",
                             wx.wxFD_SAVE,wx.wxDefaultPosition,wx.wxDefaultSize, "File Dialog" );
        if(file:ShowModal() == wx.wxID_OK)then
            local path = file:GetPath() 
            wx.wxMessageBox(tostring(path))
            mc.mcCntlProbeFileOpen(inst, path, "X%.3AXIS_X Y%.3AXIS_Y Z%.3AXIS_Z \r\n", true);
        end

end

if (mc.mcInEditor() == 1) then
    M401()
end


You have to put it in a file and name it M401.mcs

To close the file, in a file named M400.mcs put this code:

function M400()
inst = mc.mcGetInstance();
mc.mcCntlProbeFileClose( inst );
end

if (mc.mcInEditor() == 1) then
    M400()
end




Dan
22  Mach Discussion / Mach4 General Discussion / Re: Mach4 OSX Version in the future... on: May 30, 2015, 11:38:08 AM
Hi Gerry,

I started playing with MAch4 a couple of weeks ago. Looks a fairly complete software to me, apart of some little annoying 'bugs'. Not put it to extensive testing of all features, but from what I've seen I got the above impression. Could you tell me what makes you say it is not complete and it will take another year? I know lathe is not finished, but is being worked on and 'should' be finished in a week...

Dan
23  Mach Discussion / Mach4 General Discussion / Re: Mach4 Executing Gcode from LUA on: May 29, 2015, 01:23:16 AM
Thanks for explaining this Steve. So I get it that if I had several lines of Gcode I wanted to execute I'd have to concatenate them as a string like in the examples? 

Dan
24  Mach Discussion / Mach4 General Discussion / Re: Mach 4 Bug Reports on: May 26, 2015, 07:20:53 AM
OK. The workaround works.

Dan
25  Mach Discussion / Mach4 General Discussion / Re: Mach 4 Bug Reports on: May 26, 2015, 03:10:49 AM
Already have. Makes no difference.

Dan
26  Mach Discussion / Mach4 General Discussion / Re: Mach 4 Bug Reports on: May 26, 2015, 02:40:19 AM
I have this code in a button.

Dan
27  Mach Discussion / Mach4 General Discussion / Re: Mach 4 Bug Reports on: May 26, 2015, 02:18:02 AM
Not really explains the issue I mentioned...

Dan
28  Mach Discussion / Mach4 General Discussion / Re: Mach 4 Bug Reports on: May 26, 2015, 12:40:03 AM
Looks like a bug:

Trying to execute Gcode from LUA. This script works fine:

local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst, "G0 X10 Y10\n")


However, with the below function, the numbers in the DROs do not continuously update, but only when the final destination is reached.

local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecuteWait(inst, "G0 X10 Y10\n")


When trying to execute two line of Gcode, like below, the DROs again don't update continously, but only when the final point is reached.

local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst, "G0 X10 Y10\n")
mc.mcCntlGcodeExecute(inst, "G0 X5 Y5\n")


Dan
29  Mach Discussion / Mach4 General Discussion / Re: Mach4 Executing Gcode from LUA on: May 25, 2015, 08:06:36 AM
Is the bug report thread being monitored by Steve?

Dan
30  Mach Discussion / Mach4 General Discussion / Mach4 Executing Gcode from LUA on: May 25, 2015, 05:37:04 AM
Trying to execute Gcode from LUA. This script works fine:

local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst, "G0 X10 Y10\n")


However, with the below function, the numbers in the DROs do not continuously update, but only when the final destination is reached.

local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecuteWait(inst, "G0 X10 Y10\n")


When trying to execute two line of Gcode, like below, the DROs again don't update continously, but only when the final point is reached.

local inst = mc.mcGetInstance()
mc.mcCntlGcodeExecute(inst, "G0 X10 Y10\n")
mc.mcCntlGcodeExecute(inst, "G0 X5 Y5\n")


What is the correct way to programm in order for the DROs to continuously update?

Dan



Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.20 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!