PanelDue and DWC show different axes



  • I used to have a U axis, but i've sinced reconfigured with a tool changer and removed it. I now have a C axis. I went through literally all of the config and macro files and found no references or definitions to and of the axis U.

    M409 K"move.axes" -- only shows X, Y, Z, C

    {
      "key": "move.axes",
      "flags": "",
      "result": [
        {
          "acceleration": 10000,
          "babystep": 0,
          "current": 1200,
          "drivers": [
            "0"
          ],
          "homed": true,
          "jerk": 1600,
          "letter": "X",
          "machinePosition": 152.626,
          "max": 270,
          "maxProbed": false,
          "microstepping": {
            "interpolated": true,
            "value": 16
          },
          "min": 0,
          "minProbed": false,
          "speed": 24000,
          "stepsPerMm": 200,
          "userPosition": 141.155,
          "visible": true,
          "workplaceOffsets": [
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        },
        {
          "acceleration": 10000,
          "babystep": 0,
          "current": 1200,
          "drivers": [
            "1"
          ],
          "homed": true,
          "jerk": 1600,
          "letter": "Y",
          "machinePosition": 133.033,
          "max": 293,
          "maxProbed": false,
          "microstepping": {
            "interpolated": true,
            "value": 16
          },
          "min": 0,
          "minProbed": false,
          "speed": 24000,
          "stepsPerMm": 200,
          "userPosition": 127.735,
          "visible": true,
          "workplaceOffsets": [
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        },
        {
          "acceleration": 2000,
          "babystep": 0,
          "current": 800,
          "drivers": [
            "5",
            "6",
            "7"
          ],
          "homed": true,
          "jerk": 120,
          "letter": "Z",
          "machinePosition": 28.5,
          "max": 580,
          "maxProbed": false,
          "microstepping": {
            "interpolated": true,
            "value": 16
          },
          "min": 0,
          "minProbed": false,
          "speed": 1200,
          "stepsPerMm": 1600,
          "userPosition": 4.8,
          "visible": true,
          "workplaceOffsets": [
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        },
        {
          "acceleration": 400,
          "babystep": 0,
          "current": 400,
          "drivers": [
            "9"
          ],
          "homed": true,
          "jerk": 6,
          "letter": "C",
          "machinePosition": 0,
          "max": 260,
          "maxProbed": false,
          "microstepping": {
            "interpolated": false,
            "value": 8
          },
          "min": 0,
          "minProbed": false,
          "speed": 5000,
          "stepsPerMm": 100,
          "userPosition": 0,
          "visible": true,
          "workplaceOffsets": [
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0,
            0
          ]
        }
      ]
    }
    

    What the heck is going on?

    IMG_20210205_145930.jpg IMG_20210205_145949.jpg IMG_20210205_150645.jpg



  • Best to post your config.g here and someone will take a look.



  • @alankilian I would normally agree, but I programmatically went through all files on my SD card searching for any reference. Here are all of them.

    looking for u.png



  • That demonstrated a search for a U for sure.

    If you want help, post your config.g and people will help.

    If you want to be prickly, you get what you put into the forum.



  • @alankilian I hear ya. BTW that search is for a u followed by at least one number.

    Happy to paste the configs.

    config.g

    ; Configuration file for Duet WiFi (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v3.1.4 on Tue Jul 21 2020 18:20:38 GMT-0700 (Pacific Daylight Time)
    
    ; General preferences
    G90                                                  ; send absolute coordinates...
    M83                                                  ; ...but relative extruder moves
    M550 P"RailCore II ZLT"                              ; set printer name
    M669 K1                                              ; select CoreXY mode
    
    ; Network
    M552 P192.168.1.201 S1                               ; enable network and set IP address
    M553 P255.255.255.0                                  ; set netmask
    M554 P192.168.1.254                                  ; set gateway
    M586 P0 S1                                           ; enable HTTP
    M586 P1 S1                                           ; enable FTP
    M586 P2 S1                                           ; enable Telnet
    
    ; Drives
    M569 P0 S0                                           ; physical drive 0 goes b
    M569 P1 S1                                           ; physical drive 1 goes f
    M569 P2 S0                                           ; physical drive 2 goes f
    M569 P3 S0                                           ; physical drive 3 goes f
    M569 P4 S0                                           ; physical drive 4 goes b
    M569 P5 S0
    M569 P6 S0
    M569 P7 S0
    M569 P8 S0  ; rev
    M569 P9 S0
    
    M584 X0 Y1 Z5:6:7 E3:4:8 C9; U2                               ; set drive mapping
    M350 C8 I0
    M350 Z16 I1                                          ; configure microstepping without interpolation
    M350 X16 Y16 I1  ; U16  ; configure microstepping with interpolation
    M350 E64:64:64 I0 
    M92 X200.00 Y200.00 Z1600.00 E3267:3267:3267 C100 ; U400       ; set steps per mm
    M566 X1600.00 Y1600.00 Z120.00 E1600.00:1600:1600:1600 C2        ; set maximum instantaneous speed changes (mm/min)
    M203 X24000.00 Y24000.00 Z1200.00 E12000 C5000 ; U6000   ; set maximum speeds (mm/min)
    M201 X10000.00 Y10000.00 Z2000.00  E1000  C400 ;U125  ; set accelerations per axis (mm/s^2)
    M204 P4000 T5000
    
    M906 X1200 Y1200 Z800 E600 C400 I30  ;U300                     ; set motor currents (mA) and motor idle factor in per cent
    M593 F36.92
    M84 S30                                              ; Set idle timeout
    
    ;M915 C S5 F0 H200
    ;M915 X Y S5 F0 H400
    
    
    ; Axis Limits
    M208 X0 Y0 Z0 C0 S1      ; U0                               ; set axis minima
    M208 X270 Y293 Z580 C260 S0 ; U28 
    
    ; Endstops
    M574 X1 S1 P"xstop"                                  ; configure active-high endstop for low end on X via pin xstop
    M574 Y1 S1 P"ystop"                                  ; configure active-high endstop for low end on Y via pin ystop
    
    
    
    ; Heaters
    M308 S0 P"bedtemp" Y"thermistor" T100000 R4700 B3950 H0 L0       ; configure sensor 0 as thermistor on pin bedtemp
    M950 H0 C"bedheat" T0 Q100                         ; create bed heater output on bedheat and map it to sensor 0
    M307 H0 B0 S1.00                                   ; disable bang-bang mode for the bed heater and set PWM limit
    M140 H0                                            ; map heated bed to heater 0
    M143 H0 S160                                       ; set temperature limit for heater 0 to 160C
                                        ; set temperature limit for heater 0 to 160C
    M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp
    M950 H1 C"e0heat" T1                                 ; create nozzle heater output on e0heat and map it to sensor 1
    M143 H1 S300
    M307 H1 B0 S1.00                                     ; disable bang-bang mode for heater  and set PWM limit
    
    
    
    ; Fans
    M950 F0 C"fan0" Q500                                 ; create fan 0 on pin fan0 and set its frequency
    M106 P0 C"Left Blower" S0 H-1                        ; set fan 0 name and value. Thermostatic control is turned off
    M950 F1 C"fan1" Q500                                 ; create fan 1 on pin fan1 and set its frequency
    M106 P1 C"Right Blower" S0 H-1                       ; set fan 1 name and value. Thermostatic control is turned off
    M950 F2 C"fan2" Q500                                 ; create fan 2 on pin fan2 and set its frequency
    M106 P2 C"Cold Section" S1 H1:2 T80                  ; set fan 2 name and value. Thermostatic control is turned on
    
    
    ; Tools
    M563 P0 S"One" D0 H1 F0:1                           ; define tool 0
    ;M563 P1 S"Two" D1 H1 F0:1                          ; define tool 1 - single hot-end
    ;M563 P2 S"Three" D2 H1 F0:1			    ; define tool 2 - single hot-end
    
    G10 P0 X-15 Y0 Z-23.70                                 ; set tool 0 axis offsets
    G10 P0 R0 S0                                         ; set initial tool 0 active and standby temperatures to 0C
    G10 P1 X0  Y0 Z0   ; single extruder 2-into-1
    G10 P1 R0 S0                                         ; set initial tool 1 active and standby temperatures to 0C
    
    
    
    ; Custom settings
    G21
    G90                                                  ; Send absolute coordinates...
    M140 S0 R0 
    M501
    M555 P2
    M584 X0 Y1 Z5:6:7 E3:4:8 C9                            ; U5 V6 W7  ; Map Z to drivers 5, 6, 7. Define unused drivers 3,4,8 and 9 as extruders
    M671 X-39:-39:380.88 Y2.747:272.05:123.14 S7.5               ;Front left,(-10,22.5) Rear Left (-10.,227.5) , Right (333,160) S7.5 is the max correction - measure your own offsets, to the bolt for the yoke of each leadscrew
    M83                                                  ; ...but relative extruder moves
    M929 P"eventlog.txt" S1                              ; Start logging to file eventlog.txt
    
    
    ; Miscellaneous
    M501                                                 ; load saved parameters from non-volatile memory
    M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"   ; set voltage thresholds and actions to run on power loss
    
    M98 P"config-user.g"
    

    config-user.g

    ; Z-Probe
    
    M950 S0 C"duex.pwm1"
    M557 X26:300 Y30:270 P16:16 ; mesh def
    M572 D0 S0.0 ; pressure advance
    ;M593 F46.5
    
    M566 E600:600:600; jerk
    
    
    ;M558 P8 C"!zprobe.in" H5 I1 A5 F1200 T48000 S0.05 R2
    M558 P8 C"zstop" H2 I1 A5 F50 T48000 S0.01
    
    
    ;G31 P500 Z0; Set Z probe (IR) trigger value and offset
    G31 P500 X17.99 Y0 Z0; Set Z probe (IR) trigger value and offset ; Y22.5
    
    ;M591 D0 S1 P7 C"e0stop" L2.2 R70:400 E150
    ;M591 D1 S1 P7 C"e1stop" L3.155 R50:300 E150
    
    
    
    M575 P1 S1 B57600 ; enable paneldue
    M376 H0.4 ; taper mesh compensation off after .4mm Z
    
    

    config-override.g

    ; config-override.g file generated in response to M500 at 2020-09-12 14:59
    ; This is a system-generated file - do not edit
    ; Heater model parameters
    M307 H0 A230.4 C645.8 D9.1 S1.00 V24.1 B0
    M307 H1 A334.9 C192.2 D3.5 S1.00 V24.3 B0
    M307 H2 A263.9 C152.8 D5.3 S1.00 V24.3 B0
    ; Workplace coordinates
    G10 L2 P1 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P2 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P3 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P4 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P5 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P6 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P7 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P8 X0.00 Y0.00 Z0.00 C0.00
    G10 L2 P9 X0.00 Y0.00 Z0.00 C0.00
    

  • Moderator

    From 3.2 release notes.

    When new axes are created using M584, if no R parameter is specified then the default for axes ABCD is now rotational. Use the R0 parameter if you want them to be linear.

    May be best practice to use UVW for additional linear axis since ABC is typically used for rotational.



  • @Phaedrux not sure how that helps here. C is a rotational axis.



  • AND THE OTHER WEIRD THING...

    if I hit the "home U" button on the paneldue, it actually triggers something even though there is no homeu.g script.

    Could a corrupt fike system on the SD card be to blame. I have 3 different duet powered printers and they all burn through SD cards to the point of not being formatable multiple times a year.



  • @Phaedrux @dc42 Any help here? still can't figure out how to fix this.


  • administrators

    I suspect that PanelDue is still using a fixed mapping between axis numbers and letters in at least some places, instead of reading them from the object model. @wilriker should be able to confirm this.


  • Moderator

    @gnydick From the picture you posted it looks to me as if you are still using PanelDueFirmware 1.24. Can you please confirm that? If so, then please update to 3.2.9 as ObjectModel-based axes-mapping is only available from PanelDueFirmware 3.2.x.



  • Thanks, all, will try.


Log in to reply