Advanced Search

I have recently had to return to 2.7.15 from 2.9.4.  (There is no easy way to upgrade from 2.7.15 to 2.8 which is required to get to 2.9.4.  Attempts to install from 2.9.4 ISO were unsucessful.  Even getting 2.7.15 to install from ISO was hard,) 

This all worked fine in 2.9.4.  In axis gui, I have homed all four axes.  Z=0.  When I use G1 Z1 f4, I get "Can't issue MDI command when not homed."  Can you tell me what I need to fix?

In the first video it looks like it just bounces on the material.
In the second video there is some hesitation, a few tenths of a second maybe.
This is with standard plasmac settings? Meaning material height set on probe up.
If I had this kind of performance I wouldn't worry about improving it.

I can see that a stiff spring, or large hysteresis, in the float switch can have that effect
with weak materials and that probe up can help. I have actually left the float switch
as is, with probe up. It is more with ohmic sensing where I don't see the need.

Water. A possible problem only the first cut, then there is post-flow of air that blows it away.
Lasts for 15 seconds or so. I can't (or don't know how to) only start air.
Maybe torch on for 1/10 of second. Not a big problem when I have got things to work.

There is an ECT60 for Z. I can try that. What should I be looking at?
 

AMS easier to setup but lots of waste
Multi extruders are a real pain to setup and adjust, and this has to be done any time you change the nozzles. No waste though.
Knowing me, i will most probably go with multi extruders, i like to suffer!

www.eusurplus.com in Portugal
www.welectron.com in Germany

2.7 ?
You mean 2.9.7 most probably.

The RPi doesn't require an installer the way the PC platform does.
Plus I'm looking at some other tools put out by the Raspberry guys that look pretty good.

Andy, if this is tested as working, can you build an official 2.9.7 release and put it on our repo for bookworm and Trixie?
temp folder does not sound very permanent 

I think you should add a lot more bracing to those legs unless you like dancing tables!

The live build gets its code from the host that builds the system so to get a Trixie system, you need to be running Trixie. So I don't see why building for bookworm is not a problem.

In my testing back with the original installer (after some changes were made and committed to the release version), the pi firmware was not installed but it seemed after later bookworm versions were upgraded to, the firmware was  erroneously installed. And yes, I built the builder from source.

Why don't you try changing the architecture to arm64 and give the pi a go?

Yeah I could but I'd like to have a Trixe & Bookworm base image to work off. I'll get that going tomorrow (doesn't take too long) and have a look at the amd64 live-build for Trixie. Tho I'm a little desperate for disk space and had to drag a 2TB mechanical drive out of the cupboard.
This week's spending money went on RAM........so maybe in a couple of weeks I'll grab a NVMe drive.

Maybe if I stuck with Mach3 I wouldn't spend so much money, bugger I said the quiet part out load.

@langdons
Dude could you link to the main forum, there has been no lag issues for a while.

@Andy
Sorry I haven't had a chance to check with UEFI. I'll action it for tomorrow.

Your could just upgrade Bookworm  to Trixie with sudo apt dist-upgrade for testing

Use a Meanwell power supply. Say a MDR-15-5 which is 2.4 amps

I've been playing with pi-gen.....I think it is a little better, you get a more raspberry pi like experience. There's a link in my proposal thread. ATM the moment I've been building upto the "lite" stage burning & booting and installing the desktop,Xorg and the rest. Linuxcnc has been from the debian repo.....But I should be able to fine tune things.

Bookworm has been the target so far, Trixie shouldn't be an issue, but one thing I really need to know is the status of linuxcnc.org/docs/2.9/html/drivers/hal_gpio.html . I think there was an issue with the libgpiod library.
Bookworm version is 1.6.3-1
Trixie version is 2.2.1-2

You can burn to your boot device sing RPI-Imager and edit settings such via the imager.

There's realtime kernels available via the raspberry kernel repo. The Rpi4 4k page kernels run on the Rpi5.......so we may only need one image to cover both boards.

win32diskimager was my go to for years but it has let me down with later versions. I recommend you use Balena Etcher which is available for Windows, Linux and Mac.

I discussed its use in my latest video