What to do if Hesai Radar output data can be received by Wireshark but not by PandarView 2?
Ensure that: * If VLAN is enabled, the PC's VLAN ID is the same as the lidar's; this can be checked using web control or PTC commands. * The PC's firewall is disabled, or PandarView 2 is added to the firewall exceptions. * The latest PandarView 2 is installed on the PC. After checking these, power on the lidar again and see if the problem continues.
How to fix Hesai Radar when web control cannot be accessed?
First, ensure that: * The Ethernet cable is properly connected (try unplugging and plugging it again). * The lidar's IP is in the same subnet as the PC's (use WireShark to check the lidar's IP that broadcasts data packets). * If VLAN is enabled, the PC's VLAN ID should match the lidar's; verify this using web control or PTC commands. If the issue persists: 1. Restart your PC or connect the lidar to a different PC. 2. Power cycle the lidar and check if the problem is resolved.
What to do if Hesai Radar motor is running, but no output data is received?
Make sure that: * The Ethernet cable is properly connected (try unplugging and plugging it again). * The Destination IP and Azimuth FOV are correctly set, and the Firmware of Sensor Version is correct; confirm this using web control or PTC commands. * The lidar is emitting laser light; verify this using an infrared camera, an infrared sensor card, or a phone camera without an infrared filter. After these checks, power cycle the lidar and check if the issue persists.
Why is the number of data packets received by Hesai Radar abnormal?
Check the following: * The Azimuth FOV is properly set; confirm this using either web control or PTC commands. * The Spin Rate is steady; confirm using web control, PandarView 2 or PTC commands or by checking the Motor Speed field in the Point Cloud Data Packet. * The lidar's internal temperature is between –20°C and 90°C; confirm using web control, PandarView 2 or PTC commands. * The Ethernet is not overloaded. * No switch is connected to the network (data transmitted from other devices may cause network congestion and packet loss). If problems persist: 1. Connect the PC to only the lidar and check for packet loss. 2. Power cycle the lidar and check if the symptom persists.
How to troubleshoot abnormal point cloud in Hesai Radar?
Verify the following: * The lidar's cover lens is clean. * The lidar's angle correction file is imported. * The Azimuth FOV is properly set; confirm using web control or PTC commands. * The Spin Rate is steady; confirm using web control, PandarView 2 or PTC commands or by checking the Motor Speed field in the Point Cloud Data Packet. * The lidar's internal temperature is between –20°C and 95°C; confirm using web control, PandarView 2 or PTC commands. Next steps: 1. Check for packet loss. 2. If no packet is missing and the point cloud flashes, update PandarView 2 to the latest version, and then restart the PC. If the point cloud is still abnormal: 3. Connect the lidar to another PC and another network. 4. Power cycle the device and see if the issue persists.
Why Hesai Radar GPS cannot be locked?
Make sure that: * The GPS receiver is properly connected. * The PPS signal is connected to the lidar. * The GPS Destination Port is correctly set; this can be confirmed using web control or PTC commands. * The GPS signals satisfy the electrical requirements. After checking, power cycle the lidar and check if the symptom persists.
What to do if Hesai Radar motor is not running?
Ensure that: * The power adapter is properly connected and in good condition. * The input voltage and current meet the requirements. * Web control can be accessed. * The lidar is not in standby mode; this can be confirmed using web control or PTC commands. * If a connection box is used, the connection box is intact. After checking these, power cycle the lidar and see if the problem continues.
How to fix indicator light off on Hesai Radar connection box?
Ensure that: * The power adapter is properly connected and in good condition. * The connection box is intact. * The input voltage and current satisfy the requirements. After checking these, power cycle the lidar again and see if the symptom persists.
What to do if I can receive data on Wireshark but not on PandarView for Hesai Measuring Instruments?
First, ensure the Lidar Destination Port is correctly set on the Settings page of web control. Then, check if your PC's firewall is disabled, or that PandarView is added to the firewall exceptions. If VLAN is enabled, verify the PC's VLAN ID matches the lidar's. Finally, make sure you have installed the latest PandarView version. Power the device on again to check if the issue persists.
How to fix abnormal point cloud on Hesai Measuring Instruments?
Ensure the Lidar's cover lens is clean; if not, clean it. Verify the Lidar's calibration file is imported. Check that the horizontal FOV is properly set on the Azimuth FOV page of web control and the motor's spin rate is steady on the Home page of web control. Confirm the Lidar's internal temperature is between -20° and 95° on the Operation Statistics page of web control. Check for packet loss. If the point cloud flashes, update PandarView to the latest version and restart the PC. If the point cloud is still abnormal, try connecting the lidar to another PC. Power cycle the device to see if the problem continues.
Instructions on how to obtain the latest version of the manual.
Contact information for technical assistance and support.
Explanation of symbols and formatting conventions used in the manual.
Critical safety information and general warnings.
Warning about hot components and handling precautions.
Procedures for identifying and responding to product malfunctions.
Warning against unauthorized disassembly of the product.
Guidelines for safe operation regarding environmental factors.
Precautions related to mechanical vibration and hazardous atmospheric conditions.
Precautions regarding chemical exposure and operating temperature.
Information on IP rating and guidelines for proper storage.
Information on potential interference from external light sources.
Recommended qualifications and responsibilities for operators.
Warnings about electromagnetic interference with medical devices.
Requirements and safety precautions for the power supply.
Critical safety information regarding laser eye protection.
Handling and care instructions for the product's outer casing.
Guidelines for cleaning and protecting the lidar's cover lens.
Procedures for securely mounting the lidar.
Guidelines for selecting and using compatible peripherals.
Instructions for updating the product's firmware and software.
Considerations for using customized software versions.
Overview of available data processing functions.
Strict warnings against and consequences of self-repair.
Explanation of the Time of Flight (ToF) measurement principle.
Information on obtaining the angle correction file for accurate measurements.
Key performance parameters of the lidar sensor.
Physical and operational characteristics of the device.
Details on power usage and data transmission protocols.
Procedures for physically installing the lidar.
Technical drawings and dimensions of the lidar unit.
Covers Quick and Stable Installation procedures.
Guidelines for screw selection, torque, and threadlocker.
Description of the electrical connectors and pinouts.
Detailed pin assignment for the Lemo connector.
Timing requirements for GPS synchronization signals.
Instructions for proper connection, disconnection, and cable bending.
Information regarding the optional connection box.
Description of the different ports available on the connection box.
Pinout details for the lidar's trigger port.
Illustrative guide for connecting the lidar with the connection box.
Configuration of network parameters for data reception.
Overview of available software tools for lidar operation.
Information on software development kits and ROS drivers.
Detailed structure of the point cloud data packet.
Description of the Ethernet header fields within the data packet.
Structure of the UDP data payload for point clouds.
Fields within the header of the point cloud UDP data.
Content and format of the main data body in UDP packets.
Description of the tail section of the UDP data packet.
Structure of the data packet containing GPS information.
Ethernet header details for GPS data packets.
Structure of the UDP data payload for GPS information.
Format specification for GPRMC GPS sentences.
Format specification for GPGGA GPS sentences.
Ethernet tail details for GPS data packets.
Method for analyzing GPS time data.
Description of the main status and device information screen.
Explanation of NMEA and PTP synchronization status indicators.
Explanation of the function of various buttons in the settings interface.
Configuration options for network parameters like IP address and VLAN.
Configuration options for lidar functions like spin rate and return mode.
Settings for synchronizing lidar time with GPS or PTP.
Configuration parameters when using GPS for time synchronization.
Configuration parameters when using PTP for time synchronization.
Settings for Sync Angle and Trigger Method.
Settings for Noise Filtering, Reflectivity Mapping, etc.
Configuration for putting the lidar into standby mode.
Options for selecting the primary time synchronization source.
Settings for PTP synchronization profiles, transport, and domain.
Settings for PTP intervals and network switch type.
Settings for defining the horizontal field of view.
Setting a single FOV range for all lidar channels.
Defining individual FOV ranges for each lidar channel.
Configuring multiple FOV ranges for each lidar channel.
Steps to diagnose and resolve issues with the connection box indicator light.
Troubleshooting steps for when the lidar motor fails to operate.
Procedures for diagnosing issues with data reception.
Troubleshooting data reception discrepancies between tools.
Steps to resolve issues when web control cannot be accessed.
Diagnosing missing or abnormal data packets.
Troubleshooting misaligned or incomplete point cloud data.
Steps to resolve issues with the GPS signal not locking.
Using GPS signals for precise time synchronization.
Using PTP protocol for precise time synchronization.
Pinout configuration for the Phoenix connector.
General| Type | LiDAR |
|---|---|
| Model | Pandar64 |
| Laser Wavelength | 905 nm |
| Number of Lasers | 64 |
| Channels | 64 |
| Horizontal Field of View | 360° |
| Ingress Protection Rating | IP67 |
| Protection Level | IP67 |
| Interface | Gigabit Ethernet |
| Range | 200 m |
| Detection Range | 200m |
| Accuracy | ±2 cm |
| Vertical Field of View | 40° |
| Frame Rate | 20 Hz |
| Data Rate | 100 Mbps |
| Point Cloud Rate | 1, 318, 400 points/sec (10 Hz) |
| Power Supply | 9-32 VDC |
To Next Page
