-
Notifications
You must be signed in to change notification settings - Fork 4.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
RealSense error calling rs2_load_json(dev:05E01D48, json_content:05E7A680, content_size:1539): hr returned: HResult 0x80070079: "信号灯超时时间已到" #7129
Comments
Hi @xiebei The last part of the error translates to "Semaphore timeout period has expired". This is an error that does not typically appear during use of librealsense. It is apparently most commonly encountered when transferring / copying files (for example, to / from an SD card). Since the error message makes specific reference to json loading throughout: if you temporarily remove the line advanced_mode_dev.load_json(preset_json); then that should help to diagnose whether the problem is triggered by the reading of the json file. |
Hi @xiebei Do you require further assistance with this case, please? Thanks! |
@MartyG-RealSense Hi, I did a lot of testing and found that as long as Manual exposure was set, I will get this error. After debugging the realsenese source code, I found that it was an error when setting the gain value. I don't understand what's going on, Now I can only use automatic exposure... |
Hi again @xiebei Are you disabling auto-exposure before you set the manual exposure, please? If auto-exposure is active then the manual values are not updated. A RealSense team member discusses the mechanics of this in more detail in the link below. |
Yes, and I loaded the HighResHighAccuracy.json preset first, and then disabled auto-exposure, set exposure value, set gain value. |
I went back to the start of the case and reviewed all the details so far. It is not impossible that a Windows update in the past two months could have affected the camera, as it has certainly occurred numerous times in the past. Unless you roll back Windows to the last good build that you knew worked (and make updates require user permission to install so camera-breaking updates do not install again automatically), the only remedy in such cases may be to wait til Microsoft release a new build that corrects the problem somehow. Windows build versions may be one reason why a camera works fine on one Windows PC and not another. Other factors such as the USB ports on a particular computer model may also have an effect. Not all ports are built equal, despite USB being a standard. An example would be devices with built-in USB ports that handle two ports on one controller like a hub instead of having a dedicated USB controller for every port. It does not sound as though the hardware of the ports is the problem in this case though, given your past success with it. It is a good idea to divide the cameras across more than one hub like you are doing. A powered hub can supply around 12V to all the devices attached to it, and you should budget for around 2W power for each attached camera. The USB standard allows up to five hubs to be linked together on a single computer. Is using auto-exposure a problem for your project, please? |
Hi @xiebei Do you require further assistance with this case, please? Thanks! |
I didn't solve this problem, I think the power is enough, I decided to use auto exposure now... |
Thanks too for the update! |
Issue Description
I used 2 USB ports to connect 4 D415 cameras via USB hubs, sometimes this error. USB hubs support external power supplies.
It seems to be working well for two months, and I'm not sure if it's because of what I've changed. may be a win10 system update?
RealSense error calling rs2_load_json(dev:05E01D48, json_content:05E7A680, content_size:1539):
hr returned: HResult 0x80070079: "信号灯超时时间已到"
my code like this:
The text was updated successfully, but these errors were encountered: