RTC alarm

Hello,

Can anyone lend some info on the following problem. Our vector is triggered to start by applying power to it, thus the status code returned is break for the wakeup state. So I have two weeks of data with the binary number 1x10^4 which indicates break as the wakeup state. However, in one of my profiles, the code for RTC alarm is output in the 1 Hz *.sen data. This seems odd to me since the start of the data collecting was started about a minute prior to this code being returned.

Does anyone have any idea why I would get a status code of RTC alarm in the middle of a burst (actually a burst that was triggered to start by applying power to the vector) after it was started with a break as a wakeup state?

Thank you for any explanations,

Dave

It may be 8 years later but I think that we may be experiencing similar problems.

Recently during the file conversion process of turning .vec files into .dat files of some Vector burst mode data an error occurs that says: 'Error or suspicious events found. Please check the system state (.ssl) file.' Upon examination of the .ssl file it shows that on the second burst (only on the second burst) there is an error that occurs with Ecode 00, Scode 33, and Description 'Wakeup state: RTC alarm' .  It would be a great help if anyone could provide any insight on what this error is and why it is occurring.

This doesn't appear to be affecting any of our data but it would be useful to just know what the problem is.

Thanks for any additional info.

~Jeff

Hi Jeff,

I hope the ssl-file just list the RTC alarm as a warning and not an error. In any case this is not a problem, when using the start now deployment option or when starting an online measurement the wake-up state will always change from power on/break in the first burst to an RTC alarm in the second measurement. The software should probably have listed this just as information instead of a warning.

The intention of the ssl-file is to provide you with a readable overview of events during the measurement, for example if the orientation changed, tilt out of range or power glitches. 

Best regards,

Sven Nylund