Tusa Zen IQ-900 Import Issue

[KTwo]

When I import my dive data in Diving Log 6.0, the program doesn't read the temperature data from my Tusa Zen IQ-900. Everything else appears to be ok, just missing the temperature data.

-K2

[divinglog]

Hi

Do you download the dive computer directly with Diving Log or do you import from a file? If you import a file, please send it to info (at) divinglog.de

Kind regards,
Sven

[KTwo]

Downloading directly from the computer in to Diving Log 6.0 results in the temperature data missing. When I import my dive data from the dlg file generated by Tusa's program results in the temperature data appearing in Diving Log.

[TnT]

I'll need a memory dump of your dive computer to investigate this. Download the universal test application, and run it with these options:

Code: Select all

universal.exe -v -l atom2.log -m atom2.bin -b atom2 <COMx>

Replace <COMx> with the correct serial port (typically COM3). Afterwards, email me the atom2.log and atom2.bin files.

[KTwo]

TnT -

Thanks for taking a look at this. Had no luck with universal.exe. The text of the atom2.log is below.

[0.000011] DATETIME 2015-10-12T11:02:30Z (1444647750)
[0.000229] VERSION 0.5.0-devel (c72bdfe4e4175cb7ad2eb3dc4caa0e9fd9c12962)
[0.000809] Opening the device (Oceanic Atom 1.0, COM3).
[0.001517] INFO: Open: name=COM3
[0.002984] ERROR: The system cannot find the file specified (2) [in ../../source/src/serial_win32.c:152 (serial_open)]
[0.003236] ERROR: Failed to open the serial port. [in ../../source/src/oceanic_atom2.c:548 (oceanic_atom2_device_open2)]
[0.003659] ../../source/examples/universal.c:763: Error opening device.
[0.004136] Result: Input/output error

I tried several things...
1. COM ports 1-4
2. With Diving Log 6.0 and Tusa Data Log 1.0.9 running
3. Without Diving Log 6.0 and Tusa Data Log 1.0.9 running
4. With my dive computer screen showing 'PC' and without

COM3 is the correct COM port. Using that COM port both programs can communicate with the computer and download.

I'm assuming my Tusa Zen is basically an Oceanic Atom2?

Thanks again,
-K2

[TnT]

[0.001517] INFO: Open: name=COM3
[0.002984] ERROR: The system cannot find the file specified (2) [in ../../source/src/serial_win32.c:152 (serial_open)]
...
COM3 is the correct COM port. Using that COM port both programs can communicate with the computer and download.

COM3 doesn't even exist, so it can't be the correct one. Usb-serial ports will only appear if the pc interface is connected to your PC, so make sure it's connected before starting the test application!

On Windows, only one application can have the serial port open. So if Diving Log or Tusa Data Log is already communicating with the dive computer, then other applications will fail. But in that case the error would be different. Just having those applications open (without active communication) shouldn't cause any problems.

I'm assuming my Tusa Zen is basically an Oceanic Atom2?

No, they are different devices, but they do share the same communication protocol.

Jef

[KTwo]

Jef -

Latest problem . . . Now all I get is this:

[0.000011] DATETIME 2015-10-13T01:51:01Z (1444701061)
[0.000411] VERSION 0.5.0-devel (c72bdfe4e4175cb7ad2eb3dc4caa0e9fd9c12962)
[0.000784] ../../source/examples/universal.c:973: No matching device found.

Followed by 'Usage:', 'Options', and 'Supported Backends' lists.

The dive computer is in download mode - displays 'PC' and the 120 second count down timer.

COM3 exists now - I can download to Tusa software but not Diving Log.

-K2

[divinglog]

But you said in your first posting that you can download to Diving Log and just the temperature data was missing? Now you say you can't download anymore? I think the applications are blocking each other. Please make sure you're running only one application during your tests (Tusa OR Diving Log OR the Universal.exe)

[KTwo]

But you said in your first posting that you can download to Diving Log and just the temperature data was missing? Now you say you can't download anymore? I think the applications are blocking each other. Please make sure you're running only one application during your tests (Tusa OR Diving Log OR the Universal.exe)

When running universal.exe today, it was the only program running. I ran Tusa Data Logger and Diving Log to confirm that COM3 was the correct port. For some reason Tusa Data Logger worked and Diving Log did not. Probably related to operator error. I'm not worried about that now. Universal.exe doesn't give me the 'can't find COM3' error so that part is correct. Neither Tusa or Diving Log were running when I ran universal.exe

[TnT]

Latest problem . . . Now all I get is this:

[0.000011] DATETIME 2015-10-13T01:51:01Z (1444701061)
[0.000411] VERSION 0.5.0-devel (c72bdfe4e4175cb7ad2eb3dc4caa0e9fd9c12962)
[0.000784] ../../source/examples/universal.c:973: No matching device found.

That means you didn't use the correct options.

[KTwo]

Code: Select all

universal.exe -v -l atom2.log -m atom2.bin -b atom2 <COMx>

Replace <COMx> with the correct serial port (typically COM3).

I was executing this command figuring that it didn't match the required options/format for universal.exe figuring that it was leveraging hidden development options.

If that's not the case, I will go back and look at command formatting and figure out the correct command.

K2

[divinglog]

You have to use the command like that:

Code: Select all

universal.exe -v -l atom2.log -m atom2.bin -b atom2 COM3

[KTwo]

I guess I was a little unclear in my earlier response about my use of the universal.exe command. Yes, I was using it just like you typed it: "universal.exe -v -l atom2.log -m atom2.bin -b atom2 COM3"

But now I have another issue and that is intermittent functioning of the com port. Neither Tusa Datalogger or Diving Log 6.0 can see the com port. And the universal.exe command is back to not seeing COM3 either. So I need to fix that and get that to function reliably before going any further.

[KTwo]

Afterwards, email me the atom2.log and atom2.bin files.

Email sent.

Thanks for all your help.

-K2