diff options
| author | krakenrf <78108016+krakenrf@users.noreply.github.com> | 2022-09-13 16:40:54 +0200 |
|---|---|---|
| committer | krakenrf <78108016+krakenrf@users.noreply.github.com> | 2022-09-13 16:40:54 +0200 |
| commit | 14153f0c4f2f4e67f5d05f4d78c5fb5c53627655 (patch) | |
| tree | 6171622ea4507eea48f7ee8db42c1762940ba553 /07.-KrakenSDR-Troubleshooting.md | |
| parent | Updated 11. KerberosSDR Setup for KrakenSDR Software (markdown) (diff) | |
| download | krakensdr_docs.wiki-14153f0c4f2f4e67f5d05f4d78c5fb5c53627655.tar krakensdr_docs.wiki-14153f0c4f2f4e67f5d05f4d78c5fb5c53627655.tar.gz krakensdr_docs.wiki-14153f0c4f2f4e67f5d05f4d78c5fb5c53627655.tar.bz2 krakensdr_docs.wiki-14153f0c4f2f4e67f5d05f4d78c5fb5c53627655.tar.lz krakensdr_docs.wiki-14153f0c4f2f4e67f5d05f4d78c5fb5c53627655.tar.xz krakensdr_docs.wiki-14153f0c4f2f4e67f5d05f4d78c5fb5c53627655.tar.zst krakensdr_docs.wiki-14153f0c4f2f4e67f5d05f4d78c5fb5c53627655.zip | |
Diffstat (limited to '07.-KrakenSDR-Troubleshooting.md')
| -rw-r--r-- | 07.-KrakenSDR-Troubleshooting.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/07.-KrakenSDR-Troubleshooting.md b/07.-KrakenSDR-Troubleshooting.md index b38adf5..07a9009 100644 --- a/07.-KrakenSDR-Troubleshooting.md +++ b/07.-KrakenSDR-Troubleshooting.md @@ -11,6 +11,15 @@ This is most likely due to a poor power connection to the KrakenSDR. Ensure that #### The KrakenSDR graphs are updating very slowly, or the UI is slow It could be that your Pi 4 overheating and throttling the CPU, or insufficiently powered and also throttling. +#### Connection and sync status remain red in the Web GUI +This indicates that the Kraken isn't connecting to the software correctly. + +The first most likely cause of that is a poor quality or low current power supply being used with the KrakenSDR. KrakenSDR draws up to 2.2A, so a 2.4A or better 5V power supply is required. If a 1A or 2A power supply is used the unit will be unable to power up when the software requests it to start. + +The second most likely cause is booting the Pi or running the software without the Kraken plugged in and powered up. The Kraken must be powered and connected before booting the Pi. + +The third most likely cause is a poor quality USB data cable. + ## General Troubleshooting Tips ### Check Channel Power Levels |