admin@axcf2152:/opt/plcnext$ df
> Filesystem 1K-blocks Used Available Use% Mounted on
> tpmfs 250868 340 250528 1% /var/volatile
> /dev/root 356011 267778 65332 81% /media/rfs/ro
> /dev/mmcblk1p1 1891212 685696 1091396 39% /media/rfs/rw
> overlay 1891212 685696 1091396 39% /
> /dev/mmcblk0p6 499656 396 462564 1% /media/rfs/internalsd
> devtmpfs 250356 112 250244 1% /dev
> tmpfs 250868 128 250740 1% /run
> /dev/mmcblk0p7 27633 442 24898 2% /etc/device_data
> cgroup 250868 0 250868 0% /sys/fs/cgroup
> /dev/loop0 3840 3840 0 100% /opt/plcnext/apps/60002172000269
> admin@axcf2152:/opt/plcnext$
Here, I have only used 39% of the available space on my user file system. If you are at or near 100% usage, then this might be why no data is being logged. If disk space is OK, then let’s move on: The datalogger configuration in PLCnext Engineer should generate this file:
/opt/plcnext/projects/PCWE/Services/DataLogger/pcwe.MyDataLogger.dl.config
(where “MyDataLogger” is the name of your DataLogger Session from PLCnext Engineer). You should see the configuration values from PLCnext Engineer in that file, in XML format. Next: Please check the contents of this file:
/etc/plcnext/device/Services/DataLogger/Default.dl.config
You should see these entries:
Include path="$ARP_PROJECT_DEFAULT_DIR$/Services/DataLogger/*.dl.config" /
> Include path="$ARP_PROJECT_CURRENT_DIR$/Services/DataLogger/*.dl.config" /
This tells the DataLogger component where to find the configuration file that was generated by PLCnext Engineer. Next: It is possible to disable the DataLogger component using a quite complex procedure. You will probably know if you’ve done this, but to be sure - please check that you do not have the following file on the PLC:
/opt/plcnext/appshome/Device.acf.settings
If this file does not exist, then that’s good. If the file does exist, then please let us know the contents of that file. Next: Please check the contents of the file /opt/plcnext/logs/Output.log. You should see recent entries something like this:
22.10.20 10:57:59.518 Arp.System.Acf.Internal.Sm.ProcessesController INFO - Library 'Arp.Services.DataLogger.Library' in process 'MainProcess' loaded.
> 22.10.20 10:58:06.934 Arp.System.Acf.Internal.Sm.ComponentsController INFO - Component 'Arp.Services.DataLogger' in process 'MainProcess' created.
(these messages should appear every time the PLC restarts). Please also check the Output.log file for any recent messages related to the DataLogger - especially any error or warning messages. When everything works OK, you should see a .db file in the following directory:
/opt/plcnext/logs/datalogger
The name of the .db file will be the same as the DataLogger “Session” name in PLCnext Engineer. This is a sqlite file containing the historical data. =========== Something in the above steps will indicate why the DataLogger is not working in your case. To your final question:
Is there an opportunity to transfer the values with the PLCnext Engineer DataLogger to the remote server?
The DataLogger itself does not provide this feature. However, since data is logged to files on the PLC, any mechanism for copying files to a server should work, e.g. scp, sftp, or rsync. It will partly depend on what services are available on the server. Hope this helps. Martin.