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

    Panel Due v2.0 "stoped working"

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    3
    6
    1.2k
    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.
    • tux_on_tourundefined
      tux_on_tour
      last edited by

      Panel Due worked fine until I connected the the Mini height sensor.

      Now the screen is frozen heater temp says "ovf" does not react on touch. Works fine on USB and (yes I know your not supposed to do it) after disconnecting it from the running duetwifi board and reconnecting it.

      Duet webinterface works fine from start and I did not change any settings after connecting the probe.

      [[language]]
      M122
      Diagnostics
      Used output buffers: 2 of 32 (3 max)
      Platform Diagnostics:
      Memory usage:
      Program static ram used: 19280
      Dynamic ram used: 82816
      Recycled dynamic ram: 304
      Current stack ram used: 2768
      Maximum stack ram used: 3600
      Never used ram: 25072
      Last reset 00:15:04 ago, cause: external
      Error status: 1
      Bed probe heights: 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest block write time: 0.0ms
      MCU temperature: min 29.5, current 34.8, max 39.1
      Supply voltage: min 24.6, current 24.7, max 25.0, under voltage events: 0, over voltage events: 0
      Slowest main loop (seconds): 0.003113; fastest: 0.000040
      Move Diagnostics:
      MaxReps: 0, StepErrors: 0, MaxWait: 0ms, Underruns: 0, 0
      Heat Diagnostics:
      Bed heater = 0, chamber heater = -1
      Heater 1 is on, I-accum = 0.0
      GCodes Diagnostics:
      Move available? no
      Stack pointer: 0 of 5
      macro is idle
      http is ready with "M122"
      telnet is idle
      serial is idle
      aux is idle
      file is idle
      Network Diagnostics:
      WiFiServer is running
      SPI underruns 0, overruns 0
      Webserver Diagnostics:
      HTTP sessions: 1 of 8
      
      

      M575 P1 B57600 S1 is Still set in config.g.

      And is there a way to get higher measurement range on the new probe with SMD IR led like an firmware update? Given a pin out of the ISP port and the hex file I could upload it myself.

      Sincerely

      Sven

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

        No need to disconnect and reconnect the PanelDue, it has a reset button.

        Please update your PanelDue firmware to latest version. It includes a workaround for a C library bug that caused that kind of freeze.

        Do you have the IR sensor with through hole optical components, or with SMD optical components? If it has the through hole components then you can extend the sensitivity to dark surfaces by reprogramming it. The ISP port uses the standard Atmel pinout.

        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

        1 Reply Last reply Reply Quote 0
        • tux_on_tourundefined
          tux_on_tour
          last edited by

          @dc42:

          No need to disconnect and reconnect the PanelDue, it has a reset button.

          My case does not have an hole never needed an Reset button on my other duet so I removed it to save some work.

          @dc42:

          Please update your PanelDue firmware to latest version. It includes a workaround for a C library bug that caused that kind of freeze.

          I did the update from 1.14 to 1.15b3 and it works now.

          Thanks

          @dc42:

          Do you have the IR sensor with through hole optical components, or with SMD optical components?

          The new one with SMD. So no way to extend the range ?

          Thanks a lot for your help

          Sven

          1 Reply Last reply Reply Quote 0
          • Jackalundefined
            Jackal
            last edited by

            David, is it worth upgrading from IR sensor 1.1 to 1.2?

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

              @Jackal:

              David, is it worth upgrading from IR sensor 1.1 to 1.2?

              Only if your v1.1 sensor is not working, either because the target is too reflective and the sensor is saturating, or the target is too dark and the sensor is not picking it up.

              The main reason for the 1.2 redesign was to reduce the assembly cost by using SMD optical components. Unfortunately, Microchip has wiped out much of the saving by almost doubling the price of the attiny microcontroller that the sensor uses, not long after they took over Atmel. Looks like they are trying to kill off the AVR architecture in favour of PIC.

              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

              1 Reply Last reply Reply Quote 0
              • Jackalundefined
                Jackal
                last edited by

                Thanks for the info.

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