Download this binary http://hob.dyndns.org/lmce/Advanced_IP_Camera and run it on the command line (no need to replace the one in /usr/pluto/bin), and try again.

br,
sambuca

I will provide a binary with symbols later today (if no one else beats me to it...)

I don't know what the consensus about debug symbols in the default packages is? I know I haven't changed the build of the Advanced IP Camera in any way related to that.

br,
sambuca

Yes, you forgot to add the dump file parameter to the command line. It should be something like this
sudo gdb /usr/pluto/bin/Advanced_IP_Camera /home/coredump/1/core_Advanced_IP_Camera_123412341234

br,
sambuca

Ok, then you need to help me debug it. Look in /home/coredump/1 for the last file with Advanced_IP_Camera in its name, this is the dump file.

Code:

cd /usr/pluto/bin
sudo gdb Advanced_IP_Camera <path and filename to dump file>

Once gdb has started, type bt and press enter
This will give you the stack trace and will help pinpoint the error. Please copy this and post it here.

Type quit to exit gdb.

br,
sambuca

Do this:

Code:

apt-get install lmce-advanced-ip-camera

will install any newer version if available.

br,sambuca

No, the segmentation fault does not look good..

First, please make sure you have the newest version of the lmce-advanced-ip-camera package. If there is a newer one, install that and do a quick reload and try starting the Advanced IP Camera again.

br,
sambuca

You need to specify the device ID on the command line to start it like that, use -d <dev.id>

br,
sambuca

Do you have the /usr/pluto/bin/Advanced_IP_Camera binary on the core?

Once the device is created with the template, and the router has been reloaded, it should start. The correct package should be installed automatically. If the binary is not present, there must be something wrong with the install or that the system hasn't triggered the install yet. A reboot should always trigger a install of missing packages.

br,
sambuca

There is no way to copy a template at the moment.. so you have to create a new one from scratch.

It is possible to use the Advanced IP Camera template for testing, and later create a template using that data.

If the device is started properly, you should see a log file with the device id in /var/pluto/log on the core. This could also give more information about what is wrong..

Another strange thing is the use of user and password in the URL itself. Is this all that is required to authenticate with the camera? If so, you can probably clear the AuthPass and AuthUser fields. If those fields are filled in, it will try to use basic http authentication for all requests. Maybe that messes up the communication with the camera?

br,
sambuca

I am the developer of the Advanced IP Camera.

From the URLs you posted you should be able to create a template using the Advanced IP Camera in 5-10 minutes. The wiki article describes this process (well, I hope). The Pan and Zoom function was created just a few days ago, so I'm not sure if the update has been built yet.

The Motion Camera template #1916 does not use the same parameters as the Advanced IP Camera, so that is why you cannot control the camera from any orbiter.

Just ask if you have any questions.

br,
sambuca

Q 1 and 2 really depend on the ip camera itself and not lmce.

As posde said, there is development on using more advanced features of ip cameras like built in motion detection. If you use analog cameras you will need the motion wrapper to detect motion. This is a program that runs on the core and checks for motion in the video stream, assuming you dont have a video card with motion detection.

Br,
Sambuca

Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415
Expression 'snd_pcm_hw_params_set_buffer_size_near( pcm, hwParams, &lowLatency )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 415

I see this every time I start squeezeslave, so I wouldn't worry about that...

Just a basic thought that occured to me; have you checked the volume of the sound card using alsamixer?

br,
sambuca

Do you mean like the 0810-Alpha and -Beta wiki pages? No, there is no such thing for 1004 (yet). The idea is that there are too many changes to list them all for the time being. Maybe when we enter beta, we will start making such a list again.

I do agree that a changelog would be useful, and perhaps we could list the main new stuff that has been worked on lately. Anyway, you can see what has been done in the trac timeline, although it might be a bit technical for some.

br,
sambuca

One more thing that occurred to me. It seems that there are a slight difference between when you suspend a MD and when you shut it down. When shutting it down, it needs to set NETDOWN=no in /etc/default/halt to keep the network alive. Afaict, this is not required when doing suspend.

br,
sambuca

Cameras using SMTP/Mail or FTP upload on motion detection are not the ideal to interface with, but that said, I might try to add support for that too. My concern is whether the camera actually sends an email/ftp when the motion has stopped. If not, LMCE would consider the detector to be in the tripped state even though motion has stopped...

The template supports motion detection for D-Link cameras at the moment. I use a DCS-2121 to do testing, but I suspect that all D-Link cameras are built on the same firmware.

br,
sambuca