These look great!!! They match up perfectly with the first transmitter, which is always the primary transmitter (in this case, it's A0457 when viewing in Liquivisions Dive Log software)...
I know it's too much work for too few users, but it would be cool to be able to overlay the other transmitters in the distant future. But not really a big deal and prob. not worth it. Thanks a million, Tim On Sun, Mar 8, 2015 at 11:28 AM, Miika Turkia <[email protected]> wrote: > Can you verify if I got the pressure information from correct sensor? The > logic is based on luck, we treat the first pressure sensor reading to be > from diver's own cylinder... If you can check if the pressure readings are > taken from the correct DC in all of these sample dives, that might tell us > that the logic is not completely bogus... > > miika > > > On Thu, Mar 5, 2015 at 7:27 AM, Tim Thaler <[email protected]> wrote: > >> Hello, >> >> Attached is a smaller / older dive log file from my wife's >> profile that might be easier to work with than mine. Every dive should have >> two tank pressure readings. It will probably be helpful to have the >> Liquivision Dive Logger software to open this in and see how the buddy >> pressure works. And also note, sometimes the "buddies" pressure doesn't >> start till a few minutes into the dive as it doesn't have good range until >> both sonar transmitters are completely submerged (so you may have to click >> a minute into the dive to see both tank pressures). Let me know if I can be >> of any more help... I'de help with the code, but as a Java developer I >> would probably do more harm than good! >> >> Best Regards, >> Tim Thaler >> >> >> >> On Wed, Mar 4, 2015 at 11:16 PM, Miika Turkia <[email protected]> >> wrote: >> >>> I'll need a sample log to test the two pressures and to figure out how >>> it is represented and correct our import. I suppose, it'll be just one >>> sensor in the profile in the beginning, but who knows if both pressures >>> would be doable as well. >>> >>> miika >>> >>> On Thu, Mar 5, 2015 at 3:31 AM, Tim Thaler <[email protected]> wrote: >>> >>>> Hey Guys, >>>> >>>> Not sure if you want this in a new thread or not, but I just >>>> downloaded your software and imported my dives (about 50).... Anyways, I >>>> dive in "Buddy" mode, which means that I track both my air and my wifes air >>>> are logged. When it's imported into your software, it seems to log both our >>>> air on one solid line. This is virtually useless... Ideally, I could plot >>>> my wifes air over my air, but if that's too complex, it would be nice to be >>>> able to filter out her air, so that it's not combined with mine... Do you >>>> think this is possible to do? >>>> >>> >>> >>>> On Saturday, November 8, 2014 at 7:38:03 AM UTC-6, Henrik Brautaset >>>> Aronsen wrote: >>>> >>>>> On Sat, Nov 8, 2014 at 1:05 PM, Miika Turkia <[email protected]> >>>>> wrote: >>>>> >>>>>> Does the brand new LVD file import take care of the required Liquid >>>>>> Vision support? >>>>>> >>>>> >>>>> Yup, it takes care of the Liquivision (note the name) file format, >>>>> when exported from the companion Windows software. It does not import >>>>> directly from the computer, however. >>>>> >>>>> >>>>>> Does it add any value if CSV support was implemented as well? >>>>>> >>>>> >>>>> I don't think so. The CSV's I've seen so far have been via >>>>> Divinglog's export functionality. >>>>> >>>>> Henrik >>>>> >>>>> >>>> >>>> >>> >> >
_______________________________________________ subsurface mailing list [email protected] http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
