Andrey.filippov uploaded File:103991 assy.tar.gz

New page

== Licensing ==
{{CERN OHLv1.1 }} Andrey.filippov

Andrey.filippov uploaded File:103991 sch.pdf

New page

== Licensing ==
{{CERN OHLv1.1 }} Andrey.filippov

Andrey.filippov uploaded File:103991 pcb.png

New page

== Licensing ==
{{CERN OHLv1.1 }} Andrey.filippov

← Older revision Revision as of 00:51, 1 December 2018 Line 1: Line 1: −==Presentations==   ===2018/04/09 High Resolution Wide FoV CNN System for Target Classification, Ranging and Tracking=== ===2018/04/09 High Resolution Wide FoV CNN System for Target Classification, Ranging and Tracking===  *Presentation: *Presentation: Oleg

‎In the package

← Older revision Revision as of 21:44, 30 November 2018 (8 intermediate revisions by the same user not shown)Line 7: Line 7:     ==<font color="blue">In the package</font>== ==<font color="blue">In the package</font>== −* 10393 camera system+* 10393 camera system ([[Elphel_camera_assemblies|these 3D models]] might be helpful).  {| {|  |[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1a 10393 interfaces]] |[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1a 10393 interfaces]] Line 67: Line 67:  * No extra drivers are required on the host PC to operate the camera system. Can be operated from any network device with a browser. * No extra drivers are required on the host PC to operate the camera system. Can be operated from any network device with a browser.  * 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 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 a <font color='red'>'''production system'''</font> 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.+* For <font color='red'>'''development'''</font>, one can boot from the &mu;SD recovery card and use it - saving changes does not require extra sync actions.  +* Camera's software includes gcc compiler - relatively small projects can be compiled on the camera.     ==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>== Line 200: Line 201:     ==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>== ==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>==  +  +The FPGA-based Event Logger uses local clock for time-stamping data from Image Acquisition, External (Trigger) Input, GPS and IMU.  +  * [[Event_logger|'''More information''']] * [[Event_logger|'''More information''']]  ===Record=== ===Record=== Line 222: Line 226:  ** link the recorded logs to /www/pages/logs/ ** link the recorded logs to /www/pages/logs/  ** refresh http://192.168.0.9/read_imu_log.php ** refresh http://192.168.0.9/read_imu_log.php −  −      ==<font color="blue">Store/restore configuration</font>== ==<font color="blue">Store/restore configuration</font>== Line 378: Line 380:     ==<font color="blue">Other info</font>== ==<font color="blue">Other info</font>== −===Change default ip address (recommended way)===+===Change default ip address===  Modify '''''/etc/network/interfaces''''', sync the changes to the file system and reboot (or rerun init scripts). 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'''). 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===  −* '''nano''' or '''vi'''  −<font size='2'>  − ssh root@192.168.0.9  − ''pass''  − root@elphel393:~# nano /etc/elphel393/init_elphel393.py  − edit line starting with ''IPADDR'' (and optionally ''IPMASK'')  − ''&lt;ctrl-O&gt;'' - to save changes  − ''&lt;ctrl-X&gt;'' - to exit  −</font>  −'''or'''  −* '''sed'''  −<font size='2'>  − root@elphel393:~# sed -i.bkp 's/192.168.0.9/10.xx.xx.xx/' /etc/elphel393/init_elphel393.py  − root@elphel393:~# sed -i.bkp 's/255.255.255.0/xxx.xxx.xxx.xxx/' /etc/elphel393/init_elphel393.py  −</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>      ===Add a program or a shell command to autostart on boot=== ===Add a program or a shell command to autostart on boot=== Line 477: Line 451:     ===Available lengths for cables for connecting sensors in custom setups=== ===Available lengths for cables for connecting sensors in custom setups=== −* [[FPC_cables|FPC cables]] - click for available lengths - connect sensor to the system board+* [[FPC_cables|FPC cables]] - click for available lengths.  +* The cables are <font color='red'>asymmetrical</font> - for correct connecting a sensor to a system board see the figure below:  +{|  +|[[Image:Fpc_cable_conn_10393.jpeg|300px|thumb|Connecting sensors to the system board]]  +|}     ==<font color="blue">Known problems</font>== ==<font color="blue">Known problems</font>== Oleg

