-
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
T265: Problems saving maps with static nodes on t265_direct branch #5394
Comments
Here a small collection of consecutive runs of
|
Even if it works, it is decorated with a couple of disturbing warnings :)
At runtime every second this warning appears:
|
o Avoid pruning the map near static nodes o Avoid starting upside down in rare cases (fixes fly-aways during initialization) o Fix/allow map preservatiom when there is was no previous map to preserve IntelRealSense#5394
@neilyoung I pushed a few changes to #5213 that apply to this (e.g. 724c7e1) and for convenience I added #5426 to that branch also (which I believe will solve #5401). Let us know if that solves your issue, and feel free to close any you think are solved. |
@bfulkers-i Thanks. I have cloned a fresh copy of the repo, switched to development and applied #5213. Then #5426 . While doing the latter I got an error:
Would you mind to share, how to recover from this? TIA |
@bfulkers-i OK, that looks very promising. First 10-15 runs no problems. I will continue to test. EDIT: OK, freeze this version. Runs good. I will close this issue and maybe some other's too I opened in conjunction to this. |
@bfulkers-i Just one thing, which does still not work: You can't successfully save a map w/o making a pause between EDIT: Hmm, right now even the wait is no guarantee, that it will work. The common error message is:
|
@neilyoung thanks for the reminder, pull and try again, I added 467c621 which I believe fixes that (no wait required). |
@bfulkers-i Thanks. Will do later the day and report |
@bfulkers-i Doesn't except anymore, but doesn't save either :)
Result:
Result with wait:
|
@bfulkers-i I thought the 0 bytes would be explainable because I didn't move much with my first tests, so I omitted the timeout again and walked a little bit longer (20s). Same result. W/o making a pause after stop the map is always empty. |
@neilyoung so far I'm unable to reproduce this behavior, can you possibly provide more code to show exactly what you are doing? My test is:
|
@bfulkers-i Let me run your code... One second |
I admit your code works fine. I have altered it and added some wireframes of my code and I can stop the entire engine. Mostly if I play a bit with set_static_node. You need to run this at least 3-5 times until the problem comes. Hit 'n' for setting a static node where you are, hit 's' to stop and save the map.
|
@bfulkers-i I never got that "0" bytes again. Really strange, but after a couple of attempts this mostly happens:
|
@bfulkers-i Yepp, now also with "your" code. Note how many attempts it took. And I added some other options, don't know if it makes a diff, so the whole script looks like so now:
Steps to the error:
|
Thanks for the code @neilyoung, I see weird behavior in your example too. We will take a closer look and reply here. |
@bfulkers-i Many thanks. Good luck. Let me know, if you need my assistance |
@neilyoung We are in the process of fixing this map saving bug described above, but it looks like it will require a new version of the firmware. We will aim to update that toward the end of this week. I'm changing the title of this to reflect the new scope of this issue. |
@bfulkers-i Thanks for letting me know. Take your time. |
@bfulkers-i Two attempts with the latest #5213, 64c753b. Script from here #5394 (comment) Result:
Was the 0 byte issue supposed to be fixed with this commit? |
Fixed |
I suspect you just got lucky, @neilyoung. We'll have some fixes soon that should be much more reliable. |
OK, cool. I admit, after my euphoric post there have been the same issues again. But not that often as before. Keen to see the final result. |
Issue Description
Hmm, I already had made my peace with these issues, but today I downloaded a fresh copy of the entire repo, switched to development branch, applied PR #5213, compiled and installed it all again.
It is sometimes hard to launch my T265 from cold boot. Nothing helps: No plug/unplug, no restart. Twice a start of realsense-viewer helped. From that on the things did roll.
Before I got things like this (I have enabled severity console logging in pose.cpp):
After re-plug then continuoulsy:
Only realsense-viewer came to help. After starting the device there, all C and python attempts work. Until the device was powered off by unplugging. Then the same sequence restarted.
I'm sorry, I had a pretty "old" development branch until today and I thought it would have been a good idea to start from scratch. Until today a lot of my USB problems were gone with PR #5213 . I don't currently know, what happened.
The text was updated successfully, but these errors were encountered: