You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in installing this in my 2020 Breeze 33BR. I think I have the technical chops to do it, but I'm wondering if there are instructions on identifying the RVC ids needs to populate the JSON for a new model. Can I do it from the Spyder diagnostic panels or from the manifest on the front the of G6 panels?
The text was updated successfully, but these errors were encountered:
Definitely start with the 2019 Breeze JSON... there shouldn't be too many changes needed. The Spyder diagnostic panels have many of the IDs, but they're sometimes offset by 60 or so. You can compare your diag screen to the 2019 Breeze IDs and see if most things line up, to figure out the offset. Also, the CPOS software publishes all CANBUS messages over MQTT. If you install http://mqtt-explorer.com and connect to the CPOS device, you will be able to see everything going on in the RV... meaning, if you press a Spyder light switch on the wall, you'll be able to see the message that switch sends to the main Spyder system, including the ID. That method can be used to figure out new/changed IDs from year to year. The only difficult part will be things which aren't simple "DC_DIMMER_COMMAND" messages, like window shades, awnings, lifts, generator, etc. Sometimes those require actual software changes in the CPOS code.
If you're not in the Facebook CoachProxy group, you can join and get help from lots of people who have been through this and gotten it working on various 2020 models.
I'm interested in installing this in my 2020 Breeze 33BR. I think I have the technical chops to do it, but I'm wondering if there are instructions on identifying the RVC ids needs to populate the JSON for a new model. Can I do it from the Spyder diagnostic panels or from the manifest on the front the of G6 panels?
The text was updated successfully, but these errors were encountered: