구차니의 잡동사니 모음

Automatic Plate Number Recognition

그냥.. 자동화된 차번호 인식...

아직까지는 찾지를 못함..

직접 구현해야 하려나?

mjpeg 카메라 영상인데...

[링크 : http://141.89.114.98/demo/edu640x480v.html] mjpeg 예제

안드로이드(갤S2 LTE HD)는 그냥 다운로드..(재생불가)

IE 11 (edge)재생불가

IE 10 이하 재생불가

아이패드는 재생

크롬 재생

VLC 재생

It is natively supported by the QuickTime Player, the PlayStation console, and web browsers such as Safari, Google Chrome, and Mozilla Firefox.

[링크 : https://en.wikipedia.org/wiki/Motion_JPEG]

M-JPEG over HTTP

HTTP streaming separates each image into individual HTTP replies on a specified marker. RTP streaming creates packets of a sequence of JPEG images that can be received by clients such as QuickTime or VLC.

In response to a GET request for a MJPEG file or stream, the server streams the sequence of JPEG frames over HTTP. A special mime-type content type multipart/x-mixed-replace;boundary=<boundary-name> informs the client to expect several parts (frames) as an answer delimited by <boundary-name>. This boundary name is expressly disclosed within the MIME-type declaration itself. The TCP connection is not closed as long as the client wants to receive new frames and the server wants to provide new frames. Two basic implementations of a M-JPEG streaming server are cambozola and MJPG-Streamer. The more robust ffmpeg-server also provides M-JPEG streaming support.

[링크 : https://en.wikipedia.org/wiki/Motion_JPEG#M-JPEG_over_HTTP]

VLC로 raw 덤프해서 보니...

--myboundary

Content-type: image/jpeg

이렇게 시작하고 그 아래로는 깨지는걸 봐서는 그냥 jpeg 프레임인듯..

심심..(?)해서 저기 MIME 관련 헤더들 삭제하고 jpeg으로 저장하니

아래와 같이 똮!

저장을 좀 오래 하니

--myboundary

Content-type: image/jpeg

[링크 : http://gstreamer.freedesktop.org/.../section-types-definitions.html#table-video-types]

    [링크 : http://stackoverflow.com/.../correct-mime-type-for-multipart-mjpeg-stream-over-http]

[링크 : http://en.code-bude.net/tag/how-does-mjpeg-work/]

mjpeg streamer

[링크 : http://www.acmesystems.it/video_streaming]

두개에 대한 벤치마크는 안보이지만...

어느걸 택하던 상관없다 일려나?(좋은 의미던 나쁜 의미던..)

lwIP

lwIP is also a good stack when used in its intended, memory constrained, environment. It has a higher throughput than uIP, but also has a larger ROM and RAM footprint. Although the footprint is larger than uIP it is still smaller than most commercial TCP/IP offerings. In particular, lwIP saves RAM by making large data buffers by chaining smaller buffers together.

Most (if not all) the FreeRTOS demos listed here make use of quite an old lwIP version. There are however contributed demos available in the FreeRTOS Interactive forums that use a more up to date lwIP code base. Further lwIP related uploads would be gratefully received.

On the negative side, lwIP is undeniably quite complex to use at first, but time invested in its use will pay dividends in future projects. lwIP is also a moving target because it is constantly being developed and updated (which is not necessarily a negative thing).

[링크 : http://www.freertos.org/embeddedtcp.html]

[링크 : http://lwip.wikia.com/wiki/LwIP_Application_Developers_Manual]

[링크 : http://lwip.wikia.com/wiki/LwIP_Wiki]

freeRTOS+TCP 패키지

[링크 : http://www.freertos.org/FreeRTOS-Plus/FreeRTOS_Plus_TCP/index.html]

Network Video Client (NVC)

Network Video Transmitters (NVT)

Network Video Storage (NVS)

Network Video Analytics (NVA)

storage에 빼앗긴 S 때문에..

Streamer나 Server 등을 쓸 수 없어 Transmitter가 된 것 같은 기분?

ONVIF Device Manager is a Network Video Client (NVC) to manage Network Video Transmitters (NVT), Network Video Storage (NVS) and Network Video Analytics (NVA) devices. Implements Discovery, Device, Media, Imaging, Analytics, Events and PTZ services. Written in C# and uses ffmpeg for media decoding.

[링크 : http://sourceforge.net/projects/onvifdm/]

+

[링크 : http://blog.naver.com/msnayana/80155230549]

+

[링크 : http://www.onvif.org/Documents/Specifications.aspx]

    [링크 : http://www.onvif.org/specs/DocMap-2.6.1.html]

Implementation of ONVIF Core Specification v1.02 or later is required for conformance to Profile S.

Implementation of ONVIF Core Specification v2.3 or later is required for conformance to Profile C.

Implementation of ONVIF Network Interface Specification Set v2.4 or later is required for conformance to Profile G.

Implementation of ONVIF Network Interface Specification Set, version 2.5 or later is required for conformance to Profile Q. 

[링크 : http://www.onvif.org/Portals/0/documents/op/...ONVIF_Members-Profile_S_Specification.pdf]

[링크 : http://www.onvif.org/Portals/0/documents/specs/2013_12_ONVIF_Profile_C_Specification_v1-0.pdf]

[링크 : http://www.onvif.org/Portals/0/documents/specs/ONVIF_Profile_G_Specification_v1-0.pdf]

[링크 : http://www.onvif.org/portals/0/documents/specs/ONVIF_Profile_A_RC-Spec_v1-0.pdf]

[링크 : http://www.onvif.org/Portals/0/documents/specs/ONVIF_Profile_Q_Spec_RC_v1-2.pdf]

gSOAP은 단순(?)하게 C/C++에서 XML 을 편하게 연결해서 SOAP 서비스를 제공하도록 해주는

프레임 워크? 라고 해야하려나?

단지 이걸 onvif에서 사용하는 것일뿐

gSOAP이 onvif는 아니다.

[링크 : https://en.wikipedia.org/wiki/GSOAP] generic XML and SOAP

[링크 : https://en.wikipedia.org/wiki/SOAP] Simple Object Access Protocol

[링크 : http://www.w3schools.com/xml/xml_wsdl.asp] Web Services Description Language

[링크 : https://en.wikipedia.org/wiki/Web_Services_Description_Language]

[링크 : http://j2enty.tistory.com/category/Dev%20Tech./SOAP]

[링크 : http://sourceforge.net/projects/gsoap2/]

두개가 태생이 같은건 아닐텐데..은근 붙어서 검색이 되네..

일단 가장 중요(?)한 것은.. bsd license

Developing applications on STM32Cube with LwIP TCP/IP stack

[링크 : http://www.st.com/st-web-ui/static/active/jp/resource/technical/document/user_manual/DM00103685.pdf] 

Using the lwIP Network Stack

Atmel SAM4E

[링크 : http://www.atmel.com/Images/Atmel-42233-Using-the-lwIP-Network-Stack_AP-Note_AT04055.pdf]

[링크 : http://lwip.wikia.com/wiki/LwIP_Wiki]

[링크 : http://savannah.nongnu.org/projects/lwip/]

Some demos use uIP and some lwIP as the underlying embedded TCP/IP stack - and pre-date the introduction of FreeRTOS+TCP (FreeRTOS's own scalable TCP/IP stack).

[링크 : http://www.freertos.org/embeddedtcp.html]

light weight ip

micro ip

[링크 : http://savannah.nongnu.org/projects/lwip/]

[링크 : https://en.wikipedia.org/wiki/LwIP]

[링크 : https://en.wikipedia.org/wiki/UIP_(micro_IP)]

[링크 : https://github.com/adamdunkels/uip]

원본을 찾기 힘드네...

그런데 비선점도 rtos가 될 수 있는건가?

[링크 : http://www.mtcnet.net/~henryvm/4AvrOS/]

    [링크 : http://roboticslab.tistory.com/6]

ppt 에 추가된 내용으로

부팅 시간이

linux 2.6.7 - 437.11

uclinux 2.6.7 - 415.16

으로 22초 정도 단축된다.

context switching 에 소요되는 시간인

linux - avg 110us

uclinux - avg 20us

에 비하면... 의외로 미미한 수준?

MMU 지원을 받지 못해 소스를 수정해야 하는 오버헤드를 생각하면

그리 큰 성능향상이라고 하긴 그럴 듯..

[링크 : http://bit.sparcs.org/~gangster/publication/uc_linux_fall.ppt]

[링크 : http://opensrc.sec.samsung.com/document/uc-linux-04_sait.pdf]

[링크 : http://micrium.com/rtos/ucosii/overview/]

[링크 : https://www.csie.ntu.edu.tw/~d6526009/ucOS2/Chapter-1.pdf]

+

[링크 : http://repilria.tistory.com/382]