Hi,
a friend of me diving with an Oceanic OCS recently started using subsurface to log her dives.
Unfortunately, it seems like the atom2 parser doesn't support tank switch events on Oceanic OCS yet.
We dumped all dives using the "universal test application". . In the xml sample at the time of the gas switch (at 21:45), there are two <vendor></vendor> elements generated, one starting with "AA", which looks like the gas switch event. The switch was done from air to EAN 52 (the 2nd mix):
<sample>
<time>21:45</time>
<vendor type="5" size="8">AA0221296A033400</vendor>
<vendor type="5" size="8">024E74039B000001</vendor>
<temperature>25.56</temperature>
<depth>16.84</depth>
</sample>
I attached the XML of this dive (sample from 21:45 starts at line 540) and the memory dump.
What about the "34" at the end meaning 52% oxygen in the newly switched gas? Do you have other samples to verify that this theory or should I ask about some more dives with gaschanges to mixes with other amounts of oxygen?
Florian
On 16-03-14 23:04, Florian Klink wrote:
a friend of me diving with an Oceanic OCS recently started using subsurface to log her dives.
Unfortunately, it seems like the atom2 parser doesn't support tank switch events on Oceanic OCS yet.
We dumped all dives using the "universal test application". . In the xml sample at the time of the gas switch (at 21:45), there are two <vendor></vendor> elements generated, one starting with "AA", which looks like the gas switch event. The switch was done from air to EAN 52 (the 2nd mix):
<sample>
<time>21:45</time> <vendor type="5" size="8">AA0221296A033400</vendor> <vendor type="5" size="8">024E74039B000001</vendor> <temperature>25.56</temperature> <depth>16.84</depth></sample>
I attached the XML of this dive (sample from 21:45 starts at line 540) and the memory dump.
What about the "34" at the end meaning 52% oxygen in the newly switched gas? Do you have other samples to verify that this theory or should I ask about some more dives with gaschanges to mixes with other amounts of oxygen?
The 0xAA sample indicates a tank switch (for models with support for multiple tank pressure sensors). But it's certainly possible that it can also contain a gas switch. Gas switches are indeed not parsed yet for the Oceanic devices. Is the OCS an air integrated model (hosed or wireless), because in that case a tank switch sample doesn't make much sense.
Can you provide a full memory dump (together with the logfile), rather just one dive. That's a bit easier to work with.
I think I do have some other data from an OCS, but I have no idea whether there are any gas changes or not. I'm a bit in a hurry right now, but I'll have a look later at what data I have available.
Jef
Am 17.03.2014 07:48, schrieb Jef Driesen:
On 16-03-14 23:04, Florian Klink wrote:
a friend of me diving with an Oceanic OCS recently started using subsurface to log her dives.
Unfortunately, it seems like the atom2 parser doesn't support tank switch events on Oceanic OCS yet.
We dumped all dives using the "universal test application". . In the xml sample at the time of the gas switch (at 21:45), there are two <vendor></vendor> elements generated, one starting with "AA", which looks like the gas switch event. The switch was done from air to EAN 52 (the 2nd mix):
<sample>
<time>21:45</time> <vendor type="5" size="8">AA0221296A033400</vendor> <vendor type="5" size="8">024E74039B000001</vendor> <temperature>25.56</temperature> <depth>16.84</depth></sample>
I attached the XML of this dive (sample from 21:45 starts at line 540) and the memory dump.
What about the "34" at the end meaning 52% oxygen in the newly switched gas? Do you have other samples to verify that this theory or should I ask about some more dives with gaschanges to mixes with other amounts of oxygen?
The 0xAA sample indicates a tank switch (for models with support for multiple tank pressure sensors). But it's certainly possible that it can also contain a gas switch. Gas switches are indeed not parsed yet for the Oceanic devices. Is the OCS an air integrated model (hosed or wireless), because in that case a tank switch sample doesn't make much sense.
The OCS does not have any air integration at all (wired/wireless). However, it's able to calculate saturation, deco etc. with up to 3 different gases (starting always with gas one). On this dive, a switch from gas 1 (air) to gas 2 (EAN52) was done at 21:45
Can you provide a full memory dump (together with the logfile), rather just one dive. That's a bit easier to work with.
I think I do have some other data from an OCS, but I have no idea whether there are any gas changes or not. I'm a bit in a hurry right now, but I'll have a look later at what data I have available.
I will ask if she also has some other dives with gas changes logged on this DC, but this will also take some time :-)
Florian
Am 17.03.2014 08:40, schrieb Florian Klink:
Am 17.03.2014 07:48, schrieb Jef Driesen:
On 16-03-14 23:04, Florian Klink wrote:
a friend of me diving with an Oceanic OCS recently started using subsurface to log her dives.
Unfortunately, it seems like the atom2 parser doesn't support tank switch events on Oceanic OCS yet.
We dumped all dives using the "universal test application". . In the xml sample at the time of the gas switch (at 21:45), there are two <vendor></vendor> elements generated, one starting with "AA", which looks like the gas switch event. The switch was done from air to EAN 52 (the 2nd mix):
<sample>
<time>21:45</time> <vendor type="5" size="8">AA0221296A033400</vendor> <vendor type="5" size="8">024E74039B000001</vendor> <temperature>25.56</temperature> <depth>16.84</depth></sample>
I attached the XML of this dive (sample from 21:45 starts at line 540) and the memory dump.
What about the "34" at the end meaning 52% oxygen in the newly switched gas? Do you have other samples to verify that this theory or should I ask about some more dives with gaschanges to mixes with other amounts of oxygen?
The 0xAA sample indicates a tank switch (for models with support for multiple tank pressure sensors). But it's certainly possible that it can also contain a gas switch. Gas switches are indeed not parsed yet for the Oceanic devices. Is the OCS an air integrated model (hosed or wireless), because in that case a tank switch sample doesn't make much sense.
The OCS does not have any air integration at all (wired/wireless). However, it's able to calculate saturation, deco etc. with up to 3 different gases (starting always with gas one). On this dive, a switch from gas 1 (air) to gas 2 (EAN52) was done at 21:45
Can you provide a full memory dump (together with the logfile), rather just one dive. That's a bit easier to work with.
I think I do have some other data from an OCS, but I have no idea whether there are any gas changes or not. I'm a bit in a hurry right now, but I'll have a look later at what data I have available.
I will ask if she also has some other dives with gas changes logged on this DC, but this will also take some time :-)
I attached two more dives to this mail. They include a Gas Change from EAN 50 to air. As guessed, the samples starting with "AA" have a "1500" at the end, meaning 21% o2
Florian
devel mailing list devel@libdivecomputer.org http://libdivecomputer.org/cgi-bin/mailman/listinfo/devel
On 2014-03-17 20:17, Florian Klink wrote:
I attached two more dives to this mail. They include a Gas Change from EAN 50 to air. As guessed, the samples starting with "AA" have a "1500" at the end, meaning 21% o2
To investigate I need a full memory dump, instead of the individual dives. My main debugging tool (e.g. the universal app) only works with full memory dumps, and I can't import individual dives in the Oceanic software either.
Can you run the universal application with these options:
./universal -v -l atom2.log -m atom2.bin -b atom2 <serialport>
And then send the atom2.log and atom2.bin files.
Jef
On 2014-03-17 08:40, Florian Klink wrote:
Am 17.03.2014 07:48, schrieb Jef Driesen:
The 0xAA sample indicates a tank switch (for models with support for multiple tank pressure sensors). But it's certainly possible that it can also contain a gas switch. Gas switches are indeed not parsed yet for the Oceanic devices. Is the OCS an air integrated model (hosed or wireless), because in that case a tank switch sample doesn't make much sense.
The OCS does not have any air integration at all (wired/wireless). However, it's able to calculate saturation, deco etc. with up to 3 different gases (starting always with gas one). On this dive, a switch from gas 1 (air) to gas 2 (EAN52) was done at 21:45
In that case the 0xAA might be combined tank and gas switch event, or just one of them depending on what the model supports. I wonder why I never looked at the gas switches. (To be honest, I probably do know. With all those slight data format changes for *every* single model, these Oceanic devices are a real pain in the ass.)
Can you provide a full memory dump (together with the logfile), rather just one dive. That's a bit easier to work with.
I think I do have some other data from an OCS, but I have no idea whether there are any gas changes or not. I'm a bit in a hurry right now, but I'll have a look later at what data I have available.
I will ask if she also has some other dives with gas changes logged on this DC, but this will also take some time :-)
I do have two other OCS memory dumps. If you want to investigate further, I can give you access to the git repository containing all the memory dumps. To do anything useful with these memory dumps, you'll have to setup the libdivecomputer simulator first:
http://www.libdivecomputer.org/simulator.html
Jef
Am 18.03.2014 16:34, schrieb Jef Driesen:
On 2014-03-17 08:40, Florian Klink wrote:
Am 17.03.2014 07:48, schrieb Jef Driesen:
The 0xAA sample indicates a tank switch (for models with support for multiple tank pressure sensors). But it's certainly possible that it can also contain a gas switch. Gas switches are indeed not parsed yet for the Oceanic devices. Is the OCS an air integrated model (hosed or wireless), because in that case a tank switch sample doesn't make much sense.
The OCS does not have any air integration at all (wired/wireless). However, it's able to calculate saturation, deco etc. with up to 3 different gases (starting always with gas one). On this dive, a switch from gas 1 (air) to gas 2 (EAN52) was done at 21:45
In that case the 0xAA might be combined tank and gas switch event, or just one of them depending on what the model supports. I wonder why I never looked at the gas switches. (To be honest, I probably do know. With all those slight data format changes for *every* single model, these Oceanic devices are a real pain in the ass.)
Can you provide a full memory dump (together with the logfile), rather just one dive. That's a bit easier to work with.
I think I do have some other data from an OCS, but I have no idea whether there are any gas changes or not. I'm a bit in a hurry right now, but I'll have a look later at what data I have available.
I will ask if she also has some other dives with gas changes logged on this DC, but this will also take some time :-)
I do have two other OCS memory dumps. If you want to investigate further, I can give you access to the git repository containing all the memory dumps. To do anything useful with these memory dumps, you'll have to setup the libdivecomputer simulator first:
I'd love to do that! Just tell me what you need (ssh pubkey or such), and I'll try to take a look at it :-)
Florian
-
Florian Klink -
Jef Driesen -
Jef Driesen