Plugin starting point?

[atomicjello]

Very impressive stuff!

I'm looking to start on a smaller scale and use servo motor controllers to drive LEDs and possibly a servo or two. I have a table-top holiday scene just begging to be geekified. :)

I have several existing servo controllers (Pontech's sv203 and scc32) that I want to make plugins for...

So does anyone have a pointer to a thread, theory of operations guide, source code, etc. that can help fill in the gaps?

The servo controllers are controlled via a simple serial protocol. I noticed the beta for v2 has a driver for Parallax's PSC -- this is the type of thing I need.

Thanks,
atomicjello

[A Marchini]

I am trying to put something down for you but I haven't had a chance to put it together.
It should be an amalgam of how to setup a new project and things like that.

I need to ask if anyone is worried about source existing on this site (perhaps a sticky topic could be created to hold the thread, unless we get a source repository on this site).

It wouldn't be too difficult for someone to send you one of the simple serial drivers in existance right now, so you could just cut in your version of control with it.

Tony M.

[P. Short]

The wiki is also a good place to use as a repository.

--

Phil

[atomicjello]

I am trying to put something down for you but I haven't had a chance to put it together.
It should be an amalgam of how to setup a new project and things like that.
... snip ...
It wouldn't be too difficult for someone to send you one of the simple serial drivers in existance right now, so you could just cut in your version of control with it.
Tony M.

Excellent.
Also, I'd love to help out as needed. Maybe a tutorial or walk through on the wiki once I'm up to speed. Whatever is needed to compliment what you are planning.

[A Marchini]

The wiki is also a good place to use as a repository.

--

Phil

It will have to do I suppose. I just figured sticky links at begining of threads would be immediately visible, but I suppose not the best place.

Tony M.

[P. Short]

I'm playing around trying to write a simple plugin using the command line tools, is there any sample code available for anything on Version 2.0? Has the plugin interface changed between the two versions of vixen, or not?

What I'd really like to know is how to determine the interfaces to vixen for myself. There was a post on this some time back, but my chances of finding it are pretty slim.

--

Phil

[teberle]

I can document those for you. It may take a day or two.

[A Marchini]

I can document those for you. It may take a day or two.
I was working on a howto myself, only using Visual Studio 2005

Phil, what command line tools are you using?

Tony

[P. Short]

Just csc (and ildasm, now that I've downloaded the .net SDK). And emacs for the editor.

--

Phil

[teberle]

Phil and Tony,

Check you pm's.

Tony

[A Marchini]

Just csc (and ildasm, now that I've downloaded the .net SDK). And emacs for the editor.

--

Phil

Visual Studio Express should be able to help manage the projects for you. It is free. The ability to drop assemblies from the object viewer and C# code syntax highlighting might help you some.
I am not 100% familiar with its capabilities, but it does make navigation quite a bit easier.

Tony M.

[P. Short]

Thanks, Tony (Eberle), all of my questions are answered for now, and I can now modify the existing code to create the plugins that I need.

--

Phil

[stempile]

Thanks, Tony (Eberle), all of my questions are answered for now, and I can now modify the existing code to create the plugins that I need.

--

Phil

By existing code do you mean the .dll files for the plug-ins? I thought that was compile and not accessible. I haven't look at anything from vixen yet in Visual Studio Express.

ms

[P. Short]

Yes.

--

Phil

[teberle]

By existing code do you mean the .dll files for the plug-ins? I thought that was compile and not accessible. I haven't look at anything from vixen yet in Visual Studio Express.

ms

The code is compiled, but is accessible via .net tools. You can use the ildasm to look at the precompiled code.

Tony