Hi guys,
I'm playing with my new extruder and would like to know how much it extrudes in a real print.
Is it possible to display extrusion volume in DWC? Printspeed, layerheight and layerwidth? should be available for calculations.
I extruded in free air to get ballpark numbers, but real life is different.

@gtaman
It's actually the same:

• create a global variable blockDaemon
• set global.blockDaemon = true at the start of the M300 file
• set global.blockDaemon = false at the end

Then anyone using Daemon.g for real can add these lines

while global.blockDaemon = true
          G4 S1000

@jbergene

According to this picture

• positive X goes to the right
• positive Y goes to the back
• positive Z goes up

@m0ck1nj
Check the TB6600 datasheet. If it is OK with 3.3V signals on step, dir, enable you can wire it directly.
If it needs differential signals or 5V you can use the much cheaper expansion breakout board

To celebrate the new level of 3D printing named conditionals and variables I thought it would be funny to rebuild my old Prusa i3 to an IDEX with infinite Y-axis.
A macro would then apply Tic Tac Toe rules to the two feltpen-tools which actually write X and O to a foil on the bed.
The infinite Y-axis would then scroll the foil around and thereby wipe off the nonpermanent ink.

With this thread I want to encourage other users to think out off the box and come up with their crazy ideas to celebrate the amazing Duet team and their breakthrough Firmware.

@dc42 said in Smart Effector including toolboard-capabilities?:

It's clear to me that the Orbiter could not be used with a Smart Effector made to the current dimensions. We would need to increase the rod spacing to at least 80mm in order to accommodate the various parts of the extruder. We are looking into this, however it would make it unsuitable for the smaller delta printers.

Hi dc42,
I just stumbled across this thread and wanted to guide you back to 2016 , when we discussed the cycloidal direct drive. (I still have it laying around)
I've made an 45 degree adapter for it, that suited the smart effector pretty well.

Another way to mount it, was the split motor/gearbox idea.

I could try to reuse my motor and design a BMG-drive for the Smart effector?

@gloomyandy
I nominate this as macro of the month

One thing not mentioned by anyone is the G31 probe offset. Are you sure it's OK?

@samlogan87 ```

Any trigger number # greater than 1 causes the macro file sys/trigger#.g to be executed. 

This line quoted from Wiki tells two things:
The minimum trigger number is 1
The macros have to be stored in /sys folder.
I guess you've put yours in the /macro folder, which would be logical for me. (but not for everyone in the RRF dev-team?)

@cr3d
...what cosmowave said.
You can trigger your own filament-out macro with the filament sensor, which in the end toggles a different I/O pin. This pin is the 'official' filament-out pin defined in config.g

@sonderzug
I checked the variants yesterday and my concern isn't about the drylin itself but the surface quality of the rails?
Some look like extruded aluminum, which would eat up drylin in no time, I guess?

@paolozampini1973

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138                  ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0                                           ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S2.00                                                ; enable bang-bang mode for the bed heater and set PWM limit

You can not set the PWM value for the bed heater greater than S1.00

M950 F1 C"fan1" Q600                                 ; PWM ESTRUDER E1 WIRE BLACK WHITE create fan 1 on pin fan0 and set its frequency
M106 P1 S0 H-2                                       ; PWM ESTRUDER E1 WIRE BLACK WHITE set fan 1 value. Thermostatic control is turned off

"H-2" parameter is wrong. It's either H-1 or H2 I guess?

#MeToo
but for a moving bed in my K40 CO2 laser. Which means, I'd put the sensorplate on the material and reduce distance to the air-assist nozzle until touchdown

@rogerpodacter
You can reduce the motor current when in idle with the 'I' parameter of M906 and:
There is another M-code (I just don't remember) which reduces the current during slow moves and standstill (like meshlevelling Z-motors)
That's the one you need

//edit It's M917, but for some cases M913 is also useful

@jay_s_uk
That's cool ( or hot?), but it would be even better to do this automatically and have an easy way to switch it back to "normal". By drop down menu in DWC or a macro perhaps?
Wondering, if the parameters are part of the object model?
Anyway, thanks for pointing it out!

@jens55 said in If you have poor print definition, check your nozzle:

A regular hot end must be hot-tightened because of that.

I can copy your findings about leaking aluminum block.
I just want to point out, that I always get a "heater fault" error when I hot tighten the nozzle, because of the immediate temp drop caused by the metal-tools I'm using.
While at the printer, doing some "heart surgery" this error is pretty annoying, because I have to drop the tools, go to DWC PC, cancel the fault and start heating again.
So, hot tightening is a one chance game...

firmware wishlist: allow temp drop while maintaining the hotend.

I tried to promote my idea of a "mini-z" axis several times. I needed to control z-hop and mesh levelling for each toolhead individually.
So far it is still a wish, not even on the devs ToDo list.

@Feynman137
@falcounet said in Printer forgetting z-offset at start of new print:

If your Z axis move the wrong direction when using G30, you may probably need to fix the axis direction (S value of M569 for the Z driver).

That is most unlikely the cause, since he can print several parts in a row.
I guess it's a false Z-endstop-definition? Z homing to min-endstop is the way to go.

@x-stride I don't hink it's worth implementing this, as there is no good reason this concept goes "viral"

Disadvantages:

• the rails for the delta can be shorter, but without any Z-motion they will wear out quickly
• the bed mechanism of a CoreXY is usually slower and complex. You'll spend more money on it than you save for shorter Delta rails
• how would you calibrate the Delta

You can still find a workaround by calling the bed's axis "W" and postprocess the gcode files (replace all "Z" with "W")
You have to change the homing files and overwrite the z-height found by the Delta calibration.
No big deal, if you're familiar with the RRF universe.

@jay_s_uk said in Permantly save Z-Probe Offset after Z-Calibration via G30 S-3:

@wieman01 you want M500 P31

How would that work with several tools? Do I add the toolnumber?
THX
Olaf