How Teleport Works with PeekSmith

Understanding the PeekSmith pipeline is essential for getting the most out of your Teleport device. Many common issues stem from misunderstanding how data flows from source to display. Hereโ€™s the complete workflow:

The PeekSmith Pipeline

Source โ†’ Text Buffer โ†’ Trigger โ†’ Action โ†’ Teleport

Letโ€™s break down each component of this pipeline:

1. Source

Sources are where information originates. Teleport can receive data from multiple sources:

  • Send Text Screen: Manually type or paste text directly in the app
  • Predefined Text: Use saved phrases or predictions
  • NFC/RFID Readers: Scan physical tags to load text
  • Impression Pads: Capture handwritten input from devices like IARVEL pads
  • Inject 2/WikiTest: Receive words or phrases from these apps
  • Web Polling: Pull data from compatible web services
  • Other Apps: Any app that can send text to PeekSmith

2. Text Buffer

The text buffer is PeekSmithโ€™s temporary storage for information waiting to be sent to Teleport. Think of it as a clipboard that holds your content until youโ€™re ready to display it.

Key Points:

  • The buffer can hold one piece of text at a time
  • New text replaces whatever was previously stored
  • You can view the current buffer content in the app

3. Trigger

Triggers are events that can be assigned actions. You can assign actions to triggers, and actions can be sending text to Teleport or many other available actions.

  • Volume Buttons: Use your phoneโ€™s volume up/down buttons
  • Atom Remote/SB Mote: External Bluetooth remotes
  • Smart Watches: Compatible watches with button support
  • PeekSmith Device Buttons: Physical buttons on connected PeekSmith devices
  • Auto-Trigger: Automatically send when new text arrives (โ€On new textโ€ setting)
  • App Interface: Manual send button within the PeekSmith app

4. Action

Actions determine how the buffered text is formatted and sent to Teleport:

  • Text to Teleport: Render text using TrueWrite handwriting engine
  • Playing Card to Teleport: Convert text like โ€œAHโ€ or โ€œ10Sโ€ to card images
  • Fetch Image to Teleport: Retrieve and display custom images
  • Doodle to Teleport: Send drawing data from impression pads
  • Custom Actions: Specialized routines for specific effects

5. Teleport

Your Teleport device receives the formatted data and displays it on its e-ink screen. The entire process from trigger to display takes approximately 25-30 seconds.

Troubleshooting: โ€œIt Says Sent But Nothing Happensโ€

If Teleport isnโ€™t displaying your content, check these common issues:

Check Your Trigger Setup

  • Is your trigger device (remote, watch, etc.) properly connected?
  • Are you pressing the correct button or using the right method?
  • For auto-trigger, is the โ€œOn new textโ€ setting enabled?

Check Your Action Setup

  • Have you selected the correct action type for your content?
  • Is the action properly configured in the app?
  • Does the content in your text buffer match what the action expects?

Quick Checklist

  1. Verify Connection: Is Teleport showing as connected in the app?
  2. Check Buffer: Does the text buffer contain what you expect?
  3. Test Trigger: Try a different trigger method
  4. Confirm Action: Verify the correct action is selected
  5. Check Teleport: Is the device powered on and responsive?

Understanding this pipeline will help you diagnose most Teleport-related issues and create more reliable performances.