I would change
to
But your ZEC config looks like it should work with DwarfPool.
It is also worth trying removing the workername:
ZEC_WORKER="nv$IP_AS_WORKER"
to
With:
Also I have the error "Utilization is too low: restart 1bash" and multiple "Maxximus007_AUTO_TEMPERATURE_CONTROL" tabs. What it's mean? Maybe this is a reason of problem?
Due to some changes I made in the last 1bash; currently when in LOCAL mode: each restart of 1bash will kill the existing Maxximus007_AUTO_TEMPERATURE_CONTROL process, but not kill the tab containing it; then a new Maxximus007_AUTO_TEMPERATURE_CONTROL tab will be created with a new process inside.
The problem is likely that you are not connecting to the pool for some reason; when this happens the watchdog will detect low utilization and restart 1bash.
You can see if you can reach the pool by opening a new guake tab and entering the following cmd:
ping zec-ru1.dwarfpool.com
I would try to use a different pool and see if you can connect. For now while troubleshooting; I would set :
IAmNotAJeep_and_Maxximus007_WATCHDOG="NO"
fullzero, thank you for your reply. I'm sure that is no problem with connection to the pool, also ping is ok. I think it's a some problem with powerlimit, because when I disabled watchdog and trying to change some parameters, include powerlimit, my hashrate is growing to 200 Sol/s, also when I changed some parameters I seen my hashrate grow to 400 Sol/s, but I don't remember parameters what I changed. So at this moment I have hashrate 200 Sol/s with powerlimit 200, when I trying to change it to 250 I have lower hashrate. Cc 150, mc 900 as you wrote in the first message here. Also console showed power consumption lower than I set powerlimit. Any idea?