How does E-PLEX® compare to other protocols like controller area network (CAN)?
No single protocol can perform all of data communication jobs that must be performed within any system, vehicle or piece of equipment optimally. As a result, a large number of multiplexing protocols have been developed and deployed to meet these specific needs. Generally speaking, protocols are “purpose-built.” CAN was built as a message-based system for quickly communicating safety-critical data such as throttle position, airbag sensors or dynamic suspension. Most vehicles, for example, need this sort of data communicated and CAN is the correct choice; the right tool for the job. E-PLEX® was built for a much broader, system-integration purpose. As such, E-PLEX® was designed to be very flexible. Rather than do just one job in a predefined way, E-PLEX® is logic-based allowing new features and functionality to be developed as needed for unique applications. Theoretically E-PLEX® can do what CAN does well and visa verse. However, optimal performance and the lowest possible cost is achieve
Related Questions
- When I run virtual media on the DRAC controller over a Wide Area Network (WAN) with low bandwidth and latency, launching OpenManage Install directly on the virtual media failed, what do I do?
- How does E-PLEX® compare to other protocols like controller area network (CAN)?
- What is Controller Area Network (CAN)?
