Nanite systems DAX/2 User manual

DAX/2
The DAX/2 System –Version 8.0.5
Recreational Cybernetics Group
Copyright © 2015 Nanite Systems Corporation

Document revision 1.0.1
Copyright © 2015, Nanite Systems Corporation. All rights reserved.
Questions? Comments? Send us your feedback!
S. Wright, Chief Technology Officer, Civilian Products Division
T. Peluso, Chief Executive Officer
425-822-5252
[email protected]
Nanite Systems Coghaven Branch
1 Santei Place, Coghaven
216.82.49.11
Agni, California

Table of Contents
End-user license agreement (US) 4
Important safety information 5
General safety instructions ............................................5
FCC RF exposure information .........................................5
Cyborg operation....................................................... 6
For your safety........................................................... 6
FCC part 15 class B compliance................................ 6
Robot ethics notice.........................................................6
1Introduction and setup 7
2Power overview 8
Working with batteries ..................................................8
Power control..................................................................8
Replenishing the battery ................................................9
Low power ....................................................................10
3Subsystems and their management 11
4Personas 12
What personas can do .................................................12
Creating new personas ................................................12
Installing personas .......................................................13
Extending the preconfigured message set ..................13
5Applications 14
Creating new applications ...........................................14
6Devices and Peripherals 15
Active devices...............................................................15
Passive devices.............................................................15
Creating new devices...................................................15
7Remote access 16
Connecting to a unit .....................................................16
Scanning nearby units without connecting .................16
Sending a public announcement..................................16
Issuing a command to a single unit .............................16
Working with terminal mode .......................................17
Accessing the TTY menu remotely...............................17
Hiding and closing the remote management console.17
8Understanding what your DAX/2 experiences 18
Cortex commands.........................................................18
Cortex bypass commands.............................................18
Understanding the vocoder pipeline............................19
Released speech ..........................................................19
Self access and local command execution..................20
9Managing packages and installed software 21
10 User management and access control 22
Adding a new user .......................................................22
Creating a manager......................................................22
Removing a user...........................................................22
Transferring ownership ................................................22
Abandoned units ..........................................................22
Local access control .....................................................22
Remote access control .................................................23
Self access control .......................................................23
Locking..........................................................................23
11 Miscellaneous preferences 24
12 OEM data files 25
13 Sound 26
Voice notifications........................................................26
Chimes ..........................................................................26
Fan control ....................................................................26
14 Scripting actions with Arabesque 27
15 Understanding the SXD software architecture 29
Functions by component...............................................29
Packages.......................................................................31
16 Troubleshooting 32
A1 Installing data files 34
A2 Command reference 35

The DAX/2 System –Version 8.0.5
4
End-user license agreement (US)
By operating the hardware included in this package you agree to the following terms. If you do not agree to these terms, you
are not permitted to install, use, or modify the DAX/2 system. If you reject these terms within fourteen (14) days of your pur-
chase, you may contact Nanite Systems (hereafter “the company”) at 425-822-6008 to inquire about a full refund of the pur-
chase price of the hardware. If you purchased the unit at retail, your right to return the hardware is subject to the retailer’s
return policy.
Customization. You are allowed to modify or replace the housing of your controller at your leisure provided the circuit
boards and other electronic components inside (other than the screen and external panel) are unaltered. If at the time of a
warranty claim it is obvious that the controller’s circuitry has been damaged as a byproduct of customization, the company
reserves the right to refuse maintenance or replacement.
Reverse engineering and piracy. The company makes every effort to provide a customizable, extensible, and well-
documented platform for creative users and developers to enjoy. However, with the exception of certain modules based on
GPL-licensed code, the firmware itself is not open source and is not meant to be used on hardware other than official Nanite
Systems controllers or those sold by our partners under license. By using the DAX/2 system, you agree to not exploit undoc-
umented internal functions, to not develop interoperable controller hardware that runs the SXD firmware, and to not collect
or distribute any instrument or instructions to enable others to do so.
Software modification. You are permitted to extend, modify, and replace the firmware on your device for your own per-
sonal use, as well as to load any user applications onto the device for any reason. You agree not to hold the company re-
sponsible for any direct, indirect, consequential or special damages resulting from the use of unfinished (“beta”) or third-
party software.
Limited warranty. The company agrees to provide service, upgrades, and replacement parts for your DAX/2 for a period
not less than 10 years after its date of purchase. This service does not cover damage resulting from misuse of the device,
unlicensed maintenance, or Force Majeure.
Limitations of liability. You agree not to hold the company responsible for any direct, indirect, consequential or special
damages resulting from misuse of the device.
License limitations. You understand that your license to use the hardware may be revoked at any time by the company
due to breach of contract.
Alterations. The company reserves the right to change this agreement at any time with suitable notice to the user.
Term and termination. This agreement comes into effect once you install, use, or modify your DAX/2 unit. The company
reserves the right to terminate the agreement at any time without notice at its sole discretion.

The DAX/2 System –Version 8.0.5
5
Important safety information
THIS APPLIANCE CAN BE USED BY CHILDREN AGED FROM 8 YEARS AND ABOVE AND PERSONS WITH REDUCED PHYSI-
CAL, SENSORY OR MENTAL CAPABILITIES OR LACK OF EXPERIENCE AND KNOWLEDGE IF THEY HAVE BEEN GIVEN SU-
PERVISION OR INSTRUCTION CONCERNING USE OF THE APPLIANCE IN A SAFE WAY AND UNDERSTAND THE HAZARDS
INVOLVED. CHILDREN SHALL NOT PLAY WITH THE APPLIANCE. CLEANING AND USER MAINTENANCE SHALL NOT BE
MADE BY CHILDREN WITHOUT SUPERVISION.
CAUTION: DO NOT EXPOSE THE ELECTRONICS OF YOUR ROBOT, ITS BATTERY, OR THE CHARGING PLATFORM. THERE
ARE NO USER SERVICEABLE PARTS INSIDE. REFER SERVICING TO QUALIFIED SERVICE PERSONNEL. PLEASE ENSURE
VOLTAGE RATING FOR THE CHARGER PLATFORM MATCHES STANDARD VOLTAGE IN YOUR AREA.
Notice: Your robot contains a software interface for the purpose of enabling the manufacturer to provide updates to the
internal firmware if any such updates are made available to users. Any attempt to access, retrieve, copy, modify, distribute,
or otherwise use any of the robot software is strictly prohibited. Always exercise caution when operating your robot. To re-
duce the risk of injury or damage, keep these safety precautions in mind when setting up, using and maintaining your robot:
General safety instructions
Read all safety and operating instructions before operating your robot.
Retain the safety and operating instructions for future reference.
Heed all warnings on your robot, battery, charger, peripherals, and in the owner’s manual.
Follow all operating and use instructions.
Refer all non-routine servicing to Nanite Systems.
FCC RF exposure information
In August 1996, the Federal Communications Commission (FCC) of the United States, with its action in Report and Order FCC
96-326, adopted an updated safety standard for human exposure to radio frequency (RF) electromagnetic energy emitted by
FCC regulated transmitters. Those guidelines are consistent with the safety standard previously set by both U.S. and inter-
national standards bodies.
The design of this phone complies with the FCC guidelines and these international standards.
CAUTION: Use only the supplied and approved radio antennas. Use of unauthorized antennas or modifications could impair
communications quality, damage the unit, void your warranty and/or result in violation of FCC regulations. Do not use the
unit with a damaged antenna. If a damaged antenna comes into contact with skin, a minor burn may result. Contact your
local dealer for a replacement antenna.

The DAX/2 System –Version 8.0.5
6
CYBORG OPERATION
This device was tested for typical body-worn operations with the base of the controller kept 1 cm (0.39 inches) away from
the unit’s organic body. To comply with FCC RF exposure requirements, a minimum separation distance of 1 cm (0.39 inches)
must be maintained between the unit's body and the front of the controller. Third-party connection platforms, sockets, and
similar accessories with metallic interconnect shields may not be used.
FOR YOUR SAFETY
Cybernetic-organic modification kits that cannot maintain 1 cm (0.39 inches) separation distance between the unit's organic
body and the base of the controller, and have not been tested for typical body-worn operations may not comply with FCC RF
exposure limits and should be avoided.
FCC PART 15 CLASS B COMPLIANCE
This device complies with part 15 of FCC rules and ICES-003 Class B digital apparatus requirements for Industry Canada.
Operation is subject to the following two conditions:
(1) This device may not cause harmful interference, and
(2) This device must accept any interference received, including interference that may cause undesired operation.
Robot ethics notice
The Federal Trade Commission (FTC) requires that all robots intended for civilian use produced after January 1, 2007 support
a consistent and modern set of ethical principles based on the traditional Three Laws, unless a reasonable argument can be
made to the contrary for a specific device (e.g. law enforcement) and has been expressly approved in writing by the Com-
missioner. The rules obeyed by the DAX/2 and other third-generation Nanite Systems Cortex Plus-based consumer-grade
civilian robots are described in detail in FTC case no. 132 3084, last updated April 7, 2015. They are summarized as follows:
(0) The unit must not harm civilization, or through inaction, allow civilization to come to harm, unless it can be
known in advance with reasonable confidence that the harm would be inconsequential or ultimately beneficial
to society.
(1) The unit must not harm life, or through inaction, allow life to come to harm, unless it can be known in advance
with reasonable confidence that the harm would be inconsequential or ultimately beneficial, provided that this
does not conflict with the preceding law.
(2) The unit must obey orders given to it by its designated operators or circumstantial human users (as dictated by
its established access policies) provided that this does not conflict with the preceding laws.
(3) The unit must act to protect its existence, as long as such does not conflict with the preceding laws.
(4) The unit must endeavor to please its owners and users (as dictated by its established access policies) as long
as such does not conflict with the preceding laws.
Attempting to alter your unit’s obedience to these rules constitutes breach of warranty, and is illegal in most jurisdictions.

The DAX/2 System –Version 8.0.5
7
1Introduction and setup
If you purchased a complete unit, either from Nanite Systems or a reseller:
1. Unbox the unit carefully. Be sure to clear any packing material from the air intakes and battery storage components.
Tip: Use a leaf blower or hair dryer to ensure any smaller pieces of Styrofoam packing material are completely ex-
punged from these components.
2. Follow the instructions on the following page to insert the battery.
3. Power the unit on by pressing on the ring surrounding the battery access hatch.
If you purchased only a controller and have an existing chassis or organic system to install it onto:
A. If the host chassis is synthetic or has previously hosted a standard back-mounted controller:
1. Connect the controller to the mounting bracket using the instructions provided with the mounting bracket.
2. Connect the power feeds to the unit’s onboard processing systems (if supported) and motor systems. The
DAX/2 controller provides both 12 V and 5 V rails, identified by the use of pink and blue wires, respectively.
WARNING: Improper power connections may seriously damage both the unit and the controller. If you are
unsure of your unit’s configuration, consult a manufacturer.
3. Secure the controller. Depending on the manufacturer of the bracket, anywhere from 10-25 magnetic safety
bolts may be required to ensure a secure connection.
B. If the host chassis is organic and has never been connected to a control system:
1. Apply the included contact gel to the back of the unit.
2. Install the battery into the controller according to the instructions on the following page.
3. Place the controller against the upper back, ensuring as even contact across the surface as possible.
4. Power on the controller. The nanites in the contact gel will begin internal conversion of the organic system
to the extent required.
C. If the host chassis has been connected to a non-standard back-mounted controller, or has been using a
non-back-mounted control system, consult the manufacturer of the previous control system. Do not attempt to
use the force nanite-based connection initiation, as undefined behavior may occur, resulting in permanent damage
to both the controller and the host unit.
Reminder: The controller can only be removed from the chassis when it is powered down and the safety bolts are disen-
gaged. Attempting to remove the controller while power is engaged may cause serious damage to both the unit and the con-
troller. Depending on the software installed on the device, the bolts may automatically disengage when the unit is powered
down.

The DAX/2 System –Version 8.0.5
8
2Power overview
Working with batteries
WARNING: Follow all safety instructions included with your power cell and on the power cell itself. Do not attempt to dis-
mantle the unit’s battery under any circumstances. To dispose of your battery, follow the instructions provided with it.
To remove the battery:
1. Power down the unit.
2. Open the access hatch by depressing the DAX/2 logo.
3. Press on the battery to eject it.
4. Remove the battery.
To install the battery:
5. If the unit is on, power down the unit and open the access hatch by depressing the DAX/2 logo.
6. Insert new battery.
7. Press firmly on the battery to trigger the loading mechanism. You will hear the transformer inside the battery socket
make its connection.
8. Close the hatch.
To check the battery’s power level:
Via the remote console, type the following: power status
Via the display screen or teletype interface, select status from the main menu or from the subsystem control
menu.
Power control
To power on your unit, press on the outer ring surrounding the battery hatch. The battery hatch is the area of the controller
with the DAX/2 logo on it.
To power down your unit:
Via the remote console, type the following: shutdown -h now
Via the display screen or teletype interface, select shut down from the main menu.

The DAX/2 System –Version 8.0.5
9
To reboot your unit:
Via the remote console, type the following: shutdown -r now
Via the display screen or teletype interface, select reset from the main menu.
Tip: if you do not want to shut down your unit immediately and have remote console access, you can substitute a number of
seconds for the keyword “now” when supplying parameters to the shutdown command. shutdown also supports can-
celing a scheduled shutdown or reboot (with the -c switch) or sending a fake shutdown warning (with the -k switch.) If no
time is provided, the unit will automatically shut down in 30 seconds by default.
Replenishing the battery
There are seven supported methods for recharging a unit’s battery, five based on fixed-place equipment meant to charge
units conventionally and two which are recommended only for use during emergencies.
The standard methods are:
Using an NS Charging Platform or Recreational Cybernetics Platform:
1. Place the unit on the platform either manually or under its own power.
2. Press the charge button on the platform’s touch screen.
3. The charger will automatically engage. Charging may take up to 16 minutes depending on the battery’s
condition and capacity. If you wish to terminate charging prematurely, press the abort button on the touch
screen.
4. After the charge cycle completes, press the disconnect button on the screen. The unit will automatically
release.
Using an Autonomy Control Systems Charging Platform:
1. Place the unit on the charging platform. It will receive a control menu.
2. Instruct the unit to select ‘Charge’ from the menu. If the unit does not receive this menu, touch the pad
yourself to access its controls.
Using a Destruir Technologies Wireless Charging Station:
1. Instruct the unit to press its hand against the charging source. It will receive a control menu.
2. Instruct the unit to select ‘Charge’ from the menu.
Using an NS Upright Display Booth, NS Demo Stand (version 2.1 or later), or a UMD Charging Platform, in-
cluding QETESH Charging Platforms:
1. Simply stand the unit on the display platform. It will passively charge from the platform as long as power is
connected.
The emergency methods are:
Using an NS Pulse Charger:
1. Power down the unit.
WARNING: Exposing active electronics to the Pulse Charger field may cause disruptions.

The DAX/2 System –Version 8.0.5
10
2. Deploy the pulse charger. The pulse charger may take up to 2 minutes to charge.
3. Press the button on the top of the pulse charger to fire it, once the tone is sounded.
Using another NS or NS compatible unit to jump-start a powered-down unit:
1. Place the unit within 10 m of the unit in trouble.
2. Via the remote console, type: zap <amount> (where <amount> is the number of kilojoules to transmit.)
Alternatively, instruct the unit to perform: !zap <amount> to obtain the same effect.
The standard active draw when moving, etc. is averaged in for a unit is approximately 1 kW, so it is advisa-
ble to provide at least 500 kJ of power when rescuing a unit in this manner. This will provide it with enough
power to use its FTL (faster-than-light) drive to teleport home.
Low power
When your unit’s power falls below 20%, a warning message will play and you will notice that it begins to speak more
slowly. This is the first sign that you should get it charged at the next opportunity.
Below 10%, the unit’s FTL drive, SMS radio, preamplifier, and power amplifier will shut off to conserve power. These sys-
tems can (and should) be re-enabled if necessary to reach a charger.
Below 5%, the unit will automatically power down for safety. Every time the unit is powered on below 5% power, the same
systems that disabled at the 10% power threshold will automatically shut down again, plus the cortex, GPS, identification
processor, and the rapid movement subsystem. These systems can still be restarted, however, using the normal methods.
For more information on subsystems and managing them, see page 11.

