Hi, IDONTNOWCODING
For which reason did you root the machine and install ssh since it seems you don’t know how to use it?
I mean, what you want to do with secure shell? HOW did you installed ssh if you are stuck at tina promt?
Unless you know what you are doing just enjoy your machine and don’t mess with root, ssh, tina, is more complicated than what you might think.
Firstly my english is not that good sorry for that. I was using ssh succsesfuly with raspi to use klipper in my ender 3 v2 and I will need root access and ssh if people able to find a way to run klipper in this machines, by the way also I have root acces at my phone and I am running a different os, not the stock one. Ofcourse I will try to get root acces and other things that people shown here, how can I learn otherwise, I have changed root password succsesfully and installed dropbear thanks to people here who gave instructions and I am able to install back stock firmware succsesfully, saying you stay away from this kind of things, It’s deep etc. İs not helpfull
We are off topic but just a quick note for someone else who wants to use the camera from your proposed solution. Using fswebcam, python webserver and version 3.0.9 is not a good idea. Version 3.0.9 already use most of the available RAM and adding that much additional software running during printing (camera supposed to run during printing, otherwise it is useless tool) will create printing issues at some point depending on the selected printing speed and print complexity. I had to select stable speed (the lower one) for some prints to work correctly. Without the camera turned on all is good. So, if you need custom camera support, it needs to be done with dedicated simple webserver with small memory footprint and reading the pictures directly from the device driver, not from fswebcam that loads tons of libraries for all kind video formats when we have just 20MB free memory.
Honestly we are getting no where without that dsp xtensa compile tool.
The compile tool is real hard to get it seems like.
and you also need a license to even use it. Because it’s server sided.
It costs like $6500 something like that.
And there is a free trial but you need a business email and sign an nda and stuff.
Unless someone is willing to get sued.
https://www.cadence.com/en_US/home/tools/ip/tensilica-ip/hifi-dsps/hifi-4.html
And no one is willing to spend that much money for a printer that will be end of life in like 5 years or something.
But as said one could possibly use gcc to compile hopefully!
One said we could probably use gcc or something but it would be slower but it could work.
One already have a dev board to test on.
But everyone is busy and all that stuff.
I don’t think the real custom firmware with klipper will happen anytime soon.
BUT what we have done so far is we can customize the already available firmware and create custom firmware updates that has the original “app”.
So we can create custom images with modded/patched things.
You can put whatever you want on there.
So that’s all.
We plan to eventually release the tools repo to everyone so everyone can flash what they want.
You can patch/create custom updates and flash it via USB or ssh if you have it enabled.
Works for all k2max, plus and pro I believe.
But as said. This is not a real custom firmware that has klipper.
We just modified things that already exist on the printer.
Likely, you can count yourself lucky if it receives updates that long. I predict it will be max 2 years.
Sad to say, but this is a direct consequence of “shady” manufacturers who do not follow the OSS idea and release locked down and license violating products.
Anycubic went to great extremes WRT locking down on these printers.
Even more sad that most users will realize this trap after having bought such a printer.
The best thing you can all do is to spread such word and warn people to stay clear of this manufacturer. Only an impact to their business might make them rethink their policy.
Some more thoughts on this matter here: Importance of Open Source in 3D Printing and the Consequences of OSS License Infringement
1 Like
Just a note that I haven’t said anything because I’m still testing and such, but I’m close to finish replacing the kobra 2 pro motherboard with another one. There will be some “loss of funcionality” (as in, the motherboard is a bit less advanced) but honestly, given that I don’t want to work through the anycubic app, is a win win for me.
Hoping to have something more than “working on it” soon, so we have a backup plan to run Klipper on the pro.
What’s the compromise?
What do you lose as terms of functionality?
1 Like
In the tools repo that will eventually released when some things are finished you can just use kobra unleashed. It will be available to send via slicer directly. With a fake octopi api directly to the printer and print it. No need for anycubic app or slicer.
1 Like
Well, of course you can rip out the guts of the printer, but this is not how it is meant to be, right? And you pay extra bucks on the board and stepper drivers for something that looks like an Anycubic Kobra 2 but has nothing to do with it.
On the first glance, you will likely not be able to reproduce following items:
- [flow_calibration]
- [auto_leveling]
- [probe]
- [bed_mesh_probe]
- and potentially the display
1 Like
Because of budget constraints (if I spend more than 100$ in new motherboards, why not return the printer and spend those >100$ in buying a better one?) I ended up choosing the BTT SKR Mini, and I’m still trying to figure out how to hook the two accelerometers using a single SPI (and two GPIOs to the active pin). The other option (that I need to check) is sacrificing the screen and use screen SPI to drive the second accelerometer.
Unfortunately I have several projects running at the same time so this is going slow.
I think that option will be eventually better for anyone who doesn’t have its printer partially disassembled 
, specially if it can be packaged with accessible instructions so non-technical people can implement “just by following the steps”.
So, so far…
- auto-leveling works properly, SKR supports the magnetic probe, at least in theory. I still have to work the components together.
- The back switch for “zero out the Z” is basically a very sensitive switch, I was thinking of wiring it as a Z axis limit, and is just a matter of writing the proper commands to move the head to that position before Z-homing
- Display is non usable, as is directly driven, I am borrowing a display from another printer for now.
- One of the reasons I started modding the printer is precisely because flow calibration was not working for me (the printer underextruded quite a lot). Pretty sure was not properly calibrated and found no way to recalibrate it (at that point, with what we know now, could be possible). Maybe you mean resonance calibration? That indeed requires accessing the accelerometers. Good news is those are supported natively by klipper. Bad news is the board I chose only has a single SPI bus so they need to be shared.
Well, but what else can we do if AC doesn’t release the sources and the experts here can’t get a native Klipper running on the stock mobo (not even in combo with an extra host)? So replacing the stock mobo is literally the only option we then have to get Klipper running, right? 
Even tho it’s really sad and quite disappointing that it apparently won’t be possible to get a native Klipper running on the stock mobo somehow, I just wanted to shout out a huge THANK YOU GUYS for at least trying and putting all your time & efforts in this!
2 Likes
Echoing that. You really went the extra mile there!
Hi,
We have attempted to communicate with Anycubic regarding two critical security vulnerabilities we identified, in particoular one can be catastrophic if found by a malicious.
Despite our efforts over the past two months, we have not received a single response to our three emails. These vulnerabilities are significant, and we have invested considerable time and effort into addressing them.
Despite our initial intention to resolve the issue amicably, (and we still hope in it) it appears that our concerns have not been taken seriously by Anycubic.
Consequently, we are now preparing to disclose these vulnerabilities to the public
along with our repo and our tools.
1 Like
any way to get notified so I can fix it asap?
which board would you buy in hindsight for the spi issue?
in hindsight I should have returned the printer and spend the extra money towards buying a better (open source friendly) one. I was hoping to get this project finished at the end of January… and here we are
Now seriously, I think the more expensive boards are not worth the money, not because they are not good, but because i doubt the platform deserves spending more than that.
Having said that, BTT has boards (like the Manta M4P/M5P) that have a microcontroller and a socket for a raspberry pi Compute Module. If I understand the documentation correctly, you can plug the accelerometers directly to one of the SPI ports of the raspberry pi, thus negating the need of having to set it up on the microcontroller side, and I think for a while this was the more common method. Also, if you plan to use a raspberry pi as part of your build it results in a more compact package. You will still have to make custom cables, or some kind of adapter, so we’re not talking about a “plug and print” option.
I found the idea appealing, until I looked at CM prices (at least in december). You can buy some kind of CM clone from BTT but IDK how good it is, and in any case the whole package was outside my budget (which was “ideally no more than 50$, definitely less than 100$”). The M4P , with the CB1 and 4 drivers is 66€, and that’s with the clone. If you want a real CM4, pimoroni has them for 60 pounds so… On the other hand, the SK3Mini was like 32€ on sale, and is a pretty decent compact board.
Okay, cool. I was already planning on the Manta M5p + 5 controllers + compute module. It’s like. … $63 right now. I got my kobra 2 max for $300 from anycubic off ebay, so i see $370 being a pretty good deal still.
Wait, so I’m confused. So, the SKR Mini only has one spi port for one of the accelerometers, but you need two. What are you running klippy off of? Does it not have an extra spi port?
You’re not confused, just thinking that the project is one or two steps more completed than actually is. My final plan is to run klippy (in a docker) on a big server (that runs TrueNAS) that is next to the 3D printer. It used to run okto, it will run klipper&&Fluidd. Only limitation is no GPIO = sensors need to run on the MCU. I have a Pi as a backup but don’t want to use if I can wire it to the PC. But all of this is still on paper.
(Offtopic: My father asked me to build an cyanotype insolator and I’ve been dedicating the time I would work on this project for building that. Is a fairly straightforward build, just time consuming with lots of LED strips to wire, etc,)