Let’s suppose that you are a developer, tasked with designing products for RVs, and you want your products to coordinate with other devices in the RV. Maybe you just want your widget to show up on the multi-purpose touchscreen that are common today, or perhaps your product would benefit from knowing what other devices are doing – like whether the park brake is set or the generator is running. RV-C™ is the key technology that can make that happen. But getting started can be intimidating – but don’t worry, it’s really not hard at all.
The first place to start is the RVIA web site. As standards bodies go, the RVIA is different . . . and awesome! Unlike most organizations, they aren’t in it to make a buck selling the spec or other resources. Their sole interest is in helping the RV industry – their members – flourish. The RVIA’s leadership sees RV-C as an asset for the industry which they want to grow and refine. Educating developers fits in with those goals.
If you are starting from scratch, the first link you should hit is this 2-hour video, a webinar recorded about a decade ago. It starts out pretty basic, but resist the temptation to skip it or fast-forward through. If you do, you might miss a few bits that sound almost banal but actually are extremely important.
https://www.rvia.org/news-insights/rv-c-101-video
The main RV-C web page (https://www.rvia.org/rv-c) includes a link to the current protocol document. Read the first five sections clear through. As for the rest, just read the parts that apply to the products you are interested in.
Once you have the basic concepts clear in your mind, download this short document. It outlines some of the most crucial items that you need to get right. If you understand and implement its contents, your chances of releasing a first-rate product on schedule will be excellent.
https://www.rvia.org/system/files/media/file/Designing%20RV-C%20Nodes-%20Best%20Practices%20for%20Component%20Vendors.docx