Skip to main content

Navis - CH -5703 Configuration

This page covers the public configuration context for using the Navis CH -5703 with Plaspy. It summarizes the practical server settings and the typical steps required to point a CH -5703 device at the Plaspy platform so the unit can report position and messaging data to the monitoring system. The information here focuses on publicly available setup patterns rather than proprietary manufacturer procedures.

Plaspy uses a shared server endpoint and port across supported trackers and it detects the tracker protocol automatically when the device connects. Exact manufacturer side configuration steps for the CH -5703 can vary with firmware version, hardware revision, installation type, and vendor tools, so use the guidance here together with the official Navis documentation and any device specific configuration tools supplied with the unit.

Configuration Overview​

The goal of configuring a Navis CH -5703 for Plaspy is to ensure the unit reliably communicates navigation and status data to the Plaspy endpoint so the device appears and reports correctly inside the Plaspy platform. Configuration typically sets the server endpoint, transport, and any device-side messaging options so the CH -5703 sends its navigational output and status updates to Plaspy.

  • Set the device to report to the Plaspy server endpoint so location and messages route to the platform.
  • Select the appropriate transport mode on the device if the firmware requires a TCP or UDP choice.
  • Configure and save server and port information in the manufacturer configuration utility or device interface.
  • Verify the tracker powers up correctly and has the required connectivity to reach d.plaspy.com.
  • Confirm the device appears in Plaspy and is sending expected position and message updates.

Plaspy Server Settings​

Use the following public Plaspy server settings when configuring the Navis CH -5703:

  • Server domain d.plaspy.com
  • Server IP 54.85.159.138
  • Port 8888
  • Transport support for UDP or TCP depending on device requirements
  • Plaspy automatically detects the tracker protocol when the device connects

Note that Plaspy uses the same port for all supported devices, so port 8888 is the universal value to configure on the tracker.

Typical Requirements Before Setup​

  • Ensure the CH -5703 has stable power and is installed per Navis instructions.
  • Have access to the official Navis configuration method or software for the CH -5703.
  • Confirm network connectivity from the vessel so the device can reach d.plaspy.com.
  • Prepare any device identifiers or credentials required by Navis tools to edit network settings.
  • Verify you have a Plaspy platform account or access where device visibility and reporting can be validated.
  • Record the device serial or unique ID so you can identify it in Plaspy after setup.

How This Tracker Connects to Plaspy​

When configured for Plaspy, the CH -5703 sends its navigational output, event messages, and monitoring data to the shared Plaspy endpoint and port. The platform receives the inbound connections and automatically interprets the tracker protocol so reported data becomes visible to operators and monitoring systems.

  • The unit reports position and timing information to the Plaspy server endpoint at d.plaspy.com using port 8888.
  • Transport selection on the device (UDP or TCP) is used as required by the firmware; Plaspy accepts both.
  • Short text or coded messages generated by the CH -5703 are sent to the control center endpoint and shown in Plaspy where supported.
  • Device status updates and alarms are forwarded to Plaspy for operational monitoring and logging.
  • Plaspy matches incoming reports to the correct device record and makes telemetry available in the platform.

Common Configuration Workflow​

  1. Access the official Navis configuration method or software that is appropriate for the CH -5703.
  2. Locate the network or server settings section in the device interface.
  3. Enter the Plaspy server domain d.plaspy.com or the server IP 54.85.159.138 into the device server field.
  4. Set port 8888 as the destination port used by Plaspy.
  5. Choose UDP or TCP transport if the device requires a selection for connection type.
  6. Apply or save the configuration changes in the Navis tool or device menu.
  7. Restart the device if required by the manufacturer to activate the new network settings.
  8. Validate that the device reports successfully to Plaspy and that position and messages appear in the platform.

Example Configuration Commands​

The CH -5703 manufacturer configuration method may vary by software tool, firmware, and installation. Because Navis configuration commands differ across tools and firmware releases, no universal command set is provided here. Use the official Navis configuration utility or the manufacturer supplied interface to enter d.plaspy.com or 54.85.159.138 and port 8888, and select UDP or TCP if prompted.

If you have a specific Navis command list from the device manual or configuration tool, follow those commands in the order they are listed by Navis and then verify connectivity to Plaspy.

Configuration Notes​

  • Firmware differences can change where and how server and transport settings are entered; check the device manual for your CH -5703 firmware revision.
  • Choosing TCP versus UDP depends on device firmware behavior and network conditions; both are accepted by Plaspy.
  • Plaspy uses the same port 8888 for all supported devices and automatically detects the tracker protocol, so port consistency simplifies multi device deployments.
  • The CH -5703 supports transmitting short text and coded messages to a control center; confirm how these message types are enabled in the Navis configuration tool.
  • Always back up existing device settings before making changes and note any vendor specific steps required to commit configuration changes.

Why Use Plaspy with This Configuration​

Pointing a Navis CH -5703 to Plaspy provides a straightforward path for vessel monitoring and operational oversight. For organizations that rely on accurate GNSS data and on board messaging, configuring the CH -5703 to report to Plaspy gives centralized visibility into position, movement, and control center messages across a fleet of marine vessels.

To learn more about Plaspy and how it supports device integration and fleet monitoring visit https://www.plaspy.com. Please verify the latest device specific configuration methods and firmware behavior with the manufacturer at http://navis.ru/ because vendor procedures and firmware features 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