Advanced Search

Thanks, i installed a new linux

I upgraded to the development version and did the required config changes and copied over the new routines etc.

However the bug is still there. The stack trace has changed to another line but it seems to be the same error:

 

[qtpyvcp.widgets.input_widgets.gcode_text_edit][INFO]  File encoding: ascii (gcode_text_edit.py:538)
[qtpyvcp.widgets.display_widgets.vtk_backplot.vtk_backplot][INFO] 

---

Draw time 1.025238275527954 seconds --- (vtk_backplot.py:831)
[qtpyvcp.app.launcher][CRITICAL]  Unhandled exception in vtk_backplot.py line 917 (launcher.py:37)
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/qtpyvcp/widgets/display_widgets/vtk_backplot/vtk_backplot.py", line 917, in load_program
    point_01_pos = self.path_offset_start_point[prev_wcs_index]
                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^
KeyError: 1

This is the setup I'm probing.

 

I've tried probing the parts in different order etc but as soon as G56 finishes probing the error pop up. Now in the development version pressing the stop button after the error has appeared doesn't do anything instead the GUI mostly frozen for any user input however it still updates if I use my physical button for e-stop etc.

Could there be a typo somewhere relating to G56?

The THC voltage is raw cutting voltage. a THCAD can use this with the right scaling resistors. I would expect there are some resistors between these terminals and the cutting terminals to avoid lethal current! Check with a multimeter.

here the thcad manual is your friend. 200 V full scale will be best but 300v is also Ok

Its here, just add a negative sign, minus-sign, like below
 refClockSyncCycles="-5">
 

 Is synchronisation something that has to be set up on the PI or is it configured within the .xml file ? 
 

I can assist you remotely

Show ethercat-conf.xml, please.
You probably need to add synchronization with DC clock.

Current Setup:

• Raspberry Pi 5
  • 3 × Leadshine EL8 Servo Drives and 400W Motors
    
    Problem:
    I’ve recently set up LinuxCNC on a Raspberry Pi 5 and configured it to use the Probe Basic user interface.I’m experiencing an issue where the servo drives occasionally disconnect. The main symptom is that the motors sometimes make a “clonking” sound while running, as if there’s a mechanical fault and judder under movement . Power-cycling the system (turning it off and back on) sometimes clears the issue, and the motors then run normally.
    Could this problem be caused by poor latency on the Raspberry Pi 5, or possibly by the EtherCAT network going out of sync?Any advice or suggestions on how to resolve this issue would be greatly appreciated.
    
    

LCNC 2.9.6
tool_touch_0ff 6.0.0
ProbeBasic neuste Version

Werzeugtab nur 1 Werkzeug neu angelegt
tool_touch_0ff ich habe es auch mit der Version 0.3 Von Cris und Dir

Happy to hear that!
And to get feedback that the dkms driver really helps.

I haven't had a chance, honestly I don't think I could justify one ATM. The old tech budget has taken a beating already this year.
The Intel NICs sounds like a good idea.

If it's this one www.stahlwerk-schweissgeraete.de/plasmas...t70-pilotzuendung-en 
I would look at one that doesn't use HF start. You don't want HF start in cnc table.
Generally, blowback start is what you want.

I got pretty reasonable results on the RPi5 even with Wayland and LXDE.
Enough that software step generation might be an option for a mill. I was surprised by that.
I've had to go back to the basics with pi-gen, was having issues with it deciding to switch from the graphical target to multiuser.
I've got a bunch of images to test, so stay tuned.
But I think once this is nailed it will be easier to get reproducible results. You've convinced me regarding the kernels. So much easier. Thanks

Ok cool, git gets a bit over my head. I ain't real smart, but I used to lift heavy things .