2023 Terrain FireFly G12 Faults

[WPW-JAY]

hey there notice your comment. That's interesting about the firmware. I didn't know we could update it. Also when I check mine my GUI and LC is 11.15. My Firefly system hasn't had any issues. Most of my issue on the battery have been related to inverter settings.

 

[JFlightRisk]

snip...

AM i missing something here. The more I read the JOF, the more I read about factory defaults and the difficulty getting them resolved brings me to the conclusion that I need to buy a different brand.

No, you're not missing anything, but Jayco along with many other RV manufacturers source and install the same components from second party suppliers and have no control over their products. They are responsible for their own warranty, or lack of it. The propane regulator recalls affected tens of thousands of RVs on many brands. Similar to the Takata airbag debacle in cars and trucks.

I agree that owners that have stationary campers should have the ability to replace their own regulators, but that comes down to a legality thing because of the potential to improperly install one and have a fire or worse. I'm sure it was insisted upon from their legal department to keep lawsuits from dropping up. I'm not defending anyone, or their decisions, just throwing out some facts.

 

[ajais]

The G12 Offline issue appears to be an issue with 2023 Terrains.

 

[TimYeomans]

TSB 22-076 was performed on my 2022 Terrain by Camping World Longmont, CO and now I am having the issue of lights going out whenever I operate the motorized bed or the heater fan.
I did not have this problem prior to the installation of the G4 terminator block.
I unplugged the orange wire from the terminator block and the lighting issue is no longer a problem; however, the Firefly screen immediately goes to SOC 0%.
My terminator block has 2 blue wires and 1 orange wire. Does that sound correct?

 

[ajais]

This is a very interesting data point! I am working with Dehco on this issue. I will keep you all posted.

 

[ajais]

TSB 22-076 was performed on my 2022 Terrain by Camping World Longmont, CO and now I am having the issue of lights going out whenever I operate the motorized bed or the heater fan.
I did not have this problem prior to the installation of the G4 terminator block.
I unplugged the orange wire from the terminator block and the lighting issue is no longer a problem; however, the Firefly screen immediately goes to SOC 0%.
My terminator block has 2 blue wires and 1 orange wire. Does that sound correct?

Tim, this problem may have been solved by a fellow owner on the FB group thanks to this post! You gave us the hint needed. Put the termination block back on and add ferrite cores to the G12 side of the CANBUS lines (orange wires). The problem is noise on the CANBUS causing the G12 to reboot!

 

[TimYeomans]

Ajais, Wow, that is really good news. Unfortunately, I can't try the ferrite noise filters because I dropped my Terrain off at Camping World yesterday morning along with a full page write up of the problem. I will pass this new information to my service advisor.
Can you tell me what FB group you referenced in your message? I would like to check it out.
Thanks fso much for getting back to me.
Tim

 

[ajais]

It is the "Jayco Terrain and Entegra Launch Owners" group.

 

[ajais]

The ferrite cores may just be a patch over a bigger problem. There should not be that much noise on the CAN bus. The fact that pulling the orange line from the Termination Block solved one problem indicates a design fault in the CAN bus. These are core principals for CAN:

A CAN bus termination (of 120 Ohm each) must be present at the two physical end points of the CAN network and no where else.

The CAN network has to be connected from one node to the other with a bus termination for each of the two end points. A CAN network has no ring topology and there should be no stub lines present (so it is just a straight bus with termination at both ends)

At least one CAN device must have a fixed CAN bit rate configured. If more than one CAN device has a fixed CAN bit rate configured, it must be the same for each of these CAN devices.

Each CAN node ID must be unique in the CAN network, i.e. all CAN slaves must have a different CAN node ID configuration.

Dehco is working on this. I will report back once I know more.

 

[TimYeomans]

Interesting, Look forward to the Dehco response.