Advanced Search

Hi Pier,

I just googled " 4 axis foam cutter Linuxcnc" and found a couple of example using " X Y U V " axis. ABC are angular axis and according to this post , they are always treated as angular.

I'd start with that.

Cheers,
Luca

So I checked and my lathe is running Lcnc 2.8.2 on Debian Buster, with RT 4.19.

Since Buster is still okay per the updating instructions, I thought Id try an update.

 
I added the repository.
 

but get errors

 

...

 

 I attached the full error log.
Does this mean Buster can no longer be updated?
Cheers,
Mark
 

Bumping an old thread. Does anyone know if the g37 & g37.x macros from Pathpilot  can be used in LinuxCNC and if the code is available?

For those with large, conventional autochangers and fixed tool holders running production parts, I can see how this workflow seems forgien. However,for everyone using a manual change spindle and adjustable tool holders/collets, probing a tool length setter after each M6 is common. It is quicker than running a single toolpath per job and reduces the risk of collision due to operator error, i.e forgetting to manually update your WCS Z zero for each tool.

The UI looks fine and exporting tool wear/runtime data in a .csv file is operationally quite useful in a production shop. However, what is the use case for adding tool geometry and cutting data in LinuxCNC? I can see it being useful if the intention is to go deep into adding conversational CAM features, but that's it. With the latter, you'd also want to consider attaching a dxf for each cutter profile.

Honestly, synchronizing tooling parameters (what you might call metadata?) between different CAM software is a huge pain. Handling multiple machines, materials, cutter geometries is actually a deep rabbit hole. In practice, feeds and speeds are job-specific. For the controller, I populate the tool number, tool diameter, tool length, and description. That's it. I address everything else in CAM or directly or when writing the g-code.

With regards to tool databases and github.com/loobric/smooth-core. Neither Fusion (zipped json files) nor Vectric (now an sqlite3 file) define their tool database specification so they are always subject to change. According to their software license, they are proprietary. I've written python scripts for managing my library of tools within both but they do break with updates. I'd love to see this improve with a common specification/format being adopted, but I don't see the business case for any CAM software company. Ultimately, why make it easier for users to switch CAM software?

Thank you so much ! Exactly what I need.

Compaq? So that is roughly 15-20 years old, giving two possible issues:
-an NVIDIA add on graphic card
-one of the Intel 915 graphic cards built in the chipset
The first is easy, just yank out the card and use the onboard graphic...that might be the 915 and has issues with Linux and was fully blacklisted at one point in time.
Still, there are options:
-power on the PC
-hold down the right side SHIFT key till you see the GRUB menu
-press E to enter editing the boot options
-there should be "quiet splash" on one of the lines, add "nomodeset" after the quiet or splash
-press F10 to boot
Does that work?

The last error message (whilst I was sorting out the copying of stuff into the .ini file - not getting any at present) had this:

Traceback File "/usr/lib/python3/dist-packages/qtpyvcp/plugins/notifications.py", in timerEvent error = self.error_channel.poll() ^^^^^^^^^^^^^^^^^^^^^^^^^ linuxcnc.error: Error buffer invalid

... not sure if any relevance.

All secondary pin function channels are numbered 0..N
(the primary function of each pin is GPIO)

 So if you have 6 stepgens, they would be numbered 0 to 5.
And if you had 2 PWM generators or encoders  they would be numbered 0 to 1.
 

There is no software support package for the 7I89,as it is a passive daughtercard.

Here is firmware for a 7I96S with a 7I89 on  P1:

 

PktUART (V3) on the 7I96s and SSerial channel 0 on the 7I89.
 

$ qtpyvcp -i

QtPyVCP Info
Version: 5.1.0+14.gba8f741e

LinuxCNC Info
Version: 2.9.8

Qt Info
Qt Version: 5.15.8
Qt API: PyQt5
Qt API Version: 5.15.9

System Info
Description: Debian GNU/Linux 12 (bookworm)

Kernel: 6.1.0-30-rt-amd64
Version: #1 SMP PREEMPT_RT Debian 6.1.124-1 (2025-01-12)
Ram: 7 GB

CPU Info
Vendor ID: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
Architecture:
Physical Cores: 4
Logical Cores: 8

@grandixximo 
Unfortunately, the Jitter/Clunking came back, even though dc-phased is on. 

If the Num column indicates channel if the numbers are one digit long, and the pins associated with the 0 channel are for the x-axis, why is the PWM signal for the spindle and associated encoders also on channel 0 in this screenshot of the PcCConf wizard?

Hi everyone,The download link for the 7i89 firmware/support package on the Mesa website appears to be broken, and I couldn’t find any information about a firmware variant that includes pktuart, and I couldn't find one in the 7i96s package. Would it be possible to make a firmware for 7i96S with 7i89 connected on P1, pktuart enabled (for VFD/Modbus use) on the 7i96s ?  Thanks a lot,
tar

I have now gotten the tool changer working mechanically and electrically tied in with LinuxCNC. 


Next step is to set up the carousel comp. Since my lathe is still running 2.8.2, and I never updated it, the version of Carausel.comp will still be the one with the bugs identified here...
www.forum.linuxcnc.org/10-advanced-confi...carousel-toolchanger

I see three options.
1/ patch the carousel I have and recompile it
2/ download the current carousel.comp from github and compile it.
3/ upgrade my full installation from 2.8.2 to 2.9.8, and then the current carousel will already be covered.

linuxcnc.org/docs/html/getting-started/updating-linuxcnc.html
I read the wiki that it is recommended to do a clean install, but I am hestitant to do that with a working system. Wish me luck.
Cheers,
Mark
 

Hi smc.collins,

Hello smc.collins,
As an occasional user of FreeCAD, I feel exactly the same way. The topology problem isn’t intuitive to grasp. These issues also existed—and still exist—in the professional CAD software “Catia V5”! But the software handles them differently. It shows me which references are incorrect or no longer exist. FreeCAD doesn’t do that yet. Mango Jelly has uploaded a video to YouTube that gives us users a better understanding and shows a way out of the topology problem traps. I also wonder what the topology problem has to do with CAM... 
Solidworks and MasterCam is an exellent Combination.