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
After my hex303 connects to the VK mining pool, difficulty 0 will appear after about 4 hours. The device is still connected and the voltage, current, and power are normal. It is not caused by overheating (you need to restart hex303 before the difficulty will appear again). After changing to a public pool, it will still function normally for up to 8 hours.
At 3AM, the hex difficulty level was 0 again. I changed hex303 to connect to the Public Pool and it ran normally for 8 hours (from 3AM to 1PM); then I switched hex303 to connect to the VK mining pool again, and I could see 3PM & 7PM & 11PM. A total of 3 times of difficulty 0, you need to reopen hex303 to continue working.
The same situation occurs when using 302 and 302 rebase branches.
The text was updated successfully, but these errors were encountered:
After my hex303 connects to the VK mining pool, difficulty 0 will appear after about 4 hours. The device is still connected and the voltage, current, and power are normal. It is not caused by overheating (you need to restart hex303 before the difficulty will appear again). After changing to a public pool, it will still function normally for up to 8 hours.
At 3AM, the hex difficulty level was 0 again. I changed hex303 to connect to the Public Pool and it ran normally for 8 hours (from 3AM to 1PM); then I switched hex303 to connect to the VK mining pool again, and I could see 3PM & 7PM & 11PM. A total of 3 times of difficulty 0, you need to reopen hex303 to continue working.
The same situation occurs when using 302 and 302 rebase branches.
The text was updated successfully, but these errors were encountered: