Firmware wishlist

• 

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

  209
  0
  Votes
  209
  Posts
  14822
  Views

  

  @dc42 Completely understand that! Thanks. I'll have a look over that after having a better look at the most recent RC for 2.0 at work next week.
• 

  6th-order jerk-controlled motion planning
  • dragonn

  110
  1
  Votes
  110
  Posts
  4243
  Views

  

  @rcarlyle I've been wanting to try playing around with Klipper using the duet as the MCU. Best of both worlds if you will. Best in class electronics and very high steps rates. If klipper succeeds in implementing s curve motion planning before the duet I will probably give it a shot.
• 

  M106 Maximum Fan Speed Setting
  • wilriker

  10
  0
  Votes
  10
  Posts
  130
  Views

  

  @deckingman I changed my start- and end-code inserted to the slicer to be only M98 P/sys/print_start.g and M98 P/sys/print_end.g respectively. That already reduced a lot of times where I would otherwise have needed to re-slice something. I can even edit these files while the printer is still heating. I just want to push this some steps further.
• 

  Status-based fan mode
  • wilriker

  6
  0
  Votes
  6
  Posts
  139
  Views

  

  @dc42 said in Status-based fan mode: This one could maybe be simplified by using the already existing virtual heater channel for the drivers that currently reports 0°C in case of no warning and 100/150°C in case of warning or overheating. I have not checked the code base in this regard but I have the feeling this could maybe extended in a way where 0°C means drivers are off, 50°C (or any other value between 0 and 100) means drivers are on but everything OK and 100/150°C keep their current meaning. That's an interesting idea, I'll give it some thought. I created https://github.com/dc42/RepRapFirmware/pull/180 for this.
• 

  M106 - Feature Request, Limit MAX PWM parameter
  • gen2eng

  6
  0
  Votes
  6
  Posts
  178
  Views

  

  @dc42 So here is another user (me) M106 Maximum Fan Speed Setting - that just missed this thread.
• 

  Additional Parameter to Override Non-Linear Extrusion Interlock
  • DocTrucker

  4
  0
  Votes
  4
  Posts
  138
  Views

  

  Here's what I use, it's based on something David provided. G28 G1 X0 Y0 Z100 F5000 M83 G1 E5 F600 M400 M291 S3 R"Extrusion test" P"Press OK to start test" G1 X50 E50 F60 M400 M291 S3 R"Measure extrusion" P"Measure filament taken at 1mm/sec extrusion, then press OK" G1 X0 E50 F120 M400 M291 S3 R"Measure extrusion" P"Measure filament taken at 2mm/sec extrusion, then press OK" G1 X50 E50 F180 M400 M291 S3 R"Measure extrusion" P"Measure filament taken at 3mm/sec extrusion, then press OK" G1 X0 E50 F240 M400 M291 S3 R"Measure extrusion" P"Measure filament taken at 4mm/sec extrusion, then press OK" G1 X50 E50 F300 M400 M291 S3 R"Measure extrusion" P"Measure filament taken at 5mm/sec extrusion, then press OK" G1 X0 E50 F360 M400 M291 S3 R"Measure extrusion" P"Measure filament taken at 6mm/sec extrusion, then press OK" G28
• 

  JIMOU Sensor Wiring/Configuration
  • doubleoerik

  5
  0
  Votes
  5
  Posts
  359
  Views

  

  @droneon said in JIMOU Sensor Wiring/Configuration: @dc42 Would it be possible to use the thermistor wire of the sensor, connected to a spare thermistor port, to adjust the trigger offset for temperature variations? I guess this would actually be a new feature request. Yes it would be a new firmware feature. Currently the trigger height can be made to vary with bed thermistor temperature, but not with any other temperature reading.
• 

  Change V_Fan Select Header to 3 Way Plug
  • DocTrucker

  2
  0
  Votes
  2
  Posts
  60
  Views

  

  I used a single DuPont connector and it seemed to wedge very tightly onto the pin.
• 

  Pause and resume within a macro
  • balrags

  7
  0
  Votes
  7
  Posts
  192
  Views

  

  The nologo versions should work as-is too.
