Guest
Show Posts
1371
Galil / Re: Home switch set up
« on: December 30, 2010, 02:06:38 AM »
-X low and X home enabled with the same pin config is not a good idea. They are two separate signals in Mach. So keep them separate. Map Mach X-- to port 1, pin 9. Then map Mach X home to port 1, pin 17. If you use a limit switch also for a home switch, jumper the switch to both the -X and X home on the Galil ICM. Limits switch signals are disabled when homing! This is to allow using a limit switch also as a home switch. (Which I really don't know why anyone would want to do, but people asked for it. Me? I'm buying a $8.00 switch to do the job...)
The Galil plugin is looking for the Mach home signal to become activated. It basically does a jog towards the home switch using the Galil JG command. Say 2000 counts per second. That would be JGX=2000 to move the X axis in a positive direction as 2000 is a positive number. If you hit the home switch and then move off before Mach catches the signal (1/10th of a second), then you might have a problem. If this is the case, you need to rig your switch to stay activated longer.
When Mach sees the home signal get activated, the galil plugin stops the axis. It then reverses the axis by taking the initial jog velocity and multiplying it times -0.1 So 2000 becomes -200. So JGX=-200 is sent to the controller.
When Mach sees the home switch go to the inactive state, the galil plugin stops the axis withing 1/10th of a second. Homing is done at this point unless you have specified the use of the index pulse.
If using the index pulse, the galil plugin issues the same JGX=-200 jog command until it finds the index pulse from the encoder.
That's the sequence anyway. If you are blowing past your switch and your are seeing the signal light up in Mach, then there might be an error in the commands going to the controller. Enable the debug output in the plugin configuration. This creates a GalilDebug.txt file with the commands sent to the controller and the controller's response to them. Then repeat your home operation and exit Mach. This will fill the GalilDebug.txt file with the information from your home operation. Then find the GalilDebug file (usually in c:\mach3 or c:\mach3\plugins) and send it to either Kenny or Myself. Our email addresses are in the plugin PDF manual.
Steve
The Galil plugin is looking for the Mach home signal to become activated. It basically does a jog towards the home switch using the Galil JG command. Say 2000 counts per second. That would be JGX=2000 to move the X axis in a positive direction as 2000 is a positive number. If you hit the home switch and then move off before Mach catches the signal (1/10th of a second), then you might have a problem. If this is the case, you need to rig your switch to stay activated longer.
When Mach sees the home signal get activated, the galil plugin stops the axis. It then reverses the axis by taking the initial jog velocity and multiplying it times -0.1 So 2000 becomes -200. So JGX=-200 is sent to the controller.
When Mach sees the home switch go to the inactive state, the galil plugin stops the axis withing 1/10th of a second. Homing is done at this point unless you have specified the use of the index pulse.
If using the index pulse, the galil plugin issues the same JGX=-200 jog command until it finds the index pulse from the encoder.
That's the sequence anyway. If you are blowing past your switch and your are seeing the signal light up in Mach, then there might be an error in the commands going to the controller. Enable the debug output in the plugin configuration. This creates a GalilDebug.txt file with the commands sent to the controller and the controller's response to them. Then repeat your home operation and exit Mach. This will fill the GalilDebug.txt file with the information from your home operation. Then find the GalilDebug file (usually in c:\mach3 or c:\mach3\plugins) and send it to either Kenny or Myself. Our email addresses are in the plugin PDF manual.
Steve
