Advanced Search

langdons wrote:

Is dist-upgrade ever a good idea?

WHen I first started, it was never a good idea and we were warned not to do it. I might add after compiling the preempt_rt from source nobody wanted to run the risk of breaking things. Now we have made it all too easy and people keep wanting the latest and greatest which is not necessary on a CNC machine. But on a office desktop keep it updated.

Now it works properly, thanks.

These are all signs of tthe larickin  Aussie who is long since lost to political correctness. Sadly he is no longer seen as funny. What we laughed at is no longer appreciated as everything is so serious today. We have lost the ability to laugh at ourselves.

The original intent from the contributing user islander261 was that ohmic test was used before starting a cut to check there was no rubbish in the nozzle that could cause an issue. I only ever found a bit of slag in the tip once, but this test saw it.

sudo apt upgrade should upgrade to  the latest Ethercat package as its not linked to the Linuxcnc version

kjlty wrote:

How to install the latest linuxcnc-ethercat on Debian 10 (lcnc2.94)?

Upgrade to Debian 12

Wifi has always been problematic for Linux. Google enough and you should find a driver for your hardware to compile. The newer the Linux version, the more likelihood it will work out of the box. I would try Debian Trixie but we don't have an ISO for it. But it should include v 2.9.4 when released in its repos

mjoconr wrote:

There is an issue with the ISO for Intel hardware, the package "raspi-firmware" is installed, suggest everyone remove this before running dist-upgrade.

Blame Debian.

We suppress it but if you do an upgrade it comes back. A known bug in Debian 12.1 initial release of bookworm, fixed in 12.2 but not in the Debian builder. Very poor form I think.

@andypugh: I checked the coupler, didn't observe any slipping. I too believe that its unlikely to be some encoder issue.

@PCW: I tested with encoder filter on. Still facing the same issue.

My mechanical setup is,

Servo Motor -> Coupler -> BK15 (Two angular contact ball bearing (Back tot Back configuration) with a shim spacer in between ) -> Ball screw -> Ball nut -> Deep groove ball bearing

I doubt whether the issue is due to the ball bearing. I have an electronics background and am just getting started in the mechanical field.
 

avec plaisir 
comment je peux te contacter?

This is a limitation of python/linuxcnc.
The properties signal is produced in the qt_graphics widget.
The receiving widget must be in the same python instance as the qt_graphics widget.
A stand alone panel is a different instance of python then the main screen.

You could add a qt_graphics widget to your stand alone panel.
Or possibly could try using ZMQ messages with a customized handlerfile.

Hi, can it be run on Linux?

Ok try the latest please.

Yes, this definitely seems like a bug.

I can see the cut starting at a different place at different spindle
speeds due to the time needed to get synched to the spindle
varying at different spindle speeds, _but_ once synced and cutting,
the threads should be identical regardless of spindle speed...

(as they are in a normal manual lathe than maintains strict gearing
between the spindle angular position and Z offset)

How does a person manage to lift 2" thick steel?