On : Monday, January 26, 2015 10:03 AM , Uwe Hermann [mailto:u...@hermann-uwe.de] wrote: > > Right now, we have our own software stack, but would be interested in > > understanding how to work with you and the other sigrok developers, as I > > think > > we have mutual goals. (open source from hardware to firmware to GUI), end > > users learning more things about analog. > > That's great, we're always interested in supporting more hardware of course, > especially so if the device is interesting and the vendor is helpful as well > (which > both seems to be the case here :) > > Adding a new device usually means writing a "driver" for libsigrok (which is a > GPLv3+ licensed C library), the rest of the support is "automatically" there > as for > any other supported device (CLI and GUI frontends, Python/C++/Java bindings, > protocol decoders, input/output formats, etc. etc.) > > You can have a look at the current libsigrok API docs if you're interested in > the > details, or at the source code of other supported devices of course. > > http://sigrok.org/api/ > http://sigrok.org/gitweb/?p=libsigrok.git;a=tree;f=src/hardware
Thanks for the pointers -- we will have a look as soon as we can (although we are trying to get our own stuff stable enough to ship hardware first :) > > Although it's not described as such, the M1k is a dual channel source > > measure > > Unit (SMU), that does have some AC capabilities, so it really doesn't fit > > into the > > existing devices that are supported in sigrok now. Sourcing an arbitrary > > voltage|current on a pin, while measuring the resulting synchronized/actual > > voltage/current is sort of a weird combination of function generator/scope > > on a > > single pin. > > > > We do have our own open source software, a library - libsmu, and own gui - > > pixelpulse2. > > > > https://github.com/signalspec/pixelpulse2 > > https://github.com/signalspec/libsmu > > > > https://www.youtube.com/watch?v=3rBX0yXIXY8 (gui in action). > > Looks good. The libsmu is BSD(-like) licensed which means we could potentially > reuse some of that lowlevel code in sigrok if needed (might be easier to > write a > libsigrok driver from scratch based on the protocol info gathered from your > documentation and/or code though, haven't looked at the details there yet). Right now - software documentation is pretty thin (which means almost non-existant). We are working on it, but need to ship first. :) > > As soon as a few more units get off the manufacturing line, I can send some > > over to anyone interested -- Any thoughts on how to add a SMU (in a generic > > sense, and the M1k specifically) to sigrok? > > Sounds great, I'd be happy to have a shot at writing a basic driver for the > device > if hardware is available (might apply to other developers as well), please > contact > us off-list for details. No problem -- also feel free to reach out to me as well - I don't know who "us" is :) > As for how to specifically implement SMU support that'll probably need some > thoughts indeed. Let me know if we can help in any way in figuring this out. -Robin ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
