Quote from: majika on March 20, 2021, 10:29:35 AM

Quote from: didouday on March 20, 2021, 12:10:45 AM

Quote from: User_86 on March 19, 2021, 11:47:57 PM

Quote from: majika on March 19, 2021, 03:03:16 PM

I used to test latency times the old fashioned way using ping.exe util but this is not very accurate way as stratum is not same as tcpip right, its like on its own layer..

Ping uses ICMP packets, not TCP/IP packets. ;-)

It does use the TCP/IP Protocol, most specifically at Layer 3 : IP.

ICMP packtz yeah.. OSI layer 3 yeh indeed.. As per the ping utility output, my bad I should have took time to look it up properly, im a bit rusty when it comes to transport protocols, its been a while Wink

Ok so .. any ideas on how to integrate this util into PheonixMiner.. I know its ultimately down to dev for some kind of hard-integration. but maybe there is a way to tie it in with "Claymore's Remote Manager" or some other mining monitoring tool/app of same ilk.
I don't use anything apart from PuTTY/vnc/Teamviewver to track my rigs.

BUT.. Ive been thinking on it a little and what about using Claymore's Miner manager to fire off ping batch onEvent.
IDK.. if any .bat scripters wanting to take a look at ways to implement automated ping tool to compliment pheonixminer..

One potential ugly method to make this work would be to leverage Claymore's Miner Monitor tool to track the rigs hashrate and the setting where it report *if* hashrate drops do XYZ Mh/s, instead of having it "action" reboot.bat or whatever only when hashrate drops, instead set a really tight hashrate value so when the rig fluctuates/deviate's even just a couple of hashes per sec., claymore monitor will ping off a bat file that does the pool ping routine.. idk what the polling time is between the PheonixMiner and Claymore's Miner manager hence why this is a ugly way to potentially achieve this without use of some kind of static scheduled task. plus this woudl still involve hands-on to switch pools from epools.txt..
so yeah thinking out loud here..
I reckon it would be a really helpful feature, Especially when looking at times like this..

Code:

Eth: Share accepted in 688163 ms <=============

you can read all info over API directly from rigs and then do as you pleased..

Code:

req_dict = {"id":0,"jsonrpc":"2.0","method":"miner_getstat2"}
s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
try:
s.settimeout(g_timeout_s)
s.connect((ip_address, server_port))
req_byte = json.dumps(req_dict, separators=(',', ':')).encode('ascii')+b'\n'
s.send(req_byte)
resp_byte = s.recv(1024)
s.close()
resp_text = json.loads(resp_byte.decode('ASCII'))
except:
#print (f"{rig_name:s}: no response within {int(timeout_s):d}sec period")
print (f"{rig_name:s}: not responding")
return 0