DNSV4:Add TLV generation

Summary:

Support for DeviceNet V4 Protocol Stack in Configuration Tool

Description:

With the introduction of the new version of the DeviceNet protocol stack (V4), it is imperative that our configuration tool evolves to support the new TLV-based configuration. This update necessitates a change in the database format to accommodate the new protocol's requirements.

Requirement:

As a developer, I want the configuration tool to support the generation of configuration databases for the new DeviceNet V4 protocol stack, so that the tool remains compatible and functional with the latest hardware.

Detailed implementation:

• Update the database format to a TLV (Type-Length-Value) based configuration, as required by the DeviceNet V4 protocol. More on TLV can be found here: Type-length-value - Wikipedia.
• Implement version-dependent database generation within the configuration tool. This ensures that the tool can generate databases compatible with both the new V4 version and older versions of the DeviceNet protocol.
• Modify the UI/UX of the configuration tool to facilitate the selection of the protocol version by the user, ensuring a seamless transition between different versions of the DeviceNet protocol.

Integration:

Ensure the updated configuration tool integrates smoothly with existing systems and workflows, particularly focusing on compatibility with systems still using older versions of the DeviceNet protocol.

Test and Documentation:

• Conduct comprehensive testing to verify that the configuration tool correctly generates TLV-based databases for the DeviceNet V4 protocol, and ensures backward compatibility.
• Update the user manual and online help documentation to include instructions on how to use the new features, with a focus on the version selection and TLV-based configuration aspects.
• Prepare and deliver training sessions for the technical support team on troubleshooting and supporting the updated configuration tool.

Acceptance criteria:

• The configuration tool must successfully generate a TLV-based configuration database for the DeviceNet V4 protocol.
• Backward compatibility with older versions of the DeviceNet protocol must be maintained.
• UI/UX updates for selecting the protocol version must be intuitive and user-friendly.
• All new features and changes must be thoroughly documented and communicated to the end-users and support teams.