Is there a way to use that leviQ 2.0 sensor (inductive sensor)? Or is it not really a working solution and never was? Also did anyone succeed to use the original screen with klipper? I tried that thing but screen never tried to install that as firmware - i think it looking for firmware.bin which is not there.
Update: the screen solution would not work on our printer since the display model is different.
Hi there! I could be completely wrong, but I noticed that in your bed_mesh configuration, you entered:
[bed_mesh]
speed: 200
#mesh_min: 25, 17
mesh_min: 22, -13.5
mesh_max: 228, 200
algorithm: bicubic
probe_count: 10, 10
#mesh_pps: 4, 4
#bicubic_tension: 0.2
Shouldnât this be something like the following?
[bed_mesh]
speed: 200
horizontal_move_z: 2.5
mesh_min: 5, 5
mesh_max: 215, 215
probe_count: 5, 5
algorithm: bicubic
mesh_pps: 3, 3
bicubic_tension: 0.2
also, shouldnât the stepper z endstop_pin be !PB8 here?
[stepper_z]
step_pin: PC7
dir_pin: !PC6
enable_pin: !PC3
microsteps: 16
rotation_distance: 8
#endstop_pin: PB12 # heatbed sensor
**endstop_pin: probe: z_virtual_endstop**
#position_endstop: 0
position_min: -2
position_max: 230
homing_speed: 10
Hey, thanks for this guide. Have you managed to make any progress with the nozzle offset probe yet?
If not, have you been able to document the kind of data that the sensor outputs? I might take a stab at it this weekend but donât want to redo any work youâve already done
Hey,
I have a question about Klipper on this printer. Is there any speed difference between stock and klipper firmware? I have seen YT short about 13min benchy with Klipper - how to achive this result? Itâs quite impossible with speed 150mm/s (especially Y axis). I have checked resonance above 150mm/s and it looks like motherboard/stepper problem - not the mechanical issue (because construction is quite the same as PRO version, except uart mode).
I guess you can try to run same gcode provided by anycubic to see if it will do the same. I donât see a reason to go for as far as possible - the quality is more important and 150 covers most of my prints. With pla I havenât seen any issues on 250.
how did you get there?
ello,
my Kconfig looks like this:
# Kconfig settings for Huada HC32F460 processor
if MACH_HC32F460
config HC32F460_SELECT
bool
default y
select HAVE_GPIO
select HAVE_GPIO_ADC
select HAVE_GPIO_BITBANGING
select HAVE_STRICT_TIMING
select HAVE_GPIO_HARD_PWM
select HAVE_STEPPER_BOTH_EDGE
config BOARD_DIRECTORY
string
default "hc32f460"
######################################################################
# Communication interface
######################################################################
choice
prompt "Communication interface"
config HC32F460_SERIAL_PA7_PA8
bool "Serial (PA7 & PA8) - Creality Ender 2 PRO"
select SERIAL
config HC32F460_SERIAL_PA3_PA2
bool "Serial (PA3 & PA2) - Anycube"
select SERIAL
config HC32F460_SERIAL_PA15_PA9
bool "Serial (PA15 & PA09) - Voxelab"
select SERIAL
config HC32F460_SERIAL_PC0_PC1
bool "Serial (PC0 & PC1) - on LCD connector"
select SERIAL
endchoice
######################################################################
# Bootloader
# bootloader moves code and then VTOR.RESET points here:
######################################################################
config FLASH_SIZE
hex
default 0x40000
config FLASH_APPLICATION_ADDRESS
default 0x8000 # Aquila is 0xC000
config FLASH_BOOT_ADDRESS
hex
default 0x0
config RAM_SIZE
hex
default 0x8000
# use the fast RAM in the HC32F460
config RAM_START
hex
default 0x1fff8000
config STACK_SIZE
int
default 1024
config CLOCK_FREQ
int
default 200000000 # Voxelab uses 168000000
config MCU
string
default "HC32F460"
endif
Can you tell which lines to change to keep the Bootloader save?
Thanks in advance
Neuroplant
Solved
even when I updated the system via sudo apt-get update and sudo apt-get upgrade I still had to update Klipper via Webinterface.
After this the Kconfig looked like expected and I was able to add the option.
Unfortunately I am not able to update to Klipper Firmware as I lost the original 8GB SDCardâŚ
(Getting rid of z-Offset adjustment was the goal as it is crap, giving values fro 4mm to 0.4mm)
Hello @Neuroplant !
Please do us a favour: Either upload your code here as a file or use the Preformated Text feature of the editor to bring it in a proper shape.
I used the âHide Detailsâ feature in the Editor, but it obviously did not work.
âPreformatted Textâ is not what I was looking for
hi , thanks for bringing klipper to kobra 2.
i want to compile klipper v0.12.0-25-g99d7af87.
current i have v0.11.0-257-ged66982b-dirty
when i flash v012x there is no communication with mcu.
can somebody help me or provide prober firmware.bin?
sorry for my bad english . its not my first language.
kind regrads
edit:
got it working . make fresh pull of klipper in new direktory and compile firmware .
Has anyone installed KAMP with the Kobra2 and Klipper?
does the kobra 2 sensor work with it ?
A forum search for KAMP gave various results:
Was finaly able to flash the firmware (max 8GB SDHC)
I had some trouble with the z-Acceleration as the stepper slipped every now and then, e.g. at the end of the homing procedure.
So I compared the printer.cfg to the Configuration.h provided by Anycubic.
source
/**
* Default Max Feed Rate (mm/s)
* Override with M203
* X, Y, Z, E0 [, E1[, E2...]]
*/
#define DEFAULT_MAX_FEEDRATE { 300, 300, 5, 80 }
/**
* Default Max Acceleration (change/s) change = mm/s
* (Maximum start speed for accelerated moves)
* Override with M201
* X, Y, Z, E0 [, E1[, E2...]]
*/
#define DEFAULT_MAX_ACCELERATION { 3000, 3000, 500, 3000 }
(editing via M203/M201 is disabled)
vs.
source
[printer]
kinematics: cartesian
max_velocity: 300
max_accel: 5000
max_z_velocity: 100
max_z_accel: 800
Are there other Sources for these parameter?
I changed them in my personal printer.cfg to
[printer]
kinematics: cartesian
max_velocity: 300
max_accel: 3000
max_z_velocity: 5
max_z_accel: 500
these settings do not affect the print time very much.
Neuroplant
What needs to be added to the config to get the filament runout sensor to work?
[filament_switch_sensor runout]
pause_on_runout: True
switch_pin: !PC13
(not tested)
Neuroplant
Thanks! Iâll give that a shot.
Hi, i have the same problem as you. What did you do to fix it?
I also copied the text but it doesnt seem to work
Hi! love all the work that is being done with this printer but is there any chance that this would work with the kobra 2 neo as i decided to cheap out and buy that one instead and still want to use klipper on it.
hi, new to 3d printing and have a kobra 2, Iâve had issues with very unlevel bed issues so I thought ab klipper. started researching and found this to be the most prominent solution but I donât have a arduino, just a esp32
so i thought up a neat solution to my problem, which was to install klipper on linux, specifically i was gonna install it on a modded Nintendo switch that had switchroot/ubuntu and turns out, it works for now.
currently Iâm installing the custom firmware onto the printer from the switch, i used kiauh to setup the switch with mainsail and klipper so ill keep this updated on what happens.
now the solution could work on anything that can run a full distro of linux, such as old laptops or maybe rooted phones so i thought it would be a helpful tip for anyone who doesnât have the hardware at hand
Edit: the custom firmware doesnât seem to want to install, does some low tone beeps, 1234 ⌠1234 and just stuck at the anycubic screen, using official firmware works fine and brings it back to being abe to work. unsure the behavior Iâm supposed to get, if it did supposedly work on the printers part it doesnât on mine tho it may be simply because the config for the USB connection isnât setup to my specific situation, Iâm kinda stuck at this point now
@Function3D sorry for pinging but I followed crororoâs guide as it seemed to be more up to date, the issue seems to be with the USB connection anyways, could you help by any chance? (looked at logs and yes it is a problem with it No such file or directory: â/dev/serial/by-id/â)
With the help of function3d i was able to get it to work, i ended up having to use a proper distro of linux and changing the printercfg to the dir of the connected usb, i found it in /dev/ttyUSB0 but first had to uninstall brltty via apt remove, u can use dmesg -w to see what exactly happens when u connect the usb cable (if nothing then system/linux is not detecting it)
@Function3D I just got my Kobra 2 running with klipper from your guide. super easy aside from a minor snag with the USB assignment where i manually had to edit it in the printer config to point it in the right direction. anyway, easy fix and thanks for the quide.
do you have a link to the orca slicer profile you use? the link in the guide links to the cura mp4 video and not the orca slicer profile.
