Author Topic: Probem with camera device from orbiters  (Read 960 times)

joerod

  • Guru
  • ****
  • Posts: 153
    • View Profile
Probem with camera device from orbiters
« on: February 11, 2011, 02:29:17 pm »
I don't know if I missed something, but I reinstalled the core using the latest snapshot this weekend and worked fairly well (I will update the wiki and check the tickets as Saturday night).  I'm having a small issue I didn't have before and thate security camera setup... 

Motion records perfectly and has all the folders setup correct (had to fix the permissions inside /home/cameras/) but it is saving the latest shots, recordings, timelapse, etc.  These are analog cameras using a bluecherry capture card. 

So, everythings cool; but when I click on the device using the padorbiter or any on-screen orbiter (including webadmin).  I don't get a picture.  according to syslog motion seems to start up fine; I can even see a picture if I access "http://dcerouter:<motion created port>"

Is this this a known issue with the lastest snapshot or am I missing something...

purps

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1396
  • If it ain't broke, tweak it
    • View Profile
Re: Probem with camera device from orbiters
« Reply #1 on: February 11, 2011, 03:30:01 pm »
Check the scenario in question (web admin -> wizard -> scenarios -> security scenarios) has the correct device # (device # for the camera).

Cheers,
Matt.
1004 RC :: looking good :: upgraded 01/04/2013
my setup :: http://wiki.linuxmce.org/index.php/User:Purps

joerod

  • Guru
  • ****
  • Posts: 153
    • View Profile
Re: Probem with camera device from orbiters
« Reply #2 on: February 12, 2011, 04:13:05 am »
well, I'm not exactly sure what its suppose to say in the scenario editor in webadmin but i have to select "Edit scenario using wizard:  Advanced Wizard" and that indicates PK_screen: 15 and PK_device: <correct camera device id>

so i guess its ok, and again in the web admin "securty - cameras" it lists the cameras but then just show a broken link (file) where the camera image should be...

but in /home/cameras/<deviceid>/2011/2/11/<recording, snapshots, etc>  i have the correct data...

is this a bug, known issue, or I misconfigured something?

joerod

  • Guru
  • ****
  • Posts: 153
    • View Profile
Re: Probem with camera device from orbiters
« Reply #3 on: February 20, 2011, 05:09:43 am »
I did some more investigating and found this in the motion log file:

========== NEW LOG SECTION ==========
1   02/20/11 00:03:27   57 (spawning-device)   Starting... 1
1   02/20/11 00:03:27   57 (spawning-device)   Found /usr/pluto/bin/Motion_Wrapper
05   02/20/11 0:03:28.864      Connect() failed, Error Code 111 (Connection refused)) <0xb70fa6c0>
05   02/20/11 0:03:29.864      Connect() failed, Error Code 111 (Connection refused)) <0xb70fa6c0>
05   02/20/11 0:03:30.864      Connect() failed, Error Code 111 (Connection refused)) <0xb70fa6c0>
05   02/20/11 0:03:31.864      Connect() failed, Error Code 111 (Connection refused)) <0xb70fa6c0>
05   02/20/11 0:03:32.864      Connect() failed, Error Code 111 (Connection refused)) <0xb70fa6c0>
05   02/20/11 0:03:42.044      Creating child 59 <0xb70fa6c0>
05   02/20/11 0:03:42.044      Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb70fa6c0>
05   02/20/11 0:03:42.044      Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb70fa6c0>
05   02/20/11 0:03:42.044      Creating child 60 <0xb70fa6c0>
05   02/20/11 0:03:42.044      Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb70fa6c0>
05   02/20/11 0:03:42.044      Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb70fa6c0>
05   02/20/11 0:03:42.044      Creating child 104 <0xb70fa6c0>
05   02/20/11 0:03:42.044      Note: Device manager has attached a device of type 66 that this has no custom event handler for.  It will not fire events. <0xb70fa6c0>
05   02/20/11 0:03:42.044      Note: Device manager has attached a device of type 66 that this has no custom handler for.  This is normal for IR. <0xb70fa6c0>
05   02/20/11 0:05:24.934      Could not take snapshot, fail sending SIGALRM signal... <0xb58f6b90>
05   02/20/11 0:05:25.176      Could not take snapshot, fail sending SIGALRM signal... <0xb58f6b90>



it would seem the three analog cameras don't have a "custom event handler" I'm not sure what that means.... but I did follow these directions very carefully: http://wiki.linuxmce.org/index.php/Monitor_surveillance_cameras

any suggestions?

joerod

  • Guru
  • ****
  • Posts: 153
    • View Profile
Re: Probem with camera device from orbiters
« Reply #4 on: March 05, 2011, 05:20:02 am »
DCErouter.log says this when I try to view a camera from orbiter or webadmin (motion is running and recording are being stored correctly and cameras a viewable thought the ports created by motion :8000-8002:

08      03/05/11 0:08:35.667            Received Message from 0 (unknown / ) to 60 (Generic Analog Camera / Backyard), type 1 id 84 Command:Get Video Frame, retry none, parameters: <0x38e90b90>
08      03/05/11 0:08:35.667              Parameter 19(Data): 0 <0x38e90b90>
08      03/05/11 0:08:35.667              Parameter 20(Format): jpg <0x38e90b90>
08      03/05/11 0:08:35.667              Parameter 23(Disable Aspect Lock): 0 <0x38e90b90>
08      03/05/11 0:08:35.667              Parameter 31(): 0 <0x38e90b90>
08      03/05/11 0:08:35.667              Parameter 60(Width): 100 <0x38e90b90>
08      03/05/11 0:08:35.667              Parameter 61(Height): 100 <0x38e90b90>
05      03/05/11 0:08:35.764            Socket::ReceiveData 0x8ac8f58 failed, bytes left 0 start: 512620000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 10 Incoming_Conn Socket 10 127.0.0.1 <0x38e90b90>
05      03/05/11 0:08:35.765            Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 10 127.0.0.1 <0x38e90b90>
05      03/05/11 0:08:35.765            TCPIP: Closing connection to -1003 (Router Dev #0) 0x8ac8f58 m_Socket: -1 <0x38e90b90>
05      03/05/11 0:08:35.765            Router::RemoveAndDeleteSocket 0x8ac8f58 -1003 <0x38e90b90>
07      03/05/11 0:08:36.121            Event #75 has no handlers <0xa388db90>