• 

  Please move "Estimator" tracking and calculations to firmware
  • Yonkiman

  2
  0
  Votes
  2
  Posts
  100
  Views

  

  The estimates are already generated and maintained by the firmware. So I am surprised that DWC isn't showing them. Reloading DWC might help.
• 

  Cancel print if mesh not level
  • totalitarian

  7
  0
  Votes
  7
  Posts
  261
  Views

  

  @totalitarian said in Cancel print if mesh not level: Did this ever get implemented? Not yet, it's waiting for support for conditional GCode commands to be added first.
• 

  Driver order and slave axis
  • Catalin_RO

  11
  0
  Votes
  11
  Posts
  174
  Views

  

  @catalin_ro said in Driver order and slave axis: @dc42 When talking to Chrishamm, could there be an extra set of jog buttons for 0.01mm steps? When properly aligning the gantry with the machined piece, sometimes it is very important. Right now I have to manually send G0 commands for that! All other CNC software include support for that. I think Chrishamm already said in a post in the DWC Wishlist section of this forum that he has it on his work list to make the jog increments configurable for all axes. In the meantime, you could set up macros to jog 0.01mm.
• 

  Dual Y axis and rotary A axis
  • Catalin_RO

  3
  0
  Votes
  3
  Posts
  87
  Views

  

  Initially I had P4 in the command and DWC kept crashing. For a test, I have added just the A4 to the M584 command to see how it goes. Again DWC crashed, even if the extra axis were hidden. So, based on that, I think the DWC is making the controller unusable in this scenario. For all other issues, consider the other related thread.
• 

  Using Stall detection as emergency shutdown?
  • kuhnikuehnast

  3
  1
  Votes
  3
  Posts
  172
  Views

  

  The circumstance as it happend was the following: Due to the broken Bltouch the bed leveled to high. So x and y moved and the nozzle scratched over the bed. So I think it would also be great for x and Y. Other problem could be: a print that doesn't stick to the bed and causes a crash of the nozzle.
• 

  Send event data to remote server
  • jeanmarc_Scaled

  5
  0
  Votes
  5
  Posts
  114
  Views

  

  Yeah, I think there are a lot of ways it could work. Accuracy? DWC polls four times a second today. I believe that's a bit much, but one second polls would certainly work, and would seem to give "accurate enough" stats. You probably already got this, but just to be super clear: I'm talking about an intermediate "marshaling point" for the farm, pulling from multiple printers, and pushing only aggregated stuff to the final repository server. And, again, probably lots of ways... Will be interesting to follow.
• 

  Manually Set the Number of 'Smart' Drivers
  • SnowCrash

  10
  0
  Votes
  10
  Posts
  239
  Views

  

  @dc42 said in Manually Set the Number of 'Smart' Drivers: The code already implements something similar except that the "other board" code is not present. I'll add this to the work list for firmware 2.01. Very cool! Thank you very much, @dc42
• 

  Empty Layers causing incorrect layer count
  • WarriorMe

  15
  0
  Votes
  15
  Posts
  460
  Views

  

  @warriorme said in Empty Layers causing incorrect layer count: Excuse me please for taking a bit longer than expected to try this out. I updated the firmware, but the issue persists. Not changing the printing temperature at all during the print hasn't fixed it either This is very strange, because the only situation I found kin which the layer count was not updated at the correct time was when the temperatures were not stable. Try 2.0RC6?
• 

  CNC/Laser: M3 unpause R parameter
  • resam

  2
  0
  Votes
  2
  Posts
  74
  Views

  

  That sounds very sensible. I have added it to the firmware work list.
• 

  G31 and temperature tables
  • carlosspr

  6
  0
  Votes
  6
  Posts
  198
  Views

  

  If people are using the temperature compensation feature, I'll leave it in.
• 

  Notification via Pushover or other service
  • jamesarm97

  45
  0
  Votes
  45
  Posts
  2786
  Views

  

  I have added Pushover notification support to the firmware work list. I need to get firmware 2.0 released before I implement this or any other new features.