Hi,
we have the Hesai OT128 lidar.
In the Hesai manual, there are only two available profiles 802.1AS Automotive and 802.1AS AUTOSAR.
(Compare it to e.g., xt32m manual)
It is also visible in the LidarUtilities:
The nebula documentation [ link ] states, that the default parameter profile is 1588v2 <- which is not supported by the device
Moreover, there is weird behaviour while selecting other options.
The only valid values are 1588v2, 802.1as and automotive, as it is visible in the error message, when typing in gibberish:
From my inspection, the behavior is as follows :
- Setting
ptp_profile to automotive is the only valid option and results in the selection of 802.1AS AUTOSAR, i.e., when I manually changed the profile in the LidarUtilities to the 802.1AS Automotive and e.g., ptp_domain to something other than in the configuration file, it sets the profile to autosar and changes the domain
- Setting
ptp_profile to 1588v2 or 802.1as does nothing, i.e., it runs with the configuration which was previously set in the GUI, moreover it doesn't even change other parameters (like ptp_domain)
(3. Typing gibberish raises an error, like in the above screenshot)
In conclusion, there are values of the ptp_profile which are not supported by the device and also there is nothing that can be set as the value of ptp_profile that would result in the selection of the 802.1AS Automotive profile.
Hi,
we have the Hesai OT128 lidar.
In the Hesai manual, there are only two available profiles 802.1AS Automotive and 802.1AS AUTOSAR.
(Compare it to e.g., xt32m manual)
It is also visible in the LidarUtilities:
The nebula documentation [ link ] states, that the default parameter profile is 1588v2 <- which is not supported by the device
Moreover, there is weird behaviour while selecting other options.
The only valid values are
1588v2,802.1asandautomotive, as it is visible in the error message, when typing in gibberish:From my inspection, the behavior is as follows :
ptp_profiletoautomotiveis the only valid option and results in the selection of 802.1AS AUTOSAR, i.e., when I manually changed the profile in the LidarUtilities to the 802.1AS Automotive and e.g., ptp_domain to something other than in the configuration file, it sets the profile to autosar and changes the domainptp_profileto1588v2or802.1asdoes nothing, i.e., it runs with the configuration which was previously set in the GUI, moreover it doesn't even change other parameters (likeptp_domain)(3. Typing gibberish raises an error, like in the above screenshot)
In conclusion, there are values of the
ptp_profilewhich are not supported by the device and also there is nothing that can be set as the value ofptp_profilethat would result in the selection of the 802.1AS Automotive profile.