Hi Nick, When you ask is there a way to enable 32-bit time stamping, at what level are you looking to do this?
The only way to do this is by changing the code. In BoilerPlate all you need to do is change the timestampX variables from 16 bit to 32 bit, change the data packet format accordingly (to use 4 bytes for the timestamp instead of 2), and copy the longer timestamp into the packet (in the prepareDataPacket() function). Note that you would also need to modify the host side software, e.g. ShimmerConnect, so that it knows that the data packet format is different. Again, this is easily done if required. However, what problem are you trying to solve by using a longer timestamp? BoilerPlate is designed to be constantly streaming at a rate greater than or equal to 1Hz. The host side device, be it a PC, laptop, phone or whatever, surely has a clock with enough resolution to know if it hasn't received a message for over 2 seconds (the time it takes for the timestamp to roll over). You are probably better off detecting such a high rate of packet loss at the host side for a number of reasons, not least that sending an extra two bytes with every single data packet will have a significant impact on the shimmer's battery life. Mike On Tue, May 24, 2011 at 9:06 PM, Nicholas Hosein <[email protected]>wrote: > I noticed that the time stamp in the boiler plate app was 16 bits instead > of 32. Because of this it rolls over quite frequently. Is there a way to > enable 32 bit time stamping? > _______________________________________________ > Shimmer-users mailing list > [email protected] > https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users > >
_______________________________________________ Shimmer-users mailing list [email protected] https://lists.eecs.harvard.edu/mailman/listinfo/shimmer-users
