Advanced Search

spumco wrote:

Wouldn't misalignment between motor and driven component tend to break outboard of the bearing?  That's assuming the bearing didn't come with lots of negative preload from the factory, of course.

This is one of those cases where, given the final result, I can think of a plausible explanation. But that would be true in either case...
The moment is greater further from the shaft end, and a ball bearing isn't particulary stiff against torsion. Also the step that the bearing butts against, if machined poorly, might be a stress raiser. 

andypugh wrote:

I think we would need a better macro photo to tel if that was a fatigue failure or not, but it leads me to be rather suspicious of the motor-to-shaft alignment and mounting. Is there any type of flex-coupling there?

I couldn't make out any beach marks on the surface. A macro would be interesting, as would pulling the bearing shield/seal and checking for signs of heat or abnormal conditions.

Wouldn't misalignment between motor and driven component tend to break outboard of the bearing?  That's assuming the bearing didn't come with lots of negative preload from the factory, of course.

If you are looking for on site assistance, it might help to start with saying where you are located. There are Linuxcnc users all over the world. (And a few might even have spare time to pop in and give you a hand.)

Cherna post=325580 userid=43095My worry was that I was missing something that led other (more knowledgeable people) to mark this chipset as not working with LinuxCNC, but as you said if it works, it works.

Hopefully this post helps someone in my same situation in the future.

Thanks a lot for your answer.

If a card has a history of not working in the past, but does work now, the most plausible reason is that kernel updates added support for the chip used on that board.  The Linux kernel is continually being updated adding support for new hardware, and there is often a bit of a lag from a chips introduction, to inclusion in the kernel, plus add the fact that the real time kernels used by Linuxcnc are never bleeding edge.

Could've been an expensive trip if you went through the gyprock, was it one of those times you could see what was going happen next, lol.

I got the machine to open now.
But when i try to home the axis it gives me a "Joint.0 following error"

Attaching my current X set-up here.
I'd be greatful if anybody finds some time to look over it!

CODE:
#**********************************************
# X Axis (Joint: 0 / Output: 0)
#**********************************************

# PID Setup
setp pid.x.Pgain [JOINT_0](P)
setp pid.x.Igain [JOINT_0](I)
setp pid.x.Dgain [JOINT_0](D)
setp pid.x.bias [JOINT_0](BIAS)
setp pid.x.FF0 [JOINT_0](FF0)
setp pid.x.FF1 [JOINT_0](FF1)
setp pid.x.FF2 [JOINT_0](FF2)
setp pid.x.deadband [JOINT_0](DEADBAND)
setp pid.x.maxoutput [JOINT_0](MAX_OUTPUT)
setp pid.x.error-previous-target True
# limit stepgen velocity corrections caused by position feedback jitter
setp pid.x.maxerror [JOINT_0](MAX_ERROR)

# joint-0 enable chain
net joint-0-index-enable <=> pid.x.index-enable
net joint-0-index-enable <=> joint.0.index-enable

net joint-0-enable <= joint.0.amp-enable-out
net joint-0-enable => pid.x.enable

net joint-0-enable => hm2_[MESA](BOARD).0.stepgen.00.enable

# Joint 0 Step Generator Settings
setp hm2_[MESA](BOARD).0.stepgen.00.dirsetup [JOINT_0](DIRSETUP)
setp hm2_[MESA](BOARD).0.stepgen.00.dirhold [JOINT_0](DIRHOLD)
setp hm2_[MESA](BOARD).0.stepgen.00.steplen [JOINT_0](STEPLEN)
setp hm2_[MESA](BOARD).0.stepgen.00.stepspace [JOINT_0](STEPSPACE)
setp hm2_[MESA](BOARD).0.stepgen.00.position-scale [JOINT_0](SCALE)
setp hm2_[MESA](BOARD).0.stepgen.00.maxvel [JOINT_0](STEPGEN_MAX_VEL)
setp hm2_[MESA](BOARD).0.stepgen.00.maxaccel [JOINT_0](STEPGEN_MAX_ACC)
setp hm2_[MESA](BOARD).0.stepgen.00.step_type 0
setp hm2_[MESA](BOARD).0.stepgen.00.control-type 1


# joint 0 pos/vel/fb
net joint.0-pos-cmd <= joint.0.motor-pos-cmd
net joint.0-pos-cmd => pid.x.command

net joint.0-pos-fb <= hm2_[MESA](BOARD).0.encoder.00.position
net joint.0-pos-fb => joint.0.motor-pos-fb
net joint.0-pos-fb => pid.x.feedback

net joint.0-vel-cmd <= joint.0.vel-cmd

net joint.0.output <= pid.x.output
net joint.0.output <= hm2_[MESA](BOARD).0.stepgen.00.velocity-cmd

net Joint.0-vel-fb <= hm2_[MESA](BOARD).0.encoder.00.velocity
net joint.0-pos-rawcounts <= hm2_[MESA](BOARD).0.encoder.00.rawcounts
net joint.0-index-enable <=> hm2_[MESA](BOARD).0.encoder.00.index-enable

# Encoder
setp hm2_7i95.0.encoder.00.counter-mode 0
setp hm2_7i95.0.encoder.00.filter 1
setp hm2_7i95.0.encoder.00.index-invert 0
setp hm2_7i95.0.encoder.00.index-mask 0
setp hm2_7i95.0.encoder.00.index-mask-invert 0
setp hm2_7i95.0.encoder.00.scale [JOINT_0](ENCODER_SCALE)


# Home
net home-x => joint.0.home-sw-in
net x-neg-limit => joint.0.neg-lim-sw-in
net x-pos-limit => joint.0.pos-lim-sw-in