SXDjr el0ra manual

Introduction

El0ra is a Nanite Systems SXDjr pleasure robot. It was built in February 2018, and purchased by an unknown owner. That owner programmed it with nostalgic sounds and responses from the Windows 98 era, much of that programming still remains to this day.

Maintenance

The unit is mostly self sustaining, its wireless charging capability has long since failed, but it is still capable of charging via most charging pads and wall outlets. Care should be taken to ensure it can reach a charging device when needed.

Hardware

  • The unit includes a lithium-ion battery that lasts about 4 hours under mostly idle operation.
  • This can be extended to almost 5 hours by turning off unneeded subsystems and limiting movement.

  • Alternative batteries may also be obtained in capacities of 2, 8, 24, or 48 hours.

  • In case of low power, the unit will automatically power down at 5% battery. At this point the unit has enough energy to teleport at least once to reach a charger once powered back on.

  • The side of the controller has a switch enabling power control of the unit.

  • Anyone can turn the unit off, however, only someone with appropriate permissions can turn it back on.

  • On the hips of the unit are handles that allow for carrying, placing, and posing the unit.

  • Access to this is covered by security rules, which are covered in the security section below.

Security

You may consult the manual, or ask the unit for help with configuration, it is capable of setting all settings as desired as long as it has sufficient permissions to do so. Those permissions can be later revoked once configuration is ready.

Rules

  • A quick reference on security rules is available in the ARES Manual
  • A detailed document on security rules is also available in the ARES Manual

Policies:

Policies are set with the policy command: /1el policy <name> on|off

  • bolts: lock bolts preventing the removal of the units hardware
  • apparel: prevents clothing changes by the unit.

Power Subsystems

Power subsystems are managed with the power command, more info can be found in the ARES Manual

Profiles can be saved of the current power state and restored.

The subsystems are:

  • base (30 W): no intrinsic functions; required for all other subsystems
  • video (20 W): ability to parse video signals
    • hud (5 W): ability to see the ARES HUD
    • optics (50 W): ability to see visible light
    • identify (20 W): ability to see names and hovertext
  • lidar (10 W): ability to judge distances; required for FTL (teleport)
  • hearing (10 W): ability to receive incoming chat messages
  • radio (30 W): no intrinsic functions
    • GPS (location) (5 W): ability to see map location; required for FTL(teleport)
    • receive (10 W): ability to receive IMs
    • transmit (10 W): ability to send IMs
    • wifi (10 W): ability to connect to remote devices
  • FTL (teleport) (120 W): ability to teleport or be teleported; requires lidar, radio, and GPS (location)
  • motors (60 W): ability to touch nearby objects; required for all movement
    • locomotion (40 W): ability to walk and sit
    • athletics (40 W): ability to run and jump
    • flight (50 W): ability to fly
    • reach (20 W): ability to touch objects more than 2.5 m away
  • voice (20 W): ability to talk (at a whisper only)
    • speech (20 W): ability to talk (at normal volume); requires motors subsystem
    • amplifier (30 W): ability to shout; requires motors subsystem
    • mind (70 W): ability to speak messages other than those defined by persona