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

Had my first simpleFOC project running today. It was an old brushless gimbal controller without encoders and with 8bit mcu.
I was able to control two motors independently and relatively smooth (USB power only)
The atmega328 was also at it's limit, but I'm now confident it will work well with the right mcu.

@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

First print today

Instead of a benchy, I tried the extruder-woodgrain test. Yes there is some, but hardly visible. The corners were sharp and even, that was a relieve. The close loop PID setting are quite soft, so I expected worse...

At the top third, the printspeed got so low, that the filament overheated. 10°C less temp and it was nice and shiny again.

@jbergene

According to this picture

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

@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?

Hi devs,
based on the "extrusion volume" thread, I also think a back EMF calculator as DWC plugin would be helpful for tuning.
The required parameters are almost completely known for the calculation. It only misses coil resistance and inductivity (AFAIK)

Since my Duet boards run on their own network, I don't have access to the EMF calculator at reprapfirmware.org

If we could integrate it as plugin and use 'live' values from the current object model/gcode file, we'd have a nice tuning tool

@nikscha I like the idea. It's like the tool-change macros.
But there is also a problem when you retract / unretract within a toolchange.
Maybe you can solve your problem by renaming G10/G11 to G10.1 and G11.1 via postprocessing. Then you need only one macro for retraction (which also contains the real G10 move)

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

@Tinchus @dc42 I think, his intention is to constantly measure the slightly uncontrollable flow and change the printspeed instantly. (good bye planner queue)

@JoergS5 said in Can this 5-axis FDM be configured with RRF?:

built as spherical, i. e. the three axes cross in one point.

Just out of curiosity:
This crossing point is necessarily the tip of the nozzle? Or nozzle + layerheight?

@dc42 Just wanted to chime in with my 2 cents worth opinion:
The magnetic sheets used for build plates often have alternating magnetic polarisation. Like the one I use for my capacitive probe.
I never had a problem with that, but the SZP might.

@MihaiDesigns Pre-processing such a big part of a sliced file will mess up the extrusion calculation, too.
Unless your slicer already knows about the extra axes and it's just RRF that needs to be altered.

@NineMile Last time I tried, you could use sensorless homing/stall detection on any axis.
But you are right, you'd have to reduce motor current for those moves, but at the same time it needs a minimum speed to be succesful.
I wouldn't like to see my 50$ router bits crashing in a clamp.
Maybe a regular endstop-config would be a better choice? When the routerbit itself gets electric contact to the metal clamp it doesn't wait for so_many missed steps to trigger alarm.
@gloomyandy That kind of metal2metal contact probes would trigger in any direction, but you wouldn't know where the obstacle is. No problem for an emergency-stop IMHO

@Ralms instead of relais and optocoupler you might find a simple inverter/driver chip with optocoupled input in the good'ol 74hcxxx series.

For people not having that touchprobe thing, would it help to use modified "sensorless homing" moves as crash protection?
You'd check for contact , but don't set coords to whatever your homing coodrs are

@jay_s_uk I was about to edit my reply, because maybe the TS wants to use IO pins from the MCU directly?
In that case I wouldn't draw more than 2mA from each pin.

@Ralms said in Drive standard LEDs. What is the max current rating of IO pins?:

All 3 LEDs are built-in in the button, they share a common ground

Maybe you get more trouble from the fact that they share GND?
AFAIK all MOSFet IO-ports on Duet boards switch to GND and that wouldn't work for you.

@juanggrados You might be able to still use the board with low current steppers and using an external bed-heater power supply controlled by SSD-relais.