On 06/15/2013 12:33 AM, Rob van Geloven wrote:
> Hi there,
>
> I was wondering if I could contribute to your project by implementing the
> DDS 3x25 functionality (I'm planning on buying one). What would be needed
> for that and what would be the best place for me to start?
(cc'ing sigrok-devel, please subscribe to the mailing list)
As you no doubt saw on the wiki, we do have part of the protocol. There's
enough there to get started, the rest won't be hard.
We don't yet have any drivers for hardware where output is the main function
of the device, i.e. where there might be some feedback but no "acquisition"
as such. That being said, it's not that big a deal: we do have support for
setting options of various kinds with a rich type system for the values.
We also don't really have function generator support as such, but that also
is not a big deal: it's just a matter of adding SR_CONF keys for the
functionality you need. Check libsigrok.h for a list of those.
So it's slightly uncharted territory, but there are no dragons there.
So set up a git branch and get yourself a basic driver skeleton: see
http://www.sigrok.org/blog/matter-parsing
Take some time to understand the driver model, check some other drivers to
see how they do things, and get basic communication working for your
hardware. The lascar-el-usb driver has an option (SR_CONF_DATALOG) which is
used to turn on/off autonomous logging of captured measurements. That's sort
of similar to how you'll set your options and turn on/off output for your FG.
Join #sigrok on irc.freenode.net if you need help.
--
Bert Vermeulen [email protected] email/xmpp
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
