1.Network Architecture:

PXC24.2-EF32.A *4 (version 3.5.1) ,PXC100-E96.A *2  (version 3.4.0) ,some 3rd geteway and cc 4.1

2.Information:

PXC power supply and battery are normal.About a few months will occur in PXC points and PPCL loss. At this time, the points on the CC interface cannot be displayed. When CT opens the database online, the database is automatically downloaded to the fault PXC. It is learned from this phenomenon that the PXC is automatically cold under the normal situation of the power supply. Since the BLN network does not find Insight or CT, PXC is unlimited waiting for the main disk. When the CT is turned on, the database is automatically downloaded to the PXC.

================================================

page 6 in Firmware Revision 3.5.3 release notes.pdf

Section 2 - Fixed Issues
Firmware revision 3.5.3

●Desigo CC no longer fails to discover schedules and commands when the device fails to create a flash backup due to large state text definitions.
●Field panel does not coldstart anymore if multiple naming conventions, such as subpoint name and BACnet encoded names, are used in the database.
●Database backup to flash no longer locks up even during heavy FLN activity.
● Field panel does not coldstart anymore due to heavy global broadcast activity

================================================

"Field panel does not coldstart anymore due to heavy global broadcast activity ",What does heavy global broadcast activity mean?Did he cause PXC to cloudstart?

The problem I encountered is the problem described in PDF. These problems have been fixed in the firmware of the version 3.5.3 version?

Should I upgrade to the firmware 3.5.3? Who can help me and provide a suggestion?

Thanks