Motus Manager Software Changelog

Version	Date	Changes
7.3	11 Apr 2024	Improved usage and syntax information in the command line help Added support for more GPIO functions during log conversion Added command line argument to connect to the device on launch Added argument to open the Manager window maximised Updated device information window to show "BOOTLOADER" when applicable to software version
7.2	10 Nov 2023	Clear map history on reconnection Fix incorrect timezone text displayed in terminal.csv Updated leap-seconds list URL Add automatically log configuration at the start of a new log Fixed indicators behaviour on disconnect Updated support for Mac silicon with latest macOS Added support for extra NMEA 0183 messages Removed GNSS status indicator Fixed issue with opening windows containing charts Renamed External GNSS Enabled to Internal GNSS Enabled In satellites window, only populate azimuth and elevation fields in the table view when the values have been determined Added elevation to the gimbal state packet
7.0	13 February 2023	Updated from JDK8 to JDK11. JRE11/JDK11 required to run this release Refresh Port Mode information on reconnection Refresh Packet Rates information on reconnection Improved reliability of firmware update When the NTRIP sourcetable says authentication type is any of '', 'B', 'N', then use Basic Authentication. This is to workaround NTRIP servers that incorrectly populate the authentication field Overwrite/clear existing packet rates on import of configuration Added support for ARM (aarch64) processors with 64-bit OS Added support for Apple M1 processors and improved MacOS support Various UI improvements
6.2	10 October 2022	Added support for NTRIP Casters that request Username & Password to retrieve source table Added copying version numbers etc from Device Information dialog boxes Renamed Log Conversion menu item Added Settings menu item Renamed position error to position standard deviation in position page of view menu
6.1	18 February 2022	Device information updated automatically after a firmware update Fixed configuration export Add ability to control log file location Included software version number in title Improved NTRIP server reconnection Improve export configuration reliability Added external GNSS Filter option Improved Log files saved by default in the directory from where the application is launched Improved NTRIP mountpoint selection. Added handling of nonstandard NTRIP server responses Force the device to exit bootloader mode if a firmware update is not in progress

Motus Manager Software Changelog

System Requirements

Motus Manager is only available for systems with x64 and ARM architectures.

Motus Manager includes a 3D mapping display which requires an internet connection. If your machine does not meet the graphics requirements the mapping view will only show space without a globe.

Note, when Motus is running at very high output rates e.g. 1000 Hz, Motus Manager can consume significant system resources handling such large quantity of data.

Installation and Starting

The latest version of Motus Manager can be downloaded from the Motus product page of the Advanced Navigation website. Installation notes are as follows:

• Java 11 is required to run Motus Manager.
  Adoptium JRE 11 is the recommended Java installer to be used on all platforms. Install the latest version of Java 11 from Adoptium, selecting the correct operating system and architecture for your computer.

• No installation process required for the Motus Manager application on a Windows system — it can be run from any directory by simply double clicking on it. To open the program on some systems it may be necessary to right click and select open with → Java Runtime Environment.

• On MacOS systems it may be necessary to run the application from a terminal window:
   java –jar -XstartOnFirstThread MotusManager.jar

• On Linux systems it may be necessary to run the application from a terminal window:
  java –jar MotusManager.jar

The Motus Evaluation Kit includes an FTDI USB to adaptor cable. The drivers are normally installed automatically, but if not they are available for download from www.ftdichip.com/Drivers/VCP.htm.

Troubleshooting

If the application will not start, the most common reason is that you have 32-bit Java installed on a 64-bit operating system. Uninstall Java and reinstall the 64-bit version.

If the globe does not appear in the 3D map area, this indicates that either your graphics card is not powerful enough, your graphics card driver is out of date, or you have no internet connection.

• Ensure the RS232 / RS422 switch is in the correct mode. The Motus factory default mode is RS232.
• Ensure you select the correct COM port. This can be easily identified by unplugging and re-plugging in the USB connector.
• Ensure you have the correct baud rate selected in Motus Manager. The factory default value for the baud rate is 115200 bps for the Primary, GPIO and Auxiliary ports.

Contact technical support support@advancednavigation.com if you have any questions or require further assistance.

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. If you experience this problem, often a restart will resolve it. Otherwise there is a tool that can fix this issue available at
http://www.stentec.com/anonftp/pub/wingps/pnpblockersetup.exe.

If the serial port does not show up when you plug in the FTDI USB to RS232/RS422 adaptor cable, you may need to install the drivers from www.ftdichip.com/Drivers/VCP.htm.

When operating Motus on Windows at a high data rate, data can be lost due to the latency of the FTDI driver. To resolve this problem the latency of the driver should be reduced to 1 ms:

1. Start the Windows Device Manager (1) and find the Ports section (2).
2. Identify the specific COM port being used (3) by dis-connecting and re-connecting the USB to RS232 / RS422 adaptor cable.
3. Right click on the identified COM port and select Properties. Select the Port Settings tab (4) and select Advanced (5).
4. Change the Latency Timer value (6) to 1 msec then press OK (7), and OK again for the previous window. 

Linux

If serial ports do not show up, the typical reason is a lack of permissions. The user should add themselves to the dialout group with the command:

sudo adduser username dialout

Compiz causes issues with the 3D mapping. If you are experiencing problems it is recommended to turn off Compiz.

Modemmanager can also sometimes cause problems on Linux installations. If you are not using a modem, it is recommended to remove modemmanager with the command:

sudo apt-get remove modemmanager