Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login
    1. Home
    2. Vaibhav Jain
    • Profile
    • Following 0
    • Followers 0
    • Topics 1
    • Posts 5
    • Best 0
    • Controversial 0
    • Groups 0

    Vaibhav Jain

    @Vaibhav Jain

    0
    Reputation
    2
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Vaibhav Jain Unfollow Follow

    Latest posts made by Vaibhav Jain

    • RE: Dimensional Issue - (Hexagon side-to-side length)

      @norder
      Yes the measurements were taken from the printed hexagon (side to side length of 75 mm as per design).

      Is the shrinkage uniform on all 3 sides ?

      I am trying to reduce the length-difference amongst all sides. Once the dimensions are precise (equal on all sides), I can play with diagonal rod length or M579 to get the dimension accurate if required.

      posted in Using Duet Controllers
      Vaibhav Jainundefined
      Vaibhav Jain
    • RE: Dimensional Issue - (Hexagon side-to-side length)

      @phaedrux
      Okay.

      If I change the calibration routine from S6 to S7 or S8 or if there is a hardware change, do I need to delete the config-override.g before calibration ?

      posted in Using Duet Controllers
      Vaibhav Jainundefined
      Vaibhav Jain
    • RE: Dimensional Issue - (Hexagon side-to-side length)

      @phaedrux

      I did as per the instruction. I did the S6 calibration.

      The new dimensions of the hexagon are:
      Against tower Z: 74.52 mm
      Against tower X: 74.62 mm
      Against tower Y: 74.90 mm

      Surprisingly, the max deviation has come down to 0.38 mm from 1 mm, which is still a huge deviation.

      Shall I try a S7 calibration ?

      posted in Using Duet Controllers
      Vaibhav Jainundefined
      Vaibhav Jain
    • RE: Dimensional Issue - (Hexagon side-to-side length)

      @Phaedrux

      Bed - bed.g
      Configuration - config.g
      Config override - config-override.g
      Homing - homedelta.g

      M98 P"config.g"
      Turn off the current WiFi mode before selecting a new one
      HTTP is enabled on port 80
      FTP is disabled
      TELNET is disabled
      Warning: Heater 1 predicted maximum temperature at full power is 500°C

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0 (2022-03-15 18:58:31) running on Duet WiFi 1.02 or later
      Board ID: 0JD0M-9X6JA-JUNSN-6JKFJ-3SD6K-T9R3U
      Used output buffers: 3 of 24 (13 max)
      === RTOS ===
      Static ram: 23868
      Dynamic ram: 73872 of which 36 recycled
      Never used RAM 14304, free system stack 184 words
      Tasks: NETWORK(ready,13.0%,243) HEAT(notifyWait,0.0%,316) Move(notifyWait,0.0%,364) MAIN(running,86.2%,448) IDLE(ready,0.8%,30), total 100.0%
      Owned mutexes: WiFi(NETWORK)
      === Platform ===
      Last reset 00:02:12 ago, cause: power up
      Last software reset time unknown, reason: User, GCodes spinning, available RAM 14184, slot 2
      Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
      Error status: 0x00
      Aux0 errors 0,0,0
      Step timer max interval 0
      MCU temperature: min 25.0, current 30.6, max 31.1
      Supply voltage: min 23.8, current 24.1, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes
      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: standstill, SG min n/a
      Driver 1: standstill, SG min n/a
      Driver 2: standstill, SG min n/a
      Driver 3: standstill, SG min n/a
      Driver 4: standstill, SG min n/a
      Driver 5:
      Driver 6:
      Driver 7:
      Driver 8:
      Driver 9:
      Driver 10:
      Driver 11:
      Date/time: 2022-10-08 10:42:57
      Cache data hit count 4294967295
      Slowest loop: 6.34ms; fastest: 0.18ms
      I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
      === Storage ===
      Free file entries: 10
      SD card 0 detected, interface speed: 20.0MBytes/sec
      SD card longest read time 3.7ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
      === MainDDARing ===
      Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 0 -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
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Code queue is empty
      === Network ===
      Slowest loop: 15.93ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
      HTTP sessions: 1 of 8

      • WiFi -
        Network state is active
        WiFi module is providing access point
        Failed messages: pending 0, notready 0, noresp 0
        WiFi firmware version 1.26
        WiFi MAC address 4a:3f:da:a6:f0:2c
        WiFi Vcc 3.36, reset reason Power up
        WiFi flash size 2097152, free heap 25896
        WiFi IP address 11.11.11.11
        Connected clients 1
        Clock register 00002002
        Socket states: 0 0 0 0 0 0 0 0
      posted in Using Duet Controllers
      Vaibhav Jainundefined
      Vaibhav Jain
    • Dimensional Issue - (Hexagon side-to-side length)

      I have a custom built 3D printer with a Duet 2 Wifi and Smart Effector.
      For dimensional calibration, I 3D printed a hexagon of side-to-side length of 75 mm.
      Here is the dimension after printing:
      Against tower Z: 75.00 mm
      Against tower X: 75.60 mm
      Against tower Y: 74.50 mm
      (Almost upto 1 mm variation)

      I have tried calibrating using S6, S7 and S8 factor. The value of each length changes but the relative difference in dimension upto 1 mm remains.

      I have checked the length of diagonal rods multiple times. They are all equal. I have also printed two cubes of height 20 mm and 120 mm. The steps per mm are correct.

      What is that I am missing? How can I rectify this issue ?

      I have attached the image of printed hexagon.
      Kind Regards

      Image.jpg

      [link text](link url)

      posted in Using Duet Controllers
      Vaibhav Jainundefined
      Vaibhav Jain