forked from g4eml/Langstone
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathDebugging Notes.txt
More file actions
53 lines (22 loc) · 1.53 KB
/
Copy pathDebugging Notes.txt
File metadata and controls
53 lines (22 loc) · 1.53 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
If the transceiver does not start up correctly then please try the following.
Log into the Pi using ssh the same way that you did to build the software.
Type 'ps -ax' to get a list of the running programs.
You should be able to find the two programs needed in the list. They will be called home/pi/Langstone/SSB-TRX.py and home/pi/Langstone/GUI
If the transceiver is not running then one of these will probably be missing.
Make a note of the Process ID for either or both of the programs and then kill them using the command
'kill -9 nnn' where nnn is the process ID noted above.
Repeat this to kill both programs.
Try ps -ax again to make sure both programs have been killed
try starting the GNURadio Program manually
cd ~/Langstone
python SSB_TRX.py &
You should see a couple of INFO lines about the Audio Source and Audio Sync and a line len(audio_taps) = 213
The LED on your USB Audio Dongle should start flashing
Any other error messages should give a clue as to what is wrong.
If this works then start the GUI with the command
./GUI &
The LCD Screen should come to life and the transceiver should be working.
You should not see any error messages.
ps -ax again should now show both programs running.
You may see occasional aU characters printed on your ssh screen. This is normal and indicates an occasional audio overrun condition.
This seems to be a bug in GNU radio on the Pi and does not affect operation if they are only happening occasionally.