Log Pane
Last updated
Last updated
The status Log pane displays important events or statuses of the camera system operation. Events that are actively occurring are shown under the Current section, with all of the logged events saved in the History section for the record.
Open the status Log pane from the View menu or by clicking the icon on the main toolbar.
Status messages are categorized into five categories: Informational, Warning, Error, Critical, and Debugging. Logged status messages in the history list display in chronological order by default. The log history can be sorted by any field by clicking the column header. The sorted column is indicated with a cyan header.
Symbol Convention
Peripheral Devices: Attempting to add a device with an already existing serial number.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Peripheral Devices: Device reported a different number of attached devices than were created.
Troubleshooting steps:
Check hardware configuration and make sure all is setup correctly.
Contact support for the affected peripheral device (e.g., AMTI force plate).
Peripheral Devices: Plugin does not contain the required creation functions.
Troubleshooting steps: Try reinstalling peripheral DLLs and plugins.
Peripheral Devices: Unable to start plugin device because there are no active channels enabled on the device.
Troubleshooting steps: Contact support for the affected peripheral device (e.g., AMTI force plate).
Peripheral Devices: Unable to start collecting from plugin devices. Devices are present but not enabled.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Peripheral Devices: Motive attempted to start device collecting but the previously available device(s) are no longer present.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Peripheral Devices: A plugin device with the specified serial number was removed or is no longer responding.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Peripheral Devices: Plugin DLL {File Name} has been loaded.
Troubleshooting steps: Informational only. No troubleshooting required.
Peripheral Devices: No plugin devices were loaded.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
The plugin device object for an external device (e.g., force plate or NIDAQ) has been successfully created.
Troubleshooting steps: Informational only. No troubleshooting required.
The plugin device has been registered in Motive.
Troubleshooting steps: Informational only. No troubleshooting required.
Peripheral Devices: The specific device was removed.
Troubleshooting steps: Informational only. No troubleshooting required.
Peripheral Devices: The peripheral device requires manual channel enabling before recording.
Troubleshooting steps:
Check Ni-DAQ channels and make sure they are enabled.
Make sure connections to the NI-DAQ are correct.
Peripheral Devices: A Plugin device was detected, but Motive was unable to add it.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Peripheral Devices: The peripheral device manager was unable to find a required function in the device plugin dll.
Troubleshooting steps:
Check that the plugin was installed correctly.
Test on another machine.
Peripheral Devices: The peripheral device manager was unable to find a required function in the device plugin dll.
Troubleshooting steps: Make sure the device plugin peripheral DLL was installed during Motive installation.
Peripheral Devices: The peripheral device manager encountered an error when unloading a the device plugin dll.
Troubleshooting steps: Contact Support for further troubleshooting.
Peripheral Devices: The peripheral device manager was unable to find the unload function from the plugin device dll.
Troubleshooting steps: Contact Support for further troubleshooting.
Peripheral Devices: The peripheral device manager was unable to unload the plugin device dll.
Troubleshooting steps: Contact Support for further troubleshooting.
Camera System: A mocap camera or other OptiTrack device (e.g., an eSync) was disconnected from the system.
Troubleshooting steps:
Try replacing the cable or device if possible;
Connect to another port on switch or PC;
Try connecting the device (e.g., an eSync) directly to the aggregator switch and auxiliary power;
Make sure the correct power adapter is being used.
Camera System: A mocap camera dropped a frame of data, either because of incomplete packet delivery, buffer overflow, or it was not able to provide the frame in the time required to be part of the current frame group.
Troubleshooting steps:
General networking troubleshooting;
Check if PC specs are sufficient for system;
Check if Windows background processes are causing any interruption;
Monitor system performance using the Windows Task Manager;
Validate if the dropped frame was in 2D or 3D. Data can be reconstructed in Edit mode unless 2D data is missing.
Peripheral Devices: The peripheral device manager encountered an error while attempting to stop a peripheral device.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Camera System: the delivered frame group is missing a frame from one or more cameras.
Troubleshooting steps:
General network troubleshooting;
Identify if there is a faulty camera;
Disable any managed features on the switch.
Peripheral Devices: Devices was set to hardware sync, but no eSync was present.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Peripheral Devices : Device did not restart after configuration.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Peripheral Devices : Unable to start peripheral device collecting.
Troubleshooting steps: Check hardware configuration and make sure all is setup correctly.
Camera System: A specified camera's current frame ID is more than the default buffer size's (100 by default) frames difference from the group.
Troubleshooting steps: General networking troubleshooting.
Camera System: The camera frame group synchronizer's queue is full and is unable to add a new frame group to the queue, so it is delivering a partial frame group instead.
Troubleshooting steps: General networking troubleshooting.
Camera System: The eSync dropped a frame of telemetry data.
Troubleshooting steps:
Check that eSync settings are correct for the setup;
Confirm that the eSync is plugged in correctly;
Verify sync source signal is strong and the volume is up.
Camera System: The current camera frame group is older than the previous camera frame group (out of order).
Troubleshooting steps: Contact Support for further troubleshooting.
In general, when there are no errors in the system operation, the Current section of the log will remain free of warning, error, or critical messages. Occasionally during system operations, the error/warning messages (e.g., Dropped Frame, Discontinuous Frame ID) may pop-up momentarily and disappear afterward. This could occur when Motive is changing its configuration, for example, when switching between Live and Edit modes or when re-configuring the synchronization settings. This is a common behavior and does not necessarily indicate system errors as long as the messages do not persist in the Current section. If the error message persists under the Current section or there is an excessive number of events, there may be an issue with the system operation.
To export the log history to a text file, click the button at the top left of the log pane. Open the file in Notepad or the text editor of your choice. The file can also be opened in Excel.
To reset the log history, click the button in the upper left corner of the log pane.
: Informational
: Warning
: Error
: Critical
: Debugging
Informational messages are noted with the icon.
Error messages are noted with the icon.
Critical messages are noted with either the or the icon.
