Firmware wishlist and priorities for Duet WiFi and Duet Ethernet

DocTrucker

Can the switching mosfets on PS-ON be uprated to take 24V directly? 24V is more typically used in industrial saftey interlock systems and relays.

Last time I chevked they were only suitable for about 5V - which is the ATX ps on signal.

Catalin_RO

On the schematic I see that the PS_ON switch is PMV40UN2 (https://www.nexperia.com/products/mosfets/n-channel-mosfets-25-v-30-v/PMV40UN2.html). This is a 30V MOSFET. Even more, it is capable of quite some current (4.4A based on the datasheet) as it has a very low internal resistance.

PC PSUs use 5V for PS_ON pull-up as they have the 5V Vsb (stand-by). But you can have anything up to 30V pull-up without any problems.

DocTrucker

My bad, maybe I'm thinking of the old 0.6 boards and got muddled.

Catalin_RO

Duet 0.6 and 0.8.5 used BSH105 - 20V Vds and only 1A because of much higher internal resistance.

BenDiesel

@dc42
If I were to use M589: Configure access point parameters would it connect to my all ready networks and if no network create it's own? Or dose this override all existing networks?

DocTrucker

@catalin_ro Yes, checked the schematics myself to see where I'd got it from and planning the interlock loop for the Duet 0.6 was it. Only changes on the Duet2 boards has been the addition of a resistor on revision 1.02 between the gate of the MOSFET and the processor.

spw

7, 11, 6, 14, 15

dc42

@bendiesel said in Firmware wishlist and priorities for Duet WiFi and Duet Ethernet:

@dc42
If I were to use M589: Configure access point parameters would it connect to my all ready networks and if no network create it's own? Or dose this override all existing networks?

No, currently you use M552 to choose whether to run as a client or an access point.

DocTrucker

@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?

dc42

@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.

DocTrucker

@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.

DangerouslyExplosive

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

dc42

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.

Julek

10,12 would be my choice as hysteresis compensation makes definitly sense for cnc machines having a rather stiff construction

gavatron3000

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

fotomas

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.

SJI

@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

Phaedrux

@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 M0

https://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.

David Green

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.

mwinterm

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....