Hello Guest it is October 28, 2020, 05:21:11 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

Galil / Re: Upgraded to win7 on PCI system - now weird VFD behavior
« on: April 06, 2016, 07:28:21 PM »
Wow...  That is a weird one!

All the check box does is control whether or not to use a JG command or an OF to run the spindle.  It does no other magic. 

I assume that your spindle does not use an encoder.  If that is the case, then the KP, KI, and KD parameters for the axis driving the spindle all need to be set to 0 and burned with the BN command.  Otherwise, you need to have proper PID values to use an encoder.

Maybe your previous card had the PID set to zero and you new one doesn't.  That is the only thing I can come up with. 

Hello Steve, just a quick question, I have a Hardinge HNC lathe with a Galil 2130 running a VFD and have it working without the encoder, but how do I tune the (and get the P.I.D Values) so that I can use the encoder that I have on the spindle...it's a 2500 PPR quad encoder 1-1 on the spindle? The encoder is properly wired to the Y(B) axis that sends the 0-10v to the VFD also this encoder has index..does that help anything? hoping I can try threading!

-Roo Trimble...BTW: to see a lot of fun Mach-created widgits take a look at the little car that I bulit...www.roopod.com   Thanks in advance!

First, the VFD must be able to run like a servo drive.  In most cases, this means that it can accept a +-10v command signal AND allow disabling on its internal PID control loop.  This allows the Galil to run the control loop.  Then you set up the PID values in the Galil.  You cannot have two control loops running!  That is a PID fight.  Much worse than a cat fight.  :)  As to what values to use for PID in the Galil, that is very VFD/motor dependent.  And it is NOTHING like tuning a table load for a servo.  Galil has an application note that explains some of the peculiarities. 

If the VFD has a setup that shows the internal PID values, you can then use those to figure the ratios between P, I, and D, but the actual numbers will be different on the Galil.  If the VFD can't disable its own PID loop (very common, unfortunately), you are then stuck with the unenviable task of trying to match the PID loop on the VFD to the one on the Galil EXACTLY to avoid a PID fight.  Not easy to do.  But people get lucky sometimes...

Second, only Kenny has threading working on his lathe.  And it was a HUGE task.  Not for the feint of heart.  It evolves writing a Galil language routine that runs on the Galil, a modified 1076 macro, and Notifies setup to poke values down to the Galil.  The index pulse can be used to sync the thread.  However, it is just a blip on the radar and Kenny had to run that index pulse into a one shot timer to extend the signal beyond 4ms.  The output of the one shot timer is then wired to two GP inputs (the position latch inputs 1 and 3) to "start" the threading routine that is running on the Galil.  The Galil routine should be modified to reflect the counts per unit of the machine. 

The details and files required for this are here: http://www.smcomp.com/~smurph/exes/MachGalilThreading.zip.  However, you are on your own to get this working.  Kenny and I are too busy to provide any kind of support in this realm. 


Those properties are available with an Industrial or Expert license.  If in demo mode or Hobby license, they are not available.  If you have an industrial or Expert license, there is a checkbox in the General tab of the Mach config labeled "Use Advanced GUI Controls?" that enables or disables these properties as well.  


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

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.


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. 

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.  :)


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.


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. 


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.


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.