THC - out of ideas

Check the THC enable button is enabled in the GUI. IF it is, sounds like you are missing a pin connection somewhere.
Slow down on corners is expected and unavoidable due to laws of physics.
There are settings to disable the THC on a velocity slowdown.

Hey Rod - yep thc is enabled on the gui.

Any idea what pin i'm missing? Perhaps i should just do a complete reinstall of linuxcnc and qtplasmac and use the config wizards and hope that fixes it.

Yep that was my understanding too. It can only accelerate at a limited rate, it can't go from 100-0-100 in different directions instantly.

Thank you.

Sam

Hi guys - trying to do update now.

Ive done sudo apt-update and sudo apt dist-upgrade with no problems

I have then uninstalled all linuxcnc in synaptic package manager.

I have then set my repositories to  deb and deb-src buildbot.linuxcnc.org/ buster master-rtpreempt 

I then reload and have options of linuxcnc packages to install, however i get a whole host of depends: errors and cannot reinstall a package.

I have tried uspace, uspace-dbgsym, uspace-dev and none of them will install

Are the repositories not working at the moment or have i done some other cock-up?

Thanks
Sam

 

Well if you want to go with the bleeding edge, you can install linuxcnc from the debian repositories as follows:
open a terminal
Note that changes using unstable should be replaced with testing (Debian 12 Bookworm) when Linuxcnc gets there (soon)

I tested this out last night and it was flawless.
I started with Debian Bullseye.
I was also able to install the ethercat master from another repo but that's another story!
Tested as working on my ethercat machine.
I figured that with the controls Debian has around code entering their repos, the risk from having issues with the unstable branch is minimal

will the debian build in the debian repositories become outdated over time?

I know that some stuff such as I think XFCE tend to run a version behind in the repositories. "bleeding edge" is running from git clone whether RIP / local deb build + install as there is no guarantee it will work every time you update which is the essence of a development version..... sometimes it works and sometimes not.

Okay guys, I'm back.

Thanks for all the advice. I am now on debian 11.2 and QTplasmaC is updated to the Version v1.221.165.


I have rebuilt my configs, just going through the initial tests. I can happily home all axes, I can pulse the torch (to which arc voltage is then visible on the gui).

I can probe test, but as soon as the float switch is activated linuxCNC crashes and i get the following error message:
 
Traceback (most recent call last):
File "/usr/share/qtvcp/screens/qtplasmac_4x3/qtplasmac_4x3_handler.py", line 2321, in <lambda>
self.w.led_float_switch.hal_pin.value_changed.connect(lambda v:self.jog_inhibit_changed(v, 'float switch'))
File "/usr/share/qtvcp/screens/qtplasmac_4x3/qtplasmac_4x3_handler.py", line 1901, in jog_inhibit_changed
if self.isJogging[axis]:
KeyError: 3

I can hit retry but then the same thing happens again. Initially my float switch was inverted, and always on. But having added -not to the input it now works as it should, the LED lighting up only when it is activated.

Any ideas peeps? thanks so much in advance,

Sam