H2C Right Nozzle Printing in Air only on Bambu Handy App

Got an issue.

I am trying to print a model with the AMS 2 Pro using bambu matte filament and on the right vortex nozzle.

If I print from the Bambu Studio app everything will print fine. If I use the Bambu handy app (on my phone), what happens is that it bed-levels the left nozzle, then switches to the right nozzle for the vibration test, and then prints the calibration line correctly, but when it actually starts to print the object, it just prints in the air a couple of inches above the bed plate.

Things I have tried.

Deleted the Bambu Handy App, deleted the cache
Ran the Nozzle offset calibration
Ran the same model from Bambu Studio and it will print correctly, then try to do it on the Handy app right after and it fails cause its printing in the air.
Tried printing from my iPad, which is using Handy App 3.27.1 and prints correctly

My phone app is version 4.0.4

Is this happening on all models, or just one in particular?

It almost sounds like the cloud sliced file is containing some wrong code for the printer.

Two different models, I have not tested more then that.

I should also add that if I print from older version like my iPad it works correctly

Link the model your trying to use your phone to print, it might have some issues

Hows it look when you send or preview it from your slicer?

It looks fine, it will print fine on Desktop App, print fine on older version of handy, will print in air on my iphone with latest version

I dunno. Looks fine in bambuslicer and orcaslicer. I dont use phone apps so idk.

I’m experiencing exactly the same issue with my H2C.

I’ve seen it happen with both PLA Matte Nardo Grey and PLA Matte Marine Blue. The calibration/prime line prints perfectly on the build plate, but when the actual model starts printing, the nozzle is suddenly around 1 cm above the plate and starts printing in mid-air.

It doesn’t happen every time. I’d estimate it happens in roughly 40% of prints that I start through Bambu Handy 4.0.4.

I currently have three PLA Matte colors and one regular PLA Basic loaded. I’m not sure yet whether the successful prints are the ones that use regular PLA Basic at all, or specifically the ones where PLA Basic is used for the first layer. That might explain why some prints work while others don’t.

So in my case the issue is intermittent, but definitely reproducible when starting prints through Handy 4.0.4.

If you haven’t put a ticket in, they are going to ask for a video of it, also the handy log. I also gave them the printer log as well.

I am sorry you are having the same issue, but I am also thankful that I am not the only one, and hopefully they will fix the bug.

I updated the app today, and my issue went away

The new Handy build no longer inherits the Studio filament-to-nozzle map. If a color is not assigned to a head, Handy still sends the job, but the tool change never gets the 5 mm bed compensation, so the right nozzle starts high and spaghetti’s.

Once each color is pinned to left or right (and the matching Vortek hotend on the rack), the switch is correct and it prints on the plate.

Older Handy did that assignment for you from the sliced file. The new one wants it set in the app before you hit print. Studio still does not need that extra step.

So on the page you select the color, right above that, you select the Vortek head you want for that color. By default all colors are now showing the same head and it will Spaghetti because the bed doesn’t move up by 5mm by default.

I hope this helps

Hi everyone, I’m still experiencing this issue with my H2C using the latest Bambu Handy version available to me.

Prints started from Handy begin printing in mid-air immediately, while printing from Bambu Studio on my Windows PC works normally. Calibration has already been checked.

Thanks, Froggy2, for the information about filament-to-hotend mapping. Could you share a screenshot showing exactly where to assign each filament to the correct nozzle/Vortek hotend in Handy? I haven’t tested this workaround yet.

Has Bambu confirmed this issue, and is there a permanent fix?

Also having this same exact issue.