Flying Bear Reborn 2 | Part 4 - Installing Klipper on the Flying Bear Reborn 2

Поділитися
Вставка
  • Опубліковано 18 гру 2024

КОМЕНТАРІ • 8

  •  Рік тому +1

    Hi So after trying to get this thing going I find that a lot of the silk screens was wrong and also the PE7 for the neopixels never worked.
    I tested the uart 3 and its all backwards so tx rx are actually ground and 5v..? and so i used the bltouch setup for the neopixels and the uart 3 works ok for the bltouch , Just how its worked out I think the other way around would work fine also.
    So the RX is the 5v , The Tx is the Ground and The Gnd im guessing is the TX.. but is actually PB10.
    Tes your own with a multimeter, which is what i did as its all seems screwed up.. an odd board as even MKS don't have info for it. Im guessing prototype of bad silk screened versions cheap..

    • @digitaldragon72
      @digitaldragon72  11 місяців тому

      I agree Les. The MKS Robin board has many permutations as this board is heavily customized to OEM requirements. There is no specification or validated Pin Diagram for the version in the Reborn 2.

  • @leighdodd1762
    @leighdodd1762 Рік тому

    Where did you get the cloth split wire sheathing from ?

    • @digitaldragon72
      @digitaldragon72  Рік тому

      I get it from Amazon. MGI SpeedWare Woven Mesh Split-Sleeve Wire Loom for High-Temperature Automotive Harness and Home Cable Management - 25 feet (1/4") www.amazon.com/dp/B07HXSL2SH?psc=1&ref_=cm_sw_r_apin_ct_WDKZ51R0YJEEK4CGVZ5G&language=en_US

  • @dennydraco
    @dennydraco Рік тому +1

    Hello, the communication issue that you discovered was the setting for client / host. Was that just commenting out one line in the Klipper config ?

    • @digitaldragon72
      @digitaldragon72  Рік тому +1

      There were actually a few lines that needed to be commented out for the config to work. The config I used was from @3DPrintSOS and this was after he had configured the Raspberry Pi to act as a second Klipper MCU (needed to make the stock display work for Klipperscreen) The lines I needed to comment out were:
      #[mcu rpi]
      #serial: /tmp/klipper_host_mcu
      #####################################################################
      # BEEPER
      #####################################################################
      #[output_pin BEEPER_Pin]
      #pin: rpi:gpio17 # for Raspberry Pi
      #pwm: True

  • @3DPrintSOS
    @3DPrintSOS Рік тому +1

    For those just hopping on, what was the errant line in the config?

    • @digitaldragon72
      @digitaldragon72  Рік тому

      So the lines were not necessarily errant, but just not needed yet. There are a few lines that your config included to make the stock display work in Klipper as a Klipperscreen. The fact that you have Input Shaper values and called out the Beeper pin as 'rpi:gpio17' was tickling the back of my brain but I for some reason I kept looking past the second MCU config. I will be uncommenting this section tonight as I wire up the stock display for use with Klipperscreen.
      The lines in question are:
      #[mcu rpi]
      #serial: /tmp/klipper_host_mcu
      #####################################################################
      # BEEPER
      #####################################################################
      #[output_pin BEEPER_Pin]
      #pin: rpi:gpio17 # for Raspberry Pi
      #pwm: True