Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Contact Us
  • Home
  • Helpjuice Import
  • 3rd Eye Portal

Validating Profile JSON Parameters to Confluence 2

Written by Chris Britton

Updated at June 29th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Soft-Pak Help Center
  • TIRC Help Center
  • Helpjuice Import
    3rd Eye Portal
  • Testing
+ More

Table of Contents

Guide Purpose: How to Get to CCM Profile JSON Reviewing Service Events JSON Parameters Di1 Active Review (Event creation) Di1_active Review (Camera Image/Video) Di1_active Review (Threshold) Di1_active Review (To Blink) Di1_active Review (Pre & Post Time) Di1_active Review (JPEG Time) Reviewing Cummins JSON Parameters Reviewing GSM Profile JSON Parameters Reviewing Storage Media JSON Parameters Reviewing Telemetry (Min. Time Between Service Exception and Verification Events) Reviewing Telemetry (Min. Distance Between Events and Over Speed Trigger Duration) Reviewing Telemetry (Service Events Threshold Speed and Hard Event Threshold Speed) Reviewing Tablet Integration Configuration JSON Parameters Reviewing Generic Telemetry (Generic Telemetry Feature, DPS Upload Time Interval, and J1939) Reviewing Generic Telemetry (Heil, DCI, and DM01)

Guide Purpose:

  • This guide IS designed to:
    • Show where to find current firmware for Tenant.
  • This guide IS NOT designed to:
    • Show how to setup firmware for Tenant.

How to Get to CCM Profile JSON

  1. Click on the Administration tab
  2. Select the Operations button
  3. Select the CCM profile button
  4. Select Base from the profile type drop down
  5. Select Production from the deployment type drop down
  6. Search the results the profile you want to review from the box highlighted in BLUE

  1. Select the profile you want to review
    1. For the purpose of this guide, we will use the 1_Default_Settings_
  2. Select the software version of the profile
  3. Click View MCF files to view the profile JSON

Reviewing Service Events JSON Parameters

We will be reviewing the changes made to this profile from the configuration default settings. This will provide insights on what to review when a profile has been made. The service event ICP type JSON parameter is “event_handler_controller”

Di1 Active Review (Event creation)

  1. View the DI1_active confluence configuration
  2. A fast way to look up any event type is to use “ctrl-f” to find the event type. Type in the event type (Di1) and it will highlight were it shows up in the JSON parameters.
  3. Review the event creation configuration in confluence to compare with the JSON parameter as highlighted in the GREEN box
  4. Review event creation JSON parameters by reviewing box highlighted in BLUE. This Parameter will always show “enabled”, and the value is what shows if it’s turned off or on.
    1. Value 1 = ON
      1. In this case the value is 1 which means Di1_active us turned on
    2. Value 0 = OFF

Di1_active Review (Camera Image/Video)

  1. Review the camera image column configuration in confluence to compare with the JSON parameter
    1. As we can see camera 1 through 8 are identified in this column to be enabled in this example as highlighted in the GREEN box
  2. Review the “camera” parameter in the Di1_active JSON configuration. All cameras are identified in this parameter sequentially from camera 1 to 8. It’s up to the team to enable the listed cameras from camera image configuration column in confluence page. Please note that this also applies to the camera video column.
    1. The box highlighted in BLUE focuses on camera 1 where parameter named “img” stands for image and “vid” stands for video.
      1. The value for “img” when enabled is “JPEG”
      2. The value for “Vid” when enabled is “MP4”
      3. The value for “img” when disabled is “NONE”
      4. The value for “vid: when disabled is “NONE”
    2. The box highlighted in ORANGE focuses on camera 2. The next parameter will be camera 3 and so forth till we get to camera 8.

Di1_active Review (Threshold)

  1. Review the Threshold/Special Settings column configuration in confluence to compare with the JSON parameter
    1. This section is used to determine the feet calculation value and the value for this example is 2ft as highlighted in the GREEN box
  2. Review Threshold/Special Settings JSON parameters by reviewing box highlighted in BLUE. This Parameter will always show “eventThreshold”, and the value should show the same integer/number as confluence

Di1_active Review (To Blink)

  1. Review the To Blink column configuration in confluence to compare with the JSON parameter
    1. This section is used to determine what color would blink on the V4 Camera when the event is triggered as highlighted in the GREEN box
  2. Review To Blink JSON parameters by reviewing box highlighted in BLUE. This Parameter will always show “ledToBlink”, and the value should show RED which is the selected color in confluence

Di1_active Review (Pre & Post Time)

  1. Review the Pre and Post time column configuration in confluence to compare with the JSON parameter as highlighted in the GREEN box for pre time and the RED box for post time
    1. This section is used to determine how many seconds the Camera video will record before and after the triggered event.
  2. Review Pre JSON parameters by reviewing box highlighted in BLUE. This Parameter will always show “pre_time”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 8
  3. Review Post JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “post_time”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 4

Di1_active Review (JPEG Time)

  1. Review the JPEG Time column configuration in confluence to compare with the JSON parameter as highlighted in GREEN box
    1. This section is used to determine the time calculation value and the value for this example is 0
  2. Review JPEG Time JSON parameters by reviewing box highlighted in BLUE. This Parameter will always show “jpeg_time”, and the value should show the same integer/number as confluence

Reviewing Cummins JSON Parameters

  1. Review the Cummins Config column configuration in confluence to compare with the JSON parameter under the ICP type name “cummins”
    1. The section shows Cummins feature is turned disabled/off as highlighted in the BLUE box
  2. Review Cummins JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “cumminsConfig”, and the value is what shows if it’s Enabled/On or Disabled/Off.
    1. Value on = Enabled
    2. Value off = Disabled
      1. In this case the value is off which means Cummins is disabled/off

