docs: rename FAQ to Troubleshooting
This commit is contained in:
@ -2,7 +2,7 @@
|
|||||||
Getting Help
|
Getting Help
|
||||||
============
|
============
|
||||||
|
|
||||||
Before asking for help with HackRF, check to see if your question is answered in this documentation, listed in the :ref:`FAQ <faq>`, or addressed in the `HackRF GitHub repository issues <https://github.com/greatscottgadgets/hackrf/issues>`__.
|
Before asking for help with HackRF, check to see if your question is answered in this documentation, listed in the :ref:`Troubleshooting <troubleshooting>` page, or addressed in the `HackRF GitHub repository issues <https://github.com/greatscottgadgets/hackrf/issues>`__.
|
||||||
|
|
||||||
For assistance with HackRF general use or development, please look at the `issues on the GitHub project <https://github.com/greatscottgadgets/hackrf/issues>`__. This is the preferred place to ask questions so that others may locate the answer to your question in the future.
|
For assistance with HackRF general use or development, please look at the `issues on the GitHub project <https://github.com/greatscottgadgets/hackrf/issues>`__. This is the preferred place to ask questions so that others may locate the answer to your question in the future.
|
||||||
|
|
||||||
|
@ -7,7 +7,7 @@ Welcome to HackRF's documentation!
|
|||||||
:caption: User Documentation
|
:caption: User Documentation
|
||||||
|
|
||||||
getting_help
|
getting_help
|
||||||
faq
|
troubleshooting
|
||||||
synchronization_checklist
|
synchronization_checklist
|
||||||
hackrf_projects_mentions
|
hackrf_projects_mentions
|
||||||
|
|
||||||
|
@ -1,13 +1,13 @@
|
|||||||
.. _faq:
|
.. _troubleshooting:
|
||||||
|
|
||||||
================================================
|
================================================
|
||||||
FAQ
|
Troubleshooting
|
||||||
================================================
|
================================================
|
||||||
|
|
||||||
.. _bigspike:
|
.. _bigspike:
|
||||||
|
|
||||||
What is the big spike in the center of my received spectrum?
|
There is a big spike in the center of the received spectrum
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
If you see a large spike in the center of your FFT display regardless of the frequenecy you are tuned to, you are seeing a DC offset (or component or bias). The term "DC" comes from "Direct Current" in electronics. It is the unchanging aspect of a signal as opposed to the "alternating" part of the signal (AC) that changes over time. Take, for example, the signal represented by the digital sequence:
|
If you see a large spike in the center of your FFT display regardless of the frequenecy you are tuned to, you are seeing a DC offset (or component or bias). The term "DC" comes from "Direct Current" in electronics. It is the unchanging aspect of a signal as opposed to the "alternating" part of the signal (AC) that changes over time. Take, for example, the signal represented by the digital sequence:
|
||||||
|
|
||||||
@ -23,16 +23,10 @@ There was a bug in the HackRF firmware (through release 2013.06.1) that made the
|
|||||||
|
|
||||||
A high DC offset is also one of a few symptoms that can be caused by a software version mismatch. A common problem is that people run an old version of gr-osmosdr with newer firmware.
|
A high DC offset is also one of a few symptoms that can be caused by a software version mismatch. A common problem is that people run an old version of gr-osmosdr with newer firmware.
|
||||||
|
|
||||||
|
Solution
|
||||||
|
--------
|
||||||
|
|
||||||
|
There are a few options:
|
||||||
----
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
How do I deal with the big spike in the middle of my spectrum?
|
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
||||||
|
|
||||||
Start by reading :ref:`our FAQ Response on the DC Spike <bigspike>`. After that, there are a few options:
|
|
||||||
|
|
||||||
#. Ignore it. For many applications it isn't a problem. You'll learn to ignore it.
|
#. Ignore it. For many applications it isn't a problem. You'll learn to ignore it.
|
||||||
|
|
Reference in New Issue
Block a user