OSIE-2 PUCK telecon notes: 6/2/2009

Attendees:
Neil Cater, Joaquin del Rio, Dan Toma, Greg Johnson, Tom O'Reilly
 
Neil - buoy is just about ready to go into the water. Axys seems reluctant to particpate - nervous about interoperability?
 
Actions:
1. Dan to send description of UPC PUCK test-bed to group
2. Dan to try diagnosis of external PUCK datasheet erasure problem
3. Neil and Greg to set up conference call to Axys
4. Tom and Greg to discuss 1451 TEDS for RBR
5. Telecons to be held weekly on Tuesdays at 16:00 UTC
 
 
This week's agenda:
 
1. Update from UPC (Dan and Joaquin)
Using PUCK with Java properties in payload. No need for driver yet; just using a "retrieve sample" property. Also a property describing record and how to parse. Works with RBR. Had some problems with external PUCK - header gets corrupted. Gives latest sample on 1451 client request. Dan will try to isolate datasheet corruption problem. Will send "schematic" of his application.
 
2. Update from Kiel/Bremen (Jesper)
 
3. Technical plans for SmartBay (Greg Johnson, Eric Davis, Axys technical rep)
Neil - buoy is ready to go into water, but haven't gotten much interest from Axys in partiicpating in PUCK experiment. Mostly weather instruments now. Greg hasn't had contact with Axys - Neil requests that Greg contact him; they will try to get conference call. Neil will try to upgrade Nortek, will purchase RBR, maybe upgrade WETLabs. Right now there is a spare port on the Watchman dedicated to the OSIE-2 experiment. Greg: do we really need a 1451.0 server on the buoy? The Axys platform is pretty light-weight. Perhaps better to keep it simple. Greg: several buoy platforms coudl be used: Watchman, RBR DBC-2, or a MOOS controller. But MMC would not be quite so compelling; already been done. Note that buoy will be only 200 meters offshore, easy access.
 
4. Feedback on technical report outline (all)
Greg - template looks reasonable
 
5. Additional items?
Greg - Need to generate TEDS datasheet for instruments.
 
 
Report template:
 
1. PUCK header utilization
Which elements (if any) from the PUCK header does your system utilize?
 
2. PUCK payload description
What do you store and and what does your system host retrieve from the PUCK payload area (assuming that you use the payload)
 
3. PUCK “detection” algorithm
How does your system detect the presence of a PUCK-enabled instrument on a serial port? E.g. does the system host periodically interrogate the port, or have you implemented a manual utility that interrogates the port?
 
4. Approximate effort to integrate PUCK into observatory
 
5. Suggested changes to PUCK v1.3 protocol
 
6. Demonstration procedure
How were instruments plugged and unplugged from the system? Was one instrument replaced with another, etc
 
7. Assessment of PUCK utility in your test-bed