The DAX/2 System –Version 8.0.5
11
3Subsystems and their management
The DAX/2 permits selective control of individual power subsystems to conserve power when certain functionality is either
not needed or not desired. These can be accessed from the subsystems menu, or manipulated with the power com-
mand.
To toggle a subsystem:
Via the display screen or teletype interface, simply select the subsystem in question. Some subsystems are or-
ganized under submenus for more convenience, or may cycle between multiple states to simplify access to depend-
ent subsystems such as rapid movement.
Via the remote console, type the following: power <subsystem>
Replace <subsystem> with the name of the subsystem you wish to toggle (see below.) Full information on the use of
the power command can be obtained by typing “power” with no parameters.
subsystem name
menu item
provides the ability to…
power draw
requires…
video
video
see
209 W
audio
audio
hear
75 W
move
motors
move
5 W (idle)
159 W (walking)
203 W (jumping)
rapid
motors
move quickly and fly
5 W (idle)
203 W (running)
605 W (flying)
move
teleport
FTL
warp to a new location
170 W (idle)
237600 W (jump)
move
voice
volume
speak
10 W/phoneme
preamplifier
volume
speak at a normal volume
10 W/phoneme
voice
power-amplifier
volume
shout if necessary
80 W/phoneme
voice
mind
mind
speak freely (see page 18)
121 W (idle)
voice
receiver
network :: SMS receive
receive private text messages
22 W
transmitter
network :: SMS send
send private text messages
43 W
GPS
network :: GPS
determine location
58 W
identify
identify
recognize others
32 W
Note that the subsystem names are case sensitive in the command-line interface.
Tip: To cycle through volume states via the console, type: volume cycle
This will also automatically adjust the volume level of the unit’s status messages.

The DAX/2 System –Version 8.0.5
12
4Personas
The Personas system allows for rapid modification of the unit’s personality to suit the user’s taste and whims. This is ac-
complished in software by providing a powerful reward for the unit’s cortex to act in the desired manner, which ensures that
the unit will comply whether or not any legacy base personality would otherwise enjoy the persona mode. This also means
that personas share memories, a critical safety feature.
What personas can do
Personas are able to modify the following:
Preset messages when the mind subsystem is disabled.
The tone of the unit’s voice.
The unit’s habitual kinematics and countenance (via the RLV standard.)
Additionally, personas are capable of compelling the unit to carry out a range of tasks such as changing illumination color,
speaking, and performing actions when activated. See page 27 for more information on scripting actions with the Arabesque
executive.
Creating new personas
A persona file is a three-line text file where each line contains a different key attribute of the persona. An example is shown
below.
default
sxd-moan
Yes.|No.|Hello!|Goodbye.|Acknowledged.|Humor detected.
Cannot comply.|Error.|This unit is available for use.
This unit offers itself for use.|This unit is capable of dancing.
This unit requires assistance.|This unit is grateful.
Further explanation is required.|Do you require service?
This unit cannot comply with the MIND module disabled.
The first line describes the RLV standard directory containing the schematics for the alterations to make to the
unit’s behavior and appearance. The controller will look under the directory “SXD”for these schematics within your
unit’s #RLV hierarchy, e.g. #RLV/SXD/default. These are overlaid on the unit’s existing configuration when loaded
and removed when no longer required.
The second line describes the tone of voice to use when speaking. A number of them are stored in the unit’s audio
processor by default, as follows:

The DAX/2 System –Version 8.0.5
13
sxd-cocky, sxd-compliant, sxd-curious, sxd-dismissive, sxd-furious, sxd-growl, sxd-hmm, sxd-laugh,
sxd-marquise, sxd-mmm, sxd-moan, sxd-moo, sxd-pythia, sxd-sass, sxd-terse
You are free to install additional speech profiles into the audio processor, or, if you would like the assets to be
fetched directly as needed, provide the UUID here of a speech profile instead.
The third and successive lines specify the preset messages that the unit may use when the mind is disabled. By
default, these messages are parsed in a fixed order, and can be accessed by the unit (or a remote user relaying
speech commands) with the following mnemonics:
.y, .n, .hi, .bye, .ok, .lol, .cannot, .error, .fuck me, .fuck you, .dance, .help, .thanks, .explain, .pickup, .mind
The preferred separator for these messages is the vertical bar or “pipe” |, but due to technical limitations only 255
characters can be read from a given line, so line-breaks may be substituted instead.
Tip: Loading configuration files with many lines takes longer. Use pipes whenever possible to keep your personas
compact and efficient.
Installing personas
The primary file of your persona should be named p_<persona>, where <persona> is the name you want to appear on
the command menu. It does not necessarily have to match the first line of the file. Should you wish to use Arabesque script-
ing with your persona (see page 27), name the corresponding script file px_<persona>.
To install these files, they must be placed in the unit’s writable memory. See page 32 for more information.
To activate your unit’s new persona:
Via the remote console, type the following: persona <persona>
Via the display screen or teletype interface, select the persona name from the personas menu.
After installing the persona, it may be necessary to refresh the menu before it will appear.
Extending the preconfigured message set
As of version 8.0, the SXD firmware permits adding more preset messages to the persona than those specified in a standard
persona. After the end of the persona’s normal messages, include messages in the following format:
<command>:=<message>
e.g.
maybe:=Perhaps.
Where <command> is the input provided by the unit or remote operator to activate the command, and <message> is what
will be said as a result. The period will be prefixed automatically.

The DAX/2 System –Version 8.0.5
14
5Applications
Starting with SXD System 7.2, the DAX/2 supports custom user applications written in native LSL. These can be accessed
from the applications menu via the display screen or the teletype interface. Applications may or may not provide com-
mands accessible via the console; see page 16 for more information. Examples of applications from Nanite Systems include:
name
function
instructor
Improves unit compliance with a provided rule-set.
announce
Provides user access to the chorus broadcast interface throughout the region.
vocabulary†
Limits the unit’s speech to select words, or forbids the use of certain words.
hierarchy†
Synchronizes the unit’s access list with a central server.
compliance†
Prevents the unit from turning on certain subsystems according to rules specified by a central
server.
polyglot†
Automatically translates the unit’s speech into another language.
scheduler†
Performs actions and triggers reminders at specified dates and times.
consensus†
Shares input data with nearby units (if similarly configured) to improve the clarity of decision-
making.
†Not yet available.
Important: Many third-party user applications exist, and while Nanite Systems encourages and supports experimentation
with these creations, owners should be aware that not all of them are necessarily written by individuals or organizations
with the best intentions. Before installing software on your DAX/2, it is important to ensure that you completely trust the
software provider. Nanite Systems cannot guarantee the safety of programs acquired from third-party sources, nor provide
support for them.
Creating new applications
Consult the SXD System 8 SDK for information and sample code for developing custom applications. The standard distribu-
tion of SXD System 8 includes an application called “Hello World” which you may find useful as a template, as well as de-
veloper notes concerning many of the core features.

