Skip to content
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

Time is out of dual 32-bit range when using PandarQT #10

Closed
alperk-cvml opened this issue Jul 6, 2020 · 1 comment
Closed

Time is out of dual 32-bit range when using PandarQT #10

alperk-cvml opened this issue Jul 6, 2020 · 1 comment

Comments

@alperk-cvml
Copy link

Time is out of dual 32-bit range when using PandarQT

I captured successfully with Pandar 40P however I'm receiving an exception when using PandarQT LIDAR.

roslaunch hesai_lidar hesai_lidar.launch lidar_type:="PandarQT" 
    started roslaunch server http://developmentenv:34601/

SUMMARY
========

PARAMETERS
 * /hesai_lidar/gps_port: 10110
 * /hesai_lidar/lidar_correction_file: /home/...
 * /hesai_lidar/lidar_recv_port: 2368
 * /hesai_lidar/lidar_type: PandarQT
 * /hesai_lidar/pcldata_type: 0
 * /hesai_lidar/server_ip: 192.168.2.201
 * /hesai_lidar/start_angle: 0.0
 * /rosdistro: melodic
 * /rosversion: 1.14.6

NODES
  /
    hesai_lidar (hesai_lidar/hesai_lidar_node)

ROS_MASTER_URI=http://developmentenv:11311/

process[hesai_lidar-1]: started with pid [11672]
TCP Command Client Init Success!!!
Parse Lidar Correction...
Parse Lidar Correction Success!!!
terminate called after throwing an instance of 'std::runtime_error'
  what():  Time is out of dual 32-bit range

Setup

  • OS: Ubuntu 18.04

  • ROS Version: Melodic

  • Hardware: PandarQT

  • The device is directly connected to the host with an ethernet cable.

  • The difference from Pandar40P is that the time source is selected as PTP in PandarQT, as opposed to GPS in Pandar40P.

What I Tried

  • I created a PTP server on my host device using ptpd and provided a clock source to the PandarQT.
  • In the main page of PandarQT However PTP lock ofset is not very stable.
@alperk-cvml
Copy link
Author

The issue seems to be solved with commit 674d897

tlcommon added a commit to TerraDrone/HesaiLidar_General_ROS_MOD that referenced this issue Sep 6, 2021
ssh接続しなくてもlogrotateの設定を諸々変更できるような機能を追加

<手順>
1. /etc/logrotate.conf のinclude先を/home/ubuntu/uav_logger_ros/logrotate.d   に変更
2. /etc/logrotate.d/logfiles ファイルの中身(logfiles)をmaxsize から size に変更
3.  /etc/logrotate.d を/home/ubuntu/uav_logger_ros/logrotate.dにコピー

他にもいくつかアップデートする項目があるのであれば,関数ではなくクラスで作った方が綺麗かもしれないです.
tlcommon added a commit to TerraDrone/HesaiLidar_General_ROS_MOD that referenced this issue Sep 6, 2021
Merge branch 'feature/issue#10_logrotate_settings' into develop

ログローテーションが正常に行われない問題の解決
→ logrotate設定ファイルの記述修正(maxsize→size)

uav_logger_ros/uav_logger配下に
新たに「os_settings」を追加

このフォルダの中の「model_logrotate.conf」,「logrotate.d」を変更後,exporting_logs内の機能"LOT1_update"を実行すると反映されるようになってます.

反映されているか.正しくローテートされているかの実験ともに済みです.
tlcommon added a commit to TerraDrone/HesaiLidar_General_ROS_MOD that referenced this issue Sep 6, 2021
tlcommon added a commit to TerraDrone/HesaiLidar_General_ROS_MOD that referenced this issue Sep 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant