Skip to content

Clarification about the hardware precision #1

@offchan42

Description

@offchan42

Hi @fughilli , your project is very interesting and we want to reproduce your work!

First, I want to know how precise the hardware needs to be giving.
Please correct any point that I said wrongly.

  1. The hardware should provide the time difference in microseconds for both sweeps in the 60+ FPS.
  2. So it will give numbers between 0 to 8333, for each diode sensor.
  3. If the sensor is put in a fixed place, the time difference should not be more wrong than 10 microseconds.
  4. If the sensor is put in a fixed place, the angle cannot be wrong more than a degree, or even a half of degree because the ray requires the angle to be very precise on both vertical sweep and horizontal sweep.
  5. We can compute the ray on non-filtered angles and the error would not be large enough to cause bigger than a centimeter error on the position prediction.

And also, here are some questions:

  1. What is the (rough) error of your time difference when a sensor is on a fixed place?
  2. What is the (rough) error of your angle when a sensor is on a fixed place?
  3. When you say you got around 1mm error, is this before or after filtering?
  4. If it's after filtering, what is your error without filtering? (I want to know it so that I can know whether or not my implementation is close to correct)
  5. What is the minimum and maximum time and angle? (I've checked the case when the time is 8333, the angle will be 90 degrees, if time is 0, the angle will be 0 degrees. But I'm not sure how do I get to -90 degrees then?)

If you have any suggestions or concerns, please let me know!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions