AERIS ACI 2.2.2 beta

Please register or login

Welcome to ScubaBoard, the world's largest scuba diving community. Registration is not required to read the forums, but we encourage you to join. Joining has its benefits and enables you to participate in the discussions.

Benefits of registering include

  • Ability to post and comment on topics and discussions.
  • A Free photo gallery to share your dive photos with the world.
  • You can make this box go away

Joining is quick and easy. Log in or Register now!

Doug, can you comment on which OceanLog core this relates to, ie, is this = OL 2.2.4 or = OL 2.2.2?
 
Just did a quick try of the new release. Visually, it has a nice new look
especially in the details page.
It installed on top of ACI 2.2.0 on Vista with no issues.

The MAX depth on the simulated LCD screen in the dive details is not
working properly. It always indicates MAX depth for the entire dive
rather than the maximum depth achieved so far based on the cursor location.
i.e. if you are only 5 minutes into a dive and have only dove to 20 ft but
the maximum for the dive was 100ft, the simulated LCD will show 100 ft rather
than 20 ft.

OceanLog versions 2.2.4 and the newer 2.2.5 do not work this way.
They will show the deepest depth up to the current point in time.

========================================================

With respect to export files. It is painful to have a separate export file
per each dive exported.

DAN's DL7 ZXU file format does not mandate that each and every dive have its own file.
The current DL7 document has a small note in it just below Table 2 that states to repeat
segments ZDH, ZDP and ZDT for each dive. This allows multiple dives
per ZXU file. (DAN's PDE and 3rd party s/w dive log packages already support this)
However, in order to support multiple dives with different dive computers
a ZRH segment is needed for each dive computer just prior to the
ZDH, ZDP, and ZDT segments.

Currently, there is nothing in the DL7 document other than this tiny note below Table 2
that mentions how to do multiple dives and whether or not multiple ZRH
segments is allowed/supported which would allow supporting multiple dives from different
dive computers inside the same ZXU file.

That said, the paragraph above Table 2 which describes the file format
and defines what a "Segment" is, states that Segments can be required or optional,
"may occur only once in a message or they may be allowed to repeat".

According to that, multiple ZRH segments should be allowed.

DAN needs to clearly specify if multiple ZRH segments are allowed.
If multiple ZRH segments were used, any number of dive computers
with any number of dives could be bundled together inside a single ZXU file.

In the absence of using multiple ZRH sections inside a ZXU file, multiple
dives inside a single file can still be supported. The limitation will be that all the dives in a single
ZXU file must all be from the same dive computer.

Given that the majority of users that use the export function will be exporting
the data to be re-imported into a 3rd party application, and this will more than likely be after a group
of repetitive dives or dive trip that were all done on the same dive computer,
it would be really nice if all the dives were put into a single ZXU file rather
than creating a separate ZXU file for each dive so that
the import experience is greatly simplified.

An easy option for this might be to alter the "Export Dive Details" dialog such that
once a given dive computer type is selected, all the dives for computers that
do not match this dive computer are grey out and disabled. This would allow
the user to create ZXU files with multiple dives and not violate the single ZRH
segment limitation.
Since most users will only have a single dive computer or only need to export
dives from a single dive computer anyway, more than likely in real life most
users will never have to deal with multiple ZXU files when exporting/importing
data from ACI/OceanLog to their favorite 3rd party application.

Another easier alternative would be to create a ZXU file for each dive computer
say based on the serial number of the device. This would then allow all dives
to be exported and if there happens to be more than one device, each unique
divice (dive computer) will have a ZXU file with the selected dives.

In the mean time, I'll contact the DAN PDE guys and get a ruling on whether multiple
ZRH segments are allowed or supported.

If multiple ZRH segments are allowed, then all the dives from all the
user's dive computers could be put inside the same ZXU file.

--- bill
 
Hi Doug,

I like the look and feel of the new program. The scrolling comments in the dive area is much nicer than the small box at the bottom of the old interface.

I ported over a 2.2.0 file with no problems and no loss of data.

However, the download interface does not work. When I try to download from my XR2, I get a message that the DC does not match the model selected in the software. I downgraded to 2.2.0 and the interface worked fine, upgraded to 2.2.2 again and the interface stopped working again. I have not tried my Atmos 2 yet, but I will let you know.

-Ron
 
Decided to try the Atmos2 while I was thinking about it. It works fine, so the problem seems to be limited to specific models.

-Ron
 
"get a message that the DC does not match the model selected in the software." It look like you had the wrong model pick for the download. In the top left corner of the download screen make sure it say you mode its downloading it was probably looking at your Atmos 2
 
https://www.shearwater.com/products/perdix-ai/

Back
Top Bottom