Messages

141

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 23, 2014, 09:28:14 AM »

Merry Christmas for Darwin users.

I have posted a stripped down wizard to help your setups. (did not use a cvs file in this version)

Also was informed by Art that he will be including it in future Darwin Installs, (thanks Art)  
That's my Christmas gift  

This goes in your Wizard folder and you just enter in the counts and velocities for all motor you setup.
Does not store anything just gives you some additional help and understanding of Darwin setups.

And a shout out to poppabear for turning me on to lua grids.

Update: wasn't festive enough, added some color  
Thanks scott

142

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 22, 2014, 10:24:47 PM »

Thanks guys;

had an issue today with setting up Darwin, after chatting with Art, he made me aware of the baseline to setup the Slider Freq in Hz.

I needed to set my freq just above the minimum Hz computed value.

So guess what I made? , a wizard to help in the future.

But it comes down to a simple formula (Counts * Velocity)/60 for each motor.

Update: (velocity is in units/min and kernel is in ints/second, so 60 makes velocity in seconds.)

Then just need to set the slider above the Highest Hz computed for all the axis
I made this one to handle up to 7 motors.

143

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 22, 2014, 09:42:10 AM »

Taking the same concept a little further, you can use the grid tools to calculate the data in the cells

Here is a Surface Speed to RPM calculator
Changing either of the two input values and then by clicking on any other cell, outputs the results.
Quick, Dirty and Functional

Note: The csv file has to be accessible, as it is reading from that file on load.

Update: Formatting and highlighting cells is shown in the added image.
Here's a snippet that formats the code (in two separate functions)
But it shows how to get cell data, compute it, set the new values and then create the alignment, colors, and font sizing

Code: [Select]

            SS_g_SurfaceSpeedsGrid:SetCellAlignment(0,2,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(1,2,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(0,0,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(1,0,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(3,0,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(4,0,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(6,0,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(6,1,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
        for i = 7, 17 do --Loop through the last 10 rows column 0
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(i,0,wx.wxALIGN_RIGHT,wx.wxALIGN_RIGHT)
            i=i+1
        end
            SS_g_SurfaceSpeedsGrid:SetCellBackgroundColour(0, 2, wx.wxColour(wx.wxGREEN))--This code changes the new cell to green
            SS_g_SurfaceSpeedsGrid:SetCellBackgroundColour(6, 0, wx.wxColour(wx.wxGREEN))--This code changes the new cell to green
            SS_g_SurfaceSpeedsGrid:SetCellBackgroundColour(6, 1, wx.wxColour(wx.wxGREEN))--This code changes the new cell to green

            local SFM=SS_g_SurfaceSpeedsGrid:GetCellValue(0, 2)
            local DIA=SS_g_SurfaceSpeedsGrid:GetCellValue(1, 2)
            local PI=3.141592654

            RPM = (SFM * 12)/(DIA * PI)
            SFM = (DIA * PI * RPM)/12
            RPM = string.format("%0.0f",tostring(RPM))
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(3,3,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellAlignment(4,3,wx.wxALIGN_CENTER, wx.wxALIGN_CENTER)
            SS_g_SurfaceSpeedsGrid:SetCellValue(3, 3, tostring(RPM))
            SS_g_SurfaceSpeedsGrid:SetCellValue(4, 3, tostring(SFM))
            SS_g_SurfaceSpeedsGrid:SetCellBackgroundColour(3, 3, wx.wxColour(230,230,230))--This code changes the new cell to gray
            SS_g_SurfaceSpeedsGrid:SetCellTextColour(3, 3, wx.wxColour(wx.wxRED))--This code changes the new cell to Red
            SS_g_SurfaceSpeedsGrid:SetCellFont(3, 3, wx.wxFont(14,0,0,0))--This code changes the font size
            SS_g_SurfaceSpeedsGrid:SetCellBackgroundColour(4, 3, wx.wxColour(wx.wxGREEN))--This code changes the new cell to green

144

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 21, 2014, 08:15:14 PM »

Added this message popup function at the start of calling the drill chart wizard.

Code: [Select]

function DisplayMessage()
 wx.wxMessageBox("Hole Dia. Tolerance \n\nStandard drilled hole tolerances for holes drilled with a drilling machine using suitable jigs & fixtures, the hole tolerances depends upon the diameter of the hole and increases as the hole diameter increases. \n\nThe following are standard tolerances for general machine work and apply in all cases except where greater or lesser accuracy is required by the design.\n\n .0135 THRU .125   +.004/ -.001 \n .1260 THRU .250   +.005/ -.001\n .2510 THRU .500   +.006/ -.001\n .5010 THRU .750   +.008/ -.001\n .7510 THRU 1.000  +.010/ -.001\n 1.001 THRU 2.000  +.012/ -.001\n", "Notice")
end


145

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 21, 2014, 07:45:55 PM »

As I thank you for the kind words, Both Scott(PoppaBear) and I have provided countless examples and code snippits.
Where is the homework you have done using what you have learned?

The Thread heading states, this is for 'Screen Set Ideas' I am trying to motivate, inspire and share IDEAS.

Scott has filled the Toolbox with all kinds of his examples.
He is running a service/business to provide you what you desire

I'm just showing you the kind of things I want Mach4 to do for me. 
That last project took me 20+ hours to figure out, but It took well more than a thousand hours to get to that point. This (Lua) is not an easy task to pick up. And I'm using probably less than 10% of Lua capabilities.

Don't give up.

146

Show"N"Tell ( Your Machines) / Re: The "Mach4" 3D Laser Build

« on: December 21, 2014, 08:45:29 AM »

Wheels on and all put back together, so far so good. 

Setting up and Testing alignment with laser spot beam.
To help in registration a short stroke air cylinder comes up with mach4 output then goes back down before Co2 beam is turned on.
Y axis is set to 150inch per minute X is limited to 700.
Z table axis takes a little to get used to, as Z travel up is actually in the negative direction

147

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 21, 2014, 05:17:08 AM »

There's a "Tap Drill" Chart  

Updated: Added a Drill Chart

148

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 20, 2014, 08:52:50 PM »

Made a Wizard to display an internal and external Thread Chart.
Reads in a excel csv file and outputs it in a Lua grid. (1685 rows, 13 columns)

Think of all the charts we use that can now be formatted and displayed at a button press.

Took me a while to figure this one out.  

149

General Mach Discussion / Re: Dual head offsets.

« on: December 12, 2014, 09:54:21 PM »

Still not sure what your trying to do as your using the same Z move to do two things? Wont one of the heads run into something while they are both going up and down at the same time?

but as far as your numbers I would think your mixing imperial fixture offsets with metric gcode movements
150" * 25.4 = 3810mm and 50" * 25.4 = 1270mm ( that's why your seeing the huge movements)
you might want to make sure you setup units are in metric or use the equivalent value (just some more math).

Code: [Select]

%
N1 G17 G21
N3 T1 M6
G90
G54
G0 Z6.
S4851 M3
X200. Y0. M8
N6 G81 Z-10.866 F1000. R2.5
N7 G80
M9
G55
X200. Y0.
G1 Z-10.866 F1000.
G0 Z6.
G54
X200 Y0
m30
%


150

Mach4 General Discussion / Re: Screen Set Ideas

« on: December 10, 2014, 08:31:26 PM »

Looks like there not much choice, not a big issue with basic machines and small files, but as the files get bigger and the tasks get more complex you can bet that some mcodes are going to be forgotten to be set. One of the key reason you always program with a safe block and create a block of code to start from after a tool change. Rarely done and most post processors need to be setup to create them.

(and quit voting for those politicians that are too lazy to read)