[BTT Pad 7] Find help, and help others.

[bassamanator]

Please use this discussion to ask for help, and help others, with the BTT Pad.

Note that I'm not a BTT Pad user.

[tjhayko]

I'm not sure if this is the correct place to ask this, but I'm trying to get my SV06plus working with a BTT Pad 7 based on bassmanator's instructions, but /dev/serial doesn't seem to exist :(

I've flashed CB1_Debian11_Klipper_kernel5.16_20240319.img.xz onto my SD card, so I think I'm on the latest OS for the BTT Pad 7 with CB1

[tjhayko]

I've traced the problem with /dev/serial not existing back to bad USB cable (even though it worked with multiple other devices :( ), but now I get the following the klippy.log:

mcu 'mcu': Timeout on connect
mcu 'mcu': Wait for identify_response
Traceback (most recent call last):
  File "/home/biqu/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
    params = self.send_with_response(msg, 'identify_response')
  File "/home/biqu/klipper/klippy/serialhdl.py", line 262, in send_with_response
    return src.get_response([cmd], self.default_cmd_queue)
  File "/home/biqu/klipper/klippy/serialhdl.py", line 319, in get_response
    self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
  File "/home/biqu/klipper/klippy/serialhdl.py", line 254, in raw_send_wait_ack
    self._error("Serial connection closed")
  File "/home/biqu/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'mcu': Serial connection closed

[tjhayko]

I think we can close this off. In addition to a bad USB cable, I also had a bad flash of the printer firmware. Using a different microSD card to flash the firmware seems to have fixed the issue, and I'm happily printing away (for the most part) now.

[bassamanator]

Turning a budget printer into a very reliable and consistent printer takes time and effort. Keep at it, because it's well worth it!