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

    [Release 3.4.3] M555 not honored in config.g

    Scheduled Pinned Locked Moved
    General Discussion
    2
    3
    176
    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.
    • JuKuundefined
      JuKu
      last edited by

      As the subject line says. Last lines on my config.g are

      M564 H0    			; allow moves before homing
      M555 P6				; ok message comes after command done
      M118 P1 S"Duet 3 start"
      

      After reset, M564 reports movement before homing is allowed. From web interface M555 says "Output mode: RepRapFirmware", and from USB, it says "Output mode: Marlin". After sending M555 P6 manually from USB, it says "Output mode: NanoDLP" as expected.

      It still doesn't change it on the web interface. Is this as expected? Is M555 actually output channel specific? If so, is there a way to make it work for USB using a command in config.g?

      Here is the full config.g:

      ; Configuration file for Duet3, LitePlacer hardware
      ; executed by the firmware on start-up
      
      ; General preferences
      G90                                     ; send absolute coordinates...
      M550 P"LitePlacer"                      ; set machine name
      
      ; Network
      M551 P""                      ; set password
      M552 P192.168.86.206 S1                 ; enable network at fixed address
      M586 P0 S1                              ; enable HTTP
      M586 P1 S0                              ; disable FTP
      M586 P2 S0                              ; disable Telnet
      
      ; Drives
      M569 P0 S1                              ; physical drive 0 goes forwards
      M569 P1 S0                              ; physical drive 1 goes backwards (Y)
      M569 P2 S0                              ; physical drive 2 goes forwards (Z)
      M569 P4 S1                              ; physical drive 4 goes forwards (A)
      M584 X0 Y1 Z2 A4                        ; set drive mapping   ****** note A!! *******
      M350 X16 Y16 Z16 A16 I1                 ; 16x microstepping with interpolation
      M92 X160.00 Y160.00 Z400.00 A420.00     ; set steps per mm
      M566 X900.00 Y900.00 Z30000.00 A1200.00     ; set maximum instantaneous speed changes (jerk) (mm/min)
      M203 X30000.00 Y24000.00 Z15000.00 A4500.00 ; set maximum speeds (mm/min)
      M201 X2500.00 Y1500.00 Z1500.00 A250.00     ; set accelerations (mm/s^2)
      M906 X800 Y1200 Z600 A400 I20            ; set motor currents (mA) and motor idle factor in per cent
      M84 S10                                 ; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y0 Z0 S1                        ; set axis minima
      M208 X400 Y600 Z40 S0                   ; set axis maxima
      
      ; Endstops (active low)
      M574 X1 S1 p"!io0.in"		; X home
      M574 Y1 S1 p"!io1.in"		; Y home
      M574 Z1 S1 P"!io2.in"		; Z home
      
      ; M574 X2 S3			; stall
      
      ; Z-Probe
      M558 K1 P8 C"!io3.in"		; create z probe: To pin io3.in, fast switch, probe #1, inverted
      
      ; Heaters
      
      
      ; Fans
      
      ; Tools
      M563 P0 S"Dummy"	; create a dummy tool and name it (for probing to work)
      T0			; select it
      
      ; 
      M453				; CNC mode, make all g0 moves at max set speed
      M950 P4 C"out4"		; output pin for down cam LED
      M42 P4 S1			; switch it on
      M950 P5 C"out5"		; output pin for up cam LED
      M42 P5 S1			; switch it on
      M950 P6 C"out6"		; output pin for testing
      M42 P6 S0			; switch it off
      M950 P7 C"out7"		; output pin for pump
      M42 P7 S0			; pump off
      
      M950 P8 C"out8"		; output pin for valve
      M42 P8 S0			; valve off
      
      M564 H0    			; allow moves before homing
      M555 P6				; ok message comes after command done
      M118 P1 S"Duet 3 start"
      
      jay_s_ukundefined 1 Reply Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @JuKu
        last edited by

        @JuKu its channel specific I believe, so you'd have to send it from USB to get it on that channel, although the docs here seem to suggest otherwise https://docs.duet3d.com/en/User_manual/Machine_configuration/Configuration_nanoDLP

        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

        JuKuundefined 1 Reply Last reply Reply Quote 0
        • JuKuundefined
          JuKu @jay_s_uk
          last edited by

          @jay_s_uk Seems you are right. No problem, I can do that.

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