-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Intel Realsense: Time is out of Dual 32-bit range #1284
Comments
@doronhi the RealSense ROS wrapper developer investigated this error on a previous occasion and concluded that it may not be related to RealSense. A few approaches to resolving the problem are suggested in the link below. For example, a RealSense user with a Pi 4 commented that their solution was to switch from Raspbian Buster to RPI4-Ubuntu 18.04 and use a stable power connection. |
We can't replace the operating system because of the problem with the realsense sensor . @MartyG-RealSense I looked at the code and found "enable sync=true," and the error disappeared.
The variable frame_time is too large to cause an error |
Can you confirm whether you still have problems, please? Thanks! |
There are still mistakes. |
It is difficult to advise on a solution if the source of the problem is outside of RealSense. Other than doing a fresh rebuild or changing OS, another suggestion made was to check whether the system clock is correct. Can you check the clock on your Pi please and see if the time and date are correct? |
Case closed due to no further comments received. |
We are trying to get the Intel Realsense D435i to work on our RaspberryPi4 with the Raspbian OS and ROS Melodic.
After we configured our Raspberry Pi with Raspbian and installed ROS Melodic on it, we installed the realsense-ros package on our Raspberry Pi. When we connect our Realsense camera to the Raspberry and run the following command:
$ roslaunch realsense2_camera rs_camera.launch
We get the following error: error: Time is out of Dual 32-bit range
Is there anybody who has any ideas?
The text was updated successfully, but these errors were encountered: