mirror
/
wfview
kopia lustrzana https://gitlab.com/eliggett/wfview
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

Update Programmer's FAQ

master
Elliott Liggett 2020-03-26 22:50:32 +00:00
rodzic de4a8190b2
commit d4d310d372
1 zmienionych plików z 1 dodań i 1 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

2
Programmer's-FAQ.md

@ -26,7 +26,7 @@ I tried! But basically, every existing library I found was not designed to work
**How can you run flrig and fldigi with wfview?**
wfview makes a pseudo terminal device using the commhandler. This happens when the program starts. The pseudo term is generally something like /dev/pts/0, but the number can change if another program is making pseudo terms. wfview always tells you the device number in the console output. (TODO: automatically symmlink the psudo term to something nice like /tmp/rig). Within commhandler, it is easy to disscern if incomming traffic is intended for the pseudo term device or to wfview (each packet has a TO and FROM clearly indicated). However, we cheat a little here -- all packets received get parsed into wfview, because, why not. Any packet from the pseudo terminal client gets sent to the serial port. To make this work, first configure flrig to connect to the pseudo terminal device, and then launch fldigi and tell it to use flrig for the radio interface. In practice this works pretty well except for the following issues:
wfview makes a pseudo terminal device using the commhandler. This happens when the program starts. The pseudo term is generally something like /dev/pts/0, but the number can change if another program is making pseudo terms. wfview always tells you the device number in the console output. (Note, wfview automatically symmlinks the psudo term to /tmp/rig on startup). Within commhandler, it is easy to disscern if incomming traffic is intended for the pseudo term device or to wfview (each packet has a TO and FROM clearly indicated). However, we cheat a little here -- all packets received get parsed into wfview, because, why not. Any packet from the pseudo terminal client gets sent to the serial port. To make this work, first configure flrig to connect to the pseudo terminal device, and then launch fldigi and tell it to use flrig for the radio interface. In practice this works pretty well except for the following issues:
1. Most if not all client programs will reject device names like /dev/pts/0. Thus I have to write them into the preference files (~/.flrig/IC-7300.prefs) and be careful not to touch those
2. On the Raspberry Pi, last I checked, it seemed like sometimes client programs couldn't latch to the pseudo terminal device reliably. More work to be done there. Foruntately, fldigi isn't that great on a pi...
3. There is an issue where, if the client program is closed, the pseudo term remains locked or something, and new programs can't attach. If you know how to fix this, please tell me!