Development Scope
Scope and Basic Check
Determine the existing foundation, technology dependencies and content that needs to be developed based on the authorization message definition, frame format, bit rate, wire harness terminal resistance, node role and data cycle.
Implementation and integration
Implement frame reception, field parsing, timestamps, aggregation and uploading, limit sending according to bus roles, and add bus abnormal status records.
Delivery Documentation
Deliver parsing code, field tables and bus integration testing records.
Verification and Constraints
Having the CAN interface does not mean opening the business protocol. Parsing and writing must be based on authorization information and test conditions.
Project implementation process
Verification of data and interfaces → Confirmation of technical solutions and verification use cases → Implementation of integration with the target environment → Regression of abnormal scenarios → Transfer of version data.
Verify the implementation results in the target hardware and software environment, and deliver records of associated interface configurations, version dependencies, and problem handling to facilitate subsequent integration and maintenance by the enterprise R&D team.
Project Inputs
- Authorization message definition, frame format, bit rate, harness termination resistance, node role and data period.
- Design information, code, interface permissions and target test equipment can be provided.
- Source files, programs or tools expected to be delivered, inter-module integration testing responsibilities and project nodes.
- Acceptance samples, environment, test conditions and passing thresholds.
Deliverables and Acceptance
| Deliverables | Delivery content | Verification method |
|---|---|---|
| achieve results | Deliver parsing code, field tables and bus integration testing records. | Check field width, sign, and scaling. |
| Integrated data | Versions and dependencies, interface configuration, usage or deployment steps, and integration changes | Test for high load, frame drops, and node drops. |
| Verify records | Test conditions, execution records, problem lists and regression results | Verify bus recovery and platform timing sequence. |
The delivery scope and acceptance criteria are determined based on the target environment. Third-party SDK, licenses, laboratories, cloud resources, equipment materials and on-site support are listed separately; when the existing information is insufficient, follow-up work will be determined through interface verification or key function verification.
Frequently Asked Questions
CAN How to choose between transparent transmission and business field analysis?+
Message forwarding is suitable for systems where the server has parsing capabilities; when the terminal needs to filter, aggregate, alert or reduce traffic, it can parse fields according to the authorization protocol. Both methods require clear timestamps and exception handling.
4G CAN What information needs to be provided first for data collection and forwarding development?+
Please give priority to providing authorization message definition, frame format, bit rate, harness termination resistance, node role and data cycle. At the same time, the existing implementation, problems encountered, expected changes, and compatible test conditions are explained to facilitate the determination of implementation scope and reproduction methods.
Can it be implemented on existing products?+
You can first evaluate the scope of existing designs and versions that can be changed, retain the verified parts, and determine the interfaces and dependencies that need to be adjusted. Please note that for this service: having the CAN interface does not mean that the business protocol is open, and parsing and writing must be based on authorization information and test conditions. Existing and new functions must undergo regression testing within the agreed scope after the changes.
Online
Phone
WeChat
Top