Messages

241

Mach4 General Discussion / Re: My File is running real slow

« on: April 12, 2018, 05:37:53 PM »

Well, I hesitate putting this up because it is a simple fix but comes with other issues. If you want the rotational axis to display and work in RPM instead of DPM just change your steps per in motor tuning to Current Steps Per X 360. This will break other things though like toolpath preview and most CAM programs wont generate code for it.

I maintain the proper fix is to use G93. And change your way of thinking of course. The above may be a fix for you but anyone reading this needs to make sure they understand that the real issue is your way of thinking. Just because you can do something doesn't mean you should. Mach like all other software is code. The code can be written to adapt to certain things but to an incorrect way of thinking is not a goal of any programmer I know. This is why standards and following them is so important.

No one should hate having to change their way of thinking to be on par with standards. No shame in it and you will be smarter for changing. Be happy that you are smarter than the machines today. That will not be the case much longer IMO. Today you can adapt your way of thinking to overcome obstacles keeping you from the desired end result. Most machines can't do that now. But when they can (and they will)....... we become useless eaters. So, take pride in your advantage today. It may not exist tomorrow.

242

Mach4 General Discussion / Re: My File is running real slow

« on: April 12, 2018, 11:14:04 AM »

Chad, the problem is, you only have one feed rate at the time.
So say you have a line of Gcode that all axis are doing a synchronized feed move on (G1 F5 X5.000 Y5.000 Z5.000 A360.000).  All axis are going to end at the location requested at the same time.

Without the A axis this move would take 1 minute. But because of the A axis this line will take 360 degrees /5 degrees per minute = 72 minutes to complete.

However, using the same axes and values (G1 F5 X5.000 Y5.000 Z5.000 A360.000) but replacing the G1 with G93 and the F5 with F1 (G93 F1 X5.000 Y5.000 Z5.000 A360.000) it would finish in one minute............ assuming motor tuning would allow it to finish in the time of course. Now if any of the axis can't move the requested distance in the requested time (due to motor tuning) the time it would take will be extended to the fastest it can possibly happen in.

Hope that makes sense.

243

Mach4 General Discussion / Re: My File is running real slow

« on: April 11, 2018, 07:51:41 PM »

The proper solution is to use G93 – Inverse Time Feed. Study up on it. You can find information about it in the Mill Gcode programming.pdf file in your Mach4/Docs folder.

244

Mach4 General Discussion / Re: Lua file operations

« on: April 08, 2018, 12:46:03 AM »

I would create a single string then write that single string to the file once. You're opening once and writing twice.

A perfectly working example can be found here.
http://www.machsupport.com/forum/index.php/topic,35896.msg245756.html#msg245756

245

Mach4 General Discussion / Re: wx.widgets

« on: March 29, 2018, 11:39:37 AM »

This is a cheat sheet for message boxes.

Code: [Select]

--Get input from user
local MyPass = wx.wxGetPasswordFromUser("Message", "Caption", "Default Value")
local MyText = wx.wxGetTextFromUser("Message", "Caption", "Default Value")
local MyNum = wx.wxGetNumberFromUser("Message", "Prompt", "Caption", 50, 0, 100) --Default, min, max
local MyChoice = wx.wxGetSingleChoice ("message", "caption", ({"Choice1", "Choice2", "Choice3"})) --, wxWindow *parent=NULL, int x=wxDefaultCoord, int y=wxDefaultCoord, bool centre=true, int width=wxCHOICE_WIDTH, int height=wxCHOICE_HEIGHT, int initialSelection=0)
local dir = wx.wxDirSelector ("Choose a Directory", "C:\\")--Caption, default directory --long style=0, const wxPoint &pos=wxDefaultPosition, wxWindow *parent=NULL)

--wxMessageBox Types
--2 = Yes, No
--4 = Ok
--16 = Ok, Cancel
--18 = Yes, No, Cancel

--wxMessageBox Return Values
--Yes = 2
--OK = 4
--No = 8
--Cancel = 16

--Have user click a button
local Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",2) --Yes,No
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns
Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",2) --Yes,No
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns
Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",4) --Ok
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns
Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",16) --Ok, Cancel
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns
Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",16) --Ok, Cancel
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns
Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",18) --Yes, No, Cancel
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns
Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",18) --Yes, No, Cancel
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns
Iclicked = wx.wxMessageBox("This is my Message", "This is my Caption",18) --Yes, No, Cancel
wx.wxMessageBox(tostring(Iclicked)) --Show in another message box what the button click in the previous message box returns

--Another way of using a messagebox Type defined with a wx constant
local yesno = wx.wxMessageBox("This is my Message", "This is my Caption", wx.wxYES_NO)
if (yesno == wx.wxYES) then

elseif (yesno == wx.wxNO) then

end

--http://docs.wxwidgets.org/3.0.1/group__group__funcmacro__dialog.html#ga193c64ed4802e379799cdb42de252647

246

Mach4 General Discussion / Re: wx.widgets

« on: March 29, 2018, 11:30:45 AM »

I use this http://docs.wxwidgets.org/3.0.1/group__group__funcmacro__dialog.html#ga3267f33060d2ae403862427acb758bab

For your wxGetTextFromUser in particular.....
http://docs.wxwidgets.org/3.0.1/group__group__funcmacro__dialog.html#ga5a6a376f69f87e48e618f6f79e2c4a1b

247

Mach4 General Discussion / Re: Zero Brane not working properly.

« on: March 27, 2018, 04:28:49 PM »

I'm not sure either. All I do is open Mach, go to operator, Edit/Debug scripts and browse to the macro I want to step through and it all works good. You might want to delete any .mcc or .bak files in that macros directory before launching Mach just for safe measure.

248

Mach4 General Discussion / Re: Zero Brane not working properly.

« on: March 27, 2018, 03:50:19 PM »

That's probably not a bad idea either way.

249

Mach4 General Discussion / Re: A Aixs Brake

« on: March 27, 2018, 03:38:52 PM »

Would the output for the brake not be a  function of the drive? All I have ever seen required voltage to release the brake. 0 volts allows the brake to lock. Not sure I have ever seen one work as your describing. When the servo is powered up it shouldn't allow the axis to move. Usually the brake is only applied at power out, drive fault, etc. but I think I have seen the option for setting it up like you want in some drive configuration software.

250

Mach4 General Discussion / Re: Zero Brane not working properly.

« on: March 27, 2018, 03:24:58 PM »

Not what mine looks like............

Program starting as '"C:\Mach4Industrial\ZeroBraneStudio\bin\lua52.exe" -e "io.stdout:setvbuf('no')" "C:\Users\me\AppData\Local\Temp\.9764.tmp"'.
Program 'lua52.exe' started in 'C:\Mach4Industrial\Profiles\Test\Macros' (pid: 2132).
Debugging session started in 'C:\Mach4Industrial\Profiles\Test\Macros\'.
Debugging session completed (traced 0 instructions).
Program completed in 1.30 seconds (pid: 2132).