HBVCAM camera case for K1 printers
Obliczymy ostateczną cenę na podstawie wybranego pliku. Sprawdzisz ją i zaakceptujesz przed płatnością.
Zapisane na tym urządzeniu.
A case allowing you to mount an HBVCAM OV2720 to a K1 printer
- Ocena
- 0 / 5
- Polubienia
- 10
- Pobrania
- 16
- Wydruki
- 0
- Wyświetlenia
- 203
- Oceny
- 0
Aktualizacja u źródła:
Informacje o modelu
- Źródło
- Printables
- Kategoria
- Creality Parts & Upgrades
- Licencja
- Creative Commons — Attribution — Noncommercial
Need a cheap replacement for your K1 Camera, and/or are tired of the limited functionality of the stock camera? This mount allows you to use a cheap HBVCAM as a replacement. Not the best photo quality, but with the right software, you are able to mess around with the camera settings. It's only a 2MP, but you can probably source a better camera and remix the mount to fit it.
You only need a single M3 screw to assemble. The camera should simply slot right in from the top. The top cover is optional. You will also need to either repin the existing camera wire in order to connect the new camera or make your own jumper/adapter cable, which I recommend. The color of the wires matches between the OEM cable and the USB cable that comes with the camera. All you'll need is a single 1.25mm male picoblade “JST” connector, which you will splice into the included camera cable.
![]() | You only need to pin the 'bottom" four cables you see on the right. The second black cable on the left is the wire shielding. |
Note: Klipper automatically detects and can use the camera as-is. However, if you want access to camera controls, such as white balance and brightness, you will need to install DaVinci-10's camera macros.
You will need to modify the v4lctls.cfg to work with this camera. I have uploaded my cfg that may or may not work out with your printer (no guarantees). You may have to SSH into your printer and run some commands to find the appropriate location of the camera, which you will enter here:
[gcode_shell_command v4l2-ctl]
command: v4l2-ctl -d #insert camera location here. In my case it was /dev/video4/dev/video4
timeout: 5.0
verbose: True[gcode_shell_command v4l2-ctl] command: v4l2-ctl -d /dev/video4 timeout: 5.0 verbose: True
Once you verify the macros are working, you just need to tune it to your heart's content. I would take screenshots and feed them to Copilot and ask it to help me tune it with the macros I had available.
