Re: Problems importing APD CCR dive logs.

On 18 April, 2018 - Miika Turkia wrote: > On Wed, Apr 18, 2018 at 6:19 PM, Anton Lundin wrote: > > > On 18 April, 2018 - Willem Ferguson wrote: > > > > > On 18/04/2018 16:05, Miika Turkia wrote: > > > >On Wed, Apr 18, 2018 at 4:14 PM, Willem Ferguson > > >

Re: Problems importing APD CCR dive logs.

On Wed, Apr 18, 2018 at 6:19 PM, Anton Lundin wrote: > On 18 April, 2018 - Willem Ferguson wrote: > > > On 18/04/2018 16:05, Miika Turkia wrote: > > >On Wed, Apr 18, 2018 at 4:14 PM, Willem Ferguson > > > >

Re: Problems importing APD CCR dive logs.

On 18 April, 2018 - Willem Ferguson wrote: > On 18/04/2018 16:05, Miika Turkia wrote: > >On Wed, Apr 18, 2018 at 4:14 PM, Willem Ferguson > > >> wrote: > > > >Dear Miika, > > > >Would you by any chance be prepared

Re: Problems importing APD CCR dive logs.

On 18/04/2018 16:05, Miika Turkia wrote: On Wed, Apr 18, 2018 at 4:14 PM, Willem Ferguson > wrote: Dear Miika, Would you by any chance be prepared to look at the attached APD dive log? The setpoint data are

Re: Problems importing APD CCR dive logs.

On Wed, Apr 18, 2018 at 4:14 PM, Willem Ferguson < willemfergu...@zoology.up.ac.za> wrote: > Dear Miika, > > Would you by any chance be prepared to look at the attached APD dive log? > The setpoint data are there and correctly identified in the import dialog. > However, it is not written to xml.

Problems importing APD CCR dive logs.

Dear Miika, Would you by any chance be prepared to look at the attached APD dive log? The setpoint data are there and correctly identified in the import dialog. However, it is not written to xml. Consequently the setpoint is erroneously shown as the same value as pO2. Can it be user error