The Digimode Software settings set up integration (or communication) between KComm and Fldigi. This allows you to use KComm as a front-end for Fldigi. You can use KComm's DATA mode button to select the mode in use, and use the transmit and receive panels to send and receive text, logging contacts directly in KComm. By positioning the two windows so that Fldigi's waterfall appears below the bottom of the KComm window, and then keeping KComm on top, you get the benefit of Fldigi's support for multiple digital modes while retaining the convenience of using KComm for logging.
These settings set up the integration between KComm and Fldigi.
- Enable Fldigi integration - this tells KComm communicate with Fldigi when it is running.
- Keep on top - this tells KComm to keep itself in front of the Fldigi window.
- Path to Fldigi - here you must enter the path to the Fldigi program. You can use the Browse (...) button to locate it.
Fldigi normally requires access to the serial port in order to set and get the frequency from the K2 or K3 - as does KComm. It is not normally possible for two programs to access a serial port at the same time under Windows.
It is possible to use Fldigi without giving it access to the serial port. In this case it will only display audio frequencies instead of RF frequencies along the top of its waterfall and some functionality such as the QSY button (to move a received signal to the "sweet spot") will be disabled. TX/RX switching will be handled in software by KComm.
Alternatively you can set up Fldigi to control the radio and run KComm disconnected. KComm will get some information such as frequency and TX/RX status from Fldigi. Some KComm functionality (such as shortcuts or the ability to display aspects of the radio's status) will not be available.
To allow both programs to have simultaneous access to the serial port to control your K2 or K3, you must install the Eterlogic Virtual Serial Port Emulator. This is a freeware tool that lets you create various virtual devices. Use it to create a splitter in which the real serial port is the one connected to your transceiver. Then configure KComm and Fldigi to connect to the virtual serial port instead.