Duet WiFi firmware new feature priorities
-
Can Enable auto sleep by turned on my default?
-
Can Enable auto sleep by turned on my default?
Please define what you mean by auto sleep.
Currently the default behaviour is that when all motors have been inactive for 30 seconds, the motor currents are reduced to 30% of normal. The timeout and percentage are configurable.
-
In another thread it was discussed to add an exception for trigger 0 so that it was prioritised over running macro events. Purpose being to have the ability to add a physical emergency stop using a micro switch
Is this possible? -
In another thread it was discussed to add an exception for trigger 0 so that it was prioritised over running macro events. Purpose being to have the ability to add a physical emergency stop using a micro switch
Is this possible?That's already coded in 1.17RC1, although I haven't tested it or measured the latency yet.
-
G. Support for three independently-controlled Z motors, normally moved in sync but moved independently when performing bed leveling (and I really do mean bed levelling, not bed compensation).
I just want to thank you for this being in a new feature list.
And i have a question if this is a proper thread. Is it possible to do a two side filament diameter measurement with live adjusting printing parameters depending on filament diameter? -
And i have a question if this is a proper thread. Is it possible to do a two side filament diameter measurement with live adjusting printing parameters depending on filament diameter?
Possible in principle, but to do it accurately I think it would need two linear CCD sensors and probably lenses. Unless you are extruding your own filament, it's probably not worth while IMO because most filament has good diameter accuracy these days.
-
And i have a question if this is a proper thread. Is it possible to do a two side filament diameter measurement with live adjusting printing parameters depending on filament diameter?
-
Possible in principle, but to do it accurately I think it would need two linear CCD sensors and probably lenses. Unless you are extruding your own filament, it's probably not worth while IMO because most filament has good diameter accuracy these days.
Yes, i want to use my own filament(From Filastruder 2) and yes, you get my bad English right, dual CCD sensors is what i want. Not a must have thing, but i think it will increase quality of my prints and make my printer more userfriendly.
I saw this, not my thing, i want dual sensor because filament may have an oval profile.
-
Mount two at 90 degrees to each other, average the result.
But the filament should good quality. A Filastruder should achieve +/-0.05mm fairly easily and +/-0.02mm with some tweaks assuming properly dried/processed pellets.
-
I have a suggestion;
When the printer goes into "heater fault" why not just pause the print and shut off the heater that is at fault, instead of ruining a whole print… That way, after we clear the fault and check to make sure there are no issues, we can just resume printing...
-
I have a suggestion;
When the printer goes into "heater fault" why not just pause the print and shut off the heater that is at fault, instead of ruining a whole print… That way, after we clear the fault and check to make sure there are no issues, we can just resume printing...
Good idea. I have added it to the work list.
-
I'm not sure if this has been noted before or not, but ill address it here and you can correct me if its fixed.
here is my scenario, I set up a print to run at 30mm/s, however along the way i see its running well so i bump it up to 60mm/s
( 200% of speed) now when the print is finished the delta tries to home or move some where else to get out of the way and its also at 200% of speed.and that's when things get ugly….
and if for some reason it it dose make it to that location with out crashing and i forget its at 200% of speed, its almost guaranteed that it will crash trying to move to the first position of that next print.
I have all my other moves confined set at just the right speed ( Homing, max travel speeds) , so if its over 100% things get crazy.
is there a way to set the % of speed to only be that when running the print? i'm sure you can add it to the G code but i would think it could be built in so others done experience the same problem?
i use that speed function all the time to run tests and all kinds of stuff.
also dose the higher % of speed also over ride the config files max speeds?
Thanks!!
~Russ
-
Hi Russ,
Yeah I had this issue so now I use M220 S100 in my end gcode and in my cancel.g so any time a print ends I return to 100% speed before homing and begin at 100% for the next print.
I also find for autocalibration I reduce my accel/jerk and speed then return it to normal within my bed.g. -
OK, thanks for the reply, i still wonder if it can be integrated in the firmware??
also i could add to the pause.g for when i want to do that, but when i start back up i guess ill need to change the speed again.
say is there some kind of script that can be used so " get" the current speed, then put it back after a pause.g?
any how. ill add those to my .g files for now!!! Thanks!!
~Russ
-
Hi Russ
Thanks for pointing this out. Interesting question about how and when we want the firmware to overwrite the commands entered by the user in a non obvious way. My perspective (personal view entirely) is that we want the firmware to stay as the user set it until there is a reset or a fault. So if you have changed a speed, temp, acceleration, or any other variable that is what it stays at.
That said there may be very good reasons to deviate in specific cases.
-
On the whole I agree with Tony - the firmware should behave in a consistent and obvious manner. However, here are some options I can think of:
-
Reset the speed to 100% when M0 or M1 are executed. This would handle end-of-print (assuming you use M0 in your end gcode) and cancel print.
-
Always execute homing and similar special moves at 100% speed (i.e. G1 moves with S1 or S2 parameter)
-
Always execute extruder-only moves (or extruder + Z movement only) at 100%
Comments? Other suggestions?
-
-
Oh I would love that!
Only (small) reservation I have is that the more of this kind of functionality we add, the murkier the whole system becomes. The system will start to show behavior that is not totally expected.
In this case that is not a danger, as the system will do what you expect, and not what it should do. (if you get my drift)You are a very busy man, David!
-
Personally, I think the firmware should "behave itself" and not try to second guess and override what the user asks for. I've done similar things to the OP but with extrusion multipliers. One soon learns by ones mistakes. During commissioning, I started slow but played around with the speeds, not just for printing but for homing and non print moves too and I'd have been tearing my hair out if the firmware kept overriding what I was trying to do.
I hate auto correction on my 'phone which doesn't understand proper nouns and/or decides it knows what I mean better than I know myself, but I love it when the spell checker on my PC underlines something. So maybe DWC should how values other 100% in big Red letters as a warning/attention grabber but otherwise it should be left alone.
Well that's my twopence worth anyway…..
-
I'll see if some sort of consensus on this emerges, and if so, look at changing the behaviour in firmware 1.18. It had already occurred to me that whatever we do to the speed override should perhaps be applied to the extrusion override too. OTOH I use the extrusion override to adjust for the characteristics of particular filaments, so I don't generally want to reset it after a print unless I am changing filament.
-
Maybe some sort of flag or toggle in the user config so that users who want the firmware to reset speed/extrusion can have it, and those that want it left as is can have that?
