If we already had a driver for your camera, it would be very easy. In the installation wizard under Wizard/Devices/Cameras, you would just click 'add camera', choose the model, and then under Wizard/Scenarios/Security, just check the box for the camera. That's it.
But this is more difficult since theere is no driver (or device template). Creating a new driver will always require some work. However, it's not a major task like creating a driver in Windows since we have helper wizards that do most of the work for you.
So regarding your points 2 and 3, the easiest is just to delete the device you created (not the device template, which defines the device, just the device). And delete the scenario. Then use the wizard like I mentioned above to add the camera and the scenario. Once that's done, on the orbiter click the 'advanced' button (the pluto logo in the lower left corner), click 'regen this orbiter'. when the orbiter regens you will have a button to view your camera. And if you click that button, and in then watch the DCERouter's log in Pluto admin, you will see that the orbiter is sending a "Get Video Frame" request to the camera to pull the video.
Of course, at this point although the framework is done, there is no driver for the camera. So you'll see in DCERouter's log an error that the orbiter is trying to communicate with a device that hasn't registered.
So, before the camera will work, we will need to create a driver for it. In windows it probably came with a driver. So, we'll need a driver for Pluto--a DCE Device. This document explains how to do it: newbielink:http://plutohome.com/support/index.php?section=document&docID=51 [nonactive] There are 2 ways: C++ and Ruby. Ruby is quicker and easier. If this is not something you can do, what you can do is enable the 'remote assistance' option, and that will allow one of our programmers to login and work on the driver for you.
It sounds like you created your device template OK. For our purposes a camera isn't considered an audio/video device--by A/V we mean TV's, Stereos, etc. But that won't hurt anything.
As far as controlled via, rather than specifying 'controlled via device tempalte', delete those and choose controlled via device category, and choose the category "computer". What that means is that the driver will run on anything that is a computer.
What you chose for DeviceData entirely depends on the driver. When we write the driver we figure out what data parameters the driver needs, based on the device. At this point I don't know what (if any) data parameters it will need. There may be some settings like "color or black & white", or maybe "picture quality", or "motion detection", stuff like that. When we do the drivers we'll figureout what to put here.
The only commands that a camera needs to implement are "Camera Commands". That's the only box you need to check.
Take a look at the programmer's guide document and see how much makes sense and if you want to do the driver, or want our help. We're bringing in more programmers now to work on adding drivers, since it's such a common request, but they're still in training, so it will be a couple of weeks before we can have someone get to it.