Discussions - Recent Threads

AD7761 OO Test

stephenv — Fri, 04 Apr 2025 14:55:58 GMT

AD7761 OO Test

getframe buffer, retrieve last most recent frame from the buffer

GiorgioP — Thu, 20 Mar 2025 14:07:46 GMT

Hello,

having the EVAL-ADTF3175D-NXZ module up and running, with a host computer running a similar first_frame py script, in a loop saving frames together with IMU data,

I realized that the frame collected does not match with the IMU since the frames seems to be bufferized in the eval module ( I have an FPS a bit higher then the saving loop due to integer constraint)

As a workaround I made a nested loop to get frame until the time to get the new frame is approx the FPS time, if much shorter it's just getting the next one with a while loop.

So, my question wolud be : is there a way to flush the buffer, or even better to get the last frame of the supposed buffer and release the older ones ?

My FPS is 2 fps, and my loop get 2-3 "old" frames in 0.1-0.2 sec. before getting the real last one which take 0.5sec, and then I can match the IMU data with that one.

Many thanks !

Giorgio

Can't open "aditof-demo 3.1.0"

timlai — Fri, 04 Oct 2024 07:31:35 GMT

Hello,

I try to use Raspberry Pi 4B to operate the LiDAR(AD-FXTOF1-EBZ). I have followed all the steps on the website called "Raspberry Pi User Guide".

Unfortunately, I can't open it. When I pressed the play button, it would stop like the figure shown below.

When I used command window to open it, it showed some error message:

I20240919 15:54:57.865922 8189 system_impl.cpp:120] SDK version: 3.1.0 | branch: master | commit: 595409a
I20240919 15:54:57.865934 8189 system_impl.cpp:125] SDK built with websockets version:3.2.3
I20240919 15:54:57.981110 8189 sensor_enumerator_raspberrypi.cpp:53] looking for sensors on the target: Raspberry PI
I20240919 15:54:57.981846 8189 camera_fxtof1.cpp:137] Initializing camera
I20240919 15:54:57.982010 8189 addi9036_sensor.cpp:155] Opening device
I20240919 15:54:57.982040 8189 addi9036_sensor.cpp:173] Looking for the following cards:
I20240919 15:54:57.982061 8189 addi9036_sensor.cpp:175] unicam
I20240919 15:54:57.982617 8189 addi9036_sensor.cpp:191] Cannot identify /dev/video0 errno: 2error: No such file or directory
I20240919 15:54:57.982687 8189 addi9036_sensor.cpp:148] Failed to open device
I20240919 15:54:57.983664 8189 camera_fxtof1.cpp:881] Programming AFE error errno: 9 error: Bad file descriptor
I20240919 15:54:57.983736 8189 addi9036_sensor.cpp:392] VIDIOC_REQBUFS error errno: 9 error: Bad file descriptor
I20240919 15:54:57.983806 8189 camera_fxtof1.cpp:376] Failed to set frame type
I20240919 15:54:57.983773 8189 camera_fxtof1.cpp:226] Chosen mode: near
I20240919 15:54:57.983930 8189 camera_fxtof1.cpp:239] Camera range for mode: near is 250 mm and 800 mm
I20240919 15:54:57.984032 8189 camera_fxtof1.cpp:250] Found firmware for mode: near
I20240919 15:54:57.984077 8189 camera_fxtof1.cpp:253] Firmware size: 14404 bytes
I20240919 15:54:57.984107 8189 addi9036_sensor.cpp:527] Programming AFE error errno: 9 error: Bad file descriptor
I20240919 15:54:57.984166 8189 camera_fxtof1.cpp:258] Failed to program AFE

I need some feedback to help me solve this problem.

Tim

Could I use AD-96TOF1-EBZ with Nvidia jetson orin nano?

Ur30 — Thu, 28 Mar 2024 14:06:54 GMT

I have seen there is support for Nvidia jetson nano but I need to be sure I can use the orin nano.

Thanks

ADDI9036 datasheet discrepancy

mocuZ — Sun, 15 Oct 2023 04:38:38 GMT

Hello,

