29c3

From sigrok
Revision as of 16:27, 16 December 2012 by Bert (talk | contribs) (Created page with "We're getting together at the annual CCC conference, [https://events.ccc.de/congress/2012/wiki/Main_Page 29c3], for a sigrok hackathon. In addition to the usual "whatever we f...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

We're getting together at the annual CCC conference, 29c3, for a sigrok hackathon. In addition to the usual "whatever we feel like hacking on", we also have several architectural decision to make, and doing this in person is a lot easier.

If you want to be part of the conversation and decision-making process, show up!

What's decided here is what goes.

Precision/accuracy analog format

We have a real problem with analog values at the moment. A new format is needed. Some options are listed on the High precision analog page.

Timestamps

Some devices, such as dataloggers, actually log the time at which a measurement was made. This is not the current time -- some of these cannot even stream live data -- so the driver needs to submit these measurements to the session bus with an attached timestamp.

Chained packets

It may be interesting to link several packets together, and submit them to the session bus at the same time. For example, a timestamp + temperature measurement + relative humidity measurement submitted together would denote that these two measurements were takes at that specific point in time.

Samplerate: meta or DI?

Samplerate is a part of the SR_DF_META_LOGIC packet. However there is also a SR_DI_CUR_SAMPLERATE info type. Do we really need two?