This section contains instructions for the setting up (<setdcdata>), or downloading of data from (<getdcdata>) respectively, a dive computer via UDDF. Of course, using the <divecomputercontrol> section requires that the dive computer supports communication via UDDF. Because (at present) none of the available dive computers do support UDDF, this list does not claim any completeness. It is likely that new elements will be added in this section as technological possibilities will further increase in the future. Especially in this section collaboration of dive computer manufacturers is desired and wanted so that "latest techniques" can be implemented in UDDF!
<setdcdata>
All elements in this section begin with "setdc..." (for "set dive computer ...") to have a distinction from other "set" elements in other sections. Subelements need not to begin with "setdc..." (see instructions for date, and time etc.).
<setdcpassword> <setdcownerdata> und <setdcbuddydata>
All elements (data) given inside <owner>, and <buddy> are transferred to the dive computer using the above given functions.
<setdcdate> <date> <year> <month> <day> <dayofweek> <setdctime> <time> <hour> <minute> <setdcalarmtime> <time> <hour> <minute> <dcalarm> <alarmtype> <acknowledge/> <period> <setdcdivedepthalarm> <dcalarmdepth> <dcalarm> <alarmtype> <acknowledge/> <period> <setdcdivepo2alarm> <maximumpo2> <dcalarm> <alarmtype> <acknowledge/> <period> <setdcdivetimealarm> <diveduration> <dcalarm> <alarmtype> <acknowledge/> <period> <setdcendndtalarm> <dcalarm> <alarmtype> <acknowledge/> <period> <setdcdecomodel> <name> <program> <setdcaltitude> <setdcgeneratordata>
<getdcdata>
All elements in this section begin with "getdc..." (for "get dive computer ...").
<getdcalldata/> <getdcgeneratordata/> <getdcownerdata/> <getdcbuddydata/> <getdcgasdefinitionsdata/> <getdcdivesitedata/> <getdcdivetripdata/> <getdcprofiledata/>