Hello Guest it is October 20, 2019, 08:14:07 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - smurph

481
Mach4 General Discussion / Re: How to programing C# with Mach4
« on: March 02, 2016, 03:57:59 PM »

482
On the Matsuura, it is an air cylinder that engages a roller bearing into a V slot on the spindle.  The air cylinder is pressurized and the spindle is run at slow speed/low torque causing the roller bearing on the air cylinder shaft to roll on a collar.  When the V slot comes around, the roller drops into the V slot.  A limit switch detects this and shuts the spindle off.  The air cylinder is now holding the spindle in the correct orientation.  So all I did was use what the machine already had.  Another plus to converting a machine like a Matsuura, Hurco, or the like is all of this stuff is there!  Full coolant system too!  No fabrication required.  And you don't spend a year on the conversion project.  Meaning chips start flying quicker.  

I used the Galil to run the tool changer.  But Mach could have been used.  In fact, I had Mach controlling it all at one point.  But I moved it to the Galil to reduce the tool change time a bit.  The Galil can have programs running on it at the same time it controls the axes.  But any PLC could be used to work the ATC as well.  All my M6 script does is tell the Galil what tool is desired and waits for the Galil to signal when it is done.

But the BEST part about using an industrial machine is the rigidity.  You can use a 1" hog mill and remove some serious material.

The cons are it has a 10HP spindle that requires a rather large rotary phase converter if three phase is not available.  However, only the motors are 3 phase.  The drives and servos are powered from single phase.  One could replace the spindle VFD and use VFDs to run the TC, oil lube, and coolant motors and run it all on single phase.  But I had a 15HP rotary converter already.

Steve

483
Mach4 General Discussion / Re: How to programing C# with Mach4
« on: March 01, 2016, 11:16:23 PM »
In order to have access to the SDK, you need to become a registered developer.  Otherwise, the API is in the documentation that is distributed with Mach 4.  You will have to make your own C# API wrappers. 

484
Mach4 General Discussion / Re: Mach 4 Lua Scripting modbus
« on: March 01, 2016, 08:14:14 PM »
LOL!!!  Yeah...  I forget a lot of stuff too.  You pretty much have to in order to start trying to forget new stuff.  :)

Steve

485
Matsuura MC500 with 16 pod tool changer.  Mach3/Galil driving the stock Yaskawa drives and servos.  Running 500 IMP.  It does HSM perfectly fine.  The main limitation is the spindle speed which is 5K.  Using Inventor HSM for the tool paths.  It is not a large machine, but it is certainly an industrial machine.  It never crashes.  It always does what I want it to.  Never needed Macro B and it never had it.  (Original control was YASNAC).  Mach 3 is FAR superior to the original control.  Tool changes are twice as fast!  Rapids are up from 275 IPM to 500 IPM.  

I took my time integrating Mach 3.  All of the original machine safety lockout are used and functional.  All of the macros are thoroughly debugged and working flawlessly.  This machine could be put to production use and never blink an eye.  

Converting one of these type of industrial mills can be a really good option for the hobbyist.  I have about as much in this machine as it would take to retrofit a Bridgeport.  And you get nice things like limit switches on both sides of the table (no one switch wonders here!), real home switches, and ATC.  

I think you get out of Mach 3 or Mach 4 what you put into it.

Steve

486
General Mach Discussion / Re: Artsoft sold??
« on: March 01, 2016, 03:02:37 PM »
It is HILARIOUS!!!  Thanks Art, err...  Susehr.  The levity is appreciated.  :)

Oh wait...  I'm supposed to be unemployed too!  Probably fired by Trump.  Anyway...  I can't remember. 

Steve

487
Update to the latest.  You are running an extremely OLD version.  The Modules directory will be off of the base installation directory.  C:\Mach4Hobby\Modules.

You may also have to update any motion plugins as well.

Steve

488
If you have installed Mach 4, the necessary sockets modules are pre-built and are in the Mach 4 Modules directory.  The Mach 4 LUA environment is completely separate from any other installed environment.  No building or installing is necessary.  However, scripts that used the modules in the Mach4 Modules directory do need to have their package.path and package.cpath set as in the example above.

Steve

489
The LUA sockets module is in the Modules directory. 

Setting the package path and cpath is important.  This is an email example, but it is proof of concept for using the LUA sockets module.

Code: [Select]
-- Replace the from and to addresses, as well as the mail server IP address,
-- with something useful.

package.path = package.path .. ";./Modules/?.lua;"
package.cpath = package.cpath .. ";./Modules/?.dll;"

function email()

    -- load the smtp support
    local smtp = require("/socket.smtp")

    -- Connects to server "localhost" and sends a message to users
    -- "fulano@example.com",  "beltrano@example.com",
    -- and "sicrano@example.com".
    -- Note that "fulano" is the primary recipient, "beltrano" receives a
    -- carbon copy and neither of them knows that "sicrano" received a blind
    -- carbon copy of the message.
    from = "<mailfrom@sendingdomain.com>"

    rcpt = {
        "<someuser@somedomain.com>"
    }

    mesgt = {
        headers = {
            to = "Some User <someuser@somedomain.com>",
            subject = "email test"
        },
        body = "This is a message from M300."
    }

    r, e = smtp.send{
        from = from,
        rcpt = rcpt,
        source = smtp.message(mesgt),
        server = "192.168.1.25" -- mail server to use...  defaults to port 25.
    }
    r = r
end   

email()

490
Mach4 General Discussion / Re: Mach 4 Lua Scripting modbus
« on: February 24, 2016, 12:29:58 AM »
Just tell the DRO to use the modbus exported register via the "Register" property in the screen editor.  No code needed.

Steve