- #Fldigi rigcat xml files serial#
- #Fldigi rigcat xml files manual#
- #Fldigi rigcat xml files full#
- #Fldigi rigcat xml files pro#
Pity, if as appears the case, we can't make use of this very handy feature. Doesn't explain why it wasn't visible at all with your version though Terry? I appears therefore that 'Hamlib' must be enabled for this feature to work and is the reason why I guess that it's greyed out when LOG4OM is linked with XML-RPC. Very fast and very convenient! If you do not have hamlib enabled for your transceiver this button will be dimmed and not activated. The tranceiver frequency will be shifted and the fldigi audio tracking point shifted in unison such that the signal is now at the receivers sweet spot. Let the AFC capture and then press the QSY button. let's say that I just started copying a rare dx at 1758 Hz and I wanted to put the signal at the sweet spot so I could easily narrow the receiver bandwidth. As the transceivers bandwidth is changed the changes occur centered at this frequency. Each rig has a sweet spot associated with its bandwidth controller. The QSY button is very specific to rigs interfaced with either hamlib or the memory mapped i/o.
#Fldigi rigcat xml files manual#
Terry, FYI, and others following this thread I've just looked at the FLDIGI Users manual (should have done so before my previous post), it confirms what I was saying. So in conclusion its working fine within the constraints of the FLDigi parameters when using the XML-RPC interface with Log4OM, the only issues I found were FLDigi shortcomings and these are beyond our control and not a Log4om issue. But it also might be the case when the width of the main dialog is reduced so that the waterfall display does not extend over the entire available width. This is usually the case when the X2 or X4 expansion is selected.
#Fldigi rigcat xml files full#
NOTE: these controls are only functional if the current waterfall or spectrum view is smaller than the full view available. Then I read the manual for FLDigi and found this note: I found that the "Centre the signal" button on the bottom tool bar did not function with the waterfall set to x1, functioned partially with Waterfall set to x2 and worked perfectly when set to x4 XML-RPC control activated in Fldigi with Hardware PTT, RigCat and Hamlib disabled (Not selected)įLDigi "Sweet Spot" set to CW 700, RTTY 2200 & PSK et al 1500 The new version of Arduino (1.OK I have just checked this out and my set up is as follows I will be using it a lot and improving on it, but of you have any improvements, feel free to drop them in the comments. Obviously, I had to make a custom cable to go from the 8-pin round connector on my rig to the computer’s mic and phone jacks and the Arduino breadboard (well, breadboard for now). Basically, the transistor acts as a solid-state relay.Īs you can see from the sketch, most of the lines are to blink the LED (and this could be done with much fewer lines with two for loops). That allows current to go through the transistor and complete the circuit for the PTT switch.
#Fldigi rigcat xml files serial#
The sketch is really simple as all it does is respond to the correct string from the serial input and turn on the LED and send some voltage to the transistor base. Right click here, and select download or save file from the pop-up contextual menu to download the IC-F8101.xml file. This file has been tested with FLDIGI, using a baud rate of 38400. It will be the same address you use to upload the program to the Arduino. The Icom IC-F8101 RigCAT XML file is intended to provide access to frequency and mode information, as well as to provide support for commanded PTT control. In fldigi, the setup in Configure – Rig control should be like below, but make sure the device is the correct address for the Arduino Uno. This is done by putting the rig.xml file (Arduino.xml) in a good location, such as ~/.fldigi. The first thing to do is setup fldigi to communicate with the rig. It was actually pretty simple, although I did have a little bit of trial-and-error with the rig.xml file. I did this via an Arduino Uno and a transistor and a rig.xml file. While I can easily connect the mic and speaker to the computer, switching the PTT requires something to get a signal via USB (that something can read) and activate the PTT.
#Fldigi rigcat xml files pro#
My problem is that I have a MacBook Pro (no serial port) and an HTX-100 (no computer connectivity whatsoever and no VOX). Or, you need an old computer with a serial port to trigger the push-to-talk (PTT). It seems to me the way things are, the ways to run digital soundcard-based modes involves either a new rig and a new (enough) computer with a USB port.
0 kommentar(er)
