Author Topic: md usb webcam setup?  (Read 2072 times)

heinola

  • Veteran
  • ***
  • Posts: 50
    • View Profile
md usb webcam setup?
« on: August 08, 2009, 08:06:16 pm »
Setup:

AMD x2  32bit hybreed  (masterbedroom)
AMD 64bit md (livingroom)

I have a current wifi ip camera  Panasonic BB-HCM371A

auto detected and set up  pan/tilt function ok  but no zoom  ( working on this )
also have it on motion wrapper via CORE

I have a Logitech webcam that worked on the CORE using motion wrapper.

I moved it to the livingroom md

I got no prompt for new device when I did this...

My question is what is the next step as far as trouble shooting this issue  -or- someone has doc on this kind of setup/issue

ty

ivanp

  • Veteran
  • ***
  • Posts: 94
    • View Profile
Re: md usb webcam setup?
« Reply #1 on: August 09, 2009, 12:29:50 am »
I set up my USB webcam on MD following these steps:
1. Added Motion wrapper as interface
2. Added Generic motion camera as child device of Motion wrapper under Device tree
3. Reloaded the ruter

After that the green LED activated on my USB webcam and i had video feed. I found it poor, around 5 fps, but i think you can set it up higher if You google around for motion wrapper. HTH

heinola

  • Veteran
  • ***
  • Posts: 50
    • View Profile
Re: md usb webcam setup?
« Reply #2 on: August 09, 2009, 06:00:57 pm »

Both my webcams that know worked on core..

Both of them have status lights on allthe time from MD bootup..  even before i set up motion

bugui

  • Veteran
  • ***
  • Posts: 69
    • View Profile
Re: md usb webcam setup?
« Reply #3 on: July 15, 2010, 05:17:56 am »
Hi,
I get problems to setup a webcam on a diskless MediaDirector using motion wrapper.
The webcam is working ok (it saves the snapshots into the correct folder) but MotionWrapper can't write a /home/cameras/XXX/lastsnap.jpg (it should be a link) to the new snapshot.
When I try to use the camera selecting it (any method from UI or Web-UI) the MotionWrapper logs displays this:

 Missing snapshot file: /home/cameras/106/lastsnap.jpg.

That's is because the file is missing.

It's not a camera issue, the webcam was working at the core (hybrid) but is not working on the MD.
When I setting up this I followed the instructions of the wiki.
I add a template into MD tree using create a child device (for motionwrapper) and inside it I create a new generic web cam.Webcam is working but I can't visualize the video, because MD can't write a link /home/cameras/106/lastsnap.jpg.

Is this a know issue ?

Is there a way to use a webcam as security cam but connect it to an MD?? ?

Thanks in advance
Hernan











heinola

  • Veteran
  • ***
  • Posts: 50
    • View Profile
Re: md usb webcam setup?
« Reply #4 on: July 27, 2010, 05:05:19 am »
same here   have usb camera recording ect on md 


but...

no lastsnap.jpg ?

any fixes?

rperre

  • Guru
  • ****
  • Posts: 264
    • View Profile
Re: md usb webcam setup?
« Reply #5 on: July 28, 2010, 04:08:09 am »
Last time i heard anything about this was on irc and i was told it would get fixed and to just wait...........

I'm waiting..... has something todo with wrong permissions imho, but not sure ofcourse.

Richard

rperre

  • Guru
  • ****
  • Posts: 264
    • View Profile
Re: md usb webcam setup?
« Reply #6 on: August 02, 2010, 09:30:23 pm »
uhum........

 ;)

pw44

  • Addicted
  • *
  • Posts: 653
    • View Profile
Re: md usb webcam setup?
« Reply #7 on: August 03, 2010, 01:20:37 am »
webcam_server and webcam. take a look on both packages (installable by synaptic).
maybe you can install one or both on your md and have the core treating it as another ip camera.....

rperre

  • Guru
  • ****
  • Posts: 264
    • View Profile
Re: md usb webcam setup?
« Reply #8 on: August 03, 2010, 02:51:04 am »
that is a possible hack, but it would be nicer if i could figure out why lastsnap.jpg is not created, because the rest of the images are...

Richard

Beeker

  • Guru
  • ****
  • Posts: 267
    • View Profile
