Thanks for the infomation from the both of you and code to make it work...
The version that "Dias de verano" created however looks to be more of what I need a date/time stamp to tag with each recording as shown below:
The response times to this idle network device should be far better than the ms recordings shown below since we have a T1 connections between sites. I hope to roll this out to a number of systems in our triangulated network of 3 large main sites and find the bottlenecks.
One question I have with the data recorded to make sure I fully understand it is that it is recording 3 pings per recorded interval? .... so as seen below the pings of 105, 158, and 127 are the ms response times in that order followed by the next line of 63,163, and 109... so it would be if looking linear at the data like so in ping order ?
105 ms
158 ms
127 ms
63 ms
163 ms
109 ms
------------------------------Data Collected below in pinglog.csv ---------------
"Date","Time","IP Address","Min","Max","Ave"
"Mon 08/25/2008","17:16:29.81","192.168.1.125",105,158,127
"Mon 08/25/2008","17:16:33.03","192.168.1.125",63,163,109
"Mon 08/25/2008","17:16:36.23","192.168.1.125",100,138,118
"Mon 08/25/2008","17:16:39.47","192.168.1.125",97,166,133
"Mon 08/25/2008","17:16:42.70","192.168.1.125",44,91,75
"Mon 08/25/2008","17:16:45.92","192.168.1.125",125,180,147
"Mon 08/25/2008","17:16:49.18","192.168.1.125",77,113,101
"Mon 08/25/2008","17:16:52.40","192.168.1.125",36,125,69
"Mon 08/25/2008","17:16:55.57","192.168.1.125",16,188,106
"Mon 08/25/2008","17:16:58.75","192.168.1.125",75,149,104
"Mon 08/25/2008","17:17:02.00","192.168.1.125",79,152,100
"Mon 08/25/2008","17:17:05.18","192.168.1.125",16,140,100
"Mon 08/25/2008","17:17:08.43","192.168.1.125",71,123,100