So, I have no clue what’s going on here… I was able to get my two creality machines working great, but for some reason this Kobra go is giving me issues. Sometimes the z will work, sometimes it won’t. I haven’t been able to successfully start a print. The printhead crashes into the bed because Z won’t go up… Or down … after a firmware reset, it USUALLY homes all axis, no problem at all at any point on x and y, but z is hit or miss.
If z is working and I do a bed mesh calibrate, it gets like 2-4 points in then z doesn’t raise up and I get a probe triggered before movement error. I reflashed klipper and still have the same issue. I flashed the anycubic firmware and everything works flawlessly. Checked all the cables and no issues there. Used the sample .CFG from klipper git, used two to three other custom cfgs and all the same thing. Everything is updated and I’ve rebooted the host a number of times. I’m really at a loss, I would like to get this working if anyone has any suggestions!
Edit: forgot to mention if I try homing all after z stops working, x and y will go but I just get a loading circle on the home button and then the operation times out. klippy (12).zip (49.1 KB)
Could you attach your klippy.log into the post as you were instructed to and not put it on another site? If it’s too big, .zip it and attach the .zip file.
What is your endstop? You have an endstop pin defined in for you z extruder (PC14) and you have a probe defined at PA1.
If you want to use the probe, then you z extruder endstop parameter should be:
zip file added to bottom off original post. i was on my phone when i posted last night and i didnt have access to the log. anyways, this is how everyone else i talked to has the cfg for their kobra go set up, and they run it with no issues.
the issue isnt with the probe, though. it happens regardless if its probing or not, unless the z endstop is interfering with the probe in some way, but that still does not explain why the same setup works for others
You haven’t answered my question “What is your endstop?”. You have two pins that you seem to be using.
As part of “What is your endstop?” could you explain what is the actual sensor mechanism (ie switch, BL Touch, inductive sensor, etc.)?
If you’re running Mainsail (I’m not sure about Fluidd), can you go to “Endstops” (at the bottom of the “Machine” page) and see the Z stop both “TRIGGERED” (something being detected) and “OPEN” (nothing for the endstop to detect).
Don’t worry about “everyone else”, let’s just focus on you and your problems.
I am using the optical z endstop, not the inductive probe as the endstop. all endstops and probe say open. when z works and i home, it homes x and y, moves to -5,-5 (ish) z goes down to the optical end stop, then moves to the bed .
Could you post a picture of your endstop? I’m not sure what you mean by saying it’s “the optical z endstop”.
Which pin is it connected to? Can you put something in front of/under the “optical z endstop” so that it is recognized as "TRIGGERED’ on the Mainsail Config page?
Thanx for the images, although I’m not sure what the top one is showing exactly.
Could you comment out your [probe]printer.cfg parameter (and the statements following)? Test from there - see if you still detect the endstop.
Next, remove the comments on the [probe] parameter and replace the line endstop_pin: ^PC14 with endstop_pin: probe:z_virtual_endstop and Test from there - see if you still detect the endstop.
I’m trying to figure out which one is actually active and connected to the controller so we can focus on that.
i dont think the sensor is the issue, everything works completely fine using the original anycubic firmware. when the z does actually work (which it really hasnt lately), all the sensors trigger fine. its funny though…i had a spare creality board laying around so i decided to switch everything out to maybe get that to run with klipper. i havent got around to doing that quite yet, but i put the ender firmware on it, stock, mriscoc, jyers…tried all three…now the z axis works perfectly, but the x and y wontt home. they both move 10mm in the opposite direction of the limit switch then stop.
It will be interesting to see what happens when you load Klipper on it.
I will not be surprised if the problem comes up on the new main controller board; I don’t think we understand what is the actual Z axis endstop using and what is its characteristics.
Could you ask the other people you’re getting the information from (and are running Klipper successfully) to explain how the Z axis endstop works (ideally with a part number) and what pin it is wired to?
Im wondering if it isn’t the limit switches needing to be replaced for something more similar to the creality one. I don’t have the optical end stop hooked up with the creality board as I have a BL touch installed on it, and the z axis is working fine. The x and y limits are slightly different but I wouldn’t think it would be an issue, but who knows?
A redditor by the name of catnippr has a super in depth guide to the Kobra go/neo, both he and his guide has helped me out a lot since I started this hobby. To anyone who has a go or neo I definitely suggest checking it out Kobra go/neo guide
Here’s a couple screenshots of the optical limit switches from his page
Also, I will try what you mentioned about commenting the sections out. I have some time in the morning so I can swap the boards back and test it out. I need to figure out if I can add another instance of klipper or if I have to uninstall and run kuiah again with a 4th instance to swap between the 2 boards.
The Z axis endstop sensor is an “Optical Interrupter” and the X/Y endstop sensors are “microswitches”. Nothing to see here.
Regardless, you’re still not answering my question - which pin is the Z axis endstop sensor connected to? It’s either PA1 or PC14 - I suspect that it’s PC14 because that’s working but I’d like to know where you got the [probe] statement with PA1.
I’m guessing you’re not comfortable with understanding the configuration of your printer but if you want help to get it working reliably, we have to know which pin is being used by Klipper for the endstop.
man, i cant find a pinout diagram for the trigorilla v3.0.7 board anywhere. I’m fairly comfortable with electronics, but I wouldn’t know how to figure out which pin the ports are connected to. The chip is a huada hc32f450, but I don’t know if they’re configured differently between different board manufacturers. However, I did get the creality board working, turns out it just didn’t like the anycubic stock limit switches. Anyways, here’s the board with the probe and z limit marked
