Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. resam
    3. Controversial
    • Profile
    • Following 0
    • Followers 4
    • Topics 50
    • Posts 489
    • Best 102
    • Controversial 1
    • Groups 0

    Controversial posts made by resam

    • GCodes: Attempt to read a GCode unsigned array that is too long

      I just noticed today that I get the following warning/error message on PanelDue console tab after I power-up/reset my DuetWifi:
      GCodes: Attempt to read a GCode unsigned array that is too long: M350 X16 Y16 Z16 E16:16 I1

      The weird thing is, I'm tracking my config.g with git since day-0 and this config line is unchanged since then. However, I've never seen this warning message before...

      I'm running 1.21 for a while now - is this a new message, or what is happening here?
      I guess the config line in question is obviously wrong I suppose, since I'm running a CoreXY with dual Z (one on the Z driver, and one on the E1 driver)...

      The only recent change was:
      M584 X0 Y1 Z2:4 ; Drive mapping: 0=A, 1=B, 2 and 4 are individual Z steppers
      got changed to:
      M584 X0 Y1 Z2:4 E3 ; Drive mapping: 0=A, 1=B, 2 and 4 are individual Z steppers, 3=Extruder

      I'm currently running a print, but once it's done, I will try to fix the M350. Do I need to specify Z microstepping as Z16:16 or does this get applied to both driver automatically?

      posted in General Discussion
      resamundefined
      resam