Motion - Support Question 2017x 03x 23x 131350

Motion and ComOnyx CO-L221 camera

Question

Hello ! I am trying to use a motion with a ComOnyx CO-L221 camera. On official site in support is written: The correct spelling of the request for JPEG frames to ComOnyX IP cameras of various series looks like this: (Http://[IP address]/[Request]) Where: [IP-address] - the IP-camera address in the local network, [Request] - a unique set of commands for each series of IP cameras.

For example:

The CO-Lxxx series (eg CO-L111, CO-L121, CO-L122, CO-L123 ....) Http://192.168.1.100/cgi-bin/snapshot?channel=0 - JPEG request for the first stream frame But when I write in motion config file url to my cam - picture don't appear P.S. In VLC-player this link works. And now question - what I doing wrong?

Thanks!
Some conf file:
###########################################################
# Capture device options
############################################################

v4l2_palette 2
input 8
norm 0
frequency 50
rotate 0
width 1280
height 1024
framerate 10
minimum_frame_time 0
netcam_url http://192.168.112.4/cgi-bin/snapshot?channel=0
; netcam_http 1.0
netcam_tolerant_check off
auto_brightness on
brightness 50
contrast 50
saturation 30
hue 0



Output to console when motion starts:
sudo motion -n
[0] Processing thread 0 - config file /home/vsuser/.motion/motion.conf
[0] Unknown config option "logfile"
[0] Unknown config option "log_level"
[0] Unknown config option "log_type"
[0] Processing config file /home/vsuser/.motion/thread116.conf
[0] Motion 3.2.12 Started
[0] ffmpeg LIBAVCODEC_BUILD 3547904 LIBAVFORMAT_BUILD 3544067
[0] Thread 1 is from /home/vsuser/.motion/thread116.conf
[1] Thread 1 started
[0] motion-httpd/3.2.12 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 8080
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Failed to read first camera header - giving up for now
[1] Could not fetch initial image from camera
[1] Motion continues using width and height from config file(s)
[1] Resizing pre_capture buffer to 1 items
[1] Started stream webcam server in port 8116
[1] Resizing pre_capture buffer to 3 items
[1] Retrying until successful connection with camera
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Failed to read first camera header - giving up for now
[1] Retrying until successful connection with camera
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Unrecognized content type
[1] Error reading first header - re-trying
[1] Failed to read first camera header - giving up for now

Environment

Motion version: 3.2.12
ffmpeg version: not installed
Libraries: mysql Ver 14.14 Distrib 5.5.49, for debian-linux-gnu (x86_64) using readline 6.3
Server OS: Linux 3.13.0-86-generic #130-Ubuntu SMP Mon Apr 18 18:27:15 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
-- RamilMukhtarov - 23 Mar 2017

Answer

Topic revision: r1 - 23 Mar 2017, RamilMukhtarov
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.