Skip to content

Commit fcb37f6

Browse files
committed
Mirror master to GH main
1 parent 5770baf commit fcb37f6

File tree

7 files changed

+120
-5
lines changed

7 files changed

+120
-5
lines changed

.gitignore

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
*.tar

.gitlab-ci.yml

+43
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
# This file is a template, and might need editing before it works on your project.
2+
# This is a sample GitLab CI/CD configuration file that should run without any modifications.
3+
# It demonstrates a basic 3 stage CI/CD pipeline. Instead of real tests or scripts,
4+
# it uses echo commands to simulate the pipeline execution.
5+
#
6+
# A pipeline is composed of independent jobs that run scripts, grouped into stages.
7+
# Stages run in sequential order, but jobs within stages run in parallel.
8+
#
9+
# For more information, see: https://docs.gitlab.com/ee/ci/yaml/README.html#stages
10+
11+
# Image that is used in markdown spellcheck examples:
12+
# image: "registry.gitlab.com/pipeline-components/markdown-spellcheck:latest"
13+
14+
image: ubuntu:18.04
15+
16+
17+
stages: # List of stages for jobs, and their order of execution
18+
- build
19+
20+
21+
markdown-spellcheck:
22+
stage: build
23+
tags:
24+
- shared_docker
25+
when: always
26+
allow_failure: true
27+
before_script:
28+
- apt update
29+
- apt -y upgrade
30+
- apt -y install curl
31+
- curl -sL https://deb.nodesource.com/setup_6.x | bash -
32+
- apt -y install nodejs
33+
- apt -y install npm
34+
- npm i markdown-spellcheck -g
35+
script:
36+
- mdspell -a --en-us --report '**/*.md' > spellcheck-report.md
37+
artifacts:
38+
when: always
39+
paths:
40+
- spellcheck-report.md
41+
expire_in: 1 week
42+
43+

.spelling

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
ToF
2+
ifm
3+
imager
4+
FoV
5+
i.e.
6+
e.g.
7+
CONF_INVALID
8+
CONF_SATURATED
9+
CONF_BADAMBSYM
10+
CONF_LOWAMP
11+
CONF_EXPINDEX
12+
CONF_EXPSHIFT
13+
CONF_INVALID_RANGE
14+
CONF_SUSPECT_PIXEL
15+
CONF_EDGEPIXEL
16+
CONF_UNPLAUSIBLE
17+
CONF_REFLECTIVITY
18+
CONF_DYNAMIC_AMPLITUDE
19+
CONF_MIXEDPIXEL
20+
CONF_ISOLATED
21+
experimental_high_2m
22+
experimental_high_4m

O3R/Docker/docker_intro.md

-3
This file was deleted.

O3R/FAQ/FAQ.md

