UVWABCDabcdefghijkl - axis is not showing up

Aurimas

so it is me again.
I am trying to setup multiple axis - just standard cartesian setup
Firmware 3.4 6XD board + 1XD
trying to use pretty much all axis from UVWABCDabcdefghijkl - axis is not showing up
all I get is is up to D, XYZABXCDUV that are working and the rest are not showing up
what am I doing wrong?
I have all enstops configured - they are not showing up
Matrix is shoeing only those axis and not the rest

any advice would be much appreciated

M122 and the config files are below:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6XD version 3.4.6 (2023-07-21 14:11:58) running on Duet 3 MB6XD v1.01 or later (standalone mode)
Board ID: 0JD2M-999AL-D2PS0-6J9D2-3SJ6Q-15M33
Used output buffers: 3 of 40 (24 max)
=== RTOS ===
Static ram: 151692
Dynamic ram: 95132 of which 0 recycled
Never used RAM 100920, free system stack 200 words
Tasks: NETWORK(ready,77.7%,173) ETHERNET(notifyWait,0.1%,324) HEAT(notifyWait,0.0%,373) Move(notifyWait,0.0%,214) CanReceiv(notifyWait,0.1%,773) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,352) MAIN(running,22.0%,1152) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: LwipCore(NETWORK)
=== Platform ===
Last reset 00:23:52 ago, cause: software
Last software reset at 2023-12-16 16:07, reason: User, GCodes spinning, available RAM 101524, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 5013
MCU temperature: min 39.6, current 40.1, max 40.6
Supply voltage: min 24.1, current 24.1, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.3, current 12.3, max 12.4, under voltage events: 0
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/152/152, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: ok
Driver 1: ok
Driver 2: ok
Driver 3: ok
Driver 4: ok
Driver 5: ok
Date/time: 2023-12-16 16:31:40
Slowest loop: 34.35ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.2ms, write time 55.3ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 225383ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 72, completed 72, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 72], 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 -1 -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 idle 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 7912, received 183849, lost 0, boc 0
Longest wait 8ms for reply type 6036, peak Tx sync delay 272, free buffers 50 (min 49), ts 7161/7160/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 68.58ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(2) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 1 0
Socket states: 5 3 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

; Default config.g template for DuetPi
; Replace this with a proper configuration file (e.g from https://configtool.reprapfirmware.org)

; Enable network
if {network.interfaces[0].type = "ethernet"}
    M552 P169.254.112.5 S1
else
    M552 S3
    
;Enable PanelDue
M575 P1 S1 B57600
G4 S2

M584 R0 X20.0 Y21.0 Z30.0 U31.0 V40.0 A41.0 B50.0 C51.0 D60.0 a61.0 c31.0 d41.0 e51.0 f71.0 i81.0 h91.0 


M569 P21.0 S1                                        ; physical drive 0.0 goes forwards
M569 P20.0 S0                                        ; physical drive 0.1 goes forwards
M569 P31.0 S1 
M569 P30.0 S0
M569 P41.0 S1 
M569 P40.0 S0
M569 P51.0 S1 
M569 P50.0 S0
M569 P61.0 S1                                        ; physical drive 0.0 goes forwards
M569 P60.0 S1
M569 P71.0 S1                                        ; physical drive 0.0 goes forwards
M569 P70.0 S1
M569 P81.0 S1                                        ; physical drive 0.0 goes forwards
M569 P80.0 S1
M569 P91.0 S1                                        ; physical drive 0.0 goes forwards
M569 P90.0 S1


M92 X26.67 Z26.67 V26.67 B26.67 Y80.00 U80 A80 C80 D26.67
M92 a26.67 ;F26.67 G80.0 H80.0 I80.0 J80.0 K80.0 L80.0 								;steps per mm

M566 X2000.00 Y4000.00 U2000 V2000 A2000 B4000 C2000 D4000 
M566 a2000 Z4000 ;I4000 D2000 J4000 E2000 K4000 F2000 L4000

M203 X10000.00 Z10000 Y10000.00 U10000.0 V10000.0 A10000 B10000 C10000 D10000 
M203 a10000 ;I10000 D10000 J10000 E10000 K10000 F10000 L10000 

M201 X2000.00 Y4000.00 U2000 Z2000 V2000 A2000 B4000 C2000 D4000 
M201 a2000 ;I4000 D2000 J4000 E2000 K4000 F2000 L4000

M574 X2 S1 P"!20.io1.in"
M574 Y1 S1 P"!21.io1.in"
M574 Z2 S1 P"!30.io1.in"
M574 V2 S1 P"!40.io1.in"
M574 B2 S1 P"!50.io1.in"
M574 U1 S1 P"!31.io1.in"
M574 A1 S1 P"!41.io1.in"
M574 C1 S1 P"!51.io1.in"

;M574 C2 S1 P"!50.io1.in"

;
;M574 D1 S1 P"!70.io1.in"
;M574 a1 S1 P"!80.io1.in"
;M574 F1 S1 P"!90.io1.in"

 
;
;M574 G1 S1 P"!31.io1.in"
;M574 H1 S1 P"!41.io1.in"
;M574 I1 S1 P"!51.io1.in"

 
;
;M574 J1 S1 P"!71.io1.in"
;M574 K1 S1 P"!81.io1.in"
;M574 L1 S1 P"!91.io1.in" 

M208 S1 X-90 U-90 V0 Y0 A-90 B-90 C-90 D-90 a-90 ;F-90 G0 H0 I0 J0 K0 L0 S1                                     ; set axis minima
M208 S0 X90 U90 V150 Y150 A90 B90 C90 D90 a90 ;F90 G150 H150 I150 J150 K150 L150 S0

dc42

@Aurimas GCode is case insensitive, so you need to represent lower case letters by prefixing them with a single quote character, for example:

M584 'a2.0

Aurimas

@dc42 great - thank you. I will give it a go.

while I got you - am I correct that 3.4 version supports mroe axis than the 3.5?
what the reason to reduce the support?

dc42

@Aurimas maximum axes on the 6XD is 15 in 3.4.x and 30 in 3.5.x.

Aurimas

@dc42 I am confused.
in the docs it has less axis in 3.5 than it is in 3.4

U, V, W, A, B, Cnnn Driver number(s) for additional axes U, V, W, A, B and C (UVW available in RepRapFirmware 1.16 and later; UVWABC available in RepRapFirmware 1.19 and later; UVWABCD available in RepRapFirmware 3.0 and later; UVWABCDabcdefghijkl available in RepRapFirmware 3.3 and 3.4, Duet 3 MB6HC and MB6XD only; UVWABCDabcdef available in RepRapFirmware 3.5 and later, Duet 3 MB6HC and MB6XD only).

also in the docs says 15 movement axis + 8 extruders I believe. So I assume this part is outdated.

dc42

@Aurimas I have corrected the M584 documentation.

Where do the docs specify a limit of 15 axes + 5 extruders?

droftarts

@dc42 Here: https://docs.duet3d.com/User_manual/RepRapFirmware/RepRapFirmware_overview#firmware-configuration-limits

Is it that there are more axis names available than axes that can be set, ie not all can be used at once?

UVWABCDabcdefghijkl available in RepRapFirmware 3.3 and later

In 3.3 and 3.4, there are 22 axis labels, XYZUVWABCDabcdefghijkl, but a maximum of 15 axes.

additionally mnopqrstuvwxyz are available in RepRapFirmware 3.5 and later on Duet 3 MB6HC and MB6XD only

In 3.5, there are 36 axis labels, XYZUVWABCDabcdefghijklmnopqrstuvwxyz, but a maximum of 30 axes.

Ian

Aurimas

@dc42 also your correction states 15

The maximum number of axes supported on Duet 3 MB6HC is increased to 15 in RRF 3.3 and later. Axis letters abcdefghijkl may be used in addition to XYZUVWABCD. Because GCode is normally case insensitive, these must be prefixed with a single quote character in GCode commands. For example, M584 'A1.2 would assign axis 'a' to driver 1.2, and G1 'A10 would move the 'a' axis to the 10mm or 10 degree position (or by 10mm or 10 degrees if in relative mode).

dc42

@Aurimas thanks. I hadn't noticed that the notes about M584 mentioned the maximum number of axes supported. I have removed that mention and updated the table that @droftarts linked to in his post.

Aurimas

@dc42 thanks.

you probably should update this as well

MaxAxesPlusExtruders 25

dc42

@Aurimas said in UVWABCDabcdefghijkl - axis is not showing up:

@dc42 thanks.

you probably should update this as well

MaxAxesPlusExtruders 25

Where is that?

droftarts

@dc42 said in UVWABCDabcdefghijkl - axis is not showing up:

@Aurimas said in UVWABCDabcdefghijkl - axis is not showing up:

@dc42 thanks.

you probably should update this as well

MaxAxesPlusExtruders 25

Where is that?

https://docs.duet3d.com/User_manual/RepRapFirmware/RepRapFirmware_overview#firmware-configuration-limits

Ian

Aurimas

This post is deleted!

dc42

Thanks, now corrected.

Aurimas

@dc42 thank you