CARMACloudPlugin: TCR oldest issue in simulation environment

[dan-du-car]

PR Details

Description

Current TCR message is populated with oldest value based on the epoch timestamp, and defined as how many minutes from now. However, in simulation environment, the clock reference is not epoch time, it is customized clock starting from 0. This can be an issue with the current oldest implementation in v2xhub because the carma-cloud application in simulation environment uses the oldest value generated by V2xHub and reference it based on the simulation time rather than epoch time. Also, carma-platform running in the vehicle cannot control the oldest value generation. This PR is to update the TCR message oldest field with data sent by carma-platform in simulation mode.

Related Issue

NA

Motivation and Context

XIL integration testing

How Has This Been Tested?

integration tested

Types of changes

• [x] Defect fix (non-breaking change that fixes an issue)
• [ ] New feature (non-breaking change that adds functionality)
• [ ] Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• [ ] I have added any new packages to the sonar-scanner.properties file
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document. V2XHUB Contributing Guide
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
D Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint