Spatial Reference Manual
Page 64 of 158
Version 4.4
04/06/2019
Added heave offset dialogue
Firmware date added to firmware update dialogue
Minor changes
2.0
22/10/2012 Added odometer configuration dialogue
Added log converter tool
Spatial Manager will now disconnect automatically if USB
serial port is removed
Firmware update will now change the baud rate
automatically when entering bootloader mode
Alignment configuration dialogue updated
1.0
16/09/2012 Mac disconnect issue resolved
0.5
23/08/2012 Initial Release
Table 16: Spatial Manager software changelog
11.2 System Requirements
The software includes a 3D mapping display which requires a modern 3D graphics card
and up to date drivers to run. If your machine does not meet the graphics
requirements the mapping view will only show space without a globe.
When Spatial is running at very high output rates e.g. 1000 Hz, Spatial Manager can
consume significant system resources handling the large quantity of data.
11.3 Installation
Spatial Manager does not need to be installed and can be run from any directory by
double clicking on it. Spatial Manager requires a recent version of Java, available at
. On some systems to open the program it may be necessary to
right click and select open with → Java Runtime Environment.
Both the Spatial evaluation kit and the Spatial OEM development kit make use of an
FTDI USB device. The drivers are normally installed automatically, if not they are
available from
http://www.ftdichip.com/Drivers/VCP.htm
11.4 Troubleshooting
if you are having issues.
11.4.1
All Platforms
If the globe does not appear in the 3D map area, this indicates that either your
graphics card is not powerful enough or your graphics card driver is out of date.
11.4.2
Windows
There is a well known problem with USB serial devices under Windows known as
“crazy mouse”. The problem occurs when the system mistakenly installs the USB
serial device as a mouse. Unfortunately Microsoft has not fixed this problem in over 15
years, so it probably won't be fixed. If you experience this problem, often a restart will