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

    JustSumDad

    @JustSumDad

    0
    Reputation
    1
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location Vancouver Isl B.C. Canada Age 60

    JustSumDad Unfollow Follow

    Latest posts made by JustSumDad

    • RE: two things for ajustment on my Core XY

      @moth4017
      as per engikeneer here are the contents of those files but I find no mesh.g file in my system directory?
      I would like to adjust my homeall.g so that the Z is probed at the bed center and then the head moves back to Y275 leaving X as is...

      I am still working out how to deal with your M671 suggestion for lead screws.. its been some time since I built this printer and I am getting older, my mind is not what it was 🙂 the printer is a HEVO hypercube.
      the two Z axis motors are on separate drivers but I think the drivers are programed to move as one... I dont recall tho...

      ; homeall.g
      ; called to home all axes
      ;
      ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Mar 28 2020 12:55:30 GMT-0700 (Pacific Daylight Time)
      G91 ; relative positioning
      G1 H2 Z5 F6000 ; lift Z relative to current position
      G1 H1 X-243 Y280 F1800 ; move quickly to X or Y endstop and stop there (first pass)
      G1 H1 X-243 ; home X axis
      G1 H1 Y280 ; home Y axis
      G1 X5 Y-5 F6000 ; go back a few mm
      G1 H1 X-243 F360 ; move slowly to X axis endstop once more (second pass)
      G1 H1 Y280 ; then move slowly to Y axis endstop
      G90 ; absolute positioning
      G1 X-32 Y5 F6000 ; go to first bed probe point and home Z
      G30 ; home Z by probing the bed

      ; Uncomment the following lines to lift Z after probing
      ;G91 ; relative positioning
      ;G1 Z5 F100 ; lift Z relative to current position
      ;G90 ; absolute positioning

      ; bed.g
      ; called to perform automatic bed compensation via G32
      ;
      ; generated by RepRapFirmware Configuration Tool v2.1.8 on Sat Mar 28 2020 12:55:30 GMT-0700 (Pacific Daylight Time)
      M561 ; clear any bed transform
      G29 ; probe the bed and enable compensation

      posted in General Discussion
      JustSumDadundefined
      JustSumDad
    • RE: two things for ajustment on my Core XY

      ; Axis Limits
      M208 X-18 Y0 Z0 S1 ; set axis minima
      M208 X220 Y275 Z160 S0 ; set axis maxima Z288 when cooling tube removed

      ; Endstops
      M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
      M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
      M574 Z2 S2 ; configure Z-probe endstop for high end on Z

      ; Z-Probe
      M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
      M558 P9 C"zprobe.in+zprobe.mod" H5 F240 T18000 ; set Z probe type to bltouch and the dive height + speeds
      G31 P500 X29 Y10 Z2.2 ; set Z probe trigger value, offset and trigger height - Decrease to add more height.
      M557 X25:200 Y20:260 S20 ; define mesh grid

      8793e562-e330-42f6-9ccb-4408e23d2f6e-image.png

      Wow huh 🙂

      posted in General Discussion
      JustSumDadundefined
      JustSumDad
    • two things for ajustment on my Core XY

      My setup always parks the head after homing in the front left.
      its a bit in the way often, how can I set it to park in the back left?

      Also, I am not getting proper bed leveling, I have tried both a G32 or a G29 and my first layer is always a bit over squished in the front left area and too loose in the far right center

      thanx for any advise.

      posted in General Discussion
      JustSumDadundefined
      JustSumDad
    • RE: upgrade fw of duet 2 caused loss of wifi

      @droftarts said in upgrade fw of duet 2 caused loss of wifi:

      M997 S1 P"0:/sys/DuetWiFiServer.bin"

      THANK YOU!!

      That has me back to web control... now onto leaning what to do next 🙂

      posted in General Discussion
      JustSumDadundefined
      JustSumDad
    • upgrade fw of duet 2 caused loss of wifi

      Hi, been a while since I upgraded firmware as I was afraid I would have to go thru the whole setup again...
      So I finally bit the bullet and jumped from 3.01 to 3.51 today... kinda wish I didn't

      so... help 🙂 note - there is an asterisk symbol in the M588 command but its being stripped out by the forum -

      At this point I am at a loss... I am putting the complete response to M122 at the end here-
      Anyhow, as soon as I said yes to the upgrade in the web interface, it never came back...
      I finally got back in via putty and a usb connection...
      cant get wifi up tho...
      Most attempts to make adjustments to the wifi result in "another spi transfer is pending:

      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1
      Executing config.g... Error: M667 is no longer supported - use M669 instead
      HTTP is enabled on port 80
      FTP is disabled
      TELNET is disabled
      Warning: Heater 0 predicted maximum temperature at full power is 321°C
      Warning: Heater 0 predicted maximum temperature at full
      M588 S""
      Error: M588: use M552 to abandon the current connection attempt before using this command
      ok
      M552 S-1
      WiFi module stopped
      ok
      M552 S0
      ok
      M588 S"
      "
      Error: M588: Failed to reset the WiFi module to factory settings: another SPI transfer is pending
      ok

      M122
      === Diagnostics ===
      RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet WiFi 1.02 or later
      Board ID: 08DGM-95BNL-MGPSJ-6J1D2-3SD6T-9JZMW
      Used output buffers: 1 of 26 (11 max)
      Error in macro line 11 while starting up: M667 is no longer supported - use M669 instead
      === RTOS ===
      Static ram: 23256
      Dynamic ram: 72760 of which 220 recycled
      Never used RAM 14052, free system stack 194 words
      Tasks: NETWORK(1,ready,7.2%,519) HEAT(3,nWait 5,0.0%,328) Move(4,nWait 5,0.0%,359) MAIN(1,running,92.7%,514) IDLE(0,ready,0.0%,29), total 100.0%
      Owned mutexes: USB(MAIN)
      === Platform ===
      Last reset 00:05:06 ago, cause: power up
      Last software reset details not available
      Error status: 0x00
      MCU temperature: min 22.6, current 22.8, max 23.1
      Supply voltage: min 0.5, current 0.5, max 0.6, under voltage events: 0, over voltage events: 0, power good: no
      Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/60/0, gc cycles 0
      Events: 0 queued, 0 completed
      Driver 0: ok, SG min n/a
      Driver 1: ok, SG min n/a
      Driver 2: ok, SG min n/a
      Driver 3: ok, SG min n/a
      Driver 4: ok, SG min n/a
      Driver 5:
      Driver 6:
      Driver 7:
      Driver 8:
      Driver 9:
      Driver 10:
      Driver 11:
      Date/time: 1970-01-01 00:00:00
      Cache data hit count 4294967295
      Slowest loop: 4.45ms; fastest: 0.14ms
      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 0.6ms, write time 0.0ms, max retries 0
      === Move ===
      DMs created 83, 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
      === Heat ===
      Bed heaters 0 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
      Heater 1 is on, I-accum = 0.0
      === GCodes ===
      Movement locks 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 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
      Daemon is idle in state(s) 0
      Autopause is idle in state(s) 0
      Q0 segments left 0
      Code queue 0 is empty
      === Network ===
      Slowest loop: 0.29ms; fastest: 0.00ms
      Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
      HTTP sessions: 0 of 8
      === WiFi ===
      Interface state: starting2
      Module is disabled
      Failed messages: pending 0, notrdy 1, noresp 0
      Socket states: 0 0 0 0 0 0 0 0
      ok

      posted in General Discussion
      JustSumDadundefined
      JustSumDad