Use
/dev/serial/by-path/platform-.......
in the printer.cfg
[mcu]
serial: /dev/serial/by-path/platform-.......
complete /dev/serial/by-path/platform-.......
with your output
Use
/dev/serial/by-path/platform-.......
in the printer.cfg
[mcu]
serial: /dev/serial/by-path/platform-.......
complete /dev/serial/by-path/platform-.......
with your output
saved and restarted and also restart firmware - same issue. also tried plugging into different usb port and firmware restart
this same cable / printer / pi works correctly connecting with octoprint so I dont believe its a hardware issue
disconect the usb printer and run again ls /dev/serial/by-path/
then your printer has no klipper firmware
Not right now, prior to starting on installing Klipper
this should work if there is no communication with the printer it is because the printer does not have a properly functioning klipper firmware.
You can see my steps on building and installing the firmware on the printer. When I flash the printer its only about 8 secs between sets of 5 beeps. After install, printer only shows anycubic boot screen. seem correct?
I am able to successfully reflash the Kobra official firmware with no problem. Is it possible to post your firmware.bin? The options are the same, correct?
Private messaging is not yet unlocked for my user account can you please email me with best contact method. I am happy to pay consulting if needed.
aaron.basil at gmail
Now working! Thanks very much @Function3D
Issue was when I copied the text for the files /etc/udev/rules.d/10-usb-serial.rules and /etc/udev/rules.d/98-klipper.rules the CR / LF was lost so the entire text was commented out.
Hey,
First, thanks for the work.
But iāve a question.
does this also work with the āBIGTREETECH Pad 7 With Pre-Installed CB1 Core Board For Running Klipperā?
Because with the YT tutorials for the Pad 7, some steps are different.
if so, then I want to buy a Pad 7 and use it with the Kobra 2.
EDIT:
I just tested it now.
Simply followed a YOUTUBE tutorial on setting up Pad 7 and then set up the printer from @Crororo
and the Config.
and add the Part to the printer.cfg
Hey @Function3D,
I followed your instructions and everything works but the Print speed and Quality are Stock better. Do you know where the Issue could Lay?
I donāt know what could be happening to you, if you have my same printer and my same printer.cfg then the problem could be in the slicer.
So it could be the Slicers Fault, that the speed and the Quality is Slow and bad?
You choose the speed in the slicer, bad settings can also ruin the quality
This is awesome thank you so much. For everyone else who is a noob like me here were my mistakes:
Syntax error when typing in commands to putty āprompā instead of āpromptāā¦
Grabbed a non-data USB-C cable somehowā¦
Had to uncomment some things in the config file
Had to change my header gcode in cura sleightly
I am using Cura. It seems as though there is some gcode that gets inserted above the header in cura. I canāt figure out how to get the SET_PIN PIN=power_ctrl VALUE=1 code at the very top of the code. It starts heating before it runs the gcode headerā¦ Here is the example.
;FLAVOR:Marlin
;TIME:3851
;Filament used: 10.0322m
;Layer height: 0.2
;MINX:72.01
;MINY:34.46
;MINZ:0.2
;MAXX:149.99
;MAXY:187.64
;MAXZ:8.8
;Generated with Cura_SteamEngine 5.4.0
M140 S60
M105
M190 S60
M104 S200
M105
M109 S200
M82 ;absolute extrusion mode
SET_PIN PIN=power_ctrl VALUE=1
G90 ; use absolute coordinates
G28 ; home all axis
G1 Z5 F5000 ; lift nozzle
G92 E0 ; zero extruder
G1 Y3 F6000 ; move Y to purge point
G1 Z0.25 F5000 ; lower nozzle
G1 X60 E15 F500 ; Extrude 15mm of filament in a 5cm line.
G92 E0 ; zero the extruded length again
G1 E-3 F500 ; Retract a little
G1 X70 F4000 ; Quickly wipe away from the filament line
Has anyone managed to get the Z endstop probe working yet? Itās probably the only thing holding me back from making a total switch. (Iām lazy and also donāt like having features attached that I wonāt use)
I know that a script exists here to use multiple probes, but I donāt have enough knowledge of how Klipper works to alter it, and Iād rather make a clean switch if I can.
Iāve seen some people reporting the bed mesh goes screwy under klipper, has anyone else had that issue themselves?
Getting very fed up with the crippled marlin Anycubic have stuck on the printer, so Iām on the verge of switching.
I picked up a BTT Pad7 and set it up for multiple instances (3 instances). I downloaded the zip that gave me the following 4 files:
common.cfg
macros.cft
slot.cfg
printer.cfg
I discovered some paths referred by these configs are: printer_1_data but my multiple instances set up folders for printer_data, printer_2_data, printer_3_data and also Kobra2_ data
I switched the paths from printer_1_data to printer_data and after correcting my mcu serial port I got connection to my Kobra2. Now Iām getting an error as follows:
GCode path received from Klipper does not match expected location.
Received: ā/home/biqu/printer_data/gcodesā
Expected: ā/home/biqu/Kobra2_data/gcodesā
Modify the [virtual_sdcard] section Klipperās configuration to correct this error.
[virtual_sdcard]
path: /home/biqu/Kobra2_data/gcodes
If I switch my config file paths from printer_data to Kobra2_data then I no longer get connection. Suggestions?
Does this work for the Kobra 2 max or just the base model? Loved Klipper on my Vyper. Stock firmware on this is meh.