Advanced Search

--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 60420ms
rtt min/avg/max/mdev = 0.057/0.276/16.993/0.227 ms, pipe 2

OK that (almost 17 ms) is the issue.

Depending on the Ethernet hardware on the host, solutions are:

If it's a Realtek MAC, install the DKMS driver

Disable PCIE/Ethernet power management

Make sure all power management is disabled in the BIOS
It that's not good enough, pin the Ethernet IRQ to the last processor
and use isolcpus in the kernel command line.

Here's a long  thread on solutions to this issue:

forum.linuxcnc.org/18-computer/56380-error-finishing-read-sigh
 

--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 60420ms
rtt min/avg/max/mdev = 0.057/0.276/16.993/0.227 ms, pipe 2

OK, so there is a real time issue that needs to be addressed
before LinuxCNC will run on that system.

To get a rough idea of network latency:

sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10

This will run for a minute and then print statistics.

Manual for this machine is online:

veracitytechs.com/docs/MicroEDGE%20Pro%2...018%20Feb%202016.pdf

Linuxcnc is running, the light on the rj45 stays solid green and the lights on the board stay solid without any activity.   

The THCAD support was added to pncconf about 3 years ago so definitely in 2.9.4

The THCAD screen should appear on the next screen after the one where
you set the stepgen/encoder functions.

he vuelto a instalar linuxcnc ultima version estable y nada sigue sin darme la option del thc
porque¿

The search velocity is the speed when searching for the first
home switch actuation, the latch velocity is the velocity used
for for the actual homing switch/index move so only the latching
velocity is needed in this case.

Basically, Index-only homing is specified by setting the search
velocity to 0. (as the homing documentation specifies)

Seems to be a commonly found issue, HP support forums discuss this quite a bit with various cards.
Might be an idea to google your issue, TLP poisoned, and see if there are any solutions. I wouldn't mention a specific card in your searches to begin with.
My first thought was if the card wasn't on a "whitelist" the PC may refuse to play ball .

7I76U inputs are always sinking so normal connection would be:

+24V --> SWITCH --> 7I76U input

If you look in halshow, hm2_5i25.0.7i76.0.0.input-07 will always be
in the opposite state as hm2_5i25.0.7i76.0.0.input-07-not, so choosing
one or the other should make a difference.

Well, that didn't work. Inputs are back to sinking inputs as specified in the manual. I did comment out the PROBE input so it is not currently part of the configuration. However, on startup LCNC continues to show the EStop button activated so I cannot continue testing Homing.

Unable to continue at testing at this point.

These are the states of the inputs at this time:

 

And this is my HAL config:

 

Any help would be greatly appreciated.

ok, I understood that, but how will my axis move if I don't give any speed? it will never detect my plus Z. I can't understand the logic ☺

If there was no communication, LinuxCNC should exit.

Are you saying LinuxCNC is running but you have no activity light
(green LED on 7I92 RJ45)?

What does:

ip a

report when in this state?

Hallo Herr Jansen,

ich habe Ihnen unter This email address is being protected from spambots. You need JavaScript enabled to view it. eine E-Mail gesendet.

Mfg Mario Gnad

Hello, I want to use QtDragon to determine the tool height using Utils - Workpiece and then save the result so that I can access the value in the G-code. My idea was to save the result to a file, which also works by slightly modifying the auto_height.py file. I added the following line:

def show_result(self, data):
        diff = float(data) - float(data)
        self.lineEdit_height.setText(format(diff, '.3f'))
        # New line by me:
        with open('/home/dg/linuxcnc/nc_files/probe_height.txt', 'w') as f: f.write(str(diff))

But how can I access the value stored in the probe_height file in a measurement routine.ngc, or can I save the measured value directly in
the G-coder as a variable, e.g., #5000