L3+ Miner
Forum rules
Welcome to the mining rig and connectivity support forum!
This forum is for discussing issues with mining rigs and connectivity issues with experienced PROHASHING miners. This is a great place to ask questions about connecting specific hardware to PROHASHING.
Remember, PROHASHING employees do not closely monitor the forums like we do the official support channels, so this forum's purpose is to connect you with other PROHASHING miners who have experience with similar hardware/issues. If you have connectivity issues you are unable to resolve here on the forum, please submit a ticket through the official support channels.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Welcome to the mining rig and connectivity support forum!
This forum is for discussing issues with mining rigs and connectivity issues with experienced PROHASHING miners. This is a great place to ask questions about connecting specific hardware to PROHASHING.
Remember, PROHASHING employees do not closely monitor the forums like we do the official support channels, so this forum's purpose is to connect you with other PROHASHING miners who have experience with similar hardware/issues. If you have connectivity issues you are unable to resolve here on the forum, please submit a ticket through the official support channels.
For the full list of PROHASHING forums rules, please visit https://prohashing.com/help/prohashing- ... rms-forums.
Re: L3+ Miner
What is your e= argument? Are you using the correct i= argument from the configurator?
Basically prohashing values are an estimate based upon how many shares you are turning in. You should expect to see some variance, or you haven't tweaked your password arguments.
Basically prohashing values are an estimate based upon how many shares you are turning in. You should expect to see some variance, or you haven't tweaked your password arguments.
Re: L3+ Miner
n=Scrypt-504,o=Scrypt-504,i=l3_504
Re: L3+ Miner
try using e=off if your mining software doesn't require refreshes every 60 seconds.
"When "e=off," the mining server only sends work restarts and difficulty commands when those commands are necessary for their intended purpose. When "off" is selected, it is possible that no communication may be sent to the workers for minutes at a time, and buggy mining software may make the erroneous assumption that the mining server is offline and disconnect. If you know that your workers do not behave in this manner, or if you can figure out how to configure your workers to continue mining even if there has been no communication for 60 seconds, setting "e=off" will increase the hashrate of your workers because no time will be wasted in processing unnecessary communication or restarting work unnecessarily."
"When "e=off," the mining server only sends work restarts and difficulty commands when those commands are necessary for their intended purpose. When "off" is selected, it is possible that no communication may be sent to the workers for minutes at a time, and buggy mining software may make the erroneous assumption that the mining server is offline and disconnect. If you know that your workers do not behave in this manner, or if you can figure out how to configure your workers to continue mining even if there has been no communication for 60 seconds, setting "e=off" will increase the hashrate of your workers because no time will be wasted in processing unnecessary communication or restarting work unnecessarily."
-
- Posts: 7
- Joined: Sat May 15, 2021 12:51 pm
Re: L3+ Miner
Alynn wrote: ↑Thu Nov 04, 2021 1:43 pm try using e=off if your mining software doesn't require refreshes every 60 seconds.
"When "e=off," the mining server only sends work restarts and difficulty commands when those commands are necessary for their intended purpose. When "off" is selected, it is possible that no communication may be sent to the workers for minutes at a time, and buggy mining software may make the erroneous assumption that the mining server is offline and disconnect. If you know that your workers do not behave in this manner, or if you can figure out how to configure your workers to continue mining even if there has been no communication for 60 seconds, setting "e=off" will increase the hashrate of your workers because no time will be wasted in processing unnecessary communication or restarting work unnecessarily."
Where exactly is the "e=off" located? I have a couple L++ and use the password i=l3_596. They run a little slow too. MAybe this could help me out a swell. Thanks !
Re: L3+ Miner
In the password argument delimited by commas (,)
i=l3_596,e=off
you may also want to look into a minimum difficulty and other such tweaks
Full list of the arguments and what they mean are here
https://prohashing.com/help/optimizing-pool-miners
i=l3_596,e=off
you may also want to look into a minimum difficulty and other such tweaks
Full list of the arguments and what they mean are here
https://prohashing.com/help/optimizing-pool-miners
-
- Posts: 1
- Joined: Fri Nov 05, 2021 7:04 am
Re: L3+ Miner
hello, I have two L3++ . my miners all of the sudden stop hashing when the other is hashing. I rebooted both machines, changed names and changed location for the machines. but, once I turn one on, the other stops hashing. does anyone have a suggestion
-
- Posts: 12
- Joined: Thu Jun 10, 2021 1:09 pm
Re: L3+ Miner
Do you have duplicate Static IP's setup in your miners?philipdizon wrote: ↑Fri Nov 05, 2021 8:57 am hello, I have two L3++ . my miners all of the sudden stop hashing when the other is hashing. I rebooted both machines, changed names and changed location for the machines. but, once I turn one on, the other stops hashing. does anyone have a suggestion
Re: L3+ Miner
so its more for the software thinking that there is a disconnection if there is no communication from the server. So in this case, yes, it works with GPUs since it's the mining software doing the disconnecting.