Conext XW6848 Multi Inverter Random Shutdown F69

mike760

I have two XW6848 in a split phase master/slave configuration.  The slave unit randomly shuts down and displays a F69 code.  The master continues to run for a short period but eventually trips the DC breaker because the resulting load shift to one inverter is obviously too high at 12KW.  The F69 error is never logged in the events.  Resetting both DC inverter breakers will restore normal operation.  I checked the AC sync cable and it appears to be connected well and in good condition.  The system has been installed for about 8 months and this just started this week and has been happening at random times throughout the day.

Dave Angelini

Which XW 6848 ?   Pro or + ?

mike760

It's a +

Dave Angelini

OK so it worked master/slave fine for 8 months correct? When you say it is not logged are you using gateway/ events/ historical? Just curious on that?
Below is from Schneider but it is not really your problem. I suspect network cables or configuration. Tell us alot more about your set-up and use. Where, when, who installed, offgrid correct?, solar, all devices on xanbus, What are these large loads? etc.

Remember that a bad network cable can happen, they carry network power. I always have 3 in my truck.

F69 -  External Sync Failed (Multi-Unit Configuration fault)

To resolve this issue, clear the fault and disconnect everything (XANBUS, AC sync Cable) from the unit that requires the firmware upgrade. This will help rule out any communication issue due to noise and bad cables. Then connect the configuration tool directly to the single unit and proceed with the update accordingly. 

mike760

Thanks for the response.  Yes, I am using a gateway.  It was installed last summer.  Off-grid.  I installed it.  The largest loads would be air conditioners.

Connected devices:

2 @ XW6848+
8 @ MPPT 60/150
1 @ SCP
1 @ Batt Mon
1 @ AGS
1 @ Gateway
1 @ PDP
1 @ Volvo 100KVA Diesel Gen
24 @ Rolls Surrette 2YS 31P (2VDC 2527AH)
96 @ 250W Panels


So you are recommending a firmware update?  Here is some info on the problematic inverter:

XW6848-02 2

Online

FGA

865-6848-01

Device Name

XW6848-02

Unique Identifier

152593

Xanbus Address

2

Build Number

2.07.00bn4

Dave Angelini

As long as firmware is the same on both you are good. There may be one more update but your issue or similar was fixed before what you are running now. Gateway will not display much in this kind of fault as it is at the top of the list of bad things and F69 shuts down power. This should never happen. NEVER OFFGRID !

Looking at your devices there may be too many and xanbus or a cable is causing F69. This is deeper than I go on the forum and I do this for a living. My email is below. Good Luck !

MWAGNER68

@mike760

i have a very similar problem to you.  Our system sounds very similar as well … I have a parallel master-slave XW6848PRO system and I too have found this to be a relatively new phenomenon … I had convinced myself that maybe it truly was EMI noise from slugs of current confusing the communications link for the ac sync … and possibly even the Xanbus link to my BMS in my master battery via the Insight Home.  I’ve had this thing configured in a variety of ways added ferrites, shortened cables, tan cables outside the shielded channel, seappped ports, shielded the cables to no avail.   Also tried to link an high current slug event to the ‘confusion episodes’ but really cannot.  I have started to realize this happens on roughly a two week cycle and I think there maybe a combination of poor/non-robust communication link timing/design and possibly a related side effect I’d also being more susceptible to noise events tripping up the delicate timing.   I’ve had “communication error storms” that occur every couple weeks and this has been a recent occurrence.  When I’m one of these storms it seems that even a reset does not fix the problem for very long.  And then after that 12hr period of the storm time passes it runs like a champ for another couple weeks.  I think that the communications timing is either on a slip cycle where clocks slide in relation to data and then the system is in a precarious condition and vulnerable to noise confusion for that period of time until the asynchronous clocks slide further into a place where they once again have margin for error with noise triggering bad data reads.  They may or ma not have updated firmware with a fix but I am going to need to build a lot of confidence that the firmware upgrade is a proven fix for my problem before I risk creating more and other evils I do not know.  Or risk of bricking an inverter in the FW change process .   I’d be very interested to know if you found a fix and if it was in firmware upgrade?

MWAGNER68

Additionally … combined with my theory about the communication timing being vulnerable to noise in a cyclic manner every couple weeks … I know that the solar flare activity is a new event that may be bringing the interfering noise to the party and when combined with the periodic highly vulnerable to data slippage episodes we  we get this mysterious NEW issue all of a sudden.  Just my best theory to this point.  Hopefully I will hear that some people have had success with a FW upgrade.