On page 3, Table 1 under General Specifications, the following values for VH power supply voltages are listed: 8.73V (Min); 9.0V (Typ); 9.27V (Max). However, on page 14, Table 15 Pin Functional Descriptions, a different range of power supply voltages for pin K10 is listed: 8V to 15.5V. So, which range of voltages is the correct one? Which range of voltages should I use throughout the circuit design process?

Kind Regards,

Martin Botsov

AD-FXTOF1-EBZ and Jetson Xavier NX set up question

masaok — Fri, 22 Sep 2023 05:39:42 GMT

Dear Sir,

Our customer would like to connect AD-FXTOF1-EBZ to Jetson Xavier NX.

They have a problem with the software setup and ask us some questions about the procedure.

Following the wiki manual below, they set up the software step by step.

https://wiki.analog.com/resources/eval/user-guides/ad-fxtof1-ebz/ug_xavier_nx

Prepare SD card

Download and flash on a SD card the latest image provided from the following link: aditof_sdk#ad-fxtof1-ebz
Download L4T BSP L4T BSP package (Tested release R32.3.1) ---->[#1] [#2]
Extract kernel_src from BSP package
ADI ToF camera driver and devicetree should be taken from aditof_sdk.
Copy paste and replace content of kernel_src folder from L4T BSP with the one downloaded from ADI ToF Repository
Build Kernel and devicetree blob following instructions from Building_the_Kernel_from_Source selecting “CONFIG_VIDEO_ADDI9036” and “CONFIG_EEPROM_AT24” using menuconfig
Copy generated kernel Image and devicetree to SD card

Power on sequence

Plug the SD card into the Nvidia Xavier NX SD card slot
Connect the HDMI cable from the monitor to the Jetson HDMI connector
Connect the 25 pins flex cable between the camera and the interposer
Connect the 15 pons camera cable between the J1 connector of Jetson Xavier NX and the P1 connector of the interposer. Make sure to use the cable with contacts on opposite sides.

Please let me ask you about the following questions.

[#1] Tested release is R32.3.1, but there's no Jetson Xavier NX version in R32.3.1. Which release should be used for Jetson Xavier NX?

[#2] There's two BSP files, Driver Package (BSP) and Driver Package (BSP) Sources. Which BSP should we use?

If any other points we need to care for setup, please let me know.

Your kind advise would be appreciated.

Regards,

Koide

Linux Source code of NXP IMX8 SOM

HYKS — Tue, 29 Aug 2023 05:08:08 GMT

Hello,

I am using and evaluating EVAL-ADTD3175D-NXZ.

I would like to get the Linux source code for the NXP IMX8 SOM and customize it.
Could you please kind let me know how to get the Linux source code?

Best regards,

H.Kashima

How to calibrate the ToF sensor on EVAL-ADTF3175D-NXZ?

HYKS — Tue, 29 Aug 2023 04:57:22 GMT

Hello,

I want to evaluate EVAL-ADF3175D-NXZ in a specific environment and with some specific objects.
Therefore, I would like to calibrate the ToF sensor on my EVAL-ADTF3175D-NXZ by myself.

Could you please kind let me khow How to calibrate the ToF sensor on EVAL-ADF3175D-NXZ?

Best regards,

H.Kashima

Cannot identify /dev/video0errno: 2error: No such file or directory

mocuZ — Tue, 08 Aug 2023 07:39:28 GMT

Hello,

So, here's the setup. We have custom platform that basically copies the AD-96TOF1-EBZ board but a couple of minor changes: smaller size; single laser diode; proprietary laser diode driver circuit. We have successfully loaded the latest Raspberry Pi SD card image as well as implemented the Raspberry Pi Build instructions as described on GitHub. We have, or at least I hope so, successfully compiled and installed the Tools. The goal is to write a firmware located in /aditof_sdk/misc/ad-96tof1-ebz via eeprom-tool to the memory.

Scanning the I2C bus returns the following:

pi@raspberrypi:~ $ lsmod | grep i2c
regmap_i2c 16384 2 at24,addi9036
i2c_mux_pinctrl 16384 0
i2c_mux 16384 1 i2c_mux_pinctrl
i2c_bcm2835 16384 0
i2c_dev 20480 0

pi@raspberrypi:~ $ i2cdetect -l
i2c-1 i2c bcm2835 (i2c@7e804000) I2C adapter
i2c-11 i2c bcm2835 (i2c@7e205000) I2C adapter
i2c-0 i2c i2c-11-mux (chan_id 0) I2C adapter
i2c-10 i2c i2c-11-mux (chan_id 1) I2C adapter

pi@raspberrypi:~ $ i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- 38 -- -- -- -- -- -- --
40: -- -- -- -- -- 45 -- -- -- -- -- -- -- -- 4e --
50: -- -- -- -- -- -- 56 57 -- -- -- -- -- -- -- --
60: -- -- -- -- 64 -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- 76 --

When we try to write to the memory, the following happens:

pi@raspberrypi:~/workspace/github/aditof_sdk/build/tools/eeprom-tool $ ./eeprom-tool -m -w /workspace/github/aditof_sdk/misc/ad-96tof1-ebz/ad96tof1_eeprom.bin
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0808 10:38:14.983278 5165 eeprom_tool.cpp:89] Setting connection via ON_TARGET
I0808 10:38:14.983879 5165 sensor_enumerator_raspberrypi.cpp:53] Looking for sensors on the target: Raspberry PI
I0808 10:38:14.985337 5165 addi9036_sensor.cpp:155] Opening device
I0808 10:38:14.985611 5165 addi9036_sensor.cpp:173] Looking for the following cards:
I0808 10:38:14.985694 5165 addi9036_sensor.cpp:175] unicam
W0808 10:38:14.985895 5165 addi9036_sensor.cpp:191] Cannot identify /dev/video0errno: 2error: No such file or directory
W0808 10:38:14.986016 5165 eeprom_tool.cpp:144] Failed to open depth sensor
E0808 10:38:14.986196 5165 main.cpp:76] Cannot set connection
I0808 10:38:14.986259 5165 eeprom_tool.cpp:269] Destroyed connection
W0808 10:38:14.986449 5165 addi9036_sensor.cpp:137] close m_implData->fd error errno: 9 error: Bad file descriptor
W0808 10:38:14.986522 5165 addi9036_sensor.cpp:143] close m_implData->sfd error errno: 9 error: Bad file descriptor

