Hello all,

Is it possible to increase the limit on the snapshot logger? I need a lot more then 180 entries which it seems to be currently limited to.

Please let me know.

Thanks in advance,

Bryant

The limit is 180 records and could be less if the record size gets larger. The limits for Flash usage is 1 Kbytes and the text memory size is 4 Kbytes which does not seem like a lot. I'm checking with the developers whether these sizes can be increased in the display but right now there is no way to increase the number of records without get a compilation warning. An alternative method would be to get access to the USB filename ( or "LogFile.csv"). If you had access to the filename you could time stamp the file name and store multiple files on an attached USB Thumb drive. Would this be a viable solution? I've enclosed a PowerVision frame identifying the parameters we are investigating to get more Snapshot Records.

Hello pcebuhar,

The parameter you have highlighted in the screen shot is indeed what my original post was referring to. I'm not sure if you mean it can only store 180 entries per snapshot logger, meaning I could have 180 x the number of snapshot loggers I have, or is 180 for the whole PV450?

180 seems tiny for a data logging function. Why have the function there if it is only storing such as a tiny amount of information?

It would be good if there was a way around having to have multiple files.

Hello all,

Was there any more feedback on this problem? I need to make some decisions on what I'm going to do with this project.

The intent of this feature is to allow capturing data immediately before a critical event such as an engine shutdown to help determine the state of the machine leading up to the shutdown.
As an example if you select a sample count of 100 with a sample interval of 100mSec the selected variables will be continuously stored in RAM then when a snapshot log entry is called the data from RAM is dumped into FLASH and you will have a 10 second history at 100mSec intervals of the selected variables that can be analyzed to determine cause of shutdown.

There is a limit of 180 log entries and 85 variables however there is not limit on number of samples and sample interval other than the available memory.

To track engine shutdowns 180 log entries is fine but as different applications arise the 180 log entry count is limiting as in this case. A change to the limit has been placed on the list of requested feature changes and is expected to be implemented in the next major release version 2.8 which will occur around the first quarter of 2014. What it will be changed to is undetermined at this time.