# Reference File for NEST group laptop installation
# Please use the Tinyos Tutorial under tinyos-1.x/docs for more
# information.  This is just here as a starter.


Basic Commands
**************
- Program the Mote over the ethernet:
     cd $TOSROOT/apps/Blink
     make mica2dot
     program.sh --download --networkhost=192.168.0.2 --platform=mica2dot --moteid=1
  NOTE: program.sh should already be included in your path.  It's in
        tinyos-1.x/contrib/testbed/rsc

- Getting Data from Motes
  * Install TOSBase on one Mote, Oscilloscope on the other
      cd $TOSROOT/contrib/ucb/apps/MagOscope
      emacs Makefile # remove any funny transmission frequencies (DEF_FREQ...)
         ... (do emacs stuff)
      make mica2dot
      program.sh --download --networkhost=192.168.0.2 --platform=mica2dot --moteid=2
      cd $TOSROOT/apps/TOSBase
      make mica2dot
      program.sh --download --networkhost=192.168.0.2 --platform=mica2dot --moteid=1
  * java net.tinyos.sf.SerialForwarder -port 9001 -comm network@192.168.0.2:10002 &
  * java net.tinyos.oscope.oscilloscope &



TroubleShooting
***************
Q: I can't program an eMote directly connected to my ethernet port
A: First, make sure that you can connect to the eMote
    In a cygwin shell, type:
       ping 192.168.0.2  # or whatever the address of your eMote
  Software Side issues:
    If you have no connection, make sure that the laptop's ethernet port has
    the proper IP address and subnet mask.  You want the IP
    address to belong to the same class as that of the programming board.
    Without going into too much detail of how IP addresses work, basically,
    its a good idea to use a static  IP address of 192.168.0.1, subnet mask 
    255.255.255.0.  This configuration needs to be done in Windows, through
    the "Network Settings" controls in the Control Panel.
  Hardware Side issues:
    Make sure that you have a crossover cable if you are connecting directly
    to the eMote.
    Make sure that the eMote is powered.
    Sometimes, it is necessary to turn off the wireless card so the laptop
    does not get confused and send packets over the wireless card connection.
  eMote configuration issues:
    Make sure that the eMote has the proper IP address.  Try to access the
    eMote through the web browser, pointing it at the IP address.
    ex. in internet explorer, point the browser to 192.168.0.2 assuming
        that is the IP address of your eMote.  That should get you to the
        Lantronic Web-Manager page.


Q: Why does serial forwarder keep telling me I'm getting a string of bad 
   packets?
A: There are various possible answers to this.  Check the TinyOS FAQ
   on www.tinyos.net for more info.
     One possible reason is that the baud rate on the eMote's channel for
   receiving data is set incorrectly.  See 
   http://www.eecs.berkeley.edu/~phoebusc/330NEST/eMote_%28MIB600%29_Programming.html for more details.

Q: Why doesn't matlab respond after I try to make a connection with serial
   forwarder?
A: Oftentimes, this is because matlab is trying to connect to the wrong port
   on the serial forwarder.  If your serial forwarder did not start, or
   the port of the serial forwarder does not match the port that
   matlab is trying to connect to, then matlab does nothing, not even
   respond to 'quit' unless you kill it from outside.  The solution is
   to quickly start a serial forwarder connecting to that port so that
   matlab returns.
   Note that with the new java commmunication stack (Rob Szewczyk's
   change in May 2004), once matlab connects to the serial forwarder,
   it will complain if this connection is lost and try to reconnect.
   This may result in a stream of error messages on the matlab screen,
   which is good notification but also really annoying if you don't care.


Handy commands for checking ethernet port:
   ping <ip address>
   ipconfig		    report ethernet/IP configurations
   ipconfig /release	    release any DHCP IP addresses acquired
   ipconfig /renew	    renew a DHCP IP address