Any feedback would be highly appreciated.

Martin

Is there an OEM version of the AD-FXTOF1-EBZ?

DepthUser — Fri, 30 Jun 2023 08:40:59 GMT

I'm doing some tests with the AD-FXTOF1-EBZ to find out wether it's applicable for a project I'm working on.
The depth camera would be connected to a custom SBC via CSI.
So far it looks promising and the image quality could work for the job.

The AD-FXTOF1-EBZ is an evaluation board / devkit.
So I'm wondering if there is also an OEM version available? (As in, intended for integration in another product, not for evaluation) The overview page makes no mention of such OEM versions.

I thought I'd ask here in case I'm missing something obvious before I contact the sales team.

AD-96TOF1-EBZ cannot connect to windows

xuanlunhuang — Mon, 17 Apr 2023 12:38:14 GMT

Hi, my two sets of AD-96TOF1-EBZ once were able to work on windows, but now they cannot connect to window and some problems occurred. Could anyone help on this?

The software and hareware I use are:

Software: aditof-demo v3.1.0 and latest SD card image

Hareware: AD-96TOF1-EBZ, DragonBoard 410c and win 10/11

Problem 1: The logs shows that it can select among the modes, but when I press the "play", it shows "Failed to get frame from device" and the GUI is stuck there and no reponse. By the way, there is also a message "Failed FindInterface (PIN_CATEGORY_PREVIEW)", what does it mean?

I tried different PCs (win 10 or 11) and different USB ports and cables, the same problem happened. How should I solve this?

Problem 2: On another set of AD-96TOF1-EBZ, I press the S3 button and the LED DS4 cannot light up. I have tried the "Truobleshooting" in Windows User Guide but it did not work. What else should I do to solve this or locate the problem?

We need a laser that measures Linear distance to 50 micron accuracy. Could the team identify a cost effective laser device that can do so?

Coep — Fri, 14 Apr 2023 10:45:14 GMT

We need tof sensor for point cloud detection

compilation v4l-utils

Gabess — Mon, 10 Apr 2023 16:03:14 GMT

Hello,

I need your help: When i try to compile v4l-utils it fails this is the output :

make[3]: Entering directory '/home/sebmenet/Sebastien_Menet/v4l-utils/utils/qv4l2'
  CXX      qv4l2-capture-win-gl.o
capture-win-gl.cpp: In member function ‘virtual void CaptureWinGLEngine::initializeGL()’:
capture-win-gl.cpp:275:15: error: ‘GL_FLAT’ was not declared in this scope
  glShadeModel(GL_FLAT);
               ^~~~~~~
capture-win-gl.cpp:275:15: note: suggested alternative: ‘GL_FLOAT’
  glShadeModel(GL_FLAT);
               ^~~~~~~
               GL_FLOAT
capture-win-gl.cpp:275:2: error: ‘glShadeModel’ was not declared in this scope
  glShadeModel(GL_FLAT);

3D ToF Depth Sensing

Gabess — Thu, 06 Apr 2023 11:38:58 GMT

Hello,

I need your help to forward the compilation of examples samples in aditof_sdk

the lib aditof is already compile without network support.

Regards

sebmenet@sebmenet:~/Sebastien_Menet/aditof_sdk/examples/first-frame/build$ make
[ 50%] Linking CXX executable first-frame
/usr/bin/ld: CMakeFiles/first-frame.dir/main.cpp.o: undefined reference to symbol '_ZN6google10LogMessageC1EPKcii'

Issues running DNN.py on AD-96ToF1-EBZ and DragonBoard 410c

bigSlice — Wed, 05 Apr 2023 02:26:21 GMT

Hello,

I am trying to run the DNN.py example on the AD-96ToF1-EBZ sensor on the DragonBoard 410c.

When in the aditof_sdk/bindings/python/examples/dnn directory, I am trying to run the following command:

python dnn.py --prototxt \pathTo\MobileNetSSD_deploy.prototxt --weights \pathTo\MobileNetSSD_deploy.caffemodel

I tried to replace the "\pathTo" on both to "\linaro@linaro-alip:~/workspace/github/aditof_sdk/bindings/python/examples" and this gave the error:

"error: please give the correct location of the prototxt and caffemodel"

Can you let me know how to properly specify the path to the prototxt and caffemodel?

Depth, Perception & Ranging Technologies > LiDAR Solutions

Gabess — Tue, 04 Apr 2023 15:46:38 GMT

Hello,

I have followed the build instructions in order to compile aditof_sdk on jetson nano platform but compilation fails :

output compilation attached below:

can you help me ?

