Firmware wishlist

• 

  Firmware wishlist and priorities for Duet WiFi and Duet Ethernet
  • dc42

  211
  0
  Votes
  211
  Posts
  17367
  Views

  

  There is already support for a webcam, but it has to be an IP camera with a facility for returning a still jpeg image because browsers don't support RTSP. See https://duet3d.dozuki.com/Wiki/How_to_include_a_web_camera_image_in_Duet_Web_Control. There is no possibility of connecting a webcam directly to a Duet because the processor isn't powerful enough and the USB port is device-only.
• 

  Saving Baby stepping value
  • jckray

  17
  0
  Votes
  17
  Posts
  261
  Views

  

  Suppose I add an option on the M290 command to shift the current babystep offset into the G31 Z parameter, clear babystepping and adjust the Z=0 position to compensate? Then you could set up a macro to run that command and then send M501 P31 to write the new G31 command to config-override.g.
• 

  LCD support for the RADDS?
  • napierdmark

  4
  0
  Votes
  4
  Posts
  125
  Views

  

  If you want to give it a try, this is what you will need to do: Get the latest RADDS version building, using the dev branches of both RepRapFirmware and CoreNG. There are build instructions for the Mac in file buildinstructions.md. I didn't write it, so it may be a little out of date now. When that's working, switch to the v2-dev branch of RepRapFirmware and the main branch of CoreNG. That's where development is taking place at present. You will need to add the FreeRTOS and RRFLibraries projects, and port some changes into the RADDS-specific files in the CoreNG and RepRapFirmware projects. I can give you advice on that. You will also need to add a SAM3X build configuration to project RRFLibraries. We haven't supported RTOS on the SAM3X-based Duets because of shortage of RAM. However, as Due/RADDS does not have a network interface, there should be sufficient RAM saved by not having the network stack.
• 

  Duet Maestro Freefall
  • LeonMF

  51
  0
  Votes
  51
  Posts
  1371
  Views

  

  @leonmf Can you add a friction break? A solenoid that retracts a brake when the table is free to move but automatically re-engages when power is lost (or the driver is not enabled).
• 

  Print fan speed override
  • LHelge

  3
  0
  Votes
  3
  Posts
  69
  Views

  

  Sounds even better! Then it could be set up in the filament load macro to run the fan different on different printers with the same filament profile in the slicer. Something similar for hotend and bed temperature would be super as well. Right now I need to have one filament profile in my slicer for each printer due to different temperature needs. It would be cool to be able to override those temperatures as well with a gcode that I can put in my filament load macro.
• 

  S-Curve/ sinusoidal , Jerk +acceleration
  • mak

  34
  0
  Votes
  34
  Posts
  2618
  Views

  

  @stewwy the option to select which acceleration type is used is part of the plan.
• 

  Linear ADC Thermocouple Improvements
  • AJ Quick

  6
  0
  Votes
  6
  Posts
  156
  Views

  

  Pull request submitted: https://github.com/dc42/RepRapFirmware/pull/213 I hope you find it agreeable! (I also added a bit for selecting between single and differential channels)
• 

  Make use of variables
  • Googliola

  32
  2
  Votes
  32
  Posts
  701
  Views

  

  I really like your proposal, dc42. I have only one immediate use-case that I would want to employ: check current z height, and raise then lower bed to switch IDEX tools and avoid obstacles near the bed perimeter, if current z height is insufficient to clear said obstacles. This would have to be located in the actual print gcode files, in the tool switching script. I don't see any problem with doing this, based on your proposal, but just wanted to mention a use-case that would have the script inside a gcode file for printing. edit: Upon further reflection, these commands could be contained in the firmware-based macro tool change scripts. I was thinking of a case of using slicer based tool change scripts, but that would not be necessary. Ignore my stated use case of scripts in a printable gcode file.
• 

  Extend M929 logging capabilities
  • Googliola

  6
  0
  Votes
  6
  Posts
  124
  Views

  

  @dc42 having everything that goes to the console in the log (when configured to do so) + every debug output (when similarly configured) would be the best option. At all times as well not just when printing from SD. As long as there is sufficient bandwidth to write to the SD at the same time as reading. may need a RAM buffer.
