Line 38: |
Line 38: |
| *1. Clone from github | | *1. Clone from github |
| | | |
− | <code>git clone <nowiki>https://github.com/veyeimaging/raspberrypi</nowiki></code> | + | <code>git clone https://github.com/veyeimaging/raspberrypi<nowiki/>.git</code> |
| | | |
| *2. Downloading from github ([https://github.com/veyeimaging/raspberrypi link here]), upload to RPI using samba or USB disk. | | *2. Downloading from github ([https://github.com/veyeimaging/raspberrypi link here]), upload to RPI using samba or USB disk. |
− |
| |
− | [[File:Veye 123.png|center|thumb|600x600px|Software Tookits]]
| |
| | | |
| ====Toolkits Overview==== | | ====Toolkits Overview==== |
| + | [[File:Rpi github overview.jpg|alt=|center|thumb|600x600px|Software Tookits on github]] |
| + | Software toolkits contains threeparts. ''veye_raspcam'' is raspcam alike Video Stream Toolkits, D_mipi_rpi is D-SDK Video Stream Toolkits, ''i2c_cmd'' is Video Control Toolkits. |
| | | |
− | *Software toolkits contains two parts. ''veye_raspcam'' is Video Stream Toolkits, ''i2c_cmd'' is Video Control Toolkits.
| |
| *Video Stream Tookkits provides real-time display, capture, video recording, etc. | | *Video Stream Tookkits provides real-time display, capture, video recording, etc. |
| *Video Control Toolkits is a shell script which provides ISP parameters configuration capbility. | | *Video Control Toolkits is a shell script which provides ISP parameters configuration capbility. |
Line 52: |
Line 51: |
| | | |
| ===Video Stream Toolkits Manual=== | | ===Video Stream Toolkits Manual=== |
| + | |
| + | ==== veye_raspcam: raspcam alike toolkits ==== |
| VS toolkits provides several ELF file. | | VS toolkits provides several ELF file. |
| | | |
Line 70: |
Line 71: |
| Implement H.264 format encoding and record for 5 seconds,Record the stream data to file ~/test.h264. | | Implement H.264 format encoding and record for 5 seconds,Record the stream data to file ~/test.h264. |
| | | |
− | *veye_raspivid (direct tcp stream with netcat,gstreamer etc..) | + | *veye_raspivid (direct tcp stream with '''netcat,gstreamer''' etc..) |
| | | |
− | '''RPI side''' | + | '''''RPI side''''' |
| | | |
| <code>./veye_raspivid -b 4000000 -t 0 -o - | nc -l -p 5000</code> | | <code>./veye_raspivid -b 4000000 -t 0 -o - | nc -l -p 5000</code> |
| | | |
− | H.264 encoding on bitrate4Mbps,forever,listen on TCP port 5000. | + | H.264 encoding on bitrate 4Mbps,forever,listen on TCP port 5000. |
| | | |
− | '''PC side,using gstreamer(Powershell recommended)''' | + | '''''PC side,using gstreamer(Powershell recommended)''''' |
| | | |
| <code>./gst-launch-1.0 -v tcpclientsrc host=x.x.x.x port=5000 ! decodebin ! autovideosink</code> | | <code>./gst-launch-1.0 -v tcpclientsrc host=x.x.x.x port=5000 ! decodebin ! autovideosink</code> |
Line 84: |
Line 85: |
| x.x.x.x is RPI IP address | | x.x.x.x is RPI IP address |
| | | |
− | gstreamer windows version [https://gstreamer.freedesktop.org/documentation/installing/on-windows.html?gi-language=c download]. | + | '''''gstreamer''''' windows version [https://gstreamer.freedesktop.org/documentation/installing/on-windows.html?gi-language=c download]. |
| | | |
− | '''PC side, using mplayer''' | + | '''''PC side, using mplayer''''' |
| | | |
| <code>./mplayer -x 1280 -y 720 -geometry 0:0 -fps 200 -demuxer h264es -noborder ffmpeg://tcp://x.x.x.x:5000</code> | | <code>./mplayer -x 1280 -y 720 -geometry 0:0 -fps 200 -demuxer h264es -noborder ffmpeg://tcp://x.x.x.x:5000</code> |
Line 125: |
Line 126: |
| | | |
| Capturing one image every 50 milliseconds and save to /dev/shm directory(which is in DDR).1920*1080 BMP format. | | Capturing one image every 50 milliseconds and save to /dev/shm directory(which is in DDR).1920*1080 BMP format. |
| + | |
| + | ==== D-SDK Toolkits Manual ==== |
| + | It contains three parts: C language SDK(libdmipicam.so),C language sample,Python language sample. |
| + | |
| + | =====Install support package===== |
| + | <code>sudo apt-get update && sudo apt-get install libopencv-dev</code> |
| + | |
| + | <code>sudo apt-get install python-opencv</code> |
| + | =====D-SDK===== |
| + | |
| + | *interface: |
| + | |
| + | opensource,D_mipicam.h |
| + | |
| + | *compile: |
| + | |
| + | <code>./build</code> |
| + | |
| + | *install: |
| + | |
| + | <code>sudo install -m 644 ./libdmipicam.so /usr/lib/</code> |
| + | =====C sample===== |
| + | |
| + | *preview |
| + | |
| + | Dispaly real-time video to HDMI output |
| + | |
| + | *preview-dualcam |
| + | |
| + | Dispaly real-time video to HDMI output for dual cameras(RPI CM) |
| + | |
| + | *video |
| + | |
| + | H.264 format encoding and record to file. |
| + | |
| + | *capture |
| + | |
| + | Capture one jpeg image. |
| + | |
| + | *video2stdout |
| + | |
| + | H.264 format encoding and send to stdout,which could be used by pipe. It's like <code>veye_raspivid -o -</code>. |
| + | |
| + | <code>./video2stdout | nc -l -p 5000</code> |
| + | |
| + | *capture_yuv |
| + | |
| + | Capture one yuv image. |
| + | |
| + | *capture-dualcam |
| + | |
| + | Capture jpeg images for dual cameras. |
| + | |
| + | *yuv_stream |
| + | |
| + | Shows how to get yuv stream. |
| + | |
| + | *capture2opencv |
| + | |
| + | Shows how to get yuv stream,transfer to opencv format and display it. |
| + | |
| + | *qrcode_detection |
| + | |
| + | Shows how to get yuv stream,transfer to opencv format and display it and detect QR code. |
| + | |
| + | =====Python sample===== |
| + | |
| + | *preview.py |
| + | |
| + | Dispaly real-time video to HDMI output |
| + | |
| + | *capture.py |
| + | |
| + | Capture one jpeg image. |
| + | |
| + | *capture_yuv.py |
| + | |
| + | capture_yuv |
| + | |
| + | *video.py |
| + | |
| + | H.264 format encoding and record to file. |
| + | |
| + | *capture2opencv.py |
| + | |
| + | Shows how to get yuv stream,transfer to opencv format and display it. |
| ===Video Control Toolkits Manual=== | | ===Video Control Toolkits Manual=== |
| On Raspberry Pi, I2C-0 is used by GPU. We use I2C-1 as control bus for VEYE Camera Module. We provide a Shell Script — camera_i2c_config— to config pin usage. | | On Raspberry Pi, I2C-0 is used by GPU. We use I2C-1 as control bus for VEYE Camera Module. We provide a Shell Script — camera_i2c_config— to config pin usage. |