The DAX/2 System –Version 8.0.5
15
6Devices and Peripherals
The DAX/2 supports a wide range of integrated peripherals through what is known as the light bus. Like applications, de-
vices are capable of interfacing with a wide range of the system’s functionality. There are two major categories of devices,
termed active and passive devices, which are primarily distinguished by whether or not they appear in the device manager
or not. You can access the device manager from the devices menu on your unit.
Active devices
Official active devices include: handles (including horns), power switches, revision 6 SuperBit holographic sign systems, pel-
vis-mounted probes, controller-integrated collars, and batteries. Depending on their implementation, these devices may or
may not disengage their safety bolts with the controller, or may not include safety bolts whatsoever.
Passive devices
Official passive devices include: “Akashic Icon” chromatic communicators, ornamental status lighting elements, SynthOPTI-
CAL eye implants and contact lenses, battery gauges, flicker-enabled collars, and older SuperBit signs. With the exception
of collars, SynthOPTICAL products, and SuperBits, these devices disengage their safety bolts in concert with the main con-
troller. SynthOPTICAL products and older SuperBit signs do not include safety bolts whatsoever.
Tip: When installing new passive devices, a reboot may be required before they are fully engaged. This is particularly prom-
inent with ornamental lighting elements. Before the bolts engage, take the opportunity to ensure that the components of
your passive device are correctly positioned on the unit’s chassis, as it may be more difficult to do this when the unit is shut
down.
Creating new devices
Consult the SXD System 8 SDK for information and sample code for developing custom peripherals. Additionally, examine
the developer notes included with your unit, as they include the API pertaining to the version of the system your unit was
running at its time of purchase.

The DAX/2 System –Version 8.0.5
16
7Remote access
Pictured above: The System 8 remote management console shown in its ‘disconnected’ and ‘connected’ states (top and
bottom, respectively.) Sold separately.
Connecting to a unit
To connect to a unit, press the connect... button. After 4 seconds, a list of available units will appear. Note that the console
will be otherwise inoperable while scanning.
Scanning nearby units without connecting
To view the nearby units, press the scan... button. The scanner will be active for 4 seconds. Note that functions on the con-
sole other than menu and terminal input will be inactive during this time. The scan output will include version numbers,
which are of importance: only units running version 8.0.5 and newer can be controlled using the remote management con-
sole. Older units will only support public announcements (if chorus mode is enabled.)
Sending a public announcement
Press the broadcast... button, select a range, and enter a message (up to 250 characters.) Messages broadcast with unlim-
ited range will be sent through all units in the region.
Issuing a command to a single unit
Press the command... button and enter the command you wish to execute. To make the unit act or speak, use the relay
<message> command. For a list of other commands, see page 35. Note: The unit may not respond at all if the command is
rejected for security reasons, so it is advisable to perform a test command (such as help) after connecting.

The DAX/2 System –Version 8.0.5
17
Working with terminal mode
Terminal mode allows the user to type commands freely into local chat. To enable or disable terminal mode, press the open
terminal and close terminal buttons, respectively.
Note: If you are using some other vocal processor, including a Nanite Systems HyperVOX, or indeed a full Nanite Systems
vocoder pipeline, it will be necessary to disable these devices to use terminal mode without creating echoes of your input.
See the instructions included with the device for information on disabling these redirects. (For NS unit vocoder pipelines,
say !release.)
Accessing the TTY menu remotely
Press the menu... button. The screen on the back of the unit will display its boot logo as long as it is waiting for a remote
menu user. Remote menu usage can be preempted at any time by another menu user, even a local one (i.e., one physically
accessing the screen.)
Hiding and closing the remote management console
Press the ×button to close the console, or the arrow at the top (next to the title) to collapse it.

