1.06 has been released! It features Aladin support so development for DiveProxyCE
has been stopped.
Have you ever thought of saving about USD 200,-- for a Uwatec®
MemoMouse™ and paying about USD 900,-- for a PDA instead?
If so, here's a good excuse. I wrote DiveProxy CE
as a tool to buffer data from all kinds of Uwatec® Aladin dive computers, primarily to
extend the limited space for dive profiles. As the name states, it is written
for PDAs running Windows™ CE 3.0, PocketPC. Versions are available for MIPS,
ARM (XScale, PXA2xx) and SH3 CPUs. It is tested on Casio Cassiopeia E-115 and E-125, and reported
to run on several types of iPaq and hp Journada. If you have
access to other PocketPCs, please let me know if it works!
The first stage featured receiving data from the Aladin and transferring it
to a PC based program later on. Next came the urge to have a look at the dive
profiles while out for some time too. Together with the need to correct the
slack of the internal clock and to add time zone support the program now is more
or less complete. If you can't share my opinion on this, please let me know
about your ideas. If I find them useful and within my capabilities I may
To protect my PDA when I carry it under humid conditions (on board of a live
aboard boat e.g.) I bought a waterproof bag (see image further down). I haven't
tried it yet but what about a game of Solitaire when you have nothing else to do
for 6 minutes at 3 meters?
What DiveProxy CE is
DiveProxy CE is mainly a data proxy. It
is designed to look like a PC running DataTrak DOS to an Aladin and like an
Aladin towards a PC. Some of my friends own an Aladin too. DiveProxy
CE is designed to cope with more than one Aladin, even within a file.
Data packets are distinguished by the internal serial number. DiveProxy CE is
an expensive replacement for a MemoMouse with added data view.
storing groups of data packets transferred from Aladin computers.
sending stored data packets to a PC (Aladin emulation).
displaying the internal serial number or an alias name to identify the
Aladin data packet.
compensation for the internal time zone of the Aladin (for display only).
displaying the true dive number (you may specify the offset between your
true number of dives and the Aladin number of dives).
viewing logbook data (dive number, time, date, max. depth, duration,
surface interval, water temperature, warnings, ...)
viewing a dive profile for dives with profile data (about 70 minutes
across the screen, 100 for Handheld PC).
German dialogs and messages.
installable English dialogs and messages.
transmitting a compensated date/time to the PC (true time rather than
Aladin time zone time).
automatic correction of the time stamps received from the internal Aladin
clock (PDA local time).
The receiver module is available as an ActiveX control (PC and Win CE)
with Visual Basic sample code.
During my last holidays I was wondering if I should continue DiveProxyCE at
all. To be honest, it looks old-fashioned and dull, compared to TravelTrakCE.
I'm currently developing an import function to merge Aladin log and profile info into
TravelTrakCE. This would mean the end of DiveProxyCE but
then, there would
be a real log for Aladin computers too.
support for the new Smart™ series of Uwatec® dive computers
(see the TravelTrakCE page for details).
What DiveProxy CE is not
DiveProxy CE is no dive log.
You can't modify the data packets.
You can't add any information to the log entries.
It's nearly as stubborn as a real Aladin.
It doesn't beep that often though.
If you're looking for an electronic dive log, there are two possible
1) You may use SmartTrak provided by Uwatec and my latest creation, TravelTrakCE.
Although the profile display looks better than in DiveProxyCE
and additional log info may be added, there are a few shortcomings. There is
no possibility, to read Aladin data straight into SmartTrak, not even with a
MemoMouse. The only way is to read the Aladin through TravelTrakCE
and import it on the PC.
2) For a full featured operation on both a PC and a PDA I recommend WLog by Thomas
Temesvari for the PC side. WLog can't import TravelTrakCE
data files though. You may use any other communication software able
to read an Aladin but I haven't tested others (DataTrak DOS doesn't run on my
PC, it's far too fast).
If you want a dive log for Windows CE (especially for
older Win CE versions or Handheld PC devices) that interfaces with other
shareware or freeware solutions on a PC, try pDiveLog
by Chris Jackson. It was designed to run under Windows™ CE 2.x and has
been modified to run under version 3.0 too, recently. There's a similar piece of software for the Palm
series of PDAs called pAladin.
It offers Aladin and MemoMouse emulation towards a PC. As I've heard, now even
Smart Pro, Smart
Com and Smart Tec support: TravelTrakCE – version
Although the original Uwatec® interface works with my PC it doesn't with the serial cradle of my
PDA (a Casio Cassiopeia E-125). Research has shown that it works with the Casio serial cable. The DIY model described at Matthias'es
DIY interface works fine with all devices I've tested so far. It seems to draw less power from the PDA's interface chips.
A word on cable connections
Most PDAs come with a (serial) cradle. It is designed to plug into the serial
port of a PC. Therefore it features an internal "null modem", meaning
that the data and control lines are crossed. This way the receive line from the
PC will meet the transmit line from the PDA and so on. Even When you buy a
serial cable for a PDA it most probably is a "sync cable" meant to
replace the cradle when you're out and about. These cables feature the same
female (usually 9 pin-) socket and pin layout as the docking stations.
The DIY interfaces as well as the original Uwatec interface are designed to
plug into a PC as well. That's where all the troubles start. If you want to
connect them to a PDA you have three choices.
Build the interface to match the PDA pin layout. This means to use a male
SUB-D 9 pin plug and swap the connection of RxD – TxD, DTR – DSR and CTS
respectively. If the PDA connects well with a PC the pin layout most
probably is: TxD (2), RxD (3), RTS (4), DTR (7) and GND (5).
Use a null modem cable or converter between the interface and the PDA.
This is the easy way, especially if you didn't build the interface on your
own and if you don't mind the extra item to carry around. Warning: a simple
gender changer doesn't do the trick. A null modem has at least the following
connections (SUB-D9 pin numbers): 2–3, 3–2, 4–6, 6–4, 7–8, 8–7 and 5–5.
Build a double-headed interface as shown in Rein
van Koten's homepage. It is very
useful if you want to transfer data to both the PDA and the PC without any
further plugs and cables.
The CE setup images are now available for ARM (and XScale), MIPS and SH3, Pocket PC
Windows CE 3.0, Pocket PC 2002 and Handheld PC Windows CE 3.0. All packages are available in a CPU specific PC setup
(runs under Windows 98, ME, NT 4.0, 2000, XP).
DiveProxyCE is freeware. I'm not only interested
to know about those who encounter troubles when installing or running DiveProxyCE.
My provider is a bit strict on scripting on this site. Therefore, I'm asking you
to tell me
(instead of a smart registration form) so I know you're running DiveProxyCE.
If you are interested in future releases or other related stuff I'm creating
please state so. I hate spamming so I won't put you on any
mailing list by default.
Pocket PC Win CE 3.0 latest release (10-FEB-2003)
Download for ARM and XScale CPUs only: please mail me if you need the ARM
Download for MIPS CPUs only: please mail me if you need the MIPS version.
Download for SH3 CPUs only: please mail me if you need the SH3 version.
Handheld PC Win CE 3.0
The application was spawned from the 1.05. I tested the
transmission with a hp690 Handheld PC.
Profile and log data display seems mostly ok. There's
a date bug with time zones (GMT +
x only) in the MFC library for CE 2.11, go west! The only other work around is to compile
it for Win CE 3.0. I haven't heard bad things – either because nearly nobody
is using this version – or it works quite well.
The HandheldPC version isn't as complete as The PocketPC version Dialogs and Labels are in German only.
I won't be working on it any further.
There's so much else to do, ...
ActiveX Control for Windows 98/ME/NT/2000 and Win CE
I've built an ActiveX control. It features data
transmission from the Aladin only. It does not emulate an Aladin. All data items
stored in the Aladin are presented through an easy to use interface. Raw Aladin
data packets may be saved to disk. The package contains a developer version
for Win 2000 and four controls for different CPUs (ARM, MIPS, SH3, CEF) under Win CE as well as samples
in VB for Win 2000 and Win CE. I'm keen about the software you're going to write
with my controls. Please drop me a line
if you like to receive a free copy. I'm not
going to put my package here for download.
All packages are provided as .zip files. Actually these archives contain
nothing but a single .exe file but my provider allows .zip downloads only.
In order to get the whole thing running you need to follow the steps shown
Download the image suitable for your PDA. You may find the CPU type in the
system settings pages of your PDA or in the manual.
Unpack the setup image to a directory of your choice on your PC. This may
be any directory, e.g. the temp directory.
Run the setup by double clicking. You will be prompted to select the
install directory where the CE image will be stored on your PC. After this
step a set of files should show up in the specified directory.
Connect your PDA, open ActiveSync, select "Tools|Add/Remove
Programs..." The list of installable software should contain a new
entry for DiveProxyCE.
Check the entry "DiveProxyCE". Click OK to start the CE
installation. There should be a message box prompting that you should have a
look at your PDA's screen for further instructions.
Find the shortcut to DiveProxyCE in the start menu on your PDA and run the
software, that's all!
If DiveProxyCE doesn't show up in the list of installable software, check the
Did you download the image suitable for your PDA's CPU type?
Software written for other CPUs than the currently connected PDA are not
shown in the list of installable software. Connect the PDA you downloaded
the software for. Check the CPU type of your PDA and have another try.
There's five more chances!
Does your PDA run the required version of Windows CE?
If not, sorry. It's been a lot of work to write and maintain the 2 versions
I've written up to now. I gave away the sources to somebody willing to
support older versions of Windows CE some time ago. I didn't hear from him
ever since. I hope he didn't commit suicide reading my source code ;-)
Did the CE image files install properly? If yes, (there should be a .DAT,
.CAB and .INI file in the setup directory) you may try to register
DiveProxyCE manually with the ActiveSync Application Manager.
Type: "C:\Program files\microsoft activesync\CEAppMgr" /register
... from a command prompt. Alter the line to match the actual directories
and file names on your PC.
If the Aladin switches to dive plan mode when connected:
Check, if DiveProxyCE shows the receive dialog. The serial interface is
turned on only as long as the transmission dialog windows are open. If the
interface's power supply isn't turned on it shortens the contacts of your
Aladin. It doesn't harm AFAIK but it's annoying.
Check your interface. A not properly connected interface (wrong pin layout
e.g.) may cause such an effect.
The interface may draw too much current from the serial plug of your PDA.
A possible solution is either a serial cable with separate power supply or
an interface built with less power consuming components.
If DiveProxyCE always reports an error after transmission:
I found out, that at least with my PDA (Casio E125) transmission fails if
it is connected to the power supply. At least in Mexico at 110V/60Hz. I
didn't find time to verify this at 230V/50Hz. It might be worth a try to
disconnect the PDA from the mains while transferring data.
All other troubles:
The version log applies mainly to the Pocket PC version. I don't have a
Handheld PC and I did it out of curiosity | to be nice | 'cause I'm stupid.
That's why I do all changes to the Pocket PC version first. I port the changes
to the Handheld PC version only when there's a lot of time (or somebody REALLY
poor out there needing the new feature for his/her next dive in the Maldives
– while I'm sitting at home in front of my PC).
Now the offset for the dive number may be changed for every download.
Thus, you may compensate for dives that caused multiple log entries or if
you did dives without your own DC. A message box now warns if there was a
transmission error. Transmission timing has been tuned for sensitive PDAs.
Transmission packets can be deleted. Some minor performance improvements are
implemented. The data file format has changed and may not be read by prior
releases. Older files will be converted automatically when opened. The
language resources have been changed. if you have installed a language pack
for DiveProxyCE you have to upgrade to the current version.
There was a bug when displaying dives longer than 99 minutes and with the
display of certain profiles from an Aladin Air O2. As a new feature the
battery capacity is displayed in the details dialog. If you use the English
language pack you have to re-install it as well (changed dialogs).
No real release, but a correction of the setup for ARM CPUs only. The setup
now correctly registers both the main application (German dialogs) and the
additional English language support DLL with ActiveSync. You may install
the main application with or without the additional language support.
International language support checks now for matching versions. The setup
allows to install the application and language files separately. Feel free to translate the dialogs, menus
and strings and build your own DLL. I'd like to get a copy to include it in
a distribution package.
The connection icon in the receive dialog now works as expected. After a
completed transmission the icon doesn't change from "transmission
International language support added. Up to now, there's German (built in)
and English (as a DLL) available.
Known bugs: the connection icon in the receive dialog sometimes shows
"no connection", even if there is an Aladin connected.
Lots of time zone conversions. DiveProxyCE should now compensate for
almost all derivations of the internal clock of your Aladin. It also should
display correct times as long as you set your PDA to the local time zone of
your diving area when transmitting from the Aladin and the same time zone as
the PC when sending data to WLog e.g.
Some minor changes in the GUI, There's no more time zone setting in the
Alias list e.g.
The file format changed from prior versions to cope with the additional
data. As files are versioned this means that you may read files written with
older versions. You can't read files written with 1.05 with older versions
though. Date/time entries from older versions are displayed according to the
internal time of your Aladin without any compensation.
Data transmission to a PC should work now more stable. In addition, the
log dates and times are transmitted as they should be.
Spawned a version to compile and run on a Handheld PC, Win CE 2.11 and
than a Beta yet. Partly tested with the simulation.
Correct display of the serial number if no alias was specified.
Minor performance issues.
Internal code cosmetics and stabilization.
Display of log entries when the Aladin holds exactly 37 dives for the
Scaling of the profile corrected.
Setup splitted for different platforms to allow faster download.
Scrolling and scaling for the profile display.
Alias settings fixed.
Auto-selection of the last dive.
First Version released outside my PC.
Infos, suggestions, ideas: please mail
Last update 2007-08-21