AFAQY Knowledge Base
    Protocols
    Protocols

    Protocols

    📖 Afaqy Knowledge Base / AVL / Settings / Protocols

    CONTENTS
    ‣
    Introduction
    • About Afaqy
    • AVL Pro
    ‣
    Technical Requirements
    • Recommended Web Browsers
    • Hardware Specifications
    • Internet Connection
    ‣
    Quick Start
    • Account Setup
    • Logging In
    • Resetting Password
    • Glossary
    ‣
    Map
    • Map Navigation
    • Map Tools
    ‣
    Monitoring
    • Monitoring List
    • Monitoring Tools
    • Monitoring Fields
    ‣
    Dashboard
    ‣
    Statistics
    • Overview
    • Accessing Statistics
    • Filters & Controls
    • Units
    • Status
    • Others
    • Activity & Reporting
    • Exporting Data
    • Related Pages
    ‣
    Charts
    • Chart Types
    • Creating a chart
    • Chart Tools
    ‣
    Geofences
    • Overview
    • Purpose
    • Page Components
    • Display Modes
    • Unit Count Indicator
    • Actions
    • Best Practices
    ‣
    Reports
    • Reports Tab
    • Templates Tab
    • Schedules Tab
    ‣
    Report Categories Breakdown
    • Summary Reports
    • Vehicle Activity Reports
    • Driving Quality Reports
    • Zones Activity Reports
    • Sensors Activity Reports
    • Other Reports
    ‣
    Units
    • Selecting Columns
    • Creating a Unit
    • Creating a Sensor
    • Creating a Command
    • FAQs
    ‣
    Units Management
    • Importing Units
    • Accessing Units
    • Unit Groups
    • Unit Shared Groups
    • Exporting Units
    • Deleting Units
    • FAQ
    ‣
    Messages
    • Permissions
    • Tracing Messages
    • Table View
    • Graph View
    • Common Tools
    • Troubleshooting
    ‣
    Second By Second
    • Permissions
    • Scope & Limits
    • Tracing Second by Second
    • Table View
    • Graph View
    • When to use
    • Troubleshooting
    ‣
    Tracking
    • Tracking Fields
    • Generating a track
    • Tracking Tools
    ‣
    Multi-Unit Follow
    • Screen List
    • Maps
    ‣
    Users
    • Selecting Columns
    • Adding a user
    • Users Management
    • Roles & Permissions
    • User Activity & Auditing
    • Best Practices
    • Permissions & Visibility
    ‣
    Geofences
    • Geofences List
    • Markers List
    ‣
    Geofences Management
    • Importing Geofences
    • Accessing Geofences
    • Geofences Groups
    • Exporting Geofences
    ‣
    Customers
    • Selecting Columns
    • Adding a customer
    • Customers Management
    ‣
    Resources
    • Trailers
    • Drivers
    • Events
    • Status
    • Custom Fields
    ‣
    Settings
    • Protocols
    • Packages
    • Roles & Permissions
    ‣
    Audit Log
    • Overview
    • Purpose
    • Scope of Logged Activities
    • Page Components
    • Event Details
    • Export & Retention
    • Access Control
    • Best Practices

    Overview

    The Protocols page allows administrators to manage and configure communication protocols used by tracking devices to interact with the platform. Protocols define how data is received, interpreted, and processed from different device types.

    This page is foundational for device compatibility, data accuracy, and system stability.

    Purpose

    The Protocols page enables users to:

    • View supported device communication protocols
    • Configure protocol-level parameters for the default three sensors only (ACC, Vehicle Battery, Device Battery).
    • Ensure correct decoding and processing of incoming data
    • Support onboarding of different device manufacturers and models

    Protocols List

    Displays all available protocols configured in the system.

    Typical information includes:

    • Protocol name
    • Protocol code
    • Protocol decoding port
    • Status (enabled / disabled)
    • Actions: Edit only — used to configure parameters for the default three sensors (ACC, Vehicle Battery, Device Battery).
    • Vendor / device family
    • Description or notes

    Access Control

    • Protocol configuration is typically restricted to system administrators
    • Changes may impact live device data and should be performed carefully

    Best Practices

    • Activate only required protocols to reduce system complexity
    • Validate protocol settings before onboarding devices
    • Avoid modifying protocol parameters during peak operational hours
    icon
    Custom Fields
    icon
    Packages