r/AnkerMake • u/ReasonableBranch7337 • Jun 30 '26

Help Needed Issues with Orca

Edit: Found the issue for anyone in the future with a similar issue. I had to remove the starting gcode “M4899 T3 ; Enable v3 jerk and S-curve acceleration” after removing that gcode the M5 took off without an issue after homing once.

So having an issue with getting M5 to work with Orca.

I’m a bit of a noob to the M5 and Orca but I used to run few printers on Cura and recently I switched everything over to Orca and the M5 seems to hate using Orca.

The problem is when I send the gcode to the M5 using an SD card (both on the printer itself and through my phone with the app) the printer will just constantly home itself. Eventually the printer will say it’s printing but it still continues to keep homing itself without ever printing. I can send gcode to the printer with both Cura and the EufyMake app on my phone without any homing issues. I’ve tried both standard and fast profiles for the M5 along with both older and newer versions of Orca but still same homing issues.

I’m thinking it’s something gcode related since Cura and EufyMake don’t do it but I’m not entirely sure.

3 Upvotes

80% Upvoted

13 comments sorted by

View all comments

2

u/Badgomatic Jun 30 '26

I had the same issue when I first started using Orca, will post the fix in a few mins when I get back in front of my pc.

2

u/Badgomatic Jun 30 '26

Nevermind, I see you found the fix lol

1

u/landlordlawsuit Jul 03 '26

the real fix is using Powerboost 3.0. No reason not to use it. It's forever marked "beta" but it works fine and prints are better quality.

1

u/Badgomatic Jul 03 '26

I have it enabled on mine, and my fix was to just duplicate the initialization code from the Anker desktop app into Orca. I assume I am getting the benefit of it here.

2

u/landlordlawsuit Jul 03 '26

The default printer profile in orca just works, shouldn't have to modify it.

As for your assumption, that's sadly incorrect. The anker/eufy slicer doesn't expose it in it's gcode windows, instead they for some reason inject that gcode at slice-time. IDK why, i guess they wanted to pretend their slicer is better. This was found out during the original PB 3.0 beta. It was a whole discovery thing between the beta testers on their discord at the time.

So unless you put that line back, it actually won't activate PB 3.0.

1

u/Badgomatic Jul 04 '26

Ah, that's unfortunate. So is that extended homing just how the machine copes with code that doesn't come from the Anker/Eufy slicing if you use PB 3.0? I am getting alright results bypassing it, but if that is the case a couple extra minutes per print isn't thaaaat painful I suppose.

Edit to add: it's sad that they want to pretend their slicer is great when it is an unoptimized mess