Messages

971

Galil / Re: Spindle Control Through Galil Digital Output

« on: December 26, 2010, 10:56:27 PM »

There is a pin mapping in the Galil Plugin PDF.  Simply locate the output pin number that corresponds with the Galil output that you want to use and put that pin number in for the Mach output signal.

Steve

972

Galil / Re: Need Help with Galil Setup on DMC-1842

« on: December 24, 2010, 02:08:00 PM »

Abort is only brought to the Galil.  Meaning that it is not an input signal that get passed to Mach.  Simply jumper a wire from Abort to a general input of your choice and use that as your EStop in Mach.

Steve

973

Galil / Re: Spindle Control Through Galil Digital Output

« on: December 23, 2010, 03:11:52 PM »

Map Mach Output #1 to a Galil output in Ports and Pins "Output Signals".  Do the same for Mach Output #2 to another Galil output.  The Port and Pin settings are in the Galil Plugin documentation.  Then, on the Ports and Pins "Spindle" tab, enable your spindle relays.  Clockwise is output #1 and counter clockwise is output #2.

Since you have a 2 axis controller, you will not be able to control the speed of your spindle from the Galil.  That would require another axis, so your encoder wont do you much good here. 

Steve

974

Galil / Re: Need Help with Galil Setup on DMC-1842

« on: December 23, 2010, 03:02:44 PM »

All of what you need to do is done in Mach.  These questions apply to setting up any motion device for Mach whether it be Galil or the Printer port, etc...

ANSWER 1. 

You need to enable the motors in Config->Ports and Pins.  Click on the motor outputs tab and enable all of your axis motors (x, y, z and a for your slaved axis). 
Now you will be able to input the counts per unit in the motor tuning dialog.

ANSWER 2.

Config->Slave Axis.  Then for the X axis, choose the A radio button.  Restart Mach.

975

Galil / Re: Galil to Mach

« on: December 23, 2010, 02:52:39 PM »

Enable debug output in the plugin confguration and run a program.  Then take a look at the GalilDebug.txt file.  If there are a bunch of '?' characters in the file, then the firmware is probably the problem. 

You can download the firmware from the Galil website and then upload the new firmware from the Smart Term program.

Steve

976

Galil / Re: X,W home problems

« on: December 20, 2010, 06:13:12 PM »

Dave,

PM me your email address.  I send you a plugin to try out.

Steve

977

Galil / Re: Another gantry mode limit switch question

« on: December 16, 2010, 12:17:52 AM »

I would suspect that Mach treats the gantry axes as one axis.  Thus when the limit is tripped, Mach does the same for the slaved axis.

Homing...  It's supposed to home both gantry axes at the same time because they are geared together with GR (operating on the master axis switches).  Then, if axis squaring is checked in the config, it will decouple the axes and home the slaved axis to it's switches and then recouple the axes.  This second op should not move the axis very much.  Just enough to square the gantry.  In theory, that's how it should work.  But I have no way of testing it because I don't have a gantry machine.

Steve

978

Galil / Re: Multi-pull Galil controllers

« on: December 14, 2010, 01:15:08 AM »

Using two Galil controllers to gain axes is not possible.  

Also, you will need to use USB for the connection instead of Serial.

Steve

979

Mach SDK plugin questions and answers. / Re: Disabling I/O during file loading

« on: December 11, 2010, 01:27:09 AM »

Mach is generating the tool path at this point, so it's not a true simulation.  MainPlanner->PathGenerate is set to true when the gcode file is loading.  Stick this in your update loop to keep your plugin quiet while loading a file:

Code: [Select]

if (MainPlanner->PathGenerate) {
return;
}


980

Mach SDK plugin questions and answers. / Re: Communicate RS232 port

« on: December 11, 2010, 12:42:28 AM »

I would use the Windows API to do the serial port duties.  Have a look at CreateFile(), WriteFile(), ReadFile(), and DeviceIoControl();

CreateFile uses the NT namespace to open a device.  "\\.\COM1" would operate on COM1, etc...  Remember that the backslash is an escape character in C/C++, so in the code, the device path would be "\\\\.\\COM1"

Steve