Imaging solutions with Free Software & Open Hardware

Who's online

There are currently 0 users online.

Subscribe to Wiki Recent Changes feed
Track the most recent changes to the wiki in this feed. MediaWiki 1.28.0
Updated: 59 min 21 sec ago

10393 manual

Mon, 11/05/2018 - 13:03

‎Controlling multiple cameras from single GUI

← Older revision Revision as of 20:03, 5 November 2018 Line 468: Line 468:  ===Controlling multiple cameras from single GUI=== ===Controlling multiple cameras from single GUI===  * [[Multi_camera_system_operation|Recording]] * [[Multi_camera_system_operation|Recording]]  +  +===Developers version's half enclosure===  +{|  +|valign='top'|[[File:10393 half enclosure 1.jpeg|thumb|200px]]  +|valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]]  +|}     ==<font color="blue">Known problems</font>== ==<font color="blue">Known problems</font>== Oleg

File:10393 half enclosure 2.jpeg

Mon, 11/05/2018 - 12:58

Oleg uploaded File:10393 half enclosure 2.jpeg

New page

== Licensing ==
{{CC }} Oleg

File:10393 half enclosure 1.jpeg

Mon, 11/05/2018 - 12:58

Oleg uploaded File:10393 half enclosure 1.jpeg

New page

== Licensing ==
{{CC }} Oleg

Fix network configuration

Fri, 10/26/2018 - 16:51

‎Quick instructions

← Older revision Revision as of 22:51, 26 October 2018 (4 intermediate revisions by the same user not shown)Line 15: Line 15:    cd fix_net_config   cd fix_net_config    ./host_script.sh 192.168.0.9</font>   ./host_script.sh 192.168.0.9</font> −* If the boot device is internal NAND flash, run '''shutdown -hP now''' to commit changes before power-cycling the camera. Not required if booted from uSD card.+Example output:  + <font size='1'>Copy data to the target...  + rootfs.tar.gz                                                                                                                                                                                                                               + 100%  925    0.9KB/s  00:00     + fix_net_config.py                                                                                                                                                                                                                           + 100% 2701    2.6KB/s  00:00     + Run fix_net_config.py from the target...  + Step 0: Start  + Step 1: Unpack  + Step 2: Read current network settings  + Settings for /etc/network/interfaces:  +  ipaddr:  192.168.0.9  +  netmask: 255.255.255.0  +  gateway: 192.168.0.15  + Step 3: Apply network settings to file  + Step 4: Overwrite filesystem  + Step 5: Request syncing (if boot from flash)  + NEXT:  +    * if boot from SD card - simply reboot  +    * if boot from flash -  +      ~$ ssh root@192.168.0.9  +      root@elphel393:~# shutdown -hP now  +      then powercycle  + Success</font>  +   +* To sync the changes to the file system:  + <font size=2>ssh root@192.168.0.9  + ''pass''</font>  +   + <font size=2>#boot from NAND flash?  + root@elphel393:~# shutdown -hP now  + #powercycle</font>  +   + <font size=2>#boot from card?  + root@elphel393:~# sync  + root@elphel393:~# reboot -f</font>  +   Next, any extra changes related to setting ip address, netmask or gateway made to '''''/etc/elphel393/init_elphel393.py''''' can be commented out or the original file can be used. Next, any extra changes related to setting ip address, netmask or gateway made to '''''/etc/elphel393/init_elphel393.py''''' can be commented out or the original file can be used.    Line 31: Line 67:       └──'''etc/network/interfaces'''    - network setup for eth0      └──'''etc/network/interfaces'''    - network setup for eth0  </font> </font> −  −      [[Category:393]] [[Category:393]] Oleg

Fix network configuration

Fri, 10/26/2018 - 16:32

‎Quick instructions

