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
Explanation #9
Comments
Hey, which particular angle are you referring to? Have you seen this: |
Yeah, I mean the first formular. I get my measured time in ns, so I divide it by 1000. But I always get a negative angle between -1.2 and -1.3°. |
Negative angle in general is fine; it just means that the sensor is to the left of center line (if it's a horizontal sweep). What is the range of timings you get? Maybe the problem is in the timing module or the unit conversion? The formula itself should be quite simple: |
Here is a OneDrive link to the data I get. I fear that the code I use to get the time intervals is wrong. https://1drv.ms/u/s!At2vyt_CVX2WlwpsfbrrJKduDgek
I'll write a new code today with another methode to get the timings. Also I forgot to mention, that currently I'm only using one Lighthouse Box,, since I only have one avaliable, but I was thinking, that the pulses and timings would be the same except for the timings of the second box. |
Yeah the timings seem wrong. Too much variation. Be sure to calculate timing from the beginning of sync pulse to the center of the laser sweep cycle. One more thing - you're getting angle in radians, not degrees. |
Could it be, that it just won't work with only one Lighthouse Box? |
Did you manage to make it work? I'm wondering what the issue was. |
No I'm still struggling. Is it possible that it won't work without a second box? |
Yeah, it won't work with just one box. Two needed for a 3d fix. Are you trying to get it running without a full HTC Vive set? It might be possible to get the angles with two stations, but if you want to get xyz position, then you'll somehow need to get their position and rotation very precisely, which I don't know how to do without the full set. |
Just saw you asked this question a month ago, which I missed, sorry for that! |
Hi Alex, I just saw your first Alpha release. Congratulations! I'll give it a try later this week. The release comment says, "(almost) everything is configurable and users can just upload the .hex file" Is that because we still need to run SteamVR, calibrate the room using Vive's calibration, and copy/paste the matrices to the sensor? |
Thanks All! This is the wrong thread for this conversation, though :) don't
be afraid to create a new issue to discuss it.
As for your question - yes, we need base station geometry from steamvr, but
also how many sensors, objects, what format, where to stream, etc. See
small example in src/settings.cpp.
On Feb 20, 2017 11:05 AM, "Al B" <notifications@github.com> wrote:
Hi Alex, I just saw your first Alpha release. Congratulations! I'll give it
a try later this week.
The release comment says, "*(almost) everything is configurable and users
can just upload the .hex file*"
Is that because we still need to run SteamVR, calibrate the room using
Vive's calibration, and copy/paste the matrices to the sensor?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAmVHdcJLrXob8mwT2C_B-L39wugzhHQks5reeP0gaJpZM4LdbF0>
.
|
Hello, @Bloodline95 Did you determine what was causing your unexpected oscilloscope readings? I'm also getting something similar. I'm using a TS3633-CM1 with one lighthouse (no sync cable), in mode A, and here are my readings: |
Well shoot, the sensor was too close to the lighthouse. We pulled it back to ~3 feet and that fixed it. |
Hi,
I'm currently trying to get it working on a XMC 4500 Relax Kit, because I have to use an Infineon controller for my Bachelor Thesis. My current problem is, that I always get a negative angle between -1.2 and -1.3°.
So could you please explain the formular for the angle. Right now I don't really get all of it completely.
The text was updated successfully, but these errors were encountered: