kewakl (Customer) asked a question.
Productivity Suite 3.7.0.10 (or any earlier version) Data Logger
I have triggered the datalogger when the microSD is not inserted, the help file has some sort or wordywordness that says that the data goes to the 73K buffer. I did not see any mention of how to recover this buffered data.
Is there any way to retrieve this data?
I understand that I SHOULD have the microSD installed to actually get the data out of the PAC, but there are times when things don't go to plan.
The buffer is 512K. I talked with the firmware developers and it appears there is a possible bug with the firmware. It should keep that any data if logging is still enabled in the buffer up to 512k, if that limit is reached any new data will be thrown away while the memory device is removed. However, we are not seeing the correct behavior due to the possible bug.
Currently, there is no method to get the buffered data while the memory device is removed.
I have entered a trouble ticket to our QA team to begin investigating this issue.
Sorry for any inconvenience this maybe causing.
Forgot to ask. Which CPU are you using and what firmware revision?
Sorry, I should have included this in the OP, as I ask this all the time, too!
H/W P1-540 -- just CPU, No Physical IO
F/W 1.2.8.30
S/W 3.7.0.10
PSU P1-01AC
>Currently, there is no method to get the buffered data while the memory device is removed.
When the MicroSD device is reinserted, after buffering any data, it would be nice to have some method to either (1. dump the buffer content to the MicroSD) or (2. purge all buffer content)
Also, some status of MicroSD/USB DataLogger activity would be nice ---- BUSY/COMPLETE.....
As it is now, I just populate the tags, trigger and wait -- and hope that I allow enough time - but not too much time.
I am using the Productivity Data logger for the first time today and using the Event Data Logging mode, I have no idea how quickly I can log data (I would like to as quick as possible). What would happen if I tried to log data quicker than it could be written to the file?
I cannot say for sure, but I would guess that it depends on a combination of your sample frequency, sample data size and how long that this sample frequency is maintained. Maybe you can provide details about your sample dataset(tagtype and number of tags)/frequency/duration and someone can help determine if you would have trouble.
There is a buffer ( [1] 512Bytes according to the help file and 512K bytes -- according to techsupport) that will fill first and then get written to the SD/USB - if present.
aside - there is also (according to the help file) a 73Kbyte buffer for those times when the media device is not connected. However, there is currently ( [2] at least from my last conversation with AD techsupport) no way to get this logged data once the media device is connected
---------------------------- From the Help file
[1]
Note: If event logging is selected and data log buffer reaches 512 bytes of data, then the buffer will write 512 bytes segments to the pen drive (unless pen drive is not present), in attempt to lower data log buffer below 512 bytes. However, how fast the buffer is filled is dependent on the frequency of event, the number of tags, and data types of these tags selected for logging.
---------------------------- From AD forum techsupport
ADC Community_02
Open ADC Community_02 Preview
(Automationdirect.com)
9 months ago
Actions for this Feed Item Comment
[1] The buffer is 512K. I talked with the firmware developers and it appears there is a possible bug with the firmware. It should keep that any data if logging is still enabled in the buffer up to 512k, if that limit is reached any new data will be thrown away while the memory device is removed. However, we are not seeing the correct behavior due to the possible bug.
[2] Currently, there is no method to get the buffered data while the memory device is removed.
I have entered a trouble ticket to our QA team to begin investigating this issue.
Sorry for any inconvenience this maybe causing.
Yesterday I tested logging as quick as possible (logging on triggered by the done bit of a .001 sec stmr instruction with preset set to 0). Had no issues, looked at the data and it appeared to be logging around the average CPU scan time (1.8ms). I am logging 21 tags (1 X int32, 1 X uint16, 14 X boolean, 5 X float32).
I am using a 32GB card, would love to know what happens when there is no space left...