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

‎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

‎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

← 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

← 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

‎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

‎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

‎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

‎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

Oleg uploaded File:10389 sync example 1.jpeg

New page

== Licensing ==
{{CC }} Oleg

‎Description

← Older revision Revision as of 22:41, 12 October 2018 (5 intermediate revisions by the same user not shown)Line 1: Line 1:  ==<font color="blue">Description</font>== ==<font color="blue">Description</font>== −10389 board is required.+10389 board is required (and possible 103891).    −The triggering is used for one or several cameras synchronization or setting the frame rate (or fps). The conditions of the trigger can be generated either internally or externally. For external triggering a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey]) is required.+Use cases:  +* Trigger a single camera from external source  +* Synchronize multiple cameras to a master camera or external trigger source  +* Program frame rate  +   +The conditions of the trigger can be generated either internally or externally:  +* for external triggering a [[103891]] board and a 4-conductor 2.5mm audio plug with cable (example: [http://www.digikey.com/products/en?keywords=839-1029-ND digikey]) is required.  +* for internal triggering use J4-J6 connectors with a 4-pin flex cable: J4 - internal trigger source (also transmits timestamps that can be decoded by other cameras), J5-6 - receive trigger     To program trigger go to: '''http://192.168.0.9/parsedit.php => External Trigger Controls''' To program trigger go to: '''http://192.168.0.9/parsedit.php => External Trigger Controls''' Line 97: Line 104:  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: −  http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4+  - connect a sensor to port 0  + - http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4    visual: LED is blinking   visual: LED is blinking    software: frame counter is running   software: frame counter is running Oleg

‎Links

← Older revision Revision as of 22:23, 12 October 2018 Line 25: Line 25:  * [[Media:10389b.pdf|10389 Circuit Diagram, Parts List, PCB layout]] * [[Media:10389b.pdf|10389 Circuit Diagram, Parts List, PCB layout]]  * [[Media:10389b gerber.tar.gz|10389 Gerber files]] * [[Media:10389b gerber.tar.gz|10389 Gerber files]] − +* [[Media:10389b gerber.tar.gz|10389 Gerber files]]  +* [[Trigger 393|External/internal synchronization & triggering and frame rate controlling for single/multi-camera systems]]     [[Category:393]] [[Category:393]]  [[Category:Boards 393]] [[Category:Boards 393]] Oleg

‎External/internal trigger and FPS control

← Older revision Revision as of 22:18, 12 October 2018 Line 414: Line 414:  ===Switch between ERS and GRR modes in MT9P006=== ===Switch between ERS and GRR modes in MT9P006===  * [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]] * [[Electronic_Rolling_Shutter#ERS_and_GRR_in_MT9P001_on_10393|Read article]] −===External/internal trigger and FPS control===+===External/internal synchronization & triggering and FPS control for single/multi-camera systems===  * [[Trigger_393]] * [[Trigger_393]]  +  ===SSD/MMC/USB formatting=== ===SSD/MMC/USB formatting===  * [[Format_SSD_MMC]] * [[Format_SSD_MMC]] Oleg

‎internal connectors

← Older revision Revision as of 21:50, 12 October 2018 (6 intermediate revisions by the same user not shown)Line 91: Line 91:  * [[10389]] extension board * [[10389]] extension board  * [[103891]] adapter board for external trigger connection * [[103891]] adapter board for external trigger connection  +  +==<font color="blue">10389 trigger testing</font>==  +  +===external connector===  +In this test the camera triggers itself via audio cable. For cable wiring see [[103891]].  +* To test:  + http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4  + visual: LED is blinking  + software: frame counter is running  +  +* It's easy to modify the cable to trigger itself and other multiple cameras.  +  +{|  +|[[File:10389 extsync selftest.jpeg|thumb|400px]]  +|}  +  +===internal connectors===  +In this test the camera triggers itself via 4-pin flex cable.  +* Connect as displayed on the pictures below.  +** J4 - trigger output (master port)  +** J5-J6 - trigger input (slave ports)  +* To test:  + - connect a sensor to port 0  + - http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x8000&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4  + software: frame counter is running  +* To sync multiple camera, example:  + cable 1: camera1 (J4) -> camera2 (J6)  + cable 2: camera2 (J5) -> camera3 (J6)  + cable 3: camera3 (J5) -> camera4 (J6)  + etc.  +{|  +|valign='top'|[[File:10389 intsync selftest.jpeg|thumb|400px]]  +|valign='top'|[[File:10389 intsync selftest closeup.jpeg|thumb|400px]]  +|}  +  +     [[Category:393]] [[Category:393]] Oleg

Oleg uploaded File:10389 intsync selftest closeup.jpeg

New page

== Licensing ==
{{CC }} Oleg

Oleg uploaded File:10389 intsync selftest.jpeg

New page

== Licensing ==
{{CC }} Oleg

Oleg uploaded File:10389 extsync selftest.jpeg

New page

== Licensing ==
{{CC }} Oleg

‎Comparison table with similar products

Show changes Oleg

‎Comparison table

Show changes Oleg

‎Notes

← Older revision Revision as of 22:33, 4 October 2018 Line 161: Line 161:     ====Notes==== ====Notes==== −* Kernel version is 4.0, linux-xlnx+* yocto jethro: Kernel version is 4.0, linux-xlnx  +* yocto rocko:  Kernel version is 4.9.0, linux-xlnx  * Device Tree Blob is compiled separately in linux-xlnx * Device Tree Blob is compiled separately in linux-xlnx  * Uncompiled device tree files are present in the linux sources provided by linux-xlnx * Uncompiled device tree files are present in the linux sources provided by linux-xlnx Oleg