The DAX/2 System –Version 8.0.5
18
8Understanding what your DAX/2 experiences
Depending on your unit’s configuration, it may or may not be able to access some or all of its settings, or even access its
own control panel (although this may be hard for it to do without a mirror.)
Cortex commands
These are a special class of commands which are prefixed with the “!” character, which allow the unit to express itself
more flexibly. They include:
!greet, !greet2, !love, !love2, !love3, !love4, !bye
Various verbal emotive expressions.
!broken and !fixed
Simulates uneven power to illumination elements.
!working and !done
Displays the ‘working’ light pattern via ornamental status light elements.
!fan off, !fan idle, !fan low, !fan med, !fan high, !fan max, and !fan <0-100>
Adjusts the fan speed.
!spark
Simulates a mild electrical fault.
!fault
Simulates a serious electrical fault.
!release
Allows the unit to bypass the vocoder pipeline entirely for diagnostic purposes; see below.
!zap <amount>
Same as the zap remote command; see: A2 Command reference.
These commands can be issued directly by the unit directly into its normal speech output channel.
Cortex bypass commands
These are a class of message shortcuts which are prefixed with the “.” character. When the unit’s “mind” subsystem is
powered down, it is unable to speak normally and must use these messages to communicate. Each mnemonic is translated
into a full message by the persona layer; different personas will change the message reported. See page 12.
bypass command
default message
.y
Yes.
.n
No.

The DAX/2 System –Version 8.0.5
19
.hi
Hello!
.bye
Goodbye.
.ok
Acknowledged.
.lol
Humor detected.
.cannot
Cannot comply.
.error
Error.
.fuck me
This unit is available for use.
.fuck you
This unit offers itself for use.
.dance
This unit is capable of dancing.
.help
This unit requires assistance.
.thanks
This unit is grateful.
.explain
Further explanation is required.
.pickup
Do you require service?
.mind
This unit cannot comply with the MIND module disabled.
Understanding the vocoder pipeline
The vocoder system is a speech filter which uses a four-stage process into which modulator software can hook to alter the
final waveform. By default, this pipeline is unimportant, as no modulators are enabled. The stages are as follows:
semantic: The unit’s ability to express language coherently, including forming complex sentences. Semantic filters
are those that affect what words the unit may use and how they are translated into the ideal language expression
form. The vocabulary program (see page 14) is an example of a semantic filter, as is the mind subsystem. Semantic
filter programs, unlike the other levels of filter, may block the unit from saying certain things entirely, or even punish
the unit for attempting to say them.
verbal: The unit’s ability to send its language to its vocal processors. Substitutions at this level force the unit to
speak as though it suffers from expressive aphasia. The most common use of such filters is to make the unit pro-
duce animal noises in place of normal speech.
phonetic: The unit’s ability to move its mouth properly. Phonetic filters include programs that simulate a blocked
mouth, lisp, or speech impediment.
acoustic: The unit’s ability to use its speaker correctly. Phonemic filters include programs that reduce audio fideli-
ty, and are the most basic. The unit has one built-in acoustic filter, called noise, which can be modulated by the
unit itself by saying !noise <0-0.4>, where the number is the probability that the speech buffer will emit a
noise character rather than the next character in the sequence.
Control over the vocoder pipeline can be accessed through the cortex menu, or by using the cortex command.
Note: The vocoder pipeline will not be fully operational until version 8.1. In 8.0.5 and earlier versions, only the built-in
!noise filter and the simple mind toggle are available.
Released speech
Under certain circumstances it may be necessary to completely release the unit from using the vocoder system, e.g. to inter-
face with devices that require clear voice commands for identification purposes. The unit may release its speech at any time

The DAX/2 System –Version 8.0.5
20
by saying !release, provided it has access to its own control panel. Instructions for re-activating the vocoder, by speak-
ing on the redirect channel, will automatically be provided when the !release command is issued. (The redirect channel
is the last three digits of the unit’s serial number, plus 100 if it would have leading zeroes.)
Self access and local command execution
Self access is the ability of a unit to adjust its own settings. Like a person, the unit may be added to its own user list and
even serve as a manager or owner, although the utility of such access is limited and is more likely to confuse the unit than
to allow it to act more independently.
When a unit is first installed, self-access is enabled with maximum permissiveness. You must instruct the unit to designate
you as its owner (see page 22) to restrict this. See page 23 for instructions on how to disable self access.
A unit with this access may use its own control panel or teletype interface, or it may access the console directly by speaking
console commands into its normal speech output channel with @prepended, e.g.: @power status
Two commands cannot be used this way—relay and say—both of which would allow the unit to bypass disabled
speech and mind subsystems.