[[email protected]]

This, sadly, is a VERY complex issue to which I am all to familiar with!

I have many LONG conversations with one of the smartest electronics engineers I know, who not only has a 2020, but has developed what he calls a Coach Processor that is designed to take all of the heavy lifting off of the Coach network.

It’s not about “balance”; it’s about overload. Just yesterday, I was discussing this with my friend. Firefly continues to BREAK more than they FIX. Every “update” seems to cause other issues. The cause, from this expert friend is simply too much constant polling and traffic on the RVC/CANBUS network.

This is why Newell can’t fix the problem. They rely on Firefly…and that company is a disaster and I won’t go into my 5-month crap show I just ended with them on our 2015; and NO…we don’t have Intrepid, Thank God.

So, this lets you know the problem. My friend would tell you to use his processor, but many would argue against it to say the problem should be fixed without the need for a special device.

It’s a big issue that, unfortunately, Newell continues to battle since…realistically…they are but a “small fish” without much weight to push around. And taking on a complete rewrite of their system would be cost and labor intensive.

Steve, appreciate the insight. Too much traffic on the network sounds more like something I could understand, again I am no expert on this stuff but I do understand the concepts. I have considered automating some things on my coach and I actually have a PLC that I am thinking about playing around using for this. PLC's have been used for a long time to automate many things and they are quite robust, powerplants and many production facilities all run on PLC's. This seems like something that could be adapted for this use and would be much more reliable.