Advanced Search

Hi Tim,

sorry for that, is now fixed in 'main' branch

52 IPS sounds really fast, what kind of machine is this?

If the external resistor value is correct (2.4M) that's not
possible. It may be that there is enough RFI/EMI that
the voltmeter is malfunctioning.

Not sure why you are getting dropped packets, might be hardware related
though the NUC didn't drop packets. 

One line of thought, not the only one for sure, is to run the servo without a linuxcnc control loop. The drive tuning is what determines the precision.

There is unfortunately a delay in the linuxcnc Ethercat loop of one or two cycles, I think two.
So the actual position is old already. At high travel speeds the following error can be two cycles times multiplied by the speed off.
Without it being wrong in any way, just by delays.

New Version on the way - now the chance to work in your comments...

github.com/LinuxCNC/linuxcnc/pull/3494

Ahora otra pregunta yo mido con un multimetro la salida del plasma la que va al thc lo mido en DC y me da mas de 600V que es en maximo de mi multimetro asi que no se cuanto exactamente, tengo una resistencia de 2,4 mohm en serie en el “negativo” si mido después de la resistencia me da 104V.

Que tengo que hacer?

No.
to write to a pin you made in qtdragon handler depends on how you made a reference to it.
for instance if you created the pin like this:
self.myPin = QHAL.newpin("MyPin", QHAL.HAL_BIT, QHAL.HAL_OUT)

then you could use:
self.myPin.set(True)

or it you didn't keep a reference to the pin (the 'self.myPin' part)
self.h.myPin.set(True)

To write to a system pin directly (it can't be connected to anything)
QHAL.setp('qtdragon.myPin','1')

or
self.h.hal.set_p("qtdragon.myPin","1")

Topic separated, finally.
@JackRay,
Please refrain from tainting existing topics with unrelated content, start a new topic next time.
Thank you.

Dear meister：
 when I updated RIO, I got error:

riocomp.c: In function ‘register_signals’:
riocomp.c:692:52: error: ‘data_t’ has no member named ‘SIGIN_QUADENCODERZ0_INDEXOUT_INDEX_RESET’; did you mean ‘SIGIN_QUADENCODERZ0_INDEXOUT_not’?
  692 |     if (retval = hal_pin_bit_newf(HAL_OUT, &(data->SIGIN_QUADENCODERZ0_INDEXOUT_INDEX_RESET), comp_id, "%s.quadencoderz0.indexout-reset", prefix) != 0) error_handler(retval);
      |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                    SIGIN_QUADENCODERZ0_INDEXOUT_not
riocomp.c:694:52: error: ‘data_t’ has no member named ‘SIGIN_QUADENCODERZ0_INDEXOUT_INDEX_WAIT’; did you mean ‘SIGIN_QUADENCODERZ0_INDEXOUT_not’?
  694 |     if (retval = hal_pin_bit_newf(HAL_OUT, &(data->SIGIN_QUADENCODERZ0_INDEXOUT_INDEX_WAIT), comp_id, "%s.quadencoderz0.indexout-wait", prefix) != 0) error_handler(retval);
      |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                                                    SIGIN_QUADENCODERZ0_INDEXOUT_not


Tim
 

Moved and separated
-
Do NOT post random stuff here. Thank you.

Can you:

1. Post your current hal and ini files

2. When homing B use halshow to watch joint.3.index-enable
and report it's behavior

joint.3.index-enable should get set true (yellow) when B homing starts
and get cleared at the index

Hallo ich habe wieder einen Fehler, anderer Rechner AMD 3500
Mit Realtec Chipsatz, DKMS Treiber installiert. Ehternet Verbindung steigt mitten im Programm aus. Was kann ich noch tun

60000 packets transmitted, 59995 received, +5 errors, 0.00833333% packet loss, time 60033ms
rtt min/avg/max/mdev = 0.052/0.106/0.265/0.030 ms, pipe 2

Remora/Ec500 now running a Denford Triac Mill. Homing/limits/emergency stop/axis and spindle sorted. Need a relay to wire in the coolant pump.

I originally had this running on a cheap eBay BOB using the denford drivers. When I switched over to the EC500 I could not get the driver working correctly with the EC500. After many attempts with different IC and board configurations I gave up trying to use the denford drivers and bought DM556T drivers. Still on the denfords motors.

Monitor is a cheap Amazon touchscreen, worked without any messing around.

finding a thread from like 2023, it looks like what I am seeing is processing delay between ethercat and where LinuxCNC thinks things should be... The actual servo error rate (according to its software's scope) is less than 4 steps out of 1280 steps per mm)..

I did some napkin math and 5mm ferror suggests a processing delay of .0083 seconds. Does that sound reasonable or should I be looking somewhere to bring that delay down?

Thanks