LogoLogo
Home
  • DiaLog Software
  • DiaLog Software Manual
    • Introduction
      • Overview
      • Licence Agreement
      • Limitation of Liability
      • System Requirements
      • Software Versions
    • Getting Started
      • Software Installation
      • Software Introduction
        • Database Panel
        • Navigation Bar
          • Configuration Menu
          • Advanced Configuration Menu
          • Project Menu
          • Import Menu
          • Export Menu
          • Presets Menu
          • Logger Menu
          • Analysis Menu
          • StreamLog Menu
          • Settings Menu
        • Import Tabs
        • Main Panel
        • Message Panel
      • GPRS Settings
      • Wi-Fi Settings
      • Steps to Enable FIFO
      • How to obtain the diagnostic log before contacting support
  • Quick Start Guide
    • Set the Date and Time of the Rebel Data Logger.
    • Format the SD card of the Rebel Data Logger.
    • Reflash firmware of Rebel Data Logger.
    • View Live data using DaiLog
    • Manage projects in Dialog software
      • Create a new project
      • Export a project
      • Delete a project
      • Import a project
    • Create and manage a Configuration in Dialog Software
    • Configure Rebel data logger to record raw CAN messages
      • Record Raw CAN Bus data
      • Reconfigure the Rebel data logger
      • View Raw CAN data
    • Configuring Rebel Data Logger with DBC file
      • Log CAN signals using a DBC file
      • Reconfigure the rebel data logger.
    • Log data using an A2L file
      • Log data using an A2L file
      • Reconfigure the rebel data logger
    • Configuring Rebel Data Logger to record GNSS data
      • Creating a Configuration to Record GNSS data
      • Reconfigure the rebel data logger
    • Configure Analogue and Digital Inputs using DiaLog
      • Configure Analogue and Digital inputs in Dialog software using the rebel data logger
      • Reconfigure the rebel data logger
    • Using Digital Switch to Start Logging in a Rebel Logger
    • Exporting an IVD file
      • Extract an IVD file using the DiaLog software
      • Export an IVD file
    • Interpolate or resample while exporting data
    • Import DBC signals to multiple log data using Batch Processing
    • Merge multiple log data from existing IVD files
      • Method 1
      • Method 2
      • Method 3
    • Export CAN trace, EOBD, Statistical report and DTC data using BP
    • Extracting data around specific triggers using Batch Processing
    • Various methods for exporting CAN trace
      • Export Raw CAN trace from IVD files
      • Export CAN trace log by adding DBC signals
    • Configuring Rebel Dash in Dialog Software
      • Steps to Reconfigure the Rebel data logger and Rebel Dash
    • Export data from Dialog's Configurator version
    • Configure SD card/Rebel data logger using Dialog remote
      • Formatting the Sd card and sending the configuration to it
      • Using tabs in Dialog Remote
        • Set Rebel time
        • Settings
        • Reflash Rebel
    • Log data using UDS in DiaLog Software
    • Create a shell script for converting files
    • Deactivating and Moving the License of Dialog software
      • Deactivate the DiaLog license
      • Move a DiaLog license from one PC to another
  • Appendix 1
    • Reflash
    • Edit PID Presets
    • License Manager
    • General Option of Navigation bar, Settings Menu
    • Data Option of the Navigation bar, Settings Menu
    • Protocol Priorities
  • Appendix 2
    • Glossary
    • CAN Modes
    • CAN Definitions
    • Standard OBD Periodic Identifiers
  • Appendix 3
Powered by GitBook
On this page
  1. Appendix 1

Protocol Priorities

This section details the working priorities within a Configuration Structure regarding CCP and Diagnostic protocols. If either of these protocols is present in the structure by itself, there are no priorities. However, if both protocols are present, then in a single configuration, the priority needs to be considered by users.

In both CCP and Diagnostic protocols running, the CCP protocol has the priority, as shown below:

  • When the logger is powered up, it will first attempt to communicate via CCP to establish the connection.

  • Once the CCP/XCP connection has been established, the module will communicate via the Diagnostic protocol.

  • If no CCP connection can be established, the logger will not communicate via the Diagnostic protocol.

This means that the CCP module is the master and has priority. Therefore, users must establish this connection if a structure is configured with a CCP protocol.

This priority is established to stop any unwanted waking of modules by Diagnostic polling. Diagnostic polling will be possible only when the vehicle is awake, allowing CCP/XCP communication.

PreviousData Option of the Navigation bar, Settings MenuNextAppendix 2

Last updated 1 year ago