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

    Duet 3 Config file help

    Scheduled Pinned Locked Moved
    My Duet controlled machine
    duet 3 6hc duet 3 expansion board 1xd odrive config external driver
    3
    6
    487
    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.
    • Kooperundefined
      Kooper
      last edited by

      Hi all,

      Thank you in advance for any help.

      I am working on a coreXY printer. I have 3 z-axis motors and a Duet 3 v1.01 that is connected to 2 1XD v1.0 expansion boards. These pass step-direction commands to an ODrive. I am using a raspberry pi connected to the Duet 3. I am having trouble with the config.g file (I think).

      I get the following errors:
      Warning: Discarded std reply src=122 RID=1 exp 2 "Setting not available for external drivers"
      Error: Bad command: macros

      Though I am not using any macros.

      My config.g file is here: config (1).g

      Let me know if there are other relevant files and I will upload them.

      The M122 command seems to be happy:

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode)
      Board ID: 08DJM-9P63L-DJMSS-6JKD6-3SN6M-KUHZA
      Used output buffers: 1 of 40 (16 max)
      === RTOS ===
      Static ram: 151000
      Dynamic ram: 66028 of which 164 recycled
      Never used RAM 133480, free system stack 200 words
      Tasks: SBC(ready,0.6%,487) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,92) MAIN(running,86.9%,923) IDLE(ready,4.6%,30), total 100.0%
      Owned mutexes: HTTP(MAIN)
      === Platform ===
      Last reset 00:03:08 ago, cause: power up
      Last software reset at 2022-04-24 09:51, reason: User, GCodes spinning, available RAM 133480, slot 1
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Step timer max interval 135
      MCU temperature: min 25.5, current 38.3, max 38.4
      Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.0, current 12.1, max 12.3, under voltage events: 0
      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: standstill, SG min 0, mspos 4, reads 1328, writes 14 timeouts 0
      Driver 1: standstill, SG min 0, mspos 4, reads 1328, writes 14 timeouts 0
      Driver 2: standstill, SG min 0, mspos 4, reads 1328, writes 14 timeouts 0
      Driver 3: standstill, SG min 0, mspos 8, reads 1328, writes 14 timeouts 0
      Driver 4: standstill, SG min 0, mspos 8, reads 1332, writes 11 timeouts 0
      Driver 5: standstill, SG min 0, mspos 8, reads 1329, writes 14 timeouts 0
      Date/time: 2022-05-22 03:11:43
      Slowest loop: 1.46ms; fastest: 0.03ms
      === 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 ===
      DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      === 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 1652, received 5722, lost 0, boc 0
      Longest wait 1ms for reply type 6031, peak Tx sync delay 271, free buffers 50 (min 49), ts 941/940/0
      Tx timeouts 0,0,0,0,0,0
      === SBC interface ===
      Transfer state: 4, failed transfers: 0, checksum errors: 0
      RX/TX seq numbers: 7763/7763
      SPI underruns 0, overruns 0
      State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b880
      Buffer RX/TX: 0/0-0, open files: 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: 0.00, max time between full transfers: 1609.3ms, max pin wait times: 1600.7ms/5.4ms
      Codes per second: 0.00
      Maximum length of RX/TX data transfers: 3102/784

      Here is a picture of my (very messy) setup:
      printer.jpeg

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

        @kooper please also post the results of running M122 B121 and M122 B122.

        The "setting not available" message is triggered by this line:

        M350 X1 Y1 I0 ; configure microstepping without interpolation

        I suggest you remove it.

        At what point do you see the "Error: Bad command: macros" message?

        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

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

          Thanks @dc42

          I see the "Error: Bad command: macros" message on a PanelDue screen directly after turning on the printer.

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

            @kooper if you run M98 P"config.g" on the console tab, what do you get shown as the result? (in addition to the requested M122 B121 and M122 B122 commands).

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

            1 Reply Last reply Reply Quote 0
            • Kooperundefined
              Kooper
              last edited by

              Hi @oliof

              With the line;

              "M350 X1 Y1 I0 ; configure microstepping without interpolation"

              removed as suggested by dc42. When I run: M98 P"config.g" I get a response timeout. Namely:

              Error: M950: Response timeout: CAN addr 121, req type 6027, RID=44
              Warning: Discarded std reply src=122 RID=47 exp 48 ""

              Running M122 B121 gives a similar timeout response. However M122 B122 provides the response in the following image.

              7f3fd0e6-6d97-4d85-92f0-27acd675b0e0-image.png

              The cables I am using for the CAN FD bus are not crossed and I have the 1XD end resistor pins attached. So I am not sure why there is a difference.

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

                @kooper swap the cables between the boards to rule out its an issue with those maybe.

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

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