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

    Posts made by Zasquatch

    • RE: Strange movement behavior after firmware update

      Well, that did it! Thank you for the help! Even though i feel like an idiot.....

      posted in Firmware installation
      Zasquatchundefined
      Zasquatch
    • RE: Strange movement behavior after firmware update

      @phaedrux said in Strange movement behavior after firmware update:

      I'm guessing you were using a firmware version earlier than 1.21 before?

      From the 1.21 release notes.

      On Cartesian and CoreXY printers, normal G0 and G1 moves are no longer allowed before the corresponding axes have been homed. In particular, if your homex.g, homey.g and homeall.g files raise Z a little at the start and lower it at the end, you will need to add the S2 parameter to those G1 Z moves. Otherwise the G1 Z move will be refused unless Z has already been homed and the homing macro will be terminated. If you want to allow axis movement prior to homing, put M564 H0 in config.g.

      https://github.com/dc42/RepRapFirmware/blob/dev/WHATS_NEW.md

      Thanks! I apparently missed the last line.... I will try M564 H0 and see what happens. Noteworthy that my movement commands all include S2 though and it still doesn’t work right!

      posted in Firmware installation
      Zasquatchundefined
      Zasquatch
    • Strange movement behavior after firmware update

      I recently updated my Duet WiFi to firmware version 2.02 beta 1 and have been getting strange behavior. When trying to set my IR probe height (mechanically) I am unable to move the Z axis with any preprogrammed buttons. They all warn that "insufficient axes are homed". But i cannot home Z until i set my height offset!

      I found a workaround to use G1 Z1 F6000 S2 in console, but that has mixed results as well. The machine will execute the command, but if you repeat it it will ignore it. If you change the Z value it will execute but not always completely right..... it will go the opposite direction, or go the right direction but not the requested value. I am getting puzzled so could use some help.

      X and Y buttons work properly after homing each axes, respectively.

      Thanks!

      posted in Firmware installation
      Zasquatchundefined
      Zasquatch
    • RE: Drawing / CAD model request

      Thanks! That should get the job done. I am creating a mount for a cyclops/chimera Aqua - don’t think any exist yet.

      posted in IR Height Sensor
      Zasquatchundefined
      Zasquatch
    • Drawing / CAD model request

      @dc42 Is there a CAD model or drawing posted somewhere? My sensor comes tomorrow and i was hoping to design a mount ahead of time. The link to the schematic is broken (at least when i try it from here).

      Thanks!

      posted in IR Height Sensor
      Zasquatchundefined
      Zasquatch
    • RE: New duet wifi, stepper driver fried

      Awesome, thank you!!

      Steppers were these:

      https://www.omc-stepperonline.com/hybrid-stepper-motor/nema-17-bipolar-18deg-65ncm-92ozin-21a-336v-42x42x60mm-4-wires-17hs24-2104s.html?search=Nema%2017%20bipolar&limit=100

      Current was set to 0.8A

      Board is powered by 24V meanwell PS

      posted in Duet Hardware and wiring
      Zasquatchundefined
      Zasquatch
    • RE: New duet wifi, stepper driver fried

      Thanks for the tip

      posted in Duet Hardware and wiring
      Zasquatchundefined
      Zasquatch
    • New duet wifi, stepper driver fried

      I am testing the electronics for my coreXY machine before final assembly- first is the x-y axis before moving on to frame construction and z-axis.

      After setting up power and comms, I hooked up x and y steppers and x/y end stops.

      I sent a "move x axis 10mm" gcode and at that point the X stepper driver exploded and started smoking.

      I held back hysterical crying because my wife was in the room, and disconnected everything. I took a lap and calmed down.

      I then tested all remaining stepper drivers with the motor and confirmed everything else was still functional. All other drivers move the motor without issue.

      Based on the analysis above, I think i must have the 1:1,000,000 defective board. Can someone please help? I have a picture showing the damage (two charred holes in the x-driver chip) that I can send via email.

      posted in Duet Hardware and wiring
      Zasquatchundefined
      Zasquatch