ZeroG Mercury One destructive testing

Поделиться
HTML-код
  • Опубликовано: 6 сен 2024

Комментарии • 14

  • @categoricallybiased1673
    @categoricallybiased1673 Год назад +1

    Cant fool me George Lucas I know you by your voice!

  • @matthewschultz899
    @matthewschultz899 2 года назад +1

    0:53, best part! This deserves a best printer video award. It's like the naughty robot moments from Iron man!
    Have you tried spread cycle instead of stealth chop? Much faster at minimal extra noise.

    • @kamermans2
      @kamermans2  2 года назад

      Haha, bad robot indeed! I normally run SpreadCycle but I was trying to get a little more torque out of my drivers. It's back on SpreadCycle now :)

  • @seanwolfe9321
    @seanwolfe9321 3 месяца назад

    I am interested in the mercury one for my Ender 5pro. Seeing how fast X, Y move is incredible, but obviously you can’t print at that speed…. What are your experiences with that?

  • @josephyoo2100
    @josephyoo2100 Год назад

    That’s some high tech bottom panel cover 😂

  • @mongini1
    @mongini1 2 года назад +1

    wow... that crashed pretty hard xD
    who are you on the ZeroG btw?

    • @kamermans2
      @kamermans2  2 года назад +1

      Haha, yep, looks like it's OK though 😅. I'm srkthain, although perhaps I'll update my username so it's more obvious.

  • @kylelongstaff
    @kylelongstaff 2 года назад +1

    I like It.
    But there's literally no way you can acheive even half those speeds on single Z.
    My E5 starts making wonky layer lines at 60mm/s lol.

    • @kamermans2
      @kamermans2  2 года назад

      Yes, you're absolutely right, I'm going to have to do the Hydra mod with triple Z auto-leveling.

  • @KGV_Studios
    @KGV_Studios 2 года назад

    How to you do these test?

  • @tavarisjones551
    @tavarisjones551 2 года назад

    What was the cause of the crash. It almost looks like it thought that it hit the x endstop

    • @kamermans2
      @kamermans2  2 года назад +1

      The crash was caused by insufficient current running to the motors, which caused the motor to skip while accelerating or decelerating, thereby losing track of its position and ultimately slamming into the frame.

    • @JP.Alonso
      @JP.Alonso 2 года назад

      @@kamermans2 have you tried to install 4 limit switches to avoid those crashes?

    • @kamermans2
      @kamermans2  2 года назад

      @@JP.Alonso I did wonder if klipper supported that, but my understanding is that the limit switches aren't checked unless it's homing. I guess I could cobble something together with an arduino and some interrupts 🤔