DeDragonSlayer
Registered
The program was written using Microsoft Visual C++ 2010 Express, since C++ is the language I'm still most familiar with after years of not coding, and Microsoft's IDE was the only free one I was able to find.
I'm not sure .Net is needed, if you have VC++ 2010 runtime libraries installed, but then again it's Microsoft, so you never know.
There's not much I can do about connection issues - these devices are a bit quirky, have a weak IrDA and they like to hang up communication if the connection has been interrupted. Like you already discovered, the key here is persistence.
When i wrote USBRT, I tried to figure out if any other setting could be hacked like battery level. If i recall correctly I tried to find out how to calibrate pressure and set proper time as well, but I guess I made no progress with that. Also, you know, I experimented on my own two private computers, sending semi-random characters and each time crossing my fingers that they wouldn't be bricked. So once i found out what I wanted, I promptly stopped experimenting.
Another thing - you know that there is absolutely no need for the internal clock to be synchronized with anything, since the computer doesn't show current time anyway. As long as you get into a habit of uploading the logs to SmartTrak soon after a dive, and make sure to upload all of them before replacing the battery, you'll be all set. When downloading a dive, SmartTrak checks the device time, compares it to local time, and saves the dive to it's database using local time. So even if you had the battery go dead for years, then replaced it and dived, the next dive would be saved in SmartTrak with the right time. The old ones would be all wrong of course if you wanted to import them again, but you already have them in SmartTrak, right?
Cheers!
I'm not sure .Net is needed, if you have VC++ 2010 runtime libraries installed, but then again it's Microsoft, so you never know.
There's not much I can do about connection issues - these devices are a bit quirky, have a weak IrDA and they like to hang up communication if the connection has been interrupted. Like you already discovered, the key here is persistence.
When i wrote USBRT, I tried to figure out if any other setting could be hacked like battery level. If i recall correctly I tried to find out how to calibrate pressure and set proper time as well, but I guess I made no progress with that. Also, you know, I experimented on my own two private computers, sending semi-random characters and each time crossing my fingers that they wouldn't be bricked. So once i found out what I wanted, I promptly stopped experimenting.
Another thing - you know that there is absolutely no need for the internal clock to be synchronized with anything, since the computer doesn't show current time anyway. As long as you get into a habit of uploading the logs to SmartTrak soon after a dive, and make sure to upload all of them before replacing the battery, you'll be all set. When downloading a dive, SmartTrak checks the device time, compares it to local time, and saves the dive to it's database using local time. So even if you had the battery go dead for years, then replaced it and dived, the next dive would be saved in SmartTrak with the right time. The old ones would be all wrong of course if you wanted to import them again, but you already have them in SmartTrak, right?
Cheers!
