![Victron energy CCGX Скачать руководство пользователя страница 18](http://html.mh-extra.com/html/victron-energy/ccgx/ccgx_instructions-manual_1014786018.webp)
Last update: 2018-08-21 10:10
ccgx:start
https://www.victronenergy.com/live/ccgx:start
https://www.victronenergy.com/live/
Printed on 2018-08-21 11:59
Because of the aforementioned improvement in sending of backlog data, the data logging is also
highly resillient to bad internet connections. Lines of up to 70% permenant packet loss are still
sufficient to get the data out, albeit somewhat delayed.
With a log interval of once per minute, the required storage space roughly amounts to about 25 MB
per month, depending on the number of connected products. So with a 1 GB microSD card, you can
store about 3 years of backlog. In other words, any microSD card or USB stick should be sufficient to
store the 6 months of data which VRM retains.
When the storage device is full, no more data will be logged. This is due to the nature of Sqlite files.
Removing data from the Sqlite database doesn't free-up usable disk space; and because of internal
fragmentation, it doesn't guarantee more data storage.
If both a microSD card and a USB flash drive are connected to the CCGX, then data is logged to the
one that was inserted first. If one is removed, the CCGX will not try to write to the other, but will
create an internal backlog buffer until a new storage medium is inserted when it will use that storage
medium.
MicroSD cards or USB flash drives must be formatted as FAT12, FAT16 or FAT32 file systems -
and not exFAT or NTFS.
SD and SDHC type microSD cards of 32 GB capacity and smaller are sold containing FAT12,
FAT16 or FAT32. They can be used without a problem, unless they are subsequently re-
formatted to a different file system.
SDXC type microSD cards which have greater than 32 GB capacity are often formatted with
exFAT, and therefore cannot be used with the CCGX without reformatting and possibly re-
partitioning.
2.3 Using the Multi and Quattro input current-limiter setting
'Overruled by remote' setting in VEConfigure
This chapter explains the implications of enabling or disabling user control of the input current-limiter
setting, as seen here in the menu: