Setup Duet 3 Config no tools shown



  • I have just created a new config. But you don't see anything.
    Why ?
    What am I doing wrong?
    In the Duet web interface.
    (Raspberry)

    config new.zip.txt

    config.json

    I currently only connected the heating bed and its temperature sensor.
    So that I can see if it works.
    Then I wanted to connect the motors, etc.

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0beta12 running on Duet 3 MB6HC
    Board ID: 
    Used output buffers: 2 of 32 (5 max)
    === RTOS ===
    Static ram: 122240
    Dynamic ram: 171824 of which 40 recycled
    Exception stack ram used: 248
    Never used ram: 98864
    Tasks: NETWORK(ready,2044) HEAT(blocked,1208) CanReceiv(suspended,3804) CanSender(suspended,1480) CanClock(blocked,1428) TMC(blocked,216) MAIN(running,4212) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:18:04 ago, cause: power up
    Last software reset at 2020-07-22 22:18, reason: Unknown, spinning module Platform, available RAM 98848 bytes (slot 0)
    Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 not detected, interface speed: 37.5MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 40.4, current 44.5, max 44.6
    Supply voltage: min 23.7, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
    12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
    Driver 0: standstill, reads 31583, writes 14 timeouts 0, SG min/max 0/0
    Driver 1: standstill, reads 31584, writes 14 timeouts 0, SG min/max 0/0
    Driver 2: standstill, reads 31585, writes 14 timeouts 0, SG min/max 0/0
    Driver 3: standstill, reads 31585, writes 14 timeouts 0, SG min/max 0/0
    Driver 4: standstill, reads 31589, writes 11 timeouts 0, SG min/max 0/0
    Driver 5: standstill, reads 31590, writes 11 timeouts 0, SG min/max 0/0
    Date/time: 2020-07-22 22:37:31
    Slowest loop: 6.03ms; fastest: 0.25ms
    === Move ===
    Hiccups: 0, FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
    Bed compensation in use: none, comp offset 0.000
    === MainDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === AuxDDARing ===
    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    Movement lock held by null
    http* is ready with "M122" in state(s) 0
    telnet is idle in state(s) 0
    file is idle in state(s) 0
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon* is idle in state(s) 0
    queue is idle in state(s) 0
    lcd is idle in state(s) 0
    spi is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 0.53ms; fastest: 0.01ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 0 of 8
    - Ethernet -
    State: 0
    Socket states: 0 0 0 0 0 0 0 0
    === CAN ===
    Messages sent 4259, longest wait 0ms for type 0
    === Linux interface ===
    State: 0, failed transfers: 2
    Last transfer: 20ms ago
    RX/TX seq numbers: 1860/34130
    SPI underruns 0, overruns 0
    Number of disconnects: 1
    Buffer RX/TX: 0/0-0
    === Duet Control Server ===
    Duet Control Server v3.1.1
    Code buffer space: 4096
    Configured SPI speed: 8000000 Hz
    Full transfers per second: 25.93
    


  • @roth I am using a tablet and cannot read your zip file, maybe you can post it in a readable format please.



  • config.g

    ; Configuration file for Duet 3 (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Jul 22 2020 23:16:26 GMT+0200 (Mitteleuropäische Sommerzeit)
    
    ; General preferences
    G90                                                ; send absolute coordinates...
    M83                                                ; ...but relative extruder moves
    M550 P"Duet 3"                                     ; set printer name
    M665 R155 L397.19 B155 H520                        ; Set delta radius, diagonal rod length, printable radius and homed height
    M666 X0 Y0 Z0                                      ; put your endstop adjustments here, or let auto calibration find them
    
    ; Drives
    M569 P0.0 S1                                       ; physical drive 0.0 goes forwards
    M569 P0.1 S1                                       ; physical drive 0.1 goes forwards
    M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
    M569 P0.3 S1                                       ; physical drive 0.3 goes forwards
    M584 X0.0 Y0.1 Z0.2 E0.3                           ; set drive mapping
    M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z80.00 E403.00                   ; set steps per mm
    M566 X1200.00 Y1200.00 Z1200.00 E1200.00           ; set maximum instantaneous speed changes (mm/min)
    M203 X18000.00 Y18000.00 Z18000.00 E1200.00        ; set maximum speeds (mm/min)
    M201 X1000.00 Y1000.00 Z1000.00 E1000.00           ; set accelerations (mm/s^2)
    M906 X1200 Y1200 Z1200 E1200 I30                   ; set motor currents (mA) and motor idle factor in per cent
    M84 S30                                            ; Set idle timeout
    
    ; Axis Limits
    M208 Z0 S1                                         ; set minimum Z
    
    ; Endstops
    ; WARNING: No endstops configured
    
    ; Z-Probe
    M950 S0 C"io4.out"                                 ; create servo pin 0 for BLTouch
    M558 P9 C"^io4.in" H5 F120 T6000                   ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X0 Y20 Z0                                 ; set Z probe trigger value, offset and trigger height
    M557 R150 S45                                      ; define mesh grid
    
    ; Heaters
    M308 S0 P"temp0" Y"thermistor" T100000 B4138       ; 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
    M307 H0 B1 S1.00                                   ; enable bang-bang mode for the bed heater and set PWM limit
    M140 H0                                            ; map heated bed to heater 0
    M143 H0 S120                                       ; set temperature limit for heater 0 to 120C
    M308 S1 P"temp1" Y"thermistor" T100000 B4138       ; 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
    M307 H1 B0 S1.00                                   ; disable bang-bang mode for heater  and set PWM limit
    
    ; Fans
    M950 F0 C"out8" Q500                               ; create fan 0 on pin out8 and set its frequency
    M106 P0 S0 H-1                                     ; set fan 0 value. Thermostatic control is turned off
    M950 F1 C"out9" Q500                               ; create fan 1 on pin out9 and set its frequency
    M106 P1 S1 H1 T45                                  ; set fan 1 value. Thermostatic control is turned on
    
    ; Tools
    M563 P0 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
    M575 P1 S1 B57600                                  ; enable support for PanelDue
    M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
    
    
    


  • @roth thanks a lot, now I can look at it!



  • @roth what you can do as first step is to validate whether the config is valid by calling
    M98 P"config.g"
    and check for errors. I don't see an error at first view.



  • @JoergS5 said in Setup Duet 3 Config no tools shown:

    M98 P"config.g"

    Error: Bad command: Q0 @"Miscellaneous"
    23.7.2020, 00:22:53 	M98 P"config.g"
    Error: Bad command: Q0 @"Configuration file for Duet 3 (firmware version 3)"
    Error: Bad command: Q0 @"executed by the firmware on start-up"
    Error: Bad command: Q0 @"Drives"
    Error: Bad command: Q0 @"Axis Limits"
    Error: Bad command: Q0 @"Endstops"
    Error: Bad command: Q0 @"WARNING: No endstops configured"
    Error: Bad command: Q0 @"Z-Probe"
    Error: Bad command: Q0 @"Heaters"
    Error: Bad command: Q0 @"Fans"
    Error: Bad command: Q0 @"Tools"
    23.7.2020, 00:22:53 	Error: Bad command: Q0 @"Custom settings are not defined"
    23.7.2020, 00:22:53 	Warning: heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 365C.
    23.7.2020, 00:22:52 	Error: Bad command: Q0 @"General preferences"
    23.7.2020, 00:22:52 	Error: Bad command: Q0 @"generated by RepRapFirmware Configuration Tool v3.1.4 on Wed Jul 22 2020 23:16:26 GMT+0200 (Mitteleu"
    23.7.2020, 00:22:52 	Error: Bad command: Q0 @""
    


  • @roth strange, it interpretes the comments as G-Code



  • Ok thanks for your Help. I know something is wrong.





  • @roth despite the errors it seems to process the config, so you can try appending T0 at the end of the config.



  • I do not understand that.
    Just insert T0 at the end of the config code?



  • @roth yes, to select the tool



  • no change



  • === Diagnostics ===
    RepRapFirmware for Duet 3 MB6HC v0.6 or 1.0 version 3.0beta12 running on Duet 3 MB6HC

    Apparently something is wrong.
    The board is new.
    I wonder why there is a beta version on it.
    I only used the iso for the Raspberry.



  • @roth so you should update to 3.1.1

    Even a new board can lay around at some vendor. And 3.0beta12 is not very old (maybe 2 months)

    You can get the newest binaries from
    https://github.com/Duet3D/RepRapFirmware/releases



  • Yes i tried.
    Nothing changes in the version.
    I have to try that without Raspberry.



  • I have write the image new to the mico sd. And I tried to update to version 3.0 via the web interface. But it doesn't work, please wait while updates are being installed .
    And when i start all new the old firmware is on the board.



  • @roth From time to time (usually after an emergency stop), my tools + bed heater also don't show up in DuetWebControl.

    I've fixed this by:
    1). backing up my current config
    2). opening config.g in DWC and deleting all contents
    3). Paste the contents back in using my back-up

    I don't know why I have this problem, or why these steps seem to fix it.

    Or maybe just reuploading the config would work too.


  • Moderator

    To update the Duet 3 with SBC, you will need to use the pi as described here:

    https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Updating_Duet_3_main_board_firmware

    sudo apt update
    sudo apt upgrade

    3.1.1 should be your first step in getting up and running.



  • Yes but after that the Firmware on the board are the same. Update not work.


  • Moderator

    Ah, I'm afraid that beta 12 had some problems with updating sometimes. In the link I posted above the section directly below the sudo commands is instructions on using Bossa to flash the firmware directly to the board over USB. Follow that and then you should get on your way.



  • It now works after I uploaded the firmware via USB.


Log in to reply