Advanced Search

Rodw was right, seems like they finally cleared the last printk/console hurdles now.

www.phoronix.com/news/Linux-6.12-Printk-Pull-Request

increasing the ohmic threshold to 23.5 seems to have solved this issue for me.
After the nozzle got wet from the watertable the ohmic voltage was showing at above 22volts.

Hi,
Curious to know if the script for the post processor in qtplasmac worked for anyone?
Currently I am using a different post processor and it runs through a filter on qtplasmac which works ok. But some files it has issues with and I can't use the option to start at a certain line.

So I thought I would try and run this cff to see if it was a better option, using 2015 hypertherm nestmaster.

I used the cff for pronest on this thread. Screenshot and gcode attached.
 

cakeslob wrote:

is "precise" a debian version or something?

Ubuntu

machinedude wrote:

Are there any tip or tricks for getting a tandem axis tuned? it seems like it is a lot harder to get settled into.
 

About the only thing I've seen that was reasonably successful was to disconnect the gantry from the motor to be tuned, and attach half the gantry weight to that motor's carriage.

This will get the inertia in the ballpark, and the values can be copied to the other motor.  From then on adjust the same on both motors.

This may be fairly easy, or it could be a royal pain - just depends on how the hardware is assembled.

is "precise" a debian version or something?

Was going to open a new thread, but thought the image authors might want to get some feedback that might relate to the image.

Installed the 2.9.3 image on a RPi5 and after a few self-inflicted hiccups everything seems OK, including qtpyvcp/probe basic.

Except the touchscreen isn't reconized.  lsusb does't show the touchscreen.

I've got the touchscreen connected through a powered external USB hub, and I've tried every other combination of ports.  The RPi5 seems really picky about what hardware works (or doesn't) on various ports.

Keyboard w/touchpad is fine, as is a usb trackball.  Both of those work through the hub and directly in one of the Pi's ports.

Any ideas on what to do about the touchscreen?  Monitor is one of those generic 15.6 things, and works fine on everything else it's plugged in to.

Aciera wrote:

Hm, not quite sure what to think about this but the pure lack of reaction to those individual mails about broken infrastructure makes me wonder about the state of things. Seems to me that the number of mails on the developers mailing list has generally dropped substantially over the last few months and a lot of mails seem to go unanswered.

I have been wondering about the state of things as well. I am unsure if it's ever been this slow before, but it seems most of the effort is in translating the docs. Which on one hand is a good thing, and on the other hand, we have other issues like being limited to 3 axis look ahead...

Unsure what to make of it really. Maybe it'll come back around...

More piccies from different angles. Slowly working out the cable and hose routing. Bleh.