Need Help Setting Up a 2nd Spindle
- richcolvin
-
Topic Author
- Offline
- New Member
-
Less
More
- Posts: 11
- Thank you received: 0
22 May 2025 22:39 #328948
by richcolvin
Need Help Setting Up a 2nd Spindle was created by richcolvin
I am trying to configure LinuxCNC for use on a rose engine with 2 spindles + 6 other axes.
Everything works for Spindle0 & the other 6 axes of movement (X, Y, Z, B, U, & V), however I cannot get Spindle1 to work. Any ideas would be greatly welcomed!
I've copied the key items I believe are needed below. The complete versions of the HAL and INI files are attached. (The include files for the spindles had to be renamed to be .ini for attaching them, but they are actually .inc.)
hal fileloadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS num_spindles=[TRAJ]SPINDLES
loadrt hostmot2
loadrt hm2_eth board_ip="192.168.1.121" config="num_encoders=0 num_pwmgens=0 num_stepgens=8"
loadrt pid names=pid.x,pid.y,pid.z,pid.b,pid.u,pid.v,pid.s0,pid.s1
(other sections are also configured for SPINDLE 1, and are setup fundamentally the same as they are for SPINDLE 0)
ini file[TRAJ]
SPINDLES = 2
# [JOINT_7]
# SPINDLE = 0
# TYPE = ANGULAR
[SPINDLE_0]
(this works as expected, so I've not added the details here)
[JOINT_6]
SPINDLE = 1
TYPE = ANGULAR
[SPINDLE_1]
(the rest is setup just as with SPINDLE_0)
Side Note: Please don't refer me to RoseKins. I tried that and it will not meet our needs.
Everything works for Spindle0 & the other 6 axes of movement (X, Y, Z, B, U, & V), however I cannot get Spindle1 to work. Any ideas would be greatly welcomed!
I've copied the key items I believe are needed below. The complete versions of the HAL and INI files are attached. (The include files for the spindles had to be renamed to be .ini for attaching them, but they are actually .inc.)
hal fileloadrt [KINS]KINEMATICS
loadrt [EMCMOT]EMCMOT servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[KINS]JOINTS num_spindles=[TRAJ]SPINDLES
loadrt hostmot2
loadrt hm2_eth board_ip="192.168.1.121" config="num_encoders=0 num_pwmgens=0 num_stepgens=8"
loadrt pid names=pid.x,pid.y,pid.z,pid.b,pid.u,pid.v,pid.s0,pid.s1
(other sections are also configured for SPINDLE 1, and are setup fundamentally the same as they are for SPINDLE 0)
ini file[TRAJ]
SPINDLES = 2
# [JOINT_7]
# SPINDLE = 0
# TYPE = ANGULAR
[SPINDLE_0]
(this works as expected, so I've not added the details here)
[JOINT_6]
SPINDLE = 1
TYPE = ANGULAR
[SPINDLE_1]
(the rest is setup just as with SPINDLE_0)
Side Note: Please don't refer me to RoseKins. I tried that and it will not meet our needs.
Please Log in or Create an account to join the conversation.
- richcolvin
-
Topic Author
- Offline
- New Member
-
Less
More
- Posts: 11
- Thank you received: 0
22 May 2025 22:41 #328949
by richcolvin
Replied by richcolvin on topic Need Help Setting Up a 2nd Spindle
The attempts to run the spindle are by using:
M3 S10 $0 <=== that works
M3 S10 $1 <=== does not work
M3 S10 $0 <=== that works
M3 S10 $1 <=== does not work
Please Log in or Create an account to join the conversation.
- PCW
-
- Away
- Moderator
-
Less
More
- Posts: 18706
- Thank you received: 5163
22 May 2025 22:46 - 22 May 2025 22:47 #328950
by PCW
Replied by PCW on topic Need Help Setting Up a 2nd Spindle
# net machine-is-on => hm2_7i92.0.stepgen.07.enable
AFAICS, nothing sets hm2_7i92.0.stepgen.07.enable true so it can never run.
try removing the comment (#) :
net machine-is-on => hm2_7i92.0.stepgen.07.enable
AFAICS, nothing sets hm2_7i92.0.stepgen.07.enable true so it can never run.
try removing the comment (#) :
net machine-is-on => hm2_7i92.0.stepgen.07.enable
Last edit: 22 May 2025 22:47 by PCW.
Please Log in or Create an account to join the conversation.
- andypugh
-
- Offline
- Moderator
-
Less
More
- Posts: 23361
- Thank you received: 4962
23 May 2025 20:56 #329017
by andypugh
Replied by andypugh on topic Need Help Setting Up a 2nd Spindle
Use "
Halshow
" to check that the spindle.1.xxxxx pins are doing the right things, and trace the signals from there.
Please Log in or Create an account to join the conversation.
Time to create page: 0.233 seconds