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

Error: M584: Invalid number of visible axes

Scheduled Pinned Locked Moved
General Discussion
2
4
57
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.
  • undefined
    ToWi1989
    last edited by ToWi1989 23 Feb 2025, 09:20

    I'm running a core XY machine with 3 individually driven Z-axis. Sometimes I wish to take manual control over each individual Z-drive, for example when the bed becomes so tilted that autoleveling would result in a crash. I was using a macro to switch between showing the combined Z-azis and individual (UVW) axis control. However, since upgrading the firmware (now running 3.5.4) this macro is giving an error:

    Error: M584: Invalid number of visible axes

    This is my drive mapping:

    ; Drives
    M569 P0.0 S1 ; physical drive 0.0 Z1 goes forwards
    M569 P0.1 S1 ; physical drive 0.1 Z2 goes forwards
    M569 P0.2 S1 ; physical drive 0.2 Z3 goes forwards
    M569 P0.3 S1 ; physical drive 0.3 X goes forwards
    M569 P0.4 S1 ; physical drive 0.4 Y goes forwards
    M569 P121.0 S0 ; drive 121.0 goes backwards
    M584 X0.3 Y0.4 Z0.0:0.1:0.2 E121.0 ; set drive mapping
    M671 X24:333:178.5 Y-33.5:-33.5:275.5 S50 ; set lead screw position for auto bed leveling

    The macros for switching between showing/hiding the UWV axis is a simple:
    Hide UVW:
    M584 P3 ; Show only first 3 assigned axis

    Show UVW:
    M584 P6 ; Show all 6 assigned axis

    I've tried changing M584 X0.3 Y0.4 Z0.0:0.1:0.2 E121.0 to M584 X0.3 Y0.4 Z0.0:0.1:0.2 U0.0 V0.1 W0.2 E121.0 P3

    This causes some very weird behaviour. Moving the Z-axis works as expected, but moving the individual U V W axis results in a small amount of movement, and the drive is turned off after a couple of seconds.

    Does anyone have any clue how to get this to work again / what changed in the firmware?

    undefined 1 Reply Last reply 23 Feb 2025, 09:59 Reply Quote 0
    • undefined
      jay_s_uk @ToWi1989
      last edited by 23 Feb 2025, 09:59

      @ToWi1989 what firmware were you running before?
      You can't show an axis if it hasn't been configured so using M584 to map the same drivers to U V and W is correct.
      How are you setting them as homed for that axis?
      What board are you running?
      Best post your full macro you are using

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

      undefined 1 Reply Last reply 23 Feb 2025, 11:14 Reply Quote 1
      • undefined
        ToWi1989 @jay_s_uk
        last edited by 23 Feb 2025, 11:14

        @jay_s_uk I have no idea what the old firmware was. I've upgraded some months ago, but only sporadically use the UVW controls. As far as I can tell I've made no changes to the config file myself, but it's very well possible some trial and error was involved after the upgrade that I can't recall. Homing/leveling the bed is done via G32, but if the bed is tilted too much it will crash with the print head. I'm disabling the axis limits to move the UVW axis independantly, but only when needed (I had 1 stepper loose connection to the B-coil during a print last night which resulted in a prety catastrophic failure).

        I've added the UVW assignments back in the M584 comand, but missed that I need to configure all the other parameters (motor current, accell, steps/mm, ...) for the UVW axis as well. This also explains the weird behavior that I saw. This is now corrected and working again!

        I was thinking that setting these parameters once per physical drive would be sufficient, but I've proven myself wrong 😄

        undefined 1 Reply Last reply 23 Feb 2025, 11:16 Reply Quote 2
        • undefined
          jay_s_uk @ToWi1989
          last edited by 23 Feb 2025, 11:16

          @ToWi1989 glad you got it sorted

          Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

          1 Reply Last reply Reply Quote 1
          2 out of 4
          • First post
            2/4
            Last post
          Unless otherwise noted, all forum content is licensed under CC-BY-SA