Firmware wishlist and priorities for Duet WiFi and Duet Ethernet
-
@doctrucker said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:
@dc42 said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:
...I'll stat a new wishlist soon...The last numbered list of items is from October 2017?
Yes, I'll do a new list after firmware 2.0 is released.
-
@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.
-
1
2
Add support for webcam, for time-lapse and live print monitoring (That's like half the point of a WiFi printer anyway, so I don't have to go down there to check if my printer has malfunctioned)
-- Note that I only have 1 and 2 before the camera because it would be a good idea to make it hard for hackers to get access to a camera within my house.
15
11 -
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.
-
10,12 would be my choice as hysteresis compensation makes definitly sense for cnc machines having a rather stiff construction
-
My wishlist:
Move axis till endstop or input reached. If not made by "X"mm then pause
Also be able to invert the endstop or input depending on desired condition -
end.g
An optional system file, run at end of each print, instead of adding end code in slicer. I would use it to lift the print head and move the table to a position for removing the printed part.
I think those moves are more of a system setting than a print move. There fore it would be nice to have it set in the printer instead of a slicer setting.
-
@fotomas said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:
end.g
An optional system file, run at end of each print, instead of adding end code in slicer. I would use it to lift the print head and move the table to a position for removing the printed part.
I think those moves are more of a system setting than a print move. There fore it would be nice to have it set in the printer instead of a slicer setting.
In the end tab of the slicer i would add M98 Pend.g
-
@fotomas This already exists in the form of M0 and stop.g
; stop.g
; called when M0 (Stop) is run (e.g. when a print from SD card is cancelled)
; Also called by slicer end gcode by M0https://duet3d.dozuki.com/Wiki/Macros#Section_Pause_stop_and_power_fail
https://duet3d.dozuki.com/Wiki/GCode#Section_M0_Stop_or_Unconditional_stop
In my stop.g file I do all the end of print things like moving the head away from the print, maxing the part fan, turning off the heaters, etc. Then i the slicer end gcode I just have M0. That way whichever slicer I'm using stog.g gets used and I only have to make changes in one place. I do the same with start.g which gets run before a print starts.
-
No. 2 5 14. I would like to keep the G32 auto bed level as a fast check on anything moving when removing a stuck print. I have a CoreXY and it can slip the 2 motors out of position.
-
7, 10, 12, 14, 18,
would be my my wish list. However didn't put 4, 8, 19, 20 on my list as a think that is already working:
4 -> assigning 2 motors to one axis, separating them for homing and re-assembling them again with M584
8 -> M906 ..... I30 for current reduction
19 -> M80/M81 to turn ATX off
20 -> someting like M106 P2 T45:65 H100:101:102 .....Regarding better CNC support (12) my specific priorities would be:
- Safe tool-offsets and WCS so that they are still in place after restarting (similar to bed compensation)
- Modify M584 for tool measurement as I already proposed (implemented in my personal branch)
- Extend G30 with an S-3 option to allow for WCS probing (implemented in my personal branch)
- Allow macros to ask for input like position, tool-number, WCS-number....
- More frequent update of the position in the PanelDue / Webinterface (something like 10 HZ update frequency)
- Support for conditions, loops and parameters in Gcode
- Support canned cycles like G73-G89 in the form that they can be defined in e.g. G73.g ... files like for homing, cancel, resuming....
-
Ability to assign end stops to axes (especially useful for machines with "more than the norm" number of axes). Or more precisely the ability to assign end stops other than the default assignments.
Talking to Tony some time back when I was trying to get CoreXYUVnn (where nn could be AW) working, I'm fairly sure this is on the road map but it doesn't appear in this thread so I thought I'd mention it here so it doesn't get overlooked.
-
I don't know if it would be possible, but I would like to have Fanuc compatible gcode when in CNC mode. That would enable to use the vast majorities of CAM softwares available since all of them have a Fanuc post processor.
-
I thought Fanuc machines were rotary CNC machines - am I wrong?
-
@dc42 Fanuc is the standard in high quality CNC machine controllers, the are others, but Fanuc is the most used one.
They make controllers for mills and lathes, and also for all kinds of CNC machines (robots, press, EDM, wire EDM, etc...) -
@3doeste, can you list the most important Fanuc GCode commands that RRF doesn't yet support?
-
@dc42 I think the major difference is how G0 and G1 commands are used, since on industrial controllers you only used G0 and G1 once, and all the following blocks asume the last parameter until a G0 or G1 command is issue again. That allows for less data transfer (wich industrial controllers are the worst in this matter, specially older ones) and to separately tune rapid feed rates and cutting feed rates on the fly.
Canned cicles are useful but you can write all the cicle from the CAM itself, so no problem there.I attached a simple offset flat strategy, without arcs, so you can see how a Fanuc post looks like. In this case it has the block numbers, but they can be removed to decrease data transfer rates .
-
@3doeste said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:
I think the major difference is how G0 and G1 commands are used, since on industrial controllers you only used G0 and G1 once, and all the following blocks asume the last parameter until a G0 or G1 command is issue again.
What you are saying is that you can just repeat the X and/or Y coordinates without repeating the G0 or G1 command. I'll add that to the firmware wishlist.
-
@dc42 That's right! After a G0 or G1, all the following coordinates use the last parameter, you can even change the feed without changing the G1 or G0 status (well, on industrial CNCs the G0 has no feed value, since it's given by the machine, and all you do is lower it by 50%, 25%, and to feed values).
-
@gavatron3000 said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:
My wishlist:
Move axis till endstop or input reached. If not made by "X"mm then pause
Also be able to invert the endstop or input depending on desired conditionForgot to add this request is to help with making the MMU2 work as intended with respect to detecting loading and unloading issues. This way I run it with the duet electronics and not use the prusa Arduino.
Cheers
Gav