dsigns — BrightSign SD pilot 0.1.0-pilot.1

Connect a spare player

1. Keep the player's original SD card. Use a separate, writable SD/microSD
   card formatted as FAT32, with enough space for two copies of your media.
2. Extract this ZIP. Copy its CONTENTS to the top level of the new card.
   autorun.brs and index.html must be at the top level, not inside a folder.
3. Turn the player off. Insert the new card. Connect HDMI and Ethernet
   to a network with internet access, then turn the player on.
4. When five letters appear, open https://dsigns.bitprecision.com on your
   phone or computer. Sign in and choose Players > Add player. Enter the
   letters, name the player and select its customer and group.
5. A group with a ready playlist is published during connection. If no
   content appears, assign the BrightSign HDMI screen to a group with a
   playlist and publish from Players. Start with a JPEG or PNG and a short
   1080p H.264/AAC MP4. The default group volume may be muted.

Once all media has downloaded and passed its checks, playback uses the SD
card. A complete saved playlist can run after an internet outage or reboot.
Unfinished downloads keep the last complete playlist. Leave the card in the
player while it runs. Power off before inserting or removing it.

Compatibility and limits

This is a hardware-test pilot, not a verified universal BrightSign image.
It runs our app on the player's existing BrightSignOS; it does not flash
firmware or factory-reset the player. Start with an HTML-capable Series 3
or newer video player with Node.js 14 or newer (8.5.31+ on the 8.5 branch).
Use a current vendor-supported OS for the exact model where possible.
Other OS branches must provide an equivalent HTML/Node environment.
Audio-only players, old non-HTML models and players that cannot boot the
external card are outside this pilot. No model has passed our hardware
tests yet. A newer model number alone does not guarantee compatibility.

The pilot supports one landscape HDMI output, JPEG/PNG, compatible MP4,
fit/fill, volume, default playlists, timezone/date schedules and a standby
image. MP4 is a container: codec, resolution and hardware decoder support
depend on the model. Individual files are limited to 2 GiB. Start at 1080p.
Rotation, video walls, screenshots, remote reboot/app updates and the
desktop recovery controls are not implemented. Unsupported remote commands
are reported as failed. The dashboard decoder status stays "unknown".

If the pairing screen does not appear

- Still seeing another provider: the old app may be on internal storage,
  external boot may be disabled, or cloud provisioning may restore its
  setup. Ask the existing administrator to release/configure the player.
  Replacing the SD card does not remove those settings or credentials.
- Starting message stays: check the top-level files, model and OS version.
  An unsupported browser or Node runtime cannot launch the app.
- Network message: check Ethernet, IP/DNS settings, internet access and the
  player clock. Incorrect time can prevent secure HTTPS connections.
  Existing static IP and Wi-Fi settings remain. This pilot has no Wi-Fi
  setup screen; configure the player's network separately if required.
- Connected but no playlist: check the assigned group, published content
  and Players status. Use independent mode, one BrightSign HDMI screen and
  zero rotation. Content outside the pilot's formats will be rejected.
- Video fails: try a short standard H.264/AAC MP4. Test PNG/JPEG separately.
  Failed or stalled media is retried with a delay and reported for attention.
- Storage message: use a healthy writable card with room for the old and
  new playlists. A full or damaged card can prevent pairing and downloads.

Backup: manual setup code

If needed, create a manual setup code in the dashboard for the customer and
group. Save ONLY that complete dsigns1. code as setup-code.txt at the card's
top level before pairing. The app consumes and deletes it after successful
enrolment. Use one fresh code per player. An expired or invalid file must
be replaced or removed before screen pairing can continue.

Start again or restore the original player

The app saves its connection and downloaded content in dsigns-data on the
card. Keep this folder private: it contains the player access token.
Do not clone a used card for multiple players. Distribute the fresh ZIP.
For a new pairing, power off, remove dsigns-data and any setup-code.txt on
your computer, then boot again. Remove the old player from the dashboard
if you are replacing it, so its old credentials no longer work.

To return to the old app, power off and reinsert the untouched original
card. The pilot does not change firmware, network settings or provisioning.
Existing vendor provisioning may still affect what boots.

First test: pair, play an image and video, unplug Ethernet, power-cycle
with Ethernet still unplugged, then reconnect and publish a changed
playlist. Record the model, OS version and results. Keep the player on
test before using it for an unattended customer screen.

Validation: automated local and live cloud protocol/cache checks passed.
BrightScript execution, HDMI rendering, video/audio, card power-loss
durability and physical offline reboot are NOT YET TESTED on hardware.