w1hkj w1hkj-Bdlq13kUjeyLZ21kGMrzwg@public.gmane.org [linuxham]
2014-07-02 13:21:58 UTC
I've been asked many times what I use for testing and operations. My
development LAN currently supports:
* Mint-13, Acer, dual E2180 (Intel) processor - development system
* Mint-13, HP Compaq 7600, dual Pentium 4 @ 3 GHz - test system
* Mint-13, Compaq Presario C700 notebook, Intel Pentium
* Mini-mac, 1.25 GHz PowerPC G4, 10.4.11, build/test machine
* Mini-mac, Intel 2.66 GHz Intel Core 2 Duo - test and *primary
operating position*
* Windows XP, Lenovo netbook, 1.6 GHz Atom processor - test system,
dual boots to
* Lubuntu 14
* Windows 8.1, Gateway desktop - test system
All of the computers correctly interface and control one of three
transceivers using flrig or kcat:
* Yaesu FT-950, flrig
* Tentec Pegasus, flrig
* Kachina KC505DSP, kcat
The FT-950 is the one that I use most often. CAT control is via flrig,
either a h/w serial port or a USB-serial dongle depending on machine.
The audio interface is either a SignaLink-USB or a Rig Blaster Advantage
bot of which are easily moved between machines.
My log is on the development Linux (Mint-13) computer. I run fllog on
it so that I can use a single log independent of which computer I am
testing on. I've never experienced a problem with the "connect to
server" tcpip interface.
I am also testing a version of flrig that is able of connecting to a
remote transceiver using a tcpip raw socket connection. The target
socket can be on the LAN or WAN. It's been successfully tested with
both software and hardware serial<->socket interface solutions. I've
been able to control an Icom 7000 transceiver located at Folly Beach,
S.C. from my home in Toney, AL. That connection was to a h/w
interface. I use a software serial<->socket interface to test on the
LAN. Any of the machines on my LAN can then connect to the transceiver
which is usually connected to the Compaq 7600. Both socat and pyserial
software solutions have worked equally well.
If you were testing the socket connection to fllog during field day you
might want to check to be sure that the cause of fldigi's crash was not
due to RFI. I do not experience any issues with either the fllog or
flrig tcpip connections.
73, Dave, W1HKJ
development LAN currently supports:
* Mint-13, Acer, dual E2180 (Intel) processor - development system
* Mint-13, HP Compaq 7600, dual Pentium 4 @ 3 GHz - test system
* Mint-13, Compaq Presario C700 notebook, Intel Pentium
* Mini-mac, 1.25 GHz PowerPC G4, 10.4.11, build/test machine
* Mini-mac, Intel 2.66 GHz Intel Core 2 Duo - test and *primary
operating position*
* Windows XP, Lenovo netbook, 1.6 GHz Atom processor - test system,
dual boots to
* Lubuntu 14
* Windows 8.1, Gateway desktop - test system
All of the computers correctly interface and control one of three
transceivers using flrig or kcat:
* Yaesu FT-950, flrig
* Tentec Pegasus, flrig
* Kachina KC505DSP, kcat
The FT-950 is the one that I use most often. CAT control is via flrig,
either a h/w serial port or a USB-serial dongle depending on machine.
The audio interface is either a SignaLink-USB or a Rig Blaster Advantage
bot of which are easily moved between machines.
My log is on the development Linux (Mint-13) computer. I run fllog on
it so that I can use a single log independent of which computer I am
testing on. I've never experienced a problem with the "connect to
server" tcpip interface.
I am also testing a version of flrig that is able of connecting to a
remote transceiver using a tcpip raw socket connection. The target
socket can be on the LAN or WAN. It's been successfully tested with
both software and hardware serial<->socket interface solutions. I've
been able to control an Icom 7000 transceiver located at Folly Beach,
S.C. from my home in Toney, AL. That connection was to a h/w
interface. I use a software serial<->socket interface to test on the
LAN. Any of the machines on my LAN can then connect to the transceiver
which is usually connected to the Compaq 7600. Both socat and pyserial
software solutions have worked equally well.
If you were testing the socket connection to fllog during field day you
might want to check to be sure that the cause of fldigi's crash was not
due to RFI. I do not experience any issues with either the fllog or
flrig tcpip connections.
73, Dave, W1HKJ