General Troubleshooting
Animation overrider continues playing when shut down or when motors are frozen. An additional script must be installed into your AO to signal that kinematics should be terminated. The OpenCollar link script is a GPLv2-licensed implementation that is compatible with all versions of Companion and ATOS, and recognizes AOs from Oracul, Zhao, Vista, Akeyo (including Nitro), Gaeline, and Huddles. Compatibility with Firestorm's built-in AO can be enabled by searching for 'LockMeister' in the viewer's Preferences window.
permalink
"Not found: <command>" but command still works. The 'not found' message is generated in response to the command used being missing from the command index. The message can usually be eliminated by simply typing commands reindex over the remote console, or @commands reindex locally.
permalink
"Controller missing; pinging..." after teleport. Relog and remove all other attachments that share the same attachment point as your controller. Despite this and other documentation, SL simulators will sometimes fail to transfer attachments correctly if they are attached to overloaded attachment points.
permalink
Missing vox filters. Most commonly experienced by ATOS/E users when the 'noise' filter fails to load after receiving damage. Type @vox probe to re-detect missing filters.
permalink
Obtaining emergency self access. In dire situations, the unit may reset its power systems and gain basic access to its own systems by saying the following command: @safeword. This adds the unit to its own user table (if necessary), instructs the power manager to enter full draw mode, and enables self access. The unit’s owner will be immediately notified that this has occurred. This command cannot be entered by a user, only the unit itself.
permalink
Restoring the unit when it runs out of power. See Power overview for instructions on replenishing the battery under emergency conditions.
permalink
Removing inactive or deceased owners. To reset the unit’s user list, instruct it to say the following: @keychain reset. This will restore it to default factory ownership settings (i.e., self-control.) The previous owner’s account will be notified.
permalink
Removing the controller. When the unit is powered on, magnetic safety bolts hold the controller in place. By default, these automatically disengage when the unit is powered down, but they will remain active if the unit is configured to auto-lock (with a PIN code) or is locked with a PIN code when it is shut off. To remedy the issue, disable bolts from within the manage menu, and ensure that auto-locking is disabled under the manage > policies > access menu.
permalink
Checking for software updates and installing them. See Managing packages and installed software for information on installing and updating software.
permalink
Ensuring the battery is correctly positioned. Starting with generation 3 batteries (sold or replaced after February 11, 2017), all power cells have automatic positioning. Place the battery on the ground and use the Edit Tool to adjust the number in its object description, then re-insert the battery. The default value is -0.334. The ideal value is a function of the unit's chest depth. Due to an oversight, the NS-409 Nightfall does not support battery auto-positioning in Companion 8.4, so batteries will have to be manually positioned when using this controller. Third-party controllers will require similar treatment.
permalink
Preventing lighting elements from turning an unwanted color (especially black) after executing the ‘rainbow’ sample action or similar. This is caused by an improper value (or no value) stored for the unit’s permanent color. Devices such as the NS illumination control panel only set the unit’s accent color temporarily. To store a permanent color, type color save over the remote console (or have the unit perform the equivalent @color save) once it has been set. Alternatively, the manage :: identity :: color prompt in the menu system will always set the permanent accent color. This should also resolve issues with inconsistent coloring of the screen following module resets.
permalink
Fixing stuck subsystems. In rare cases following charging, or when recovering from a period of low power, the unit may still have certain subsystems powered off. Use the status main menu item on the local panel or TTY access (or the remote command power) to determine which subsystems are disabled—or, if no subsystems appear to be disabled, use the chart on Subsystems and their management to diagnose which subsystems have entered a powered-down state unexpectedly. Then, toggle the subsystems until they regain normal behaviour via the subsystems menu or with the command power <subsystem>, where <subsystem> is the name of the affected component. If the subsystem is listed as disabled, one toggle should suffice; if it is not, then it will be necessary to toggle it twice.
permalink
Charging-related issues. The controller deliberately powers down certain subsystems during charging to accelerate the regeneration process. If a charger malfunction occurs, and your unit remains unable to move or speak freely, reset the bonds and power modules in the manage > modules menu. Logging out and then logging back in should also clear issues with stuck restraints.
permalink
Interference-related issues. If the unit reports that a fault has been detected in one or more of its subsystems, it may appear to behave as though these subsystems are disabled. These anomalies in function, called interference, are a result of exposure to improperly shielded electromagnetic sources that are not compliant with FCC guidelines. Depending on the severity of the interference, the subsystems may remain disabled for up to an hour after the unit is removed from the vicinity of the source of the malfunction. If it is absolutely vital to clear the malfunction in a more timely manner, resetting the bonds module in the manage > modules menu, or with the @reset <module> command, and then rebooting the unit is generally adequate to fix the behavior.
permalink
Vision remains obscured after controller is removed. Reattach and remove the controller again to properly reset the host unit’s vision processors.
permalink
Fatal error in task management: cannot find library for task -1. This is caused by software that requires Companion 8.5.0 or later running under a version of Companion 8.4. It is normal to see this message when performing a system update. Make sure your operating system is up to date by following the instructions at the Updating FAQ page.
permalink
Name or serial number reset to NS 100-00-0001. This is a known issue under Companion 8.5. Use the about command and then reboot the unit.
permalink