Advanced Search

If I use the following code which has the one missing dash error that I corrected:

# estop
loadrt estop_latch
addf estop-latch.0 servo-thread
net estop-loopout iocontrol.0.emc-enable-in <= estop-latch.0.ok-out
net estop-loopin iocontrol.0.user-enable-out => estop-latch.0.ok-in
net estop-reset iocontrol.0.user-request-enable => estop-latch.0.reset
net remote-estop estop-latch.0.fault-in <= parport.0.pin-in-10-not

The bug-a-boo for me is how do I tie the GPIO25 to the remote-estop. Do I change the last line to:
net remote-estop estop-latch.0.fault-in <= hal_gpio.GPIO25-in-10-not

?

Most normal wiring would be:

FIELDA  +24V
FIELDB  +24V
VIN (unconnected)
W1 LEFT

 

Thanks for your answer! My tests are in aluminum EN-AW 5083. That is my target material.
Yes I know that a really stiff machine should be made of steel or cast, but I have bult what I could.

Hakan, thanks for your reply! Yes the 500 were the result of another contribution and the servo thread setting at 2 million.
See forum.linuxcnc.org/42-deutsch/55139-moto...4-7-5-m-min?start=20
There are other hints for FF1 and FF2 in the motor settings, even though there is no real feedback loop. I don't understand this in depth, but I follow those experts as tommylight and PCW.

Ahh, no discernible action when I hit SUBMIT the first time. I can wait it out in the future.

Come here first.

Too many times users have received info from chatgpt that make absolutely no sense.

Google searching for "linuxcnc estop latch" gives the link above as the 4th result.
Or you could use the search function of the forum.

Yes, I have a jaundiced view of ChatGPT but I try to exhaust my resources before coming here.
I will check the link.
If you would like to read the question as formatted, check here:

acrobat.adobe.com/id/urn:aaid:sc:VA6C2:0...f2-9441-faf83de82c31

Thanks.

There were 2 new threads submitted by yourself with the same heading.

I'm not sure what norm I have violated?

Undo everything ChatGPT suggests and never ever use it again for anything related to Linuxcnc.

Far better to visit this thread
forum.linuxcnc.org/47-hal-examples/25861-external-e-stop#26684

You may have to invert the estop signal, as when you press the estop you are providing a 0v signal. You may also need to check whether the inputs to the estop are tied hi or low when the Estop is pressed.

Thanks for your reply, Lcvette!
Okay, I think I have a (relative )rigid machine for a hobby CNC. All critical plates are made of 20mm 5083 aluminum, heavy profiles filled with cement, an 80x160mm filled portal profile, 20mm HGR guides. A good standard for  a 1000x500 machine.  I aligned everything using angles and a dial gauge. I placed a dial gauge on the end of the Y ball screw, which shows only 1/100 mm of backlash. Using a spring balance, I pulled with 20 kg on the spindle in the X and Y directions, with a maximum deflection of 0.06 mm, in the X less in the Y direction. I think the mechanics are OK, as this deviation of almost 0.5 mm cannot be explained.
Ok, You say, my settings are correct. What is the reason for motor alarms at the reduction of FERROR from 1.0 to 0.1 and MIN.FERROR from 0.1 to 0.01? 

Stop posting new topics with the same question and tittle.

My SetupRaspberry Pi 5 8GBByte2Bot Parallel Port Raspberry Pi HatByte2Bot 5 Axis CNC Interface Adapter Parallel Breakout Board For Stepper Motor DriversPicture 1My wiring is as follows:Picture2

The motors move, the home switches register as functioning, the probe is not hooked up and the eStop appears to do nothing.From LinuxCNC V2.9.7 Documentation PDF Page 1854.9.3.7 External ESTOP button The standard_pinout.hal file assumes no external ESTOP button. For more information on an external E-Stop see the estop_latch man page.Yet from 2 pages earlier in LinuxCNC V2.9.7 Documentation PDF Page 183 I see this line in the HAL file:# create a signal for the estop loopbacknet estop-loop iocontrol.0.user-enable-out iocontrol.0.emc-enable-in I assume “man page” is a typo and this is unnecessary if I am trying to connect it to  GPIO25. A search of the document looking for “estop_latch” only reveals this on page 254Picture 3So my estop is on pin10, but that is GPIO25 on the Pi 5. I must refer to it as such.In my .Hal file I have the following lines:loadrt hal_gpio inputs=GPIO7,GPIO8,GPIO25,GPIO12,GPIO13 outputs=GPIO5,GPIO6,GPIO11,GPIO9,GPIO10,GPIO23,GPIO16,GPIO17,GPIO19,GPIO20,GPIO21,GPIO22,GPIO24,GPIO26net estop-out   <= hal_gpio.GPIO25-in  ornet estop-ext <= hal_gpio.GPIO25-in Using tools I can identify that all my limit switches are being read, but I have nothing to suggest the estop is being read.I have added“Addf gpio-input servo-thread” as recommended by ChatGPT, and that is not read by the programThe advice I am looking for is:
I would like to know how to connect GPIO25 to LinuxCNC’s E-Stop chain.I have tried:

net estop-out hal_GPIO.GPIO25.out => iocontrol.0.emc-enable-inand any variation thereof I could think of, failed.Eventually, I lost control of my servos and only when I removed all lines I gained control of F1, which controls the estop and F2, which powers the servos. 

I'm hooking a 7i84u to a 7i96s and I'm unsure about the power for the 7i84u
From what I understand reading the manual (page 2) there is an onboard switching power supply that will take FIELDB voltage down to logic level if W1 jumper is in the left hand position. So I can supply 24v to FIELDB and it's not going to hurt anything.
Or is that only if I was using 5V FIELD and anything above that I should be using a separate supply for VIN?

Also, from what I understand 
Both field A and field B need to be powered regardless. I've hooked my 24v power (same that is being used on the 7i96s field) to one of the grounds (pin 8) and into pin 1 (VFIELDB) and then a jumper from pin 2 (VFIELDB) into pin 3 (VFIELDA) so they are both powered with 24v.

Right now I've got a 5v line coming over from the same supply that I use for the 7i96s into pin 5 (VIN) and the W1 jumper in the right hand position. That seems to work, I have a flashing green light (CR6 activity) and I can see changes on hm2_7i96s.0.7i84.0.0.imput-00 in HALshow if I power pin0 TB3 (either with 5c or 24v)

Before I let out the magic smoke....
Thanks
M
 

Thanks for all info so far.
I decided to change the Y-axis also with a M4-(screw) spindle drive (not M3 as I said before), as I did on the X-axis.
Had the (almost) same stepper-motor around, although after testing it needed 2 times more Volt to be powerful enough.
Now it all looks much better!
The old gear setup was too much worn out, I believe. And 2 (plastic) gears before driving the arm had 1.3 mm backlash is also kinda 'too much'.

PS. I thought I tried the write action at last position in the .hal file (base-thread), but was forgotten to change the .ini file accordingly.
It does run fine now and I am not (willing) able to build back the old situation to test this again, sorry for that.

And yes, I will cleanup my configuration files after this change, the X- and Y-axis are now the same.

Regards, DG.