Advanced Search

Is this topic dead? Every single tutorial i have found is like six to nine years old. I'm just getting started with CNC plasma cutting, my shop computer is on Linux because i really dislike windows, but if there's no new tutorials out there to guide newbs, then i might as well not waste my time and just install windows.

Wenn das Leben nur so einfach wäre.

Das ganze wird in menu-config im Klartext eingegeben,.

Ich bekomme noch eine zweite SSD und werde da mal probehalber die 2.8 für Raspi installieren.
 

I installed live-build from the Debian repos for my bookworm machine and had no luck. Upon looking at the firmware function the code to blacklist the firmware was not there.
Building a live-build package from the Trixie branch on my bookworm machine resolved the issue. As I also stated the same procedure as allowed me to successfully build a ISO on my Mint machine.

@Admins

I feel I overstepped my position and would like this topic deleted.

unknown wrote:

Building on a system running Debian Trixie raspi-firmware IS NOT installed. (built twice on 2 different machines)
Building on a system running Debian Bookworm raspi-firmware IS installed. (single build only attempted)

This is because they fixed it (it's actually fixed in Debian 12.1) 

bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065640

The _joint_ (ie the actual moving part of the lathe) is not outside the joint limits.

However the drill chuck _is_ outside the Axis (XYZ) limits.

The INI specifies the joint and axis limits separately. You might just need to able to set the axis limits to allow a very negative Z (deep down the spindle bore is very reasonable for a long drill)

It came as a surprise to everyone, I think, that a fix for a preview bug in Gmoccapy caused the touch-off dialog in Axis to break.

I mean, who would even think to check that when testing the bugfix? It's about the most obscure interaction I have ever seen.

(And it only showed up if trying to touch-off to anything other than zero, too)

It came down to the fact that the Axis touch-off dialog parses the entry as G-code,and passes it through the G-code parser. (this is actually quite cool, you can touch-off to "sin[45]" if you want to.

But that relied on something in the startup sequence initialising something in the interpreter, and that, in turn, was messing up the Gmocapy (and others) graphical preview position. (specifically it was running STARTUP_GCODE every time, but only for the preview)

The fix was obviously good, but a side-effect was making the Axis touch-off work by accident..,

Well, the only person who knows for sure is the release manager.
And he thinks that a 2.9.7 is very likely given that one of the fixes in 2.9.6 broke the WHB... pendant driver.

But he is also looking at an ISO based on Trixie, but that will need a new archive signing key as the current one is considered too short.

Please submit your work as pull requests to the "official" ISO building repository rather than going off on your own with this.

The question is whether the drives can do preset velocity with no commutation.

ChatGPT (or any AI) is going to do very poorly with anything that hasn't been done before.

Some of the drones i have built, and more in the works, mostly 3D printed

Certainly seems that way.

Aciera literally stated there would be another release, did he not?

But when?

Not helpful, I was looking for a definite answer. Not the words of someone whose words soothe them.

Try:
min_limit = -250
max_limit = 0
home = 0
home_offset = 0 or -3 due to not stopping at the switch
Notice there are two instances of min/max limits to change.

Referencing this post forum.linuxcnc.org/29-forum-announcement...-9-6-released#336514 is there a possibility of a 2.9.7 release or something along those lines.
The reason I ask as I have been working on trying to create an ISO that doesn't suffer from the "raspi-firmware" issue. And I would like to have a dialogue with regards to releasing a 2.9.x ISO.

Yes, that’s the weird part. It is correct.




INI for Z it’s like this:



[AXIS_Z]
# MAX_VEL & MAX_ACC need to be twice the corresponding joint value
MAX_VELOCITY = 66.66666666666667
MAX_ACCELERATION = 1500.0
OFFSET_AV_RATIO = 0.5
MIN_LIMIT = -0.0
MAX_LIMIT = 250.0

[JOINT_2]
TYPE = LINEAR
HOME = 250.0
FERROR = 10.0
MIN_FERROR = 1.0
MAX_VELOCITY = 33.333333333333336
MAX_ACCELERATION = 750.0
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION
# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 41.67
STEPGEN_MAXACCEL = 937.50
P = 1000.0
I = 0.0
D = 0.0
FF0 = 0.0
FF1 = 1.0
FF2 = 0.0
BIAS = 0.0
DEADBAND = 0.0
MAX_OUTPUT = 0.0
# these are in nanoseconds
DIRSETUP = 10000
DIRHOLD = 10000
STEPLEN = 3000
STEPSPACE = 3000
STEP_SCALE = -1000.0
MIN_LIMIT = -0.0
MAX_LIMIT = 250.0
HOME_OFFSET = 260.000000
HOME_SEARCH_VEL = 16.666667
HOME_LATCH_VEL = 5.000000
HOME_FINAL_VEL = 0.000000
HOME_USE_INDEX = NO
HOME_SEQUENCE = 2

So it was a mistake, that is a huge relief.
And i was not aware who did it as i did not bother to check from frustration.
Thank you.