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

    PT1000 not working. no heatbed in DWC.

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    35
    1.3k
    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.
    • duttiundefined
      dutti @Phaedrux
      last edited by

      @phaedrux
      I´ll try it tomorrow but......
      That doesn´t makes fun. I decided to send it back to the reseller if I can´t solve the problem tomorrow.
      Lot´s of time spend finding the problem is no good idea in my case.
      And you also spend more time helping people with other problems.
      I go for Duet3 mini, I think.

      thanks for your support!

      1 Reply Last reply Reply Quote 0
      • duttiundefined
        dutti @Phaedrux
        last edited by

        @phaedrux said in PT1000 not working. no heatbed in DWC.:

        M122

        The SD-Card works fine wit my computer... don´t have any else here at the moment.

        I extract it first and another time I uploaded it as single zip file. What is correct?
        Is there any description for making the files in the correct way on the card?

        M122

        M122
        === Diagnostics ===
        RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
        Board ID: 08DLM-996RU-N85T0-6J9F4-3S86N-TASZN
        Used output buffers: 1 of 24 (11 max)
        === RTOS ===
        Static ram: 23460
        Dynamic ram: 73212 of which 16 recycled
        Never used RAM 15392, free system stack 192 words
        Tasks: NETWORK(ready,521) HEAT(blocked,294) MAIN(running,383) IDLE(ready,20)
        Owned mutexes: USB(MAIN)
        === Platform ===
        Last reset 00:10:45 ago, cause: power up
        Last software reset details not available
        Error status: 0x00
        Aux0 errors 0,0,0
        MCU temperature: min 25.1, current 28.2, max 28.6
        Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 1, over voltage events: 0, power good: no
        Driver 0: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
        Driver 1: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
        Driver 2: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
        Driver 3: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
        Driver 4: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
        Driver 5: position 0
        Driver 6: position 0
        Driver 7: position 0
        Driver 8: position 0
        Driver 9: position 0
        Driver 10: position 0
        Driver 11: position 0
        Date/time: 1970-01-01 00:00:00
        Cache data hit count 871082808
        Slowest loop: 100.55ms; fastest: 0.15ms
        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 3.1ms, write time 0.0ms, max retries 0
        === Move ===
        DMs created 83, 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 -1 -1, chamberHeaters = -1 -1 -1 -1
        === 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 ready with "M122" 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
        Daemon is idle in state(s) 0
        Autopause is idle in state(s) 0
        Code queue is empty.
        === Network ===
        Slowest loop: 0.23ms; fastest: 0.00ms
        Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
        HTTP sessions: 0 of 8

        • WiFi -
          Network state is starting2
          WiFi module is disabled
          Failed messages: pending 0, notready 3, noresp 0
          Socket states: 0 0 0 0 0 0 0 0
          ok
          M552 S1
          Turn off the current WiFi mode before selecting a new one
          ok
          M552 S-1
          WiFi module stopped
          ok
          M552 S0
          ok
          M552 S1
          Turn off the current WiFi mode before selecting a new one
          ok
          M552
          WiFi module is being started
          ok
          M552
          WiFi module is being started
          ok
          M122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
          Board ID: 08DLM-996RU-N85T0-6J9F4-3S86N-TASZN
          Used output buffers: 1 of 24 (11 max)
          === RTOS ===
          Static ram: 23460
          Dynamic ram: 73212 of which 16 recycled
          Never used RAM 15392, free system stack 192 words
          Tasks: NETWORK(ready,519) HEAT(blocked,294) MAIN(running,383) IDLE(ready,20)
          Owned mutexes: USB(MAIN)
          === Platform ===
          Last reset 00:12:22 ago, cause: power up
          Last software reset details not available
          Error status: 0x00
          Aux0 errors 0,0,0
          MCU temperature: min 27.8, current 28.1, max 28.6
          Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 1, over voltage events: 0, power good: no
          Driver 0: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
          Driver 1: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
          Driver 2: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
          Driver 3: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
          Driver 4: position 0, temperature-shutdown! short-to-ground, standstill, SG min/max not available
          Driver 5: position 0
          Driver 6: position 0
          Driver 7: position 0
          Driver 8: position 0
          Driver 9: position 0
          Driver 10: position 0
          Driver 11: position 0
          Date/time: 1970-01-01 00:00:00
          Cache data hit count 1001423174
          Slowest loop: 99.29ms; fastest: 0.15ms
          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 3.1ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, 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 -1 -1, chamberHeaters = -1 -1 -1 -1
          === 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 ready with "M122" 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
          Daemon is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === Network ===
          Slowest loop: 0.23ms; fastest: 0.00ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
          HTTP sessions: 0 of 8
        • WiFi -
          Network state is starting2
          WiFi module is disabled
          Failed messages: pending 0, notready 0, noresp 0
          Socket states: 0 0 0 0 0 0 0 0
          ok

        M20 P"/www/"
        Begin file list
        favicon.ico.gz
        manifest.json.gz
        index.html.gz
        service-worker.js.gz
        precache-manifest.60203ed55805000c1d8c35cfc138f4cf.js.gz
        css
        js
        img
        fonts
        End file list
        ok

        Phaedruxundefined 1 Reply Last reply Reply Quote 0
        • duttiundefined
          dutti @Phaedrux
          last edited by

          @phaedrux 96629821-0559-41f4-ae1d-60291048a91b-image.png WhatsApp Image 2021-04-21 at 10.22.56.jpeg

          1 Reply Last reply Reply Quote 0
          • Phaedruxundefined
            Phaedrux Moderator @dutti
            last edited by

            @barbarossa-cologne said in PT1000 not working. no heatbed in DWC.:

            I extract it first and another time I uploaded it as single zip file. What is correct?

            Upload the single zip file. The Duet will extract it and put the files in the correct place automatically.

            @barbarossa-cologne said in PT1000 not working. no heatbed in DWC.:

            Is there any description for making the files in the correct way on the card?

            Yes there is: https://duet3d.dozuki.com/Wiki/SD_Card

            Your SD card is a bit of a mess at the moment.

            The root of the card should only have a few folders.

            sys
            www
            macros
            gcodes
            

            Nothing else.

            Inside of sys you should have the normal configuration files, example:

            │   ├── bed.g
            │   ├── cancel.g
            │   ├── config.g
            │   ├── homedelta.g
            │   ├── pause.g
            │   ├── resume.g
            │   ├── sleep.g
            │   ├── stop.g
            │   ├── tfree0.g
            │   ├── tpost0.g
            │   └── tpre0.g
            

            And also the firmware .bin files from the 3.2.2 zip file

            The www folder should have these folders and files:

            css
            fonts
            js
            img
            favicon.ico
            index.html
            manifest.json
            precache-manifest...
            service-worker
            

            So it looks like you have the files in the correct place, but you also have the files duplicated in many places.
            Once you clean up the SD card, please try again.

            It shows that it is reading from the SD card, so that's good.

            But the wifi is not starting, possibly because it doesn't have the firmware flashed. So once you have the card cleaned up, send M997 S1 again to initiate the wifi flash.

            Z-Bot CoreXY Build | Thingiverse Profile

            duttiundefined 2 Replies Last reply Reply Quote 0
            • duttiundefined
              dutti @Phaedrux
              last edited by

              @phaedrux said in PT1000 not working. no heatbed in DWC.:

              M997 S1

              Just upload the single file...?

              • firmare , confiduration from the tool and json?
                or just firmware?

              just with firmware ---> M997 S1
              Error: M997: File DuetWiFiServer.bin not found

              1 Reply Last reply Reply Quote 0
              • duttiundefined
                dutti @Phaedrux
                last edited by

                @phaedrux
                I just replaced the firmware in the sd card (deleted everyrhing else before) and it looks like this..
                31d38982-f7d8-4f20-bf38-cd551bdea396-image.png

                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  The firmware files must be in a folder called SYS

                  Z-Bot CoreXY Build | Thingiverse Profile

                  duttiundefined 1 Reply Last reply Reply Quote 0
                  • duttiundefined
                    dutti @Phaedrux
                    last edited by

                    @phaedrux 35a1fee4-0a00-4c33-a8a0-c95187c47db1-image.png

                    I don´t know how to get the www files... can´t i just put the zip files on the sd card and the duet do the rest like you said?
                    😞

                    1 Reply Last reply Reply Quote 0
                    • Phaedruxundefined
                      Phaedrux Moderator
                      last edited by Phaedrux

                      Maybe we should start from scratch.

                      The duet has the correct firmware on it 3.2.2, so that's good.

                      The wifi module isn't starting. Possibly because it doesn't have the right firmware flashed. 1.25.

                      First backup your SD card contents somewhere safe so you have a copy of your config files handy.

                      Then wipe the SD card so that it is blank.

                      Create 4 folders sys macros gcodes www

                      Inside the www folder place the DWC files by extracting the contents of this zip file into the www folder.

                      https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/DuetWebControl-SD.zip

                      Inside of the sys folder you will place your configuration .g files such as config.g, homing files, etc you can copy those over from your SD card backup or generate a new set from the config tool.

                      Also inside of the sys folder you will place this bin file

                      https://github.com/Duet3D/RepRapFirmware/releases/download/3.2/DuetWiFiServer.bin

                      Now boot up the board and connect via USB. Send M997 S1.

                      It should then flash the wifi module and afterwards you should be able to send M552 S1 to turn the module on.

                      If that works you should be able to connect to the IP address of the Duet in your browser and use DWC again.

                      From there you can upload the 3.2.2 zip file as a single file again to the system tab to ensure that all the files are present for future use.

                      https://github.com/Duet3D/RepRapFirmware/releases/download/3.2.2/Duet2and3Firmware-3.2.2.zip

                      Z-Bot CoreXY Build | Thingiverse Profile

                      duttiundefined 2 Replies Last reply Reply Quote 0
                      • duttiundefined
                        dutti @Phaedrux
                        last edited by

                        @phaedrux
                        ok I just did the files like in the describtion... so starting from zero. It´s loading 🙂

                        1 Reply Last reply Reply Quote 0
                        • duttiundefined
                          dutti @Phaedrux
                          last edited by

                          @phaedrux
                          Ok it´s working, now!!
                          thank you so much. sry for beeing stupid and frustrated. Usally the duets are doing what I want from them!!

                          thanks a lot!!!

                          1 Reply Last reply Reply Quote 1
                          • Phaedruxundefined
                            Phaedrux Moderator
                            last edited by

                            With enough time, effort, and patience, we can solve anything.

                            Z-Bot CoreXY Build | Thingiverse Profile

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