After a simulated print finished, there is a big green button in the status section to "Simulate again". I cannot think of any reason why anyone could want this.
To my understanding after a simulation the only reasonable options are either print the simulated file now or not to print the file.
I would like to suggest to change the button to a "Print Now"-button, which starts the actual print of the just simulated file.
For anyone still looking for a simple solution for those Meanwell RSP Power Supplys. Here it is.
I implemented and I tested this with my Meanwell RSP-500-24 Power Supply. It works perfectly as intended.
There is also a PCB-Layout, but I have not implemented it yet and hence it is untested.
I really like the concept of the Duet 3 Toolboard. But since I mainly use delta-printers, it is of limited use for me.
I would really like to see a new revision of the smart effector, which includes the capabilities from a Duet 3 Toolboard. It would be really awesome, to be able to reduce the number of wires going to the effector.
Currently I need 6 + 6 + 1 Wire (2x temp, 4x zprobe + 4x fan (2x2), 2x heater + fan tacho signal). With toolboard-effector it would be 2 + 4 Wires (2x Power + 4x CAN), whereby I would consider the CAN-wires actually as single cable. However, it would reduce the number of wires by at least 50%.
Are there any plans for a smart effector like this?
If not, please consider this as a suggestion for future hardware development.
I am afraid the usual thing happened when someone is asked to give full details on printer- and slicer-settings. I went thoroughly through my settings to make sure everything is consistent and reasonable. I reduced the printing speed from 90mm/s to 80 mm/s and I lowered the line width from 0.6mm to 0.45mm.
Now my extrusion problem is gone. My best guess is, that there was a back pressure problem, because of the high flow.
The result is not perfect, but I can absolutely work with it and do not have to cancel prints anymore. However, I am little afraid that this problem might come as soon as I raise the print speed. But for now I am good.
@Phaedrux Thank you for being my Rubber Duck. 
I like the temperature chart shown in DWC. But I would like it even more, if the chart would not depend on the connection between my browser and the duet board, e.g. due to bad wifi connection or a accidentally closed browser (tab) or "background browser sleep" when using DWC on the smart phone.
I suggest to have the temperature data buffered on in the web server and delivered with (let's say 10 minutes) history to the browser from there.
It seems I have not read the docs as good as I thought. The L Parameter of the M106-Command fixes my problem. This is the minimum Power for this fan.
M950 F1 C"duex.fan8+^duex.pb6"
M106 P1 C"HeatSinkFan" S0 H1 T45 L255
I found this out when investigating the fan status by running M106 P1. It only turned with 50% power.
I am afraid the usual thing happened when someone is asked to give full details on printer- and slicer-settings. I went thoroughly through my settings to make sure everything is consistent and reasonable. I reduced the printing speed from 90mm/s to 80 mm/s and I lowered the line width from 0.6mm to 0.45mm.
Now my extrusion problem is gone. My best guess is, that there was a back pressure problem, because of the high flow.
The result is not perfect, but I can absolutely work with it and do not have to cancel prints anymore. However, I am little afraid that this problem might come as soon as I raise the print speed. But for now I am good.
@Phaedrux Thank you for being my Rubber Duck.
Hi,
I have a extrusion problem with my big delta printer. It seems that the end or the start (or both) of an extrusion is problematic. My current print project are assortment-boxes for drawers.
My first approach was to align all seams, but it did not went well. At the seams, excess filament built up a blob of plastic. The print nozzes stumbled over this blob and my tower axes skipped steps, what resulted in a shifted XYZ-Positioning and I have to cancel the print.
At first I took a look in the curling-corners section of the Simlify 3D Print Quality Troubleshooting Guide. It said overheating might be the problem. Thus I reduced the nozzle temp from 230°C to 215°C and turned my nozzle fans to 100% from layer 3 on. At least all no-seam-Corners came out well now. They were a little curly before. How ever, the problem with the seam-edge persisted.
Next approach was to randomly distribute the seams. Finally I did not have to cancel the print, but it came out really ugly.
Next I took a look at the Blobs and Zits section of the Simplify3D guide. It did not help, because it was all about retraction. As far as I can see my extrusion problems are not about retraction, at least the problematic seam-edge had none.
I use:
Printer: Tevo little Monster with:
Filament: Prusament PLA Galaxy Black
Slicer: PrusaSlicer 2.5.0
However. To me my problem seems more slicer-setting-related (or maybe hotend-related) than Duet- or RRF-related. There are many many tuning knobs in the slicer. I do not know where to start.
I hope this is a common error pattern and you could maybe give me a hint, what I could try to change.
I like the idea of using the daemon.g. But what about the wear of the sd card? How smart can the controller of the sd card expected to be? Is it writing the exact same blocks over and over again? How bad is it for the card?
As I learned there is only the option to limit cartesian movement speeds. To account for the non-linear relation of cartesian movements and tower axes movements, the best practice is to take a lower maximum speed by factor 1.7.
That seems insufficient in two ways for delta printers:
For CoreXY printers a factor of 1.41... is usually used instead of 1.7. On the one hand, that prevents all motors from going too fast in the worst case, but on the other hand it limits the maximum speed on all moves that are not straight parallel to the X axes or straight parallel to the Y axes.
The same arguments go for the acceleration and jerk.
Thus I would like to suggest an implementation of M203 (M205 and M201 respectively) that allows for per-driver speedlimits instead of (or in addition to) cartesian movements.
I like the temperature chart shown in DWC. But I would like it even more, if the chart would not depend on the connection between my browser and the duet board, e.g. due to bad wifi connection or a accidentally closed browser (tab) or "background browser sleep" when using DWC on the smart phone.
I suggest to have the temperature data buffered on in the web server and delivered with (let's say 10 minutes) history to the browser from there.
@dc42 Thank you. That answers my question and solves my problem.
But I am curious. It seems, the EMF calculator just takes the delta-geometry into account with a factor of 1.7. But why 1.7? Where does it come from? (Follow-up question: Why 1.414 (≈ √2) for CoreXY?)
@Phaedrux Thank you for citing the docs to me. No irony here. I absolutely overlooked that the value for the H parameter is in stepper steps and not in mm/s. 
Thus there is no problem and my value is way less off than i thought.
I consider this problem solved now.
Hi,
I have a problem with configuring the maximum feedrate on my big delta printer (Modified Tevo little Monster with Duet2Ethernet, running RRF3.4.4). Maybe it is just my lack of understanding.
I would like to tell RRF how fast it may drive the tower axes at maximum. But as far as I see, this is not possible.
Instead the only configurable feedrate limit is for cartesian axes (aka X,Y and Z) via M203. Since the kinematic of a delta printer implies a non-linear relation between tower-axes moves and cartesian XY-moves, configuring only limits for cartesian moves might not suffice.
The only thing I could find in the docs was a rule of thumb:
As a general guide, your maximum XYZ speeds in mm/minute multiplied by your tower steps/mm should be no more than 3.6 million when running firmware 1.09i-dc42 and later
Considering the named firmware version, this might be outdated. Moreover it does not answer my question.
So I am a little puzzled. The EMF Calculator tells me, that I should stick to a maximum of 245 mm/s on the tower axes, but how do I configure RRF to keep this limit?
@Phaedrux said in Tuning stall detection:
@justus2342 said in Tuning stall detection:
rated_holding_torque (Nm) = 0.46
Does your motor have a spec sheet that shows a torque curve? You may find the rated holding torque to be quite a bit lower.
Yes, here you go:
https://www.omc-stepperonline.com/download/17HM19-2004S1_Torque_Curve.pdf
It seems indeed a little lower, but since the formula has it in the denominator, smaller values do even raise my minimum speed. That's the wrong direction.
@Phaedrux said in Tuning stall detection:
Have you tried adjusting the sensitivity yet?If you're getting lots of false positives that's where I would start.
Yes, I played around with it a little. It seems the truth lies somewhere between 3 and 10. I will have to figure it out by trial and error. (It would be really nice to see the trigger value in the warning log-message by the way. )
Nevertheless, I would like to have at least a reasonable value for the H-parameter.
@jay_s_uk We are not talking about sensorless homing, right? What could be a better option to detect skipped steps on a delta printer?