Skip to content

Wiki Update 12 - Others#10452

Merged
SoftFever merged 18 commits into
OrcaSlicer:mainfrom
ianalexis:Wiki-12
Sep 9, 2025
Merged

Wiki Update 12 - Others#10452
SoftFever merged 18 commits into
OrcaSlicer:mainfrom
ianalexis:Wiki-12

Conversation

@ianalexis

@ianalexis ianalexis commented Aug 18, 2025

Copy link
Copy Markdown
Collaborator

This wiki update will focus in others descriptions.

  • Updates
    • Tab.cpp material PA wiki link
    • PA Wiki improvement
      • Reorder
      • Specific save section
    • Add Google safe browsing report link in Readme
    • Improved home icons and desc
  • Others
    • others_settings_skirt
    • others_settings_brim
    • others_settings_g_code_output
    • others_settings_notes
    • others_settings_post_processing_scripts
    • others_settings_special_mode
    • others_settings_fuzzy_skin
    • Placeholdes Variables
      • Basic descriptions
  • Fix

This time I was a little lazier than usual, but I wanted to finish it once and for all.


Wiki TODOs:

This was referenced Aug 18, 2025
@Fisheye3D

Copy link
Copy Markdown

Hi @ianalexis, thanks for offering to include this!

My proposal is to update the Wiki examples for M106/M107 so that fans can be mapped by both index and name. This way users can still use M106 P0, M106 P1, etc., but also reference the fan by the name they assign in their config (e.g., CPAP, EXHAUST).

Example implementation:

[fan_generic CPAP] #fan 0 orcaslicer
pin: PB7
max_power: 0.8
shutdown_speed:0
kick_start_time: 0.100
cycle_time: 0.005
hardware_pwm: False
off_below: 0.10

[fan_generic EXHAUST] #fan 3 Orcaslicer
pin:PE5
#max_power:
#shutdown_speed:
cycle_time:0.01
hardware_pwm:false
#kick_start_time:
off_below:.2

[gcode_macro M106]
description: "Set fan speed (Orca compatible)"
gcode:
{% set fan_map = {
0: "CPAP", # Orca P0 → CPAP blower
3: "EXHAUST", # Orca P3 → Exhaust
} %}
{% set p = params.P|int if 'P' in params else 0 %}
{% set fan = fan_map[p] if p in fan_map else "CPAP" %}
{% set speed = (params.S|float / 255 if 'S' in params else 1.0) %}
SET_FAN_SPEED FAN={fan} SPEED={speed}

[gcode_macro M107]
description: "Turn off fans. No P = all, P# = specific"
gcode:
{% set fan_map = {
0: "CPAP", # CPAP blower
3: "EXHAUST", # Exhaust (or remap as needed)
} %}
{% if 'P' in params %}
{% set p = params.P|int %}
{% if p in fan_map %}
SET_FAN_SPEED FAN={fan_map[p]} SPEED=0
{% else %}
RESPOND PREFIX="warn" MSG="Unknown fan index P{p}"
{% endif %}
{% else %}
# No P → turn off all mapped fans
{% for f in fan_map.values() %}
SET_FAN_SPEED FAN={f} SPEED=0
{% endfor %}
{% endif %}

This allows more user-friendly naming while keeping backwards compatibility with M106 P# commands.
Hopefully this is what your requesting.

@ianalexis

Copy link
Copy Markdown
Collaborator Author

Hopefully this is what your requesting.

I made some changes and sent them to you via Discord to see if you agree before uploading them.

@ianalexis ianalexis force-pushed the Wiki-12 branch 4 times, most recently from 0f62c9b to 066de6c Compare August 22, 2025 20:03
@ianalexis

Copy link
Copy Markdown
Collaborator Author

thanks for offering to include this!

Moved to #10369

@ianalexis ianalexis force-pushed the Wiki-12 branch 4 times, most recently from cefc8cc to 5584121 Compare August 26, 2025 17:57
@dewi-ny-je

Copy link
Copy Markdown
Contributor

I post it here even if offtopic: I was providing help on Facebook and I checked the Wiki. It looks amazing compared to few months ago, you (and everyone else who helped) did an amazing job!
Thanks.

@dewi-ny-je

Copy link
Copy Markdown
Contributor

I'll try to add some mention about the implications of various infill patterns over the layer time, as per #8107 (comment)
It does affect banding and differing shrinkage.

In which section should I put it?

@ianalexis

Copy link
Copy Markdown
Collaborator Author

In which section should I put it?

Every pattern has it's own section here https://github.com/SoftFever/OrcaSlicer/blob/main/doc/print_settings/strength/strength_settings_patterns.md

Each pattern has some params:

- **Horizontal Strength (X-Y):** Low
- **Vertical Strength (Z):** Low
- **Density Calculation:**  % of  total infill volume
- **Material Usage:** Normal
- **Print Time:** Normal-Low
- **Material/Time (Higher better):** Normal-High
- **Applies to:**
  - **[Sparse Infill](strength_settings_infill#sparse-infill-density)**

Maybe you could add something like

- **Horizontal Strength (X-Y):** Low
- **Vertical Strength (Z):** Low
- **Density Calculation:**  % of  total infill volume
- **Material Usage:** Normal
- **Print Time:** Normal-Low
  - **Layer Time Consistency:** XXXX
- **Material/Time (Higher better):** Normal-High
- **Applies to:**
  - **[Sparse Infill](strength_settings_infill#sparse-infill-density)**

The issue is how to calculate this difference. To calculate the other values, I used that XLSX file where I automated the process by loading values from a standard part for each infill.
I don't know how we could do this other than by eye. If you want, talk to me on Discord and we can discuss it.

@ianalexis ianalexis force-pushed the Wiki-12 branch 5 times, most recently from f340a36 to 300ec46 Compare September 5, 2025 18:59
@ianalexis ianalexis marked this pull request as ready for review September 5, 2025 21:47
@dewi-ny-je

Copy link
Copy Markdown
Contributor

The issue is how to calculate this difference. To calculate the other values, I used that XLSX file where I automated the process by loading values from a standard part for each infill

I'm slicing a cube 100x100x100 mm 20% infill and I check the variation in layer time. "none" is zero, "minimal" is few percent, "large" is more than 100%, then "low" for few tens % (think gyroid)

@dewi-ny-je

Copy link
Copy Markdown
Contributor

strength_settings_patterns.zip

Here it is

@SoftFever SoftFever left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome!
Thank you!

@SoftFever

Copy link
Copy Markdown
Collaborator

Fantastic work! I will do an overall review of the Wiki content before I release the public 2.3.1 Beta.

@SoftFever SoftFever merged commit 4faaa5e into OrcaSlicer:main Sep 9, 2025
13 checks passed
@dewi-ny-je

Copy link
Copy Markdown
Contributor

Did you include my last file?

@ianalexis ianalexis deleted the Wiki-12 branch September 9, 2025 14:28
@ianalexis

Copy link
Copy Markdown
Collaborator Author

Did you include my last file?

I didn't get to see it before they accepted the PR. I saw it and it looks good. I'm going to make some changes (to the xlsx and the file) and if you want, I can send you the files so you can upload your own PR, or if you prefer, I can upload it and list you as a co-author. Whatever you prefer.

@dewi-ny-je

Copy link
Copy Markdown
Contributor

I uploaded the file since I was the only one to modify it, now you can upload as part of your commit and list me as co author. Maybe two commits, one for mine and one for your changes on top, so I'll review them more easily.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants