Advanced Search

besriworld wrote:

At a later stage, I plan to add an additional 1kW servo motor, which will operate in torque mode to act as a dynamic load on the main 7kW motor. This will increase the system's rigidity. Currently, I'm using the encoder from the main motor
 

That sounds interesting.  How are you planning to couple the secondary motor to the spindle?

Are you sure the proximity switches are deactivated (red in halshow) when not at home position?

If these were inverted, the "home" move might actually be LinuxCNC backing off what it thinks is
a closed switch.

Kept looking last night and ran the IRQ script found else where on this forum.
This seemed to improve things, I left LCNC running all night with glxgears and other things running and did not get the messages again.

Ping result
cnc@minimill:~$ sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 60401ms
rtt min/avg/max/mdev = 0.056/0.084/7.709/0.139 ms

The issue maybe be fixed I'll see how we go actually using it today.

1. make sure both Y spin in the correct direction
2. what sensing distance do the proximity switches have? 1 and 2mm should be avoided. And switches are not mounted correctly, they should be sideways to prevent crashing into stuff.
For 1:
make a normal 3 axis test config, test one Y with a short jog, change drive inputs and test second Y with a short jog.
This can be done on software but more complicated to explain.

www.welectron.com/Motion-Controller

www.linuxcnc.org/docs/html/gcode/m-code.html#mcode:m68

See the note about the hal pin.

Looks like meister was using different numbers for different positions
some likely being fully open and some fully closed

Hi All

I have an issue with getting XYYZ gantry to home (using 7i92t with 7i76u)

Home position is at bottom left of the work area.

I am trying to use the second option,  of the four homing sequences,  found in Figure3. Homing Sequences. (stop, back, forward, home)

Order of homing is Z (micro switch), then X (micro switch),  then Y gantry (proximity sensor on both ends of gantry, Y and Y1).

The Z axis homes correctly.

The X axis homes correctly.

The Y gantry axis moves in the correct direction, towards the two proximity sensor stops.
The gantry stops for a spit second, as it find the proximity sensor stops.
The Y motor looks like it tries to begin to do the correct four step process (stop, back, forward, home), and it doesn’t ever crash.
However the Y1 motor side of the gantry, just continues straight forward, and crashes the machine every time, with a hammering sound.

Context:
The two switches, and both proximity sensors, provide +24v to the four inputs on the 7i76u.
in pncconf I had to invert the four inputs, otherwise all four inputs triggered before one began.
In halshow the switches and the proximity sensors all seem fine (to me).

I have negative values on all axis (see attached ini and hal), if I change these to positive, then it homes in the wrong direction.

Any ideas for troubleshooting greatly appreciated