I have updated the template a bit, and added motion detection capabilities. The necessary code hasn't been released yet, but you can download the recent binary from the same url as before. You would have to update sqlCVS too, and only new devices will be set up with the new template data.

So: update sqlCVS, download new binary - place it in /usr/pluto/bin, create a new device with the template, reload. (and cross fingers )

br,
sambuca

Ok, I got what I need. I will do some tests for myself and post here when ready

br,
sambuca

Right, because of the & on the URL, it doesn't work. Try this:

Code:

wget "http://192.168.111.93/get_status.cgi?user=USER&pwd=PASSWORD"

It shouldn't be much more questions now, but thanks for the offer.

br,
sambuca

Ok, that is the result I was expecting. Now I wonder if the camera shuts down the connection immediately, or if it sends more data along as things change (D-Link camera does this). Don't know if this is easy to test with a browser, but you could use wget on the command line: wget <url> and see if it finishes, or just keeps going (stop with CTRL+C in that case).

It's quite easy to a motion detection to this template, but depending on how the camera uses the connection, I might have to make a small code change first.

br,
sambuca

There is no 100% sure method of finding mac ranges, but the consensus seem to be that the first 3 or 4 bytes is used as a range. So in you case it would be from 00:0d:c5:d0:00:00 to 00:0d:c5:d0:FF:FF. This can always be changed later on if needed.

To do a quick test, can you open your browser to this address on your camera. You probably need the same user/password format on the url as other commands:

Code:

http://x.x.x.x/get_status.cgi?user=USER&pwd=PASSWORD

and post the output from that.

I suppose it should be possible to do that with some timed event and such, if not too advanced. There is not built-in support for such a thing iirc.
And I don't know how well this will work with built-in motion detection. Ideally cameras should compensate for camera movement, but ymmv. That would be true when using a motion wrapper too, it does not know that the camera moves rather than there is motion in the frame.

Glad you liked my short guide I think there should already be wiki articles on this, but maybe they can be improved on.

br,
sambuca

Your template has been approved, thanks for your work.

Please update sqlCVS and check that the template still is OK. There was some inconsistency after approving it, but I took care of it. It was not anything you did wrong

You could also add a DHCP range for the cameras to make them plug-and-play.

It seems the camera is also capable of motion detection, and I think it is possible to add that to the template if your interested in helping a bit.

br,
sambuca

Yes, do
"apt-get update" followed by "apt-get upgrade"

br,
sambuca

Yes, you need to upload it to sqlCVS. You can do this anonymously, and I will approve it after checking that it looks ok.

Everything you need related to sqlCVS is found in the web-admin, under Advanced -> sqlCVS.
First you should do a sqlCVS update, check all under DCE, and click next. This will pop up a new window (watch out for popup blockers...) and will take a while to complete.
When this completes, open your IPCAM02 template and make sure everything is ok (no device data is missing or added by mistake by the update). I don't think it should, but better safe than sorry. Also note that your template might have gotten a new template number, you need this later.

Next, do a sqlCVS diff. Check all under DCE and click next.
This is where it gets interesting...  This will, after a short while, display all changes in your installation compared to the standard one.

You will probably have several changes that are unrelated to the device template, and selecting those will in the worst case break existing templates (like the changes you did to the original Advanced IP Camera template).
What you see is a list of items, with NEW/MOD/DEL in front of them. In your case you created a new template, so only NEW items should be selected, deselect all others.

Now, look more closely at the selected items... You should see a column with PK_ or FK_DeviceTemplate for each item. In this column there should be the same number as your device template. If you have any other numbers, it may be other device templates you created but did not upload. So deselect everything not containing the IPCAM02 device template ID.

Create a new ticket in trac, and use the ticket ID as a reference in the text input at the bottom of the web-admin screen, along with perhaps a short description. Click "Commit". This will also take a short while. When that is done, let me know and I will take it from there.

br,
sambuca

There should be some procedures in the wiki. Basically it goes like this:
Go to Advanced -> Configuration -> Device Templates, click Add device template. You need to specify your cameras manufacturer and device category first (category should be "IP Cameras < Surveillance cameras < Peripherals"). If you don't know the manufacturer, there is also a "Generic" manufacturer.

From there, you can follow the instructions on http://wiki.linuxmce.org/index.php/Advanced_IP_Camera to fill in the required information.

I will look at the segmentation fault, but I think it is happening when the program stops and shouldn't prevent the camera from working.

br,
sambuca

Glad you finally got it working 

It would be great if you create a new template for your camera so that it is plug and play.

Changing the Orbiter layout is definitely another topic yes..

br,
sambuca

Ok, I've made a new version that does not add extra slashes. You can download it from the same URL.

br,
sambuca

I've seen the triple /// too, but it has not been a problem before.

I see that the URL request gets a 404 error, which means that the requested resource does not exist.  Are you sure that the url is correct?

br,
sambuca

The log wont show much more than now before something starts happening..

But you should enable more logging like I described, it will help troubleshoot.

br,
sambuca

You should be able to set up the camera now.

What you can do is to edit the /etc/pluto.conf file and find the LogLevels line. Add ,10 to the end of it to get more logging:

Code:

LogLevels = 1,5,7,8,10

And do a quick reload - or if you like, for testing purposes, you can start the device on the command line (no reload required).

br,
sambuca

Not sure if I have fixed it, but can you download the binary again - I've created a new version, and try again. See if it still segfaults.

br,
sambuca