beside: for the controls, i had to switch UP and DOWN since my camera is upside down...

Next is to change the orbiter layout (buttons assigment) a bit. I don't have zoom, and i would like to replace this with preselections views (fe 10ups, 15 rights) But i think this another topic/template/..., no?

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.

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.

It seems the camera is also capable of motion detection....... if your interested in helping

I'm very intrested in this. I was thinking to add motion wrapper for this. But if there's another method, i'm open to that. I'm pro centralizing everything. I test the camera motion detection already as stand-alone. But hated it a bit that the mails/files were treated as something seperated. So if it could be integrated in LinuxMCE, great...

I'm also looking for a kind of 'fixed movement'. I've got 2 camera's that should cover 2 angles. So i'm thinking to create a small script that 'center' the camera, and then move the 10x up, 6x left (or something like that). I don't know if there's a part in linuxmce that i could/should use?

ps your help on 'creating and uploading templates' was easy to follow! Short and direct...Maybe a dedicated wiki for this? Could help everybody who wants to create/share templates?

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:

http://x.x.x.x/get_status.cgi?user=USER&pwd=PASSWORDand 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.