Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order
    1. Home
    2. e4d
    • Profile
    • Following 0
    • Followers 0
    • Topics 14
    • Posts 32
    • Best 2
    • Controversial 0
    • Groups 0

    e4d

    @e4d

    2
    Reputation
    4
    Profile views
    32
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    e4d Unfollow Follow

    Best posts made by e4d

    • RE: How to configure dependant X and Y axis

      @dc42 thank you I got it working. For those who might come later in this post here is my config for reference :

      M584 X0.0 Y0.1 Z0.2 A0.3 C0.4 E0.5 U1.0         ; set drive mapping
      
      M669 K0 X1:0:0:0:0:0 Y0:1:0:0:0:0 Z0:0:1:0:0:0  ; set kinematics parameters
      M669 K0 U0:0:0:1:0:0 A0:0:0:0:1:0 C0:0:0:0:-1:1 ; set kinematics parameters
      
      posted in Using Duet Controllers
      e4d
      e4d
    • RE: Low voltage on Duet3 6CH IO pins

      @jay_s_uk I had success with your proposition, thank you !

      posted in Duet Hardware and wiring
      e4d
      e4d

    Latest posts made by e4d

    • Problem with Duet3D Magnetic filament sensor

      Hello, I have trouble using the Duet3D magnetic filament sensor. I installed all the parts in the 3D printed case and tried to commision it as written in the Duet docs but keeps getting some errors :

      • At the very begining of the print it goes in pause directly and show "Too little filament"
      • I saw that the min and max value where way out of range of the "allow" range so I changed it to : M591 D1 P3 C"e1_stop" S1. I now have the print going without pause but the values are strange. Here's what I have in the console :
      M591 D1
      Duet3D rotating magnet filament monitor v4 on pin e1stop, enabled, sensitivity 28.80mm/rev, allow 0% to 500%, check printing moves every 3.0mm, version 4, mag 128 agc 58, measured sensitivity 2609.32mm/rev, min 0% max 1546% over 305.8mm
      

      I don't understand the min and max value that I get. Do you have any solution to put me in the right direction ? Thanks

      posted in Duet Hardware and wiring filament sensor
      e4d
      e4d
    • Set min and max PWM of fan

      Hello, I want to control a proportionnal pneumatic valve that need a PWM signal between 45% and 70%. I have it configured as a fan using theses commands :

      M950 F0 C"0.out2" Q1000
      M106 P0 S0 C"T0" B0.1 L0.45 X0.7
      

      In my understanding the value chose between 0% and 100% should be a proportionnal of the values between 45% and 70%. However when I try to plot the actual vs expected value I have the following curve :

      alt text

      Can you tel me why nothing change before S0.6 ? And how can I fix this ?

      posted in Using Duet Controllers
      e4d
      e4d
    • Can't edit daemon.g file

      Hello, I have an error when I want to edit the daemon.g file : "Error: Cannot delete file /sys/daemon.g because it is open"

      I thought it was because there is a while loop running in the daemon file so I tried using a runDeamon variable that could stop this while loop.

      Here's my daemon.g file :

      while global.runDaemon == true
          if global.var1== true
              ; suction
              if sensors.gpIn[0].value == 0 && sensors.gpIn[1].value == 1 ; high pressure
                  M42 P1 S1   ; start distr2
              if sensors.gpIn[0].value == 0 && sensors.gpIn[1].value == 0 ; low pressure
                  M42 P1 S0   ; stop distr2
          else
              M42 P1 S0	; stop distr2
      
          G4 S1	
      

      Can you please tell me how to bypass this problem ? Thanks

      posted in Using Duet Controllers
      e4d
      e4d
    • RE: Lots of heater fault since RRF 3.4

      @dc42 I have the error in around 1 in 10 prints when I'm actually printing. I always pre-heat the head before starting the print, the heating process don't give me error. But sometimes I have "temperature rising too slowly" error during the print (could be already an hour in).

      posted in Using Duet Controllers
      e4d
      e4d
    • RE: Lots of heater fault since RRF 3.4

      @dc42 I have it while printing at 210C. Here's my tuning :
      M307 H1 R2.096 K0.441:0.084 D5.95 E1.35 S1.00 B0 V24.3
      Pretty similar to your values

      posted in Using Duet Controllers
      e4d
      e4d
    • RE: Lots of heater fault since RRF 3.4

      @miss-rebekah Hello, I put it in the main config file. It has been rebooted several times since the begining so I'm sure it has been executed

      posted in Using Duet Controllers
      e4d
      e4d
    • RE: Lots of heater fault since RRF 3.4

      @jay_s_uk I used M303 T0 S210, so I guess I tuned it as a tool.

      My tool is a classic E3D Toolchanger bowden tool but I don't have the sock on. Never had for a year now and it worked great so I'm not sure why this would be the cause.
      da437c8a-6c89-4eed-8a47-3ff34368b58a-image.png

      posted in Using Duet Controllers
      e4d
      e4d
    • Lots of heater fault since RRF 3.4

      Hello, I updated to RRF 3.4 a few days ago and I now have a lot of heater fault (eg : Error: Heater 0 fault: temperature rising too slowly: expected 0.63°C/sec measured 0.10°C/sec). I already tried retuning the PID with M303 command but it doesn't change this behaviour. Is it something known in this version ? How can I correct this ?

      posted in Using Duet Controllers
      e4d
      e4d
    • RE: Can't disable negative Z coordinates

      I successfuly manage to set the limit with this command in the tpre2.g :

      ;Adjust Z axis limits to tool offset
      M208 Z{-tools[2].offsets[2]}:{move.axes[2].max}
      

      @dc42 thank you for your help on the previous point ! You said that in recent firmware the machine should not restore the old Z, mine does, is it a configuration somewhere ?

      posted in Using Duet Controllers
      e4d
      e4d
    • RE: Can't disable negative Z coordinates

      @dc42 I frequently change nozzle or work on my tools, that mean I need to update the tool offset and the tool macro everytime ? I think it would be way more practical is there was a way for the Duet to use the tool position as limit when a tool is selected.

      I have a Duet3 6CH with RRF3.3, here's my M122 :

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
      Board ID: 08DJM-956BA-NA3TJ-6J1DJ-3S46S-198YT
      Used output buffers: 3 of 40 (26 max)
      === RTOS ===
      Static ram: 150904
      Dynamic ram: 93648 of which 200 recycled
      Never used RAM 106584, free system stack 152 words
      Tasks: NETWORK(ready,29.2%,224) ETHERNET(notifyWait,0.3%,117) HEAT(notifyWait,0.0%,325) Move(notifyWait,0.0%,250) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,362) CanClock(delaying,0.0%,333) TMC(notifyWait,7.8%,59) MAIN(running,62.6%,944) IDLE(ready,0.0%,29), total 100.0%
      Owned mutexes:
      === Platform ===
      Last reset 00:51:27 ago, cause: power up
      Last software reset details not available
      Error status: 0x00
      Step timer max interval 584
      MCU temperature: min 11.1, current 29.1, max 29.6
      Supply voltage: min 23.9, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
      12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
      Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/12/12, gc cycles 0
      Driver 0: position 36450, standstill, reads 61776, writes 14 timeouts 0, SG min/max 0/0
      Driver 1: position 6450, standstill, reads 61747, writes 43 timeouts 0, SG min/max 0/65
      Driver 2: position 120000, standstill, reads 61776, writes 14 timeouts 0, SG min/max 0/0
      Driver 3: position 21481, standstill, reads 61738, writes 52 timeouts 0, SG min/max 0/1023
      Driver 4: position 0, standstill, reads 61738, writes 52 timeouts 0, SG min/max 0/1023
      Driver 5: position 0, standstill, reads 61735, writes 55 timeouts 0, SG min/max 0/204
      Date/time: 2022-03-15 12:17:01
      Slowest loop: 84.70ms; fastest: 0.05ms
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 25.0MBytes/sec
      SD card longest read time 3.3ms, write time 4.3ms, max retries 0
      === Move ===
      DMs created 125, maxWait 524449ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 2872, completed moves 2872, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 74], CDDA state -1
      === AuxDDARing ===
      Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === Heat ===
      Bed heaters = 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = 3 -1 -1 -1
      === 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 27798, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 15439/0/0
      Tx timeouts 0,9,15438,0,0,12348 last cancelled message type 30 dest 127
      
      === Network ===
      Slowest loop: 104.18ms; fastest: 0.02ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
      HTTP sessions: 3 of 8
      - Ethernet -
      State: active
      Error counts: 0 0 1 0 0
      Socket states: 5 2 2 2 2 0 0 0
      
      posted in Using Duet Controllers
      e4d
      e4d