+52
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
# FAQ
2+
3+
__Q: Is it necessary to shut down the camera before switching off the power?__
4+
__A:__ No, the O3R system can be switched off at anytime (except during firmware update).
5+
6+
__Q: What kind of certificates does the O3R fullfil?__
7+
__A:__ CE (Europe) and UL(USA) will be fulfilled at the release of the system (October 2021).
8+
9+
__Q: VPU? Camera heads?__
10+
__A:__ `VPU` - Video Processing Unit. The O3R is using the NVidia TX2 as a base computing platform and free CPU and GPU resources can be used for customer algorithms. You can connect our camera heads directly to the VPU and you do not need to take care of communication, power etc. separately. These heads come in different flavors. 2D/3D, 38k or VGA resolution, 105° or 60° opening angle.
11+
12+
__Q: Are there any plans to include the O3R platform into the ifmVisionAssistant?__
13+
__A:__ Absolutely! The ifmVA will be available sometime after the official release of the O3R (October 2021).
14+
15+
__Q: What ports are used and can I change them?__
16+
__A:__ The O3R system is using the ports 8080,8888,50010-50025. Right now, it is not possible to change the ports, but this will be possible in the future.
17+
>Note: Ports 8080 and 8888 are reserved ports for specific ifm applications and can't be changed.
18+
19+
__Q: How can I define the extrinsic calibration for my different heads?__
20+
__A:__ There are several ways to do that and we do not recommend any one over the other. At ifm, we manly use the checkerboard method, but you can also manually measure everything or use other tools. If you want to know more, please get in touch with us and read our documentation.
21+
22+
__Q: Is it possible to change the extrinsic calibration?__
23+
__A:__ Indeed! You have the possibility to change the extrinsic calibration for each head. The calibration will be saved on the VPU and is also available after an reboot (see [configuring the camera](INSERT-LINK)). To know more, check out our [calibration documentation *coming soon*](INSERT-LINK).
24+
25+
__Q: Okay, so you have the ability to set the extrinsic calibration. Do we also need to intrinsically calibrate the camera?__
26+
__A:__ No, don't worry about this. We are calibrating each head individually in production. You can, however, receive the intrinsic calibration if you need it (it is sent in the `distance_image_info`, see the [images description *coming soon*](INSERT-LINK)).
27+
> Note: Our calibration also includes temperature, lens position, etc. There is no need for an additional calibration on your side.
28+
29+
__Q: Unfortunately, one of the heads was destroyed in dubious circumstances. Can I replace the head?__
30+
__A:__ Sure thing! Just get a new one and replace the broken one. We recommend performing a sanity check of the extrinsic calibration of the newly mounted head (the mounting of the camera might have shifted a few millimeters or degrees in the replacement process). But that's it. Just keep in mind that we have different kind of heads.
31+
32+
__Q: Can I replace a head with another type of head (60 degrees vs. 105 degrees for instance):__
33+
__A:__ Yes! The VPU does not need any new information about the new head. It might be that the VPU needs a bit longer after the first start with the new head. The VPU will query different information from the head to work properly. We are talking about seconds here, not minutes.
34+
35+
__Q: Are there any debug or logging capabilities within the VPU?__
36+
__A:__ The system is logging a lot of information all the time. You can receive this *trace* with our [ifm3d-library](INSERT-LINK) for the official launch).
37+
38+
__Q: How often do I have to update the firmware/software? Do I always need them?__
39+
__A:__ We are in a phase were we will release a new firmware fairly often (around once a month). This will most likely change after the official release. We recommend to always update to the newest firmware (due to bug fixes, but also because of security). We know that most of our customers use the approach "never touch a running system" and we get that. Our changelog and release notes will tell you exactly what changed and you can decide if it is worth the risk to update or not. If in doubt, just get in touch with us!
40+
41+
__Q: What kind of connection protocols can I use?__
42+
__A:__ Well, the default would be TCP/IP. This is also the default protocol for our libraries. You will, however, get access to the VPU itself at a certain point. Then, you can use other protocols, e.g., UDP. Ad UDP is not yet officially supported by ifm, you will need to implement it by yourself, but you are free to do so. You also can use the CAN interface.
43+
44+
__Q: How do I get access to the VPU in general?__
45+
__A:__ You have access via ssh and a customer account.
46+
47+
__Q: Can I use the VPU with its CPU/GPU and let my program run on it?__
48+
__A:__ 100%! You will be able to upload your program and/or develop directly on the VPU. The VPU will already run the docker engine, which will enable you to have an easy deployment. You can first develop on your machine, build the container and forward it to the VPU. We can provide to you some base images for the development if needed.
49+
50+
__Q: Do you support ROS1 & ROS2?__
51+
__A:__ We have two ROS-Wrappers for our ifm3D libraries, for ROS1 and ROS2. You can easily test the set up using containers, running the roscore on the VPU for instance, or just connect the VPU as a ROS client to your roscore or other nodes. Whatever suits you best. If you want to know more, you can read our [documentation](INSERT-LINK) or get in touch with us.
52+

O3R/Parameters/AcquisitionSettings/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -5,4 +5,4 @@
55
| [Modes](../../Parameters/AcquisitionSettings/modes.md)|
66
| [Offset](../../Parameters/AcquisitionSettings/offset.md)|
77

8-
Acquisition parameters change the basic setting on how the camera heads are taking images.
8+
Acquisition parameters change the basic setting on how the camera heads are taking images.

O3R/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,4 @@ Here you can find different topics related to the O3R product. Containing inform
1515
- configuring the O3R
1616
- using Docker on the O3R
1717
- getting data from the system
18-
- etc.
18+
- etc.

0 commit comments

Comments
 (0)