Hi guys
This is my first post here!
I'm having a bit of trouble with my UT61E.
Using the UT61E user interface program V4.01 (UT61E.exe), and loging data to the PC in sample intervals (15 sec for example), I end with time inconsistent results in the log file. Sometimes it jumps one second, sometimes it jumps 9 minutes of log.
Since the UT61E can't be programmed, i.e. the data communication is one-way UTE61e --> PC only, and since it therefore always sends with a fixed sample interval, which the PC software can't change, the reason for the occasional 1 second jumps seem obvious. Any sample interval that isn't a multiple of the UT61E's native data rate (probably 2 sec.) will sooner or later end up with such a jump, due to accumulating errors when the software tries to map the time of received data to the nearest time for the intended sample rate. Even a sample rate set to a multiple of the native sample rate will sooner or later have such a jump, depending how the UT61E's clock rate and the Windows timer differ.
Nine minutes of data loss, however, experienced with two different pieces of software, means there is something wrong outside of the applications. E.e. the driver, Windows, hardware ...
Anyhow, you could try yet another software, http://www-user.tu-chemnitz.de/~heha/hs_freeware/UNI-T/dmm.zip Don't be surprised that the software is so small, the guy who did that software doesn't believe in .NET rubbish. Maybe that software does what you want.
I have done a good bit of logging since I got my UT-61E around New Year time. I can confirm that Bored@Work is spot on for both counts.
I deal with the +-1 tick by adding a "calculated time" column in the spreadsheet, and made that
=CellAbove + N Seconds (where N is my sampling interval)
Of course, the first row has no CellAbove, you have to copy-paste the start time onto that cell.
You will find that a few rows down, it will get out of sync (calculated time != time stamp) and then in a few more rows it will get back in sync, then later, it will be out again and back again. The time delta could be 2 clock ticks: Mathematics saids when you truncate and round, you have a +-1 on each. When PC and UT both have a +-1, your max error is 2.
I just add that extra column and plot the graph based on that extra.
* * *
As to the 9 minute lost...
After encountering the same thing, I ignore it at first, then I saw it attempting to download new anti-virus file while logging data and not having a good time doing it. So, now when I am logging, I disable WiFi and hard-IP the NIC with no gateway and no DNS. Hard-IP means type it in yourself. These auto-updates are deadly. Flash, JAVA, whatever. With the NIC having no DNS and no gateway, I can talk to it inside (so I can monitor progress remotely) inside the house, but it has no official way to talk to the outside world. It has not happened since.
If you are not sure what IP to use, turn your machine on normally and do a:
ipconfig /all
It will tell you what IP you are using. You can use the same IP and just erase the gateway and DNS entry. That IP assigned to your machine will stay with your machine for (typical) 24 hours). Without gateway and DNS, it will disable most normal network connections to the outside world. Hackers may hard-code their target IP (no need for DNS) and try various gateways (typical setup makes it easy to find). Those you will need a firewall setting to stop which is hard, or just pull the darn RJ45 plug which is easy. Make sure you set it back when done. The hacker's communication target IP is likely not their own IP but a zombie machine.
Rick