18579609 18579605 5374783 18579605 5636099 18645128 2 2012-01-24 18:30:00.327 2012-01-24 18:30:31.310 18579610 18841633 18841634 18841635 18841636 18841637 18841638 18841639 18841645 18841646 18841647 18841649 18841650 18841651 18841652 18841653 18841654 18841655 18579605 5374783 18579609 5374783 5636099 18645125 2 2012-01-24 18:28:16.080 2012-01-24 18:29:24.410 18579607 9798434 5374783 5374783 5636099 9831185 2 2009-05-12 08:01:48.193 2009-05-12 08:02:08.847 9798435 9928767 9928768 18186348 18186349 15630601 5374783 17236042 5374783 5636099 15663360 15697166 15697167 15697168 15697169 2 2010-12-30 16:14:17.607 2010-12-30 17:03:48.047 15630603 10356405 5374783 5374783 5636099 10389118 10461768 10461769 2 2009-10-05 14:13:08.307 2009-10-05 14:13:31.620 10356406 20971663 5374783 5374783 5636099 21004429 21170345 21170346 21170347 21170348 21170349 21170350 21170351 21170352 12 2013-04-22 14:11:36.310 2013-04-24 13:31:11.940 20971666 20971668 20971704 20971706 20971708 20971710 20971712 20971714 20971716 20971729 20971850 9798116 5374783 5374783 5636099 9830871 5 2009-05-03 11:40:55.807 2012-07-24 10:33:42.907 9798117 9798118 15631409 19040230 15728752 15728754 15728756 15728758 15728759 15728753 15728755 15728757 21528618 18579589 5374783 5374783 5636099 18645113 7 2012-01-24 13:07:29.183 2012-01-24 13:13:50.297 18579590 18579591 18579593 18579595 18579596 18579597 18841620 18841622 18841623 18841624 17236042 15630601 5374783 15630601 5636099 17268807 17302065 17302066 17302067 17302068 17302069 11 2011-06-01 08:20:43.727 2011-06-01 14:10:28.677 17236044 17236046 17236048 17236050 17236055 17236057 17236060 17236066 17236067 17236069 19040224 18252394 5374783 18252394 5636099 19072931 2 2012-07-24 10:04:09.983 2012-07-24 10:16:05.517 19040225 19040227 18252394 5374783 18252394 5636099 19072933 19159663 19159664 19159665 19159666 19159667 19159668 16 2012-07-24 10:25:33.017 2012-07-26 10:17:41.487 19040229 19040231 19040232 19040234 19040235 19040237 19040277 19040286 19040288 19040290 19040292 19040293 19040294 19040296 19040298 9928729 9928730 10485958 10485959 15728776 15728777 18186350 18186351 18186352 19169501 19169502 19169503 19169504 19169505 19169506 19169507 24018992 24018993 24018994 19169499 19169500 15631493 15631451 5374783 15631451 5636099 15664237 4 2011-02-10 14:22:55.020 2011-03-16 13:11:01.420 15631495 16416839 16416840 10356189 10356187 5374783 10356187 5636099 10388908 2 2009-09-15 08:15:36.937 2009-09-15 08:15:55.583 10356190 10485970 10485971 10485972 5636099 5374782 5374783 34406585 34406586 34406587 34406588 34406589 34406590 34406591 34406592 34406593 34406594 34406595 34406596 34406597 34406598 2008-07-11 18:09:02.707 2008-07-11 18:09:02.707 global 10356187 5374783 10356189 5374783 5636099 10388907 1 2009-09-15 08:14:58.213 2009-09-15 08:14:58.213 18579647 5374783 5374783 5636099 18645164 18776644 23 2012-01-25 15:53:11.910 2012-01-26 11:34:59.583 18579649 18579650 18579658 18579659 18579661 18579663 18579665 18579667 18579671 18579673 18579675 18579676 18579678 18579680 18579682 18579683 18579685 18579687 18579689 18579692 18579694 18579696 18841656 18841657 18841658 18841659 18841662 18841660 18841661 11240082 5374783 5374783 5636099 11272828 1 2010-02-25 08:27:12.690 2010-02-25 08:27:12.690 5701639 theme.key ]]> 18579747 5374783 5374783 5636099 18645262 6 2012-02-01 16:17:33.537 2012-02-02 11:05:09.153 18579748 18579755 18579756 18579758 18579759 18841663 18841664 18841665 18841666 18841667 18841668 18841669 15630460 5636099 15663223 15696641 15696642 15696643 15696644 15696645 15696646 15696647 15696648 15696649 15696650 15696651 15696652 15696653 15696654 15696655 15696656 15696657 12 2010-12-14 18:38:45.807 2010-12-15 13:53:01.227 15630463 15630467 15630469 15630471 15630472 15630478 15630480 15630482 15630484 15630499 15630502 15728668 15728669 11239985 5374783 5374783 5636099 11272734 11339649 11339650 11339651 11339652 11339653 11339654 11339655 3 2010-02-22 14:08:22.107 2010-02-22 14:34:12.143 11239987 11239989 21366097 5374783 5374783 5636099 21398800 2 2013-08-28 14:37:15.587 2013-08-28 14:37:40.807 21366098 21528646 21528647 21528648 21528649 21528650 21528651 21528652 21528653 21528654 21528655 21528656 21528657 21528658 21528659 21528660 21528661 21528662 21528663 21528664 21528665 21921795 21921796 21921797 21921798 15630458 5374783 5374783 5636099 15663222 15696458 3 2010-12-14 18:38:20.443 2010-12-15 09:40:13.023 15630461 15630466 15631663 15631451 5374783 15631451 5636099 15664402 3 2011-02-15 09:15:44.343 2011-02-15 09:19:05.793 15631664 15631665 15728772 15728773 5832857 5374783 5374783 5636099 5865618 5899727 5 2008-07-25 11:03:10.933 2008-07-25 16:47:40.667 5832859 5832861 5832863 5832886 5832865 5374783 5832872 5374783 5636099 5865626 5899715 4 2008-07-25 12:40:28.863 2008-07-25 14:15:02.457 5832869 5832870 5832874 15631451 5374783 15631493 15631663 5374783 5636099 15664201 12 2011-02-10 08:42:17.687 2011-09-27 14:10:52.357 15631452 15631453 15631457 15631459 15631486 15631489 18252344 18252350 18252352 18252353 18252355 15728761 15728762 15728763 15728764 15728765 15728766 15728774 15728775 5832872 5832865 5832878 5832882 5374783 5832865 5636099 5865633 5899723 5899724 5899725 5899726 3 2008-07-25 14:14:00.993 2008-07-25 15:50:34.247 5832884 5832885 5701640 2]]> 18252534 5374783 5374783 5636099 18285285 3 2011-10-31 11:06:34.957 2020-03-30 20:49:21.263 18252535 32407553 18186386 18186389 18186390 18186397 18186398 18186399 18186400 18186405 18186406 18186407 18186401 18186402 18186403 18186404 32374785 5701641 Rich false global ]]> 29196438 5374783 5374783 5636099 29229206 2 2016-09-08 14:01:01.607 2016-09-08 14:01:37.327 29196439 29392915 5832878 5832872 5374783 5832865 5832872 5636099 5865639 2 2008-07-25 15:42:25.023 2008-07-25 15:43:52.910 5832880 5374783 5374784 5832857 5832865 9798116 9798434 10356187 10356405 11239985 11240082 15630458 15630601 15631451 18252373 18252382 18252394 18252534 18579556 18579589 18579605 18579647 18579747 18579761 18579799 20971663 21366097 21790731 21790737 29196438 5636099 5407513 5 2008-07-11 18:09:02.717 2012-08-03 15:40:01.763 18579575 18579592 18579594 19040398 19169511 19169512 19169513 5374784 5374783 5374783 5636099 5407515 5509557 1 2008-07-11 18:21:16.457 2008-07-11 18:21:16.457 5832882 5832872 5374783 5832865 5832872 5636099 5865643 1 2008-07-25 15:47:52.560 2008-07-25 15:47:52.560 18252373 5374783 5374783 5636099 18285132 3 2011-09-30 22:00:51.843 2011-09-30 22:18:23.767 18252375 18252380 18186346 18252377 5636099 18285135 2 2011-09-30 22:12:15.623 2011-09-30 22:12:43.943 18252378 18186347 18252382 5374783 5374783 5636099 18285139 2 2011-10-05 13:34:33.407 2011-10-05 13:34:48.937 18252383 18186353 18186354 18579556 5374783 5374783 5636099 18645084 2 2012-01-23 10:46:15.013 2012-01-23 10:47:02.353 18579557 18841605 18841606 18841607 18841608 18841609 18841610 18841611 18841612 18841613 18841614 18841615 18841617 18841618 18841619 18841616 18579799 5374783 5374783 5636099 18645313 3 2012-02-03 13:01:11.797 2012-03-07 14:25:23.683 18579800 18580090 18841675 18841676 18841677 18841678 18841679 18841680 18841763 18252394 5374783 18252618 19040224 19040227 5374783 5636099 18285151 18353982 3 2011-10-06 12:12:04.233 2011-11-16 10:48:13.230 18252397 18252616 21790737 5374783 5374783 5636099 21823502 1 2013-08-29 13:45:10.437 2013-08-29 13:45:10.437 21790731 5374783 5374783 5636099 21823497 3 2013-08-29 11:33:00.300 2013-08-29 12:01:27.153 21790732 21790735 21921799 21921800 21921801 21921802 21921803 18252618 18252394 5374783 18252394 5636099 18285368 2 2011-11-16 11:08:40.337 2011-11-16 11:15:36.007 18252619 18186410 18186411 18579761 5374783 5374783 5636099 18645276 1 2012-02-02 11:08:04.487 2012-02-02 11:08:04.487 17302068 17236042 2011-06-01 14:10:28.950 2011-06-01 14:10:28.950 17302069 17236042 2011-06-01 14:10:28.950 2011-06-01 14:10:28.950 19159663 19040227 2012-07-26 10:17:41.500 2012-07-26 10:17:41.500 19159665 19040227 2012-07-26 10:17:41.500 2012-07-26 10:17:41.500 19159664 19040227 2012-07-26 10:17:41.500 2012-07-26 10:17:41.500 19159667 19040227 2012-07-26 10:17:41.500 2012-07-26 10:17:41.500 19159666 19040227 2012-07-26 10:17:41.500 2012-07-26 10:17:41.500 15630603 15663362 1 2010-12-30 16:14:17.607 2010-12-30 16:14:17.607 15630601 9928729 19040227 2009-05-03 11:41:28.470 2014-01-10 10:20:28.443 27839 19 9928730 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 133 1 9928729 21004429     AllowOverride None     Options \+ExecCGI     Order allow,deny     Allow from all \\ also added handler in same file... AddHandler wsgi-script .wsgi \\ restarted httpd then created a small test.wsgi file in /var/www/cgi-bin \[root@mbari1548-COS-vm cgi-bin\]# more test.wsgi def application(environ, start_response):     """Simplest possible application object"""     output = "Hello World"     status = '200 OK'     response_headers = \[('Content-type', 'text/plain'),                         ('Content-Length', str(len(output)))\]     start_response(status, response_headers)     return \[output\]   make it read and executable.. browse to http://134.89.11.51/cgi-bin/test.wsgi it works  ]]> 20971663 17302067 17236042 2011-06-01 14:10:28.950 2011-06-01 14:10:28.950 21170348 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 17302066 17236042 2011-06-01 14:10:28.950 2011-06-01 14:10:28.950 21170349 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 17302065 17236042 2011-06-01 14:10:28.950 2011-06-01 14:10:28.950 21170350 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 21170351 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 5374782 5636099 5407512 1 2008-07-11 18:09:02.707 2008-07-11 18:09:02.707 29523980 21170352 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 9928768 9798434 2009-05-12 08:02:08.840 2009-05-12 08:02:08.840 133 1 9928767 9928767 9798434 2009-05-12 08:02:08.840 2011-10-03 11:18:12.563 9673 4 21170345 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 21170346 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 21170347 20971663 2013-04-24 13:31:12.003 2013-04-24 13:31:12.003 21528651 21366097 2013-08-28 14:37:40.793 2013-08-28 15:32:52.740 20663 5 21528646 21528650 21366097 2013-08-28 14:37:40.793 2013-08-28 15:22:02.017 14577 4 21528646 21528653 21366097 2013-08-28 14:37:40.793 2013-08-28 15:43:27.957 20877 7 21528646 21528652 21366097 2013-08-28 14:37:40.793 2013-08-28 15:40:59.617 20639 6 21528646 21528647 21366097 2013-08-28 14:37:40.793 2013-08-28 14:37:40.793 133 1 21528646 21528646 21366097 2013-08-28 14:37:40.793 2013-08-29 11:37:29.333 27088 24 21528649 21366097 2013-08-28 14:37:40.793 2013-08-28 15:20:32.490 14279 3 21528646 21528648 21366097 2013-08-28 14:37:40.793 2013-08-28 14:48:15.737 5319 2 21528646 21528658 21366097 2013-08-28 14:37:40.793 2013-08-28 16:08:58.583 21565 12 21528646 21528659 21366097 2013-08-28 14:37:40.793 2013-08-28 16:15:57.667 23340 13 21528646 21528660 21366097 2013-08-28 14:37:40.793 2013-08-28 16:18:22.007 25167 14 21528646 9831185 9798434 21528661 21366097 2013-08-28 14:37:40.793 2013-08-28 16:22:26.280 25348 15 21528646 21528654 21366097 2013-08-28 14:37:40.793 2013-08-28 15:52:17.093 20877 8 21528646 21528655 21366097 2013-08-28 14:37:40.793 2013-08-28 15:55:31.007 20993 9 21528646 21528656 21366097 2013-08-28 14:37:40.793 2013-08-28 16:00:03.757 20898 10 21528646 21528657 21366097 2013-08-28 14:37:40.793 2013-08-28 16:05:41.027 20898 11 21528646 21528662 21366097 2013-08-28 14:37:40.793 2013-08-28 16:23:33.567 25369 16 21528646 15631665 15664404 2 2011-02-15 09:15:44.343 2011-02-15 09:16:04.083 15631663 21528663 21366097 2013-08-28 14:37:40.793 2013-08-28 16:31:58.770 26265 17 21528646 15631664 15664403 1 2011-02-15 09:15:44.343 2011-02-15 09:15:44.343 15631663 21528664 21366097 2013-08-28 14:37:40.793 2013-08-28 16:32:14.677 26265 18 21528646 21528665 21366097 2013-08-28 14:37:40.793 2013-08-28 16:38:35.347 26753 19 21528646 21921797 21366097 2013-08-28 14:37:40.793 2013-08-29 11:33:58.920 27088 22 21528646 21921796 21366097 2013-08-28 14:37:40.793 2013-08-29 11:33:56.673 27088 21 21528646 21921795 21366097 2013-08-28 14:37:40.793 2013-08-28 16:38:37.193 26753 20 21528646 15696641 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696642 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 21921803 21790731 2013-08-29 11:59:52.177 2013-08-29 12:39:17.143 127073 4 21921799 15696643 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 21921802 21790731 2013-08-29 11:59:52.177 2013-08-29 12:36:43.943 93651 3 21921799 21921801 21790731 2013-08-29 11:59:52.177 2013-08-29 12:01:58.277 27088 2 21921799 21921800 21790731 2013-08-29 11:59:52.177 2013-08-29 11:59:52.177 27088 1 21921799 21921799 21790731 2013-08-29 11:59:52.177 2013-08-29 12:40:24.933 126969 5 21921798 21366097 2013-08-28 14:37:40.793 2013-08-29 11:34:50.477 27088 23 21528646 15696649 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696648 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 5832863 5865624 3 2008-07-25 11:03:10.933 2008-07-25 12:27:05.973 5832857 15696651 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696650 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 5832861 5865622 2 2008-07-25 11:03:10.933 2008-07-25 12:24:33.377 5832857 15696645 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696644 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 5832859 5865620 1 2008-07-25 11:03:10.933 2008-07-25 11:03:10.933 5832857 15696647 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696646 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696657 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 5832874 5865635 3 2008-07-25 12:40:28.863 2008-07-25 14:13:23.617 5832865 15696656 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 5832869 5865630 1 2008-07-25 12:40:28.863 2008-07-25 12:40:28.863 5832865 15696653 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 5832870 5865631 2 2008-07-25 12:40:28.863 2008-07-25 13:22:07.880 5832865 15696652 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696655 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 15696654 15630460 2010-12-15 13:53:01.247 2010-12-15 13:53:01.247 18645262 a couple of times to get its attention.   2.    the login path diverges here depending on how the last user left it.                                              a.    if you are presented a command-line login prompt then log in as user = tiburon (pilots or Dan C have pswd)                                             b.    if previous user had left it logged in at a cmd line prompt, proceed to step '3'                                              c.    If its it was left logged in at the 'modern 'Graphical UI (red hats red background etc.) then use mouse to do a System>Log Off. And let it close the GUI and revert to the command-line interface. Then go back to (a) above and re-login as tiburon    3.    Type dk to kill any previously running datamanager.   4.    Select 'itchy' on the KVM, select it and hit a couple of times to get its attention.                                              a.    Log in as tiburon (same as steps 2a-c above)                                             b.    Type nk then to kill any previously running navproc or datamanager                                              c.    type 'ds' to restart datamanager (may take about 10 seconds to boot - and tell you it couldn't find a boot server, that's OK)                                             d.    type 'ns' to restart navproc   5.    Re-select 'scratchy' on the KVM                                              a.    type ds to start datamanager (should start almost immediately )                                             b.    (note there is no navproc to start on scratchy)   Data logging should start within and Dataprobe over on LAVA should go green two minutes. (It takes about two minutes for the watchdog tasks on scratchy to autostart the data logging. IF NOT, more serious problems are at play. There is a WesternFlyer/DocRicketts Data Logging Users Guide in a white binder above 'LAVA' you will need to start troubleshooting there.   \\ {gliffy:name=ItchyScratchyLava|space=Rich|page=Data Loging for non-ROV cruises|pageid=18579747|align=left|size=L}]]> 18579747 5832880 5865641 1 2008-07-25 15:42:25.023 2008-07-25 15:42:25.023 5832878 5832884 5865645 1 2008-07-25 14:14:00.993 2008-07-25 14:14:00.993 5832872 5832886 5865647 4 2008-07-25 11:03:10.933 2008-07-25 12:28:47.690 5832857 5832885 5865646 2 2008-07-25 14:14:00.993 2008-07-25 15:49:52.097 5832872 20971850 21004613 11 2013-04-22 14:11:36.310 2013-04-23 11:27:56.223 20971663 18645276 18579761 18580090 18645597 2 2012-02-03 13:01:11.797 2012-02-03 13:01:33.643 18579799 19159668 19040227 2012-07-26 10:17:41.500 2012-07-26 10:17:41.500 21528618 9798116 2013-07-18 10:23:54.250 2013-07-18 10:23:54.250 133 1 18645313 18579799 9798435 9831186 1 2009-05-12 08:01:48.193 2009-05-12 08:01:48.193 9798434 21823497 21790731 5509557 5374784 2008-07-11 18:21:16.507 2008-07-11 18:21:16.507 21823502 21790737 20971668 21004434 2 2013-04-22 14:11:36.310 2013-04-22 14:17:16.830 20971663 10356406 10389119 1 2009-10-05 14:13:08.307 2009-10-05 14:13:08.307 10356405 21398800 21366097 20971666 21004432 1 2013-04-22 14:11:36.310 2013-04-22 14:11:36.310 20971663 19040398 19073100 4 2008-07-11 18:09:02.717 2012-01-24 13:10:31.217 5374783 20971706 21004472 4 2013-04-22 14:11:36.310 2013-04-23 08:43:25.257 20971663 20971704 21004470 3 2013-04-22 14:11:36.310 2013-04-22 14:18:11.470 20971663 18645125 18579605 15631489 15664234 6 2011-02-10 08:42:17.687 2011-02-10 14:04:47.733 15631451 15631486 15664232 5 2011-02-10 08:42:17.687 2011-02-10 09:57:59.430 15631451 20971716 21004482 9 2013-04-22 14:11:36.310 2013-04-23 09:18:03.593 20971663 18645128 18579609 20971714 21004480 8 2013-04-22 14:11:36.310 2013-04-23 09:07:37.377 20971663 15631495 15664238 1 2011-02-10 14:22:55.020 2011-02-10 14:22:55.020 15631493 20971712 21004478 7 2013-04-22 14:11:36.310 2013-04-23 08:57:11.563 20971663 20971710 21004476 6 2013-04-22 14:11:36.310 2013-04-23 08:50:51.580 20971663 20971708 21004474 5 2013-04-22 14:11:36.310 2013-04-23 08:48:58.803 20971663 34406591 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 34406592 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 34406589 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 34406590 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 34406595 5636099 2026-02-04 08:49:33.271 2026-02-04 08:49:33.271 34406596 5636099 2026-02-04 08:49:33.271 2026-02-04 08:49:33.271 34406593 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 34406594 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 20971729 21004495 10 2013-04-22 14:11:36.310 2013-04-23 09:22:54.793 20971663 34406587 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 34406588 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 34406585 5636099 2026-02-04 08:49:18.859 2026-02-04 08:49:18.859 34406586 5636099 2026-02-04 08:49:33.270 2026-02-04 08:49:33.270 10461769 10356405 2009-10-05 14:13:31.647 2009-10-05 14:13:31.647 10461768 10356405 2009-10-05 14:13:31.647 2009-10-05 14:13:31.647 18645164 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... The post-rov-delivery changes to the system to meet MBARI requirements means both the MBARI and SMD software "design" is not clean. There is some data  duplication and some seemingly circular data pathways - hopefully they are correctly captured below... although about two years afte-the-fact. h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd. So commands from terminal>digi begin \*0100 and data from digi>terminal should begin \*0001... I think below was investigating how it was shipped by SMD: {panel} {color:#ff0000}THIS IS APPROXIMATE... NEEDS VERIFICATION.{color} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) (also assumes PR=238 ZS=0 ZV=0 ZL=0 from prior setup) {panel} h2. The Navproc Code on Itchy Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING (see below, extract from /usr/tiburon2/bin/navproc/coreNav.wf on itchy.) {panel}  serialPort  0,15  9600   8    1    None   CR/LF  # ROV Digiquartz Pressure In ... serialIn  ROV.DIGIQ.STRING        CHAR\[64\]  "%s\n"       No   0,15  None {panel} Navproc runs depthCalcTask() (see: /usr/tiburon2/src/navproc/calculateDepth.c) * consumes ROV.DIGIQ.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer.  6) ROV.MBARI.DEPTH is consumed by the navproc vorneTask and sent serially to the Vorne Display in the control room.  ]]> 18579647 34406598 5636099 2026-02-04 08:49:33.271 2026-02-04 08:49:33.271 34406597 5636099 2026-02-04 08:49:33.271 2026-02-04 08:49:33.271 15630472 15663235 5 2010-12-14 18:38:45.807 2010-12-15 10:30:27.537 15630460 15630471 15663234 4 2010-12-14 18:38:45.807 2010-12-15 10:27:09.857 15630460 15630467 15663230 2 2010-12-14 18:38:45.807 2010-12-15 08:16:30.997 15630460 15630469 15663232 3 2010-12-14 18:38:45.807 2010-12-15 09:40:13.050 15630460 18645084 18579556 15630463 15663226 1 2010-12-14 18:38:45.807 2010-12-14 18:38:45.807 15630460 15630466 15663229 2 2010-12-14 18:38:20.443 2010-12-14 18:39:53.823 15630458 15630461 15663224 1 2010-12-14 18:38:20.443 2010-12-14 18:38:20.443 15630458 15631409 15664160 3 2009-05-03 11:40:55.807 2009-05-03 11:46:49.620 9798116 21366098 21398801 1 2013-08-28 14:37:15.587 2013-08-28 14:37:15.587 21366097 11239989 11272738 2 2010-02-22 14:08:22.107 2010-02-22 14:30:50.903 11239985 19040235 19072941 5 2012-07-24 10:25:33.017 2012-07-24 11:30:48.790 19040227 11239987 11272736 1 2010-02-22 14:08:22.107 2010-02-22 14:08:22.107 11239985 19040237 19072943 6 2012-07-24 10:25:33.017 2012-07-24 11:31:08.793 19040227 19040298 19073003 15 2012-07-24 10:25:33.017 2012-07-26 10:16:09.510 19040227 19040296 19073001 14 2012-07-24 10:25:33.017 2012-07-26 10:14:56.857 19040227 15630502 15663265 11 2010-12-14 18:38:45.807 2010-12-15 13:49:42.220 15630460 10389118 10356405 19040294 19072999 13 2012-07-24 10:25:33.017 2012-07-26 10:14:10.997 19040227 19040293 19072998 12 2012-07-24 10:25:33.017 2012-07-26 10:13:23.927 19040227 19040292 19072997 11 2012-07-24 10:25:33.017 2012-07-26 10:07:04.557 19040227 15630499 15663262 10 2010-12-14 18:38:45.807 2010-12-15 13:26:11.057 15630460 19040290 19072995 10 2012-07-24 10:25:33.017 2012-07-26 09:15:38.717 19040227 18645113 18579589 19040288 19072993 9 2012-07-24 10:25:33.017 2012-07-26 09:11:59.740 19040227 19040286 19072991 8 2012-07-24 10:25:33.017 2012-07-25 20:03:49.007 19040227 15631459 15664209 4 2011-02-10 08:42:17.687 2011-02-10 09:56:10.957 15631451 19040277 19072982 7 2012-07-24 10:25:33.017 2012-07-24 11:36:10.720 19040227 19072931 19040224 15630484 15663247 9 2010-12-14 18:38:45.807 2010-12-15 13:16:30.577 15630460 19072933 19040227 15631453 15664203 2 2011-02-10 08:42:17.687 2011-02-10 08:42:34.823 15631451 15630482 15663245 8 2010-12-14 18:38:45.807 2010-12-15 12:54:08.423 15630460 15631452 15664202 1 2011-02-10 08:42:17.687 2011-02-10 08:42:17.687 15631451 15630480 15663243 7 2010-12-14 18:38:45.807 2010-12-15 12:48:39.813 15630460 15631457 15664207 3 2011-02-10 08:42:17.687 2011-02-10 08:43:00.477 15631451 15630478 15663241 6 2010-12-14 18:38:45.807 2010-12-15 10:31:06.880 15630460 15696458 15630458 2010-12-15 09:40:13.043 2010-12-15 09:40:13.043 29392915 29196438 2016-09-08 14:01:37.327 2016-09-08 14:01:37.327 133 1 11339649 11239985 2010-02-22 14:34:12.170 2010-02-22 14:34:12.170 17236044 17268809 1 2011-06-01 08:20:43.727 2011-06-01 08:20:43.727 17236042 18579610 18645129 1 2012-01-24 18:30:00.327 2012-01-24 18:30:00.327 18579609 11339650 11239985 2010-02-22 14:34:12.170 2010-02-22 14:34:12.170 18579607 18645127 1 2012-01-24 18:28:16.080 2012-01-24 18:28:16.080 18579605 17236046 17268811 2 2011-06-01 08:20:43.727 2011-06-01 09:15:33.240 17236042 11339651 11239985 2010-02-22 14:34:12.170 2010-02-22 14:34:12.170 17236048 17268813 3 2011-06-01 08:20:43.727 2011-06-01 09:20:38.053 17236042 17236050 17268815 4 2011-06-01 08:20:43.727 2011-06-01 09:23:26.890 17236042 17236055 17268820 5 2011-06-01 08:20:43.727 2011-06-01 10:06:48.300 17236042 18579597 18645121 6 2012-01-24 13:07:29.183 2012-01-24 13:13:41.567 18579589 17236057 17268822 6 2011-06-01 08:20:43.727 2011-06-01 10:58:32.807 17236042 18579595 18645119 4 2012-01-24 13:07:29.183 2012-01-24 13:10:15.793 18579589 18579596 18645120 5 2012-01-24 13:07:29.183 2012-01-24 13:12:41.137 18579589 17236060 17268825 7 2011-06-01 08:20:43.727 2011-06-01 11:06:39.520 17236042 15664201 15631451 17236066 17268831 8 2011-06-01 08:20:43.727 2011-06-01 11:33:44.317 17236042 17236067 17268832 9 2011-06-01 08:20:43.727 2011-06-01 14:05:23.967 17236042 17236069 17268834 10 2011-06-01 08:20:43.727 2011-06-01 14:06:00.910 17236042 11339653 11239985 2010-02-22 14:34:12.170 2010-02-22 14:34:12.170 11339652 11239985 2010-02-22 14:34:12.170 2010-02-22 14:34:12.170 11339655 11239985 2010-02-22 14:34:12.170 2010-02-22 14:34:12.170 11339654 11239985 2010-02-22 14:34:12.170 2010-02-22 14:34:12.170 18579575 18645102 1 2008-07-11 18:09:02.717 2008-07-11 18:09:02.717 5374783 15728774 15631451 2011-02-10 08:43:00.457 2011-02-10 09:35:22.083 7627 6 15728761 15728775 15631451 2011-02-10 08:43:00.457 2011-02-15 09:19:56.330 7627 7 15728761 15728776 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 2363 4 9928729 15728777 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 13282 5 9928729 9830871 9798116 15728766 15631451 2011-02-10 08:43:00.457 2011-02-10 09:15:55.627 7308 5 15728761 18252397 18285153 1 2011-10-06 12:12:04.233 2011-10-06 12:12:04.233 18252394 15728772 15631663 2011-02-15 09:16:04.057 2011-02-15 09:16:49.130 176 2 15728773 15631663 2011-02-15 09:16:04.057 2011-02-15 09:16:04.057 133 1 15728772 18579592 18645116 2 2008-07-11 18:09:02.717 2012-01-24 12:33:39.883 5374783 18579591 18645115 2 2012-01-24 13:07:29.183 2012-01-24 13:07:37.597 18579589 18579594 18645118 3 2008-07-11 18:09:02.717 2012-01-24 13:09:13.713 5374783 18579593 18645117 3 2012-01-24 13:07:29.183 2012-01-24 13:08:47.583 18579589 18285285 18252534 18579590 18645114 1 2012-01-24 13:07:29.183 2012-01-24 13:07:29.183 18579589 15664237 15631493 18579667 18645183 8 2012-01-25 15:53:11.910 2012-01-25 17:15:21.827 18579647 18579673 18645189 10 2012-01-25 15:53:11.910 2012-01-25 20:51:56.767 18579647 18579671 18645187 9 2012-01-25 15:53:11.910 2012-01-25 17:23:10.353 18579647 18579661 18645177 5 2012-01-25 15:53:11.910 2012-01-25 17:01:06.107 18579647 18579659 18645175 4 2012-01-25 15:53:11.910 2012-01-25 16:59:18.307 18579647 18579665 18645181 7 2012-01-25 15:53:11.910 2012-01-25 17:11:04.227 18579647 18579663 18645179 6 2012-01-25 15:53:11.910 2012-01-25 17:09:31.000 18579647 18579685 18645201 17 2012-01-25 15:53:11.910 2012-01-25 22:53:57.697 18579647 32407553 32440321 2 2011-10-31 11:06:34.957 2011-10-31 11:06:58.793 18252534 19040225 19072932 1 2012-07-24 10:04:09.983 2012-07-24 10:04:09.983 19040224 18579683 18645199 16 2012-01-25 15:53:11.910 2012-01-25 22:53:36.430 18579647 18579689 18645205 19 2012-01-25 15:53:11.910 2012-01-25 23:01:06.297 18579647 18579687 18645203 18 2012-01-25 15:53:11.910 2012-01-25 23:00:20.797 18579647 18579678 18645194 13 2012-01-25 15:53:11.910 2012-01-25 21:15:03.860 18579647 19040231 19072937 2 2012-07-24 10:25:33.017 2012-07-24 10:29:41.760 19040227 19040232 19072938 3 2012-07-24 10:25:33.017 2012-07-24 10:35:14.203 19040227 18579676 18645192 12 2012-01-25 15:53:11.910 2012-01-25 21:10:46.010 18579647 18579675 18645191 11 2012-01-25 15:53:11.910 2012-01-25 21:04:56.497 18579647 19040234 19072940 4 2012-07-24 10:25:33.017 2012-07-24 10:36:23.090 19040227 18579682 18645198 15 2012-01-25 15:53:11.910 2012-01-25 22:27:40.460 18579647 19040229 19072935 1 2012-07-24 10:25:33.017 2012-07-24 10:25:33.017 19040227 18579680 18645196 14 2012-01-25 15:53:11.910 2012-01-25 21:27:23.937 18579647 19040230 19072936 4 2009-05-03 11:40:55.807 2011-02-06 10:55:59.707 9798116 10356190 10388909 1 2009-09-15 08:15:36.937 2009-09-15 08:15:36.937 10356189 15663223 15630460 15663222 15630458 32374785 18252534 2020-03-30 20:49:21.247 2020-03-30 20:49:21.247 133 1 18579658 18645174 3 2012-01-25 15:53:11.910 2012-01-25 15:55:44.207 18579647 18579650 18645167 2 2012-01-25 15:53:11.910 2012-01-25 15:55:14.557 18579647 18579649 18645166 1 2012-01-25 15:53:11.910 2012-01-25 15:53:11.910 18579647 18285151 18252394 18285139 18252382 18776644 18579647 2012-01-26 11:34:59.620 2012-01-26 11:34:59.620 18285135 18252377 18285132 18252373 15728668 15630460 2010-12-15 08:41:05.127 2010-12-15 08:41:05.127 54681 1 15728669 15630460 2010-12-15 08:42:03.583 2010-12-15 08:42:03.583 36486 1 19169507 19040227 2009-05-03 11:41:28.470 2012-07-24 11:19:21.283 26416 15 9928729 19169506 19040227 2009-05-03 11:41:28.470 2012-07-24 11:17:08.973 26559 14 9928729 19169503 19040227 2009-05-03 11:41:28.470 2012-07-24 10:41:01.113 20409 11 9928729 5865639 <\!-\- Example Server Configuration File \--> <\!-\- Note that component elements are nested corresponding to their parent-child relationships with each other \--> <\!-\- A "Server" is a singleton element that represents the entire JVM, which may contain one or more "Service" instances. The Server listens for a shutdown command on the indicated port. Note: A "Server" is not itself a "Container", so you may not define subcomponents such as "Valves" or "Loggers" at this level. \--> <\!-\- Comment these entries out to disable JMX MBeans support used for the administration web application \--> <\!-\- Global JNDI resources \--> <\!-\- Test entry for demonstration purposes \--> <\!-\- Editable user database that can also be used by UserDatabaseRealm to authenticate users \--> <\!-\- A "Service" is a collection of one or more "Connectors" that share a single "Container" (and therefore the web applications visible within that Container). Normally, that Container is an "Engine", but this is not required. Note: A "Service" is not itself a "Container", so you may not define subcomponents such as "Valves" or "Loggers" at this level. \--> <\!-\- Define the Tomcat Stand-Alone Service \--> <\!-\- A "Connector" represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated "Container" (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 5 documentation bundle for more detailed instructions): * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or later, and put the JAR files into "$JAVA_HOME/jre/lib/ext". * Execute: %JAVA_HOME%\bin\keytool \-genkey \-alias tomcat \-keyalg RSA (Windows) $JAVA_HOME/bin/keytool \-genkey \-alias tomcat \-keyalg RSA (Unix) with a password value of "changeit" for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the "enableLookups" attribute to "false". When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. \--> <\!-\- rschramm, change from default 8080 to 8085 12-Apr-2007 \--> <\!-\- Define a non-SSL HTTP/1.1 Connector on port 8080 \--> <\!-\- Note : To disable connection timeouts, set connectionTimeout value to 0 \--> <\!-\- Note : To use gzip compression you could set the following properties : compression="on" compressionMinSize="2048" noCompressionUserAgents="gozilla, traviata" compressableMimeType="text/html,text/xml" \--> <\!-\- Define a SSL HTTP/1.1 Connector on port 8443 \--> <\!-\- \--> <\!-\- Define an AJP 1.3 Connector on port 8009 \--> <\!-\- Define a Proxied HTTP/1.1 Connector on port 8082 \--> <\!-\- See proxy documentation for more information about using this. \--> <\!-\- \--> <\!-\- An Engine represents the entry point (within Catalina) that processes every request. The Engine implementation for Tomcat stand alone analyzes the HTTP headers included with the request, and passes them on to the appropriate Host (virtual host). \--> <\!-\- You should set jvmRoute to support load-balancing via AJP ie : \--> <\!-\- Define the top level container in our container hierarchy \--> <\!-\- The request dumper valve dumps useful debugging information about the request headers and cookies that were received, and the response headers and cookies that were sent, for all requests received by this instance of Tomcat. If you care only about requests to a particular virtual host, or a particular application, nest this element inside the corresponding or entry instead. For a similar mechanism that is portable to all Servlet 2.4 containers, check out the "RequestDumperFilter" Filter in the example application (the source for this filter may be found in "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters"). Request dumping is disabled by default. Uncomment the following element to enable it. \--> <\!-\- \--> <\!-\- Because this Realm is here, an instance will be shared globally \--> <\!-\- This Realm uses the UserDatabase configured in the global JNDI resources under the key "UserDatabase". Any edits that are performed against this UserDatabase are immediately available for use by the Realm. \--> <\!-\- Comment out the old realm but leave here for now in case we need to go back quickly \--> <\!-\- \--> <\!-\- Replace the above Realm with one of the following to get a Realm stored in a database and accessed via JDBC \--> <\!-\- \--> <\!-\- \--> <\!-\- \--> <\!-\- Define the default virtual host Note: XML Schema validation will not work with Xerces 2.2. \--> <\!-\- Defines a cluster for this node, By defining this element, means that every manager will be changed. So when running a cluster, only make sure that you have webapps in there that need to be clustered and remove the other ones. A cluster has the following parameters: className = the fully qualified name of the cluster class name = a descriptive name for your cluster, can be anything mcastAddr = the multicast address, has to be the same for all the nodes mcastPort = the multicast port, has to be the same for all the nodes mcastBindAddr = bind the multicast socket to a specific address mcastTTL = the multicast TTL if you want to limit your broadcast mcastSoTimeout = the multicast readtimeout mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes tcpListenAddress = the listen address (bind address) for TCP cluster request on this host, in case of multiple ethernet cards. auto means that address becomes InetAddress.getLocalHost().getHostAddress() tcpListenPort = the tcp listen port tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS has a wakup bug in java.nio. Set to 0 for no timeout printToScreen = true means that managers will also print to std.out expireSessionsOnShutdown = true means that useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called. false means to replicate the session after each request. false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager) <% HashMap map = (HashMap)session.getAttribute("map"); map.put("key","value"); %> replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'. * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication. * Synchronous means that the thread that executes the request, is also the thread the replicates the data to the other nodes, and will not return until all nodes have received the information. * Asynchronous means that there is a specific 'sender' thread for each cluster node, so the request thread will queue the replication request into a "smart" queue, and then return to the client. The "smart" queue is a queue where when a session is added to the queue, and the same session already exists in the queue from a previous request, that session will be replaced in the queue instead of replicating two requests. This almost never happens, unless there is a large network delay. \--> <\!-\- When configuring for clustering, you also add in a valve to catch all the requests coming in, at the end of the request, the session may or may not be replicated. A session is replicated if and only if all the conditions are met: 1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND 2. a session exists (has been created) 3. the request is not trapped by the "filter" attribute The filter attribute is to filter out requests that could not modify the session, hence we don't replicate the session after the end of this request. The filter is negative, ie, anything you put in the filter, you mean to filter out, ie, no replication will be done on requests that match one of the filters. The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to. filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI ending with .gif and .js are intercepted. The deployer element can be used to deploy apps cluster wide. Currently the deployment only deploys/undeploys to working members in the cluster so no WARs are copied upons startup of a broken node. The deployer watches a directory (watchDir) for WAR files when watchEnabled="true" When a new war file is added the war gets deployed to the local instance, and then deployed to the other instances in the cluster. When a war file is deleted from the watchDir the war is undeployed locally and cluster wide \--> <\!-\- \--> <\!-\- Normally, users must authenticate themselves to each web app individually. Uncomment the following entry if you would like a user to be authenticated the first time they encounter a resource protected by a security constraint, and then have that user identity maintained across *all* web applications contained in this virtual host. \--> <\!-\- \--> <\!-\- Access log processes all requests for this virtual host. By default, log files are created in the "logs" directory relative to $CATALINA_HOME. If you wish, you can specify a different directory with the "directory" attribute. Specify either a relative (to $CATALINA_HOME) or absolute path to the desired directory. \--> <\!-\- \--> <\!-\- Access log processes all requests for this virtual host. By default, log files are created in the "logs" directory relative to $CATALINA_HOME. If you wish, you can specify a different directory with the "directory" attribute. Specify either a relative (to $CATALINA_HOME) or absolute path to the desired directory. This access log implementation is optimized for maximum performance, but is hardcoded to support only the "common" and "combined" patterns. \--> <\!-\- \--> ]]> 5832878 19169502 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.280 19664 10 9928729 19169505 19040227 2009-05-03 11:41:28.470 2012-07-24 11:14:50.710 26041 13 9928729 19169504 19040227 2009-05-03 11:41:28.470 2012-07-24 11:12:48.760 25709 12 9928729 5865643 RovctdDataServlet org.mbari.rovctd.datagenerators.RovctdDataServlet deployedDate 15-Aug-2006 jdbcDriver net.sourceforge.jtds.jdbc.Driver RovctdDataServlet /servlet/RovctdDataServlet Resource reference to a factory for java.sql.Connection instances that may be used for talking to a particular database that is configured in the server.xml file. jdbc/ROVCTD javax.sql.DataSource Container ]]> 5832882 19169511 5374783 2012-08-03 15:40:01.737 2012-08-03 15:46:52.357 5364 3 18252375 18285134 1 2011-09-30 22:00:51.843 2011-09-30 22:00:51.843 18252373 18252378 18285136 1 2011-09-30 22:12:15.623 2011-09-30 22:12:15.623 18252377 19169513 5374783 2012-08-03 15:40:01.737 2012-08-03 15:46:48.087 5364 2 19169511 19169512 5374783 2012-08-03 15:40:01.737 2012-08-03 15:40:01.737 133 1 19169511 15728756 9798116 2011-02-06 10:55:59.673 2011-02-06 12:03:46.407 3592 2 15728752 18252380 18285138 2 2011-09-30 22:00:51.843 2011-09-30 22:08:34.377 18252373 15728757 9798116 2011-02-06 12:29:28.167 2011-02-06 12:29:28.167 2880 1 15697167 15630601 2010-12-30 17:03:48.353 2010-12-30 17:03:48.353 15728754 9798116 2011-02-06 10:55:59.673 2011-02-06 10:55:59.673 133 1 15728752 15697166 15630601 2010-12-30 17:03:48.353 2010-12-30 17:03:48.353 15728755 9798116 2011-02-06 12:04:26.417 2011-02-06 12:04:26.417 53401 1 18252383 18285140 1 2011-10-05 13:34:33.407 2011-10-05 13:34:33.407 18252382 15697169 15630601 2010-12-30 17:03:48.353 2010-12-30 17:03:48.353 15728752 9798116 2011-02-06 10:55:59.673 2011-02-06 12:47:51.510 6552 5 15697168 15630601 2010-12-30 17:03:48.353 2010-12-30 17:03:48.353 15728753 9798116 2011-02-06 12:02:31.003 2011-02-06 12:02:31.003 65834 1 18579557 18645085 1 2012-01-23 10:46:15.013 2012-01-23 10:46:15.013 18579556 15728764 15631451 2011-02-10 08:43:00.457 2011-02-10 09:11:19.487 7290 3 15728761 15728765 15631451 2011-02-10 08:43:00.457 2011-02-10 09:15:52.257 7308 4 15728761 15728762 15631451 2011-02-10 08:43:00.457 2011-02-10 08:43:00.457 133 1 15728761 15728763 15631451 2011-02-10 08:43:00.457 2011-02-10 08:52:59.030 6789 2 15728761 15728761 15631451 2011-02-10 08:43:00.457 2011-02-15 09:20:03.537 7627 8 15728758 9798116 2011-02-06 10:55:59.673 2011-02-06 12:17:47.587 3920 3 15728752 15728759 9798116 2011-02-06 10:55:59.673 2011-02-06 12:45:43.510 6553 4 15728752 16416840 16449604 3 2011-02-10 14:22:55.020 2011-03-16 13:10:35.087 15631493 16416839 16449603 2 2011-02-10 14:22:55.020 2011-02-10 14:24:02.127 15631493 15663360 1.5.5) commons.dbcp (1.2.1 > 1.4) commons.logging (1.1.1) commons-collections (3.2 > 3.2.1) All of the above, basically download the binary distributions, unzip somewhere, then drag the .jar file to c:/Program Files/Apache Software Foundation/Tomcat 7.0/lib\\ h4. Get jFreeChart  download distribution of jFreeChart (1.0.2 > 1.0.13) get the jfreechart-1.0.13.jar and jcommon-1.0.16.jar that is with it and drag to  c:/Program Files/Apache Software Foundation/Tomcat 7.0/lib h4. Get the old rovctd webapps folder from anvils tomcat 5.5 and drop it into my tomcat 7.0 webapps dir h4. Checkout RovctdPlots from cvs to C:\Projects edit all applications.java to point to localhost 8080 or....anvil or typhoon edit build.xml\\ configure server.xml etc according to database inst. here and elsewhere... need the jtds add, also note that is where the connection is set to either solstice or other...\\  Restart tomcat.... I often had to start twice after stoppin, it throws error when stopping, then have to start twice, once with error. Fist time after startup, takes a long time to runt the app.\\ Able to do ant clean prepare compile deploy.libs deploy.datagenerators deploy.plots run.1 thru 5\\ Stopped for today... doesnt run over browser. I get errors  http://134.89.11.41:8080/rovctd/pages/stackedtimeseries.jsp?platform=vnta&dive=3596&domain=epochsecs&noHTMLHeader=0&r1=p&r2=t&r3=s&r4=light&r5=o2\\ org.apache.jasper.JasperException: /pages/stackedtimeseries.jsp(24,49) Attribute value request.getParameter("platform") is quoted with " which must be escaped when used within the value org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:40) org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:407) org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:88) org.apache.jasper.compiler.Parser.parseAttributeValue(Parser.java:280) \\ \\ \\ \\]]> 15630601 5865618 5832857 18252344 18285102 7 2011-02-10 08:42:17.687 2011-02-10 14:20:46.110 15631451 18252350 18285108 8 2011-02-10 08:42:17.687 2011-09-26 14:20:32.750 15631451 5865626 f(clean);\- <\!-\- Define a non-SSL HTTP/1.1 Connector on port 8080   \-->f(clean);   [FOR DATABASE SETUP SEE THIS|Rich:database setup]]]> 5832865 18252353 18285111 10 2011-02-10 08:42:17.687 2011-09-27 14:05:00.580 15631451 18252352 18285110 9 2011-02-10 08:42:17.687 2011-09-27 14:02:17.237 15631451 19169500 19040227 2012-07-24 10:29:41.737 2012-07-24 10:29:41.737 133 1 19169499 19169501 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.280 19661 9 9928729 24018994 19040227 2009-05-03 11:41:28.470 2014-01-10 10:20:25.557 27839 18 9928729 18252355 18285113 11 2011-02-10 08:42:17.687 2011-09-27 14:05:39.383 15631451 19169499 19040227 2012-07-24 10:29:41.737 2012-07-24 10:29:56.667 176 2 24018992 19040227 2009-05-03 11:41:28.470 2012-07-24 11:23:34.757 26416 16 9928729 24018993 19040227 2009-05-03 11:41:28.470 2014-01-10 10:19:07.470 27464 17 9928729 5865633 tag of the examples context and the tag closing the localhost definition.   3) Add the following snippet to your applications WEB-INF/web.xml file. You should ensure that you respect the element ordering defined by the DTD when you create you applications web.xml file.     Resource reference to a factory for java.sql.Connection     instances that may be used for talking to a particular     database that is configured in the server.xml file. jdbc/ROVCTD javax.sql.DataSource Container 4) make sure jTds driver file is in C:\Program Files\Apache Software Foundation\Tomcat 5.5\common\lib (also might need it in C:\Program Files\Apache Software Foundation\Tomcat 5.5\shared\lib but when I was test deploying to anvil it was needed in common) 5) Fetching the connection will be done by: Context initContext = new InitialContext(); Context envContext  = (Context)initContext.lookup("java:/comp/env"); DataSource ds = (DataSource)envContext.lookup("jdbc/ROVCTD"); Connection conn = ds.getConnection(); {color:#ff0000}{*}{_}LOOK AT THESE EXAMPLES FOR{_}{*}{color} [conf\server.xml|Rich:Tomcat 5.5 server.xml on anvil] and [web.xml|Rich:web.xml on anvil]\\ \\ ; ]]> 5832872 17268807               {panel} h2. Install jFreeChart and a bunch of other jar files: jfreechart-1.0.13.jar (from tempbox/rich/downloads) jcommon-1.0.16.jar jFastCGI-2.0.jar commons-logging-1.1.1.jar commons-pool-1.5.5.jar commons-collections-3.2.1.jar commons-dbcp-1.4.jar jtds-1.2.5.jar h2. Install the webapps # rovctd ## grab  rovctd folder from tempbox\rich\downloads put in C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps # jitensha-rougu (Brian Schlining's...)  ANVIL ONLY, NOT TYPHOON? ## copy Tomcat 5.5\webapps\jitensha-rogu.war to Tomcat 7.0\webapps ## restart tomcat service (should create cause tomcat to create webapps\jitensh-rogu folder and sub-folders) # any other webapps...besides defaults? (manager and ROOT) \\]]> 17236042 18841678 18579799 2012-02-03 13:01:33.630 2012-02-03 13:52:09.870 4760 3 18841675 10485972 10356189 2009-09-15 08:15:55.573 2009-09-15 08:44:16.780 10964 2 10485970 18841679 18579799 2012-02-03 13:01:33.630 2012-02-03 14:19:09.513 8778 4 18841675 18841680 18579799 2012-02-03 13:01:33.630 2012-02-03 14:21:43.790 9234 5 18841675 10485970 10356189 2009-09-15 08:15:55.573 2009-09-15 09:12:58.090 12343 3 10485971 10356189 2009-09-15 08:15:55.573 2009-09-15 08:15:55.573 133 1 10485970 18841667 18579747 2012-02-01 16:30:18.980 2012-02-01 16:38:10.923 1472 4 18841663 18841666 18579747 2012-02-01 16:30:18.980 2012-02-01 16:35:53.007 2646 3 18841663 18841669 18579747 2012-02-02 11:01:18.850 2012-02-02 11:01:18.850 227328 1 18841668 18579747 2012-02-01 16:30:18.980 2012-02-01 16:48:00.547 8177 5 18841663 9798117 9830872 1 2009-05-03 11:40:55.807 2009-05-03 11:40:55.807 9798116 18841663 18579747 2012-02-01 16:30:18.980 2012-02-01 16:51:01.727 10157 6 9798118 9830873 2 2009-05-03 11:40:55.807 2009-05-03 11:41:28.470 9798116 18841662 18579647 2012-01-25 15:55:44.197 2012-01-25 16:44:45.087 18493 4 18841656 18841665 18579747 2012-02-01 16:30:18.980 2012-02-01 16:35:49.763 2646 2 18841663 18841664 18579747 2012-02-01 16:30:18.980 2012-02-01 16:30:18.980 133 1 18841663 18841675 18579799 2012-02-03 13:01:33.630 2012-03-07 14:26:03.963 8658 7 18841677 18579799 2012-02-03 13:01:33.630 2012-02-03 13:29:02.507 2118 2 18841675 10485959 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 2363 3 9928729 18841676 18579799 2012-02-03 13:01:33.630 2012-02-03 13:01:33.630 133 1 18841675 10485958 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 3518 2 9928729 18841649 18579609 2012-01-24 18:30:31.307 2012-01-25 09:35:49.840 17017 10 18841633 18841646 18579609 2012-01-24 18:30:31.307 2012-01-25 09:33:55.253 17017 8 18841633 18841647 18579609 2012-01-24 18:30:31.307 2012-01-25 09:34:22.010 17017 9 18841633 18841652 18579609 2012-01-24 18:30:31.307 2012-01-25 11:19:56.287 21044 13 18841633 18841653 18579609 2012-01-24 18:30:31.307 2012-01-25 11:20:43.230 21420 14 18841633 18186389 18252534 2011-10-31 11:06:58.783 2011-10-31 11:06:58.783 133 1 18186386 18841650 18579609 2012-01-24 18:30:31.307 2012-01-25 11:02:44.187 20220 11 18841633 18186386 18252534 2011-10-31 11:06:58.783 2011-10-31 14:47:46.380 19849 10 18841651 18579609 2012-01-24 18:30:31.307 2012-01-25 11:12:24.677 20606 12 18841633 18841656 18579647 2012-01-25 15:55:44.197 2012-01-25 23:02:20.717 18498 5 18841657 18579647 2012-01-25 15:55:44.197 2012-01-25 15:55:44.197 133 1 18841656 18841654 18579609 2012-01-24 18:30:31.307 2012-01-25 11:21:13.677 21420 15 18841633 18186390 18252534 2011-10-31 11:06:58.783 2011-10-31 11:42:16.030 14590 2 18186386 18841655 18579609 2012-01-24 18:30:31.307 2012-01-25 11:23:02.990 22653 16 18841633 18841660 18579647 2012-01-25 17:06:53.130 2012-01-25 17:06:53.130 430159 1 18841661 18579647 2012-01-25 17:07:04.070 2012-01-25 17:07:04.070 122226 1 18186397 18252534 2011-10-31 11:06:58.783 2011-10-31 11:42:33.577 14672 3 18186386 18841658 18579647 2012-01-25 15:55:44.197 2012-01-25 16:12:54.603 13393 2 18841656 18841659 18579647 2012-01-25 15:55:44.197 2012-01-25 16:43:53.883 18491 3 18841656 15664402 15631663 18841633 18579609 2012-01-24 18:30:31.307 2012-01-25 11:27:26.733 22653 17 18841637 18579609 2012-01-24 18:30:31.307 2012-01-24 19:12:05.003 7562 4 18841633 18841636 18579609 2012-01-24 18:30:31.307 2012-01-24 18:47:20.960 4576 3 18841633 18841635 18579609 2012-01-24 18:30:31.307 2012-01-24 18:36:09.380 4576 2 18841633 18841634 18579609 2012-01-24 18:30:31.307 2012-01-24 18:30:31.307 133 1 18841633 18841639 18579609 2012-01-24 18:30:31.307 2012-01-24 20:08:57.110 15623 6 18841633 18841638 18579609 2012-01-24 18:30:31.307 2012-01-24 19:14:21.567 7570 5 18841633 18841645 18579609 2012-01-24 18:30:31.307 2012-01-24 20:09:46.800 15621 7 18841633 18841614 18579556 2012-01-23 10:47:02.330 2012-01-23 12:39:45.357 37455 9 18841605 29229206 29196438 18841615 18579556 2012-01-23 10:47:02.330 2012-01-23 16:21:38.060 40231 10 18841605 18841616 18579556 2012-01-24 09:34:57.887 2012-01-24 09:34:57.887 388305 1 18841617 18579556 2012-01-23 10:47:02.330 2012-01-23 16:22:07.003 40274 11 18841605 18841618 18579556 2012-01-23 10:47:02.330 2012-01-24 09:38:26.383 41012 12 18841605 18841619 18579556 2012-01-23 10:47:02.330 2012-01-24 09:39:37.703 41009 13 18841605 18841620 18579589 2012-01-24 12:33:39.883 2012-01-24 13:09:13.737 16662 4 18841622 18579589 2012-01-24 12:33:39.883 2012-01-24 13:09:13.737 133 1 18841620 18841623 18579589 2012-01-24 12:33:39.883 2012-01-24 13:09:13.737 19581 2 18841620 18841624 18579589 2012-01-24 12:33:39.883 2012-01-24 13:09:13.737 19548 3 18841620 18186399 18252534 2011-10-31 11:06:58.783 2011-10-31 12:46:22.553 16456 5 18186386 18186398 18252534 2011-10-31 11:06:58.783 2011-10-31 12:36:29.123 14672 4 18186386 18186401 18252534 2011-10-31 14:19:18.243 2011-10-31 14:19:18.243 2724 1 18186400 18252534 2011-10-31 11:06:58.783 2011-10-31 12:48:27.097 17125 6 18186386 18186403 18252534 2011-10-31 14:19:43.553 2011-10-31 14:19:43.553 15901 1 18186402 18252534 2011-10-31 14:19:30.467 2011-10-31 14:19:30.467 7842 1 18186405 18252534 2011-10-31 11:06:58.783 2011-10-31 13:03:55.453 17091 7 18186386 18841605 18579556 2012-01-23 10:47:02.330 2012-01-24 09:39:45.987 41009 14 18186404 18252534 2011-10-31 14:20:15.757 2011-10-31 14:20:15.757 19303 1 18186407 18252534 2011-10-31 11:06:58.783 2011-10-31 14:28:32.350 19239 9 18186386 18841607 18579556 2012-01-23 10:47:02.330 2012-01-23 11:00:03.067 6959 2 18841605 18186406 18252534 2011-10-31 11:06:58.783 2011-10-31 14:22:44.837 18501 8 18186386 18841606 18579556 2012-01-23 10:47:02.330 2012-01-23 10:47:02.330 133 1 18841605 18841609 18579556 2012-01-23 10:47:02.330 2012-01-23 11:43:20.703 19992 4 18841605 18841608 18579556 2012-01-23 10:47:02.330 2012-01-23 11:29:57.947 15139 3 18841605 18841611 18579556 2012-01-23 10:47:02.330 2012-01-23 12:06:47.543 30645 6 18841605 18186411 18252618 2011-11-16 11:15:35.983 2011-11-16 11:15:35.983 133 1 18186410 18841610 18579556 2012-01-23 10:47:02.330 2012-01-23 12:00:21.260 27264 5 18841605 18186410 18252618 2011-11-16 11:15:35.983 2011-11-16 15:43:42.977 8682 2 18841613 18579556 2012-01-23 10:47:02.330 2012-01-23 12:37:35.213 37455 8 18841605 18841612 18579556 2012-01-23 10:47:02.330 2012-01-23 12:36:23.350 37450 7 18841605 11272828 New Continue without disc Select: "Use operating system installation disc image file" and navigate to .iso file Select: Linux and "Other 2.6.x kernel" Select: "Customize Settings" and give name (Poseidon.3.1 vm) Setting Popups... Choose "Hard Drive" bump size from 8 to 20GB, and uncheck both "pre-allocate disk space" and "split to 2gb files" then Apply Now the Virtual Machine Library should have a powered-off VM, dclick it and power it on \\ \\ \\ \\ \\ \\]]> 11240082 18579748 18645263 1 2012-02-01 16:17:33.537 2012-02-01 16:17:33.537 18579747 18186354 18252382 2011-10-05 13:45:40.947 2011-10-05 13:45:40.947 45928 1 18186351 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 16944 7 9928729 18186350 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 16471 6 9928729 18186353 18252382 2011-10-05 13:34:48.917 2011-10-05 13:34:48.917 133 1 18186352 19040227 2009-05-03 11:41:28.470 2012-07-24 10:35:14.283 17993 8 9928729 18186346 18252373 2011-09-30 22:00:20.763 2011-09-30 22:00:52.080 112903 1 18186347 18252377 2011-09-30 22:12:43.937 2011-09-30 22:12:43.937 133 1 18579696 18645212 22 2012-01-25 15:53:11.910 2012-01-26 09:23:29.603 18579647 18186348 9798434 2009-05-12 08:02:08.840 2009-05-12 08:04:58.613 3399 2 9928767 18186349 9798434 2009-05-12 08:02:08.840 2011-10-03 11:05:26.783 8657 3 9928767 18579694 18645210 21 2012-01-25 15:53:11.910 2012-01-26 09:10:26.953 18579647 10388907 10356187 10388908 10356189 18579692 18645208 20 2012-01-25 15:53:11.910 2012-01-26 08:55:55.677 18579647 18252535 18285286 1 2011-10-31 11:06:34.957 2011-10-31 11:06:34.957 18252534 29196439 29229207 1 2016-09-08 14:01:01.607 2016-09-08 14:01:01.607 29196438 18252619 18285369 1 2011-11-16 11:08:40.337 2011-11-16 11:08:40.337 18252618 18579800 18645314 1 2012-02-03 13:01:11.797 2012-02-03 13:01:11.797 18579799 18353982 18252394 2011-11-16 10:48:13.263 2011-11-16 10:48:13.263 18841763 18579799 2012-02-03 13:01:33.630 2012-02-03 14:35:07.583 10112 6 18841675 5899715 5832865 2008-07-25 14:15:02.463 2008-07-25 14:15:02.463 21790735 21823500 2 2013-08-29 11:33:00.300 2013-08-29 11:51:39.147 21790731 18252616 18285367 2 2011-10-06 12:12:04.233 2011-10-06 12:17:55.237 18252394 21790732 21823498 1 2013-08-29 11:33:00.300 2013-08-29 11:33:00.300 21790731 11272734 Add Server and entered "localhost"{color}\\ back in another terminal..... {color:#ff0000}7) create an expdba user and expd database:{color} rich@rich-desktop:/$  rich@rich-desktop:~/Desktop$ sudo \-u postgres createuser \-D \-A \-P expddba Enter password for new role: Enter it again: Shall the new role be allowed to create more new roles? (y/n) y  {color:#ff0000}8) create an expd database:{color} rich@rich-desktop:~/Desktop$ sudo \-u postgres createdb \-O expddba expd \\ rich@rich-desktop:~/Desktop$   \\ \\]]> 11239985 18579758 18645273 4 2012-02-01 16:17:33.537 2012-02-02 11:02:49.763 18579747 18579756 18645271 3 2012-02-01 16:17:33.537 2012-02-02 11:02:22.487 18579747 5407515 5374784 18579755 18645270 2 2012-02-01 16:17:33.537 2012-02-01 16:30:19.003 18579747 5899726 5832872 2008-07-25 15:50:34.260 2008-07-25 15:50:34.260 5899727 5832857 2008-07-25 16:47:40.707 2008-07-25 16:47:40.707 5899724 5832872 2008-07-25 15:50:34.257 2008-07-25 15:50:34.257 5899725 5832872 2008-07-25 15:50:34.260 2008-07-25 15:50:34.260 18579759 18645274 5 2012-02-01 16:17:33.537 2012-02-02 11:04:35.417 18579747 5899723 5832872 2008-07-25 15:50:34.257 2008-07-25 15:50:34.257 5407513 5374783 18285368 18252618 21004495 20971729 21004432 20971666 21004434 http://www.thegeekstuff.com/2012/06/enable-epel-repository/\\ {code} [rich@mbari1548-COS-vm ~]$ yum repolist Loaded plugins: fastestmirror, refresh-packagekit, security Determining fastest mirrors Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=6&arch=i386&repo=os error was 14: PYCURL ERROR 6 - "Couldn't resolve host 'mirrorlist.centos.org'" repo id repo name status base CentOS-6 - Base 0 extras CentOS-6 - Extras 0 pgdg91 PostgreSQL 9.1 6 - i386 0 updates CentOS-6 - Updates 0 repolist: 0 [rich@mbari1548-COS-vm ~]$ {code}  shows need stuff... as root: {code} [rich@mbari1548-COS-vm ~]$ su - Password: [root@mbari1548-COS-vm ~]# rpm -Uvh http://ftp.linux.ncsu.edu/pub/epel/6/i386/epel-release-6-8.noarch.rpm Retrieving http://ftp.linux.ncsu.edu/pub/epel/6/i386/epel-release-6-8.noarch.rpm warning: /var/tmp/rpm-tmp.UFfaT0: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY Preparing...                ########################################### [100%]    1:epel-release           ########################################### [100%] [root@mbari1548-COS-vm ~]# {code}\\ \\ \\]]> 20971668 21004478 20971712 21004476 20971710 21004482 20971716 21004480 20971714 21004470 20971704 21004474 20971708 21004472 20971706 9831186 9798435 18645263 18579748 18645270 18579755 18645271 Stopping and Starting Datamanager and Navproc   Linux workstations itchy & scratchy are located below Keyboard #1. Both must be powered ON. There is a third linux box below them but its for backup and stays OFF.   Turn on Monitor #1. You will be directed to switch the Kbd/Monitor between itchy & scratchy a couple of times. To do that, hit scroll-lock key twice to bring up KVM switch software. Then scroll down to ' itchy' or 'scratchy' and select as directed.   1.    Select 'scratchy' on the KVM, select it and hit a couple of times to get its attention.   2.    the login path diverges here depending on how the last user left it.                                              a.    if you are presented a command-line login prompt then log in as user = tiburon (pilots or Dan C have pswd)                                             b.    if previous user had left it logged in at a cmd line prompt, proceed to step '3'                                              c.    If its it was left logged in at the 'modern 'Graphical UI (red hats red background etc.) then use mouse to do a System>Log Off. And let it close the GUI and revert to the command-line interface. Then go back to (a) above and re-login as tiburon    3.    Type dk to kill any previously running datamanager.   4.    Select 'itchy' on the KVM, select it and hit a couple of times to get its attention.                                              a.    Log in as tiburon (same as steps 2a-c above)                                             b.    Type nk then to kill any previously running navproc or datamanager                                              c.    type 'ds' to restart datamanager (may take about 10 seconds to boot - and tell you it couldn't find a boot server, that's OK)                                             d.    type 'ns' to restart navproc   5.    Re-select 'scratchy' on the KVM                                              a.    type ds to start datamanager (should start almost immediately )                                             b.    (note there is no navproc to start on scratchy)   Data logging should start within and Dataprobe over on LAVA should go green two minutes. (It takes about two minutes for the watchdog tasks on scratchy to autostart the data logging. IF NOT, more serious problems are at play. There is a WesternFlyer/DocRicketts Data Logging Users Guide in a white binder above 'LAVA' you will need to start troubleshooting there.   {gliffy:name=ItchyScratchyLava|space=Rich|page=Data Loging for non-ROV cruises|pageid=18579747|align=left|size=L}]]> 18579756 18645273 a couple of times to get its attention.   2.    the login path diverges here depending on how the last user left it.                                              a.    if you are presented a command-line login prompt then log in as user = tiburon (pilots or Dan C have pswd)                                             b.    if previous user had left it logged in at a cmd line prompt, proceed to step '3'                                              c.    If its it was left logged in at the 'modern 'Graphical UI (red hats red background etc.) then use mouse to do a System>Log Off. And let it close the GUI and revert to the command-line interface. Then go back to (a) above and re-login as tiburon    3.    Type dk to kill any previously running datamanager.   4.    Select 'itchy' on the KVM, select it and hit a couple of times to get its attention.                                              a.    Log in as tiburon (same as steps 2a-c above)                                             b.    Type nk then to kill any previously running navproc or datamanager                                              c.    type 'ds' to restart datamanager (may take about 10 seconds to boot - and tell you it couldn't find a boot server, that's OK)                                             d.    type 'ns' to restart navproc   5.    Re-select 'scratchy' on the KVM                                              a.    type ds to start datamanager (should start almost immediately )                                             b.    (note there is no navproc to start on scratchy)   Data logging should start within and Dataprobe over on LAVA should go green two minutes. (It takes about two minutes for the watchdog tasks on scratchy to autostart the data logging. IF NOT, more serious problems are at play. There is a WesternFlyer/DocRicketts Data Logging Users Guide in a white binder above 'LAVA' you will need to start troubleshooting there.   \\ {gliffy:name=ItchyScratchyLava|space=Rich|page=Data Loging for non-ROV cruises|pageid=18579747|align=left|size=L}]]> 18579758 18645274 a couple of times to get its attention.   2.    the login path diverges here depending on how the last user left it.                                              a.    if you are presented a command-line login prompt then log in as user = tiburon (pilots or Dan C have pswd)                                             b.    if previous user had left it logged in at a cmd line prompt, proceed to step '3'                                              c.    If its it was left logged in at the 'modern 'Graphical UI (red hats red background etc.) then use mouse to do a System>Log Off. And let it close the GUI and revert to the command-line interface. Then go back to (a) above and re-login as tiburon    3.    Type dk to kill any previously running datamanager.   4.    Select 'itchy' on the KVM, select it and hit a couple of times to get its attention.                                              a.    Log in as tiburon (same as steps 2a-c above)                                             b.    Type nk then to kill any previously running navproc or datamanager                                              c.    type 'ds' to restart datamanager (may take about 10 seconds to boot - and tell you it couldn't find a boot server, that's OK)                                             d.    type 'ns' to restart navproc   5.    Re-select 'scratchy' on the KVM                                              a.    type ds to start datamanager (should start almost immediately )                                             b.    (note there is no navproc to start on scratchy)   Data logging should start within and Dataprobe over on LAVA should go green two minutes. (It takes about two minutes for the watchdog tasks on scratchy to autostart the data logging. IF NOT, more serious problems are at play. There is a WesternFlyer/DocRicketts Data Logging Users Guide in a white binder above 'LAVA' you will need to start troubleshooting there.   \\ {gliffy:name=ItchyScratchyLava|space=Rich|page=Data Loging for non-ROV cruises|pageid=18579747|align=left|size=L}]]> 18579759 18645314 18579800 18645210 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... The post-rov-delivery changes to the system to meet MBARI requirements means both the MBARI and SMD software "design" is not clean. There is some data  duplication and some seemingly circular data pathways - hopefully they are correctly captured below... although about two years afte-the-fact. h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} {color:#ff0000}THIS IS APPROXIMATE... NEEDS VERIFICATION.{color} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) (also assumes PR=238 ZS=0 ZV=0 ZL=0 from prior setup) {panel} h2. The Navproc Code on Itchy Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING (see below, extract from /usr/tiburon2/bin/navproc/coreNav.wf on itchy.) {panel}  serialPort  0,15  9600   8    1    None   CR/LF  # ROV Digiquartz Pressure In ... serialIn  ROV.DIGIQ.STRING        CHAR\[64\]  "%s\n"       No   0,15  None {panel} Navproc runs depthCalcTask() (see: /usr/tiburon2/src/navproc/calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer.  6) ROV.MBARI.DEPTH is consumed by the navproc vorneTask and sent serially to the Vorne Display in the control room.  ]]> 18579694 18645208 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... The post-rov-delivery changes to the system to meet MBARI requirements means both the MBARI and SMD software "design" is not clean. There is some data  duplication and some seemingly circular data pathways - hopefully they are correctly captured below... although about two years afte-the-fact. h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code on Itchy Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING Navproc runs depthCalcTask() (see: calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer.  6) ROV.MBARI.DEPTH is consumed by the navproc vorneTask and sent serially to the Vorne Display in the control room.  ]]> 18579692 18645205 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... The post-rov-delivery changes to the system to meet MBARI requirements means both the MBARI and SMD software "design" is not clean. There is some data  duplication and some seemingly circular data pathways - hopefully they are correctly captured below... although about two years afte-the-fact. h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code on Itchy Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING Navproc runs depthCalcTask() (see: calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer. \\ \\]]> 18579689 18645203 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... The post-rov-delivery changes to the system to meet MBARI requirements means both the MBARI and SMD software "design" is not clean. There is some data  duplication and some seemingly circular data pathways - hopefully they are correctly captured below... although about two years afte-the-fact. h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code -Unfortunately, sprinkled throughout the original code, data were referred to as depth even in places when it was a pressure value.- Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING Navproc runs depthCalcTask() (see: calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer. \\ \\]]> 18579687 18645212 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... The post-rov-delivery changes to the system to meet MBARI requirements means both the MBARI and SMD software "design" is not clean. There is some data  duplication and some seemingly circular data pathways - hopefully they are correctly captured below... although about two years afte-the-fact. h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd. So commands from terminal>digi begin \*0100 and data from digi>terminal should begin \*0001... I think below was investigating how it was shipped by SMD: {panel} {color:#ff0000}THIS IS APPROXIMATE... NEEDS VERIFICATION.{color} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) (also assumes PR=238 ZS=0 ZV=0 ZL=0 from prior setup) {panel} h2. The Navproc Code on Itchy Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING (see below, extract from /usr/tiburon2/bin/navproc/coreNav.wf on itchy.) {panel}  serialPort  0,15  9600   8    1    None   CR/LF  # ROV Digiquartz Pressure In ... serialIn  ROV.DIGIQ.STRING        CHAR\[64\]  "%s\n"       No   0,15  None {panel} Navproc runs depthCalcTask() (see: /usr/tiburon2/src/navproc/calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer.  6) ROV.MBARI.DEPTH is consumed by the navproc vorneTask and sent serially to the Vorne Display in the control room.  ]]> 18579696 18645194 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output pressure(decibars), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached.... {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to decibars) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code]]> 18579678 18645191 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output pressure(decibars), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached.... {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to decibars) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code]]> 18579675 18645192 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output pressure(decibars), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached.... {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to decibars) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code]]> 18579676 21823498 21790732 18645189 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to remove their changes and offsets etc. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached.... {panel} \*0100EW    (Enable EEPROM write for one command.) \*0100ZL = 1 (zero tare locked) \*0100UN = 0 (user defined units based on UF multiplier) \*0100UF = 0.683853 (psi to decibars) \*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code]]> 18579673 18645187 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to remove their changes and offsets etc. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 EW \*0100MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the 0100EW (enable eprom write cmd) See manual attached.... {panel} \*0100EW \*0100ZL = 1 (zero locked) \*0100UN = 0 \*0100UF = 0.683853 \*0100MD = 2 {panel} h2. The Navproc Code]]> 18579671 18645201 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code -Unfortunately, sprinkled throughout the original code, data were referred to as depth even in places when it was a pressure value.- Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING Navproc runs depthCalcTask() (see: calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer. \\ \\]]> 18579685 18645199 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code -Unfortunately, sprinkled throughout the original code, data were referred to as depth even in places when it was a pressure value.- Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING Navproc runs depthCalcTask() (see: calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system) h2. What Gets Used 1) Core data logging by shipnavlogr on scratchy logs the following Pressure and Depth items derived from the Digiquartz ROV.DIGIQ.SCALED_PRESSURE ROV.MBARI.DEPTH  2) SMD consumes the digiq formatted value of  ROV.MBARI.DEPTH as if it had come from the sensor  3) SMD therefore re-outputs the depth via the original DVECS output message string, which ends up back in navproc as ROV.DVECS.DEPTH  4) Navproc dvcsIntfcTask outputs ROV.MBARI.DEPTH within the NVP string as originally agreed.    5) Navproc overlay.c task consumes ROV.MBARI.DEPTH_RATE , ROV.MBARI.DEPTH, ROV.DVECS.DEPTH (and lots of other items) and outputs on a serial line to the vehicle overlay computer. \\ \\]]> 18579683 18645198 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output (nominal meters of seawater), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters od seawater (nominal,uncorrected). Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to meters of seawater manual pg 6-9) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code -Unfortunately, sprinkled throughout the original code, data were referred to as depth even in places when it was a pressure value.- Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanager as DIGIQ.MSG.STRING Navproc runs depthCalcTask() (see: calculateDepth.c) * consumes DIGIQ.MSG.STRING * backs out the nominal psi-to-meters correction made in the xducer. ( psi = digiqDepth / 0.683853) * converts psi to decibars. (psi * 0.6894757 ) * removes observed surface pressure offset (10.1325) and publishes as ROV.DIGIQ.SCALED_PRESSURE * computes depth in meters using standard algorithms and ship's latitude and publishes as ROV.MBARI.DEPTH * computes depth change rate and publishes as ROV.MBARI.DEPTH_RATE * formats and outputs ROV.MBARI.DEPTH in Digiquartz format on serial port (back to the SMD system)           ]]> 18579682 21823500 21790735 18645196 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. What we did... We intercept the data coming from the Digiquartz and run it over to navproc, where a task parses it, converts to pressure, computes depth using ships latitude, applies offsets and then outputs back out a serial port for injection to the SMD system (Refer to FIgure). This also required reprogramming the Digiquartz to continuously output rs232 on powerup, output pressure(decibars), and no zero-offset tare. Additionally, we also provide a depth output from the Seabird CTD in Digiquartz format in case the sensor ever dies in the field.... h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) Note cmd format is \*ddsscc  dd=destination(the sensor) ss=source(you,the terminal or PC) cc=cmd I think below was investigating how it was shipped by SMD: {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the \*0100EW (enable eeprom write cmd) See manual attached... {color:#ff0000}THIS NEEDS VERIFICATION.{color} {panel} Note \*0100EW  =  (Enable EEPROM write for one command.) \*0100EW*0100ZL = 1 (zero tare locked) \*0100EW*0100UN = 0 (user defined units based on UF multiplier) \*0100EW*0100UF = 0.683853 (psi to decibars) \*0100EW*0100MD = 2   (display off, continuous rs232 on) \\ {panel} h2. The Navproc Code Unfortunately, sprinkled throughout the original code, data were referred to as depth even in places when it was a pressure value. Navproc runs a serialIn task to ingest the Digiquartz message string and publishes it to datamanageras DIGIQ.MSG.STRING ]]> 18579680 21398801 21366098 18645129 18579610 18645127 18579607 18645174 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. As Built \\   ]]> 18579658 18645175 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. As Built We re-program the Digiquartz to output Depth in meters uncorrected. \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 EW \*0100MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it {panel} \*0100EW \*0100ZL = 1 (zero locked) \*0100UN = 0 \*0100UF = 0.683853 \*0100MD = 2 {panel}]]> 18579659 18645177 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. As Built We re-program the Digiquartz to output Depth in meters uncorrected. \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 EW \*0100MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it {panel} \*0100EW \*0100ZL = 1 (zero locked) \*0100UN = 0 \*0100UF = 0.683853 \*0100MD = 2 {panel}]]> 18579661 18645179 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. As Built We re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual.. see Confluence Attachments to this page.  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 EW \*0100MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the 0100EW (enable eprom write cmd) See manual attached.... {panel} \*0100EW \*0100ZL = 1 (zero locked) \*0100UN = 0 \*0100UF = 0.683853 \*0100MD = 2 {panel}]]> 18579663 18645181 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. As Built First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 EW \*0100MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the 0100EW (enable eprom write cmd) See manual attached.... {panel} \*0100EW \*0100ZL = 1 (zero locked) \*0100UN = 0 \*0100UF = 0.683853 \*0100MD = 2 {panel}]]> 18579665 18645183 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. Programming the Digiquartz First step was to re-program the Digiquartz to output Depth in meters uncorrected. Refer to manual and notes below..... (see Confluence Attachments to this page).  \\ Direct connect serially My notes are sketchy here... refer to digiquartz manual....(Model: 8B4000-I s/n 107921) I think below was investigating how it was shipped by SMD {panel} \*0100 MD MD=2 \*0100 PR   PR=238 \*0100 EW \*0100MD=0           UN=8 (metersH2O (freshwater))           UF=1.00000           ZS = 0           ZV = 0           ZL = 0 {panel} I think below is how I commanded it - possibly each cmd was preceded by the 0100EW (enable eprom write cmd) See manual attached.... {panel} \*0100EW \*0100ZL = 1 (zero locked) \*0100UN = 0 \*0100UF = 0.683853 \*0100MD = 2 {panel}]]> 18579667 18645166 \\ ROV Paroscientifics Digiquartz configured by SMD to provide depth in meters (nominal/uncorrected)\\ SMD software allows for pilot input of an offset to account for surface diff (atmospheric plus slight calibration trim). \\ SMD software has no provision to tell us what the offset is for post-processing.\\ SMD contract specified pressure be provided in the 'DVECS' serial string to navproc, however as built was digiquartz depth in meters plus SMD applied pilot depth offset.\\ Our requirements are for: o   precise pressure>depth conversion (using ships latitude) o   any offsets are known and stable o   nominal 'depth=zero' at surface (psig) o   single source - ie everyone looks at, logs and displays the same value\\   ]]> 18579649 18645167 depth conversion (using ships latitude) * any offsets are known and stable * nominal 'depth=zero' at surface (psig) * single source - ie everyone looks at, logs and displays the same value h2. As Built \\   ]]> 18579650 18645085 18579557 21004613 20971850 18645119 18579595 18645120 18579596 18645121 18579597 10389119 First:   truncate table ctdder   Then, working in small batches within a single year   Open the dts job ROVCtdDerLoader and set the connection1 property to point to the der file you want to load and then run it   Repeat as needed...     Then fix the target table below in two places: the year, and the platform id (989 is tibr, 988 is vnta)   INSERT INTO RovctdBinData_1997   (DatetimeGMT,         DeviceID,         EpochSecs,         LoadID_FK,         bin,         p,         t,         c,         s,         o2,         light,         oc,         ot,         trans,         rlat,         rlon,         ptsFlag,         o2Flag,         lightFlag,         latlonFlag,         ProcessingID_FK)                SELECT         \[dbo\].EpochSecondsToDTG(usec) as DatetimeGMT,         989,         usec,         \-1997,         usec,         pres,         \[temp\],         cond,         dbo.Salinity(cond,temp,pres),         oxyg,         light,         o2curr,         o2temp,         transvolt,         lat,         lon,         2,         2,         2,         2,         0   FROM         ctdder   go   \---truncate table ctdder \---go]]> 10356406 18645115 18579591 18645116 18579592 18645117 18579593 18645118 18579594 18645114 18579590 19072936 19040230 19072935 19040229 19072938 19040232 19072937 19040231 19072932 19040225 18645102 18579575 19072943 19040237 19072940 19040234 19072941 19040235 19072982 19040277 19072993 19040288 19072991 19040286 19072995 19040290 19072998 19040293 19072997 19040292 19072999 19040294 19073001 19040296 19073003 19040298 15664202 15631452 15664209 15631459 15664207 15631457 15664203 15631453 9830872 9798117 9830873 9798118 15664232 15631486 15664234 15631489 18285286 18252535 15664238 15631495 15664160 15631409 15663232 15630469 15663234 15630471 19073100 19040398 15663230 15630467 15663229 15630466 15663224 15630461 15663226 15630463 18285153 18252397 15663262 15630499 15663265 15630502 18285140 18252383 32440321 32407553 18285136 18252378 18285138 18252380 16449604 Device Name = MARS             Device Description = MARS Main Hub *Device ID = 1785*            *Device UUID = 9a5310bd-4442-11e0-bf45-bd9bff065a7d* \\ Device Name = MARS LOAD1 *Device ID = 1772*            *Device UUID = 6b2e4697-352d-11e0-8cb9-cb191be4ef2b*\\ Device Name = MARS LOAD2 *Device ID = 1773*            *Device UUID = b64dfe9f-352d-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS LOAD3 *Device ID = 1774*            *Device UUID = cbf3ae50-352d-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS LOAD4 *Device ID = 1775*            *Device UUID = f05e7f80-352d-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS LOAD5 *Device ID = 1776*            *Device UUID = fff3e816-352d-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS LOAD6 *Device ID = 1777*            *Device UUID = 112d3d37-352e-11e0-8cb9-cb191be4ef2b*\\ Device Name = MARS LOAD7 *Device ID = 1778*            *Device UUID = 1eb5e64c-352e-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS LOAD8 *Device ID = 1779*            *Device UUID = 2e012759-352e-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS GROUNDFAULT *Device ID = 1780*            *Device UUID = 7da926f7-352e-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS ONEWIRE HA7 *Device ID = 1781*            *Device UUID = d6c69b66-352f-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS PSC *Device ID = 1782*            *Device UUID = 04acca72-3530-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS LVC *Device ID = 1783*            *Device UUID = 4c3bbb62-3530-11e0-8cb9-cb191be4ef2b* \\ Device Name = MARS MVC *Device ID = 1784*             *Device UUID = 6608cd34-3530-11e0-8cb9-cb191be4ef2b*]]> 16416840 15663235 15630472 16449603 16416839 15663241 15630478 18285134 18252375 15663245 15630482 15663243 15630480 15663247 15630484 5865635 f(clean);\- <\!-\- Define a non-SSL HTTP/1.1 Connector on port 8080   -->f(clean);   SEE ALSO...]]> 5832874 5865641 ]]> 5832880 5865645 tag of the examples context and the tag closing the localhost definition.   3) Add the following snippet to your applications WEB-INF/web.xml file. You should ensure that you respect the element ordering defined by the DTD when you create you applications web.xml file.     Resource reference to a factory for java.sql.Connection     instances that may be used for talking to a particular     database that is configured in the server.xml file. jdbc/ROVCTD javax.sql.DataSource Container 4) make sure jTds driver file is in C:\Program Files\Apache Software Foundation\Tomcat 5.5\common\lib (also might need it in C:\Program Files\Apache Software Foundation\Tomcat 5.5\shared\lib but when I was test deploying to anvil it was needed in common) 4) Fetching the connection will be done by: Context initContext = new InitialContext(); Context envContext  = (Context)initContext.lookup("java:/comp/env"); DataSource ds = (DataSource)envContext.lookup("jdbc/ROVCTD"); Connection conn = ds.getConnection();]]> 5832884 5865646 tag of the examples context and the tag closing the localhost definition.   3) Add the following snippet to your applications WEB-INF/web.xml file. You should ensure that you respect the element ordering defined by the DTD when you create you applications web.xml file.     Resource reference to a factory for java.sql.Connection     instances that may be used for talking to a particular     database that is configured in the server.xml file. jdbc/ROVCTD javax.sql.DataSource Container 4) make sure jTds driver file is in C:\Program Files\Apache Software Foundation\Tomcat 5.5\common\lib (also might need it in C:\Program Files\Apache Software Foundation\Tomcat 5.5\shared\lib but when I was test deploying to anvil it was needed in common) 5) Fetching the connection will be done by: Context initContext = new InitialContext(); Context envContext  = (Context)initContext.lookup("java:/comp/env"); DataSource ds = (DataSource)envContext.lookup("jdbc/ROVCTD"); Connection conn = ds.getConnection(); LOOK AT THESE EXAMPLES FOR [conf\server.xml|Rich:Tomcat 5.5 server.xml on anvil] and [web.xml|Rich:web.xml on anvil] \\ \\ ; ]]> 5832885 5865647 5832886 17268834               {panel} h2. Install jFreeChart and a bunch of other jar files: jfreechart-1.0.13.jar (from tempbox/rich/downloads) jcommon-1.0.16.jar jFastCGI-2.0.jar commons-logging-1.1.1.jar commons-pool-1.5.5.jar commons-collections-3.2.1.jar commons-dbcp-1.4.jar jtds-1.2.5.jar h2. Install the webapps # rovctd ## grab  rovctd folder from tempbox\rich\downloads put in C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps # jitensha-rougu (Brian Schlining's...)  ANVIL ONLY, NOT TYPHOON? ## copy Tomcat 5.5\webapps\jitensha-rogu.war to Tomcat 7.0\webapps ## restart tomcat service (should create cause tomcat to create webapps\jitensh-rogu folder and sub-folders) # any other webapps...besides defaults? (manager and ROOT) \\]]> 17236069 17268831               {panel}\\ \\ \\ h2. Install jFreeChart and other jar files: \\ jFreeChart from http://www.jfree.org/index.html  jfreechart-1.0.13.jar (from tempbox/rich/downloads) jcommon-1.0.16.jar jFastCGI-2.0.jar and commons-logging-1.1.1.jar from FastCGI project \\ \\]]> 17236066 17268832               {panel} h2. Install jFreeChart and a bunch of other jar files: jfreechart-1.0.13.jar (from tempbox/rich/downloads) jcommon-1.0.16.jar jFastCGI-2.0.jar commons-logging-1.1.1.jar commons-pool-1.5.5.jar commons-collections-3.2.1.jar commons-dbcp-1.4.jar jtds-1.2.5.jar h2. Install the webapps # rovctd ## grab  rovctd folder from tempbox\rich\downloads put in C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps # jitensha-rougu (Brian Schlining's...)  ANVIL ONLY, NOT TYPHOON? ## copy Tomcat 5.5\webapps\jitensha-rogu.war to Tomcat 7.0\webapps ## restart tomcat service (should create cause tomcat to create webapps\jitensh-rogu folder and sub-folders) # any other webapps...besides defaults? (manager and ROOT)\\]]> 17236067 17268822 17236057 18285110 18252352 15663362 15630603 17268820 17236055 18285108 18252350 17268825               {panel}\\ \\]]> 17236060 18285113 18252355 18285111 18252353 5865622 5832861 18285102 18252344 17268813 17236048 5865620 5832859 17268811 17236046 5865624 5832863 17268815 17236050 5865630 f(clean);- <\!-\- Define a non-SSL HTTP/1.1 Connector on port 8080   \-->f(clean);   ]]> 5832869 17268809 17236044 5865631 f(clean);\- <\!-\- Define a non-SSL HTTP/1.1 Connector on port 8080   \-->f(clean);   ]]> 5832870 15664404 15631665 15664403 15631664 29229207 29196439 29523980 2 5374782 2016-11-14 10:43:59.103 2016-11-14 10:43:59.103 10388909 10356190 18645597 18580090 11272736 Add Server and entered "localhost"  rich@rich-desktop:/$ \\]]> 11239987 11272738 Add Server and entered "localhost"{color} \\ back in another terminal..... {color:#ff0000}7) create an expdba user and expd database:{color} rich@rich-desktop:/$  rich@rich-desktop:~/Desktop$ sudo \-u postgres createuser \-D \-A \-P expddba Enter password for new role: Enter it again: Shall the new role be allowed to create more new roles? (y/n) y  {color:#ff0000}8) create an expd database:{color} rich@rich-desktop:~/Desktop$ sudo \-u postgres createdb \-O expddba expd \\ rich@rich-desktop:~/Desktop$  \\ \\]]> 11239989 18285367 18252616 18285369 18252619 5407512 5374782 2 2006-10-17 21:48:40.373 2026-02-04 08:33:05.020 18252394 5 false 0.0 0 0 18579609 5 false 0.0 0 0 5374783 5 false 0.0 0 0 11239985 6 false 0.0 0 0 9798116 5 false 0.0 0 0 21790731 6 false 0.0 0 0 21790727 6 false 0.0 0 0 18252377 5 false 0.0 0 0 18252382 5 false 0.0 0 0 18251909 5 false 0.0 0 0 29196438 5 false 0.0 0 0 18579647 5 false 0.0 0 0 15631663 6 false 0.0 0 0 15630460 6 false 0.0 0 0 11239985 5 false 0.0 0 0 15630458 6 false 0.0 0 0 10356189 5 false 0.0 0 0 15631451 6 false 0.0 0 0 18579647 6 false 0.0 0 0 18579556 5 false 0.0 0 0 15631461 6 false 0.0 0 0 15630601 6 false 0.0 0 0 9798116 6 false 0.0 0 0 21366097 5 false 0.0 0 0 15631461 5 false 0.0 0 0 15631451 5 false 0.0 0 0 18579572 5 false 0.0 0 0 15630601 5 false 0.0 0 0 9798434 5 false 0.0 0 0 18579609 6 false 0.0 0 0 18579583 5 false 0.0 0 0 21366097 6 false 0.0 0 0 18252534 6 false 0.0 0 0 18579589 5 false 0.0 0 0 15631493 6 false 0.0 0 0 15631493 5 false 0.0 0 0 18579605 6 false 0.0 0 0 18579605 5 false 0.0 0 0 15631663 5 false 0.0 0 0 5832872 5 false 0.0 0 0 18579589 6 false 0.0 0 0 5832865 5 false 0.0 0 0 18252534 5 false 0.0 0 0 18579747 5 false 0.0 0 0 18579583 6 false 0.0 0 0 5374783 6 false 0.0 0 0 5832857 5 false 0.0 0 0 5832865 6 false 0.0 0 0 18579572 6 false 0.0 0 0 20971663 6 false 0.0 0 0 19040224 5 false 0.0 0 0 20971663 5 false 0.0 0 0 5832872 6 false 0.0 0 0 19040227 5 false 0.0 0 0 5832857 6 false 0.0 0 0 5832878 5 false 0.0 0 0 10356189 6 false 0.0 0 0 18579799 6 false 0.0 0 0 9798434 6 false 0.0 0 0 18579556 6 false 0.0 0 0 17236042 5 false 0.0 0 0 5832878 6 false 0.0 0 0 18579799 5 false 0.0 0 0 15630460 5 false 0.0 0 0 18252373 6 false 0.0 0 0 15630458 5 false 0.0 0 0 19040224 6 false 0.0 0 0 19040227 6 false 0.0 0 0 21790731 5 false 0.0 0 0 21790727 5 false 0.0 0 0 10356405 6 false 0.0 0 0 18251909 6 false 0.0 0 0 18252382 6 false 0.0 0 0 18252377 6 false 0.0 0 0 18252618 6 false 0.0 0 0 29196438 6 false 0.0 0 0 18252618 5 false 0.0 0 0 18252394 6 false 0.0 0 0 18579747 6 false 0.0 0 0 17236042 6 false 0.0 0 0 18252373 5 false 0.0 0 0 10356405 5 false 0.0 0 0