Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Can access but cannot control....

    Firmware installation
    2
    4
    331
    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.
    • peirof
      peirof last edited by

      Hi,

      After 4 correct prints, today I connected the printer and I found the following problem:

      • The extruder has disappeared.
      • The bed does NOT detect the temperature
      • I've tried Homing, and the engines make noise but it DOES NOT move.
      • The WiFi, after restart, does NOT connect automatically, I have to restart it by DWC.
      • The same functionality that I have for the DWC, I have it for the DueFirmware Panel

      Panel Due Image

      It's a DUET 2 WiFi board

      The firmwares that it carries in these moments, are, if I remember correctly, those that it took when it installs it.

      Firmware Name: RepRapFirmware for Duet 2 WiFi / Ethernet
      Firmware Electronics: Duet WiFi 1.02 or later
      Firmware Version: 1.21 (2018-03-21)
      WiFi Server Version: 1.21RC4 (08b3)
      Web Interface Version: 1.21-RC4**

      1 Reply Last reply Reply Quote 0
      • peirof
        peirof last edited by

        i have try to uptadte firmwares.... but the same

        in this moments:

        Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
        Firmware Electronics: Duet WiFi 1.02 or later
        Firmware Version: 2.0(RTOS) (2018-06-05b3)
        WiFi Server Version: 1.21RC4(08b3)
        Web Interface Version: 1.21.1

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

          Check that you have the correct files in /sys on the SD card, and check that the config.g file looks ok in particular.

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

            @dc42

            again ... thanks DC42.

            it was a typographical error in config.g .... it had that instead of M558, it had M559 ...

            Solved, thanks

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