Reviewing GSM Profile JSON Parameters

  1. Review the GSM Profile column configuration in confluence to compare with the JSON parameter under the ICP type name “service_provider”
    1. The section shows the GSM provide listed under Priority 1 as the primary provider which is highlighted in the BLUE box
  2. Review GSM Profile JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “serviceProviderName”, and the value should show the same character as confluence
    1. The Value in this example is “att”

Reviewing Storage Media JSON Parameters

  1. Review the Storage Media column configuration in confluence to compare with the JSON parameter under the ICP type name “storage_media”
    1. This section shows the storage media type selected as Sequential which is highlighted in the BLUE box
  2. Review Storage Media JSON parameters by reviewing the box highlighted in ORANGE. This Parameter will always show “ModeSelection”, and the value should show the same character as confluence
    1. The Value in this example is “sequence”

Reviewing Telemetry (Min. Time Between Service Exception and Verification Events)

  1. Review values of the Min. Time Between Service Exception as highlighted in the BLUE box and Verification as highlighted in the RED box Events rows configuration in confluence to compare with the JSON parameter
  2. Review Min. Time Between Service Exception Event JSON parameters by reviewing box highlighted in GREEN. This Parameter will always show “service_excep_event_time_filter_sec”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 3
  3. Review Min. Time Between Service Verification Event JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “service_verif_event_time_filter_sec”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 3

Reviewing Telemetry (Min. Distance Between Events and Over Speed Trigger Duration)

  1. Review values of the Min. Distance Between Events as highlighted in the BLUE box and Over Speed Trigger Duration as highlighted in the RED box rows configuration in confluence to compare with the JSON parameter
  2. Review Min. Distance Between Events JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “service_distance_filter_feet”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 5
  3. Review Over Speed Trigger Duration JSON parameters by reviewing box highlighted in GREEN. This Parameter will always show “udu_adxl_duration”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 15

Reviewing Telemetry (Service Events Threshold Speed and Hard Event Threshold Speed)

  1. Review values of the Service Events Threshold Speed as highlighted in the BLUE box and Hard Event Threshold Speed as highlighted in the RED box rows configuration in confluence to compare with the JSON parameter
  2. Review Service Events Threshold Speed JSON parameters by reviewing box highlighted in GREEN. This Parameter will always show “service_events_threshold_speed”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 10
  3. Review Hard Event Threshold Speed JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “hard_events_threshold_speed”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 20

Reviewing Tablet Integration Configuration JSON Parameters

  1. Review the Tablet Integration configuration in confluence to compare with the JSON parameter under the ICP type name “tablet_integration”
    1. This section shows Tablet Integration turned on as highlighted in the BLUE box
  2. Review Tablet Integration JSON parameters by reviewing the box highlighted in ORANGE. This Parameter will always show “enabled”, and the value is what shows if it is turned off or on.
    1. Value on = Enabled
      1. In this case the value is on which means Tablet Integration is turned on
    2. Value off = Disabled

Reviewing Generic Telemetry (Generic Telemetry Feature, DPS Upload Time Interval, and J1939)

  1. Review values of Generic Telemetry Feature, DPS Upload Time Interval and J1939 rows configuration in confluence to compare with the JSON parameter as highlighted in the BLUE box
  2. Review Generic Telemetry Feature JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “genericTelemetryEnable”, and the value is what shows if it’s turned off or on.
    1. In this example, the value is on
  3. Review DPS Upload Time Interval JSON parameters by reviewing box highlighted in GREEN. This Parameter will always show “dpsUploadInterval”, and the value should show the same integer/number as confluence.
    1. In this example, the value is 10
  4. Review J1939 JSON parameters by reviewing box highlighted in PURPLE. This Parameter will always show “j1939”, and the value is what shows if it’s turned off or on.
    1. In this example, the value is on

Reviewing Generic Telemetry (Heil, DCI, and DM01)

  1. Review values of Heil, DCI, and DM01 rows configuration in confluence to compare with the JSON parameter as highlighted in the BLUE box
  2. Review Heil JSON parameters by reviewing box highlighted in ORANGE. This Parameter will always show “heil”, and the value is what shows if it is turned off or on.
    1. In this example, the value is on
  3. Review DCI JSON parameters by reviewing box highlighted in GREEN. This Parameter will always show “dci”, and the value is what shows if it’s turned off or on.
    1. In this example, the value is on
  4. Review DM01 JSON parameters by reviewing box highlighted in PURPLE. This Parameter will always show “dm01”, and the value is what shows if it is turned off or on.
    1. In this example, the value is on

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Customer Profile Fields
Terex Corporation logo
Products & Solutions
  • Equipment
  • Services
  • Merchandise
  • Terex Telematics - Terms of Use
  • Digital Solutions
Company
  • Purpose, Mission & Values
  • Culture & Inclusion
  • Contact Us
  • News
  • Press Releases
  • Intellectual Property & Patents
  • UK Group Tax Strategy
  • Suppliers
Sustainability
  • Product Innovation & Customer Solutions
  • Responsible Operations
  • Team Member & Community Engagement
  • Governance
  • Modern Slavery Statement
  • California Transparency Policy
Investors
Careers
  • View Job Openings

Looking for a Terex dealer ?

Preferences
Site Map
Linking
Terms of Use
Privacy Policy
Cookie Notice
Accessibility
© 2025 Terex Corporation. Terex, the Terex Crown Design, Works For You, Genie, Powerscreen, Finlay, EvoQuip, CBI, Ecotec, Fuchs, Advance, Bid-Well, Simplicity, Cedarapids, Canica, Jaques and Franna are trademarks of or licensed by Terex Corporation or its subsidiaries.
Expand