File:103992 sch.pdf
Andrey.filippov uploaded File:103992 sch.pdf
New page
== Licensing =={{CERN OHLv1.1 }} Andrey.filippov
103992
Created page with "==103992== Adapter for FLIR Lepton-3 160x120 LWIR sensor module thumb|400px| [[Media:103992_sch.pdf|103992 circuit diagram <br/> Media:103992_gerber..."
New page
==103992==Adapter for FLIR Lepton-3 160x120 LWIR sensor module
[[Image:103992_pcb.png|thumb|400px|
[[Media:103992_sch.pdf|103992 circuit diagram]] <br/>
[[Media:103992_gerber.tar.gz|103992 Gerber files]] <br/>
[[Media:103992_assy.tar.gz|103992 placement files]]
]]
Mechanical CAD files and 3D model: [[Elphel_camera_parts_0393-00#0393-00-992_-_103992_rev_0_Adapter_for_FLIR_Lepton-3_160x120_LWIR_sensor_module | 0393-00-991]] Andrey.filippov
Elphel camera parts 0393-00
0393-00-992 - 103992 rev 0 Adapter for FLIR Lepton-3 160x120 LWIR Sensor module
← Older revision Revision as of 21:18, 17 December 2018 (One intermediate revision by the same user not shown)Line 26: Line 26: ---- ---- −=== 0393-00-991 - 103991 rev 0 rigid-flex board for Ulis ATTO320-58 LWIR sensor===+=== 0393-00-991 - [[103991]] rev 0 rigid-flex board for Ulis ATTO320-58 LWIR sensor=== {{Cad4a|0393-00-991}} {{Cad4a|0393-00-991}} ---- ---- −=== 0393-00-992 - 103992 rev 0 Adapter for FLIR Lepton-3 160x120 LWIR Sensor module ===+=== 0393-00-992 - [[103992]] rev 0 Adapter for FLIR Lepton-3 160x120 LWIR sensor module === {{Cad4a|0393-00-992}} {{Cad4a|0393-00-992}} ---- ---- Andrey.filippov103991
103991
← Older revision Revision as of 21:16, 17 December 2018 (One intermediate revision by the same user not shown)Line 7: Line 7: [[Media:103991_assy.tar.gz|103991 placement files]] [[Media:103991_assy.tar.gz|103991 placement files]] ]] ]] + +Mechanical CAD files and 3D model: [[Elphel_camera_parts_0393-00#0393-00-991_-_103991_rev_0_rigid-flex_board_for_Ulis_ATTO320-58_LWIR_sensor | 0393-00-991]] Andrey.filippovElphel camera parts 0393-00
0393-00-25B - 10385 rev B power supply PCB assembly with 48V Traco
← Older revision Revision as of 20:28, 17 December 2018 Line 20: Line 20: === 0393-00-25B - 10385 rev B power supply PCB assembly with 48V Traco === === 0393-00-25B - 10385 rev B power supply PCB assembly with 48V Traco === {{Cad4a|0393-00-22B}} {{Cad4a|0393-00-22B}} +---- + +=== 0393-00-893 - 103893 rev 0 uIMS adapter board === +{{Cad4a|0393-00-893}} +---- + +=== 0393-00-991 - 103991 rev 0 rigid-flex board for Ulis ATTO320-58 LWIR sensor=== +{{Cad4a|0393-00-991}} +---- + +=== 0393-00-992 - 103992 rev 0 Adapter for FLIR Lepton-3 160x120 LWIR Sensor module === +{{Cad4a|0393-00-992}} ---- ---- Andrey.filippovMirroring to github
Created page with "* git.elphel.com: Create a project on https://git.elphel.com * git.elphel.com: Do anything * github: Create an empty project with the same name on https://github.com - withou..."
New page
* git.elphel.com: Create a project on https://git.elphel.com* git.elphel.com: Do anything
* github: Create an empty project with the same name on https://github.com - without any files
* github: Then "import code from another repository" - provide https url
* git.elphel.com: Add the webhook (take from an already mirrored project) Oleg
Development for 10393
after building
← Older revision Revision as of 01:25, 13 December 2018 Line 144: Line 144: </font> </font> +At some point when building from command line the sysroots link will be created. After '''sysroots''' link is there the project can be build from Eclipse IDE [[Category:393]] [[Category:393]] OlegTrigger 393
External trigger receive
← Older revision Revision as of 19:55, 12 December 2018 Line 59: Line 59: * http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4 * http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0&TRIG_OUT=0x66555&TRIG_PERIOD=25000000&TRIG=4 −===External trigger receive===+===External trigger receive (with possible self-triggering loop)=== −* http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x95555&TRIG_OUT=0x66555&TRIG_PERIOD=100000000&TRIG=4+Here, internal generator is routed to sync the cable output wires. +If the output wires are connected to the input wires (red+black and white+green) the camera will be self-triggering. +If the wires are not connected - use external source - apply "plus" to black, "minus" to green ([[103891|check colors and pinout]]): + + http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x95555&TRIG_OUT=0x66555&TRIG_PERIOD=100000000&TRIG=4 +* at the same time the fpga generator outputs a 1 fps signal - if the sync cable wires are properly connected the camera can be triggered from this 'external' signal + +===External trigger receive (external source only)=== +The sync cable wires can be looped or not - does not matter. + http://192.168.0.9/parsedit.php?sensor_port=0&immediate&TRIG_CONDITION=0x95555&TRIG_OUT=0x0&TRIG_PERIOD=100000000&TRIG=4 * at the same time the fpga generator outputs a 1 fps signal - if the sync cable wires are properly connected the camera can be triggered from this 'external' signal * at the same time the fpga generator outputs a 1 fps signal - if the sync cable wires are properly connected the camera can be triggered from this 'external' signal OlegROS2
ROS2
ROS2
ROS2
ROS2 General Notes
Show changes OlegROS1
Created page with "===Build=== <font color='red'>'''Won't build'''</font> <font size='1'>Build Configuration: BB_VERSION = "1.37.0" BUILD_SYS = "x86_64-linux" NATIVELSBS..."
New page
===Build===<font color='red'>'''Won't build'''</font>
<font size='1'>Build Configuration:
BB_VERSION = "1.37.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "elphel393"
DISTRO = "poky"
DISTRO_VERSION = "2.4+snapshot-20181204"
TUNE_FEATURES = "arm armv7a vfp neon cortexa9"
TARGET_FPU = "softfp"
meta
meta-poky
meta-yocto-bsp = "HEAD:72867393fe2004ab9f0ee23eb09a975c82938b9e"
meta-ezynq = "rocko:046de13c06cc248b725cb7b9928f35d4a369b50f"
meta-elphel393 = "rocko:0cea9b9b8776f0fe725316f1be1501396c95feb4"
meta-ros = "HEAD:72068b17e4192b51e09c8dc633805a35edac8701"
meta-xilinx-bsp = "HEAD:a18947c20dba2c0c38db8bde1ad4684995df4bbd"
meta-oe
meta-python
meta-networking
meta-webserver = "HEAD:34aa4c3202b427f59f843dc43a4e1afda4f81d13"</font>
* Error 1:
** ROS_USE_PYTHON3 = "yes"
** IMAGE_INSTALL += "roslaunch"
<font size='1'>NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'python3-pycrypto' (but /home/oleg/GIT/elphel393_rocko_clean_install/meta/meta-ros/recipes-devtools/python/python3-paramiko_1.16.0.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'python3-pycrypto' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python3-pycrypto']
NOTE: Runtime target 'python3-paramiko' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python3-paramiko', 'python3-pycrypto']
NOTE: Runtime target 'roslaunch' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['roslaunch', 'python3-paramiko', 'python3-pycrypto']
ERROR: Required build target 'core-image-elphel393' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-elphel393', 'roslaunch', 'python3-paramiko', 'python3-pycrypto']</font>
* Successful build:
** IMAGE_INSTALL += "roslaunch"
<font size='1'>NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'python3-pycrypto' (but /home/oleg/GIT/elphel393_rocko_clean_install/meta/meta-ros/recipes-devtools/python/python3-paramiko_1.16.0.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'python3-pycrypto' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python3-pycrypto']
NOTE: Runtime target 'python3-paramiko' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['python3-paramiko', 'python3-pycrypto']
NOTE: Runtime target 'roslaunch' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['roslaunch', 'python3-paramiko', 'python3-pycrypto']
ERROR: Required build target 'core-image-elphel393' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-elphel393', 'roslaunch', 'python3-paramiko', 'python3-pycrypto']</font>
* Error 2:
** <font color='red'>Seems like '''rostopic''' causes:</font>
<font size='1'>ERROR: python-imaging-1.1.7-r5 do_package_qa: QA Issue: python-imaging: The compile log indicates that host include and/or library paths were used.
Please check the log '/home/oleg/GIT/elphel393_rocko_clean_install/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_compile' for more information. [compile- host-path]
ERROR: python-imaging-1.1.7-r5 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: python-imaging-1.1.7-r5 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /home/oleg/GIT/elphel393_rocko_clean_install/poky/build/tmp/work/cortexa9-neon-poky-linux-gnueabi/python-imaging/1.1.7-r5/temp/log.do_package_qa.19425
ERROR: Task (/home/oleg/GIT/elphel393_rocko_clean_install/meta/meta-openembedded/meta-python/recipes-devtools/python/python-imaging_1.1.7.bb:do_package_qa) failed with exit code '1'</font>
potential links:
https://github.com/intel-aero/meta-intel-aero/issues/81
https://github.com/bmwcarit/meta-ros/issues/395
removed python3-imaging from '''rosbag''' - everything builds but then not really working.
with '''ROS_USE_PYTHON3 = "yes"''' stopped at finding an appropriate '''python-pycrypto''' lib
===Work===
* <font color='red'>'''Won't work'''</font>
** There's no '''rosrun''' (does not exist?)
** SSH session 1:
*** Add to /etc/hosts:
127.0.0.1 elphel393.localdomain elphel393
*** Export vars:
export ROS_ROOT=/opt/ros
export ROS_DISTRO=indigo
export ROS_PACKAGE_PATH=/opt/ros/indigo/share
export PATH=$PATH:/opt/ros/indigo/bin
export LD_LIBRARY_PATH=/opt/ros/indigo/lib
export PYTHONPATH=/opt/ros/indigo/lib/python2.7/site-packages
export ROS_MASTER_URI=http://localhost:11311
export CMAKE_PREFIX_PATH=/opt/ros/indigo
touch /opt/ros/indigo/.catkin
*** Roscore
roscore
** SSH session 2:
root@elphel393:~# rosnode list
<font size='1'>/rosout</font>
root@elphel393:~# rospack list
<font size='1'>cpp_common /opt/ros/indigo/share/cpp_common
genmsg /opt/ros/indigo/share/genmsg
genpy /opt/ros/indigo/share/genpy
rosbag /opt/ros/indigo/share/rosbag
rosbag_storage /opt/ros/indigo/share/rosbag_storage
rosclean /opt/ros/indigo/share/rosclean
rosconsole /opt/ros/indigo/share/rosconsole
roscpp /opt/ros/indigo/share/roscpp
roscpp_serialization /opt/ros/indigo/share/roscpp_serialization
roscpp_tutorials /opt/ros/indigo/share/roscpp_tutorials
rosgraph /opt/ros/indigo/share/rosgraph
rosgraph_msgs /opt/ros/indigo/share/rosgraph_msgs
roslaunch /opt/ros/indigo/share/roslaunch
roslib /opt/ros/indigo/share/roslib
roslz4 /opt/ros/indigo/share/roslz4
rosmaster /opt/ros/indigo/share/rosmaster
rosnode /opt/ros/indigo/share/rosnode
rosout /opt/ros/indigo/share/rosout
rospack /opt/ros/indigo/share/rospack
rosparam /opt/ros/indigo/share/rosparam
rospy /opt/ros/indigo/share/rospy
rospy_tutorials /opt/ros/indigo/share/rospy_tutorials
rostime /opt/ros/indigo/share/rostime
rostopic /opt/ros/indigo/share/rostopic
std_msgs /opt/ros/indigo/share/std_msgs
topic_tools /opt/ros/indigo/share/topic_tools
xmlrpcpp /opt/ros/indigo/share/xmlrpcpp</font> Oleg
ROS2
ROS2
ROS2
ROS2
ROS2
ROS2
Workflow
Show changes OlegROS2
Interfaces
← Older revision Revision as of 22:41, 7 December 2018 (20 intermediate revisions by the same user not shown)Line 1: Line 1: −==<font color='blue'>GitHub</font>==+==<font color='blue'>About</font>== −https://github.com/bmwcarit/meta-ros.git+Use ROS2 in Elphel single or multi-camera systems. The cameras are 10393 system boards based on Xilinx Zynq, ARM. −<font color='red'>https://github.com/erlerobot/meta-ros2</font> ?+==<font color='blue'>Goals</font>== +Having ROS2 cross-compiled and installed on each camera: +* '''Initialize cameras in a pre-defined multi-camera system''' - sync and sequence critical init +* '''Control multiple cameras from any camera of the system''' - parameters, recording +* '''Control multiple cameras from a PC''' (with ROS2 for PC installed). +* '''Control multiple cameras from a network device''' (w/o ROS2 installed, but with a browser) - by accessing a web server running on a camera interfaced with ROS2 of the camera. Can use nodejs or just lighttpd+php. +==<font color='blue'>Status</font>== +Development −==<font color='blue'>ROS2 General Notes</font>==+==<font color='blue'>Interfaces</font>== −===Notes===+ROS2 nodes communicate over: −* SROS is Secure ROS or something+* '''1 GigE LAN''' or (possibly) '''wifi''' (camera1-camera2..N, pc-camera1..N, pc1-pc2..M) −===Useful links===+* within a single device −* [http://docs.erlerobotics.com/robot_operating_system/ros2/tutorials/tutorial_10 Tutorials ErleRobotics]+<font color='green'>'''Notes:''' −* [https://github.com/intel/ros2_intel_realsense Intel RealSense]+* image sensors, IMS (or GPS & IMU), any other sensors are attached to cameras via a custom interface or USB, with appropriate driver support. −* [https://index.ros.org/doc/ros2/Ament-Tutorial/ Ament tutorial] - will not work for PC because it's outdated, will work in Yocto+* normally cameras in the system are synced with a custom trigger cable - this is setup over network −* [https://index.ros.org/doc/ros2/Colcon-Tutorial/ Colcon tutorial] - this one worked for PC+* any device attached to PC? −* [https://discourse.ros.org/t/suggestions-for-std-srvs/1079/16 STD-SRVS '''discussion'''] & [https://github.com/ros2/examples/issues/4 ROS2 examples(?)]+</font> −* [https://discourse.ros.org/search?q=meta-ros%20order%3Alatest About meta-ros]+ +==<font color='blue'>ROS2 on Zynq</font>== + +===Installation=== +* For Embedded Linux (but not Ubuntu Distro) use [https://github.com/bmwcarit/meta-ros.git meta-ros.git]. What about <font color='red'>[https://github.com/erlerobot/meta-ros2 meta-ros2]</font>? +<font color='green'>'''TODO:''' Include [https://github.com/bmwcarit/meta-ros.git meta-ros.git] in [https://git.elphel.com/Elphel/elphel393 elphel393] build system.</font> + +===Workflow=== + + +==<font color='blue'>ROS2 on PC</font>== +===Installation=== +* Google and follow the [https://index.ros.org/doc/ros2/ general instructions]. +<font color='green'>'''Notes:''' +* '''apt install ros-bouncy-desktop''' available in 18.04, <font color='red'>n/a in 16.04</font> +* '''apt install ros-ardent-desktop''' available in 16.04</font> −===PC workflow===+===Workflow=== −* Install ROS2 - will get installed to '''/opt/ros/<name>'''+* ROS2 will get installed to '''/opt/ros/<name>''', <name> = ardent, bouncy. * Terminal setup: * Terminal setup: source /opt/ros/bouncy/setup.bash source /opt/ros/bouncy/setup.bash Line 36: Line 58: * [https://erlerobotics.gitbooks.io/erle-robotics-python-gitbook-free/udp_and_tcp/a_simple_tcp_client_and_server.html Good book about UDP?] * [https://erlerobotics.gitbooks.io/erle-robotics-python-gitbook-free/udp_and_tcp/a_simple_tcp_client_and_server.html Good book about UDP?] −===Embedded workflow===+==<font color='blue'>ROS2 General Notes</font>== −* Use meta-ros in yocto+===Notes=== −* Go for ROS2 recipes. Use as examples.+* SROS is Secure ROS or something −* The build system in Yocto is '''ament''' - which is one generation older then '''colcon'''+===Useful links=== −* Here there's no workspace - packages do get installed somewhere+* [http://docs.erlerobotics.com/robot_operating_system/ros2/tutorials/tutorial_10 Tutorials ErleRobotics] −* Need to +* [https://github.com/intel/ros2_intel_realsense Intel RealSense] − export AMENT_PREFIX_PATH=/usr+* [https://index.ros.org/doc/ros2/Ament-Tutorial/ Ament tutorial] - will not work for PC because it's outdated, will work in Yocto −* Python scripts can live anywhere - because ROS2 populates /usr/lib/...+* [https://index.ros.org/doc/ros2/Colcon-Tutorial/ Colcon tutorial] - this one worked for PC −* Service formats are too few - for a simple "Request string - Response string" server need to add new srv.+* [https://discourse.ros.org/t/suggestions-for-std-srvs/1079/16 STD-SRVS '''discussion'''] & [https://github.com/ros2/examples/issues/4 ROS2 examples(?)] +* [https://discourse.ros.org/search?q=meta-ros%20order%3Alatest About meta-ros] ===Docker=== ===Docker=== Oleg