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

    Endstops unstable and EMERGENCY STOP NOT STOPPING EXT.BOARD ???

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    5
    14
    575
    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.
    • jrocklandundefined
      jrockland
      last edited by

      Also endstops on extension board are ignored when homing after a print.
      -Yes endstops are connected on the same ext board as the related stepper motors.

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

        @dc42 Just realised when I do a M115, it say firmware_version 3.1.1 BUT Firmware_date 2020-05-19.b2. is it right ?

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

          Can you post the results of M122 so we can see what boards you're talking about?

          Z-Bot CoreXY Build | Thingiverse Profile

          jrocklandundefined 2 Replies Last reply Reply Quote -1
          • jrocklandundefined
            jrockland @Phaedrux
            last edited by

            @Phaedrux m122
            === Diagnostics ===
            RepRapFirmware for Duet 3 MB6HC version 3.1.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
            Board ID: 08DJM-956L2-G43S4-6J1F8-3SD6T-9V56D
            Used output buffers: 1 of 40 (16 max)
            === RTOS ===
            Static ram: 154604
            Dynamic ram: 163276 of which 60 recycled
            Exception stack ram used: 224
            Never used ram: 75052
            Tasks: NETWORK(ready,1972) HEAT(blocked,1188) CanReceiv(suspended,3408) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,204) MAIN(running,4952) IDLE(ready,76)
            Owned mutexes:
            === Platform ===
            Last reset 00:29:43 ago, cause: software
            Last software reset at 2020-12-31 18:49, reason: User, spinning module LinuxInterface, available RAM 74620 bytes (slot 2)
            Software reset code 0x0010 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
            Error status: 0
            MCU temperature: min 34.1, current 35.2, max 37.0
            Supply voltage: min 24.1, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
            12V rail voltage: min 12.0, current 12.0, max 12.2, under voltage events: 0
            Driver 0: standstill, reads 1982, writes 14 timeouts 0, SG min/max 0/0
            Driver 1: standstill, reads 1982, writes 14 timeouts 0, SG min/max 0/0
            Driver 2: standstill, reads 1983, writes 14 timeouts 0, SG min/max 0/0
            Driver 3: standstill, reads 1983, writes 14 timeouts 0, SG min/max 0/0
            Driver 4: standstill, reads 1983, writes 14 timeouts 0, SG min/max 0/0
            Driver 5: standstill, reads 1984, writes 14 timeouts 0, SG min/max 0/0
            Date/time: 2020-12-31 20:31:34
            Slowest loop: 6.29ms; fastest: 0.14ms
            === Storage ===
            Free file entries: 10
            SD card 0 not detected, interface speed: 37.5MBytes/sec
            SD card longest read time 0.0ms, write time 0.0ms, max retries 0
            === Move ===
            Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
            === GCodes ===
            Segments left: 0
            Movement lock held by null
            HTTP* is ready with "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.
            === Network ===
            Slowest loop: 0.66ms; fastest: 0.01ms
            Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
            HTTP sessions: 0 of 8

            • Ethernet -
              State: disabled
              Error counts: 0 0 0 0 0
              Socket states: 0 0 0 0 0 0 0 0
              === CAN ===
              Messages sent 23204, longest wait 1ms for type 6018
              === Linux interface ===
              State: 0, failed transfers: 0
              Last transfer: 16ms ago
              RX/TX seq numbers: 45704/29677
              SPI underruns 0, overruns 0
              Number of disconnects: 0
              Buffer RX/TX: 0/0-0
              === Duet Control Server ===
              Duet Control Server v3.1.1
              Code buffer space: 4096
              Configured SPI speed: 8000000 Hz
              Full transfers per second: 33.53
            1 Reply Last reply Reply Quote 0
            • jrocklandundefined
              jrockland @Phaedrux
              last edited by

              @Phaedrux So I managed to get my expension board to actually update to the last version, and none of my 6hc. half is giving me duet3_sbciap_mb6hc.bin canot be find, other half doest update. (I have 3 machines running 6hc + exp)

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

                @dc42 your 3.2 cant be installed on any of my board. tried every way possible and it always fail.
                I did a hard reset with bossa using the last firmware and now I have a dead machine. "DSC isnt started".

                1 Reply Last reply Reply Quote 0
                • oliofundefined
                  oliof
                  last edited by

                  Sounds like your raspberry pi is not up and running

                  <>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>

                  jrocklandundefined 1 Reply Last reply Reply Quote 0
                  • jrocklandundefined
                    jrockland @oliof
                    last edited by

                    @oliof would be hard to do all those update since im working directly on it -_-"
                    I also connected it to my other board and it work so it is from the board 100%.

                    Most useless comment yet.

                    1 Reply Last reply Reply Quote 0
                    • jrocklandundefined
                      jrockland
                      last edited by

                      Ill mark this one as "solved" for now as obviously it didnt update right, and start one about why I cant update ??

                      Multisaftundefined 1 Reply Last reply Reply Quote 0
                      • Multisaftundefined
                        Multisaft @jrockland
                        last edited by

                        @jrockland I had the same problem therefor I installed 3.1.1 fw package on both, hc6 and on hc3. After this the update package 3.2 did properly updated both boards.

                        Maybe u need to do this also.

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