Timeout waiting for camera!

[vtretyakov]

I've been trying for 2 days to bring up the OVP800 unit with a O3R225 camera with no success. I tried following all possible confusing and contradicting instructions, including connecting cameras as described in the Hardware Unboxing, namely 2D cable to Port0, 3D cable to Port2, as well as pairwise as described in other guideline, namely 2D cable to Port0 and 3D cable to Port1.

On the software side I used your compatibility matrix and compiled:
ifm3d v0.91.0 + ifm3d-ros v1.0.0
ifm3d v0.93.0 + ifm3d-ros v1.0.1

The result is the same:

[ INFO] [1667904385.796269644]: Loading nodelet /ifm3d_ros_examples/camera of type ifm3d_ros/camera_nodelet to manager camera_standalone_nodelet with the following remappings:
[ INFO] [1667904385.803766394]: waitForService: Service [/ifm3d_ros_examples/camera_standalone_nodelet/load_nodelet] has not been advertised, waiting...
[ INFO] [1667904385.828006897]: Initializing nodelet with 1 worker threads.
[ INFO] [1667904385.847170178]: waitForService: Service [/ifm3d_ros_examples/camera_standalone_nodelet/load_nodelet] is now available.
[ INFO] [1667904385.867199504]: IP default: 192.168.0.69, current 192.168.0.69
[ INFO] [1667904385.867980863]: pcic port check: current 50010, default 50010
[ INFO] [1667904385.964625342]: Running dtors...
[ INFO] [1667904385.964667762]: Initializing camera...
[ INFO] [1667904386.985657382]: Initializing framegrabber...
[ INFO] [1667904386.987635215]: Nodelet arguments: 16, 50010
[ INFO] [1667904386.988019139]: Initializing image buffer...
[ WARN] [1667904387.489142860]: Timeout waiting for camera!
[ WARN] [1667904387.989997008]: Timeout waiting for camera!
[ WARN] [1667904388.490464163]: Timeout waiting for camera!
[ WARN] [1667904388.991586166]: Timeout waiting for camera!
[ WARN] [1667904389.494529229]: Timeout waiting for camera!
[ WARN] [1667904389.995031032]: Timeout waiting for camera!
[ WARN] [1667904390.495960401]: Timeout waiting for camera!
[ WARN] [1667904390.996422148]: Timeout waiting for camera!
[ WARN] [1667904391.497560812]: Timeout waiting for camera!
[ WARN] [1667904391.998816841]: Timeout waiting for camera!
[ WARN] [1667904391.999247200]: Attempting to restart framegrabber...

Is there a clear path to bring up the unit with ROS to at least see the camera data?

[desengph]

Hi @vtretyakov
can you please double-check that the camera stream you're trying to access is actually in RUN state: http://ifm3d.com/sphinx-doc/build/html/ifm3d/doc/sphinx/content/examples/basic_lib_usage/first_steps_ifm3dpy.html#run-conf-idle

The RUN state is also mirrored in the SOFT-Start helper.

Please let me know if this changes the output. If you have any additional questions, please get in touch.

[vtretyakov]

Hi @desengph
I tried following the guides there. First, configuring the camera as described here. The output looks like that:

{
"euphrates": "1.4.3",
"firmware": "0.14.23-493",
"kernel": "4.9.140-l4t-r32.4+g1582a8a5405d",
"l4t": "r32.4.3",
"schema": "v0.2.4",
"tcu": "1.0.2"
}
RUN
great_o3r

It feels to me like the sate is RUN as required. Trying to read the image as in the link you provided gives still an error:

[ok, frame] = fg.wait_for_frame().wait_for(500)
importlib._bootstrap.Error: Lib: Image chunk not found

The ROS node is dying:

Initializing framegrabber...
terminate called after throwing an instance of 'std::invalid_argument'
what(): stoi
[ifm3d_ros_examples/camera_standalone_nodelet-2] process has died [pid 5433, exit code -6, cmd /opt/ros/noetic/lib/nodelet/nodelet manager __name:=camera_standalone_nodelet

[lola-masson]

Could you please send the full json configuration of your device (the output of o3r.get() with ifm3dpy for instance, or of ifm3d dump from the command line interface). From the snippet that you sent is seems like the "RUN" setting is not applied properly. You should have something like:

    "port2": {
...
      "state": "RUN"
    },

[vtretyakov]

@lola-masson please mind that we are debugging ifm3d-ros! Are there steps to be performed using ROS? Can the ROS node switch the camera into the RUN state or perform required configurations? If not, then when will it be possible?

[lola-masson]

Yes, there is a service that you can use for configuration, see here

[samialperen]

hi @lola-masson, I am having the same error with ifm3d v0.93.0 + ifm3d-ros v1.0.1 configuration (ROS noetic). I upgraded firmware for OVP800 too. The camera I am using is O3R225. Do you have any suggestions?

[lola-masson]

Hi all,

Unfortunately the ROS notes are currently behind in terms of version compatibility, compared to our other packages, which explains some of these headaches especially with newer firmwares. Sorry for the inconvenience.

A good way to verify that the issue is on the side of ROS and not of the O3R is to use the ifm Vision Assistant to check the data streams (you can also use python or c++, but the Vision Assistant provides a convenient GUI). If you all can email [email protected] requesting the Vision Assistant we can send you a link to the latest version. Alternatively, you can go to ifm.com, find the O3D303, go to the download section and download version 2.4.13 from there (it is an older version but should have basic functionalities for the O3R). Once we have identified which side the issues comes from, it will be easier to provide guidance.

[dekhanra]

@vtretyakov
As there have been no recent updates to this GitHub issue, we're closing it.
If you still have questions, please feel free to open a new issue thread.