Topics created by littlehobbyshop

@littlehobbyshop, @T3P3Tony

I can see the usage case for this even with a "conventional" mixing hot end which might be mixing different filaments (yes it can be done if the temperature requirements are similar). Currently firmware retraction (G10) will retract all extruders contained in the tool definition by the same amount. But if one were mixing a more viscous filament with a less viscous one, then it might be desirable to have different retraction amounts per extruder drive. I don't think retraction based on mixing ratio would be much use (but I could be wrong) because we tend to need the same amount of retraction regardless of filament flow rate. But configurable retraction per extruder drive could be useful. We have configurable pressure advance per extruder drive so why not retraction as well?

@littlehobbyshop I can confirm that the volumetric extrusion on/off flag is saved when a macro is called and restored when it completes. However, the filament diameters are not saved and restored.

If you always use volumetric extrusion, you can add a M200 command to config.g.

You should include a M200 command in your slicer start GCode if the print is sliced using volumetric extrusion.

Thanks for the clarification, I wasnt too sure on the details which is why I pulled you in (-:

@dc42 Thank you, I just this minute found and applied the update. I'm usually pretty good with the updates but this one slipped through the net.

@T3P3Tony said in Duet2 CAN system:

A lower cost Duet 3 mainboard with CAN is under consideration but no firm decisions have been made yet.

I'd be fore e.g. very interested in a duet3 type board that

have step/dir/enable headers for the on-board stepper drivers, but none of the drivers itself have link to SBC have CAN so I can use those 3 driver boards and single driver toolboards toolboard without a driver - so toolboard with everything as is only without a driver but just a header for external driver (but with all the inputs and outputs), ideally if it makes no difference in price have 3 headers like current 3driver can board

Now, "very interested" - I'd probbly want to buy 2, maybe 3 of those mainboards and up to ten toolboards, not like I'm reselling them / adding to devices I sell. I was already considering making this type of boards myself, after I'm out of the current projects (probbly january 2021)

@noobydp @littlehobbyshop please look at the heater power feedforward feature. See https://docs.duet3d.com/User_manual/Reference/Gcodes#m309-set-or-report-heater-feedforward. It's not quite what you are looking for but it may allow you to use a lower print temperature.

EDIT: I've solved the problem below, the heater supply and drain were crossed, meaning I was PWM controlling the whole supply to the tool board rather than just the heater.

So, an update. Everything is now connected. BL Touch is working, thermistor is working, extrusion motor is working. I am having a problem with the fans though.

When the hotend heater comes on, the heatsink fan completely dies, as PWM starts to kick in as the heater reaches it's setpoint, the fan starts to ramp up again.
Without the heater on, PWM behaves as expected on the fan.
I have power to the tool board coming direct from the PSU, wiring is sufficient diameter, nothing feels like it's getting warm where it shouldn't.
It appears to be a voltage drop issue where supplying the heater causes the fan voltage to just die. Connecting the fan drain to ground gives no improvement, the fan dies when the heater is supplied. I can't work out why though? It's a standard V6 heater at 35W (1.46A @24v) the wiring and connectors used should be good for 5A at least.
As luck would have it one of my Fluke leads also died today so I can't even measure it reliably.
Here's how I have it wired, 24v from PSU, drain from each the fans and heater go to the corresponding drain pins on the Duet mainboard.
3566b470-d51b-4d06-99aa-9a27083abd1f-image.png

Legendary ! Thanks again.

Well, that's not good but I'm glad it's not just me.

As I have stated in the github issue, whilst the developer console was open in chrome there was no problem, stopping the network log in console brought the problem back again.

Still can't reproduce it though.