Directly? Indirectly? How, if at all?
They have to update it first, but if they do it should work with printer in developer mode or by sending the g-code though Bambu Connect app.
People are calling for H2D support in Orca: Add slicing support for Bambu Lab H2D ¡ Issue #9254 ¡ SoftFever/OrcaSlicer ¡ GitHub
Several companies contributed profiles to orca, would Bambu do the same, or would people have volunteer and contribute their own time to do the profiles?
Based on text on official website
It should be possible to directly communicate with h2d from orca in developer modeâŚ
If Bambu canât get Orca to support H2D, for whatever reason, then itâs incumbent on Bambu to improve its slicer to be just as good. Or at minimum at least as good as Orca was before the rift happened. Right now, especially with respect to H2D calibration, Bambu slicer is just nowhere as complete as Orca slicer. Donât agree? Please prove me wrong. I would be very happy if you did.
So why am I wasting my breath with this post? Honestly, I donât know. Maybe Iâve overlooked something, and hopefully somebody has suggestions? I thought I could maybe get what I needed a la cart from makerworld, but some of those models rely on orca slicer and arenât supported by bambu slicer. For instance:
explicitly calls for using orca slicer. As a check on that, I tried printing it using Bambu slicer instead, and it totally does not work if sliced in Bambu slicer: each of the test coupons prints identically. Useless.
Regardless, weâre all in the same boat. I guess you either get your work done using just the default print profiles, or⌠what, exactly? Just what exactly is it that people are doing, in detail, to manage their way through the hole left by orca slicer? Especially the calibrations. Letâs not all re-invent the wheel separately if some smart person has already blazed a trail by finding all the best-in-class substitutes. What are they? For example, Iâm truly looking forward to using the vision calibration sheet to increase accuracy, but itâs counterproductive if the print profiles arenât sufficiently well dialed in so that the added accuracy can make a difference. Right? Anyone disagree?
Anyone? Anyone? Bueller? Anyone?
The requirement is only for the per-object settings. You can export to stl and drop it into BambuConnect, no? An extra manual step for sure, but I donât think SoftFever is going to budge on the vendetta, and integrate the PR to open the BC url with the file.
Sorry, but I donât understand what you mean. Would you please elucidate?
No it doesnât work this way. Only orca has per-object flow settings. There are further problems: thereâs no H2D profile in orca so itâs currently not possible to just slice the thing in orca and send it via Useless Piece of Friction that some marketing âgeniusâ called âBambu Connectâ.
So you cannot slice the calibration in orca and send it through connect, exporting stl from 3m file wonât do anything.
Thatâs not a vendetta. The PR to âintegrateâ connect was correctly deemed useless from multiple standpoints - it brings no value to the user, brings no value to orca, gives no real security, removes features people use⌠Integrating that is counter-productive as long as âdeveloper modeâ will allow normal connection and full functionality without a need for âthe cloudâ.
Itâs in ref to @NeverDie 's example of custom calibration models. I went on a lark and assumed one who uses Orca can understand how to create an interm H2D profile by copying settings from BambuSlicer, it will still work as itâs a single filament project. Multiple nozzles may still be an issue, but thatâll be up to the next pull. Weâll have to wait and see on that.
Drag-drop the exported file onto BambuConnect
Either itâs lack of sleep or my skull is unusually thick, but I still donât get it. Help me find the disconnect. I am running Orca 2.3.0, which is the current stable release:
There is no H2D printer shown in the list of supported printers in Orca 2.3.0:
Right? Ergo, if youâre exporting a G-code file, which printer are you using as the basis for generating that g-code?
Are you saying to somehow copy the guts of Bambuâs latest slicer, or a subset thereof, and somehow massage that into a sythetic H2D printer in Orca slicer? i.e. what youâre calling an âinterm H2D profileâ? I suppose that would be interesting, but Iâve never read anywhere about anyone doing that before. But if itâs so easy to do, why isnât it already a part of the 2.3.0 build? At least to me, it sounds sketchy on its face. From my perspective, this has ârabbit holeâ written all over it. But what do I know? Evidently not enough, or I wouldnât be posting here and waiting on the kindness of strangers for a non-BS answer.
Is anyone else here doing this? Am I the only one who has never heard of this before?
Jump to Customizing a Preloaded and DIY 3D Printer Profile
I used to do it in the old Ender 3 days. Youâd probably want to pick the X1C as a starting point and go from there copying over sizes, gcode start/end and speeds/acceleration. It can be a rabbit hole alright Iâm not entirely sure the work is worth the effort since itâs very likely itâll appear in a month or two after general availability. But if you really need it now, you can at least copy the 0.4 Standard profile and get running.
I bought this printer precisely so I wouldnât have to do that kind of stuff. Seriously. For a printer that costs more than $2k? That kind of work is Bambooâs job, not mine. If Iâm doing it instead, I have to ask myself WTF I bought it for. Iâm not going to become an unpaid employee of a black box.
This is exactly what I donât want to be doing.
Sorry for the rant. If you have the time, skills, and motivation to do it, more power to you. The ROI just isnât there for me.
They did the work⌠itâs in BambuStudio. Orcaslicer is definitely not under their control. For that, youâd have to be patient for another user to go through the trouble of making those profiles, either officially or unofficially - or do it yourself (which youâre not precluded from doing).
Reminder, youâre the one who asked:
Using H2D for a week now - feels like iâve gone back in time using BambuStudio. Even something as trivial as shrinkage for Z is missing (thereâs a global xyz shrinkage parameter in BS Only).
One of the devs of Orca noticed that bambu network plugin causes issues for developers, meaning itâll be harder for devs to improve either BambuStudio or work on Orca with bambu printers: Please remove anti-debugging code in BBL network plugin ¡ Issue #6726 ¡ bambulab/BambuStudio ¡ GitHub
Core Configuration
Printer Settings
Parameter | Value | Source |
---|---|---|
Printer Type | CoreXY | H2D specs |
Build Volume | 325Ă320Ă325 mm (Single Nozzle) | Official specs |
300Ă320Ă325 mm (Dual Nozzle) | ||
Nozzle Diameter | 0.4 mm (default) | |
Max Temperatures | Nozzle: 350°C, Bed: 120°C | Technical specs |
Max Speeds | 1000 mm/s (travel) | H2D documentation |
Max Acceleration | 20,000 mm/s² | |
Filament Diameter | 1.75 mm |
text
; Example machine start G-code (adapt from Bambu Studio exports)
M140 S{bed_temp} ; Set bed temp
M104 S{nozzle_temp} ; Set nozzle temp
G28 ; Home all axes
G1 Z10 F3000 ; Lift nozzle
Advanced Parameters
Critical Settings for H2D Compatibility:
- G-code Flavor: Marlin (compatible with Bambu firmware)
- Retraction: 0.8-1.2 mm @ 40 mm/s (direct drive configuration)
- Pressure Advance: 0.02-0.04 (requires calibration)
- Cooling: 30-100% fan speed (adjust for chamber heating)
Dual Nozzle Configuration:
text
[multi_material]
toolchange_gcode = T{next_extruder}
purge_volume = 35 ; For 0.4mm nozzle
Filament Presets
Material | Nozzle Temp | Bed Temp | Max Flow Rate |
---|---|---|---|
PLA | 210-220°C | 60°C | 40 mm³/s |
PETG | 230-250°C | 80°C | 35 mm³/s |
ABS | 250-270°C | 100°C | 30 mm³/s |
Workflow Integration
- File Handling:
- Export sliced files as .gcode
- Transfer via SD card or use H2Dâs developer mode for network transfer
- AMS Compatibility:
text
M620 P{filament_id} ; AMS filament selection
M621 S1 ; Enable filament cutting
Calibration Tools
Use OrcaSlicerâs built-in calibration suite with these H2D-specific adjustments:
- Flow Ratio: Start with 0.98 for PLA
- Max Volumetric Speed: 40 mmÂł/s (standard hotend)
- Temperature Tower: 190-230°C in 5°C increments
Limitations and Workarounds
- Multi-material Printing: Requires manual G-code editing for tool changes
- Input Shaping: Currently requires manual frequency input (X: 48Hz, Y: 52Hz)
- Camera Integration: Not yet supported through OrcaSlicer
Community-Tested Profile Template
text
; H2D_OrcaProfile.ini
[printer]
model = Bambu_Lab_H2D
technology = FFF
bed_shape = 0x0,325x0,325x320,0x320
max_z_velocity = 30
max_z_acceleration = 1000
Next Steps
- Save this configuration as Bambu Lab H2D.ini in:
- Windows: %APPDATA%\OrcaSlicer\printer
- Mac: ~/Library/Application Support/OrcaSlicer/printer
- Test with benchmark models like XYZ calibration cube
- Adjust thermal parameters based on chamber temperature readings
While this profile enables basic functionality, full integration of H2D-specific features like active chamber heating control and automatic calibration will require official support from OrcaSlicer developers. The Bambu Lab community is actively petitioning for native integration, with several GitHub issues tracking progress
This profile should handle most single-material prints effectively. For dual-nozzle operations, consider using Bambu Studio for slicing until OrcaSlicer adds official multi-tool support. Community members report successful operation in developer mode using these settings
I would provide the source I found this but this forum wonât allow. Canât use screenshots as I canât use media. Yet you can look at otherâs and they are using media and or links. Thus maybe I need to become a " super member". Here is some details i found that may be useful. Hopefully Orca Slicer can just get this done and integrate H2D. Bambu studio has been difficult to say the least to get to work properly.
Excellent summary [user_670373523]
Thank you.
I will assume this is not a question of IF, but WHEN.
So I wonder, any news on WHEN Orca slicer will support H2D natively?
Thanks!
Orca announced a while back that they will not. After Bambu announced that they will lol
Not quite. Orca announced they wont support useless so-called authorization, but they havenât excluded h2d - only thing needed is someone to contribute profile(s) and (if necessary) code.
They have to update it first, but if they do it should work with printer in developer mode or by sending the g-code though Bambu Connect app.