I’ve just updated, and now the screen displays correctly. The arrows seem to respond properly, but none of the conversational macros work—or maybe I’m doing something wrong when entering the values in the fields, although it doesn’t work in simulation either. I’m attaching a screenshot.The default RPM the spindle should run at when I press the Forward button still isn’t working.

By the way, I’m not sure if I mentioned it, but I’m on the dev branch.

1920x1080

I've been busy doing a complete rewrite of the core motion control libraries of linuxcnc to fix some pretty vig structural issues. In the mean time I've decided to buy a ised working CNC cam grinder

grandixximo wrote:

New PR from YangYang is ready, hopefully will be merged soon in master

This adds ruckig in the planner type 1
if you want to test it get the binary from

github.com/LinuxCNC/linuxcnc/actions/runs/21975584400

or build source from my repo

github.com/grandixximo/linuxcnc

Testers are welcome to report here or in github, thanks!
 

Hello gentlemen,

movement are incredible smooth ... basic shaping what I have tested till now is pretty ... but during movement at more points during simulation of rotation interpolation its jumping or woobing ... kind off braking and next accelleration 

most spiking during cloud of points are gone ... some spiking are still present but it a huuuuge step forward 

testing setup 2ms benchtop profibus master 3axis geany gui ... 3 servo axis with synchronized speed control loop at 2ms

some testing fault popups triggered during the movement of file 3_1001.ngc

I am still testing at default simulation file from past but splitted to separated operations ..

thanks a lot for your progress ... I am watching it every single day with mount open and box of popcorn to reading the edits ... 

regards E.

Please share min and max values calculation formulas for capacitive sense velocity for the optimum up and low signals for the fiber laser cutter. Eg to set up 100 volts 100/(fmax-fmin) for arc volt scale. Please correct if i am interpreting it wrong.

As soon as the limit switch moves to the cam, the axis stops, and after a few seconds, an error message appears. The X, Y, and Z home contacts are displayed correctly.

What error message?

Do the drives have any direct connection to the limit/home switches?
(some systems disable the drives directly when limits are reached)

Can you do a halscope plot of the say X position and X home switch state while homing?


 

Hello, i updatet my LinuxCNC and Probe Basic to the latest Version and edited my config and copied the files and folders to my config folder. Everything works fine expect of the tool setter settings.When i jog to the tool setter position and click on "SET TOOL TOUCH OFF POS" the X value will be set but the Y value is 0. What can be the problem here?

this is a really old ui for qtpyvcp from JT, it may no longer be compatible as it likely did not get updated and tested when we moved to python3 and I think JT has moved on to flexgui, may want o see what he has there if that is your style flavor preference.

ok i found the resolution issue again it was another rogue widget with an expanding policy. I have capped max height for all tab widget pages now so that shoud never happen again and the height will display correctly . I am getting ready to push the latest changes.

as for buttons working im not sure, the machine must be out of estop (estop button showing red is out of estop ( so its easy to find if you need to hit it).

power button must be on Green lit

and the machine must be homed in order for buttons to be available in the sim

report back on those.

This was a complete new install from ISO, wasn't it?
Did you install the r8168-dkms driver again?
 

Thanks for your feedback.

The last time the machine was running (the video is a few pages back), I only updated the firmware of the 7I97, from Debian10 to Debian13, and the LinuxCNC software. There were no changes to the wiring, hardware, or the HAL/INI files.

In any case, the handwheel on the machine works, for example.

However, there's still a problem with the homing function, and that also worked the last time the machine was running. The Z-axis moves correctly. The limit switch moves to the cam and then releases itself, reporting a successful homing. Unfortunately, this isn't the case with the X and Y axes. As soon as the limit switch moves to the cam, the axis stops, and after a few seconds, an error message appears. The X, Y, and Z home contacts are displayed correctly.

I then tried manually homing the X and Y axes. I manually pressed the switch, and the machine recognized the command and performed the referencing by moving freely and reporting a successful referencing.

The settings for all three axes are the same; you can see them in my latest .ini file.

Does anyone have any other suggestions?

Hi All

Thanks for the help with this. But I am truly stuck up in calculation of the below.: 22900 and 23900 & 930000.0
 If the head is away I am getting a safe value of about 24000 for capacitive-sense-velocity in the halshow
My hm2_7c81.0.encoder.00.velocity-rpm is about 1440000 in the halshow.

When i run my program, the IHS happens perfectly but when the the THC takes control the torch just gets the down signal and never goes up. Kindly help with any formulas with these three parameters. Thanks!

# Configure a limit component for the capacitive sensor output since it is scaled
loadrt limit1
addf limit1.0 servo-thread
net capacitive-sense-velocity limit1.0.in
setp limit1.0.min 22900
setp limit1.0.max 23900
# hook up the limited signal to the plasmac arc voltage
net plasmac:arc-voltage-in <= limit1.0.out

and 

# Make a fake Ohmic probe based on the capacitive sensor
# Use the .velocity-rpm so the .velocity can be left unused for arc_ok
loadrt comp count=1
addf comp.0 servo-thread
net fake-ohmic-probe-in hm2_7c81.0.encoder.00.velocity-rpm comp.0.in0
setp comp.0.in1 930000.0
net plasmac:ohmic-probe comp.0.out
# ohmic output is comp.0.out