Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. jasko
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 12
    • Best 0
    • Controversial 0
    • Groups 0

    jasko

    @jasko

    0
    Reputation
    1
    Profile views
    12
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    jasko Unfollow Follow

    Latest posts made by jasko

    • SD CARD PROBLEM DUET 6HC V1.01

      Hi,

      I have this problem where my duet will not boot, here is a copy from YAT:

      M115
      FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.5.4 ELECTRONICS: Duet 3 MB6HC v1.01 FIRMWARE_DATE: 2024-11-24 10:47:10
      ok
      M39
      Error: M39: No SD card mounted in slot 0
      ok
      M122
      === Diagnostics ===
      RepRapFirmware for Duet 3 MB6HC version 3.5.4 (2024-11-24 10:47:10) running on Duet 3 MB6HC v1.01 (standalone mode)
      Board ID: 08DJM-956L2-G43S8-6J9D0-3S86S-9A36D
      Used output buffers: 1 of 40 (1 max)
      === RTOS ===
      Static ram: 155464
      Dynamic ram: 118376 of which 0 recycled
      Never used RAM 72152, free system stack 191 words
      Tasks: NETWORK(1,ready,8.7%,549) HEAT(3,nWait 6,0.0%,367) Move(4,nWait 6,0.0%,335) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,339) TMC(4,nWait 6,0.0%,67) MAIN(1,running,86.9%,444) IDLE(0,ready,4.4%,29), total 100.0%
      Owned mutexes: USB(MAIN)
      === Platform ===
      Last reset 00:01:12 ago, cause: power up
      Last software reset details not available
      Error status: 0x00
      MCU temperature: min 17.8, current 21.9, max 22.0
      Supply voltage: min 0.1, current 0.2, max 0.3, under voltage events: 0, over voltage events: 0, power good: no
      12V rail voltage: min 0.0, current 0.1, max 0.1, under voltage events: 0
      Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
      Driver 1: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
      Driver 2: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
      Driver 3: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
      Driver 4: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
      Driver 5: ok, SG min n/a, mspos 0, reads 0, writes 0 timeouts 0
      Date/time: 1970-01-01 00:00:00
      Slowest loop: 0.13ms; fastest: 0.07ms
      === Storage ===
      Free file entries: 20
      SD card 0 detected, interface speed: 12.5MBytes/sec
      SD card longest read time 0.0ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
      no step interrupt scheduled
      Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
      === DDARing 0 ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
      === DDARing 1 ===
      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 ===
      Movement locks held by null, null
      HTTP is idle in state(s) 0
      Telnet is idle in state(s) 0
      File is idle in state(s) 0
      USB is ready with "M122" 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
      File2 is idle in state(s) 0
      Queue2 is idle in state(s) 0
      Q0 segments left 0, axes/extruders owned 0x0000000
      Code queue 0 is empty
      Q1 segments left 0, axes/extruders owned 0x0000000
      Code queue 1 is empty
      === CAN ===
      Messages queued 364, received 0, lost 0, errs 349459, boc 0
      Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 364/0/0
      Tx timeouts 0,0,363,0,0,0 last cancelled message type 30 dest 127
      === Network ===
      Slowest loop: 0.12ms; fastest: 0.00ms
      Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
      HTTP sessions: 0 of 8
      = Ethernet =
      Interface state: disabled
      Error counts: 0 0 0 0 0 0
      Socket states: 0 0 0 0 0 0 0 0
      === Multicast handler ===
      Responder is inactive, messages received 0, responses 0
      ok

      I have tried many SD cards and formatting these as described in manual but I can not get it to work. This board was bought on reprapworld but they dont exist any more.

      Does anyone have some ideas?

      posted in Duet Hardware and wiring
      jaskoundefined
      jasko
    • Walls not touching only on one axis

      Hello,

      I am making one large 3D printer as you can see on images that I have attached. Everything works fine except I have some weird effect on Y axis ( dual Y). Using Duet 3 board with latest firmware. config.g
      Extruder is e3d titan aero with supervulcano hotend.

      When printing rectangle parallel to axes, as you can see on photos attached, walls are not touching on Y axis but on X axis everything is fine.
      IMG-1116cd6254bd9e8b1c6075ad9e3c0483-V.jpg IMG-e4a563ea2ec059d32e21a5ce02f9ee7f-V.jpg

      When printing some radius then walls come out some pattern in which one is shifted left and the next one is shifted right.

      20201202_161803.jpg IMG-2e2ea9a37bd777bcdd777f45bc80ab57-V (1).jpg

      Things I have tried up till now:

      1. Tightening belts, equal force on Y and X axis
      2. Reinforcing Z axis

      Does you have some ideas, is this software or hardware issue?

      posted in General Discussion
      jaskoundefined
      jasko
    • RE: Nozzle to high when printing BLTouch

      @Phaedrux Thank you this worked.

      posted in Beta Firmware
      jaskoundefined
      jasko
    • RE: Nozzle to high when printing BLTouch

      This is result of G31:

      Z probe 0: current reading 0, threshold 500, trigger height 0.700, offsets X0.0 Y0.0
      

      This is from config.g:

      G31 P25 X-38.2 Y-11 Z1.447							   ; Set Z probe trigger value, offset and trigger height
      
      posted in Beta Firmware
      jaskoundefined
      jasko
    • RE: Nozzle to high when printing BLTouch

      @DIY-O-Sphere Those are for headed bed, PID tuning.

      posted in Beta Firmware
      jaskoundefined
      jasko
    • RE: Nozzle to high when printing BLTouch

      @Veti said in Nozzle to high when printing BLTouch:

      M574 Z2 S1 P"io4.in" ; configure active-high endstop for high end on Z via pin io4.in

      I have removed it but nothing changes. 😞

      I'll make those changes for y axis for now it works.

      Should I eliminate z endstop switch? Can i use it for homing but instead of z probe homing? But I would still like to use mesh bed compensation?

      posted in Beta Firmware
      jaskoundefined
      jasko
    • RE: Large granite bed PID heater tuning (Beta tuning algorithm)

      @Phaedrux Alright, thanks.

      posted in Beta Firmware
      jaskoundefined
      jasko
    • RE: Nozzle to high when printing BLTouch

      Tried that but noting happens, its like this offset is ignored.

      posted in Beta Firmware
      jaskoundefined
      jasko
    • RE: Large granite bed PID heater tuning (Beta tuning algorithm)

      @Phaedrux Yes I used this one. It took 4 hours to complete but it was successful.

      posted in Beta Firmware
      jaskoundefined
      jasko
    • Nozzle to high when printing BLTouch

      Hi,

      I have issue that when I do z probe in home all when i go to G1 Z0 nozzle is 1mm away from build plate, so when print starts it is 1mm higher than it should have. I have done Z probe calibration many times. Mesh bed compensation also. Baby stepping does not work also I put even -0.5 but nothing happens, but it triggers some error that printer is out of limits... Any advice would be great. I am using latest beta firmware.

      homeall.g config.g

      posted in Beta Firmware
      jaskoundefined
      jasko