Advanced Search

Have to correct myself after reading through the QtPlasmaC documentation.
Centerpunch uses the spotter tool, which is the torch firing short enough to only make an indentation. Very clever. Has its own setting on the Parameter page, firing time most notably. So let the M3 $2 S1 stay.

Actually, when I think of it. I think its a bug/feature of PlasmaC that M3 won't allow a line above with only coordinates, but must include also the move command.
Not ok

Ok

I think one can not take for granted that EL3061's signal ground is the same potential as the workpiece ground. If you are lucky it might work, but to be on the safe side the torch signals should be isolated and free to float.

No the selection of the type of desktop has absolutely nothing to do with your issue. It only selects what kind of Desktop environment you will have once booted.
Grub is the boot loader, this is where your issue is.
Due to HP being in bed with MS they chose "Microsoft's way" on naming the boot files for uefi.

If you turn on legacy boot and disable secure boot, as tommy mentioned a while back this may resolve your problem.

MTTI wrote:

Thanks for this answer.

I would like to install RTAI due to the jitter in my setup, which is around 70k.
I'm using 4 stepper motors with encoders (closed loop) and a USC board from PICO.

Sometimes, though not very often, I get an "Unexpected realtime delay" message.
Do you think this could be related to the jitter amount?

I've tried every optimization I could find in the BIOS...
 

Just having a look at the PICO config, is the base thread used ? From a quick look nothing appears to attach to the base thread. Which would lead me to think that a simple RT_PREEMPT kernel would be suffice. The PICO board would seem to operate in a simialr way to a mesa 7i90 using the EPP protocol. IE using the parallel port to send timing info to a FPGA.

I think that there are issues with https on the wiki, try http:
wiki.linuxcnc.org/uploads/hobbing.zip
 

Rodw, you said "Be sure to select Mate or XFCE desktop" The defaults in your suggested ISO / Debian 13"are "Debian desktop environment", then "Gnome" and "standard system utilities". All preselected. Not selected are "Mate and Xfce" among others. Do you feel going with the preselected defaults will cause the "can not find a bootable drive" error problem? or should I just go with the defaults? If I don't select some of the unchecked software options on this install page, will it cause my system to not install or just not find the bootable OS on reboot? It does say "the core of the system is installed"

Debian 13 is still in testing. Debian 12 is the current stable version. So no Debian 13 (Trixie) is not more stable than Debian 12 (Bookworm). Honestly I would stay away from Trixie based on your Linux experience. Stay with the version that actually has been released rather than a version that is still in testing.

I would also look for any HP forums that discuss your particular machine as it maybe a "HP issue" with some input from Microsoft that is causing the issue, not a "Linux issue".

But have you followed my advice regarding testing the latency of the computer ? If the latency is not suitable I wouldn't bother trying to install Linuxcnc on that machine.

You keep mentioning "sudo commands" but give no indication to what these areor what they are supposed to do, do you see this is another issue where you are not supplying information, do you need this information beaten out of you (this does not mean an actual beating, but this how frustrating you are being). Would these be related to HP's buggy uefi and having to rename some boot files.

I have a HP computer 110-210, The system info is in the first photo provided “Mysystem.jpg” I will send a photo of the label on the side of the box if you like, but it has less info than the detailed system info. Sorry to provide to much background info on me, but is was suggested that I did not try the obvious things first like using the default settings or installing to my main internal drive first.

"unknown" said “The reason for my troll comment was because you seemed to not want to give a lot of info, or it would seem directly reply to any suggestions.” I though with all the photos like “my detailed system info” I was providing too much info. If there is something missing from all the info and photos provided, I am happy to provide it.

I saw the latency test while in live mode. It asked to do things like stress my system that I could not do yet like running motors I think. But it did not seem like it would prevent my “successful installs” from being found on ether hard drive” Do you think they are related? Now that you have seen my system info, do you feel that my system is not capable of recognizing a successful install on ether of my hard drives?

Update… I thought trying installs without the Ethernet connected may help avoid the “UEFI: IPv4 Realtek PCIe FE family controller” coming back and interfering with something, but the install made it clear it wants to be connected to get all needed files. So I am starting over with it reconnected. I am currently trying “rodw” suggestion to see if this ISO “debian-trixie-DI-alpha1-amd64-netinst.iso” will be found after a successful install I hope. I did see it said Debian13, so maybe it is more stable than the others I have tried. Unless the problem is something else. I will post the results of this install attempt using the suggestions like “Be sure to select Mate or XFCE desktop “ but the sudo commands would need to be in a live mode terminal if the install fails.

NO = normally open switch
NC = normally closed switch