Advanced Search

20 rdy missing?

15 oz+
14 ob+
13 oa+
11 da ground gnda
10 as-
6 brk
5 alm
2 drive disabled cwl
1 aclr
30 oz-
29 ob-
28 oa-
26 as+
23 do com
17 drive disabled ccwl
16 son
31 com+

Hello, what connections are needed for the 7i97t?
I have this spreadsheet, and these are the connectors.

has no rdy
 

I dont thimk so. when i checked the ini file, there was nothing under Traj, so i added AXES=4, and it worked

Is rdy needed?

In the lay out the X arrow is not correct as it is to the negative, not positive as mine is.
So remove the input pins and put 0.0 in the 3 locations you show, I will try that.
In a new config for the Y axis.
Thanks

Is the estop input debounced? (software or hardware)

A bare parallel port input will react to 20 or so ns noise spikes
These will occur only occasionally because the likelyhood
of the servo thread reading the input just an the moment of the
noise spike is unlikely. Motor drives make just these sorts of spikes.

Note that while an open switch wire with as resistive pullup will be susceptible
to capacitively coupled noise, a shorted switch wire will be susceptible
to inductively coupled noise.

I would check the routing of the estop wiring to make sure is is not anywhere
near the motor wiring.

If all else fails I would try a RC filter on the parallel port input pin (say 330 ohm and .1 uF at the parallel port itself)
or adding a hal debounce component to the ESTOP signal

Well, yes and no, not the same thing.
If the arrow on the X axis shows towards positive values, it is wrong, but if it shows towards negative then all is good.
From your ini file:Setting all those to 0 should work, but i never tried it without also removing limit switch inputs.
-
Some more info:
-you can have Y axis with limits as you have it now
-you can make a new config that has no limit switch on Y for use with rotary
-you need to move just the motor wires over to rotary.

That is interference, no matter how you put it, caused by:
- bad wiring,
- cross wiring,
- no ground,
- bad grounding,
- ground loops,
- bad power supply/s,
- dirty power supply (not physically)
-
A quick way to narrow down things is to use the halscope and watch the input parallel port pins, 4 at a time, for each port.