Topics created by PCR

@PCR Thanks, I'm getting around to documenting the complexities of the Tool Distribution board. I just realised the other day that it's possible to support eight toolboards (and maybe even nine if you use the CAN_OUT RJ11 port) wired as stubs, on a single TDB! You can use either pair of pins on each Tool output for a stub, and have a separate stub connected to each pair. Then, of course, you could have more than one toolboard per stub...

And yes, the tool bypass jumper needs to be on for stubs to work.

Ian

This may be of interest to anyone looking at this in more detail as it allows examination of bgcode files.

https://github.com/ellensp/bgcodewalk/blob/main/README.md

The example given seems to show Heatshrink compression being used along with Meatpack, both of which I think are designed to use a relatively small amount of memory to decode.

This issue is now fixed. See https://forum.duet3d.com/post/303514 for more details.

@pcr said in Brainstorming for mesh bed limits.:

@phaedrux that's what I want to say. I had this problem

Can you elborate?

I'm trying to do this on my printer right now, but somehow I can't get S3D to output the min/max XY for the file to be printed.
Anyone have a tip on how to do this with S3D?

@phaedrux

https://forum.duet3d.com/topic/25882/only-probe-bed-where-it-is-printed-solution-with-prusaslicer/3

for PrusaSlicer and Ideamaker its super Easy ;)=

@zapta

@0nn0 sent PM

The impacts on PA likely vary with the input shaping algorithm and targeted frequency. I'm running MZV at 23.85 HZ and my PA tuning strips look nearly identical.

@pcr said in " Probe was not triggered during probing move" Emergency Stop?:

@fcwilt

ahh sorry 3.4B5

Scroll down in this documentation to where they have an example of using result and abort during bed leveling.

The example uses a while loop which aborts if the bed leveling fails.

Bed Leveling Example

Frederick

@o_lampe said in New Raspberry Pi Zero 2W:

@zapta @dc42
It would be interesting to know:

To set the record straight, I know almost nothing about CANBUS and the little I know is mostly from this thread. 😉

BTW, I do have some experience with another automotive bus call LINBUS that you can find in modern cars but is seldom mentioned. This product for example is based on a public domain design that I published on github http://t-design9.com/memory_module_porsche.html .

@pcr From RRF3.3 M950 assigns 1, 2 or 3 pins to a spindle as described in the documentation:

When using M950 to create a spindle (from RRF 3.3) use the following format:

M950 R0 C"pwm_pin+forward_pin+reverse_pin" Qfff Laa:bb

C can have 1, 2 or 3 pins. The first pin defined is a pwm capable pin to set the spindle speed. If a second pin is defined it is used as spindle on/of, if three pins are defined then the second pin is spindle forward and the third is spindle reverse. "fff" is the PWM frequency as usual "Laa:bb" sets the RPM range as "aa" to "bb". "Lbb" just sets the max RPM to "bb". Default RPM values are 60 min 10000 max

So the command as you have it would end up using that pin in PWM mode which you don't want with a relay.

Please try the following:

M950 R0 C"null+!exp.heater3";

This is untested by me but I hope that will assign a null pin for PWM and just us the heater 3 pin for on/off. Please test it, and especially test that M5 works as well as M3.

@pcr said in Just a little sanity check.:

@dc42

https://youtu.be/8oclp8xvztU

And

https://youtu.be/YFMlYbNTgBw

Looks good!

FYI the Duet 3 Mini includes a connector for a 2-driver expansion board. We included a 5V pin on that connector, so that instead of a 2xTMC2209 daughter board, it would be possible to fit a 2x external driver daughter board.

@pcr i'm interested to buy a pcb...

@diy-o-sphere Tested some ldo,s super loud.

@PCR updated the wiring diagram image.

@pcr
Actually the design is based on the Sherpa Mini 👅
But they all use BMG gears (with Orbiter motor), but without planetary gears from the Orbiter.
And they seem to require a wider rod-spacing or higher adapter to clear the rods.

Here is a teaser of my ongoing experiement, trying to free some space between the rods.
It's too early so say anything.

20mm_spacing.jpg
20mm_carrier.jpg

@PCR said in G30 Question / Feature Request:

Running 3.2 stable.

if i type

G30 X100 Y100 P0 Z-9999

it will probe at the 100/100 with the probe offset in mind

But if it want to home my machine with a G30

G30 X100 Y100

does not probe at at 100/100. It probes at the current location. I suppose thats normal?
So before i home my machine i have to Go to G1 X130 Y100 when my prob offset is -30.

Best

OK back to your question.

It has been suggested more than once that a G30 with no P parameter respect the X and Y parameters so the probe gets moved to the correct XY position, taking into account the probe X and Y offsets.

You can add your voice to this suggesting in the category for firmware updates.

As it stands you have to use a normal G1 command with X and Y adjusted according to the probe offsets.

You can compute the values for X and Y yourself or you can use the conditional code feature of v3 firmware to do it for you - if you wish.

Frederick

I use a PizeroW with the Pi cam module and MotionOS to turn it into a webcam. It works very well with DWC and makes for a very small and very functional cam.

https://github.com/ccrisan/motioneyeos/wiki