Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    RRF and Heaters – Duet 2 WIFI 3.1.1

    Scheduled Pinned Locked Moved
    General Discussion
    3
    39
    1.7k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • MJCTundefined
      MJCT @Veti
      last edited by

      @Veti Just like this?

      ; config-override.g file generated in response to M500 at 2020-11-13 11:54
      ; This is a system-generated file - do not edit
      ; Heater model parameters
      M307 H0 A135.2 C635.5 D0.6 S1.00 V23.6 B0
      M307 H1 A600.5 C163.9 D10.4 S1.00 V24.0 B0
      ; Workplace coordinates
      G10 L2 P1 X0.00 Y0.00 Z0.00
      G10 L2 P2 X0.00 Y0.00 Z0.00
      G10 L2 P3 X0.00 Y0.00 Z0.00
      G10 L2 P4 X0.00 Y0.00 Z0.00
      G10 L2 P5 X0.00 Y0.00 Z0.00
      G10 L2 P6 X0.00 Y0.00 Z0.00
      G10 L2 P7 X0.00 Y0.00 Z0.00
      G10 L2 P8 X0.00 Y0.00 Z0.00
      G10 L2 P9 X0.00 Y0.00 Z0.00
      M501

      Vetiundefined 1 Reply Last reply Reply Quote 0
      • Vetiundefined
        Veti @MJCT
        last edited by

        @MJCT

        thats you config-overwrite not your config

        MJCTundefined 1 Reply Last reply Reply Quote 0
        • MJCTundefined
          MJCT @Veti
          last edited by

          @Veti Sorry

          ; Heaters
          M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
          M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
          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
          M143 H0 S110 ; set temperature limit for heater 0 to 110C
          M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
          M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
          M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
          M140 H1 ; map heated bed to heater 0
          M143 H1 S290 ; set temperature limit for heater 0 to 110C

          ; Fans
          M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
          M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
          M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
          M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

          ; Tools
          M563 P0 S"Extr 1" 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
          T0 ; select first tool
          M501

          Vetiundefined 1 Reply Last reply Reply Quote 0
          • Vetiundefined
            Veti @MJCT
            last edited by

            @MJCT
            yes

            MJCTundefined 1 Reply Last reply Reply Quote 1
            • MJCTundefined
              MJCT @Veti
              last edited by

              @Veti And another problem arises.
              On my touch screen I’m only getting readings for temperature under the “bed Icon”, nothing appears bellow the “nozzle icon”.
              Web interface shows readings both for extruder 1 and bed. When I request the temperature to rise in one of them, they both show the same target temperature but only the extruder 1 curve moves up

              ; Configuration file for Duet WiFi (firmware version 3)
              ; executed by the firmware on start-up
              ;
              ; generated by RepRapFirmware Configuration Tool v3.1.4 on Thu Nov 12 2020 15:24:07 GMT+0000 (Hora padrão da Europa Ocidental)

              ; General preferences
              G90 ; send absolute coordinates...
              M83 ; ...but relative extruder moves
              M550 P"AA 300x300x600" ; set printer name
              M669 K1 ; select CoreXY mode

              ; Network
              M551 P"AA" ; set password
              M552 S1 ; enable network
              M586 P0 S1 ; enable HTTP
              M586 P1 S0 ; disable FTP
              M586 P2 S0 ; disable Telnet

              ; Drives
              M569 P0 S1 ; physical drive 0 goes forwards
              M569 P1 S1 ; physical drive 1 goes forwards
              M569 P2 S1 ; physical drive 2 goes forwards
              M569 P3 S0 ; physical drive 3 goes backwards
              M584 X0 Y1 Z2 E3 ; set drive mapping
              M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
              M92 X80.00 Y80.00 Z400.00 E98.50 ; set steps per mm
              M566 X950.00 Y950.00 Z30.00 E3000.00 ; set maximum instantaneous speed changes (mm/min)
              M203 X6000.00 Y6000.00 Z1000.00 E3300.00 ; set maximum speeds (mm/min)
              M201 X3100.00 Y3100.00 Z100.00 E10000.00 ; set accelerations (mm/s^2)
              M906 X1850 Y1850 Z1750 E1750 I30 ; set motor currents (mA) and motor idle factor in per cent
              M84 S30 ; Set idle timeout

              ; Axis Limits
              M208 X10 Y10 Z0 S1 ; set axis minima
              M208 X300 Y300 Z570 S0 ; set axis maxima

              ; Endstops
              M574 X1 S1 P"!xstop" ; configure active-high endstop for low end on X via pin !xstop
              M574 Y1 S1 P"!ystop" ; configure active-high endstop for low end on Y via pin !ystop
              M574 Z1 S2 ; configure Z-probe endstop for low end on Z

              ; Z-Probe
              M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
              M558 P9 C"^zprobe.in" H5 F120 T10000 ; set Z probe type to bltouch and the dive height + speeds
              G31 P25 X24 Y0 Z2.425 ; set Z probe trigger value, offset and trigger height (quanto mais elevado Z, mais proximo da mesa)
              M557 X50:250 Y50:250 S25 ; define mesh grid

              ; Heaters
              M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp
              M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
              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
              M143 H0 S110 ; set temperature limit for heater 0 to 110C
              M308 S1 P"e0temp" Y"thermistor" T100000 B4092 ; configure sensor 1 as thermistor on pin e0temp
              M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
              M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
              M140 H1 ; map heated bed to heater 0
              M143 H1 S290 ; set temperature limit for heater 0 to 110C

              ; Fans
              M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
              M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
              M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
              M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on

              ; Tools
              M563 P0 S"Extr 1" 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
              T0 ; select first tool
              M501

              1 Reply Last reply Reply Quote 0
              • Vetiundefined
                Veti
                last edited by

                what firmware are you running on the paneldue?

                MJCTundefined 1 Reply Last reply Reply Quote 0
                • MJCTundefined
                  MJCT @Veti
                  last edited by

                  @Veti 1.24

                  1 Reply Last reply Reply Quote 0
                  • MJCTundefined
                    MJCT
                    last edited by

                    Under "Heat" is it every thing normal?

                    M122
                    === Diagnostics ===
                    RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
                    Board ID: 08DJM-9178L-L4MSJ-6J9F0-3S46Q-KT3YP
                    Used output buffers: 3 of 24 (13 max)
                    === RTOS ===
                    Static ram: 27980
                    Dynamic ram: 93884 of which 60 recycled
                    Exception stack ram used: 304
                    Never used ram: 8844
                    Tasks: NETWORK(ready,308) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
                    Owned mutexes: WiFi(NETWORK)
                    === Platform ===
                    Last reset 00:21:42 ago, cause: power up
                    Last software reset at 2020-11-13 12:09, reason: User, spinning module GCodes, available RAM 8836 bytes (slot 0)
                    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
                    Error status: 0
                    MCU temperature: min 43.0, current 49.1, max 49.4
                    Supply voltage: min 23.7, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
                    Driver 0: standstill, SG min/max not available
                    Driver 1: standstill, SG min/max not available
                    Driver 2: standstill, SG min/max not available
                    Driver 3: standstill, SG min/max not available
                    Driver 4: standstill, SG min/max not available
                    Date/time: 2020-11-13 13:30:55
                    Cache data hit count 2136812117
                    Slowest loop: 13.47ms; fastest: 0.14ms
                    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                    === Storage ===
                    Free file entries: 10
                    SD card 0 detected, interface speed: 20.0MBytes/sec
                    SD card longest read time 4.1ms, write time 6.0ms, max retries 0
                    === Move ===
                    Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, 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 CDDA state: -1
                    === AuxDDARing ===
                    Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                    === Heat ===
                    Bed heaters = 1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                    Heater 1 is on, I-accum = 0.2

                    === GCodes ===
                    Segments left: 0
                    Movement lock held by null
                    HTTP is idle in state(s) 0
                    Telnet is idle in state(s) 0
                    File is idle in state(s) 0
                    USB is idle in state(s) 0
                    Aux is idle in state(s) 0
                    Trigger is idle in state(s) 0
                    Queue is idle in state(s) 0
                    Daemon is idle in state(s) 0
                    Autopause is idle in state(s) 0
                    Code queue is empty.
                    === Network ===
                    Slowest loop: 26.07ms; fastest: 0.00ms
                    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                    HTTP sessions: 1 of 8

                    • WiFi -
                      Network state is active
                      WiFi module is connected to access point
                      Failed messages: pending 0, notready 0, noresp 0
                      WiFi firmware version 1.23
                      WiFi MAC address ec:fa:bc:01:d4:c6
                      WiFi Vcc 3.38, reset reason Unknown
                      WiFi flash size 4194304, free heap 24528
                      WiFi IP address 192.168.10.62
                      WiFi signal strength -54dBm, reconnections 0, sleep mode modem
                      Socket states: 0 0 0 0 0 0 0 0
                    1 Reply Last reply Reply Quote 0
                    • Vetiundefined
                      Veti
                      last edited by

                      i dont see anything unusual. maybe someone else can have a look?

                      MJCTundefined 1 Reply Last reply Reply Quote 0
                      • MJCTundefined
                        MJCT @Veti
                        last edited by

                        @Veti Funny

                        Just deleted the 2 lines that I added manually to the config (M140 and M143) and everything went back to normal
                        How can this be?

                        1 Reply Last reply Reply Quote 0
                        • MJCTundefined
                          MJCT
                          last edited by

                          Adding M143 H1 S290 and everything stays normal
                          Adding M140 H1and everything gets broken again

                          This M140 H1 command for the nozle makes all the difference

                          Vetiundefined 1 Reply Last reply Reply Quote 0
                          • Vetiundefined
                            Veti @MJCT
                            last edited by

                            @MJCT

                            that makes sense.

                            M140 H1 ; map heated bed to heater 0

                            this means that the heater is designated to be a bed heater.
                            you dont want to do that for H1, as it is not a bed heater.

                            MJCTundefined 1 Reply Last reply Reply Quote 0
                            • MJCTundefined
                              MJCT @Veti
                              last edited by

                              @Veti that said, don't I need to map it anyway with some other M140?
                              I just leave it like that?

                              Vetiundefined 1 Reply Last reply Reply Quote 0
                              • Vetiundefined
                                Veti @MJCT
                                last edited by

                                @MJCT

                                yes

                                MJCTundefined 1 Reply Last reply Reply Quote 1
                                • MJCTundefined
                                  MJCT @Veti
                                  last edited by

                                  @Veti Ok, thank you very much for all this hours that you spent helping me

                                  1 Reply Last reply Reply Quote 1
                                  • First post
                                    Last post
                                  Unless otherwise noted, all forum content is licensed under CC-BY-SA