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: 2 min 27 sec ago

Meta-ros testing

Tue, 12/04/2018 - 14:05

‎ROS2

← Older revision Revision as of 21:05, 4 December 2018 (11 intermediate revisions by the same user not shown)Line 1: Line 1: −==GitHub==+==<font color='blue'>GitHub</font>==  https://github.com/bmwcarit/meta-ros.git https://github.com/bmwcarit/meta-ros.git     +==<font color='blue'>ROS1</font>==    −==ROS1==+===Build===  * Won't build * Won't build  +===Work===  +* Won't work    −==ROS2==+==<font color='blue'>ROS2</font>==  +   +===Build===  * Add path to bblayers.conf * Add path to bblayers.conf  * Add to "IMAGE_INSTALL_append" of core-image-elphel393.bb: * Add to "IMAGE_INSTALL_append" of core-image-elphel393.bb: Line 13: Line 18:    ros2msg \   ros2msg \    ros2run \   ros2run \  +  +'''Notes:'''  +* Is this a required minimum?  +* '''ROS_USE_PYTHON3 = "yes"''' results in errors?  +===Work===  +====1. Test Talker and Listener====  +* SSH session 1:  + root@elphel393:~# export AMENT_PREFIX_PATH=/usr  + root@elphel393:~# ros2 run demo_nodes_cpp talker  +* SSH session 2:  + root@elphel393:~# export AMENT_PREFIX_PATH=/usr  + root@elphel393:~# ros2 run demo_nodes_cpp listener  +  +'''Notes:'''  +* If AMENT_PREFIX_PATH is not set then:  + <font size='1'>Traceback (most recent call last):  +  File "/usr/bin/ros2", line 11, in <module>  +    load_entry_point('ros2cli==0.4.0', 'console_scripts', 'ros2')()  +  File "/usr/lib/python3.5/site-packages/ros2cli/cli.py", line 64, in main  +    rc = extension.main(parser=parser, args=args)  +  File "/usr/lib/python3.5/site-packages/ros2run/command/run.py", line 59, in main  +    executable_name=args.executable_name)  +  File "/usr/lib/python3.5/site-packages/ros2run/api/__init__.py", line 30, in get_executable_path  +    paths = get_executable_paths(package_name=package_name)  +  File "/usr/lib/python3.5/site-packages/ros2pkg/api/__init__.py", line 41, in get_executable_paths  +    prefix_path = get_prefix_path(package_name)  +  File "/usr/lib/python3.5/site-packages/ros2pkg/api/__init__.py", line 34, in get_prefix_path  +    prefix_path = get_package_prefix(package_name)  +  File "/usr/lib/python3.5/site-packages/ament_index_python/packages.py", line 49, in get_package_prefix  +    content, package_prefix = get_resource('packages', package_name)  +  File "/usr/lib/python3.5/site-packages/ament_index_python/resources.py", line 37, in get_resource  +    for path in get_search_paths():  +  File "/usr/lib/python3.5/site-packages/ament_index_python/search_paths.py", line 30, in get_search_paths  +    "Environment variable '{}' is not set or empty".format(AMENT_PREFIX_PATH_ENV_VAR))  + <font color='red'>'''OSError: Environment variable 'AMENT_PREFIX_PATH' is not set or empty'''</font></font>  +  +====2. Available packages====  +* SSH session:  + root@elphel393:~# export AMENT_PREFIX_PATH=/usr  + root@elphel393:~# ros2 pkg list  + <font size='1'>builtin_interfaces  + demo_nodes_cpp  + example_interfaces  + geometry_msgs  + rcl  + rcl_interfaces  + rclcpp  + rclpy  + rcutils  + rmw  + rmw_fastrtps_cpp  + rosidl_cmake  + rosidl_generator_c  + rosidl_generator_cpp  + rosidl_parser  + rosidl_typesupport_interface  + rosidl_typesupport_introspection_c  + rosidl_typesupport_introspection_cpp  + sensor_msgs  + </font> Oleg

Meta-ros testing

Tue, 12/04/2018 - 13:32

Created page with "==GitHub== https://github.com/bmwcarit/meta-ros.git ==ROS1== * Won't build ==ROS2== * Add path to bblayers.conf * Add to "IMAGE_INSTALL_append" of core-image-elphel393.bb:..."

New page

==GitHub==
https://github.com/bmwcarit/meta-ros.git


==ROS1==
* Won't build

==ROS2==
* Add path to bblayers.conf
* Add to "IMAGE_INSTALL_append" of core-image-elphel393.bb:
ros2-demo-nodes-cpp \
ros2topic \
ros2msg \
ros2run \ Oleg

Nc393-h

Mon, 12/03/2018 - 12:37

← Older revision Revision as of 19:37, 3 December 2018 Line 19: Line 19:  * 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.    −* 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.+* 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 will 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 programmatically (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 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. Oleg

Nc393-h

Mon, 12/03/2018 - 12:37

← Older revision Revision as of 19:37, 3 December 2018 (One intermediate revision by the same user not shown)Line 15: Line 15:  * Actual rotating - it is safe to rotate ±180&deg; (for any allowed rotation on Fig.2). 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.+* Do not rotate the vertical tubes around the cross tube (actually rotating by ±5&deg; is ok) - there are stoppers that prevent cutting 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.    −* 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.+* 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 will 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 programmatically (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 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. Oleg

103991

Sat, 12/01/2018 - 22:25

Created page with "==103991== Sensor front end for ULIS ATTO320-058 Sensor. thumb|400px| [[Media:103991_sch.pdf|103991 circuit diagram <br/> Media:103991_gerber.tar...."

New page

==103991==
Sensor front end for ULIS ATTO320-058 Sensor.

[[Image:103991_pcb.png|thumb|400px|
[[Media:103991_sch.pdf|103991 circuit diagram]] <br/>
[[Media:103991_gerber.tar.gz|103991 Gerber files]] <br/>
[[Media:103991_assy.tar.gz|103991 placement files]]
]] Andrey.filippov

File:103991 gerber.zip

Sat, 12/01/2018 - 22:21

Andrey.filippov uploaded File:103991 gerber.zip

New page

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

File:103991 gerber.tar.gz

Sat, 12/01/2018 - 22:21

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

New page

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

File:103991 assy.zip

Sat, 12/01/2018 - 22:20

Andrey.filippov uploaded File:103991 assy.zip

New page

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

File:103991 assy.tar.gz

Sat, 12/01/2018 - 22:20

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

New page

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

File:103991 sch.pdf

Sat, 12/01/2018 - 22:19

Andrey.filippov uploaded File:103991 sch.pdf

New page

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

File:103991 pcb.png

Sat, 12/01/2018 - 22:18

Andrey.filippov uploaded File:103991 pcb.png

New page

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

Presentations

Fri, 11/30/2018 - 17:51

← 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

10393 manual

Fri, 11/30/2018 - 14:44

‎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

10393 manual

Fri, 11/30/2018 - 14:44

‎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

10393 manual

Fri, 11/30/2018 - 12:30

‎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

Nc393-h

Thu, 11/29/2018 - 19:15

‎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

Nc393-h

Thu, 11/29/2018 - 19:15

‎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

Nc393-h

Thu, 11/29/2018 - 18:03

‎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

File:Hcam rotations.jpeg

Thu, 11/29/2018 - 18:00

Oleg uploaded File:Hcam rotations.jpeg

New page

== Licensing ==
{{CC }} Oleg

Nc393-h

Thu, 11/29/2018 - 16:13

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

Pages