ping times from TN rtt min/avg/max/mdev = 39.860/42.676/52.315/2.578 ms
ping times from TN rtt min/avg/max/mdev = 39.860/42.676/52.315/2.578 ms
Ping times from Brisbane, Australia
Code:64 bytes from 66-232-106-106.static.hvvc.us (66.232.106.106): icmp_seq=7 ttl=47 time=231 ms ^C --- forum.pjrc.com ping statistics --- 7 packets transmitted, 7 received, 0% packet loss, time 6249ms rtt min/avg/max/mdev = 230.129/230.649/231.222/0.313 ms
Above is the result from the UK (Gloucestershire, England)Pinging pjrc.com [162.254.150.250] with 32 bytes of data:
Reply from 162.254.150.250: bytes=32 time=106ms TTL=54
Reply from 162.254.150.250: bytes=32 time=107ms TTL=54
Reply from 162.254.150.250: bytes=32 time=107ms TTL=54
Reply from 162.254.150.250: bytes=32 time=108ms TTL=54
Ping statistics for 162.254.150.250:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 108ms, Average = 107ms
Pinging forum.pjrc.com [66.232.106.106] with 32 bytes of data:
Reply from 66.232.106.106: bytes=32 time=107ms TTL=55
Reply from 66.232.106.106: bytes=32 time=106ms TTL=55
Reply from 66.232.106.106: bytes=32 time=107ms TTL=55
Reply from 66.232.106.106: bytes=32 time=107ms TTL=55
Ping statistics for 66.232.106.106:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 106ms, Maximum = 107ms, Average = 106ms
Quick update, this morning:
so not as bad as yesterdayCode:C:\Users\kurte>ping pjrc.com Pinging pjrc.com [162.254.150.250] with 32 bytes of data: Reply from 162.254.150.250: bytes=32 time=105ms TTL=44 Reply from 162.254.150.250: bytes=32 time=88ms TTL=44 Reply from 162.254.150.250: bytes=32 time=87ms TTL=44 Reply from 162.254.150.250: bytes=32 time=87ms TTL=44 Ping statistics for 162.254.150.250: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 87ms, Maximum = 105ms, Average = 91ms
Still 37-38 ms here. Not much beats that except Google (11 ms).
- Wes, W5ZZO
From the Netherlands:
Similar to the times from the UK.Code:Pinging 162.254.150.250 with 32 bytes of data: Reply from 162.254.150.250: bytes=32 time=110ms TTL=48 Reply from 162.254.150.250: bytes=32 time=108ms TTL=48 Reply from 162.254.150.250: bytes=32 time=109ms TTL=48 Reply from 162.254.150.250: bytes=32 time=110ms TTL=48 Ping statistics for 162.254.150.250: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 108ms, Maximum = 110ms, Average = 109ms Pinging 66.232.106.106 with 32 bytes of data: Reply from 66.232.106.106: bytes=32 time=108ms TTL=49 Reply from 66.232.106.106: bytes=32 time=107ms TTL=49 Reply from 66.232.106.106: bytes=32 time=108ms TTL=49 Reply from 66.232.106.106: bytes=32 time=109ms TTL=49 Ping statistics for 66.232.106.106: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 107ms, Maximum = 109ms, Average = 108ms
Paul
Still no email notifications - for this post or the usbhost thread.
Also earlier post took some time in browser 'spinning' then said - "leave and the post dies" I ignored and the post had completed :: This has happened in the past but not recently here.
Also seeing a DOUBLE post from mjs513 - I assume he may have gotten the above and hit save again for a double post.
@Paul - seems some issue unique about the forum server setup?
Still no email notifications - for this post or the usbhost thread.
Also earlier post took some time in browser 'spinning' then said - "leave and the post dies" I ignored and the post had completed :: This has happened in the past but not recently here.
Also seeing a DOUBLE post from mjs513 - I assume he may have gotten the above and hit save again for a double post.
@Paul - seems some issue unique about the forum server setup?
Hit save and got the WAIT and this LEAVE - hit Cancel and then this double post:
![]()
I had the same issue today with the 'spinning' but I just posted in Audio Projects with no issues.
Edit: well the spinning is back![]()
@strud had a DUPE post I removed. {was #6 after Faster-way-to-read-in-digital-inputs-into-a-byte-value
Seems there may be a timing issue with the wait then failed coordination recognizing 'posted'
@strud had a DUPE post I removed. {was #6 after Faster-way-to-read-in-digital-inputs-into-a-byte-value
Seems there may be a timing issue with the wait then failed coordination recognizing 'posted'
Edit: This gave the 'Leave' warning - I hit 'Esc'ape and see it double posted after refresh