Home

Documentation

Project Support

Changes in Version 2 of GraspSwControllerCmdConsole

Author:
isani
Timestamp:
Thu Sep 8 11:45:05 2011
Comment:
Updated info about automatic "console off" in newer firmware.

Legend:

Unmodified
Added
Removed
Modified

  • GraspSwControllerCmdConsole

    v1 v2
    1 1  '''[wiki:GraspSwControllerCmd console]''' 
    2 2  [[TracNav(GraspContents)]] 
    3 3  ||Command:||'''console'''|| 
    4 4  ||Contexts:||Network socket.|| 
    5 5  ||Function:||Turns off and on echo of commands on the serial console.|| 
    6 6  ||Required Parameters:||Console echo '''on''' (default at power up) or '''off'''|| 
    7 7  ||Optional Parameters:||none.|| 
    8 8  When the STARGRASP controller boots, before the network is initialized, diagnostic 
    9 9  messages are sent to the serial console port (9600 BAUD, No stop bits, 8 data, 1 parity.) 
    10 10  After a DHCP (or static IP) address is assigned, the controller attempts to 
    11    send log messages to the network console, to a process called  send log messages to the network console, to a process called grasp_receiver 
      11  send log messages to the network console, to a process called  send log messages to the network console, to a process called [wiki:GraspSwToolkitReceiver grasp_receiver] 
    11 11  which usually runs on tcp port 55515 of the DHCP server host (though the DHCP server 
    12 12  can redirect to another host using the "next-server" directive.) 
    13 13  Once "stage2" controller firmware is running and the network console connection 
    14 14  is established, all commands sent to the controller still echo on the serial 
    15 15  console, too.  This should be turned off using the command '''console off''' 
    16 16  with grasp_cmd through the network, for best performance. 
      17  Later versions of the controller embedded code (developed after summer 2011) turn off console output automatically as soon as any network command is received to minimize the chances of console output being generated and unintentionally slowing down controller performance.  In all cases, lack of a connection to the network logging program [wiki:GraspSwToolkitReceiver grasp_receiver] will still result in serial console output and slow performance. 
      18   
    17 19  === Notes: === 
    18 20  ''Controller real-time performance will be adversely affected if the controller is unable to establish network logging, or if the controller is left in '''console on''' mode where commands still echo on the serial port.'' 
    19 21  ''Any command (or carriage return) entered on the serial console will re-enable '''console on''' mode.'' 
    20    Recommendation is to have '''console off''' sent as part of the power-on initialization sequence for your detector. 
      22  Recommendation is to have '''console off''' sent as part of the power-on initialization sequence for your detector unless you have newer firmware which defaults to this mode.  Even in that case, the command won't do any harm. 
      23