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
54
55
56
57
58
59
|
Setting up gpredict for use with a Yaesu FT-847 radio
As an USB to RS232 interface I bought the converter from "TechnoFix UK",
which can be obtained from e.g. ebay et al.
There might be a problem with your braille kernel driver, so you have
to disable this from loading at system start (to get /dev/ttyUSB?).
Remember to add the user running rigtcl[d] to the dialout group.
My PC is running an actual debian with KDE as desktop environment and
hamlib is the version delivered as distri package (currently
Hamlib 1.2.15.3), because I have been too lazy to compile it by myself.
Another issue I found while testing the threaded version of my gpredict
build: transponder modes, such as FM, LSB, USB etc. have to be set
manual on the radio.
FT-847:
Menu 37 "CAT RATE" -> 57600
rigctld:
/usr/bin/rigctld -m 101 -r /dev/ttyUSB0 -t 4532 -s 57600 --set-conf=stop_bits=2,serial_handshake=None
gpredict:
Edit -> Preferences -> Interfaces -> Add New
Name: YAESUFT-847
Host: 127.0.0.1
Port: 4532
Radio Type: Duplex TRX
PTT status: Read PTT
VFO Up/Down: SUB /\ / MAIN \/
LO Down: <used with downconverter>
LO Up: <used with upconverter>
Signalling: [ ] AOS [ ] LOS
in Radiocontrol widget:
Settings:
1. Device: YAESUFT-847
2. Device: None
Cycle: 2500
Note on Cycle:
You have to chose a value bigger than the communication via RS232 to
the radio takes! This is approximately 300 ms per command, existing of
the command itself and the answer, containing the result. With a
full-duplex radio there are 7 (!) commands executed: 1. [t] get PTT
status, 2. [f] get current VFOA frq, 3. [F {...}] set new VFOA frq,
4. [f] check if new VFOA frq is set, 5. [i] get current SUB frq,
6. [I {...}] set new SUB frq, 7. [i] check if new SUB frq is set. This
results in a cycle-time of approx 2100 ms - add some time to ensure all
commands are transmitted. The idea to enclose the whole communication
into separate threads came up, because socket communication is always
blocking. This also comes up with rotcld! Still some work to do...
One full cycle:
2017-03-02 19:24:18.918677
t f F {...} f i I {...} i
2017-03-02 19:24:21.036607
(to be enhanced...)
Mar. 2017, Patrick Dohmen (DL4PD)
|