In file included from /home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:32:0:
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.h:51:17: error: ‘recursive_mutex’ in namespace ‘std’ does not name a type
static std::recursive_mutex m_mutex;
^~~~~~~~~~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:72:1: error: ‘recursive_mutex’ does not name a type
recursive_mutex Network::m_mutex;
^~~~~~~~~~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp: In member function ‘int Network::ServerConnect(const string&)’:
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:168:27: error: ‘recursive_mutex’ is not a member of ‘std’
std::unique_lock<std::recursive_mutex> mlock(m_mutex);
^~~~~~~~~~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:168:27: error: ‘recursive_mutex’ is not a member of ‘std’
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:168:42: error: template argument 1 is invalid
std::unique_lock<std::recursive_mutex> mlock(m_mutex);
^
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:168:50: error: ‘m_mutex’ was not declared in this scope
std::unique_lock<std::recursive_mutex> mlock(m_mutex);
^~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp: In member function ‘int Network::SendCommand()’:
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:214:34: warning: ‘int google::protobuf::MessageLite::ByteSize() const’ is deprecated: Please use ByteSizeLong() instead [-Wdeprecated-declarations]
int siz = send_buff.ByteSize();
^
In file included from /usr/local/include/google/protobuf/any.h:38:0,
from /usr/local/include/google/protobuf/generated_message_util.h:53,
from /home/sebmenet/Sebastien_Menet/aditof_sdk/build/sdk/buffer.pb.h:27,
from /home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.h:32,
from /home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:32:
/usr/local/include/google/protobuf/message_lite.h:421:7: note: declared here
int ByteSize() const { return internal::ToIntSize(ByteSizeLong()); }
^~~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:222:31: error: ‘recursive_mutex’ is not a member of ‘std’
std::unique_lock<std::recursive_mutex> mlock(m_mutex);
^~~~~~~~~~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:222:31: error: ‘recursive_mutex’ is not a member of ‘std’
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:222:46: error: template argument 1 is invalid
std::unique_lock<std::recursive_mutex> mlock(m_mutex);
^
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:222:54: error: ‘m_mutex’ was not declared in this scope
std::unique_lock<std::recursive_mutex> mlock(m_mutex);
^~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp: In static member function ‘static int Network::callback_function(lws*, lws_callback_reasons, void*, void*, size_t)’:
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:360:30: error: ‘recursive_mutex’ is not a member of ‘std’
std::lock_guard<std::recursive_mutex> guard(m_mutex);
^~~~~~~~~~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:360:30: error: ‘recursive_mutex’ is not a member of ‘std’
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:360:45: error: template argument 1 is invalid
std::lock_guard<std::recursive_mutex> guard(m_mutex);
^
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:360:53: error: ‘m_mutex’ was not declared in this scope
std::lock_guard<std::recursive_mutex> guard(m_mutex);
^~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:360:47: warning: unused variable ‘guard’ [-Wunused-variable]
std::lock_guard<std::recursive_mutex> guard(m_mutex);
^~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:420:30: error: ‘recursive_mutex’ is not a member of ‘std’
std::lock_guard<std::recursive_mutex> guard(m_mutex);
^~~~~~~~~~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:420:30: error: ‘recursive_mutex’ is not a member of ‘std’
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:420:45: error: template argument 1 is invalid
std::lock_guard<std::recursive_mutex> guard(m_mutex);
^
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:420:53: error: ‘m_mutex’ was not declared in this scope
std::lock_guard<std::recursive_mutex> guard(m_mutex);
^~~~~~~
/home/sebmenet/Sebastien_Menet/aditof_sdk/sdk/src/connections/network/network.cpp:426:38: warning: ‘int google::protobuf::MessageLite::ByteSize() const’ is deprecated: Please use ByteSizeLong() instead [-Wdeprecated-declarations]
int siz = send_buff.ByteSize();

[ 2%] Building CXX object sdk/CMakeFiles/aditof.dir/src/connections/network/network.cpp.o
sdk/CMakeFiles/aditof.dir/build.make:349: recipe for target 'sdk/CMakeFiles/aditof.dir/src/connections/network/network.cpp.o' failed
CMakeFiles/Makefile2:226: recipe for target 'sdk/CMakeFiles/aditof.dir/all' failed
Makefile:135: recipe for target 'all' failed

Depth, Perception & Ranging Technologies > LiDAR Solutions

Gabess — Tue, 04 Apr 2023 15:40:17 GMT

Hello,

I have followed the build instructions in order to compile aditof_sdk on raspberrypi3 platform but compilation fails :

output compilation attached below:

can you help me ?

pi@raspberrypi:/home/Sebastien_Menet/protobuf/build_3_9_0 $ sudo make -j4
[ 15%] Built target libprotobuf-lite
[ 56%] Built target libprotobuf
[ 98%] Built target libprotoc
[ 99%] Linking CXX executable protoc
/usr/bin/ld: libprotobuf.a(arena.cc.o): in function `google::protobuf::internal::ArenaImpl::Init()':
arena.cc:(.text+0x44): undefined reference to `__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/protoc.dir/build.make:98: protoc-3.9.0.0] Error 1
make[1]: *** [CMakeFiles/Makefile2:180: CMakeFiles/protoc.dir/all] Error 2
make: *** [Makefile:128: all] Error 2

Issue:Depth, Perception & Ranging Technologies > LiDAR Solutions

Gabess — Tue, 04 Apr 2023 15:28:05 GMT

Hello,

I have followed the build instructions in order to compile aditof_sdk on jetson platform but compilation fails :

output compilation attached below:

