Unable to receive frames from Femto Mega after firmware update. #28
Comments
Suedocode
changed the title
|
I confirmed that streaming works with firmware 1.2.7, running the same code with different sensors that hadn't been upgraded yet. There's something incompatible with firmware 1.3.0 and femto mega. |
|
Thank you for your testing and feedback! Could you confirm whether your network bandwidth is gigabit or megabit? (You can check the bandwidth rate in the 'Show Frame Metadata' section of OrbbecViewer.) From the logs, the stream appears to be normal. The reason for not being able to fetch frames from the pipeline might be due to the simultaneous activation of |
|
Both tested systems use the same hardware and ethernet cables, and they are gigabit. I disabled From OrbbecViewer, the depth frames show 88.72Mbps and color frames are 14.18Mbps |
|
1.2.7 and 1.2.9 work,1.3.0 does not. All tested on the same hardware configuration. |
|
Hello! If possible, could you please use firmware version 1.3.0 with the following two configurations and provide a debug-level log? I only encountered this issue at a 100Mbps network speed, not at 1000Mbps, so your feedback would be extremely helpful in addressing this problem. // Configuration 1
mConfig->setFrameAggregateOutputMode(OB_FRAME_AGGREGATE_OUTPUT_ANY_SITUATION);
mPipeline->enableFrameSync();
// Configuration 2
mConfig->setFrameAggregateOutputMode(OB_FRAME_AGGREGATE_OUTPUT_ALL_TYPE_FRAME_REQUIRE);
mPipeline->enableFrameSync();
mPipeline->start(mConfig);
while(true) {
auto frameSet = mPipeline->waitForFrameset(1000);
if (frameSet) { // checck if the frameset has depth and color frames }
} |
|
Output format: Configuration 1 (C1): Configuration 2 (C2): In C2, there's no test output. The Orbbec log commenst about fps don't appear in C1, presumably because it ends too soon after receiving 20 frames. As a side note, the time stamps on color and depth frames in C1 are oddly out-of-sync. I don't expect them to be the same, but I expected them to at least be chronological. |
|
Hello, thank you for your cooperation! I noticed that there is an anomaly in the Color timestamp, and the log output you provided is also different. If you are using the SDK with the tag v2.0.24-rc, the log output related to FPS should include the device name and device SN, like this: When the Mega device uses firmware version v1.3.0 and the color stream is set to an RGB-related format, the issue you encountered may occur. This problem has already been fixed in version v2.0.23. Could you please confirm the version number of the SDK you are using? The confirmation method is as follows:
ob::Context::setLoggerSeverity(OB_LOG_SEVERITY_DEBUG);
In the next version, the SDK version number will be embedded in the .so library name to enhance convenience. |
Updated Femto Mega firmware to v1.2.9 -> v1.3.0 and our sample can no longer stream from them. OrbbecViewer (v1.10.16) can successfully pull frames though, and I'm not sure what the difference is. Here's the code we're using:
Here's the output, with extra stuff removed:
For some reason, the frames are not getting put into the frameset callback. Similarly,
waitForFramestimes out in the same way, and never produces a valid frameset.Here is the relevant directory structure:
Environment:
Ubuntu 22.04.5 LTS (x86_64)
g++ 11.4.0
OrbbecSDK_v2 51c2902 (tagged v2.0.24-rc)
Femto: Firmware v1.3.0
The text was updated successfully, but these errors were encountered: