Page 1 of 1
L3+ Miner
Posted: Thu Nov 04, 2021 7:20 am
by Macky82
i have a l3 miner in admin says 506mh/s avg 495mh/s and on prohashing its 450mh/s and lower why is it showing so low on prohashing
![Image]()
![Image]()
Re: L3+ Miner
Posted: Thu Nov 04, 2021 8:25 am
by Alynn
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.
Re: L3+ Miner
Posted: Thu Nov 04, 2021 9:16 am
by Macky82
n=Scrypt-504,o=Scrypt-504,i=l3_504
Re: L3+ Miner
Posted: Thu Nov 04, 2021 1:43 pm
by Alynn
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."
Re: L3+ Miner
Posted: Fri Nov 05, 2021 6:02 am
by Leftoverloser
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
Posted: Fri Nov 05, 2021 7:33 am
by Alynn
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
Re: L3+ Miner
Posted: Fri Nov 05, 2021 8:57 am
by philipdizon
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
Posted: Fri Nov 05, 2021 11:12 pm
by steve_empire
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
Do you have duplicate Static IP's setup in your miners?
Re: L3+ Miner
Posted: Sun Nov 07, 2021 8:43 pm
by Alynn
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.
