Hello Guest it is September 21, 2019, 04:52:21 PM

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

431
Galil / Re: Galil + G31+ Mach3
« on: September 16, 2016, 10:31:15 PM »
In other words, if you are going to probe, you must dedicate at least inputs 1, 2, and 3 to the probe.  If some other switch is tickling ANY of those inputs, it will be seen as a probe latch.  Not too good!  So please un-wire anything connected to inputs 1 and 2 (X and Y latches) and if you are going to do that, you might as well wire the  probe to all 3 of them.  Remember to wire in input 4 if you have A axis enable in Mach too!

Steve

432
Galil / Re: Galil + G31+ Mach3
« on: September 16, 2016, 10:27:17 PM »
Correct, the plugin handles AL and RL.  But understand that the plugin will do an AL for every axis it controls.  So you really need to wire the probe to all three of the latch inputs if you have X, Y, and Z axes enabled in Mach, regardless if you will only be doing Z probe moves.  If A axis is enabled in Mach, then wire in input 4 as well. 

Steve

433
Galil / Re: Galil + G31+ Mach3
« on: September 16, 2016, 01:31:10 PM »
In order to use a Galil, one must understand how the Galil works.  The plugin documentation assumes that the user is familiar with the Galil and we don't try to teach or document Galil aspects that are in the Galil documentation.  You can't simply hook up a Galil and run the plugin and it magically work.  This is because the Galil has its' own motion planner and can be used as a stand alone motion controller.  It is not a "dumb" controller like a parallel port or some other step generator motion device.  This makes it more complicated to setup, but the end result is worth it.  

The latch inputs are a Galil term.  Look at the Galil operator's manual and command reference (AL and RL) and read up on the latch inputs.  There is one latch input per Galil axis.  You need to wire the probe to all of the latch inputs that from which you wish to get a position.  For a 3 axis mill, that would be X, Y, and Z, meaning Galil input 1, 2, and 3.  Galil Input 6 is not going to cut it.  :(

Since the probe will be wired to multiple inputs, simply pick one of those inputs and map it to Mach's probe signal.  Mach only has one probe signal and it is NOT used to capture the the positions.  The Galil does that via AL and RL.  However the Mach probe signal is used to prevent a probe move if it thinks the probe is activated.  If the probe is not activated and Mach thinks it is, simply check or uncheck the Mach digitize "active low" setting until the signal agrees with the actual state of the probe.  

Steve


434
Mach4 General Discussion / Re: LOVING the PMC!! Thanks Steve!!!
« on: September 11, 2016, 08:10:24 PM »
Probably not until after IMTS.  :(

435
Mach4 General Discussion / Re: LOVING the PMC!! Thanks Steve!!!
« on: September 02, 2016, 08:05:22 PM »
The SAFE thing to do is use a general availability release from the main page.  :)  ANY of them from the development ftp site are likely to be bleeding edge. 

Steve

436
Mach4 General Discussion / Re: LOVING the PMC!! Thanks Steve!!!
« on: September 01, 2016, 12:52:12 AM »
Well...  that is hard to say.  Maybe by week's end?  I'm working on jogging during feed hold and it is a complex issue.  :(

437
Mach4 General Discussion / Re: LOVING the PMC!! Thanks Steve!!!
« on: August 31, 2016, 08:12:55 PM »
Arturo,

I added the encoder registers in the list of input registers for the PMC.  So the next build will have that in there.  However, I really don't think the PMC is the proper place for it.  That sounds like something the motion controller plugin should be doing.

Steve

438
Mach4 General Discussion / Re: LOVING the PMC!! Thanks Steve!!!
« on: August 30, 2016, 11:39:18 PM »
Arturo,

At this time, encoder registers are not included in the list of input registers.  But are you needing an encoder value in the PMC?  To drive an MPG?  If so, you can associate an encoder to a MPG object in the Mach config.

Steve

439
Mach4 General Discussion / Re: Re: Mach 4 and Galil
« on: August 23, 2016, 12:04:19 PM »
We are in the final stages of releasing it.  Be aware that it will be a licensed product for Mach 4, meaning there will be a cost to it.  As to what the cost will be, I don't know at this point.  

The "supported" controllers will be the 40x0 and 41x3 controllers.  However, the older 21x3 and 21x0 controllers may work but no testing has been done at this point.  Rigid tapping and lathe threading are not implemented yet.  ISA cards will not be supported at all.  

Galil is working on a special Mach 4 firmware that will enable advanced features such as movement coordinated outputs, single input probe latches, backlash compensation, and screw mapping.  This firmware will be available to users that purchase a 41x3 or 40x0 from Galil.  This firmware will not be available for the older controllers.

Steve

440
Mach4 General Discussion / Re: CNC movements not smooth
« on: August 19, 2016, 04:16:53 PM »
The only M codes that don't break the CV chain are M62 and M63.  M03 and M05 will.  If you think about it, you would never want the look ahead to turn your spindle off (M05) when the machine is actually still 100 lines back in the G code (assuming you have a 100 line look ahead set).  So when the interpreter look ahead runs up to a M05, it simply waits until all of the prior motion is complete (and it will be an exact stop) before turning the spindle off. 

The reason Pedio's code works is because the S word is given just once before a large set of G01 blocks.  CV is in effect for all of those G01 blocks. 

Steve