| |
1 |
'''[wiki:GraspSwControllerCmd console]''' |
| |
2 |
|
| |
3 |
[[TracNav(GraspContents)]] |
| |
4 |
|
| |
5 |
||Command:||'''console'''|| |
| |
6 |
||Contexts:||Network socket.|| |
| |
7 |
||Function:||Turns off and on echo of commands on the serial console.|| |
| |
8 |
||Required Parameters:||Console echo '''on''' (default at power up) or '''off'''|| |
| |
9 |
||Optional Parameters:||none.|| |
| |
10 |
|
| |
11 |
When the STARGRASP controller boots, before the network is initialized, diagnostic |
| |
12 |
messages are sent to the serial console port (9600 BAUD, No stop bits, 8 data, 1 parity.) |
| |
13 |
After a DHCP (or static IP) address is assigned, the controller attempts to |
| |
14 |
send log messages to the network console, to a process called grasp_receiver |
| |
15 |
which usually runs on tcp port 55515 of the DHCP server host (though the DHCP server |
| |
16 |
can redirect to another host using the "next-server" directive.) |
| |
17 |
|
| |
18 |
Once "stage2" controller firmware is running and the network console connection |
| |
19 |
is established, all commands sent to the controller still echo on the serial |
| |
20 |
console, too. This should be turned off using the command '''console off''' |
| |
21 |
with grasp_cmd through the network, for best performance. |
| |
22 |
|
| |
23 |
=== Notes: === |
| |
24 |
|
| |
25 |
''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.'' |
| |
26 |
|
| |
27 |
''Any command (or carriage return) entered on the serial console will re-enable '''console on''' mode.'' |
| |
28 |
|
| |
29 |
Recommendation is to have '''console off''' sent as part of the power-on initialization sequence for your detector. |
