Advanced Search

Awesome! Thanks TurBoss!

You need to turn off all screen saver and power saving modes.

Qtvcp is much better documented on the Linuxcnc web site. The qtdragon GUI is very good.

The GUI's typpically don't use C++ but the real time side of linuxcnc (Components and core code) is based on C. Some parts are in C++ but the core code predates C++

TangentAudio wrote:

rodw wrote:

I would rather buy an industrial wireless pendant/MPG for similar money.
 

This is another topic, but those wireless MPG's have never seemed like a great idea to me.  They look convenient, especially for large routers or plasma tables, but potentially fraught with peril.  How robust is the wireless protocol, and how exactly does it behave with potential interruptions/interference?  I definitely sleep better using hard-wired controls for potentially dangerous and expensive CNC machines. 

I saw one with an mushroom E-Stop on it, which seemed optimistic at best.  I don't think that would pass any sort of safety system design review.  It could be designed to fail safe if the wireless link drops out, but then if you had a brief interruption of the wireless link, your whole system would go into E-Stop and potentially ruin work or tools.  If it's more tolerant of wireless dropouts, then it no longer is truly safe as an E-Stop.

 

I would much rather have a dumptruck hardwired operating in real time than a Ferrari dependent on a USB connection!
I belive the 433 MhZ pendants I use are compliant and include a dual circuit estop. Here is the receiver. I have used one for 7-8 years and it never let me down.

 

 
 

Just thought I would upvote the din rail MDR-10-5 and also mention the NDR-120-24v as a possible option for
the drivers depending on the max current requirements for your motors.

Using din rail power supplies can help to keep things more compact and tidy.

(I bought a MDR and a couple of the SDR (an upgraded NDR) series for the mill I am currently building and
really liked how much more convenient they were compared to the computer PSU I was working with initially.)

If you can get by on just 12v/5v, the computer PSU could be an option on a budget, I had one laying around so
my build started out using one, but it mostly got replaced by the mean well supplies I upgraded to. Keep in mind
that some hardware does not like to have input power supplied through a switch, it may not be the most practical
to have all of your power supplied from one source...

@cmorley I've created github.com/LinuxCNC/linuxcnc/pull/2977 because I think this change could be good for people in general (not just my customized machine)

I tested edit mode and get what I think is the right behavior from it (maximizes to window and shrink back down again)

Resizing the window seems to have reasonable behavior, the size of the splitters are implicitly saved by the preferences it seems.

There is an open question of whether things should be collapsible or not, right now the gcode_editor splitter is collapsible, but the other is not. Let me know if you want me to change this, or if you want me to just ditch the PR because you don't want it.

Thank you for all your help on this.

I might be wrong but from my memory linuxcnc does not like being run by the root user. Certainly compiling hte source as root creats all sorts of issues. I found that out the hard way.

What you could do is build linuxcnc from source via RIP as a specific user and that will place all of the executables in that users home folder. The linuxcnc folder will also be there too. Its pretty easy to do. I did a tutorial of it. 

So other users can be set up as another user and they will never see any access to linuxcnc and root is not used at all.

StoneB wrote:

Hello all, 
first thanks so much for building this image - it really works nicely (although I still need to get my touchscreen working but assuming this is just a driver issue).

The main question I have before connecintg and configuring a MESA card is that my latency looks decidedly wrong - I am wondering if I have the RT kernel enabled at all? When I make uname -r, I get this, which doesn't mention RT:
6.6.28+rpt-rpi-2712

All I did was load the GDrive image a few posts ago, and run a update && upgrade.

Is there any way to check and correct?

 

Blindly running an update is not a good idea.

The easiest way is to reflash the image. The kernel really should have been "pinned" to prevent updates. The RT kernel is a "custom" one.
So you really shouldn't be updating, it's fine as is.

If you are the type that "must update" read this
www.snel.com/support/how-to-block-packag...l-updates-in-debian/

Can you post the g-code file for the above cut and also the BACKUP from the SETTINGS tab.
 

The <SHIFT> key may drop the Pi into diagnostic boot mode.  <ESC> likewise does not work on the Rpi.  From what I'm reading at places like raspberrypi.stackexchange.com/questions/...which-kernel-to-load changing the kernel is more than tricky on the Pi and involves moving/building kernel images manually and editing config.txt.  It would certainly be easiest to just use the ready-made Debian Rpi 4/5 LinuxCNC build found here: linuxcnc.org/downloads/  Just burn it using your favorite flashing software (Rpi Imager, Balena Etcher, etc.)

Do note that the Rpi 5 uses a new and incompatible SPI chip, so vendor boards which use SPI are currently a no-go.  Rpi said they may release the details of their new chip sometime in the future, but not anytime soon.

That is quite an improvement !

I would think they would be nearly identical
though the configuration utilities may have improved
a bit (plus 2.7 is pretty old)

With regards to “security” with Linuxcnc.
It really comes down to who has access to the machine. I feel once the “bad guy” has physical access it’s the damage that can be done to the cnc machine whilst running linuxcnc. It’s not like you’re running a server with sensitive info, you’re running a piece of equipment that can either harm personnel or damage itself.
First rule of security is physical security of the machine. Once an unauthorised person get physical access to your cnc machine I can guarantee it’s not the file system on the computer you’ll be “shitting bricks” about.

Just a quick note on my supposition above, I'm not sure of this... and I'm not trying to lob it out and say it's a bug report, but the whole problem of editor/preview/interpreter loading of the file seems to be disconnected to me and I want to learn why.

Is 2.9 easier to setup the configure for tb6560 than 2.7