Advanced Search

There are also raspberry packages now:
multixmedia.org/debian-packages/

There are two ways to do this. You can either run an external latch (which is a momentary switch) that resets the safety relay. In this case, you should connect a signal to a Linuxcnc input which is connected in hal to iocontrol.0.emc-enable-in This is the approach I took.
 
There is no need to press anything in Linuxcnc

The other way is to  use iocontrol.0.user-request-enable instead of your external latch. Linuxcnc sends a pulse on this signal to act as the latch when the on screen estop is reset (S34 in the diagram).
When I researched this, this was compliant provided you isolated Linuxcnc (your controller) with redundant relays (K3 & K4). These needed to be force guided relays where a non conducting pin is forced between the contacts when they are triggered to ensure the contacts cannot become welded closed.

It's good that you used a safety relay with a timer in it can retain control until motion stops.

 

On the lathe, I decided to use macro commands when changing tools: Т№M6 G43.
I have 10 instruments in total. I decided to bind these commands to xhc-hb04. I came across the fact that the macro3 macro4 macro8 buttons do not work, although the commands were written in the ini file. In the hal file responsible for the operation of mpg, I saw that these buttons are reserved.
Is it possible to somehow remove/exclude the default spindle control or change the hal file so that macros become active (Fn+macro3/macro4/macro8)?

p.s.
translated and voiced by Google translator

Ha e you tried just setting it up in hal as an estop?

I have a simple estop button to LinuxCNC and when I reset the button LinuxCNC comes out of estop.
I still have to hit "power on" on LinuxCNC after reseting estop. This is generally recommended behaviour

Reseting estop should never result in immediate motion

Its very unlikely to be a card issue.

Try the ping command in the previous post to see what the Ethernet latency is.

You also have to disable basically all power management/speed shifting/
turbo modes etc in the PC BIOS

Finally, using isolcpus and pinning the Ethernet to the last CPU can help a lot

If you have isolcpus setup in the kernel command line, you can temporarily
pin the Ethernet IRQ with this script:

 

and check that its done the expected thing with this script:

 






 

Did you use linuxcnc-HAL radio/check buttons?

Yes, Pushed.

Looks like I made a spelling mistake, so it's under a different heading (missing hyphen).

[VERSA_PROBE OPTIONS]
ps_probe_tool = 0

I'll fix that soon.

Chris

For this:
forum.linuxcnc.org/additive-manufacturin...here?start=20#304779

ONLY one of the below, not both!
Here are the STL files on Printables, versions for 6mm belt on XY
www.printables.com/model/945595-voron-24...near-rods-round-rods
Version for 9mm belts on XY
www.printables.com/model/945612-voron-24...-rods-round-rods-9mm
-
AND the Z axis stuff
www.printables.com/model/945618-voron-24...r-rod-mounts-and-car

Seems very easy to use, thank you.

Hi JT,

Unfortunately Im not a programmer so I cant help you there but don't you create the file last when you hit save? Aren't all the items you enter placeholders for options that have been selected which will be saved into the file.

Only other suggestion I have is reorder the contents of the tabs so the workflow order is from top to bottom of the tab. IE; picking the default units would be the first item in the Machine Tab, then select Mesa card, then test card,

I have added radiobuttons and checkboxes from qtdesigner
the radiobuttons and checkboxes shown in gui but no hal pins.
How can create the hal pins for radiobuttons ?

Sounds like you've got a solid plan.  Can't wait to see it.

Sorry I have not been able to get back to these diagnostics. I tried another type of mini PC with the same failed results. I tried the driver update and kernel parameters from Rod's docs (all the mini pcs were RTL8111 ethernet chipsets), then I used a regular fairly old desktop which ran for much longer but eventually encountered the same issue.

I'm going to order another 7i92T to see if there is potentially a problem with the card itself,

I did at one point flash this with the Path Pilot 7i92T firmware as a part of a previous experiment running Path Pilot on the mini PC, but flashed it to the 7i92t_g540d firmware before all of this. I don't know if anything can persist from the Path Pilot flash process.

Thanks,

Scott

  Oh I agree and the eventual goal is to run linuxcnc on it . For now I am just seeing how far I can
push simple hardware. The end goal will be a 7i96 because I have 2 in my inventory but the newer
S version would work just as well. I don't think MESA makes a cheaper 5 axis ethernet board
then the 7i96S.
as far as free wing design software I use this
www.diyrcwings.com/app/