Hello, I’m working with the Datalogger and had a couple of questions about functionality.
* Currently, it appears there is no way to remove files based on max files, etc. will this be added in the future?
* When using the datalogger's variable type function blocks (i.e. DL_AnyTypeFB) if the xActivate is set to true and the Datalogger FB is set to true(this is set first) it stops the controller. I found that by leaving the xActivate field empty for the variable type blocks it works fine. That said, is this a known issue and is the library safe to use?
Hi Josh, which Version of the DataLogger are you using in your application?
* Both described behaviors should be possible
* The current available Version in the AppStore is 2_07.
Please verify it. It could be possible that you use an older Version. If you still face issues it would be helpful for me if you can add screenshots of the used configurations of the FBs. Regards,
Mirko
I’m using the latest version (2_07). I did create my own means of deleting files but cannot find how to remove files with the library. For the issue I’m having please see attached image. I enable the xActDatalogger bit first then start to activate the DL_*Type_2 blocks. When the first block, DL_StringType_21, is activated the controller stops.
* _"I did create my own means of deleting files but cannot find how to remove files with the library. "
_ This feature is implemented in the FB “DL_File_2”. With the Input “iMaxFiles” you are able to activate a ring buffer mechanism. In the following I attached the description you can also find in the integrated help file:
Maximum files stored on the file system of the PLC. Valid values 0 - nn. 0 = deactivated. The file names are stored in a separate INI file.
* Activation sequence
In the help file it is also recommended to the other activation sequence:
Data type: BOOL
Description: Block activation. (TRUE = Active). If data point should be used this input must be set before xActivate @ DL_Logger_2
But that has the reason that the Header of the log file can miss in case if you use such a sequence in combination with the other datapoints. Why? After Activation of the “DL_Logger” will all active datapoints registered in the internal structure for the new file to be created.
Nevertheless the activation sequence in combination with the FB “DL_StringType” leads to your described error (PLC Stop). That should not happen. We will fix this issue with the next Version.
Workaround - Change activation sequence:
For example: Set the Input "xActivate of the datapoints at Default “True”.
The Log entry (data set) will be triggered with the Input “xReq” of the FB “DL_Logger”.
