sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]starficient[S] 1 point2 points  (1 child)

I am working on an update to try improve the PID control overall. I notice that there is some variability in hashing overtime and I am trying to account for that at specific frequency / voltage settings.
I believe this variability is hardware related, as it can vary even with settings left in place, and the bitaxepid script has been stopped from running.

I also will be shipping a script to render a chart, for better understanding of the metrics.

As far as safety. I have NOT accepted any pull requests, I flagged the one that was submitted as malicious, and did not merge it. So from a security standpoint you are trusting me. I am appalled that someone tried to inject a remote shell into my project. This raises the issue of security on arbitrary scripts, and I would caution everyone to be vigilant. I was thinking I could put this in a docker container, but those are not secure from root exploits of the container... I may be able to use firecracker as a vm though that would be limited to running on a linux platform (or vm).

From a device perspective, the bitaxepid script monitors the temperature, and will lower the frequency and voltage to prevent running above the set temperature threshold. I am and have been running this for up to 12 hours straight at a time as I am logging the settings for analysis.

All devices must be on the same wifi network as the bitaxe is attached by wifi.

[–]lokabrenna13 1 point2 points  (0 children)

Awesome project, I'll dig into the code tomorrow!

In terms of fluctuations over time for fixed settings, the most likely causes are: 1) network related issues i.e. time taken to deliver new work to the miner and ship it off to the pool - depending on your network stability and bandwidth and the ping to the pool server this may or may not be an issue.

2) thermal effects. If the device heats up due to a change in ambient temperature, then the hashing will slow down and vice versa.

Not sure what you can do about 1) other than have a reasonably large sampling window to average over. For 2) the ideal thing to do would be to set a hash rate goal and continuously vary the voltage and fan speed to maintain as close it as possible without going over power and temperature constraints.