Home

Documentation

Project Support

Changes in Version 1 of GraspSwControllerCmdLeds

Author:
isani
Timestamp:
Mon Sep 30 15:39:17 2013

Legend:

Unmodified
Added
Removed
Modified

  • GraspSwControllerCmdLeds

    v0 v1
      1  '''[wiki:GraspSwControllerCmd leds]''' 
      2   
      3  [[TracNav(GraspContents)]] 
      4   
      5  ||Command:||'''leds'''|| 
      6  ||Contexts:||Network socket, serial console.|| 
      7  ||Function:||Disables or Enables the STARGRASP controller's diagnostic LEDs|| 
      8  ||Required Parameters:||none.|| 
      9  ||Optional Parameters:||on | off|| 
      10   
      11  == About the Diagnostic LEDs == 
      12   
      13  The STARGRASP FPGA board has 6 diagnostic LEDs.  5 are in a row on the 
      14  top edge of the board, and the 6th is with the fiber for the Ethernet. 
      15  The Ethernet light behavior is fairly standard: Solid (green) 
      16  indicates a link has been established, and blinks correspond to 
      17  packets going in or out.  Note that packets could be any Ethernet 
      18  packets, including ARP requests or DHCP requests, so blinks do not 
      19  necessarily indicate that IP has been configured.  LED D2 can be used 
      20  to determine more about IP addressing and logging. 
      21   
      22  === D1 (green) === 
      23   * Blinks a few times rapidly: Selftests are about to start. 
      24   * OFF: Selftests are in progress, or have failed. 
      25   * ON: Selftests completed successfully. 
      26   * Blinks a few times slowly: Selftest completed, but failed (will stay off after.) 
      27   
      28  === D2 (green) === 
      29   * ON indicates the board has an IP address.  This could either be a static IP or one assigned by DHCP. 
      30   * Blinks: each time a TCP log message is successfully sent (1Hz status update or other message) 
      31   
      32  === D3 (red) - OPB Error === 
      33   * ON after a bus error occurs. 
      34   
      35  === D4 (red) - PLB Error === 
      36   * ON after a bus error occurs. 
      37   
      38  === D5 - FPGA Done? === 
      39   
      40  Currently, it is not possible to determine if one of the red error 
      41  LEDs is lit (or that a bus error has occurred) other than by looking 
      42  at the boardset. 
      43   
      44  === "leds off" === 
      45   
      46  Whether any of the leds are lit or not, it is advisable to issue the 
      47  "leds off" command at the start of every exposure to ensure that the 
      48  controller is not adding stray light before the shutter opens.  In the 
      49  case of D3/D4, these lights will be silently made dark and will not 
      50  re-light unless another bus error occurs.  In the case of D1/D2 and 
      51  the Ethernet light, those LEDs will continue operating normally once 
      52  "leds on" is issued. 
      53   
      54  If your CCD is configured to use background cleaning, the "leds off" 
      55  command also serves as a way to stop cleaning before integration 
      56  begins, because any command received by the controller will stop 
      57  background cleaning.