Timeline for Time elapsed between two 8-bit timestamps
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2016 at 2:33 | review | Close votes | |||
| Mar 27, 2016 at 16:51 | |||||
| Dec 16, 2015 at 9:20 | vote | accept | mariusmmg2 | ||
| Dec 15, 2015 at 14:09 | answer | added | Rotem | timeline score: 2 | |
| Dec 15, 2015 at 14:05 | comment | added | mariusmmg2 | @Clockwork-Muse I can't, I'm stuck with this format. | |
| Dec 15, 2015 at 14:00 | comment | added | mariusmmg2 | @Rotem I'm not actually sure what they represent... but the presented method works, if the sec bytes are identical, substract the msec ones, and you'll get the elapsed msec. This is all the info. that I got. L.E. It may actually be 1/256ths of a second. | |
| Dec 15, 2015 at 13:52 | comment | added | Rotem | @André Well there are only so many values per bit. Either he'll need to use lower resolution (e.g. 10ms) increments or a single 16-bit value for seconds and miliseconds (basically just milliseconds) which can count up to ~6.5 seconds. | |
| Dec 15, 2015 at 13:48 | comment | added | André | Maybe he is within some hardware with this limitation | |
| Dec 15, 2015 at 13:47 | comment | added | Clockwork-Muse | ...I'd probably start by getting a 16bit timestamp representing milliseconds. | |
| Dec 15, 2015 at 13:46 | comment | added | Rotem | How is it milliseconds if it's incremented at 255? It's actually 1/256ths of a second, isn't it? | |
| Dec 15, 2015 at 13:37 | review | First posts | |||
| Dec 16, 2015 at 3:46 | |||||
| Dec 15, 2015 at 13:34 | history | asked | mariusmmg2 | CC BY-SA 3.0 |