Sherline and Gecko
08 Mar 2014 05:07 - 08 Mar 2014 05:08 #44556
by MattM
Sherline and Gecko was created by MattM
I know there are sample configs for both of these in the basic LinuxCNC install. But I am setting up a machine for the first time, and it is a Sherline 2000 4-axis Mill, but with GeckoDrive 540 controller and Gecko G723-280-4 steppers.
Is there some way to build the right config by picking and copying selected files from each? I'm trying to avoid manual entry, measurement and calculation of any values, at least until I get more familiar with this software.
Thanks!
Is there some way to build the right config by picking and copying selected files from each? I'm trying to avoid manual entry, measurement and calculation of any values, at least until I get more familiar with this software.
Thanks!
Last edit: 08 Mar 2014 05:08 by MattM.
Please Log in or Create an account to join the conversation.
08 Mar 2014 18:31 #44563
by Rick G
Replied by Rick G on topic Sherline and Gecko
I think your best bet is to run the latency test, use those numbers in Stepconf to create a configuration that will work with your computer and hardware.
You can then edit this config using the sherline 4 axis sample config as an example or edit the sherline files to match your hardware.
Depending on the version of linuxcnc there may also be a sample config for a gecko-540 4 axsi (gecko_540B4) but that may only be on linuxcnc dev.
There are several threads here on linuxcnc and gecko 540 to help.
Rick G
You can then edit this config using the sherline 4 axis sample config as an example or edit the sherline files to match your hardware.
Depending on the version of linuxcnc there may also be a sample config for a gecko-540 4 axsi (gecko_540B4) but that may only be on linuxcnc dev.
There are several threads here on linuxcnc and gecko 540 to help.
Rick G
Please Log in or Create an account to join the conversation.
08 Mar 2014 22:56 - 08 Mar 2014 22:57 #44568
by MattM
Replied by MattM on topic Sherline and Gecko
It's the latest version and comes with the following in the sample configs directory:
Gecko_540B4
custom.hal
custom_postgui.hal
Gecko_540B4.hal
Gecko_540B4.ini
Gecko_540B4.stepconf
README
tool.tbl
Sherline4Axis
README
Sherline4Axis_inch.ini
Sherline4Axis_mm.ini
standard_pinout.hal
stepper.tbl
stepper_xyza.hal
I just started to get a little confused looking through these files... For instance, the Gecko directory contains a stepconf XML file to edit and get started, but the Sherline directory does not. I was thinking the files would be a little more consistent and just contain different data: stepper.tbl in one directory, not the other, tool.tbl in one and not the other, stepper_xyza in one and not the other, etc.
Gecko_540B4
custom.hal
custom_postgui.hal
Gecko_540B4.hal
Gecko_540B4.ini
Gecko_540B4.stepconf
README
tool.tbl
Sherline4Axis
README
Sherline4Axis_inch.ini
Sherline4Axis_mm.ini
standard_pinout.hal
stepper.tbl
stepper_xyza.hal
I just started to get a little confused looking through these files... For instance, the Gecko directory contains a stepconf XML file to edit and get started, but the Sherline directory does not. I was thinking the files would be a little more consistent and just contain different data: stepper.tbl in one directory, not the other, tool.tbl in one and not the other, stepper_xyza in one and not the other, etc.
Last edit: 08 Mar 2014 22:57 by MattM.
Please Log in or Create an account to join the conversation.
08 Mar 2014 23:02 #44569
by MattM
Replied by MattM on topic Sherline and Gecko
Started digging a little further...
The tool.tbl in the Gecko directory is identical to the stepper.tbl in the Sherline directory, and both list tools. So it looks like just bad file naming.
The tool.tbl in the Gecko directory is identical to the stepper.tbl in the Sherline directory, and both list tools. So it looks like just bad file naming.
Please Log in or Create an account to join the conversation.
08 Mar 2014 23:13 #44570
by ArcEye
Replied by ArcEye on topic Sherline and Gecko
Hi
You can call the files whatever you want.
GeckoB3 and GeckoB4 have consistant names because they were done at the same time by the same person.
There is no relationship between Gecko and Sherline, so no reason for the file naming to be the same
Who connected up this mill? Where is the configuration?
What matters is what is connected to which pin, the hardware it is used on or the drives it uses, are largely irrelevant, save from driver timing issues and scale.
regards
You can call the files whatever you want.
GeckoB3 and GeckoB4 have consistant names because they were done at the same time by the same person.
There is no relationship between Gecko and Sherline, so no reason for the file naming to be the same
Who connected up this mill? Where is the configuration?
What matters is what is connected to which pin, the hardware it is used on or the drives it uses, are largely irrelevant, save from driver timing issues and scale.
regards
Please Log in or Create an account to join the conversation.
09 Mar 2014 16:24 #44594
by Rick G
Replied by Rick G on topic Sherline and Gecko
The names of many of the files that a config uses are set in the ini file.
www.linuxcnc.org/docs/devel/html/config/ini_config.html
some_file_name.tbl is the name of the tool table that config uses.
If you run Stepconf it will create a basic config for you and take care of all of that.
You need to know how the machine is wired to the parallel port.
Use the gecko information for the step and direction timing.
Try the sherline config for the mechanics, gear ratio, scale, etc.
Use your latency test to set the base thread.
Rick G
www.linuxcnc.org/docs/devel/html/config/ini_config.html
some_file_name.tbl is the name of the tool table that config uses.
If you run Stepconf it will create a basic config for you and take care of all of that.
You need to know how the machine is wired to the parallel port.
Use the gecko information for the step and direction timing.
Try the sherline config for the mechanics, gear ratio, scale, etc.
Use your latency test to set the base thread.
Rick G
Please Log in or Create an account to join the conversation.
Time to create page: 0.068 seconds