ADM5 Klipper Mod v00.03-beta

[xblax]

I guess it's time to finally announce that this mod has reached "beta" status and the repository is opened to the public 🎉

Welcome to all that are new to this project!

And thank you to all that have already contributed to this project during the last weeks! It took a fair amount of work to get to this point but it was also a lot of fun! Special thank is due to @consp who has tremendously helped with the development, testing and cool features that are now part of this mod.

There is not much to say about the features of this Release, since all the information is in the Readme, other documentation, discussions and open issues.

Everyone is welcome to contribute to this open source project and join the discussions here on GitHub!

[johncotten]

So far so good! Installed and did an initial print. Thank you all for making this happen!

[DomanRulez]

It's possible to print directly from Orca Slicer using this connection setting?

[the-redone]

This is basic stuff and all explained already by OP and pretty much basic knowledge, don't think this is for you if you're asking these basic questions

https://github.com/xblax/flashforge_adm5_klipper_mod/blob/master/docs/SLICING.md

[xblax]

This is basic stuff and all explained already by OP and pretty much basic knowledge, don't think this is for you if you're asking these basic questions

I don't mind if some easy questions are asked, maybe not everything is immediately obvious to newcomers.
But the Github Discussions have a Q&A section where these kind of questions would fit best.

[consp]

To answer the original question:

Octo/klipper would be correct, as moonraker has octo-compatibility. your-printer-ip:7125 would be the hostname/ip/url as stated in SLICING.md.

Do note the possible problems with the default orcaslicer settings from flashforge in the docs.

[the-redone]

TBH coming from groups on facebook etc it's got to the point where people need to be spoon fed, maybe I'm a bit abrupt but sick of seeing people ask questions that have answers in front of them and relying on others to show them. Ends up in a free for all and answering the same questions over and over, will avoid q&a if that's how it's going to go, appreciate all the work you've done and all collaborators too

[DougJoseph]

Thank you so much! Will be trying this out ASAP today!

[xblax]

Wrote a short post on Reddit to announce the start of public beta for this mod.
https://new.reddit.com/r/FlashForge/comments/1bcvwpj/custom_klipper_mod_for_flashforge_adventurer_5m/

[DougJoseph]

Thank you SO much for making this for all of us in this community!

I would really like try the KlipperScreen approach, but I don't yet know how to install that variant. I could not locate a prebuilt file for that variant. I downloaded the source code as a Zip file, and opened the folder in VSCode, but I don't how to build it.

Please bear in mind I'm brand new to Klipper. I would sure appreciate any kind advice.

Thank you again for being so awesome!

[KaruroChori]

https://github.com/xblax/flashforge_adm5_klipper_mod/releases/tag/v00.03-beta
Third file in there

[DougJoseph]

Wow, thanks. Don't know how I missed it!

[consp]

VSCode, but I don't how to build it

I doubt that will work, you definitly need a cross compilation environment which probable means linux is a requirement (or wsl). Building is a bit of a stretch at the moment due to buildroot. Ease of build (plus good docs) is an improvement yet to happen.

[DougJoseph]

Re. "I doubt that will work" — I definitely don't want to build myself in VS Code. I just had somehow overlooked the already built file that's provided! @KaruroChori was kind enough to point it out for me. I now have it installed and working! Thanks!

[DougJoseph]

I got both the normal variant and the Klipperscreen variant working! Thank you!

The only struggle I've had so far is that I could not get connected to wifi even after trying all the options shown in the wifi docs page, with the exception of the final option by use of Klipperscreen. On the klipper_mod method, I'm pretty sure I did it right, but it would not connect (i.e. after reboot). On the SSH method, the commands seemed to work fine, but after reboot no wifi.

Thanks again for making this!

[consp]

but after reboot no wifi.

I've had this once but could find no a reason for it. Might be worth a look into.

[DougJoseph]

Hello again! I'm not a novice at either code or 3D printing, however, I am a novice regarding Klipper, and barely know enough about GCode to be dangerous. I am trying to alter the Flashforge AD5M print profile in OrcaSlicer to be suitable for this Klipper mod. I have read and reread this portion in the docs, but don't understand what to do on the last part:

• GCODE output style should be klipper
• Do not use the default FlashForge OrcaSlicer settings, they do not contain proper start/end sequences.
• Edit the printer profile to use the START_PRINT and END_PRINT as described in macros.cfg as start/end macros.
Example:
START_PRINT BED_TEMP={first_layer_bed_temperature[0]} EXTRUDER_TEMP={first_layer_temperature[0]}
Variables may differ depending on the slicer used.

I am basing this on Flashforge's profile provided for printing the DIY enclosure.

For the first portion, the profile seems to already specify "Klipper" as the GCode Flavor:

For the last portion, am I supposed to remove all the GCodes and etc that are in the Start and End...

...and replace as shown like this?

If not, then would someone be kind enough to explain if incorrect, and/or what else is needed?

Thank you so much!

[DougJoseph]

You have to figure it out on your own what variables you exactly need to use. You can probably get them from the original code, but the original start gcode does a M104 which won't wait for the extruder to heat up and will stop before the print starts.

Yes that START_PRINT works fine with Orca slicer.

Well, I tried a test print with that "example" code, and something is not right. It tried to heat the nozzle to 255 instead of 220, and it started pressing the nozzle down into the bed really hard. Ugh.

[xblax]

Can you provide G-Code that you sliced? Or you can just open it in an Editor and see if the START_PRINT looks as it should. But it would be great if you open a thread in the Q&A section about slicer configuration help.

There that discussion is better suited than here in the release announcement thread.

[Tiwatz]

This is mine, tested multiple prints today. Probably something else that is wrong for you.

[DougJoseph]

OK, seeking to move this over to Q&A here: #57

[DougJoseph]

Over on the other thread, I managed to solve the "params" issue. Circling back for convenience of readers here.

#57 (comment)

[babyshampoo112]

i downloaded the klipper screen version, its very good but I connected it to the wifi and whenever i try accessing moonraker or fluidd it says site cant be reached

[consp]

Are you sure you are connecting to the correct IP? This sounds more like a network issue to me. There are some issues with klipperscreen not reporting the correct wifi ip though, i.e. see #39

[DougJoseph]

I can confirm that connecting via Moonraker and Fluidd does work once the printer has actually connected to Wifi. My printer did not connect via wifi until I used the Klipperscreen interface on the LCD to input the Wifi login details. All the previous options in the list of how to connect, did not work for me for whatever reason. But once I got connected, the remote interfaces worked.

[webbbn]

I've been holding off installing this until I confirmed that my Voron was back up an running after some upgrades, and I just installed the 00.04 release. So far it's working great!

I also hoped to make sure that Flashforge knows that I only bought this printer because this printer ran klipper, I saw their (maybe halfhearted?) release of the klipper firmware, and saw this repo.

Just finished my first test print after upgrading, and it looks perfect. Great work!

[consp]

maybe halfhearted

Look mode like malicious compliance.
It's also not possible to build klipper since the analogue parts of the chip won't work. It's therefore impossible to use the repo to build a klipper version for the MCU. It's likely they made changes and did not include them.

But at least it's modable. Really hope someone can get the NS chip SDK somewhere and build for it, would enable everyone to build newer klipper versions.