Duet 3 hc6 firmware '''issues''
-
It only takes the routter asigned dynamic IP nothing else
-
@Torppa can you update the firmware? You’re on a beta version. Either 3.0, or the latest 3.01-RC6 will be fine.
Ian
-
Probably could, how ever the printter sits in one place and weighs around 47kg, i dont have a reliable laptop and the printter is build so the aces to the duet is under it in a metal enclosure.
I would avoid mooving it around since ill most likely drop it sooner or later.
-
?
if you can access the SD card and YAT, put the firmware file on the sd card and upgrade using YAT. (or if DWC is stable with the dynamic address, just upload the firmware and let it do the upgrade).
Kinda difficult to say what to do when information isn't forthcomming.
-
Ill try updating via DWC, i hope it works since this is starting to feel like a job and i dont need a second one.
Thanks for the help.
-
Witch one of these i need to update?
-
https://github.com/dc42/RepRapFirmware/releases/tag/3.0
Duet3Firmware_MB6HC.bin
and these for good measure
Duet3_SDiap_MB6HC.bin
DuetWebControl-SD-2.04.zipput the files in the /sys folder if transfered using the sd card, if uploading to dwc it will put it in the right place when you upload and ask you to update.
if using YAT then you need to run
M997 S0:2
after having placed the files on the sd card -
(but I'm a little concerned what happens if the SD card glitches during the update. recovery should be possible with bossa but more hassle.)
-
@bearer
Sounds fun! cant wait for this to happen, if so how far do you bet an average guy could throw the thing lets not take wind into consideration.
-
@Torppa what version of DWC are you using? If 1.22.6 I wonder if there’s an issue using the old version with RRF3 and Duet 3.
Ian
-
I'd put the files on the sd card, disconnect the network, put the sd card back before powering up the board again and issue the M997 command on the terminal.
should reduce the odds of anything going a miss, and if it does you can follow these instructions for recovery https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware
-
Its 2.0.4
-
And its broken now, no lights no nothing. dont care anymore worst purchase so far trying to be civil so no anger, its hard... wasted basicly 260eur... POS is going to the land fill probably... well atleast my home insurance covers it so i dont haveto fight duet3d over it.
-
Sigh, I can understand the frustration; but unless the board was damaged the update shouldn't render it unrecoverable.
And the update would only have affected one LED, the two indicating 5v and 3.3v are hardwired to the power rails - if they don't work something other than an failed update occured.
If you find the will to keep at it; high resolution picture if the board would be helpfull in determining the cause.
-
Got it to ''work'' again how ever Z and Y axis are reversed, the weird part is that DWC has no trouble homing only when manuly G1 Y34 F3000 Its the Z axis that mooves. The is something weird going on.
-
I guess that implies it was never broken.
Maybe its time to sit down and do some reading.
-
@Torppa Post your config.g and home all.g.
Check you have connected the Y and Z motors to the correct driver as per your M584 command, the physical order of the drivers on the board isn’t necessarily what you expect; it’s
0 1 2
5 4 3So driver 3 is behind driver 2, not behind driver 0.
See the wiring diagram here: https://d17kynu4zpq5hy.cloudfront.net/igi/duet3d/TF1FBCbopEsxvYAv.huge
Ian
-
on 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v2.1.8 on Thu Apr 09 2020 16:09:20 GMT+0300 (Itä-Euroopan kesäaika); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"My Printer" ; set printer name; Network
M551 P"***********" ; set password
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0.1 S0 ; physical drive 0.1 goes backwards
M569 P0.0 S0 ; physical drive 0.0 goes backwards
M569 P0.2 S0 ; physical drive 0.2 goes backwards
M569 P0.3 S0 ; physical drive 0.3 goes backwards
M584 X0.1 Y0.0 Z0.2 E0.3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E409.00 ; set steps per mm
M566 X600.00 Y600.00 Z12.00 E300.00 ; set maximum instantaneous speed changes (mm/min)
M203 X15000.00 Y15000.00 Z180.00 E3600.00 ; set maximum speeds (mm/min)
M201 X2800.00 Y2800.00 Z100.00 E250.00 ; set accelerations (mm/s^2)
M906 X2600 Y2600 Z2600 E1197 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X670 Y620 Z430 S0 ; set axis maxima; Endstops
M574 X1 S1 P"io1.in" ; configure active-high endstop for low end on X via pin io1.in
M574 Y1 S1 P"io0.in" ; configure active-high endstop for low end on Y via pin io0.in
M574 Z1 S1 P"io2.in" ; configure active-high endstop for low end on Z via pin io2.in; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"io7.in" H5 F120 T2400 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X0 Y0 Z2.5 ; set Z probe trigger value, offset and trigger height
M557 X15:215 Y15:195 S20 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T97700 B4619 C9.743561e-8 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M143 H1 S285 ; set temperature limit for heater 1 to 285C
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit; Fans
M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency
M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off
M950 F2 C"out9" Q500 ; create fan 2 on pin out9 and set its frequency
M106 P2 S1 H-1 ; set fan 2 value. Thermostatic control is turned off; Tools
M563 P0 S"Hotend" D0 H1 F0 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss -
The fans are cooling the steppers, aiming to print mostly nylon ans ASA, duet has a fan 240v for cooling. dont knoiw if this is abit mad for my first 3d printter
-
@Torppa said in Duet 3 hc6 firmware '''issues'':
M584 X0.1 Y0.0 Z0.2 E0.3 ; set drive mapping
So motor wires are connected like this?
Y0 X1 Z2 5 4 E3
I've just been playing around with the networking on a standalone Duet 3. This in my config.g works for me to set a static IP address:
; Network M552 P192.168.0.28 S1 ; enable network and set IP address M553 P255.255.255.0 ; set netmask M554 P192.168.0.1 ; set gateway M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet
I can connect to the DWC, edit the IP address and reset, and the IP address will move to the new IP address.
I can also connect when starting up without an SD card inserted. Start up, connect via USB with Serial terminal (in this case Pronterface, as I'm on a Mac):
Connecting... Printer is now online. >>>M115 >SENDING:M115 >FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.01-RC4 ELECTRONICS: Duet 3 MB6HC v0.6 or 1.0 FIRMWARE_DATE: 2020-03-16b1 >>>>M552 SENDING:M552 Ethernet is disabled, configured IP address: 0.0.0.0, actual IP address: 0.0.0.0 >>>M553 P255.255.255.0 SENDING:M553 P255.255.255.0 >>>M554 P192.168.0.1 SENDING:M554 P192.168.0.1 >>>M553 SENDING:M553 Net mask: 255.255.255.0 >>>M554 SENDING:M554 Gateway: 192.168.0.1 >>>M552 P192.168.0.28 S1 SENDING:M552 P192.168.0.28 S1 Ethernet running, IP address = 192.168.0.28 >>>M552 SENDING:M552 Ethernet is enabled, configured IP address: 192.168.0.28, actual IP address: 192.168.0.28 >>>M552 S0 SENDING:M552 S0 Network stopped >>>M552 P192.168.0.69 S1 SENDING:M552 P192.168.0.69 S1 Ethernet running, IP address = 192.168.0.69 >>>M552 SENDING:M552 Ethernet is enabled, configured IP address: 192.168.0.69, actual IP address: 192.168.0.69
I can ping all the addresses I set, even when running with no SD card. I did make sure to send the subnet mask and gateway before the static IP address and enabling the network, though. This is with firmware 3.01-RC4.
So I can't replicate the problem you are seeing.
Ian