Messages

1321

Galil / Re: Limit switch tripping

« on: February 10, 2011, 07:44:13 PM »

One the plugin config general tab, there is the option to configure the limits and homes active low.  These check boxes determine how is CN configured.  If yours is checked, uncheck it, or visa verse.  You may have to go back to the ports and pins page and undo what you did there.

The deal is that you need the Galil to be satisfied as to the switch arrangement first.  This is done with the plugin config.  Then you need to get Mach lined up in Ports and Pins.

Steve

1322

Galil / Re: Galil error code # 1 (Unrecognized command)

« on: February 09, 2011, 11:13:30 PM »

Turn on the debug output in the plugin config and send the GalilDebug.txt to Kenny or me.  Our email addresses are in the Plugin docs.  I bet your firmware needs updating.  What does Smart Term report for your firmware revision?

Steve

1323

Galil / Re: Mach3 with a DMC-2162 (Aero)

« on: February 07, 2011, 09:11:04 PM »

If you will go to the Mach Diagnostic screen, you will see that a limit switch has been tripped. 

And that error is a Galil error!  So you have an issue with the Galil thinking that a limit is tripped for your Galil D axis.  When a limit is tripped, you can only move the axis in the direction that would take it off the switch.  The "22 Begin not possible due to limit switch." error is axis specific.  Meaning that the Galil does indeed see an active limit switch for your Galil D axis (the one you were trying to move).  It is not a global error where another axis limit switch would keep your D axis from moving.  I suspect a wiring issue.  Did you change the polarity of LSCOM?

Any error message that begins with "Galil Error:" then a number and then a description is a Galil message.  You can look at the Galil user manual to see what that error is and what to do to correct it.

Uninstalling Mach and re-installing is not ever going to help anything.    The program does not corrupt that easily.  In fact, it just increases your chances of overwriting some setting that you previously had correct.

I can report that your AC and DC values look much better!

Steve

1324

Galil / Re: Mach3 with a DMC-2162 (Aero)

« on: February 07, 2011, 06:57:46 PM »

A motor running away most likely means that the encoder is not following the direction of the motor.  Swap the A & B signals at the ICM and see if your runaway stays home. 

Once you get your motor staying home, then you can reverse it if necessary in the plugin config by selecting "servo revesed" for that Galil axis.  And get your DROs reporting correct direction with the Ports and Pins.

Steve

1325

Galil / Re: Galil controller compatability (what works with the plugin)

« on: February 07, 2011, 12:49:23 PM »

Heh...  I bet -3 does feel worse!!! 

The units could be one issue.  But getting that acceleration correct is going to make things a lot better.

Steve

1326

Galil / Re: Galil controller compatability (what works with the plugin)

« on: February 07, 2011, 12:40:44 AM »

Look at the calculated G force!  Almost 13 Gs!  Your acceleration is still too high.  We humans black out a 4 to 6 Gs.    And I think you are blowing the controller's mind.  Set your accel to get a G force of less than 1.

Steve

1327

Galil / Re: Galil controller compatability (what works with the plugin)

« on: February 05, 2011, 08:31:04 PM »

Your AC DC settings come from Mach settings in Config->Motor Tuning.  You need to set the counts per unit correctly as well.

You might want to read the Mach documentation a bit more to get an understanding on what is required in the Mach settings.  They are geared to the parallel port, but the concept is the same no matter what control you are using.  You will then be able to put all of the pieces together.

You need to do this for all of your axes:

1. Enable the axis in Config->Ports and Pins (motor tab).
2. In motor tuning, set your counts per unit, the max seed, and acceleration.  (This is where your problem is)

Then, in the Galil plugin config:

1. Map the Mach axes to the Galil axes.
2. Set the motor types.

Do not map multiple Mach axes to one Galil axis.  Meaning each Mach axis requires a unique Galil axis.

The PID settings should be the only thing burned into the Galil's NVRAM.  All other settings are calculated from Mach settings (which HAVE to be correct for your machine).

Disable the MPG until you get the Motor Tuning corrected.  It can make things harder to diagnose.  Also, set the motor type for your E and F Galil axes to servo to get rid of the SM jumper warning.

Steve

1328

Galil / Re: Galil controller compatability (what works with the plugin)

« on: February 05, 2011, 10:44:34 AM »

None of those step/dir parameters are required.

1329

Galil / Re: Galil controller compatability (what works with the plugin)

« on: February 05, 2011, 12:05:19 AM »

I don't know why you had problems with the plugin, as it has been at version 4.4 for a good while now.  Neither Kenny nor myself have updated the website.

To run a servo, the plugin needs the motor type to be set to either "servo" or "servo reversed" and the stepper jumpers on the Galil for that axis need to be open.  Also, the KP, KI, and KD parameters need to be burned in the NVRAM.

Verify that you can get axis movement in SmartTerm or Galil Tools before trying to configure the Mach plugin.  Please read the plugin documentation about turning on debug output and send us a GalilDebug.txt file if you continue having problems.

Steve

1330

Galil / Re: Galil controller compatability (what works with the plugin)

« on: February 02, 2011, 11:08:55 PM »

That error means that the plugin could not find some support DLL.  The plugin is linked against these Windows system DLLs.  These should all reside in the System32 directory. 

dmc32.dll (SmartTerm)
dmcser32.dll (SmartTerm)
VERSION.dll
KERNEL32.dll
USER32.dll
GDI32.dll
comdlg32.dll
ADVAPI32.dll
COMCTL32.dll
SHLWAPI.dll
ole32.dll
OLEAUT32.dll

Sometimes a bare bones Windows install does not provide all of these DLLs.

Steve