Flsun Super Racer Klipper Issues and wondering if klipper doc will ever be updated

I am trying to see if the Klipper Documentation will ever be updated i have read through it multiple times to solve my own issues when switching to klipper but it seems like a lot of people here get mad or upset when asking questions or having issues with klipper but the Documentation is years out of date and still doesnt have standard config files for flsun super racer which has been out over a year now and A lot of others have gotten down right mad over someone asking a beginner question or maybe they just dont understand the correct format. I have used the Klipper Documentation entirely to help me make the switch and where marlin has a entire community around it willing to help any time and updates there material consistently which most are probably user ignorance but still when your reading documentation that is no longer relevant and not even klipper understands certain codes in the documentation or is now obsolete. Everyone keeps referencing to the klipper documentation but it is way outdated and in desperate need of a refresh. I just feel that if the documentation was up to par or at least regularly updated then it would cut down on a huge portion of the groups time and also help new commers or beginners work out there problems. Still after all of this time over a year now there is no klipper config file for a Flsun Super Racer Delta Printer so its like playing Russian roulette everyone here ends up cutting copying and pasting a config file that we are not sure is even close or may destroy the printer entirely and many others are missing as well

In the documentation is specifically states to lower z height minimum to -2 during leveling but to zero this out before printing to avoid the nozzle crashing into the bed, Every time i change it to zero after leveling is complete the print head stops about 30mm above the bed and just says out of range but if i change it back then sometimes it works ok then sometimes out of the blue crashes into the bed for no apparent reason. I do all of my leveling even manually delta calibrate, manual bed mesh and manual z height and still slammed right into the bed.

After Leveling and setting the Z height 20mm above the bed it will still slam right into the bed as if the Z offset has no change in the print height. But if i change the z Minimum to 0 then it says out of range but not until its heated up ready to go and 20 mill. above the bed why cant it see that is not going to work before it starts the print it

When leveling klipper will normally turn out numbers of 18 ish millimeters for all probed points on the bed weather delta calibrate or bed mesh either way and after removing the probe and adjusting z height normally to around 16mill. on the probed points with the nozzle but has to go into a Negative Z height to get close enough but the delta calibrate should be showing where 0 is so it should never be going to a negative z height for any reason after delta calibrate has been done the math just doesnt add up.

even though my printer is a delta i get a squared bed mesh and one that is absolutely horrible but when running a bed level on the stock printer board it does perfect never once hit the bed now after trying klipper it has completely destroyed the bed running the nozzle plum through it in the beginning I really like klipper but the bed mesh on a delta is a complete disaster but its using the same probe that the stock is and passes the probe_accuracy command every time. I dont get why i cant get a hexagon image or atleast something that is relativly close to the bed mesh, but works flawlessly on Marlin.

No Slicer has a klipper format, I looked everywhere to find a slicer for klipper but only found Superslicer and even that is sending out commands that are way outdated and klipper cant understand them. I had to chop up my start config so bad just to get cura to print on the same printer it had printed on for over a year

The new bed mesh load profile code that is in the new notifications doesnt show where to even put the code just says add to slicer or start g code but not sure where in the start g code it should be added i later found out that it needs to be added after the g28 code to actually load the mesh with out it being here klipper ignores the bed mesh completely.

after setting z height and saving it the nozzle just sits there while it rebooting it doesnt return to home or atleast raise up a little bit after doing a save_config command the printer will disengage the stepper motors allowing the nozzle to hit the bed then after it hits the bed i have to run a g28 code to home the printer but the old outdated mks robin nano v3 board running marlin was able to take a very accurate bed mesh of the printer, adjust the z offset and home the printer all by its self with a very minimal program just seems like klipper should be able to do 1 of the 3.

I’m not sure, what you want to achieve with this wall of text and to be honest, for me it sounds quite impudent.

So, without going into the details:

  • Klipper is an open source project and nobody is paying the folks that
    • are developing the code
    • writing documentation
    • providing support here
  • All above is done in the free / spare time of the respective people
  • Being open source, everybody can contribute to make it better (my apologies, should I have overlooked your contributions)
  • Slicers: There is no Klipper gcode format, it is fully compatible to Marlin
  • Round bed probing: Yes, could be improved but a lot of deltas use the current form with success. Feel free to do so
  • Bed mesh loading: You can load the mesh before or after G28. It does not matter

In my view:

  • Klipper offers a very comprehensive and up to date documentation, which is excellent compared to many other OSS projects
  • Converting a printer from OEM to Klipper takes some experience, reading the documentation and trial and error, searching the www for additional resources - no documentation will ever be able to cover each and every aspect for each and every printer out there

Stick to them OEM configuration if you do not feel comfortable with it. Otherwise folks here are willing to help, given you ask politely and patiently and not come across like you are paying for a multi thousand USD maintenance contract with Klipper

(post deleted by author)

This is 1 sentence. One. I feel your pain, and in fact I really want a klipper config for my SuperRacer, too. But please use punctuation so that your questions/comments can be parsed. Please.

2 Likes

@JCFPV you seem quite frustrated but still I cannot understand nor share your PoV here:

Updating the documentation:

See History for docs - Klipper3d/klipper · GitHub
The whole documentation is reviewed and update every few days.

Also currently in process are some documentation relevant Pull Requests, e.g. Config_Reference: Fixed 'screw_thread' explanation in 'screws_tilt_adjust' section. by bassamanator · Pull Request #6039 · Klipper3d/klipper · GitHub or https://github.com/Klipper3d/klipper/pull/5996 or https://github.com/Klipper3d/klipper/pull/6032

What the documentation will never offer

  • A step by step guide for each and every printer or printer-board. There are just too many combinations
  • A guide that is teaching you basic mechanical / electrical / Linux know how. There are enough available in the www
  • A guide that is teaching you basic or even advanced 3D printing know how. There are enough available in the www
  • A guide why exactly your printer is not behaving in a way that you would expect. Since you are deviating from your OEM configuration, this above mentioned knowledge on 3D printing / mechanical stuff / electrical stuff / Linux etc, is YOUR responsibility

What the documentation offers

  • General guidelines how to setup and configure your printer
  • An explanation of the different settings (IF applicable or needed for your given printer will again be YOUR responsibility
  • Basic troubleshooting / FAQ

What this place or the Klipper discord offers

  • Many experienced users who are willing to lend you a helping hand
  • A great resource of issues other people had, for you to learn from it. Again YOUR responsibility to dig into it. Or to put it the hard way: I could give a f%$%& if your printer is running under Klipper or not (mine do). Still I offer you my help and experience
  • A Knowledge Base where we collect additional information and helpful information

Final words

Statements like these (and others) in your OP are pissing me off big times:

  • Klipper is successfully running on countless printers including deltas.
  • Who gives you the right to demand this in a free of charge, open source product like Klipper?
  • A 30 seconds google search reveals a quite comprehensive guide how to install Klipper on a Flsun Super Racer Delta
  • Who tells me, that you have correctly understood or followed the information / instructions already provided in the documentation?

Having said this, I’m still willing to support you in getting Klipper running on your machine.

2 Likes

Jep, and I rejected these flags

See you again after a cool down of two weeks

3 Likes

GitHub - Guilouz/Klipper-Flsun-Super-Racer: Klipper pour FLSUN Super Racer (JSTECH Edition) Awesome Klipper configs here, and install instructions.