7h7 makes multitool printers. Previously they used Smoothieware, now Duet.

What are possible heating element voltage and power for DIY pellet extruders?

This bit goes in your config.g

Mine is before the Endstops section
;BLTOUCH CONFIG; Z-Probe
M574 Z1 S2 ; Set endstops controlled by probe
;M558 P9 H5 F120 T6000 ; Set Z probe type to bltouch and the dive height + speeds
M558 P9 H5 F120 T6000 A10 R0.75 S0.02
;G31 P500 X40 Y-13 Z0.340 ; Set Z probe trigger value, offset and trigger height
G31 P25 X40 Y-13 Z0.853 ;453 ;940 ;744 ;817 ;981 ;0.842 ;1.265 ;1.286 ;403 ;377
M557 X40:220 Y15:220 S20 ; Define mesh grid

This is in my bed.g
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation

deployprobe.g
M280 P64 S10

homeall.g
; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Apr 08 2019 10:31:02 GMT+0100 (British Summer Time)
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
;M98 Pdeployprobe.g ; deploy mechanical Z probe
G1 S1 X-240 Y-240 F1800 ; move quickly to X and Y axis endstops and stop there (first pass)
G1 X5 Y5 F6000 ; go back a few mm
G1 S1 X-240 Y-240 F360 ; move slowly to X and Y axis endstops once more (second pass)
G90 ; absolute positioning
G1 X122 Y122 F6000 ; go to first bed probe point and home Z
G30 ; home Z by probing the bed

homex.g
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 X-240 F1800 ; move quickly to X axis endstop and stop there (first pass)
G1 X5 F6000 ; go back a few mm
G1 S1 X-240 F360 ; move slowly to X axis endstop once more (second pass)
G1 Z-5 F6000 S2 ; lower Z again
G90 ; absolute positioning

homey.g
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G1 S1 Y-240 F1800 ; move quickly to Y axis endstop and stop there (first pass)
G1 Y5 F6000 ; go back a few mm
G1 S1 Y-240 F360 ; move slowly to Y axis endstop once more (second pass)
G1 Z-5 F6000 S2 ; lower Z again
G90 ; absolute positioning

homez.g
G91 ; relative positioning
G1 Z5 F6000 S2 ; lift Z relative to current position
G90 ; absolute positioning
G1 X122 Y122 F6000 ; go to first probe point
G30 ; home Z by probing the bed

retractprobe.g
M280 P64 S90

That is about it for setting up the BL Touch.
Please make sure it is wired correctly as per this.
https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch

My printer was an ender 3 Pro. You will need to measure the offset for the probe.

HTH Paul.

I do it the opposite way. I always edit stuff on my pc and upload changes. I made a script to automate that. You can find it at https://github.com/token47/duetcfgen

It works on linux, cygwin and WSL.

OK.. it´s old.. but...

A workaround ist.. define the 2. FAN.. as Thermostatic controled.. and it´s gone in WBC.
Reason.. you can´t control a thermostatic controlled FAN

@minim said in Question about DWC v2xx:

You can also use the old interface when you run dwc2.0RC7. Just add "/reprap" behind the link. I do that since I find the old easier to use.

Thanks for that info.

So far I'm liking the new layout.

Frederick

As others have said, M28 ignores comments in commands. Like you can (probably, I haven't tried) send console commands with comments, but they are lost as soon as the command is sent.

I can see why you might want to do this (maybe for logging?), but it's probably easiest to write the gcode file in a text editor, then send each line by copying and pasting that into your terminal program (I assume that's how you're connecting). Then you'd have a local editable copy of the file from the SD card, with comments. Or remove the SD card from the Duet, copy the file onto it locally, then replace it in the Duet.

Ian

here is a more detailed guide.
https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware

use the Duet2CombinedFirmware.bin in that case.

https://duet3d.dozuki.com/Wiki/Gcode#Section_M584_Set_drive_mapping

VERY IMPORTANT! Assigning a drive using M584 does not remove its old assignment. Therefore, if you assign a drive that defaults to being an extruder drive, you should also assign the extruder drives explicitly as in the above example. Failure to do so may result in unexpected behaviour.

you are not unassigning the Y from the extruder. this will cause strange behaviour.

Thats interesting, most network equipment only cache the mac to ip mapping for a few minutes (with the exception of the dhcp server). Would be interesting to see if a new reservation causes new problems or if it was a one off.

@dc42 ,

any thing else I need to do?
I can confirm that this issue exists with DuetWiFIServer 1.22 and Duet FW 2.02 as well.

THanks,
Madhu.

Check your config-override for M305 commands

I have it connected to Endstop for E0.
DWC does not report the sensor, but it does appear in M112:

=== Filament sensors === Extruder 0: pos -1.74, ok, measured min 61% avg 76% max 96% over 3368.6mm, errs: frame 6 parity 0 ovrun 0 pol 0 ovdue 0

Im assuming since its not a switch and a laser filament sensor its not reporting as expected in the json.

All good will try and work around it.

Supply voltage: min 23.3, current 24.1, max 24.6, under voltage events: 0, over voltage events: 0,
Supply voltage: min 20.7, current 23.9, max 24.8, under voltage events: 0, over voltage events: 0, power good: yes

There was no undervolt event in both cases. Though a drop to 20V is significant. This could mean that either the psu is not enough for your setup, or its damaged.

@ram yes you can push files to the Duet but it can't go out and "pull" them (at least with Duet 2). Duet 3 OTOH will allow for a plugin to be written on the SBC that does that.

Yes, there is DEFINITELY something WRONG with filament estimating. This job did have wipe on retract checked, in a different slicer.

I really thought it was a "wait for it to converge" when other people posted. It is not. This job said "n/a" under filament for about 10 hours, then went to ridiculous numbers like shown. And, by the way, it did finish eight or nine minutes after this photo.

0_1565042374664_IMG_0657 (2).jpeg

Uh...never mind... my lack of knowledge. Just put in the proper address for my Duet and everything is running fine.

I would think its safe to say any consumer or nat capable router has built in dns server, what sets them aside is the dhcp and dns server talking to each other (or in the case of openwrt w/dnsmasq, being the same server daemon)