can you help me ?

Aditof_sdk

EngShan — Thu, 30 Mar 2023 13:25:25 GMT

Hey there,

I am trying to set the flags for the bindings on in my SDK but I run into an error of OpenCV_Viz module is missing. This stops any flags that I am trying to set. I have tried reflashing the SD but I still run into the same error. I can't reinstall OpenCV again as the hardware does not have the capability of handling such a large download. Could you give me the steps to figuring this error out?

AD-3DSMARTCAM1-PRZ

ADIApproved — Wed, 22 Mar 2023 15:52:51 GMT

I would like to buy (4) of the AD-3DSMARTCAM1-PRZ. Who has them available for sale? How hard is it to retrofit this using ADTF3175 and ADSD3500 inside with an ethernet port using the GenIcam protocol?

AD-FXTOF1-EBZ

GP2000 — Thu, 16 Mar 2023 20:36:24 GMT

Hello,

Our Goal is to integrate the ToF Module in a Multisensor System.

Critical information like CSI-2 Clock Speed and Register Overview (How to Configure the System) is not findable in the Internet.

Can you provide a full datasheet of the System (or maybe of the ADDI9036 Depth Processor)

Thanks and kind regards

Unable to get DNN.py working using dragonboard 410c and AD-96ToF1-EBZ

bigSlice — Tue, 14 Mar 2023 22:45:31 GMT

Hello, I am using the dragonboard 410c with the AD-96TOF1-EBZ time of flight sensor and want to write the DNN.py example from the ADITOF SDK but keep running into the following error:

File "home/linaro/worksapce/github/aditof_sdk/bindings/python/examples/dnn/dnn.py", Line 32, in <module>

import aditofpython as tof

ModuleNotFoundError: No module named 'aditfopython'

How do I fix this error? All I need to do is get this dnn exmaple running to display object detection for a project. Steps to solve this issue even from the start after flashing a new SD card would be very helpful.

Thank you.

problem with the latest image (AD-FXTOF1-EBZ) on Jetson Nano

smenet — Tue, 07 Mar 2023 10:19:49 GMT

Hello,

i have a problem, i flashed the latest image (AD-FXTOF1-EBZ) for Jetson Nano that i found on your github (https://github.com/analogdevicesinc/aditof_sdk#ad-fxtof1-ebz), but when i use the Jetson Nano, there are some problems with the OS:

1) the google chrome browser doesn't work (but the connection to internet works)

2) i can't install any IDE (for python and for C++)

When i try to install any IDE, i have this message:

Also, when i try to run the exemples for the sensor AD-FXTOF1-EBZ, it tells me that he can't find the the files or directory(but i checked, the library is present in the OS)?

I would like some help please?

How to increase performance of AD-FXTOF1-EBZ on Raspberry Pi 3

LukaF — Thu, 02 Mar 2023 15:23:25 GMT

I am working on a Raspberry Pi 3 model B v1.2 and i'm using the FXTOF1 camera to publish the depth images on a ros topic, I am using the latest sd card image and the Melodic ROS distribution. I followed all the installation guides on the official repository and I have built the opencv and ros packages too. Earlier I had problems with the source original ros camera_node so I replaced it with my own code (below) and it's working just as intended.

I'd like to eventually use this setup with a turtlebot to navigate the environment but the ROS node publishes with a frequency of 6Hz which isn't exactly a lot; is the low frequency normal on a raspberry? Is there any way to increase the performance wihout changing the setup? Keep in mind that I will use the pointcloud to navigate and I still have to figure out a method that can convert the depth matrix to a point cloud.

I have already tried to resize the frame and it did boost the frequency from 4Hz to 6Hz but i think I messed up the numbers because the frames are warped. If you need any further information just ask.

Sorry in advance but I am a student and new to robotics

#include <aditof/camera.h>
#include <aditof/depth_sensor_interface.h>
#include <aditof/frame.h>
#include <aditof/system.h>
#ifndef JS_BINDINGS
#include <glog/logging.h>
#else
#include <aditof/log_cout.h>
#endif

#include <opencv2/highgui/highgui.hpp>
#include <opencv2/imgproc/imgproc.hpp>
#ifdef OPENCV2
#include <opencv2/contrib/contrib.hpp>
#endif

