Conversation
|
this is related to #1099 |
|
have to extend the chart, that it shows the applied voltage, frequency and fanspeed to have somekind of feedback for the user what is is happening. |
|
Still draft? |
|
Yes hope I have tomorrow time to extend the chart and add the missing stuff on esp side to statistic and livedata. |
main/http_server/axe-os/src/app/components/autotune/autotune.component.ts
Outdated
Show resolved
Hide resolved
main/http_server/axe-os/src/app/components/home/home.component.ts
Outdated
Show resolved
Hide resolved
main/http_server/axe-os/src/app/components/home/home.component.ts
Outdated
Show resolved
Hide resolved
main/http_server/axe-os/src/app/components/autotune/autotune.component.html
Outdated
Show resolved
Hide resolved
|
Maybe it's a good idea to wait for #955 before any changes on the home chart? |
|
Maybe it is, no hurry. will keep this up to date with master |
|
well the chart part is more or less obsolete with #955 |
f631cd2 to
9d540aa
Compare
9d540aa to
bfa5d98
Compare
…ngs and into own navigation item
…iner into master_autoclock
| description: Internal server error | ||
|
|
||
| /api/system/autotune: | ||
| post: |
There was a problem hiding this comment.
minor nit: could the endpoint be PATCH like the axe config endpoint?
main/http_server/openapi.yaml
Outdated
| type: object | ||
| properties: | ||
| power_limit: | ||
| type: number | ||
| description: Power limit (in watts) | ||
| fan_limit: | ||
| type: number | ||
| description: Fan speed limit (%) | ||
| max_voltage_asic: | ||
| type: number | ||
| description: Maximum voltage for ASIC chips (volts) | ||
| max_frequency_asic: | ||
| type: number | ||
| description: Maximum frequency for ASIC chips (MHz) | ||
| max_temp_asic: | ||
| type: number | ||
| description: Maximum temperature for ASIC chips (°C) | ||
| auto_tune_hashrate: | ||
| type: boolean | ||
| description: Whether autotuning is enabled to optimize hashrate | ||
| overshot_power_limit: | ||
| type: number | ||
| description: Power limit during overshot conditions (watts) | ||
| overshot_fanspeed: | ||
| type: number | ||
| description: Fan speed limit during overshot conditions (%) | ||
| max_temp_vr: | ||
| type: number | ||
| description: Maximum temperature for VR (°C) | ||
| required: | ||
| - power_limit | ||
| - fan_limit | ||
| - max_voltage_asic | ||
| - max_frequency_asic | ||
| - max_temp_asic | ||
| - auto_tune_hashrate | ||
| - overshot_power_limit | ||
| - overshot_fanspeed | ||
| - max_temp_vr |
There was a problem hiding this comment.
same nit here, named AutotuneResponse? just Autotune?
| //all after that get not read when looping through the settings,but is still avail due nvs | ||
| NVS_CONFIG_COUNT, | ||
|
|
||
| NVS_CONFIG_KEY_POWER_LIMIT, | ||
| NVS_CONFIG_KEY_FAN_LIMIT, | ||
| NVS_CONFIG_KEY_MAX_VOLTAGE_ASIC, | ||
| NVS_CONFIG_KEY_MAX_FREQUENCY_ASIC, | ||
| NVS_CONFIG_KEY_MAX_TEMP_ASIC, | ||
| NVS_CONFIG_KEY_AUTO_TUNE_ENABLE, | ||
| NVS_CONFIG_KEY_OVERSHOT_POWER_LIMIT, | ||
| NVS_CONFIG_KEY_OVERSHOT_FAN_LIMIT, | ||
| NVS_CONFIG_KEY_MAX_TEMP_VR, | ||
| NVS_ALL_CONFIG_COUNT | ||
|
|
There was a problem hiding this comment.
Its there that http server dont have to check not used keys for the info
| isUsingFallbackStratum: boolean, | ||
| poolAddrFamily: number, | ||
| frequency: number, | ||
| frequencySet: number, |
There was a problem hiding this comment.
Its for the settings to show the frequency from the config and not that one used by auto tune.
There was a problem hiding this comment.
hmm, i think i prefer the furst as its easier to adjust the autotune if it gets confused. i got it into a state where it was holding a high voltage and low clock to reach the target temp instead of doing the opposite.
There was a problem hiding this comment.
that still do work. i only show the saved frequency in nvs as it would be expected. when you set the frequency it gets applied.
… same for target temp when switching back to pid
# Conflicts: # main/http_server/http_server.c
|
10m avg tuning is a lot more stable :D im lovin it |
|
Whats currently missing for this branch to be merged? |
Time to review. It's a really big change and it needs proper attention. You can help by also reviewing the code. |
# Conflicts: # main/http_server/axe-os/src/app/services/system.service.ts # main/http_server/axe-os/src/models/ISystemInfo.ts # main/http_server/http_server.c
…iner into master_autoclock
…ce.ts and autotune-settings.ts
|
@KillerInk why closed ? |
|
I'm bored and dont think its desired. Good luck with the project. |





What This Does
This PR introduces a new set of features that significantly enhance the auto-tuning capabilities of the ESP-Miner. The auto-tune functionality is crucial for optimizing mining performance by adjusting key parameters such as power limit, fan speed, voltage, and frequency based on real-time conditions.
Auto-Tune Enhancements:
Benefits:
By enhancing the auto-tuning features, this PR aims to provide users with more control over their mining operations, leading to improved performance and potentially higher returns.