Dave Angelini

What firmware are you running?  The post  from Mike is 3 years old and was an XW+. Not related to your xwp.

BB.

MW,

Please feel free to start a new discussion/thread... Avoids confusion with earlier Q&A's.

Bill "moderator" B.

MWAGNER68

Dave Angelini 

I totally agree that his system was XW+ and my system being XWPRO so his solution is not going to be my exact solution but I was still curious if he came to a resolution and if it ended up with Schneider fixing non-robust communications links with new firmware because that could be informative to me about the kinds of things I may find with my XW PRO issue.   I literally was going through one of those 12hr data comma funk periods on 6-1-24 when I wrote my comments … and like before … after pulling my hair out watching it go down then back up repeatedly and sometimes resetting it myself only to watch it get confused again shortly afterwards and watching it run it’s course … THEN it started running like a champ again (~12hrs later after initial fail of the sequence).

what I find is:  first will be the ac sync error followed by ‘perceived’ system multi-unit config error then I will also see ‘lost comms with BMS’ which spawns an erroneous ‘low SOC’ … and when I’m in one of these periodic extended error storm funks it will continue going through this sequence even with me providing resets once i become frustrated with watching the system go down then back up and down etc.  I do know that there is definitely heightened Solar flare activity this weekend and these Solar events have been a fairly common occurrence in recent months … I definitely feel it is susceptibility and noise source combinational type problem … and after seeing about 3 to 4 of these ‘error storms’ repeating every ~2-3weeks I am definitely starting to see a pattern with the timing between events. 

You asked what FW on the XWPROs I am running … it is 1.11.01bn49 on both 

If you know of any other similar issues that other people are having … or if the clues that I am watching and the pattern I’ve seen develop helps you in any way with other systems that are acting up I’d be very interested to hear from you. 

I’d also be very interested in knowing if you’ve seen a correlation with solar flare activity and increased frequency of data comms link errors on ac sync link and even on XANbus.

thanks in advance.

if this conversation takes off, I will start a new discussion thread (as was suggested by a moderator) … explaining my symptoms in a more detailed manner to help inform anybody who might have some answers from their experiences with other similar systems… 

MW

Dave Angelini

You are running the right firmware as the later version is being replaced and you should not install it.

Did you update to this firmware and did you set the region code when if you did update?

MWAGNER68

I didn’t have to update to this FW.  Both my inverters were this version out of the box in Fall 2022 at time of install and I am not selling to grid … majority of the time my config is completely off grid.   

MWAGNER68

I would have to go back through my notes and check what the region code choice that I had found in my research through Schneider install resources (Eric video) and also in other setup and configuration instructions.   I distinctly remember there being a particular selection that I was to make for my scenario as the appropriate choice.   Knowing I was going to be off grid and with no grid share I did the “set and forget” and I’ve forgotten what the choices were and which I was instructed to use.  

Your question to me specifically asked about the region setting IF and seemingly ONLY IF I had to personally update to this FW version (which I didn’t have to) … should I go dig into settings to see what I set it to?  Or is that not necessary since I didn’t update to this FW version?

I appreciate your insight on this issue and any possible remedies.  

Dave Angelini

You probably should know how it is set to eliminate this as a source. From the commissioning video below.

Enter the password that you obtained in step 1 and click OK. Select an appropriate region for your utility.  – For off-grid, select IEEE 1547-2003

In case you have gotten into a bad state from ?  Power cycle the units and leave off until DC voltage falls below<2 volt on terminals of the inverter(Wait about 20-30 min)

That is the end of my general advice. I am in business and have used and field tested for Schneider since the beginning of XW. My email is below.  Good Luck !

MWAGNER68

Yes that is what I originally set to … (For off-grid, select IEEE 1547-2003) … I remember the IEEE part … 

Thanks and I definitely will keep you as a resources for future support for sure. However I AM not able to see the commissioning video or your email address that you referenced as ‘see below’

thanks 
Mike

BB.

If you are using your mobile device, signatures usually don't display.

Here is Dave's information:

"we go where power lines don't" 

Sierra Nevada mountain area   

 htps://offgridsolar1.com/ 

E-mail offgridsolar@sti.net

Dave Angelini

Thank-you Bill !  Hope all is peachy !

BB.

Thank you Dave,

Well--Not exactly peachy--More the "cycle of life" right now.

-Bill

MWAGNER68

Thanks to both of you