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

    3.4.0 Stable breaks Nozz Heater[1LC ]Error:M307:Response timeout

    Scheduled Pinned Locked Moved Solved
    Using Duet Controllers
    4
    17
    783
    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.
    • SputnikOC3dundefined
      SputnikOC3d
      last edited by

      everything else on the toolboard is working except the H1 nozzle heater .... therm / probe / fans . Heater was working before on the old toolboard that had the bad mosfet/blown mosfet - replaced the 1LC to a ver 1.2 - flashed all the fw up to 3.4.0 and started installing Klicky - klicky is working - all else is - but the Heater.

      1 Reply Last reply Reply Quote 0
      • SputnikOC3dundefined
        SputnikOC3d
        last edited by

        This is my 2nd 1LC tooboard ... I do have another spare. [3rd ]

        Not sure whats going on here. All other crimps and wiring on the 1LC works or worked before 3.4.0

        1 Reply Last reply Reply Quote 0
        • SputnikOC3dundefined
          SputnikOC3d
          last edited by

          Put on a spare v1.2 1LC toolboard.

          FW ver 3.3 atm - and all works as intended - even the heater.

          Will flash the board to 3.4.0

          1 Reply Last reply Reply Quote 0
          • SputnikOC3dundefined
            SputnikOC3d
            last edited by

            Ok well flashing the 1LC FW to 3.4.0 using M997 B121 ... updated the firmware.

            It hung on updating - please wait like it did the very first time I upgraded to 3.4.0 Stable.

            1LC worked fine on 3.3 from the factory. Now on 3.4.0 Stable - the above errors have returned, and no heater control. Its as if it is DEAD.

            jay_s_ukundefined 1 Reply Last reply Reply Quote 0
            • SputnikOC3dundefined SputnikOC3d referenced this topic
            • SputnikOC3dundefined SputnikOC3d referenced this topic
            • jay_s_ukundefined
              jay_s_uk @SputnikOC3d
              last edited by

              @sputnikoc3d i suggest check your wiring

              Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

              SputnikOC3dundefined 1 Reply Last reply Reply Quote 0
              • SputnikOC3dundefined
                SputnikOC3d @jay_s_uk
                last edited by

                @jay_s_uk said in 3.4.0 Stable breaks Nozz Heater[1LC ]Error:M307:Response timeout:

                @sputnikoc3d i suggest check your wiring

                I have multiple times and it works great. Everything works on 1LC ver 3.3 fw. Everything on the toolboard except the heater works on 3.4.0

                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @SputnikOC3d
                  last edited by

                  @sputnikoc3d what type of wiring are you using?

                  Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                  SputnikOC3dundefined 1 Reply Last reply Reply Quote 0
                  • SputnikOC3dundefined
                    SputnikOC3d @jay_s_uk
                    last edited by

                    @jay_s_uk

                    Cat 5 twisted pair for CAN

                    dc42undefined 1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators @SputnikOC3d
                      last edited by dc42

                      @sputnikoc3d the M307 errors are why the heater won't turn on. Have you used M115 or M122 to check that the main board is running firmware 3.4 ?

                      You may need to rerun heater 1 tuning to generate a new M307 H1 command.

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      SputnikOC3dundefined 2 Replies Last reply Reply Quote 0
                      • SputnikOC3dundefined
                        SputnikOC3d @dc42
                        last edited by

                        @dc42 - TY for your reply.

                        Fresh reboot and power cycle of the SBC / Duet generates No M307 error code - that only happens on estop of the duet.

                        1st op after fresh reboot of entire machine and no reporting of errors, I try M303 H1 S240. I get :

                        M303 H1 S240
                        Auto tuning heater 1 using target temperature 240.0°C and PWM 1.00 - do not leave printer unattended
                        Auto tune starting phase 2, heating up
                        Auto tune cancelled because temperature is not increasing

                        1 Reply Last reply Reply Quote 0
                        • SputnikOC3dundefined
                          SputnikOC3d @dc42
                          last edited by

                          @dc42 well there it is ... looks like the FW upgrade from the previous post using the USB stick didnt actually work as planned ...

                          M122
                          === Diagnostics ===
                          RepRapFirmware for Duet 3 Mini 5+ version 3.4.0beta3 (2021-08-24 14:08:24) running on Duet 3 Mini5plus Ethernet (SBC mode)
                          Board ID: 1JDTH-UA67A-G65J0-40TFU-22D0Z-R2KLQ
                          Used output buffers: 1 of 40 (11 max)
                          === RTOS ===
                          Static ram: 102756
                          Dynamic ram: 93644 of which 0 recycled
                          Never used RAM 42456, free system stack 200 words
                          Tasks: SBC(ready,2.3%,312) HEAT(notifyWait,0.0%,269) Move(notifyWait,0.0%,338) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,372) CanClock(delaying,0.0%,346) TMC(notifyWait,1.1%,106) MAIN(running,95.1%,536) IDLE(ready,0.7%,29) AIN(delaying,0.8%,264), total 100.0%
                          Owned mutexes: HTTP(MAIN)
                          === Platform ===
                          Last reset 00:05:55 ago, cause: power up
                          Last software reset at 2021-10-30 23:33, reason: User, GCodes spinning, available RAM 42456, slot 0
                          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a
                          Error status: 0x00
                          MCU revision 3, ADC conversions started 355962, completed 355961, timed out 0, errs 0
                          Step timer max interval 1474
                          MCU temperature: min 21.7, current 29.9, max 29.9
                          Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
                          Heap OK, handles allocated/used 99/5, heap memory allocated/used/recyclable 2048/224/158, gc cycles 0
                          Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 32297, writes 11, timeouts 0, DMA errors 0
                          Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 32296, writes 11, timeouts 0, DMA errors 0
                          Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 32296, writes 11, timeouts 0, DMA errors 0
                          Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 32296, writes 11, timeouts 0, DMA errors 0
                          Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 9, reads 32299, writes 9, timeouts 0, DMA errors 0
                          Driver 5: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 32296, writes 11, timeouts 0, DMA errors 0
                          Driver 6: position 0, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 11, reads 32296, writes 11, timeouts 0, DMA errors 0
                          Date/time: 2021-10-31 00:02:40
                          Cache data hit count 836168537
                          Slowest loop: 9.15ms; fastest: 0.07ms
                          === Storage ===
                          Free file entries: 10
                          SD card 0 not detected, interface speed: 0.0MBytes/sec
                          SD card longest read time 0.0ms, write time 0.0ms, max retries 0
                          === Move ===
                          DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                          === MainDDARing ===
                          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                          === AuxDDARing ===
                          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                          === Heat ===
                          Bed heaters = 0 -1, chamberHeaters = -1 -1
                          === GCodes ===
                          Segments left: 0
                          Movement lock held by null
                          HTTP* is doing "M122" 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
                          LCD is idle in state(s) 0
                          SBC is idle in state(s) 0
                          Daemon is idle in state(s) 0
                          Aux2 is idle in state(s) 0
                          Autopause is idle in state(s) 0
                          Code queue is empty
                          === CAN ===
                          Messages queued 3111, received 6801, lost 0, longest wait 2ms for reply type 6026, peak Tx sync delay 3, free buffers 16 (min 15), ts 1778/1777/0
                          Tx timeouts 0,0,0,0,0,0
                          === SBC interface ===
                          State: 4, failed transfers: 1, checksum errors: 0
                          Last transfer: 4ms ago
                          RX/TX seq numbers: 13281/13281
                          SPI underruns 0, overruns 0
                          Disconnects: 0, timeouts: 0, IAP RAM available 0x10810
                          Buffer RX/TX: 0/0-0
                          === Duet Control Server ===
                          Duet Control Server v3.4.0
                          Code buffer space: 4096
                          Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
                          Full transfers per second: 39.80, max time between full transfers: 87.9ms, max pin wait times: 51.1ms/11.5ms
                          Codes per second: 0.22
                          Maximum length of RX/TX data transfers: 3464/796
                          
                          1 Reply Last reply Reply Quote 0
                          • SputnikOC3dundefined
                            SputnikOC3d
                            last edited by

                            Please mark this issue as resolved - it was due to m failure to notice mismatched firmware.

                            Got the right FW on the Duet Mainboard via M997 S0

                            SputnikOC3dundefined 1 Reply Last reply Reply Quote 0
                            • SputnikOC3dundefined
                              SputnikOC3d @SputnikOC3d
                              last edited by

                              @sputnikoc3d - well the rasp pi is not updated to 3.4.0 stable though

                              grep of the isntalled duet versions indicates all are still on 3.4beta3 on the Pi

                              Ideas to correct this ?

                              1 Reply Last reply Reply Quote 0
                              • Phaedruxundefined Phaedrux marked this topic as a question
                              • Phaedruxundefined Phaedrux has marked this topic as solved
                              • Phaedruxundefined
                                Phaedrux Moderator
                                last edited by

                                I think you got your answer in your other thread.

                                Z-Bot CoreXY Build | Thingiverse Profile

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