DAQ demo instructions

What's shown in this demonstration

1. Streaming DAQ data from LabVIEW
2. Data Turbine
3. Streaming video from a standalone Axis 2400 camera
4. Streaming numeric data, with units, from the DAQ via DaqToRbnb
5. NTCP control, implemented in LabVIEW, presently limited to the X10 lights. This is because the table is new, and I've not yet written the control interface code.
6. RDV, in all its glory
7. A Java-based NTCP client (optional)
8. X10 control for lighting
9. Quanser shake table, with resonant masses provided by Jared

Requirements

Machines used

• The shaketable control program and DAQ code runs on shaketable.sdsc.edu. This is an XP box, dual Xeon. It has MATLAB, LabVIE and the Quanser code installed.
• neestpm.sdsc.edu runs the turbine, and the DaqToRbnb & AxisSource sources.
• neestpm.sdsc.edu also runs the OGSA container for NTCP, which talks to LabVIEW
  
• Your laptop, to run RDV and MS remote desktop.
  

Software required on your (demo) machine

• Java (Runtime is fine)
  
• MS Remote desktop. Included with XP, not sure if its installed by default on 2k etc.
• Firefox or other decent (non-IE) browser.
  

Software on the DAQ PC

Username/password

Procedures

Basic demonstration

1. Open up remote desktop (Programs/Accessories/Communications/Remote Desktop connection on XP) and connect to shaketable.sdsc.edu. Username is neesit. Do not disconnect any user if RDC tells you there's another user active!
2. Run RDV from http://it.nees.org/support/demos/turbine/RDV.jnlp Close the panes that it opens by default, and open video from 'Shake table video' and data from 'Shake table DAQ'. You should see pitch black video (no lights) and noisy data. If the data or video are missing, go to step 'Troubleshooting' below.
   
3. Go back to RDC window, but leave RDV running. Open up the 'X10' folder on the desktop, and run 'beacon on' and then 'lights on'. Go back to RDV and see the lights turn on in the video feed.
4. Talk enthusiastically about how cool this is. Sincerity is essential.
5. When done, use the icons in the X10 folder to turn off the beacon and lights, and close RDC. Leave the LabVIEW code running!

Basic + Quanser table

1. Follow steps 1-3 above.
2. In RDC, open the 'Q4 Lab files' folder, and select q_boot_upm_Q4.wcp. Start WinCon by clicking on the green 'Start' button. You should see a dialog that says 'End of initialization. Right and left LEDs on UPM should not be flashing'. This initializes the table and control hardware.
3. Close WinCon. For some reason, you have to close it between different WCP files.
   
4. Next, select the q_sine_x_Q4.wcp. Run it, and increase the frequency to 1Hz and the amplitude to about 50%. Go back to RDV, and check out the wildly waving masses, and the oscillating accelerometer data.
5. Take more enthusiastically about how drop-dead cool this is, and how Paul should be paid more.
6. When done, press 'Stop' on WinCon. Verify that the table has stopped moving via RDV.
7. Use X10 to turn off the lights, and close RDC as above. You can leave WinCon and LabVIEW up.

• q_north_x_Q4.wcp Northridge 94 quake
• q_elcen_x_Q4.wcp El Centro
  
• q_hach_x_Q4.wcp Hachimoto
• q_kobe_x_Q4.qcp Kobe
  

Basic + Quanser + NTCP

        String                 serverURL = "http://neestpm.sdsc.edu:8090/";

[hubbard@macilent ~/code/nclient] ant
Buildfile: build.xml

checkOGSA:

prepare:

compile:
    [javac] Compiling 2 source files to /Users/hubbard/code/nclient/build/classes

BUILD SUCCESSFUL
Total time: 8 seconds

1. 'Control program, simulated actuator' from 'ntcp-testing.llb'
2. 'Control daemon (NTCP)', from 'daemon-programs.llb'

lvHost=shaketable.sdsc.edu

1. On your laptop, run the nclient via 'ant run'
2. Then switch to RDV. The lights should come on and stay on for about 60 seconds.
3. Talk very enthusiastically about how ubernifty this all is.

Troubleshooting

1. Make sure that the LabVIEW code is running. You need 'server daemon (streaming data)' from 'daemon-programs.llb' and 'Single serial accelerometer' from 'anco-table.llb' for streaming data. For NTCP, you also need 'Control daemon' from 'daemon-programs.llb' and 'Control program, simulated actuator' from 'ntcp-testing.llb'
2. Check 'server daemon'. It should show 4 green lights - driver connected, daq running, data streaming and , er, something else. Driver means DaqToRbnb, DAQ running means the 'single serial accelerometer' program, and data streaming means that DaqToRbnb is working.
3. Make sure you ran the LabVIEW code out of the 'needs-merge' folder.
4. If the camera is black, check http://flextps.nees.org and see if the video works there. If it does, check on neestpm.sdsc.edu and restart the AxisSource program; it does sometimes hang if there's a network glitch. I think there's already a FogBug for this. Also check that no one has re-aimed the camera off to the side; this bit me in Singapore.
5. If the DAQ runs, but the driver isn't connected or is failing, you'll see no data in RDV. Log onto neestpm and restart the DaqToRbnb program. Check ~hubbard/turbine-apps.csh for details.
6. The Quanser manual is at http://users.sdsc.edu/~hubbard/neesit/. It's also on NEES central under Equipment.
7. The Turbine applications (DaqToRbnb, AxisSource) are documented on http://users.sdsc.edu/~hubbard/neesit/rbnb-apps.html