• 

  More options for Stall detection
  • jckray

  3
  2
  Votes
  3
  Posts
  139
  Views

  

  Awesome, thank you!
• 

  new function whish list
  • chris33

  3
  0
  Votes
  3
  Posts
  123
  Views

  

  Yeah, maybe you can replace the layer graph. for a toolpad preview .
• 

  M558 F parameter only applied during approaching of probe
  • Googliola

  13
  0
  Votes
  13
  Posts
  182
  Views

  

  The X40 and Y-40 move is basically to negate the nozzle offset of the BLTouch, so that I am probing the same spot that the nozzle actually touches. The bed move by 10 was basically done to ensure enough clearance and dive height while I was still narrowing down the dive height. It also gives a longer dive height to allow for the probe to settle. That plus the lower speeds is an attempt to give the probe the best chance of getting a repeatable measurement. I also have a macro for manual bed leveling and then another for mesh grid measurement. I don't run these very often, but they are nice to have when you need them. 1_1538593590722_0_Grid Compensation Assist.g 0_1538593590721_0_Auto Bed Level Assist.g And there's also this bundle for tuning: https://forum.duet3d.com/topic/6181/tuning-macros-menus-accel-jerk-retraction-pressure-advance
• 

  Could there be a possibility to set motor currents per drive?
  • deckingman

  9
  0
  Votes
  9
  Posts
  170
  Views

  

  @dc42 Oh that's excellent! Thank you.
• 

  WiFi module auto reconnect
  • Drammy

  8
  0
  Votes
  8
  Posts
  655
  Views

  

  I also looking forward to this
• 

  Plugins
  • fma

  1
  1
  Votes
  1
  Posts
  75
  Views

  No one has replied

• 

  Real-time encoder adjustments for Generic LCDs
  • bass4aj

  1
  0
  Votes
  1
  Posts
  61
  Views

  No one has replied

• 

  Pause/Stop AND Resume
  • my67nova

  24
  0
  Votes
  24
  Posts
  1579
  Views

  

  @phaedrux 👍Thanks - made me smile.
• 

  Gcode file check.
  • Agniusm

  6
  0
  Votes
  6
  Posts
  104
  Views

  

  A clue is that if PanelDue or DWC can't tell you the amount of filament required by the print, the file may be incomplete. This used to be a particular problem with slic3r, because when writing the file it doesn't keep it open in exclusive mode, making it possible for you to upload it to the Duet before slic3r has finished writing it. I don't know if that has changed since I last used slic3r about 2 or 3 years ago.
• 

  Add Drive/Extruder Parameter to M207
  • BMMal

  7
  0
  Votes
  7
  Posts
  232
  Views

  

  @dc42 said in Add Drive/Extruder Parameter to M207: It sounds like per-tool is the way to go, but this feature still needs to be specified. Assuming that I add an additional parameter to specify the tool number: Should a M207 command that doesn't specify a tool number affect only the current tool? Or all tools? Or something else? If no parameter is given it should be the global default but not overwrite any tools that were explicitly configured. This way M207 can be in config.g without a tool parameter to give a good starting point for all tools or just to set them for single extrusion setups or users who do not have independent settings for materials. Then, the beginning of a gcode file would include the more specific configuration depending on what is set in the slicer custom gcode. This would also allow for the current behavior to be mimicked if no tool numbers are ever specified. If a second print is run without resetting the firmware, then the second file would contain the specific M207 tool configs for that print and update them as needed. When a new tool is created, what M207 parameters (if any) should it inherit? I think it should inherit the global default since this is how the current implementation would behave. I don't want to break the current behavior as it is working well for me now and I know for other people. I just want to add the possibility of having it be configured per tool to allow me to expand into other slicers while still reducing the amount of manual configuration I have to do for each print/material.
• 

  Can Duet compensate for unmatched ditto mode extrusion rates?
  • sle

  3
  0
  Votes
  3
  Posts
  79
  Views

  

  You should also be able to set different extrusion multipliers using the sliders in Duet Web Control or the extrusion multipliers in PanelDue, because the underlying M221 GCode command allows the extrusion multiplier to be set per extruder drive.