‎In the package

← Older revision Revision as of 21:44, 30 November 2018 (10 intermediate revisions by the same user not shown)Line 7: Line 7:     ==<font color="blue">In the package</font>== ==<font color="blue">In the package</font>== −* 10393 camera system+* 10393 camera system ([[Elphel_camera_assemblies|these 3D models]] might be helpful).  {| {|  |[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1a 10393 interfaces]] |[[File:NC393-CS marked ports.jpeg|thumb|200px|Fig.1a 10393 interfaces]] Line 65: Line 65:  ====Notes==== ====Notes====  * Boot time: ~30s * Boot time: ~30s  +* No extra drivers are required on the host PC to operate the camera system. Can be operated from any network device with a browser.  * 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 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 a <font color='red'>'''production system'''</font> 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.+* For <font color='red'>'''development'''</font>, one can boot from the &mu;SD recovery card and use it - saving changes does not require extra sync actions.  +* Camera's software includes gcc compiler - relatively small projects can be compiled on the camera.     ==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>== Line 199: Line 201:     ==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>== ==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>==  +  +The FPGA-based Event Logger uses local clock for time-stamping data from Image Acquisition, External (Trigger) Input, GPS and IMU.  +  * [[Event_logger|'''More information''']] * [[Event_logger|'''More information''']]  ===Record=== ===Record=== Line 221: Line 226:  ** link the recorded logs to /www/pages/logs/ ** link the recorded logs to /www/pages/logs/  ** refresh http://192.168.0.9/read_imu_log.php ** refresh http://192.168.0.9/read_imu_log.php −  −      ==<font color="blue">Store/restore configuration</font>== ==<font color="blue">Store/restore configuration</font>== Line 377: Line 380:     ==<font color="blue">Other info</font>== ==<font color="blue">Other info</font>== −===Change default ip address (recommended way)===+===Change default ip address===  Modify '''''/etc/network/interfaces''''', sync the changes to the file system and reboot (or rerun init scripts). 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'''). 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===  −* '''nano''' or '''vi'''  −<font size='2'>  − ssh root@192.168.0.9  − ''pass''  − root@elphel393:~# nano /etc/elphel393/init_elphel393.py  − edit line starting with ''IPADDR'' (and optionally ''IPMASK'')  − ''&lt;ctrl-O&gt;'' - to save changes  − ''&lt;ctrl-X&gt;'' - to exit  −</font>  −'''or'''  −* '''sed'''  −<font size='2'>  − root@elphel393:~# sed -i.bkp 's/192.168.0.9/10.xx.xx.xx/' /etc/elphel393/init_elphel393.py  − root@elphel393:~# sed -i.bkp 's/255.255.255.0/xxx.xxx.xxx.xxx/' /etc/elphel393/init_elphel393.py  −</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>      ===Add a program or a shell command to autostart on boot=== ===Add a program or a shell command to autostart on boot=== Line 476: Line 451:     ===Available lengths for cables for connecting sensors in custom setups=== ===Available lengths for cables for connecting sensors in custom setups=== −* [[FPC_cables|FPC cables]] - click for available lengths - connect sensor to the system board+* [[FPC_cables|FPC cables]] - click for available lengths.  +* The cables are <font color='red'>asymmetrical</font> - for correct connecting a sensor to a system board see the figure below:  +{|  +|[[Image:Fpc_cable_conn_10393.jpeg|300px|thumb|Connecting sensors to the system board]]  +|}     ==<font color="blue">Known problems</font>== ==<font color="blue">Known problems</font>== Oleg

‎Event Logger (GPS, IMU, IMG & EXT)

← Older revision Revision as of 19:30, 30 November 2018 (3 intermediate revisions by the same user not shown)Line 65: Line 65:  ====Notes==== ====Notes====  * Boot time: ~30s * Boot time: ~30s  +* No extra drivers are required on the host PC to operate the camera system. Can be operated from any network device with a browser.  * 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 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 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. * For development, one can boot from the &mu;SD recovery card and use it - saving changes does not require extra sync actions.  +* Camera's software includes gcc compiler - relatively small projects can be compiled on the camera.     ==<font color="blue">Defaults</font>== ==<font color="blue">Defaults</font>== Line 199: Line 201:     ==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>== ==<font color="blue">Event Logger (GPS, IMU, IMG & EXT)</font>==  +  +The FPGA-based Event Logger uses local clock for time-stamping data from Image Acquisition, External (Trigger) Input, GPS and IMU.  +  * [[Event_logger|'''More information''']] * [[Event_logger|'''More information''']]  ===Record=== ===Record=== Line 221: Line 226:  ** link the recorded logs to /www/pages/logs/ ** link the recorded logs to /www/pages/logs/  ** refresh http://192.168.0.9/read_imu_log.php ** refresh http://192.168.0.9/read_imu_log.php −  −      ==<font color="blue">Store/restore configuration</font>== ==<font color="blue">Store/restore configuration</font>== Oleg

‎Body and lenses adjusting

← Older revision Revision as of 02:15, 30 November 2018 Line 13: Line 13:  * To '''rotate a part around a tube''', release the screws. If the part is plastic, try to release them evenly with small steps. Start with the ones located close to the sides of the part, then do the middle ones. * To '''rotate a part around a tube''', release the screws. If the part is plastic, try to release them evenly with small steps. Start with the ones located close to the sides of the part, then do the middle ones.    −* Actual rotating - it is safe to rotate ±180&deg;. The cables inside the tubes are flat.+* Actual rotating - it is safe to rotate ±180&deg; (for any allowed rotation on Fig.2). The cables inside the tubes are flat.  +   +* Do not rotate the vertical tubes around the cross tube - it can cut off the cables inside.     * To '''fixate a part around a tube''', <font color='red'>'''carefully'''</font> tighten the screws. If the part is plastic try to tighten them evenly with small steps. Start with the screws located in the middle of the part where it is stronger. When fixated there's approximately 1-1.5mm gap between the parts arms. * To '''fixate a part around a tube''', <font color='red'>'''carefully'''</font> tighten the screws. If the part is plastic try to tighten them evenly with small steps. Start with the screws located in the middle of the part where it is stronger. When fixated there's approximately 1-1.5mm gap between the parts arms. Oleg

‎Body and lenses adjusting

← Older revision Revision as of 02:15, 30 November 2018 (3 intermediate revisions by the same user not shown)Line 1: Line 1:  ==Notes== ==Notes==  +===Exterior===  {| {| −|[[File:Hcam flat.jpeg|thumb|300px|Fig.1a NC393-H with rotated lenses and vertical mount, Front]]+|valign='top'|[[File:Hcam flat.jpeg|thumb|300px|Fig.1a NC393-H with rotated lenses and vertical mount, Front]] −|[[File:Hcam flat bot.jpeg|thumb|300px|Fig.1b Back]]+|valign='top'|[[File:Hcam flat bot.jpeg|thumb|300px|Fig.1b Back]]  |} |}  +===Body and lenses adjusting===  +{|  +|valign='top'|[[File:Hcam rotations.jpeg|thumb|500px|Fig.2 NC393-H '''with rotated lenses''', available rotations]]  +|}  +  +  +* To '''rotate a part around a tube''', release the screws. If the part is plastic, try to release them evenly with small steps. Start with the ones located close to the sides of the part, then do the middle ones.  +  +* Actual rotating - it is safe to rotate ±180&deg; (for any allowed rotation on Fig.2). The cables inside the tubes are flat.  +  +* Do not rotate the vertical tubes around the cross tube - it can cut off the cables inside.  +  +* To '''fixate a part around a tube''', <font color='red'>'''carefully'''</font> tighten the screws. If the part is plastic try to tighten them evenly with small steps. Start with the screws located in the middle of the part where it is stronger. When fixated there's approximately 1-1.5mm gap between the parts arms.  +  +* By default the camera is mounted vertically (easier to ship in this configuration), see Fig.1b. To change to horizontal mount the vertical tubes, those with sensors on ends, (Fig.2) have to be rotated 90&deg;. <font color='red'>The body (the blue one) should not be rotated around the cross tube - there's a stopper inside, so the cables might not get cut off.</font> After switching to horizontal mount - the sensors will be oriented upside down - they can be reattached but '''preferably''' change their vertical flips programatically (FLIPV) and store the settings.  +  +* To rotate a sensor front end 180&deg; = putting it upside down (This is discouraged in favor of setting everything from software - all settings can be stored/restored). Just remove all 4 screws holding it, then carefully pull it out from the plastic part, keeping in mind the cable - it's long enough but can be damaged. Rotate, then reinstall. Do not touch the screws that hold the plastic part and the tube.  +  +* To detach the sensor from the camera - do the previous action and just disconnect the cable.  +  +* To rotate the body 180&deg; = upside down. Unscrew only the screws holding the body with the plastic part.    −==Howtos==+* To detach the body (system boards) from the camera - it's complicated - please contact '''support'''. −===Rotate lens===  Oleg

‎Rotate lenses and body

← Older revision Revision as of 01:03, 30 November 2018 (One intermediate revision by the same user not shown)Line 1: Line 1:  ==Notes== ==Notes==  {| {| −|[[File:Hcam flat.jpeg|thumb|300px|Fig.1a NC393-H with rotated lenses and vertical mount, Front]]+|valign='top'|[[File:Hcam flat.jpeg|thumb|300px|Fig.1a NC393-H with rotated lenses and vertical mount, Front]] −|[[File:Hcam flat bot.jpeg|thumb|300px|Fig.1b Back]]+|valign='top'|[[File:Hcam flat bot.jpeg|thumb|300px|Fig.1b Back]]  |} |}     ==Howtos== ==Howtos== −===Rotate lens===+===Rotate lenses and body===  +{|  +|valign='top'|[[File:Hcam rotations.jpeg|thumb|500px|Fig.2 NC393-H '''with rotated lenses''', available rotations]]  +|} Oleg

Oleg uploaded File:Hcam rotations.jpeg

New page

== Licensing ==
{{CC }} Oleg

Created page with "==Notes== {| |thumb|300px|Fig.1a NC393-H with rotated lenses and vertical mount, Front |thumb|300px|Fig.1b Back |} ==Howto..."

New page

==Notes==
{|
|[[File:Hcam flat.jpeg|thumb|300px|Fig.1a NC393-H with rotated lenses and vertical mount, Front]]
|[[File:Hcam flat bot.jpeg|thumb|300px|Fig.1b Back]]
|}

==Howtos==
===Rotate lens=== Oleg

Oleg uploaded a new version of File:Hcam flat bot.jpeg

New page

== Licensing ==
{{CC }} Oleg

Oleg uploaded File:Hcam flat bot.jpeg

New page

== Licensing ==
{{CC }} Oleg

Oleg uploaded a new version of File:Hcam flat.jpeg

New page

== Licensing ==
{{CC }} Oleg

Oleg uploaded File:Hcam flat.jpeg

New page

== Licensing ==
{{CC }} Oleg

‎0393-27-16 - Calibration SFE housing

← Older revision Revision as of 00:31, 18 November 2018 Line 55: Line 55:  ---- ----    −=== 0393-27-16 - Calibration SFE housing ===+=== 0393-27-16 - Calibrated SFE housing ===  {{Cad4c|0393-27-16}} {{Cad4c|0393-27-16}}  ---- ---- Andrey.filippov

‎Notes

← Older revision Revision as of 23:48, 16 November 2018 (2 intermediate revisions by the same user not shown)Line 474: Line 474:  |valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]] |valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]]  |} |}  +  +===Available lengths for cables for connecting sensors in custom setups===  +* [[FPC_cables|FPC cables]] - click for available lengths - connect sensor to the system board     ==<font color="blue">Known problems</font>== ==<font color="blue">Known problems</font>==  * <font color='green'>'''[SOLVED]'''</font> Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing. * <font color='green'>'''[SOLVED]'''</font> Vertical artifacts in jpegs. Images are ok at 100% quality. Fixed, testing. −* http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?+* <font color='green'>'''[SOLVED]'''</font> http://192.168.0.9:232x/noexif/mimg - multipart jpeg displays corrupted frames from time to time. Reason: network bandwidth?  * <font color='green'>'''[SOLVED]'''</font> Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok. * <font color='green'>'''[SOLVED]'''</font> Sometimes on power-on (NAND flash boot) cannot mount the card's rootfs partition. Kernel Panics. Power off/on. Soft "reboot -f" works ok.  <font size='2'> <font size='2'> Line 485: Line 488:  </font> </font>  [[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]] [[VFS:_Unable_to_mount_root_fs_on_unknown-block(179,2)|More info]] −* Changing exposure/quality/gains - can corrupt images - needs testing.+* <font color='green'>'''[SOLVED]'''</font> Changing exposure/quality/gains - can corrupt images - needs testing.    −* After rewriting rootfs to &mu;SD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.+* <font color='green'>'''[SOLVED]'''</font> After rewriting rootfs to &mu;SD card - some of the cards get a corrupted partition - re-partitioning (reformatting?) solves the problem.  <font size='2'> <font size='2'>    On the camera the rootfs is mounted as RW and some of the files are changed (also links created) -   On the camera the rootfs is mounted as RW and some of the files are changed (also links created) - Line 494: Line 497:     ==<font color="blue">Notes</font>== ==<font color="blue">Notes</font>== −* In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]+* <font color='green'>'''[SOLVED]'''</font> In case rootfs is on flash, it might make sense (or maybe not as the history is updated only once on session exit) to disable bash sessions command history - [http://stackoverflow.com/questions/18663078/disable-history-in-linux disable bash history]    −* When using '''overlays''', deleting, existing in the lower layer, dirs can cause errors (hopefully it gets fixed someday), example:  +* <font color='green'>'''[SOLVED]'''</font> When using '''overlays''', deleting, existing in the lower layer, dirs can cause errors (hopefully it gets fixed someday), example:    ** /mnt/sda1 exists in lower layer: /tmp/rootfs.ro/tmp ** /mnt/sda1 exists in lower layer: /tmp/rootfs.ro/tmp  ** upper layer is mounted to "/" ** upper layer is mounted to "/" Oleg

‎Other info

← Older revision Revision as of 00:07, 16 November 2018 Line 474: Line 474:  |valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]] |valign='top'|[[File:10393 half enclosure 2.jpeg|thumb|200px]]  |} |}  +  +===Available lengths for cables for connecting sensors in custom setups===  +* [[FPC_cables|FPC cables]] - click for available lengths - connect sensor to the system board     ==<font color="blue">Known problems</font>== ==<font color="blue">Known problems</font>== Oleg

‎Links

← Older revision Revision as of 00:01, 16 November 2018 (One intermediate revision by the same user not shown)Line 115: Line 115:  *[[10389|10389 board]] *[[10389|10389 board]]  *[[Using_10359_mux_with_10393|Using 10393 with multiplexer boards 10359]] *[[Using_10359_mux_with_10393|Using 10393 with multiplexer boards 10359]]  +* [[FPC_cables|FPC cables]] - used to for connecting sensors, available lengths are 50-450 mm, follow the link for proper connecting     ==Known issues== ==Known issues== Oleg