So after the upgrade, the camera doesn’t properly identify the E3D ObXidian high flow nozzles, and apparently I am not the only one. I have to jump through hoops to keep telling the printer that it’s a High Flow Hardened 0.4mm - then it loses it’s mind every time I start a new print.
Is there a way for me to just set the nozzle type, etc., on the printer menu and force it to skip that nozzle ID step for every @#%$^ print?!
Looks like I might need to downgrade the firmware if that’s even possible.
Any ideas would be welcomed - I opened a ticket with support but don’t expect much.
In the H2D machine’s start G-code there’s this block around line 162:
M1002 gcode_claim_action : 72 ; Hotend Type Detection
T1001
M972 S14 P0 T5000 ; nozzle type detection
The first line just displays a message about hotend detection. The next 2, I think do the actual check. You could try commenting those out (put a ; in front of them) and see what happens… what could go wrong, right?
Mind you this is a guess, proceed at your own risk. I have not tried this. Google search bot agrees, FWIW (it’s not terrible at parsing g-code actually, but… it also makes stuff up sometimes).
Thanks! I’ll investigate this. It’s getting downright maddening because sometimes it detects it correctly, then other times it gets a total brain fart - which tells me it’s something in their OCR code that does the nozzle recognition. Works fine on BLACK labeled Bambu nozzles. Seems to suck mostly at the purple color that E3D uses. I find this amusing since all the docs from E3D say they work very closely with Bambu to insure compatibility.
If I shine a flashlight directly on the nozzles when it does the read, that seems to help it scan correctly more often. Maybe putting a string of LED lights in the D3P riser might help it along.
But thanks. Gonna play with g-code to see if I can make it hands-off.
Tried it - created a custom profile for my H2D and edited out that section of g-code. Went to the printer and assigned both nozzles High Flow, Hardened Steel, 0.4mm - then opened a project in Bambu Studio, sync’d the printer, sliced the plate, sent it, and it didn’t do the nozzle check. I guess up and until I reboot the printer, successive prints should be fine.
I also figured they modified the wait time or something to do with the identification, as when I shine a flaslight right on the head when it comes up to the camera, it tends to actually work. I will have to investigate that g-code further and seeing if I can change the timeout or do something for it look “longer” maybe? I dunno - but editing the g-code definitely worked. Thanks!
That printer (“machine”) start g-code gets included with every print, not at printer startup. I just realized, as I was responding here, that it could be interpreted that way… wow, sure could be labeled clearer now that I think about it! It really means “starting g-code for prints on this machine” or something like that.
So I’d assume you’d need to use that same printer config any time you want to use those nozzles/skip detection. Having those nozzles on a separate profile may have other benefits as well… or just be annoying to maintain.
The whole bit with needing to read a tiny code at the top of a mounted nozzle which is routinely handled, abused, etc, seems like a weak link to me. The code could rub off, get covered up, etc, assuming it was printed clearly in the first place. I was surprised it seemed a bit “low tech” compared to some of the other printer bits (I’m old enough that calling anything like that “low tech” is very amusing, hence the quotes). Though I guess it’s not really essential. The induction nozzles on H2C are much smarter (since they have wireless comms already), which is good because the printed codes are unreadable on half of mine. OTOH they’re much more expensive, so… yeah.
Anyway, seems like adding a “skip nozzle detection” printer option could be a useful feature and not really hard to add. Even if it’s just in Studio at first.
Yep. I created the custom printer config and just have to be sure to select it every time I go and slice a print because if I don’t? The printer will bark at me when it can’t read the heads. I have E3D in the name to remind me which one. Thanks again for the idea!
Well they finally added “Dry While Printing“ to all the AMS 2/HT units so who knows - perhaps anything is possible at this point? lol I would think E3D might add a little pressure since it might wind up affecting their business maybe at some point.
I am facing the exact same issue with my E3D Nozzles making them pretty useless. Editing gcode every time seems a bit much. Seems like there should be a firmware fix.
If you edit the “start gcode” as the solution suggest you only have to do it once as this section of gcode is applied whenever you slice using that machine setting.
That is not a solution, but a workaround for the problem. So marking the post as solution is a bit wrong, IMO. Especially, considering that E3D are “Officially approved & licensed Bambu Lab product.“
Do you happen to know if this issue was reported to them? If not, would you mind to point me if they accept bug reports through GitHub or just standard support channels?
The solution is literally what was requested in the title of this post. Just sayn’. And Ryan provided most of it by actually trying my crazy suggestion.
Another thought would be to ask E3D why their “officially licensed” nozzles aren’t being recognized. Maybe they could print a dark dot behind the code or something, if the color is the issue.
No worries… I spent minutes the other day trying to figure out where my previous post on a thread had gone off to, only to finally realize that had been on another thread (on the same topic).
Also I realized now by “them” you meant E3D, not BL. I think. Sorry!
Hmm, well, hopefully they respond with something useful. Maybe high-temp vinyl dark background stickers with the codes? (IDK if that’s even the issue ofc.) If it’s something they really tested and it had worked and then BL broke that in some update… then yea BL should probably fix it.
The whole thing with disabling the check in the first place is already a workaround, really, not even a very good one (even if it was an easy-to-use option on the printer). Which is likely what you meant already.
I did open a ticket through BL’s support channel in the Handy app, but they are still “Investigating”. They definitely changed the algorithm to read the heads on the H2D. When I shine a flashlight right on the nozzles most times it reads it fine. But disabling the check on each print with the g-code works just as well for now.
I also find that if you shine a fairly bright flashlight right on the nozzle when it reads, it picks it up most of the time. So yeah, they def changed something with the ID code that runs.
