Tiger Control Panel (TCP) is a windows program to interface with TG-1000 controller over serial. It provides a serial terminal to send and receive serial commands to the controller and graphic interface to report positions , axis status etc.
1) Com Port, select the serial port the controller is connected to. If your unsure open window's device manager and look for a device called “Silicon Labs CP210..(COM##)”.
2) Open Comm & Close Comm , to open and close serial communication to the controller. if unsuccessful an error message would be displayed in a pop up box. After the comm port opens, the text on the button changes to “Close Comm” , when pressed again comm port is closed.
3) Serial Input, type serial commands to sent to the controller. Pressing the enter key sends the command. This box is disabled when serial com port is closed.
4) Send, sends the serial command typed in the “Serial Input” text box.
5) Halt, sents Command:HALT (\) to all the axes in the controller.
6) Where, open a small window that displays the position of all the axis in the controller. Doesn't work for Filter wheels.
7) Man Input, opens the manual input window. User can assigns manual input device like Joystick and Knobs to an axis.
8) Status, opens a window that shows the axis state in color. Green for enabled, grey for disabled, red when axis is at upper limit and white when axis is at lower limit. This window doesn't work with filter wheel.
9) LED, opens the led illumination control window. Use the checkbox to turn on/off a led, the intensity box sets the led brightness (0 to 100)
10) V Joystick, opens the virtual joystick window. User can open multiple instances of this window at the same time. It lets user move an axis with spin command or relative move command. Note spin command only works with motorized axis, and doesn't work with piezo, micro mirror and tunable lens.
11) Multi Cmd, is a utility window that lets user send a series of serial command repeatedly in order. Type a series of serial command, separate them with semi-colon(;), then when “Step” button is pressed, the program sends the first command,when pressed again, sends the 2nd command and so on. Once it gets to the end, it'll send the first command again.
12) BENABLE, open the Button enable/disable window. user can set if a particular card in the controller should or should not repond to the button presses on the joy pod , such as @, home, zero and the joystick button. Pressing the “[addr#]ss” button would save the button state to the cards non volatile memory.
13) Identify, to enable all the above utilities, the program needs to scan and identify all the cards, axis and modules in the controller. This is done automatically when the serial comm port is opened with the “Open Comm” button. However if there was an error , user can rerun this scan by pressing the identify button.
14) CLEAR, clears all the text in the serial command response window ie the big black box.
15) Motor Axis, list all the axis the program has found in the controller.
16) TX Buffer, prints the number of serial commands that are in queue waiting to be sent to the controller.
17) Gamepad, Opens the Gamepad UI which lets you assign function to a XBox Controller. This module is available since version 18.104.22.168. First is the header “Gamepad Found” or “Gamepad NOT Found” that indicates if the UI has found a controller or not. Next is the Left and Right Thumb stick options. This lets you assign an axis and a multiplier to the controllers thumb sticks. When the thumbstick is deflected, the UI reads the deflection applies the multiplier and issues a Command:SPIN (@) that is proportional to the deflection. Note spin command only works with motorized axis, and doesn't work with piezo, micro mirror and tunable lens. Next is the Button assignment table. The left column list all the buttons on the gamepad, and the editable right column holds the list of serial commands that will be sent on a button press. All these settings are automatically saved between sessions , however the user can use the SAVE and LOAD button to save the settings into a XML file and load them later.