You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I want to set a specific temp for a vendor should I just match the slicers name for the filament with the dashboard config? The multiace UI has only 3 vendors so it cannot be done there
After hours of printing and swapping these settings and results for me have been flawless. No hold ups, no jams smooth unwinding and loadings on all 4 ACE units
I wanted to share a PETG tip-forming profile that has been working really well for me. I’m definitely no tip-forming master, but since PETG can be tricky with strings and blobs, I thought this might help someone else.
So far, I’ve had good results with Sunlu PETG Basic and Elegoo Rapid PETG
Hello, I've been working on Orca Slicer for this setup. Just wanted to post my settings in case anyone wanted to try. I also printed the tube guards that help ensure filament is loaded straight.
The AFC issue is resolved. The Ace now correctly reports a single loaded roll, and the feeder heads display their loaded states accurately. The UI reflects the proper mapping.
The system auto‑loads all colors for any Ace in any layout. Since the Ace always enumerates four slots when connected, unused slots simply appear as “not loaded.” That’s the intended default behavior.
All buttons are functioning. Any filament roll with RFID loads normally and tracks usage.
This implementation relies on the mapping generated by MultiACE. Do not modify that mapping. Leave it exactly as is.
Hello, I've been working on Orca Slicer for this setup. Just wanted to post my settings in case anyone wanted to try. I also printed the tube guards that help ensure filament is loaded straight.
Thanks, 195 for PLA, thats new, have to try it.. On the other materials, i have maybe 6 of them here :)
You are the guy with the Orca Slicer fork coming soon, right?
For PLA I have found that max should be set to 205. Anything higher created too large of a "blob" and causes quite a loud pop/bang when it starts to pull through the extruder.
Here is my current tip-forming routine for PLA. I think it's a good starting point but still a work in progress. The higher unload temp is b/c I am working on the background purges. To maximize time, it should be your print temperature.
The final 'deep dip' at 42 mm/ -42 mm may vary based on each extruder, still investigating this. You may need to tune this a millimeter or so for your setup. To deep and you will get a swollen tip, to shallow and you will get a deformed tip with stringing.
@decay71 Just a quick heads-up: while testing PR #186, I noticed that on the 1.30b-pre1 beta build, ace_tipform.py had introduced the prime:, primetemp:, and bgtemp: tokens.
Because our branch is branched off current main (the 1.27b baseline), ace.py doesn't have the pre-prime caller dispatch yet, which caused a jam on my end when using my 1.30-tuned tip-form string without that pre-purge move. I've adjusted my config back to standard 1.27 tokens and kept this PR strictly focused on ACE_BG_WAIT / arrival hold without touching ace.py or tip-forming logic.
Wanted to give you visibility so it's on your radar for the 1.30 release. Whenever you're ready, we can merge #186 in, or I can rebase/merge 1.30 changes into my branch if you'd like more testing first!
Thanks for the heads-up, that matches what the code does: on the 1.27b baseline ace_tipform's parser rejects prime:, primetemp: and bgtemp: as unrecognised tokens, the whole PLA table is dropped with a loud line at startup, and the pull runs the stock choreography at the DB temperature, without the pre-purge. So a tip-form string tuned on the beta needs the beta build; I will put a note in the 1.30 release notes. Nothing to change in #186.
Rebasing onto 1.30 is not possible, the dev tree is private and the beta branch is only a snapshot. Let's merge #186 into main. One request before that: the pick-notice fix is in main now (fix/bg-pick-notice, merged), and it touches the same spots as your branch, the prime loop and _check_docked in ace_bg_swap.py. Please merge main into your branch and resolve that, and while you are there call the new request_pick_abort(head) from ACE_BG_WAIT in the LD_GRIP/LD_PRIME phases instead of passing through, then wait for is_busy to clear like the T wrapper does. With that in, #186 is complete from my side and I merge it; the port to the 1.30 line happens on my end.
Activity
[-]Tip forming result and strings[/-][+]Tip forming results and strings[/+]decay71 commentedon Aug 2, 2026
Will try that!
JReacher2 commentedon Aug 5, 2026
Hi
If I want to set a specific temp for a vendor should I just match the slicers name for the filament with the dashboard config? The multiace UI has only 3 vendors so it cannot be done there
decay71 commentedon Aug 5, 2026
if you add a new vendor in tip forming, it should be selectable in dashboard afterwards..
DjFillament commentedon Aug 9, 2026
After hours of printing and swapping these settings and results for me have been flawless. No hold ups, no jams smooth unwinding and loadings on all 4 ACE units
BigMcRat commentedon Aug 18, 2026
I wanted to share a PETG tip-forming profile that has been working really well for me. I’m definitely no tip-forming master, but since PETG can be tricky with strings and blobs, I thought this might help someone else.
So far, I’ve had good results with Sunlu PETG Basic and Elegoo Rapid PETG
PETG: unloadtemp:235, 30@400, 0.7@1600, 0.7@2400, -27@2700, fan:255, waittemp:185, 2@600, -2@600, 28@2000, pause:100, -28@2000, waittemp:240, fan:0, -35@1500
Mnemonic3D commentedon Aug 20, 2026
Hello, I've been working on Orca Slicer for this setup. Just wanted to post my settings in case anyone wanted to try. I also printed the tube guards that help ensure filament is loaded straight.
DjFillament commentedon Aug 20, 2026
Dope.. close to mine but you have a lot more... thanks for the settings! And I downloaded those tube guards they work amazing
Mnemonic3D commentedon Aug 20, 2026
The AFC issue is resolved. The Ace now correctly reports a single loaded roll, and the feeder heads display their loaded states accurately. The UI reflects the proper mapping.
The system auto‑loads all colors for any Ace in any layout. Since the Ace always enumerates four slots when connected, unused slots simply appear as “not loaded.” That’s the intended default behavior.
All buttons are functioning. Any filament roll with RFID loads normally and tracks usage.
This implementation relies on the mapping generated by MultiACE. Do not modify that mapping. Leave it exactly as is.
Updated mapping and names:
DjFillament commentedon Aug 21, 2026
Dope. Was giving me a headache thx dm me ya. I dm you but nothing lol
decay71 commentedon Aug 21, 2026
Thanks, 195 for PLA, thats new, have to try it.. On the other materials, i have maybe 6 of them here :)
You are the guy with the Orca Slicer fork coming soon, right?
deboni1 commentedon Aug 23, 2026
For PLA I have found that max should be set to 205. Anything higher created too large of a "blob" and causes quite a loud pop/bang when it starts to pull through the extruder.
0005323 commentedon Oct 6, 2026
https://makerworld.com.cn/models/3028581
I think my model is helpful about this.
docx-tech commentedon Oct 14, 2026
Here is my current tip-forming routine for PLA. I think it's a good starting point but still a work in progress. The higher unload temp is b/c I am working on the background purges. To maximize time, it should be your print temperature.
The final 'deep dip' at 42 mm/ -42 mm may vary based on each extruder, still investigating this. You may need to tune this a millimeter or so for your setup. To deep and you will get a swollen tip, to shallow and you will get a deformed tip with stringing.
unloadtemp:210, loadtemp:240, 20@600, -15@1800, -22@2400, -6.2@1200, -3.2@720, 20@1200, -20@940, 42@1740, -42@2400, 20@680, -20@420, -21.1@2700
docx-tech commentedon Oct 25, 2026
@decay71 Just a quick heads-up: while testing PR #186, I noticed that on the
1.30b-pre1beta build,ace_tipform.pyhad introduced theprime:,primetemp:, andbgtemp:tokens.Because our branch is branched off current
main(the 1.27b baseline),ace.pydoesn't have thepre-primecaller dispatch yet, which caused a jam on my end when using my 1.30-tuned tip-form string without that pre-purge move. I've adjusted my config back to standard 1.27 tokens and kept this PR strictly focused onACE_BG_WAIT/ arrival hold without touchingace.pyor tip-forming logic.Wanted to give you visibility so it's on your radar for the 1.30 release. Whenever you're ready, we can merge #186 in, or I can rebase/merge 1.30 changes into my branch if you'd like more testing first!
decay71 commentedon Oct 25, 2026
Thanks for the heads-up, that matches what the code does: on the 1.27b baseline ace_tipform's parser rejects prime:, primetemp: and bgtemp: as unrecognised tokens, the whole PLA table is dropped with a loud line at startup, and the pull runs the stock choreography at the DB temperature, without the pre-purge. So a tip-form string tuned on the beta needs the beta build; I will put a note in the 1.30 release notes. Nothing to change in #186.
Rebasing onto 1.30 is not possible, the dev tree is private and the beta branch is only a snapshot. Let's merge #186 into main. One request before that: the pick-notice fix is in main now (fix/bg-pick-notice, merged), and it touches the same spots as your branch, the prime loop and _check_docked in ace_bg_swap.py. Please merge main into your branch and resolve that, and while you are there call the new request_pick_abort(head) from ACE_BG_WAIT in the LD_GRIP/LD_PRIME phases instead of passing through, then wait for is_busy to clear like the T wrapper does. With that in, #186 is complete from my side and I merge it; the port to the 1.30 line happens on my end.