Advanced Search

Is that just a y thing?

Is it possible to run all these things together: 

Mesa 7i76 E  ---- 7I84 (Isolated remote field I/O card). Will use it to output quadrature signals to the Ultra3000s, it will generate this quadrature output from the Fanuc encoders [is this possible?], remaining I/O used elsewhere. 
                               
                         ---- 7I85 (4 Channel encoder 5 channel Serial RS-422 interface). Will hook up the 4 Fanuc redcaps to 4 of these RS-422 ports. And the encoder inputs are good to have around incase I want to add linear scales (2 axis) and maybe two MPG wheels. 

Sure would be great if this system worked because it happens to be two fairly inexpensive boards. Canadian dollar isn't so great right now 
I would be pleased to have those encoder inlets, too. 

Progress pic from a little while ago: 
 

Licenses were reviewed in depth by Debian as part of getting into their distros. (There are many different licenses) I think you can say the differences in licenses is not a conflict or we would not be in Debian

If the axis do not move, I would check:

1. That you don't have a watchdog bite
(If you are running "Axis" it will report this if not,
you may need to check with halshow)


2. The physical wiring (remember I asked what were the
connections between TB2 pins and drive signals?)


3. The timing specifications of the drives (the current timings should work
with most drives but there are so oddball drives with really slow inputs)


 

Y cannot jog until it is homed.

andypugh wrote:

Is there any chance that this corresponds to something in the kinematics? Maybe an inflection point in one of the joints?

Its possible that at that point another joint starts contributing to the motion.
Think of 2D motion on X & Y at 45 deg at max velocity. Both axes will be moving at their max, but the total combined axis velocity  will be about 40% higher.

okay update. 

I reran the pncconf, reassigned the second y as a tandem and also corrected what turns out was mis-assignment by me initially. Everything should be good to go now in terms of what the board thinks is assigned and what is actually. Updated hal and ini attached. 

Still no movement from any axis:
X: Does nothing physically but machine thinks its jogging (DRO updating)
Y: Throws an error: "Cannot Jog Joint 1 because home_sequence is synchronized 
Z:Does nothing physically but machine thinks its jogging (DRO updating)
A: Does nothing physically but machine thinks its jogging (DRO updating)

totally make sense thanks for your help.

I just went to restart the pncconf and i only have three options when it comes to kinematics: XYZ, XYZA, OR XZ lathe. I believe i am missing some options here in this drop down.

edit: im stupid, trying again now.