Advanced Search

I don't exactly know how it would, but there could be an explanation if the override is constantly dithering. Maybe as the python is updating the override it misses a message back from the probe routine. The probe routine and the screen sends messages back and forth at start and finish of probing.

If you run in debug mode (DISPLAY = qtvcp -d qtdragon) and run linuxcnc from a terminal, we maybe able to see the difference in commands

There are some instructions here:

forum.linuxcnc.org/9-installing-linuxcnc...dware-eg-realtek-nic
 

I need search and compile him or only apt-get?

the answer is simple,
GRBL,... is a firmware for CNC milling machines, laser cutters and the like.

LinuxCNC is a highly configurable motion control platform,
it can synchronize all kinds of input and output devices,
also from external not self-controlled movements.

It can handle all kinds of actuators, not only step/dir or RC servos. It can handle all kinds of protocols like Ethercat, CAN, Modbus, .... and even mixed.

It can handle
all kinds of inputs, glass scales, encoders, camera images, .....

It also doesn't need gCode as input, that's just another module in the chain


So if you want to operate a simple hobby CNC, you are well served with GRBL and so on, for everything else LinuxCNC is the best choice.

rtt min/avg/max/mdev = 0.158/0.255/4.918/0.225 ms

Yeah, ~ 5 ms will be an issue

What is the Ethernet hardware?

If Realtek you likely need to install the DKMS driver

Please , i want understand :

If remain refclocksynccycles = -1 in xml file, can have some problem on real machine ?

ping -c 4 -i .2 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=255 time=0.295 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=255 time=0.416 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=255 time=0.278 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=255 time=0.425 ms

--- 10.10.10.10 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 612ms
rtt min/avg/max/mdev = 0.278/0.353/0.425/0.067 ms


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, 59999 received, 0.00166667% packet loss, time 60751ms
rtt min/avg/max/mdev = 0.158/0.255/4.918/0.225 ms

I have a feeling the way I'm trying to wire my end and home min stops is the prob(use to 3d printers) but I redid the pnconfig using discover board and now the endstops don't stop me from turning the machin on in linuxcnc so I'm slowly getting there

No, just the statistics reported at the end of:

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

The last command will run for 1 minute


 

Hello,

I'm trying to set up an EC500 board with Remora firmware, but I'm encountering an issue.
I successfully flashed the latest BIN file to the MCU (using DAPLink, PyOCD, etc.).
Then, I tried to upload the DMA-based stepgen configuration (), but Remora reports:My Python version is 3.11.2

Here is the upload log:
And this is the serial port response:Has anyone encountered this issue before?
What am I doing wrong?Thanks in advance!

PCW wrote:

What was the result of the ping command?

 

You need result of all 40000000?

Typically you just have one track of holes and the B detector offset from the A detector by
hole_pitch*(N+1/4). That is, if the holes were 2 mm apart, the A/B detectors would be
spaced .50 MM or 2.50 mm or 4.50 mm etc.

This 1/4 pitch offset gives you the desired 90 degree phase difference between A and B.
Note the when drilling holes you should aim for a 50% duty cycle waveform
on A and B. This may require some experimentation and changing  the sensors
radial positions.

Why if i put in spindle shaft an aluminum disk with 2x100 holes(pi/2 equally spaced for A- and 1 hole for index drilled on the same mill?
I think i can do holes 1-1.5mm in the same mill accurately.

What was the result of the ping command?
 

If you can get LInuxCNC running, I would first verify the home switch operation
with halshow.