Re: md usb webcam setup?
« Reply #9 on: August 08, 2010, 02:35:31 am »
Hi All,
Looking for some help with a generic USB webcam that I have plugged into the core. I have followed the instructions in the wiki and I now have a USB Camera button on my web orbiter and when I click on it it has all the functions zoom, pan and tilt etc and the little penguin indicates that it is refreshing every 5 secs but no image appears. When I go to admin on the core and go to security  - view cameras and select the USB Camera I get a small window with the msg saying loading and it stays like that. Below are the logs from the motion wrapper and if anybody could help that would be really appreciated.

Kind regards
Bruce

Quote
== ATTEMPT FRESH START ==
1   08/08/10 09:16:11   /usr/pluto/bin/Spawn_Device.sh 212 (spawning-device)   14630 Dev: 212; Already Running list: 15,16,18,19,33,34,164,166,21,
== FRESH START ==
1   08/08/10 09:16:11   /usr/pluto/bin/Spawn_Device.sh 212 (spawning-device)   device: 212 ip: localhost cmd_line: Motion_Wrapper
0   08/08/10 09:16:11   212 (spawning-device)   Entering 212
========== NEW LOG SECTION ==========
1   08/08/10 09:16:11   212 (spawning-device)   Starting... 1
1   08/08/10 09:16:11   212 (spawning-device)   Found /usr/pluto/bin/Motion_Wrapper
05   08/08/10 9:16:11.788      Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 212 last error 2 <0xb789c6c0>
05   08/08/10 9:16:11.788      The router must be reloaded before this device is fully functional <0xb789c6c0>
05   08/08/10 9:16:11.790      void ClientSocket::Disconnect() on this socket: 0x8ad4b80 (m_Socket: 5) <0xb789c6c0>
05   08/08/10 9:16:11.796      Connection for client socket reported NEED RELOAD IP=127.0.0.1, device 212 last error 2 <0xb789c6c0>
== ATTEMPT FRESH START ==
1   08/08/10 09:24:21   /usr/pluto/bin/Spawn_Device.sh 212 (spawning-device)   22119 Dev: 212; Already Running list: 15,16,18,19,33,34,
== FRESH START ==
1   08/08/10 09:24:21   /usr/pluto/bin/Spawn_Device.sh 212 (spawning-device)   device: 212 ip: localhost cmd_line: Motion_Wrapper
0   08/08/10 09:24:21   212 (spawning-device)   Entering 212
========== NEW LOG SECTION ==========
1   08/08/10 09:24:21   212 (spawning-device)   Starting... 1
1   08/08/10 09:24:21   212 (spawning-device)   Found /usr/pluto/bin/Motion_Wrapper
05   08/08/10 9:24:21.497      Creating child 213 <0xb7a086c0>
05   08/08/10 9:24:21.497      Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb7a086c0>
05   08/08/10 9:24:21.497      Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb7a086c0>
05   08/08/10 9:25:20.971      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:25:26.108      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:25:31.225      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:25:36.341      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:25:41.451      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:25:46.579      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:25:51.685      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:25:56.795      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:26:01.916      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:26:03.592      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:26:08.706      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:26:10.360      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:26:15.487      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:26:20.591      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:27:55.855      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:00.967      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:06.092      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:11.202      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:16.395      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:21.504      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:26.607      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:31.548      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:31.728      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:36.549      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:36.849      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
01   08/08/10 9:28:39.506      Unknown command 685 received. <0xb7206b90>
05   08/08/10 9:28:41.550      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:41.952      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
01   08/08/10 9:28:42.654      Unknown command 684 received. <0xb7206b90>
05   08/08/10 9:28:47.100      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:52.205      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:28:57.311      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:02.421      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:07.539      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:12.668      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:17.847      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:22.970      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:28.079      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:33.188      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:38.308      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:43.423      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:48.534      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:53.652      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:29:58.768      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:30:03.878      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:30:09.012      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:30:14.120      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:30:19.260      Could not take snapshot, fail sending SIGALRM signal... <0xb7206b90>
05   08/08/10 9:31:39.752      Got a reload command from 0  <0xb7206b90>
05   08/08/10 9:31:40.005      void ClientSocket::Disconnect() on this socket: 0x991e3a8 (m_Socket: 7) <0xb7a086c0>
Return code: 2
2   08/08/10 09:31:40   212 (spawning-device)   Device requests restart... count=1/50 dev=212
Sun Aug  8 09:31:40 EST 2010 Restart
========== NEW LOG SECTION ==========
1   08/08/10 09:31:48   212 (spawning-device)   Starting... 1
1   08/08/10 09:31:48   212 (spawning-device)   Found /usr/pluto/bin/Motion_Wrapper
05   08/08/10 9:31:48.184      Creating child 213 <0xb79046c0>
05   08/08/10 9:31:48.184      Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb79046c0>
05   08/08/10 9:31:48.184      Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb79046c0>
05   08/08/10 9:33:10.015      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 9:33:15.132      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:00:37.027      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:00:42.028      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:00:47.029      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:08.779      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:13.899      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:19.028      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:24.146      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:29.504      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:34.626      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:39.955      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:45.246      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:50.721      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:01:55.983      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:02:01.100      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:02:06.236      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:02:11.558      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:02:16.710      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:02:21.832      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:02:26.960      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:02:32.170      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:06:57.250      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:07:02.460      Could not take snapshot, fail sending SIGALRM signal... <0xb7102b90>
05   08/08/10 10:07:08.833      Got a reload command from 0  <0xb7102b90>
05   08/08/10 10:07:09.101      void ClientSocket::Disconnect() on this socket: 0x9b413a8 (m_Socket: 7) <0xb79046c0>
Return code: 2
2   08/08/10 10:07:09   212 (spawning-device)   Device requests restart... count=1/50 dev=212
Sun Aug  8 10:07:09 EST 2010 Restart
========== NEW LOG SECTION ==========
1   08/08/10 10:07:17   212 (spawning-device)   Starting... 1
1   08/08/10 10:07:17   212 (spawning-device)   Found /usr/pluto/bin/Motion_Wrapper
05   08/08/10 10:07:18.208      Connect() failed, Error Code 111 (Connection refused)) <0xb79866c0>
05   08/08/10 10:07:19.208      Connect() failed, Error Code 111 (Connection refused)) <0xb79866c0>
05   08/08/10 10:07:20.208      Connect() failed, Error Code 111 (Connection refused)) <0xb79866c0>
05   08/08/10 10:07:22.310      Creating child 213 <0xb79866c0>
05   08/08/10 10:07:22.310      Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb79866c0>
05   08/08/10 10:07:22.310      Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb79866c0>
05   08/08/10 10:08:42.553      Could not take snapshot, fail sending SIGALRM signal... <0xb7184b90>
05   08/08/10 10:08:47.554      Could not take snapshot, fail sending SIGALRM signal... <0xb7184b90>
05   08/08/10 10:11:38.663      Could not take snapshot, fail sending SIGALRM signal... <0xb7184b90>
01   08/08/10 10:11:42.522      Unknown command 685 received. <0xb7184b90>
05   08/08/10 10:11:43.664      Could not take snapshot, fail sending SIGALRM signal... <0xb7184b90>
01   08/08/10 10:11:44.055      Unknown command 685 received. <0xb7184b90>



Beeker

  • Guru
  • ****
  • Posts: 267
    • View Profile
Re: md usb webcam setup?
« Reply #10 on: August 08, 2010, 03:54:06 am »
Just a update
I changed the device number and now when I go to admin on the core and go to security  - view cameras and select the USB Camera I get a image that refreshes every 5 sec.

Though if I use the weborbiter and select the USB Camera in security security section I get a window with all the icons like zoom in and out etc but no image, if I use the onscreen orbiter from the core and select the camera it also works so it's just the web orbiter where I don't get an image...........can anybody please help

Thanks
Bruce

Beeker

  • Guru
  • ****
  • Posts: 267
    • View Profile
Re: md usb webcam setup?
« Reply #11 on: August 08, 2010, 03:59:37 am »
Further update that when I use a weborbiter I now do get a picture if I select any of the icons like zoom in or one of the arrows. Sorry for the confusion still recovering from my illness, I seem to remeber from other posts that this is how it works would someone please set me straight on how it is meant to work.....................again sorry for wasting peoples time if this is how it is meant to work.

Kind regards
Bruce

rperre

  • Guru
  • ****
  • Posts: 264
    • View Profile
Re: md usb webcam setup?
« Reply #12 on: August 08, 2010, 05:17:07 pm »
http://forum.linuxmce.org/index.php?topic=10325.0

3rd post in this thread seemed to help me. you have to restart the core after you have done this.

Let us know if it worked.

Richard

Beeker

  • Guru
  • ****
  • Posts: 267
    • View Profile
Re: md usb webcam setup?
« Reply #13 on: August 09, 2010, 04:04:16 am »
Hi Richard,
Thanks............I ended up rebooting the core & the md and ever since then the USB camera all worked fine which is great

Cheers
Bruce