#include "../../../opencv/aditof_opencv.h"

//added ros lib
#include <ros/ros.h>
#include <image_transport/image_transport.h>
#include <cv_bridge/cv_bridge.h>
#include <iostream>

using namespace aditof;

int main(int argc, char *argv[]) {

#ifndef JS_BINDINGS
google::InitGoogleLogging(argv[0]);
FLAGS_alsologtostderr = 1;
#endif

Status status = Status::OK;

System system;

std::vector<std::shared_ptr<Camera>> cameras;
system.getCameraList(cameras);
if (cameras.empty()) {
LOG(WARNING) << "No cameras found!";
return 0;
}

auto camera = cameras.front();
status = camera->initialize();
if (status != Status::OK) {
LOG(ERROR) << "Could not initialize camera!";
return 0;
}

std::vector<std::string> frameTypes;
camera->getAvailableFrameTypes(frameTypes);
if (frameTypes.empty()) {
LOG(ERROR) << "No frame type available!";
return 0;
}

status = camera->setFrameType(frameTypes.front());
if (status != Status::OK) {
LOG(ERROR) << "Could not set camera frame type!";
return 0;
}

std::vector<std::string> modes;
camera->getAvailableModes(modes);
if (modes.empty()) {
LOG(ERROR) << "No camera modes available!";
return 0;
}

status = camera->setMode(modes[0]);
if (status != Status::OK) {
LOG(ERROR) << "Could not set camera mode!";
return 0;
}

aditof::CameraDetails cameraDetails;
camera->getDetails(cameraDetails);
int cameraRange = cameraDetails.depthParameters.maxDepth;
aditof::Frame frame;

aditof::FrameDetails myframe;

const int smallSignalThreshold = 50;
camera->setControl("noise_reduction_threshold",
std::to_string(smallSignalThreshold));

//cv::namedWindow("Display Image", cv::WINDOW_AUTOSIZE);

//added ros init
ros::init(argc, argv, "image_publisher");
ros::NodeHandle nh;
image_transport::ImageTransport it(nh);
image_transport::Publisher pub = it.advertise("camera/image", 1);
ros::Rate loop_rate(30);

while (nh.ok()) {
/* Request frame from camera */
status = camera->requestFrame(&frame);
if (status != Status::OK) {
LOG(ERROR) << "Could not request frame!";
return 0;
}

//frame resizing
status = frame.setDetails(myframe = (FrameDetails) {
400, // width
300, // heigth
400, // The width of the actual full frame
300, // heigth.2 vedi sopra
400, // rgbwidth
300, // rgbheigth
});
if (status != Status::OK) {
std::cout << "My error frame resizing";
return 0;
}

/* Convert from frame to depth mat */
cv::Mat mat;
status = fromFrameToDepthMat(frame, mat);
if (status != Status::OK) {
LOG(ERROR) << "Could not convert from frame to mat!";
return 0;
}

/* Distance factor */
double distance_scale = 255.0 / cameraRange;

/* Convert from raw values to values that opencv can understand */
mat.convertTo(mat, CV_8U, distance_scale);

/* Apply a rainbow color map to the mat to better visualize the
* depth data */
applyColorMap(mat, mat, cv::COLORMAP_RAINBOW);

sensor_msgs::ImagePtr msg = cv_bridge::CvImage(std_msgs::Header(), "bgr8", mat).toImageMsg();
pub.publish(msg);
ros::spinOnce();
loop_rate.sleep();

}

return 0;

}

AD-96TOF1-EBZ faild to connect to windows PC and could not run on Dragonboard 410c.

POTATOO — Thu, 23 Feb 2023 11:59:50 GMT

I am using the AD96 TOF board with Dragonboard 410c.

After the DragonBoard boots up, i followed the course to press the S3 button on the camera board. But the DS4 LED did not light up and the USB carmera driver has not been loaded on the computer.

Then i used the linux system built into the dragon board. When i run aditof-demo.sh, the program flashed back, and the following error report is displayed before flashing back.

I used it normally a few months ago, but these errors occurred recently.