My original reporting on the issue of the communication problems between SeeYou and the 5030 can be found here and here. Turns out not all was well as I had originally thought. Dave Cameron had lots of problems with the new July DLL that defined the communication protocols between the 5030 (and similar instruments) and SeeYou. David Cameron () writes:

I have had the problem of bad waypoint uploads from SeeYou to my 5030 ever since SeeYou version 3.5. Lately I have been sending test data to Andej at Naviter, and it looks like after three tries they now have it fixed (with a new DLL). The link below is to an updated bracom.dll to replace the current one in the SeeYou program directory. Andrej asked that I pass this on to anyone having similar problems.

One additional note: The first few waypoint seem to upload extremely slowly, and then the rest proceed at the “normal” speed (as indicated by the rate of beeping of the device). Andrej says that this is expected and is due to the way they verify correct communication with the device.

http://data.naviter.si/dll/winlog/bracom.dll

The July DLL had new problems for me, still corrupted altitude data, but causing program error dialogs as well. I sent him lots of log files from all three dlls, and he says they have definitively fixed the problem now. It works for me. This new .dll is as of 9/19/2007. Logging goes to C:TMPBRACOM.LOG.

It’s a little maddening that they don’t seem to have any version control on the DLL files. In my communication with Andrej I referred to them by their md5chksum result. The DLL file I downloaded from the link above and that works for me has an md5chksum of: dad1ad0971f6081ef92676ab41a4c949

The md5sum calculator can be found here:

http://www.etree.org/md5com.html#download

Discuss SeeYou at the Oz Report forum
   
 
 
del.icio.us