-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to load nodelet '/acquisition_node of type
acquisition/capture_nodelet to manager
vision_nodelet_manager'
#108
Comments
Tried with rosrun: [ INFO] [1612187576.893107793]: [ OK ] USB memory: 1000 MB |
@dostyaaa One issue I noticed is that |
Thanks for your answer shahvi. Launch file calls the defaut test_params.yaml. cam_ids:
#Assign all the follwing via launch file to prevent confusion and conflict #save_path: ~/projects/data #Camera info message details
#specified as [fx 0 cx 0 fy cy 0 0 1]
rectification_coeffs:
projection_coeffs:
Black dots are '-', github automatically changes it. |
I think you have the yaml formatting incorrect. Every space and line break matters. Take a look at the example file. You cam_ids is being read as "-20285628" instead of a list, same for master_cam |
Reading the yaml is done outside the node. Roslaunch reads the yaml file and loads the parameters to the ROS parameter server. Our node reads it from the parameter server. You could check if the file is being read into the ROS parameter server by running rosparam list, you might have to start a separate roscore before running the launch file so that the ros master doesn't close when the node seg faults. |
For anyone else with this issue, the problem seems to have been a change in the ROS API between kinetic and melodic that prevents execution of code within These are used frequently in setting the parameters from A fix can be found in pull request #141 . |
System Description
Camera Name and Model: BFS-U3-28S5C-C
Operating System: Ubuntu 18.04
Spinnaker Version: 2.0.0.147
ROS Version: Melodic 1.14.10
Computer details
Processor: Intel i7-6600u 2.6 GHz
RAM: 16GB
Multiple Cameras Only
How is the triggering setup? Master/Slave or all slaves or all software triggered?
For USB 3.0 cameras:
On same USB 3.0 bus or different buses?
Is the USB 3.0 hub externally powered?
For Ethernet cameras:
How busy is the network, does the system work in grayscale, at a lower resoultion (binning) and framerate?
Do the cameras work with SpinView?
Yes, working perfectly fine
Describe the bug
Built sdk_driver with catkin without problems. Once i tried to launch acquisition.launch got the following error :
[FATAL] [1612185131.933308616]: Failed to load nodelet '/acquisition_node
of type
acquisition/capture_nodeletto manager
vision_nodelet_manager'[vision_nodelet_manager-2] process has died [pid 24036, exit code -11, cmd /opt/ros/melodic/lib/nodelet/nodelet manager __name:=vision_nodelet_manager __log:=ros/log/17e047e4-648f-11eb-863c-a44cc895af49/vision_nodelet_manager-2.log].
log file: ros/log/17e047e4-648f-11eb-863c-a44cc895af49/vision_nodelet_manager-2*.log
[acquisition_node-3] process has died [pid 24038, exit code 255, cmd /opt/ros/melodic/lib/nodelet/nodelet load acquisition/capture_nodelet vision_nodelet_manager __name:=acquisition_node __log:=ros/log/17e047e4-648f-11eb-863c-a44cc895af49/acquisition_node-3.log].
log file: ros/log/17e047e4-648f-11eb-863c-a44cc895af49/acquisition_node-3*.log
Tried both dev and master branch, same problem. Modify cam ids in the yaml file, same problem. Tried to upgrade sdk spinnaker but works with Ubuntu 20.04. Running out of ideas...
Error Messages
Full message:
Screenshots
If applicable, add screenshots to help explain your problem.
Best regards !
The text was updated successfully, but these errors were encountered: