Closed thkfighter closed 9 months ago
I don't think this is an IP address problem.
HTTP ERROR: Empty reply from server
The HTTP request failed. @ptruka ?
I will test it next week with the same device and report back.
我将在下周使用相同的设备对其进行测试并报告。
May I ask if your driver implementation has been successful? Can you share it
hello @thkfighter I just finished testing the driver with this device.
with porting-ros2 branch from April I receive the following output
$ ros2 launch pf_driver r2000.launch.py
[INFO] [launch]: All log files can be found below /home/ubuntu/.ros/log/2023-05-24-10-49-02-945890-ubuntu-4255
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [ros_main-1]: process started with pid [4258]
[INFO] [robot_state_publisher-2]: process started with pid [4260]
[INFO] [rviz2-3]: process started with pid [4262]
[ros_main-1] [INFO] [1684918143.813628118] [ros_main]: device name: R2000
[ros_main-1] [INFO] [1684918143.813741831] [ros_main]: transport_str: udp
[ros_main-1] [INFO] [1684918143.813753302] [ros_main]: scanner_ip: 169.254.0.103
[ros_main-1] [INFO] [1684918143.813761998] [ros_main]: port:
[ros_main-1] [INFO] [1684918143.813770655] [ros_main]: scan_frequency: 731366192
[ros_main-1] [INFO] [1684918143.813781104] [ros_main]: samples_per_scan: 32765
[ros_main-1] [INFO] [1684918143.813790522] [ros_main]: start_angle: -1800000
[ros_main-1] [INFO] [1684918143.813815298] [ros_main]: max_num_points_scan: 0
[ros_main-1] [INFO] [1684918143.813826008] [ros_main]: watchdogtimeout: 60000
[ros_main-1] [INFO] [1684918143.813834765] [ros_main]: watchdog: 1
[ros_main-1] [INFO] [1684918143.813843321] [ros_main]: num_layers: 0
[ros_main-1] [INFO] [1684918143.813851997] [ros_main]: topic: /scan
[ros_main-1] [INFO] [1684918143.813863168] [ros_main]: frame_id: scanner_link
[ros_main-1] [INFO] [1684918143.813872055] [ros_main]: packet_type: C
[ros_main-1] [INFO] [1684918143.813880701] [ros_main]: apply_correction: 0
[ros_main-1] [INFO] [1684918143.813890940] [ros_main]: start_angle: -1800000
[robot_state_publisher-2] Parsing robot urdf xml string.
[robot_state_publisher-2] Link scanner_link had 0 children
[robot_state_publisher-2] [INFO] [1684918143.863500320] [robot_state_publisher]: got segment scanner_link
[robot_state_publisher-2] [INFO] [1684918143.863663415] [robot_state_publisher]: got segment world
[ros_main-1] [INFO] [1684918143.893668535] [ros_main]: Device found: R2000
[ros_main-1] [INFO] [1684918143.928406280] [ros_main]: Device state changed to Initialized
[ros_main-1] [INFO] [1684918143.941994801] [ros_main]: Device state changed to Running
[rviz2-3] [INFO] [1684918144.519794734] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-3] [INFO] [1684918144.519928385] [rviz2]: OpenGl version: 4.6 (GLSL 4.6)
[rviz2-3] [INFO] [1684918144.580298279] [rviz2]: Stereo is NOT SUPPORTED
[rviz2-3] [ERROR] [1684918144.810952971] [rviz2]: PluginlibFactory: The plugin for class 'rviz_common/Time' failed to load. Error: According to the loaded plugin descriptions the class rviz_common/Time with base class type rviz_common::Panel does not exist. Declared types are
[rviz2-3] Parsing robot urdf xml string.
The driver started, but in this version there were problems with the visualization in rviz. However, you can see that the /scan topic is already output:
$ ros2 topic hz /scan
average rate: 9.992
min: 0.099s max: 0.101s std dev: 0.00063s window: 11
To find the issue we need more information:
http://10.0.10.9/cmd/get_parameter
to get all parameters (you can post all of them here to give us a better view)@chenwu-cc: @ipa-hsd made some changes yesterday. Now the driver for R2000 is working together with rViz. First tests are looking good, but it has not been fully tested yet.
@thkfighter closing this issue. If you are still facing the issue, feel free to re-open
I am using
An error occurs, saying "Unable to communicate with device. Please check the IP address". Computer IP: 10.0.10.100 LiDAR IP: 10.0.10.9 Pinging the LiDAR from the computer works.
Console log: