1 Introduction

2 The Devices

2.1 Usage

Fig. 2.1: The SpaceController is handled most ergonomically with the left hand

Fig. 2.2: Optimal hand position

Fig. 2.3: Handling in Right Hand Mode

Fig. 2.4: Hand position when handled with the right hand

2.2 Control Elements

Fig. 2.5: The SpaceController's control elements

2.2.1 Cap and Wheel

Fig.2.6: SpaceController in cap and ball configuration

2.2.2 Keys

• Function Keys : These keys are meant to be redefined by the user. They will do nothing if not redefined. The current assignment is shown on the display.
  
• Shift Keys : These keys do the same as the corresponding keys on your keyboard.
• Panel Key : The panel key opens the SpaceControl Panel . With the panel you can configure the device (see chapter 3.3).
• Menu Key : When the menu key is pressed the device switches into the so called menu mode (see section 2.2.4). In this mode you can adjust some of the device's parameters, without the need to open the SpaceControl Panel .
• View Keys : If your application (or the belonging plug-in) supports it you can rotate an object into the front, top or right position.
• 2D/3D , Enter Key : In standard mode this key turns the rotation off ("2D mode") and on ("3D mode"). In menu mode it is used as the enter key to confirm a selection you made in the menu.
• Fit Key : If your application (or the belonging plug-in) supports it you can move an object so it fills the screen completely.
  

2.2.3 Display

The title line shows the application which is in the foreground at the moment and the configuration file the driver has loaded; in this case the foreground application is "Inventor" and the configuration file is "Assembly.cfg". In the midsection are the six function keys listed. If there is a function assigned to a key the function name is shown, "--Inactive--" is displayed if not. The base line displays some status information, namely whether the device is in ORG, CAM, WFL, 2D or DOM mode. These modes are explained in the next section. The display will change its content in other modes, see the next section.

Fig. 2.7: The display in standard mode

2.2.4 Modes

• Normal operation is done in standard mode . You can move the cap and press the keys, and these events are transmitted to connected applications. The display shows the standard screen, i. e. the assignment actually chosen for the function keys (see fig. 2.7).
• • ORG: The SpaceController provides several move modes (s. below). You can rotate a scene e. g. around the focal point (middle of the screen window) or around the scene's origin. In the second case the field ORG is highlighted in red.
  • CAM: The cap may move the scene or the camera looking at the scene. In camera mode the field CAM is illuminated in red.
  • WFL: The silver wheel beneath the cap can be used for different tasks. If it is configured for the Wheel Function Launcher (s. below) the field WFL is red.
  • 2D: If the device is in 2D mode only translation data is transmitted, rotation data is suppressed. In this state the 2D/3D key is illuminated in red and the display's 2D field is highlighted:
    
    
    
    
    Fig. 2.8: 2D mode: 2D/3D key illuminated and 2D field in display highlighted
    
    
  • DOM: If the device is in dominant mode the device checks which of the cap's six axes is elongated most. Only the data of this axis will be transmitted, all others will be suppressed. This is useful especially if you are a beginner to avoid confusion when moving objects. In this mode the DOM field in the display is highlighted.
    
• In menu mode all keys but the MENU key and ENTER key are inoperative. To symbolize this state all blue LEDs are shut off and theMENU key and the ENTER key are illuminated in green. (The 2D/3D key operates as a Enter key in this state and does not change from 3D into 2D mode).
  

  Fig. 2.9: Menu mode: MENU and ENTER key and the menu itself are green illuminated

  Fig. 2.10: Adjusting sensitivity

  
  The menu is shown in green, and you can adjust the sensitivity, the threshold, the LCD's and the LED's brightness. To change a setting move the wheel to the element you want and press the enter key. The display will show a bar graph, move the wheel again to change the value.
  Eventually the user has connected one of these parameters directly with the wheel so you can adjust this parameter with the wheel without activating the menu mode. In this case the display shows a little circle behind the parameter (in fig. 2.9, the wheel controls e. g. the sensitivity). Only in order to show this the last two lines "Wheel Function Launcher" and "Function Keys" are displayed here; you can not select them.
  To leave the menu mode press the menu key again or wait some seconds.
  
  

3 The Software

3.1 Installation and Uninstallation

3.1.1 Windows^®

3.1.1.1 Installation

• Double click the file to start the installer.
• To save disk space you can deselect not wanted plug-ins (see below) .
• Choose an appropriate installation folder if you want to change the default one.

• 3ds Max
• AutoCAD
• Blender
  
• Catia
• Creo
• GstarCAD
• Inventor
• NX
• ProEngineer WF2
• ProEngineer WF3
• ProEngineer WF4
• ProEngineer WF5
• Solid Edge
• SolidWorks
• Universal
• Videos
  

3.1.1.2 Deinstallation

3.1.2 Linux^®

3.1.2.1 Installation

• Copy the file into an arbitrary folder (a new temporary folder "SpaceControl" will be created there and moved to "/opt/" in the end).
  
• Make sure that the installation file is executable. If not, change its access rights with your file browser or navigate to the file in a terminal window and enter there:
     chmod u+x SpaceControl_Driver_281_LNX64_setup.sh
• Open a terminal, start the file and follow the instructions. Do the installation as normal user, not as root, because the installer starts the driver at the end of the process and would create the configuration files in the root's home folder then; that is not wanted normally.
  
• Dependent on the Linux distribution it may be necessary to reboot the system before the device will be detected by the driver.
  
• After installation the installation file is not necessary any longer, and you may delete it.
• For uninstalling the software start the script "uninstall" in the just created folder "/opt/SpaceControl/".
  

3.1.2.2 Deinstallation

3.1.3 OS X^®

• Double click on the file, it is mounted in the operating system and its content is shown in a Finder window.
• Double click the icon "Double click to install ...". The software will be unpacked; root access is necessary to copy a file; enter the password when asked so.
• For starting the driver and the user interface click on the icon "SpaceControl Panel" in the Launchpad.
• For uninstalling the software start the script "uninstall" in the just created folder "/Applications/SpaceControl/".

3.1.4 Plug-ins

3.2 Starting Driver and SpaceControl Panel

3.3 SpaceControl Panel Application

Fig. 3.2: The built-in Cube Demo

• Advanced Configuration
  Opens the Advanced Configuration dialog (see below).
  
  
• Function Assignment
  Opens the dialog for configuring the keys, the Wheel Function Launcher and special assignments for the cap (see below).
  
  
• Video
  Shows a short help video with explanations for this dialog.
  
  
• Help
  Opens the manual in chapter 3.3 (this is here).
  
  
• Zero
  Defines the actual cap displacement as the zero value. The driver will send no data to the applications if the cap is in this position again and not stronger displaced than the threshold (see below).
  
  
• Defaults
  Sets all values to the default values which build a reasonable set of parameters for most applications. Attention: Also the key configurations and all recorded macros are deleted.

3.3.1 Basic Configuration

Sensitivity With the sensitivity slider you can change the speed with which your objects are moving. Higher values cause your object to move quicker with the same displacement of the cap. If the slider is moved you will see a visualization of it in the SpaceController's display as shown in fig. 3.3. Rotation Center You can change between the settings Focal Point and Origin or Camera . In the first case the cap rotates your scene around the midpoint of the screen (the midpoint of the active window to be precisely), in the second case around the origin of the scene (in scene mode) or around the camera (in camera mode). Move Mode The entries in this list are Scene and Camera . In case of Scene the cap moves (seemingly) your scene, in case of Camera the cap moves the virtual camera looking on the scene. Wheel The silver wheel beneath the cap is freely configurable. Some quick assignments can be made here by the drop down list: Left: Sensitivity, Right: WFL A movement to the left opens a little slider dialog for setting the cap's sensitivity. A movement to the right opens the so-called Wheel Function Launcher. Wheel Function Launcher The WFL is used to trigger arbitrary functions very comfortably. See there for details. Gesture Detection With this setting the wheel recognizes up to six different "gestures", i. e. combinations of left/right movements. Each gesture can be connected with a function to trigger. Sensitivity The wheel controls the cap's sensitivity. Function Keys In this mode the wheel can be used to trigger the device's six function keys (in case your fingers are not long enough to reach key 5 or 6 ...). LCD Brightness The wheel controls the brightness of the LCD. LED Brightness The wheel controls the brightness of the blue LEDs. User Defined The wheel has another setting, configured with the Function Assignment dialog.

Fig. 3.3: Display when adjusting sensitivity

• 2D Mode
  This can be set to On or Off . If set to On all the cap's rotation data is suppressed. It is needed in some applications to avoid an unwanted rotation of a drawing for example.
  
  
• Dominant Mode
  This can be set to On or Off . If set to On the driver looks which of the six coordinates x, y, z, a, b or c currently has the highest value at this moment. Only this component is transmitted, all others are set to 0. This mode is useful if you want to be sure that your object to be manipulated will not be moved in directions you are not interested in. As an example try the Roboter Demo application.

3.3.2 Advanced Configuration

Fig. 3.5: Advanced Configuration dialog, Remapping , Mouse Movement and Further Settings activated

• On/Off
  This column lets you activate or deactivate the sending of a single data component.
  
  
• Sensitivity
  The sensitivity of a single data component can be adjusted here. This sensitivity is added to the global sensitivity you can configure on the Basic Configuration sub-panel. I. e. you reach the minimal/maximal sensitivity only when both sliders - the corresponding slider here and the slider on the Basic Configuration sub-panel - are set to minimum/maximum.
  If the Connect Sensitivity Sliders checkbox is activated all three sliders are moved simultaneously.
  
  
• Reversed
  If this check box is activated the components data is multiplied by -1. For instance, if you move the cap to the left side your object will move to the right side. Some applications need this setting to work correctly (e. g. Google Earth ).
  
  
• Remap To
  This combo box allows you to redefine an axis. If you remap e. g. the x translation to the y translation, your object will move up and down instead of left and right when displacing the cap in x direction. This is also needed for certain applications (e. g. Google Earth ).
  
  
• Mouse Pointer
  It is possible to connect the cap displacement with the movement of the mouse pointer. Example: Connect the x translation with the Horizontal mouse movement and the z translation with the Vertical . Now you can move the mouse with the cap when displacing it forward/backward or left/right. (Hint: Connect the predefined "PressLeftMouseButton" command (see there) with the y-down translation and you can even click on objects with the cap. See chapter 3.3.3.5 for details.)
  If the Restore Mouse Position checkbox is activated the driver stores the current mouse position before the cap is displaced and sets it back when the cap is released again.
  With the Absolute Mouse Coordinates checkbox activated the mouse pointer is set to the center of your screen if the cap is released. Moving the cap causes the pointer to move proportionally in the corresponding direction and to move back when releasing the cap again.
  Attention: As soon as mouse pointer movement is activated no cap data is sent to the applications anymore.
  

• Move Mode :
  This parameter adjusts the mode of moving and the rotation center. Basically you can change between scene mode and camera mode.
  In scene mode the cap moves pretendedly the scene; i. e., pushing the cap to front causes the objects to move away, they will appear smaller (in truth always the camera is moved of course, not the scene).
  In camera mode the cap moves the camera looking at the scene; i. e., pushing the cap to front causes the camera to move into the scene, and objects will therefore appear bigger.
  The following modes are available:
  • Scene Mode: Rotate around Focal Point : We are in object mode, and the center of rotation is the point the camera is looking at (i. e. the window's midpoint).
  • Scene Mode: Rotate around Origin : We are in scene mode, and the center of rotation is the scene coordinate system's origin.
  • Camera Mode: Rotate around Camera : We are in camera mode, the cap moves therefore the camera looking on the scene, and the camera is the center of rotation.
  • Camera Mode: Rotate around Focal Point : The cap moves the camera, but the center of rotation is the point the camera is looking at (i. e. the window's midpoint).
  The window's midpoint determines the rotation center's x- and y-coordinate only of course. On the z-axis (the direction out of the screen) the center may be located anywhere at first. But, by rotation and concurrent translation (to hold the wanted area in the middle) the center can be moved even on the z-axis to the wanted location step by step, so that additional translation is not necessary any longer. This works more intuitive than can be explained in words.
  All move modes can be modified by two additional settings:
  
  • Lock Horizon : If this field is checked the camera is in its movement restricted in such a way, that the horizon can not be rotated. This simplifies the movement especially with camera flights.
  • Hover : In this mode the camera movement is restricted, so that a translation can not modify the distance between the camera and the x-z-plane. It results in a kind of "helicopter" flight in camera mode.
  Please be aware that not all applications and/or SpaceControl plug-ins may support all modes
  
  
• Right Hand Mode :
  The SpaceController is designed especially for the left hand (for right handers who hold there normal mouse still in the right hand). Of course the SpaceController can be handled with the right hand too, if you turn it around 90 degrees so that the wrist rest is in the correct position (see fig. 2.3 and 2.4). The cap's orientation must be adjusted then 90 degrees in the opposite direction. This is accomplished by activating the check box Right Hand Mode . Besides that, the display is rotated.
  
  
• Cap Data
  Here you can adjust the way the cap's data is sent to the applications:
  
• • Threshold
    You have to displace the cap over a minimal threshold before the driver will start sending data. This threshold can be adjusted here.
    This is useful to avoid unwanted movement of objects, e. g. if your device is pressed in a carry case for transportation over a longer period: It will last some time until the springs in the device have gained their original position. Increase the threshold if you see the driver is sending unwanted data.
  • Averaging
    Because of random fluctuations in power consumption etc. the data delivered by the cap may oscillate a little over time. To avoid moving an object even if the cap is not moved you can set the threshold to an appropriate value (see above). However, the cap will have better responsiveness with a threshold of 0. Another way to cure this unwanted movement is to average some data received by the cap. You can adjust here how many data packets are used for the averaging process from 0 (or 1 = no averaging) to 15 (the last 15 data packets will be used for averaging). Set the number of packets used for averaging to the smallest value where you see no oscillation anymore as there is a disadvantage in using this mechanism: You will see a slight time lag if the Send Gap is set to higher values at the same time.
  • Send Gap
    The Send Gap slider is used to reduce the data rate with which the device will produce its output. Figure 3.5 shows a setting of 30 ms. This means the Controller will send a data packet with translational and rotational data every 30 ms to the foreground application. Some applications are not able to receive and handle the data with high data rates. If you observe a visual delay in your application set the Send Gap to to higher values.
    If the slider is moved to its upmost position (> 400) no cap data will be sent at all.
    
    
• Brightness
  With the two sliders the Display's and the blue LEDs' brightness can be adjusted. While the sliders are moved blue bars are displayed on the LCD.
  

3.3.3 Function Assignment (Key Configuration)

3.3.3.1 Assigning Functions to Keys

• Device functions : These are functions related to devices, especially to the SpaceController of course, but also to the normal mouse or a joystick. For instance, the function SetZero does the same as the Zero button on the main dialog. You will find below a list of all device functions available.
  
  
  
  
  Fig. 3.7: Function Assignment dialog, device functions expanded
  
  
  
  
• User functions : These functions can be modified by the user and are sequences of keystrokes which you can record with a small keystroke recorder (see below).
  Additionally there are three functions named Execute Application x and  Load Configuration x ; with the first group you can execute arbitrary applications just by a keypress, with the second you can load configurations.
  
  
  
  Fig. 3.8: Function Assignment dialog, user functions expanded
  
  
  
• Application functions : This branch of functions is only there if an application is in the foreground to which a plug-in exists supporting this feature. The functions listed in this branch mirror more or less the application's menu structure and do the same as the application's menu items do. So, by dragging it to a function key you can activate an application's menu item by pushing the function key:
  
  
  
  
  Fig. 3.9: Function Assignment , application functions expanded
  
  Figure 3.9 shows the application functions list using the example of Autodesk Inventor ^® . What you can see here depends mainly on the capabilities of the application's API: Some applications give full access to their menu structure as you can see here. Others will only provide a plain list of all functions available or no functions at all. Our plug-ins try to do the best, but be prepared to see less information than shown in Fig. 3.9.
  

Fig. 3.10: Display showing the function keys' functions

Fig. 3.11: Display showing the clock

3.3.3.2 Defining User Functions (Macros)

• In the Key Configuration dialog's functions list scroll down to one of the entries "User_Function_00", "User_Function_01" etc. and press the Edit button. The Function Editor will appear:
  
  
  
  
  
  Fig. 3.12: Function Editor
  
  
  
• Give your function a meaningful name in the Function Name edit field, e. g. "my_first_own_function" as shown above.
  
• Place the cursor into the Keystrokes field and start typing your keystroke sequence by pressing the corresponding keys on the keyboard.
  There are some special commands which can not be recorded in this way:
  
  • Back : Since the backspace key will be recorded as any other key rather than doing its usual task you will need to press the Back button to correct errors.
  • Clear : You may clear the whole edit field by pressing the Clear button.
  • SpaceController Key : Pressing a SpaceController key can be simulated here: Choose the wanted key from the list. In this way the keys can be combined, and the maximal number of allowed key presses can be extended.
  • SpaceController Function : In this list you will find all SpaceController device functions. You can drag them to a key as described above or record them here as a macro. With the latter method you can even combine more than one on one key.
  • Other Key or Function : Here are four special functions listed:
    
    • Tabulator : To record a Tab you have to use this function because the tab key on your keyboard will move the focus instead of being recorded.
    • Insert Left Mouse Click : Similarly you have to use this function to insert a left mouse click because it moves the cursor in the edit field and therefore can not be recorded directly.
    • Insert Delay : This function inserts a delay of 100 ms into your macro; some applications may not react to the command without such a delay.
    • Execute only in case of state change:
      - If the macro is assigned to a cap deflection (s. section 3.3.3.6): In this case its result is that the macro is only triggered if the corresponding cap deflection changes and not (as without the function) as long as the deflection persists. So this function does the same as the checkbox Send Function only in Case of Cap Changes, but in difference to this not for all cap deflections but only for those the macro is assigned to.
      - If the macro is assigned to a key: In this case all "key pressed" events in the macro are sent into the operating system when the device key is pressed, and all "key released" events are sent when the devcice key is released. Without this function in the macro all "pressed" and "released" events are sent when the key is pressed, and no event is sent when the key is released.
      
  • Reset : This button also clears the edit field but resets the function name additionally to its default value.
• Leave the dialog with OK .
• Once defined you can apply your function to a key by dragging it to the key's combo box as described above.
  
• In The Function Assigment dialog you can copy a user function to the clipboard with the button Copy; it can be pasted then to another user function with the button Paste. When using the common short cut "Ctrl-c" and "Ctrl-v" for this press the Ctrl key and release it not until "c" or "v" is pressed and released!
  

• If your function consists only of "Shift" keys (these are the keys Ctrl, Alt, Shift and Esc by definition), the sequence is filtered and all "key pressed" events are sent into the operating system when the device key is pressed, and all "key released" events are sent when the device key is released.
• If your function contains at least one "No Shift" key, the sequence is sent completely into the operating system when the device key is pressed and nothing will be sent when the key is released again. Unless your macro contains the function Execute only in case of state change (s. above); in this case the behaviour is the same as with the shift keys.
  

3.3.3.3 Assigning Functions to Special Keys

Fig. 3.13: Function Assignment dialog with activated Special Key configuration

• Below the Function Keys you see the Shift Keys ; these accomplish the same as the keys with the same name on your keyboard.
• The View Keys have a special meaning in some CAD applications: They are used to realign an object you are handling into the given direction. If the check box Perform Automatic Fit is activated an additional fitting to the application's window size is performed.
• The Other Keys :
  • Fit adjusts the size of the scene to the size of the window.
  • 2D/3D enables and disables the transmission of rotational data.
• Wheel Assignment allows you to apply arbitrary functions to the wheel movement.

3.3.3.4 Assigning Functions to the Wheel

3.3.3.5 Assigning Functions to the Wheel Function Launcher

Fig. 3.15:  Function Assignment dialog with activated WFL Assignment configuration

3.3.3.6 Assigning Functions to the Cap

Fig. 3.16:  Function Assignment dialog with activated Cap Assignment

Fig. 3.17: W, A, S and D are the common control keys in shooter games

Fig. 3.18: Mapping W, A, S and D to the cap allows movement of characters with the SpaceController

3.3.3.7 Device Functions

• SpaceController,
• Mouse and
• Joystick.

3.3.4 The Wheel Function Launcher (WFL)

3.3.4.1 Using the Wheel Function Launcher

• Double click the function with the mouse,
• press the device's CTRL key,
  
• press the button Trigger or
  
• the WFL does this by itself when the Autotrigger Delay is not set to Infinite .

3.3.4.2 Configuring the Wheel Function Launcher

Fig. 3.19: Wheel configuration to open the WFL

Fig. 3.20: Configuring the WFL

3.3.5 Calculator and Number Pad

Fig. 3.21: Integrated calculator

Fig. 3.22: Integrated number pad

• "+ n % =": Adds n percent to the number displayed.
• "- n % =": Subtracts n percent from the number displayed.
• "* n % =": Multiplies by n percent the number displayed.
• "/ n % =": Divides by n percent the number displayed.

• How much are 1000 plus 25 percent?: "1000 + 25 % =" results in 1250.
• How much are 1000 minus 25 percent?: "1000 - 25 % =" results in 750.
• How much are 25 percent from 1000?: "1000 * 25 % =" results in 250.
• From how much are 1000 25 percent?: "1000 / 25 % =" results in 4000.

• STO: Copies the number displayed into the memory.
• RCL: Copies the memory into the display.
  
• SUM: Adds the number displayed to the memory.
  
• EXC: Swaps the memory and display.
  

• Add CR when pressing 'Send'
  This function is available only in the calculator mode; it modifies the Send button's behaviour slightly: If activated it sends not only the calculator's display's content to the foreground application but a carriage return character (CR) additionally. In many applications you can close an open input in this way.
• Use '.' as Decimal Separator
  If activated a decimal point is sent to the foreground application instead of a decimal comma. Some applications need the one or the other.
• Close Automatically
  Normally an input in progress will be closed by a carriage return character in an application, and you do not need the Number Pad any more. If activated the dialog will be closed when a carriage return character has been sent.
  

3.3.6 Menu Bar

3.3.6.1 File Menu

• Load Configuration .../Save Configuration/Save Configuration As ...:
  These items can be used to store and restore the device's configuration parameters to/from harddisk. The parameters are those presented in the Basic Settings sub-panel, the Advanced Configuration dialog and the Function Assignment dialog.
  
  
• Start Driver/Stop Driver:
  If the connection between the driver and the SpaceControl Panel is not established the panel assumes that the driver is not running and you can start the driver here. If there is a connection the menu item is greyed to prevent a second start of the driver. As the item says Stop Driver is used to stop the driver.
  
  
• Autostart Driver When User Logs In :
  This is a toggle menu item. If checked the driver will be started automatically as soon as the user logs in.
  
  
• Preferences :
  If activated the Preferences dialog will appear:
  
  
  
  
  
  Fig. 3.24: Preferences dialog
  
  
  
• • The Help Browser section lets you choose your favourite Web browser for displaying the help pages. If Use Default Browser is checked your operating system's default browser is used, if not you can search for another one and put its path into the Browser path field.
  • The user interfaces language can be set with the Language section. If Default is activated the SpaceControl Panel will open in the language your desktop is in.
    
  • The Look And Feel section allows the selection of your favourite SpaceControl Panel 's skin. The list is generated automatically out of the proposel delivered by the Java Runtime Environment and depends on the operating system.
    
  • The section Others assembles some more preferences:
    
    • If Start Driver with Panel is checked the SpaceControl Panel will start the driver automatically when started if it is not already running.
      
    • If Ask Before Exit is checked the SpaceControl Panel presents a message box before leaving the application.
    • If Readjust Dialog Size on Device Change is checked the SpaceControl Panel 's window adjusts its size when the user changes the device with an item of the Device menu. This is used to restore the default window size in case the user has changed it.
    • If Show Cap Data as Graphic is checked you see the white bars and arcs when moving the cap as shown in fig. 3.1.
    • If Show Cap Data as Digits is checked the numerical values of the sent data are shown below the device's picture.
    • If Show Tooltips is checked short help texts are displayed when the mouse cursor rests over a dialog's control element.
    • If Show "Tip of the Day" is checked a little hint is displayed when the SpaceControl Panel is started.
      
      
• Update Firmware ... :
  The SpaceController device contains three microcontrollers with their own software and a RAM chip with data for the display, which is together called firmware. From time to time we will publish firmware versions on our web site, downloadable as files.
  Clicking the menu item will show the Firmware Update dialog:
  
  
  
  
  Fig. 3.25: Firmware Update dialog
  
  
  For updating perform these two steps:
  
  • Click on the Select button and choose the firmware file.
  • Click on Start Update to load the new firmware into the device. This will last some minutes, the four bars in the dialog's lower area will show the progress.
  The actual firmware version is displayed in the SpaceControl Panel 's main window in the area Device Type .
  Update the firmware with the newest driver version generally if no other hint is given.
  
  
• Exit :
  Leaves the SpaceControl Panel and saves the preferences and the Control Panel's window size and position.
  

3.3.6.2 Device Menu

3.3.6.3 Help Menu

3.4 Loading And Saving Configurations

3.4.1 All Applications

3.4.2 Supported Applications

3.4.3 Special Handling for the Windows Explorer

3.4.4 Technical Notes for System Administrators

• Each user has its own configurations.
• Each device (in case more than one are connected) has its own configurations.
• All configurations are stored in files, not in the registry (due to compatibility with Linux and OS X).
  
• There are default configuration files.

3.5 Remote Control of Applications Over the Network

3.5.1 Overview

Fig. 3.26: Client/Server environment for remote control

• Client and server must run the same operating system. It is not possible for example to control a Windows server from a Linux client or vice versa. But different Windows versions on client and server are no problem.
• The remote control is working only if the application to control (respectively its plug-in) communicates with the driver over TCP/IP. But this is not the case for all applications: Creo, Google Earth, HiCAD, hyperCAD and Pro/Engineer e. g. are using an interface based on Windows messages and cannot be controlled in this way. In such cases it may be possible with third party software to transfer USB signals over the network rather than just IP packets; contact our support for this scenario.

3.5.2 Configuration on the Server's Side

1. Install the SpaceControl driver software:
   The driver is not needed for operation but the plug-ins and some DLLs must be installed.
2. Create the folder structure:
   The plug-ins expect a folder structure for their configuration files in "C:\Users\<username>\SpaceController\". The folders are created in a user's home directory when the driver starts the first time. The driver must be started therefore once on each user account.
3. Create configuration files:
   The configuration files described in the next section are created in the folder "C:\Users\<username>\SpaceController\" when the application starts (better said: when it ends) the first time. The application you want to control must be started and ended once therefore if the needed configuration file is not there.
   Furthermore our plug-ins (with the exception of the Universal Plug-in) create a so called MNU file when started the first time containing the menu commands of the application. This file has to be copied to all clients, see below.
   
4. Modify the configuration files:
   Which configuration file is needed depends on the application you want to control. Most of our plug-ins use the file "spc_ctrlr_dll.ini", but our Universal Plug-in uses the file "siapp_dll.ini". It is best to modify both of them: You just have to assign the IP address or the network name of the computer you want to control the application from to the parameter "ipv4Addr"; overwrite the old value "localhost".
   Samples:
   
   • ipv4Addr = localhost     # this is the default value and must be overridden by
     
   • ipv4Addr = saturn        # the network name of a computer "Saturn" e. g. or by
     
   • ipv4Addr = 192.168.30.74 # its IP address
     

3.5.3 Configuration on the Client's Side

1. Install the needed plug-ins:
   The plug-ins are not necessary on the clients, but we need the configuration files ("assembly.cfg", "part.cfg" etc.) to modify them with the SpaceControl Panel. These files are copied with default values to the client during installation.
   
2. Define the Remote Desktop Software:
   The driver should be prevented from sending data to applications not in the foreground. Running on the client, the driver can only detect if the local remote control software is in the foreground (not if an application on the server is in the foreground there) and can stop sending data to the server if not. You can let the driver know the binary name of your remote control software: Assign its binary name to the parameter "remoteSoftware" in file "daemon.ini". Suppress the file extension ".exe".
   Samples:
   
   • remoteSoftware =            # the default value is empty and must be overridden by a binary name
   • remoteSoftware = mstsc      # "mstsc.exe" is the binary name of the Microsoft Remote Desktop client
   • remoteSoftware = TeamViewer # "TeamViewer.exe" is the binary name of the TeamViewer client
   The driver reads the file "daemon.ini" only when it starts; you have to restart the driver therefore when the file is modified.
   
3. Copy the MNU file(s):
   When started the first time our plug-ins (with the exception of the Universal Plug-in) create a so called MNU file containing the menu commands of the application. This file has the extension ".mnu", is located in folder "C:\Users\<Username>\SpaceController\Applications\" and is needed by the driver and the SpaceControl Panel as well. Copy it into the same folder on each client.
   

3.5.4 Configuration of the Firewall

• The driver process on the clients is "sc_daemon.exe"; it is listening on port 31415 for communication requests from the plug-ins. (The port number can be changed in file "daemon.ini" if needed.)
• The plug-ins are normally DLLs and part of the applications to be controlled therefore. Their EXE files must be allowed to communicate; in case of Inventor its name is "inventor.exe" e. g., in case of NX its name is "ugraf.exe".

3.6 The C++ Application Programming Interface

3.7 The Java Application Programming Interface

4 Troubleshooting

5 Technical Data

6 System Requirements

• PC with x86 CPU
• 1 GHz clock rate
• 512 MB RAM
• 200 MB free harddisk memory
• Screen resolution >= 1024 x 768 Pixel (for the SpaceControl Panel )
  

• Windows XP to Windows 10, 32 or 64 bit
  
• Linux 32 or 64 bit.
  Driver version 2.8.0 has been tested successfully with Debian 7.8.0, Fedora 21, openSuse 13.2 and Ubuntu 14.04.1 LTS.
  Driver version 2.8.7 has been tested successfully with Debian 8.7.1 and Fedora 25.
  Driver version 2.8.8 has been tested successfully with Debian 9.1.0, Fedora 26, openSuse Leap 42.3 and Ubuntu 16.04.02 LTS
• macOS or OS X from version 10.8 on
  
• for requirements concerning the plug-ins see above
  

• Web browser for reading the documentation
  

7 Change Log

• Siemens NX 12 is supported (Windows).
  
• Due to an incompatibility in the SC DLL some plug-ins had decreased performance. These plug-ins are improved.
• In this context there is a new parameter "dllReadTimeout" in file "spc_ctrlr_dll.ini". If there is a stuttering movement in an application it should be set to 50.
  
• Detection of the foreground application is enhanced. The CAM software Vericut is working now therefore (Windows).
• The driver could crash while shutting down the computer if a device has been removed before.
  
• Minor bug-fixes.
  

• The right Ctrl and Shift keys has not been working in macros.
• The calculator did not calculate operations correctly immediately after the RCL or EXC key have been pressed.
  
• Blender plug-in enhanced; more devices than just one can be used simultaneously.
• There is an Universal Plug-in for macOS now.
• Universal Plug-in for Windows enhanced.
  

• Creo 4 is supported (Windows only).
• AutoCAD 2018 is supported (Windows only).
• 3ds Max 2018 is supported (Windows only).
  
• You can trigger a selected function in the Wheel Function Launcher by pressing the device's CTRL key now.
• In the Function Assignment dialog you can copy user functions with "copy and paste" now.
  
• Moving the cap with activated option Restore Mouse Position in dialog Advanced Configuration has crashed the driver under Linux.
• There is a new parameter deviceCheckingTime in file "daemon.ini". If its value is 5 e. g., the driver checks only for five second after its start if SpaceControl devices are connected or disconnected. The default value is 0; this means the check is always performed.
  (Meaning: The driver of the USB chip [FTDI] built into our device has a bug which may lead to interferences with other devices with a FTDI chip if the check is active.)
• Universal Plug-in enhanced.
  

• The 2D/3D key does not work reliably with a second function assigned to it. The driver has resetted the device and other strange effects could occur.
• The driver has prevented the screensaver from being activated when moving the cap, but not the system from going into sleep mode.
• When resuming from the computer's energy saving modes, the driver could crash sometimes.
• The Solid Edge plug-in could crash after executing Solid Edge's menu function "PMI/Section".
• The Catia plug-in uses ready-made MNU files now rather than creating them by itself.
  
• Under Linux FreeCAD versions newer than 0.14 are running again.
• Default configuration files for Blender enhanced (double press, "...-nonnormal.cfg" files available).
  
• New parameter "exclusiveAppl" in file "daemon.ini". If an application name is given here (mostly as shown in the SpaceControl panel's status line, in the other cases the application's binary name without the ".exe" extension) only that application will receive data, even if it is not in the foreground.
• Our entries in the PATH environment variable are added at the beginning and not at the end now. Otherwise it could happen that wrong (= older) GNU DLLs of the same name from other software have been loaded instead of our newer ones.
  
• New Java Runtime Environment version 1.8.0_121.
• When unplugging a device a deadlock could occur, causing a semi-crash of the driver.
  

• There is a shift level for the device's keys now. You can switch to it with the new device function "SwitchKeyShiftLevel". Alternatively you can trigger the second function on a key by double pressing it.
• The plug-ins are aware of the new device functions "Back", "Left" and "Bottom". By default they are assigned to the shift level (double press) of the keys FRONT, RIGHT and TOP.
  
• On some computers data has been sent to applications although not in the foreground.
  
• The menu item File/Stop Driver in the SpaceControl Panel will work now even if the driver does not react on commands anymore; the process "sc_daemon.exe" is killed in such a  case.
  
• Some minor bugs in the AutoCAD plug-in are fixed. There is a new "hybrid" mode in the plug-in; in this mode AutoCAD interprets the translation and rotation data by itself, the plug-in is only responsible for the device keys.
  
• Siemens NX 11 is supported. The NX plug-in can be run in a hybrid mode as well.
• Minor bugs in the Blender plug-in are fixed.
• A rotation center defined in Solid Edge for the normal mouse will be used by the SpaceController now.
  
• New GNU compiler version 6.2.0 used under Windows.

• New GNU compiler version 5.3.0 used under Windows.
  
• New Java Runtime Environment version 1.8.0_77.
  
• New Java 3D version 1.6.0.
• If the Mouse Movement is activated the sending of data to connected applications is suppressed now.
• 3ds Max 2017 is supported.
• AutoCAD 2017 is supported.
  
• Universal Plug-in improved (support for Tenado 3D added, TurboCAD is working again).
  
• The graphical demos tend to appear with an empty window when started under Windows 10.
• Under OS X 10.11 ("El Capitan") the driver did not start without tricks, and the built-in cube demo could not be stopped once started.
• Icons have no ugly white border any longer.
  

• Existing configuration files from version 2.8.1 and 2.8.2 have not been updated but replaced by new files with default values.

• The device can control applications on a remote server now. See section 3.5 for details.
  
• The plug-ins have the ability of remote control as well.
• A bug in the Blender plug-in is fixed.
  

• Some of the settings in our SolidWorks plug-in have not been saved when closing SolidWorks.
• The installer of the Siemens NX plug-in copies some additional DLLs.
• Some bugs in the Blender plug-in are fixed.
  
• Under Windows 10 the help browser could not be started under some conditions.
• Minor bug-fixes.
  

• Support for 3ds Max 2016 and 3ds Max Design 2016.
• Support for AutoCAD 2016.
• Blender plug-in enhanced, see readme file.
• Firmware update and its handling improved.
• Device pictures in the SpaceControl Panel updated.
• The device's lights remains off now even if the computer changes itself into the standby mode.
• Due to security reasons the driver daemon will accept connection requests only from the SpaceControl Panel of the same user.
  
• Installer improved; there is a "silent" mode for Linux now, see section 3.1.2.
• Changes in the OS X version:
  
  • Installer improved.
  • The foreground application detection did not work reliably with the SpaceControl Panel in the foreground.
  • The configuration files could get corrupted with two devices connected to the computer.
  • The lights are switched off now when the computer goes into sleep mode, and the device will be reinitialized when it wakes up.
  • Firmware update is working now.
    

• Firmware update is working now under Apple OS X.
• Various bug-fixes under Linux, among other things the Panel key and executing macros with the WFL is working now even with other desktops than XFace (KDE, Gnome).
• The macro function Execute only in case of state change works with the device keys as well now, not only with the cap deflections. See section 3.3.3.2.
• We have a plug-in for the DCC software "Blender".
• Plug-in for 3ds Max is improved, it integrates its own menu in 3ds Max.
• The NX Viewer is working again without editing the "daemon.ini" file.
  
• 64 bit applications compiled with Visual Studio 2012 could not load our Universal Plug-in when run on Windows 8.1. Because of a similar problem the plug-ins for Inventor and AutoCAD are recompiled.
  
• GNU compiler changed from version 4.7.1 to 4.9.2.
• Java runtime changed from version 7 to version 8.
• Linux and OS X driver are not in the beta state any longer and contain a plug-in for Blender as well.
  

• There is a new function scTransferCallbackFunction() in the C++ API. The callback function is to be defined by the user and called automatically as soon as new data is available from the device; it gets the actual device data packet in its parameters. It may spare you some thread handling needed when using scFetchStdData() instead.
• The Inventor Plug-in has a "hybrid" mode, and you can use the Universal Plug-in additionally to achieve higher performance. Ask our support for details.
• AutoCAD 2015 (64) and Inventor 2015 (64) could not load our plug-ins under Windows 8.1 (64).
• Creo 3.0 is supported.
  
• A beta driver for Apple OS X is available.
• Some bug-fixes in the beta Linux driver, e. g. the CPU load is much smaller now, the installer is enhanced.

• GstarCAD from Gstarsoft Co. Ltd. is supported. The plug-in is in beta state though, there are still some problems when refreshing the screen.
  
• The wheel shows in the Wheel Function Launcher and if moving sliders an acceleration now if moved fast. With the parameter "wheelAccelerator" in file "C:\Users\<Username>\SpaceController\daemon.ini" you can control the effect or switch it off again.
• The installer knows in its "silent" mode a new parameter "/P=<list of wanted plug-ins>" and the uninstaller a new option "/UF=delete". See section 3.1.1 for details.
• The plug-in for Siemens NX is updated, see Readme file there.
• There is a new function scRegisterCallbackFunction() in the C++ API. The callback function is to be defined by the user and called automatically as soon as new data is available from the device; it gets the actual device data packet in its parameters. It may spare you some thread handling needed when using scFetchStdData() instead.
  

• SpaceController "blackline" is supported.
• Help videos may be installed locally.
• Autodesk 3ds Max 2015 und 3ds Max Design 2015 are supported.
• The CAD/CAM software Tebis supports SpaceControl devices directly now:
  • The Universal Plug-in is not necessary any longer therefore.
  •  For older Tebis versions you have to enable our Universal Plug-in again by deleting line "tebis = tebis tebis" in files "siapp_dll.ini" and "daemon.ini". Both are located in folder  "C:\Users\<Username>\SpaceController\".
  • The available Tebis functions are integrated into the Function Assignment dialog. If you want to see these functions in German and not in English delete file "tebis.mnu" and rename file "tebis_de.mnu" to "tebis.mnu". Both files are located in folder "C:\Users\<Username>\SpaceController\Applications\". Do the same with the files "tebis.cfg" and "tebis_de.cfg" in folder C:\Users\<Username>\SpaceController\Devices\<SerialNo>\".
    
• The Universal Plug-in could not transmit data into the simulation window of Mastercam X7.
  
• The AutoCAD plug-in has been reworked and supports all move modes and AutoCAD 2015 now. If upgrading from older driver versions have a look at the AutoCAD plug-in's Readme file, please! You can find it in the Windows Start menu.
  
• Under Windows the SpaceControl Panel does not inspect the Java system property "user.home" any longer to get the user's home directory but inspects the environment variable "USERPROFILE" as the daemon does. This is changed because "user.home" points to a wrong location on some network installations due to a Java bug.
  

• Some special characters caused problems when sent to the device's display.
  
• The plug-in for Siemens NX is updated to version 2.6.1.
• The Universal Plug-in is working with Autodesk Revit again.

• When changing the foreground application it could happen that the old foreground application's configuration was transfered to the new foreground application's configuration. The former configuration was lost then.
• The driver has not been able to detect applications installed on network drives as foreground applications.
• Installer and uninstaller delivered the error code 1223 even in case of successful installation/deinstallation; now the correct value 0 is returned.
• The Catia plug-in has failed on some network installations to detect Catia's language setting. In consequence Catia's menu items could not be read and their assignment to the SpaceController's keys has not been possible.
• Our installer adds some new entries into the PATH environment variable. If getting longer then 1024 characters the installer wiped out the variable.
• The device's illumination is switched off after 10 minutes of inactivity now. This time can be adjusted with the new parameter "timeBeforeSleeping" in the driver's configuration file "daemon.ini".
  
• New compilation with updated development environment.
• New API functions scGetDaemonPar() and scSetDaemonPar().
• New plug-in for PTC Creo 1.0 and 2.0; it is a DLL now and does not delete Creo's undo buffer any longer.
• New plug-in for Siemens NX is available. This is a beta version yet. In case you observe non-tolerable bugs you can reactivate the former mechanism for using NX (without plug-in, no mode detection available therefore):
  • Uninstall the plug-in.
  • Open the file "C:\Users\<username>\SpaceController\daemon.ini" and remove the line beginning with "NX" in section [SUPP_APPLS].
  • Restart the driver.
    
• Linux driver is available.

• The new calculator has delivered wrong results in case of percent calculation in combination with the plus and minus operators.
• The plug-in for 3ds Max has not worked with 3ds Max Design 2013.

• A new SpaceControl command "HandleCalculatorNumPad" is implemented. It can be assigned to a key or the WFL. In this case a little dialog appears to send number characters to the foreground application. You can input numbers with your mouse in this way.
• In the same dialog you can find a little calculator. Calculation results can be sent to the foreground application as well.
• The wheel understands gestures now: By appropriate moving in left and right direction you can trigger functions if gesture detection is activated.
• There are two new events you can assign functions to in the Function Assignment dialog: "Cap movement started" and "Cap movement stopped" (i. e. "cap touched" and "cap released").
• In the Function Assignment dialog the check box Send Function Only in Case of Cap Changes affects all cap makros and events globally. Now you can configure this individually for each macro when adding the function Execute only in case of cap state change to the macro. You can find this function in the drop down list Other Key or Function.
  
• There are 64 free programmable User Functions (macros) now instead of the only 18 as used to be.
  

• Some bugs concerning the GEN and its illumination are fixed.
• The Wheel Function Launcher contains a function Pause now in its function list. It keeps the dialog open and does nothing. This enables you to change the settings in the dialog even if you have set a very short Autotrigger Delay.
• The default values in the configuration files are slightly modified. You can not modify the cap's function by accident any longer.
• The device type data can be copied with Ctrl-C from the GUI.
• The slider dialogs (device functions "HandleSensitivityDialog" etc.) did not work reliably sometimes when triggered by the WFL.
• With the new parameter "sendDelay" in the driver's configuration file "daemon.ini" you can avoid sending data too early to a new foreground application. SpaceClaim e. g. likes to crash in this case.
• All applications may use MNU files now. See the technical notes for details.
  
• SolidWorks plug-in is strongly improved.
  

• Our new, smaller device GEN is supported.
  
• Applications using a legacy communication protocol are detected now when coming into the foreground. The driver asks for enabling the old protocol.
• The driver can handle several devices concurrently now, a "Master" device is not necessary any longer.
• The driver informs supported applications now when they come into the foreground. The applications can react on this event and send the mode they are in e. g. (important if more then one instance is open).
• In the driver's configuration file "daemon.ini" some new parameters are used:
  • maxBytesInRxQueue:
    If this value is bigger than 0 after each of the device's handled data packet the receicve queue is read again (without handling the data) until the queue contains less bytes than or equal the value says. In some applications this mechanism can avoid a time lag in movement. Example: The data packet for the cap's standard data contains 15 bytes. If you set maxBytesInRxQueue to the value 45 the queue can contain three data packets at the most after releasing the cap.
    
  • sendMode
    This parameter controls how the SpaceController's data is distributed to the applications. The data is sent only to the foreground application as before or to all connected applications or to the application the mousepointer is over.
  • singleComPerAppl:
    "LegacyCom2" applications as Google Earth or Pro/ENGINEER connect themself to the driver to get data from the device. Pro/ENGINNER does this wrongly several times with bad impact to the performance. If this parameter is set to "on" the driver accepts only the first connection. If using Pro/ENGINEER this parameter should be set to "on" therefore.
  • blinkPeriod:
    The GEN's LEDs are blinking while the Wheel Function Launcher is waiting on input. Here you can set the time (in milliseconds) the LEDs are on and off respectively (i. e. the half period).
    
• Unused elements are not longer shown in the Wheel Function Launcher.
  
• The plug-in for Autodesk Inventor is improved. See the change log there.
• The plug-ins for Pro/ENGINEER are improved. See the change log there.
• The plug-in for Solid Edge is improved. See the change log there.
• The Universal Plug-in is improved, applications like CimatronE are supported now.
  
• Configuration files for Excel, Word, Outlook, Internet Explorer, Firefox, Opera and Acrobat Reader are delivered.
• Minor bug-fixes.

• A plug-in for AutoCAD 2013 is delivered (version 2.4.0 beta 1).
• The plug-in for Autodesk Inventor is strongly enhanced, see the change log there (version 2.4.0 beta 4).
• The plug-in for Catia is enhanced, see the change log there (version 2.4.0 beta 2).
• The plug-ins for Pro/ENGINEER are enhanced, see the change log there (version 2.4.0 beta 1).
• The plug-in for Solid Edge is enhanced, see the change log there (version 2.4.0 beta 2).
• The Universal Plug-in is enhanced, see the change log there (version 2.4.0 beta 6).
• The driver is unchanged, only the plug-ins are replaced by the versions listed above.
  

• The Universal Plug-in is enhanced, applications like Alibre Design are supported now.
• The plug-in for Catia is improved. See the change log there.
  

• The SpaceControl Panel 's main dialog is slightly redesigned.
  
• The most sliders in the SpaceControl Panel 's main dialog are displaced into the dialog Advanced Configuration .
  
• New fields ORG, CAM and WFL in the display's status line are available. Attention: These fields will be displayed only with a firmware from version 2.141.141.130.0 on. Update your firmware if necessary.
  
• There is a new button Video on all dialogs; pressing it opens your Internet browser and shows a short video explaining the dialog.
• The cap's characteristic is changed from quadratic to cubic. In the configuration file "daemon.ini" you can choose between different cap functions with parameter "capCharacteristic"; the value 6 is the one of former versions.
  
• Date and time will be displayed reliably again on the device's display.
• Firmware update reworked.
• The plug-ins for Solid Edge and Catia are significantly improved. See the change log there.
• Plug-in for AutoCAD 2012 is delivered with the driver.
  
• After returning from standby or hibernate mode the foreground application was not detected by itself and the configuration not loaded therefore.
• While triggering a function with the WFL and nearly concurrent changing of the foreground application the configuration of the new foreground application could be lost.
• The device functions LoadConfiguration_x can now be triggered by the WFL.
  
• Minor bug-fixes.
  

• Converting the configuration files from version 2.0.0 to 2.2.1 caused a crash.

• API functions scConnect() and scSetState() replaced by scConnect2() and scSetState2() . See the API documentation for details.
• The built-in cube demo supports all move modes now (object mode, camera mode etc., see section Move Mode).
• New device functions ToggleObjectCameraMode , ToggleScreenOriginRotation , ToggleLockHorizon , ToggleHover .
• Recorded key sequences may consist of up to 42 key presses now.
• The SpaceController keys may be recorded in macros and can be combined in this way.
• The Display can show the SpaceController's device functions in German as well now.
• If the driver is updated your own settings will be preserved now. This works for configuration files from driver version 2.0.0 on.
  
• Autodesk 3ds Max is supported.
  
• Minor bug-fixes.

• The new Wheel Function Launcher allows you to trigger functions with the silver wheel too.
• The Advanced Configuration dialog allows you to configure the device for using it with the right hand.
  
• If the checkbox Restore Mouse Position is activated in the Advanced Configuration dialog the mouse pointer's position is restored not only when the cap is released, but also when the mouse pointer reaches the screen borders.
• A second instance of an application has not been detected as foreground application, the cap data has been sent still to the first instance.
• LEDs and LCD are switched off when the driver is stopped or the system goes down into standby or hibernate mode.
• Moving the cap will stop the screensaver and prevent it to be activated.
  
• Detection of Pro/ENGINEER Wildfire 5 and creo as foreground application did not work reliably.
• The user interface can be switched between English and German now.
  
• New test mode for internal production tests implemented.
  

• Driver and all plug-ins are combined in one big installation program.
• Even if some instances of the same application are started, only the foreground application of this group will get data from the SpaceController.
• Eventual graphics card driver problems do not prevent the SpaceControl Panel from starting.
  
• Internal changes due to a new compiler version.

• Displaying the foreground application's name in the device's LCD works again.
• Firmware update routines rewritten.
• Bug in writing configuration files fixed.
• The function editor swallowed the next key event after pressing the Alt key.
• When using a German Windows the German user manual is opened.
  
• With most browsers the user manual opens reliably in the right section now when pushing the Help button in a dialog; unfortunately the Internet Explorer has a bug preventing this.
  

• The user manual is available in German now.
• A configuration file loaded by hand is displayed in the LCD now correctly.
  
• A bug in starting the correct version of the plug-in for Pro/ENGINEER is fixed.

• The driver is aware of our new AutoCAD plug-in.
• Minor bug-fixes.

• Occasionally the SpaceControl Panel was not able to connect to the driver again if it was stopped and restarted.
• German umlauts are allowed now in user function names.
• Deleting of the users' configuration folders when deinstalling the driver works now also with Windows Vista and Windows 7.
• The device's illumination can be switched off and on by pressing the "Ctrl" and "Panel" keys concurrently.
• The rotation center can be adjusted within the Advanced Settings dialog if supported by the CAD application.
  
• Some further bug-fixes.
• Attention:
  This version is not compatible with plug-ins prior to version 1.4.0.
  Older plug-ins must be run with drivers <= 1.3.0 beta (note: version 1.3.0 beta is an unpublished release).
  Configuration files created with driver versions less than 1.4.0 can not be loaded by versions 1.4.0 and greater due to some new parameters.
  

• Functions with German umlauts could not be displayed on the SpaceController's display, in succession the device was a little noncompliant to update its content.
  
• The SpaceControl Panel closed itself occasionally when the device was plugged into the USB socket.
  Both bugs were built into the software in the course of the 64 bit modifications and are fixed now.

• The driver is aware of 64 bit plug-ins now.
• The process "dwm.exe" is ignored as foreground application. This invisible process is casually put into the foreground by Autodesk Inventor and caused a heavy bucking because the driver loaded another configuration then.
  

• Support for SolidEdge added.

• Some applications (e. g. Siemens NX ^® ) were unable to execute the user functions recorded with the Function Editor described above. It works now.
• The parameter "rememberLastCfg" in the daemon.ini file did not work properly.
• Autodesk Inventor versions prior to Inventor 2008 will work without plug-in if the parameter "allowInventor" in the file "daemon.ini" is set to "on" (cap movement only, no mode detection, no integration of menu functions into the Key Configuration dialog). For Inventor 2009 and later this parameter must be set to "off".
• There is nearly no delay any longer in object movement when changing a configuration.
• Under certain conditions it could happen that sending data from the device after changing a configuration stopped, because the "Send Delay" parameter in the Advanced Settings dialog switched to 405 ms (= data sending off). This is fixed.
  
• Minor bug-fixes.

• After a power resume it could happen that the driver must be restarted to work properly again. This is fixed.
  
• Minor bug-fixes.

• First published release.

8 Known Bugs

• If the SpaceControl Panel is started from "within" the driver (i. e. by double click on the tray icon or by pressing the PANEL key on the device) and the driver is stopped and restarted again it may happen that the SpaceControl Panel and all other applications or plug-ins are not able any longer to establish a connection to the driver. The SpaceControl Panel must be closed to cure this.
  To avoid this you can start the SpaceControl Panel with the entry in your Windows start menu.
  
• Under certain conditions it may still happen that the SpaceControl Panel 's sliders and other control elements flicker if the in-built cube demo tab is open. The menus are not usable in this state. See the entry in the troubleshooting section.
• Awakening from power resume seems not to work reliably in all cases. Unfortunately we cannot improve this because the driver of the USB chip in our device is responsible for the misbehaviour.
  

9 Trademarks

Author: Friedemann Seebass Copyright © SpaceControl GmbH & Co. KG, Am Technologiepark 10, 82229 Seefeld, Germany