← Older revision Revision as of 22:32, 26 October 2018 (2 intermediate revisions by the same user not shown)Line 9: Line 9:  ==How to update network setup for '''20180511''' (or older firmware)== ==How to update network setup for '''20180511''' (or older firmware)==  ===Quick instructions=== ===Quick instructions=== −* Camera is online. The ip address can be any, e.g., 192.168.0.9+* Camera is online. The IP address can be any, e.g., 192.168.0.9 −* PC: in a terminal window (linux os) type the following commands:+* PC: in a terminal window (GNU/Linux OS) type the following commands:    <font size='2'>wget https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz   <font size='2'>wget https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz    tar -xzpf fix_net_config.tar.gz   tar -xzpf fix_net_config.tar.gz    cd fix_net_config   cd fix_net_config    ./host_script.sh 192.168.0.9</font>   ./host_script.sh 192.168.0.9</font> − +* If the boot device is internal NAND flash, run '''shutdown -hP now''' to commit changes before power-cycling the camera. Not required if booted from uSD card.  Next, any extra changes related to setting ip address, netmask or gateway made to '''''/etc/elphel393/init_elphel393.py''''' can be commented out or the original file can be used. Next, any extra changes related to setting ip address, netmask or gateway made to '''''/etc/elphel393/init_elphel393.py''''' can be commented out or the original file can be used.    Line 21: Line 21:  From a Linux PC, download [https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz fix_net_config.tar.gz]. From a Linux PC, download [https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz fix_net_config.tar.gz].  The archive contains 2 scripts - one (shell) is run from the host PC, another (python) will be copied and automatically run on the camera.   The archive contains 2 scripts - one (shell) is run from the host PC, another (python) will be copied and automatically run on the camera.   −The python script will write the current configuration to '''''/etc/network/interfaces''''' and overwrite one of the init scripts to disable network+The python script will write the current configuration (IP, mask, default gateway for eth0) to '''''/etc/network/interfaces''''' and overwrite one of the init scripts to disable network  configuration in '''''/etc/elphel393/init_elphel393.py''''' on startup. configuration in '''''/etc/elphel393/init_elphel393.py''''' on startup.    <font size='2'>'''fix_net_config.tar.gz'''   <font size='2'>'''fix_net_config.tar.gz''' Andrey.filippov

Fix network configuration

Fri, 10/26/2018 - 16:25

‎Quick instructions

← Older revision Revision as of 22:25, 26 October 2018 (One intermediate revision by the same user not shown)Line 9: Line 9:  ==How to update network setup for '''20180511''' (or older firmware)== ==How to update network setup for '''20180511''' (or older firmware)==  ===Quick instructions=== ===Quick instructions=== −* Camera is online. The ip address can be any, e.g., 192.168.0.9+* Camera is online. The IP address can be any, e.g., 192.168.0.9 −* PC: in a terminal window (linux os) type the following commands:+* PC: in a terminal window (GNU/Linux OS) type the following commands:    <font size='2'>wget https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz   <font size='2'>wget https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz    tar -xzpf fix_net_config.tar.gz   tar -xzpf fix_net_config.tar.gz Line 21: Line 21:  From a Linux PC, download [https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz fix_net_config.tar.gz]. From a Linux PC, download [https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz fix_net_config.tar.gz].  The archive contains 2 scripts - one (shell) is run from the host PC, another (python) will be copied and automatically run on the camera.   The archive contains 2 scripts - one (shell) is run from the host PC, another (python) will be copied and automatically run on the camera.   −The python script will write the current configuration to '''''/etc/network/interfaces''''' and overwrite one of the init scripts to disable network+The python script will write the current configuration (IP, mask, default gateway for eth0) to '''''/etc/network/interfaces''''' and overwrite one of the init scripts to disable network  configuration in '''''/etc/elphel393/init_elphel393.py''''' on startup. configuration in '''''/etc/elphel393/init_elphel393.py''''' on startup.    <font size='2'>'''fix_net_config.tar.gz'''   <font size='2'>'''fix_net_config.tar.gz''' Andrey.filippov

10393 manual

Fri, 10/26/2018 - 16:04

‎Other info

← Older revision Revision as of 22:04, 26 October 2018 Line 389: Line 389:    root@elphel393:~# nano /etc/elphel393/init_elphel393.py   root@elphel393:~# nano /etc/elphel393/init_elphel393.py    edit line starting with ''IPADDR'' (and optionally ''IPMASK'')   edit line starting with ''IPADDR'' (and optionally ''IPMASK'') −  ''&lt;cntrl-O&gt;'' - to save changes+  ''&lt;ctrl-O&gt;'' - to save changes −  ''&lt;cntrl-X&gt;'' - to exit+  ''&lt;ctrl-X&gt;'' - to exit  </font> </font>  '''or''' '''or''' Oleg

Fix network configuration

Fri, 10/26/2018 - 15:51

‎How to update network setup for 20180511 (or older firmware)

