Skip to main content

Flextrack - Lommy Capture Configuration

This page provides public configuration context for using the Flextrack Lommy Capture tracker with Plaspy. It summarizes the shared server settings Plaspy requires, explains the practical steps technicians or integrators typically follow, and highlights the manufacturer details that matter for a successful integration. Use this guide to prepare the device and confirm connectivity before registering assets in Plaspy.

Plaspy uses shared server settings across supported devices and automatically detects the tracker protocol to simplify onboarding. Exact manufacturer-side setup steps for Lommy Capture can vary by firmware, hardware revision, installation type, and the vendor's configuration tools, so always cross-check with Flextrack documentation when you need device-specific command syntax or advanced options.

Configuration Overview​

This configuration prepares the Lommy Capture to communicate reliably with the Plaspy platform and enables live monitoring, alerts, and historical route playback. The focus is on pointing the device at Plaspy's ingestion endpoint, ensuring the device has cellular connectivity and adequate charge from its energy harvesting arrangement, and confirming reported messages arrive in Plaspy.

  • Configure the device to report to the Plaspy endpoint (domain or IP) and the required port.
  • Verify transport selection (UDP or TCP) if the device firmware requires an explicit choice.
  • Confirm cellular connectivity, SIM configuration, and any APN settings required by the installation environment.
  • Validate that the device sends position, motion, and alarm messages and that those messages appear in Plaspy.
  • Check device charge state and installation wiring so the Lommy Capture can report at the expected intervals.

Plaspy Server Settings​

Use these public Plaspy server settings when configuring Lommy Capture for cloud ingestion. These values are the common endpoint details Plaspy uses across supported devices.

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support: configure UDP or TCP on port 8888 if your Lommy Capture firmware requires a transport selection
  • Plaspy automatically detects the tracker protocol when data reaches the server and Plaspy uses the same port for all supported devices

Typical Requirements Before Setup​

  • Physical access to the Lommy Capture unit and any wiring inside the light housing to ensure correct installation and water protection.
  • A working cellular SIM with voice/SMS or data capability as required by the device role; confirm mobile network coverage at the installation site.
  • Access to the official Flextrack configuration method or software for Lommy Capture (manufacturer tool, web portal, or SMS command set).
  • Knowledge of any APN or operator settings required by the SIM; have those credentials available if the manufacturer tool does not auto-detect them.
  • A Plaspy account or project where the device will be registered so you can validate incoming messages after configuration.
  • A plan for device power state testing given Lommy Capture’s energy harvesting design so you can observe reporting behavior under normal and disconnected conditions.

How This Tracker Connects to Plaspy​

Lommy Capture transmits position, motion, and alarm messages and can be set to deliver those messages to Plaspy using the shared server endpoint and port. Plaspy ingests the device payloads and maps the events to assets for live tracking, geofence alerts, and historical analysis.

  • The device is configured to report to d.plaspy.com or directly to 54.85.159.138 on port 8888.
  • Transport may be UDP or TCP on port 8888 depending on firmware; Plaspy accepts either and will process messages.
  • Plaspy automatically detects the tracker protocol once messages reach the server, simplifying protocol configuration on the server side.
  • Motion and alarm messages generated by the onboard G-sensor are forwarded to Plaspy for real-time alerting.
  • Historical data stored in the device’s internal flash is uploaded to Plaspy when connectivity allows, enabling route playback and compliance reporting.

Common Configuration Workflow​

  1. Access the official Flextrack configuration method or software for Lommy Capture (manufacturer PC tool, web UI, or SMS command set).
  2. Enter the Plaspy server address using either the domain d.plaspy.com or the server IP 54.85.159.138 in the device server/host field.
  3. Set the server port to 8888 as the destination port for tracker messages.
  4. Choose the transport protocol UDP or TCP if the device requires an explicit transport selection; some firmware versions default to UDP.
  5. If applicable, verify or enter APN and SIM operator settings so the device can establish cellular connectivity.
  6. Apply or save the configuration and restart the device if the manufacturer instructions require a reboot to activate changes.
  7. Validate that the Lommy Capture is reporting to Plaspy by checking the device status and recent messages in your Plaspy project or dashboard.

Example Configuration Commands​

The Lommy Capture model configuration commands and exact syntax depend on the Flextrack tools or SMS command set provided by the manufacturer. Because manufacturer command formats vary by firmware and vendor tool, this page does not include device-specific command strings. Use the Flextrack configuration tool or official SMS commands provided in the Lommy Capture manual to:

  • Set the server host to d.plaspy.com or 54.85.159.138
  • Set the port to 8888
  • Select transport UDP or TCP if required
  • Configure APN placeholders or operator credentials when needed

Refer to the official Flextrack documentation for the precise command examples and placeholders required by the Lommy Capture firmware.

Configuration Notes​

  • Firmware differences: exact menu names, field labels, and command syntax can vary across Lommy Capture firmware revisions; always match the device firmware version to the correct configuration guide.
  • Transport choice: UDP is commonly used for lightweight position reporting, but TCP may be available for devices that require connection-oriented delivery; Plaspy accepts both on port 8888.
  • SMS fallback: Lommy Capture supports SMS-based reporting in addition to UDP; SMS integration paths into Plaspy depend on your gateway or ingestion setup and may require additional configuration.
  • Energy harvesting behavior: because the device relies on lighting circuits for charge, test reporting behavior both when lights are active and when the trailer is disconnected to understand fallback reporting intervals.
  • Manufacturer documentation: follow Flextrack installation wiring guidance to protect connections and avoid moisture ingress in light housings.

Why Use Plaspy with This Configuration​

Using Lommy Capture with Plaspy gives fleet managers persistent visibility into trailers and towed assets with minimal maintenance. The device’s discreet installation, motion sensing, and energy-harvesting design match well with Plaspy’s real-time position, alerting, and historical route playback capabilities, enabling efficient anti-theft workflows and operational monitoring for fleets.

To learn more about Plaspy and how it ingests telematics data, visit https://www.plaspy.com. For the latest device-specific setup details, command syntax, and installation instructions for Lommy Capture, verify current information on the manufacturer site https://flextrack.dk as firmware and setup methods can change over time.

Tracker Configuration

Need a platform for this tracker setup

Plaspy helps you connect compatible trackers, receive device data, and centralize monitoring from one GPS tracking platform.

Learn more about Plaspy