# Handling mixed v0/v1 and Classic CAN / CAN FD networks

**URL:** <https://forum.opencyphal.org/t/handling-mixed-v0-v1-and-classic-can-can-fd-networks/1230>\
**Category:** Development & Maintenance\
**Created:** [May 4, 2021, 3:30am UTC](https://forum.opencyphal.org/t/handling-mixed-v0-v1-and-classic-can-can-fd-networks/1230 "2021-05-04T03:30:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![coder\_kalyan](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/coder_kalyan/32/1361_2.png) [@coder\_kalyan](https://forum.opencyphal.org/u/coder_kalyan)\
**Post date:** [May 4, 2021, 9:28pm UTC](https://forum.opencyphal.org/t/handling-mixed-v0-v1-and-classic-can-can-fd-networks/1230/3 "2021-05-04T21:28:10Z")

</div>

## Classic CAN vs CAN-FD

Sadly, this problem does not have a clear-cut solution. The lack of a large selection of affordable MCUs with CAN-FD capability (especially more than 1 CAN-FD controller) paired with the current silicon shortage is likely to drag adoption out for the next few years at least. The biggest issue is that a single node that is not FD-compatible causes problems for the entire network. A band-aid solution to this might be to implement conversion nodes as @tridge mentioned, to connect a classic network to an FD one. This is far from ideal, I know, but it might accelerate adoption a bit. If anyone has any good ideas on how to go about this, please speak up 🙂

---

_[View the full topic](https://forum.opencyphal.org/t/handling-mixed-v0-v1-and-classic-can-can-fd-networks/1230)._