← Older revision Revision as of 21:51, 26 October 2018 (2 intermediate revisions by the same user not shown)Line 15: Line 15:    cd fix_net_config   cd fix_net_config    ./host_script.sh 192.168.0.9</font>   ./host_script.sh 192.168.0.9</font>  +  +Next, any extra changes related to setting ip address, netmask or gateway made to '''''/etc/elphel393/init_elphel393.py''''' can be commented out or the original file can be used.     ===Description=== ===Description=== Oleg

10393 manual

Fri, 10/26/2018 - 15:47

‎Other info

← Older revision Revision as of 21:47, 26 October 2018 Line 377: Line 377:     ==<font color="blue">Other info</font>== ==<font color="blue">Other info</font>==  +===Change default ip address (recommended way)===  +Modify '''''/etc/network/interfaces''''', sync the changes to the file system and reboot (or rerun init scripts).  +  +For firmware 20180511 or older, follow [[Fix_network_configuration|these instructions]] to fix network configuration (= disable setting ip address via '''/etc/elphel393/init_elphel393.py''').  +  ===Change default ip address=== ===Change default ip address===  * '''nano''' or '''vi''' * '''nano''' or '''vi''' Oleg

Fix network configuration

Fri, 10/26/2018 - 15:40

‎Description

← Older revision Revision as of 21:40, 26 October 2018 (5 intermediate revisions by the same user not shown)Line 1: Line 1:  ==Description== ==Description== −In the firmware [https://community.elphel.com/files/393/20180511/ '''20180511'''] and older the ip address and network mask of the camera are applied from ''/etc/elphel393/init_elphel393.py''+In the firmware [https://community.elphel.com/files/393/20180511/ '''20180511'''] (and older) the ip address and network mask of the camera are set by '''''/etc/elphel393/init_elphel393.py''''' −script overriding ''/etc/network/interfaces'', which appeared to have incorrect configuration.+script overriding '''''/etc/network/interfaces''''', which appeared to have incorrect configuration.    −In the newer firmware releases this functionality will be disabled to bring the network setup to a more traditional way, i.e. by modifying ''/etc/network/interfaces''.+In the newer firmware releases this functionality will be disabled to bring the network setup to a more traditional way, i.e. by modifying '''''/etc/network/interfaces'''''.      −==How to update network setup for '''20180511''' or older firmware==+Follow the instructions below to fix this for the older firmware.  +   +==How to update network setup for '''20180511''' (or older firmware)==  ===Quick instructions=== ===Quick instructions===  * Camera is online. The ip address can be any, e.g., 192.168.0.9 * Camera is online. The ip address can be any, e.g., 192.168.0.9 −* In a terminal window (linux os) type the following commnads:+* PC: in a terminal window (linux os) type the following commands:    <font size='2'>wget https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz   <font size='2'>wget https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz    tar -xzpf fix_net_config.tar.gz   tar -xzpf fix_net_config.tar.gz Line 17: Line 19:  From a Linux PC, download [https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz fix_net_config.tar.gz]. From a Linux PC, download [https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz fix_net_config.tar.gz].  The archive contains 2 scripts - one (shell) is run from the host PC, another (python) will be copied and automatically run on the camera.   The archive contains 2 scripts - one (shell) is run from the host PC, another (python) will be copied and automatically run on the camera.   −The python script will write the current configuration to ''/etc/network/interfaces'' and overwrite one of the init scripts to disable network+The python script will write the current configuration to '''''/etc/network/interfaces''''' and overwrite one of the init scripts to disable network −configuration in ''/etc/elphel393/init_elphel393.py'' on startup.+configuration in '''''/etc/elphel393/init_elphel393.py''''' on startup.    <font size='2'>'''fix_net_config.tar.gz'''   <font size='2'>'''fix_net_config.tar.gz'''    ├── '''README.md'''            ├── '''README.md'''          Line 24: Line 26:    ├── '''fix_net_config.py'''            - unpacks '''rootfs.tar.gz''', replaces network configuration with the current one and copies all files to the root file system   ├── '''fix_net_config.py'''            - unpacks '''rootfs.tar.gz''', replaces network configuration with the current one and copies all files to the root file system    └── '''rootfs.tar.gz'''                - archive with 2 files   └── '''rootfs.tar.gz'''                - archive with 2 files −     ├──'''etc/init.d/init_elphel393''' - init script that disables network setup in ''/etc/elphel393/init_elphel393.py''+     ├──'''etc/init.d/init_elphel393''' - init script that disables network setup in '''''/etc/elphel393/init_elphel393.py'''''       └──'''etc/network/interfaces'''    - network setup for eth0      └──'''etc/network/interfaces'''    - network setup for eth0  </font> </font> Oleg

Fix network configuration

Fri, 10/26/2018 - 15:29

Created page with "==Description== In the firmware [https://community.elphel.com/files/393/20180511/ '''20180511'''] and older the ip address and network mask of the camera are applied from ''/e..."

New page

==Description==
In the firmware [https://community.elphel.com/files/393/20180511/ '''20180511'''] and older the ip address and network mask of the camera are applied from ''/etc/elphel393/init_elphel393.py''
script overriding ''/etc/network/interfaces'', which appeared to have incorrect configuration.

In the newer firmware releases this functionality will be disabled to bring the network setup to a more traditional way, i.e. by modifying ''/etc/network/interfaces''.

==How to update network setup for '''20180511''' or older firmware==
===Quick instructions===
* Camera is online. The ip address can be any, e.g., 192.168.0.9
* In a terminal window (linux os) type the following commnads:
<font size='2'>wget https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz
tar -xzpf fix_net_config.tar.gz
cd fix_net_config
./host_script.sh 192.168.0.9</font>

===Description===
From a Linux PC, download [https://community.elphel.com/files/393/fix_network_config/fix_net_config.tar.gz fix_net_config.tar.gz].
The archive contains 2 scripts - one (shell) is run from the host PC, another (python) will be copied and automatically run on the camera.
The python script will write the current configuration to ''/etc/network/interfaces'' and overwrite one of the init scripts to disable network
configuration in ''/etc/elphel393/init_elphel393.py'' on startup.
<font size='2'>'''fix_net_config.tar.gz'''
├── '''README.md'''
├── '''host_script.sh''' - run from host pc: copies '''fix_net_config.py''' and '''rootfs.tar.gz''' then runs '''fix_net_config.py'''
├── '''fix_net_config.py''' - unpacks '''rootfs.tar.gz''', replaces network configuration with the current one and copies all files to the root file system
└── '''rootfs.tar.gz''' - archive with 2 files
├──'''etc/init.d/init_elphel393''' - init script that disables network setup in ''/etc/elphel393/init_elphel393.py''
└──'''etc/network/interfaces''' - network setup for eth0
</font>



[[Category:393]] Oleg

10393 manual

Wed, 10/24/2018 - 19:59

‎Change default ip address

← Older revision Revision as of 01:59, 25 October 2018 Line 383: Line 383:    ''pass''   ''pass''    root@elphel393:~# nano /etc/elphel393/init_elphel393.py   root@elphel393:~# nano /etc/elphel393/init_elphel393.py −  ''edit - save''+  edit line starting with ''IPADDR'' (and optionally ''IPMASK'')  + ''&lt;cntrl-O&gt;'' - to save changes  + ''&lt;cntrl-X&gt;'' - to exit  </font> </font>  '''or''' '''or''' Line 402: Line 404:    root@elphel393:~# reboot -f   root@elphel393:~# reboot -f  </font> </font>  +  ===Add a program or a shell command to autostart on boot=== ===Add a program or a shell command to autostart on boot===  There's a way to do this using [https://unix.stackexchange.com/questions/56957/how-to-start-an-application-automatically-on-boot cron or init.d] but it might run before the sensors are initialized by init_elphel393.py. The recommended way is the following: There's a way to do this using [https://unix.stackexchange.com/questions/56957/how-to-start-an-application-automatically-on-boot cron or init.d] but it might run before the sensors are initialized by init_elphel393.py. The recommended way is the following: Andrey.filippov

Development for 10393

Wed, 10/24/2018 - 19:27

‎Flash vs micro SD

← Older revision Revision as of 01:27, 25 October 2018 (2 intermediate revisions by the same user not shown)Line 31: Line 31:  * flash works best for a production system: * flash works best for a production system:  ** non-replaceable ** non-replaceable −** limited write cycles+** provisions are made to limit write cycles and to prevent inadvertent file system changes −** because of overlayfs changes need an extra sync (overlay_sync) and a proper reboot to get written to the flash.+** overlayfs file system merges nonvolatile (flash) and volatile (ram disk) file systems, power-cycling discards all file modifications made during the last session  +** an extra sync command (overlay_sync) and a proper reboot is required to commit file system changes to the system flash memory (see overlay_syn usage example [[10393_manual#Change_default_ip_address]]).     ===Environment tree=== ===Environment tree=== Andrey.filippov

Network configuration

Wed, 10/24/2018 - 17:13

← Older revision Revision as of 23:13, 24 October 2018 (One intermediate revision by the same user not shown)Line 1: Line 1: −Network camera and especially RTP/RTSP network streaming require a proper network configuration. Here is the list of default settings and some hacks you can do.+{{Legacy}}  += NC393 cameras =  +Network configuration for the NC393 cameras is documented in 10393 Manual: [[10393_manual#Change_default_ip_address]]  +      = Elphel 353 network config  = = Elphel 353 network config  =  +Network camera and especially RTP/RTSP network streaming require a proper network configuration. Here is the list of default settings and some hacks you can do.     == Serial Number/Ethernet Address == == Serial Number/Ethernet Address == Andrey.filippov

Images and videos examples

Wed, 10/24/2018 - 10:59

← Older revision Revision as of 16:59, 24 October 2018 Line 1: Line 1: −=Images=+This page contains many of the old examples, some are very old     +Our current (2018) focus is in extremely long range 3D vision now combines our advanced hardware with the neural networks [https://blog.elphel.com/2018/09/neural-network-doubled-effective-baseline-of-the-stereo-camera/]  +  +=3D scene models (2017-2018)=  +3D scenes captured in May 2018 with the quad stereo camera [https://community.elphel.com/3d+biquad]  +  +3D scenes captured in 2017 with the prototype (3d-printed) quad stereo camera [https://community.elphel.com/3d+map]. There are interesting scenes, such like frozen in time ocean waves, but the camera itself was less precise  +  +=Images (old)=  ==3MPix micron sensor== ==3MPix micron sensor==  === Examples of pictures taken with various lens types === === Examples of pictures taken with various lens types === Line 68: Line 76:  An image in [[JP4]] format (JPEG without color interpolation) [http://community.elphel.com/pictures/jp4.jpg] An image in [[JP4]] format (JPEG without color interpolation) [http://community.elphel.com/pictures/jp4.jpg]    −=Videos=+=Videos (old)=  Additional videos are available [http://community.elphel.com/videos/ here] Additional videos are available [http://community.elphel.com/videos/ here]    Line 174: Line 182:  This is a 5 MPix MJP4/MOV example: [http://community.elphel.com/videos/lezard-5MP-JP4-1207170824_859137.mov]. MJP4 is based on JPEG compression of the raw Bayer pixels, rearranged in each macroblock before compression to reduce the high frequency components caused by color ) This is a 5 MPix MJP4/MOV example: [http://community.elphel.com/videos/lezard-5MP-JP4-1207170824_859137.mov]. MJP4 is based on JPEG compression of the raw Bayer pixels, rearranged in each macroblock before compression to reduce the high frequency components caused by color )    −=Medical=+=Medical (old)=     ==Endoscopy camera== ==Endoscopy camera== Andrey.filippov

10393 manual

Tue, 10/23/2018 - 10:39

‎Power on

← Older revision Revision as of 16:39, 23 October 2018 (6 intermediate revisions by the same user not shown)Line 65: Line 65:  ====Notes==== ====Notes====  * Boot time: ~30s * Boot time: ~30s −* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot+* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot. −* For development one can boot from the &mu;SD recovery card and use it+* For a production system with rare changes to the file system it is recommended to boot from NAND flash. Changes to the file system require running an extra sync command (overlay_sync) followed by a proper reboot.  +* For development, one can boot from the &mu;SD recovery card and use it - saving changes does not require extra sync actions.     ==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>== Line 401: Line 402:    root@elphel393:~# reboot -f   root@elphel393:~# reboot -f  </font> </font>  +===Add a program or a shell command to autostart on boot===  +There's a way to do this using [https://unix.stackexchange.com/questions/56957/how-to-start-an-application-automatically-on-boot cron or init.d] but it might run before the sensors are initialized by init_elphel393.py. The recommended way is the following:  +* '''nano''' or '''vi'''  +<font size='2'>  + ssh root@192.168.0.9  + ''pass''  + root@elphel393:~# nano /etc/elphel393/init_elphel393.py  + ''edit - save''  + ''example: to launch the rtsp streamer - add '''shout("/usr/bin/str")''' to the end of the file''. shout() function is just a wrapper for '''subprocess.call(cmd,shell=True)'''  +</font>  +Then:  +<font size='2'>  + #boot from NAND flash?  + root@elphel393:~# overlay_sync 1  + root@elphel393:~# shutdown -hP now  + #powercycle  +  + #boot from card?  + root@elphel393:~# sync  + root@elphel393:~# reboot -f  +</font>  +  ===Set up histogram window and autoexposure parameters=== ===Set up histogram window and autoexposure parameters===  [[Autoexposure|Read article]] [[Autoexposure|Read article]] Oleg

10393 manual

Mon, 10/22/2018 - 19:10

‎Add a program or a shell command to autostart on boot

← Older revision Revision as of 01:10, 23 October 2018 (5 intermediate revisions by the same user not shown)Line 65: Line 65:  ====Notes==== ====Notes====  * Boot time: ~30s * Boot time: ~30s −* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot+* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot. −* For development one can boot from the &mu;SD recovery card and use it+* For a production system with rare changes to the file system it is recommended to boot from NAND flash.  +* For development, one can boot from the &mu;SD recovery card and use it.     ==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>== Line 401: Line 402:    root@elphel393:~# reboot -f   root@elphel393:~# reboot -f  </font> </font>  +===Add a program or a shell command to autostart on boot===  +There's a way to do this using [https://unix.stackexchange.com/questions/56957/how-to-start-an-application-automatically-on-boot cron or init.d] but it might run before the sensors are initialized by init_elphel393.py. The recommended way is the following:  +* '''nano''' or '''vi'''  +<font size='2'>  + ssh root@192.168.0.9  + ''pass''  + root@elphel393:~# nano /etc/elphel393/init_elphel393.py  + ''edit - save''  + ''example: to launch the rtsp streamer - add '''shout("/usr/bin/str")''' to the end of the file''. shout() function is just a wrapper for '''subprocess.call(cmd,shell=True)'''  +</font>  +Then:  +<font size='2'>  + #boot from NAND flash?  + root@elphel393:~# overlay_sync 1  + root@elphel393:~# shutdown -hP now  + #powercycle  +  + #boot from card?  + root@elphel393:~# sync  + root@elphel393:~# reboot -f  +</font>  +  ===Set up histogram window and autoexposure parameters=== ===Set up histogram window and autoexposure parameters===  [[Autoexposure|Read article]] [[Autoexposure|Read article]] Oleg

10393 manual

Mon, 10/22/2018 - 18:27

‎Notes

← Older revision Revision as of 00:27, 23 October 2018 (2 intermediate revisions by the same user not shown)Line 65: Line 65:  ====Notes==== ====Notes====  * Boot time: ~30s * Boot time: ~30s −* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot+* The default boot is from the on-board NAND flash. [[Boot_options_393|More information]] on available boot options and recovery boot. −* For development one can boot from the &mu;SD recovery card and use it+* For a production system with rare changes to the file system it is recommended to boot from NAND flash.  +* For development, one can boot from the &mu;SD recovery card and use it.     ==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>== Oleg

Trigger 393

Tue, 10/16/2018 - 10:46

‎10389 trigger testing

← Older revision Revision as of 16:46, 16 October 2018 (One intermediate revision by the same user not shown)Line 101: Line 101:  ==<font color="blue">10389 trigger testing</font>== ==<font color="blue">10389 trigger testing</font>==    −===external connector===+===External connector===  In this test the camera triggers itself via audio cable. For cable wiring see [[103891]].   In this test the camera triggers itself via audio cable. For cable wiring see [[103891]].    * To test: * To test: Line 115: Line 115:  |} |}    −===internal connectors===+===Internal connectors===  In this test the camera triggers itself via 4-pin flex cable.   In this test the camera triggers itself via 4-pin flex cable.    * Connect as displayed on the pictures below. * Connect as displayed on the pictures below. Line 134: Line 134:  |} |}     +===Sync example: from external to internal (chaining)===  +* The simplest synchronization would be making a custom audio cable to sync all cameras in the system  +* In case there are multiple cameras in the same enclosure it might make sense to sync them by chaining using 4-pin flex cables  +{|  +|valign='top'|[[File:10389 sync example 1.jpeg|thumb|400px]]  +|}        [[Category:393]] [[Category:393]] Oleg

File:10389 sync example 1.jpeg

Tue, 10/16/2018 - 10:41

Oleg uploaded File:10389 sync example 1.jpeg

New page

== Licensing ==
{{CC }} Oleg

Pages