Can the Nozzle Identification step be disabled in GCODE?

Cash grab? E3D is older than Bambu Lab and are quite respectable contributors in FDM industry.

it doesn’t cost to create synth diamond coating that money they ask , also for THAT price it should work flawlessly with any bambu in any setup .

Sorry, but you have no idea what you’re talking about

Get a clue dude.

The E3D Diamondback doesn’t have a diamond coating, it has a solid tip machined out of a custom-grown PCD diamond.

Next time learn the whole story before running your mouth, all the E3D nozzles were working perfectly and then Bambu pushes a firmware update that caused this issue. E3D is making it right with all their customers and sending stickers that allow the hotends to be read properly again.

whatever , i dont really care how its coated . its not working as intended , piece of crap . printer loses nozzle info every second print . despite deep knowledge in coating or whatever its not working as it should fore insane price. you argue all you want and defend expensive piece of crap - it wont make it work and waste time.

Any luck on pressuring Bambu? This makes using the Diamondback borderline insufferable. As you might imagine, those of us committed to Diamondbacks for their quality and abrasive handling also invest quite a bit in calibrations — which we can’t run cleanly from Bambu Studio as even a custom g-Code machine preset won’t apply to flow dynamics, flow rate, or z-offset calibrations. This means having to manually calibrate every single filament, going through the yo-yo of the H2D start sequence, having to ‘ignore’ the unrecognized nozzle, then going back to the printer each and every time to set it again (I’ve just leaned on letting it be read as the Standard Tungsten Carbide to differentiate).

The problem, however, is that the filament presets — especially temperature and flow —settings for the Diamondback (left nozzle) are invariably different from the standard hardened nozzle, and there’s no way to split that except for creating literal copies of every single filament.

If they don’t care to support it, whatever. All we need is the ability to disable the obnoxiousness of the auto-read and override that it triggers.

@Bambu_support do you care at all?