开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Guide to New Rig backend creation?

 

Thanks David.

I was looking in the makefile.am file in the project's root director, not the src directory!
Hence the confusion...

Thanks again.

73.

??? Dave G0WBX.

--
Created on and sent from a Unix like PC running and using open source software:


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

Yes, the CAT commands can be confusing. I was looking at byte 0 for the filter width, but byte 7 is correct.
?
I changed the code to use names like your code and also fixed the vfo-b modes.
?
I found that flrig was again not setting the vfo-b frequency. The op code was wrong and should be the same as the vfo-a procedure.
In set_vfoB I changed
? ? cmd += 0x8A;
to
? ? cmd += 0x0A; // Not 0x8A, as it is the same as vfo-a
?
I still need to do more testing, but I'm out of time for now.
?
----Steve


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

开云体育

Thanks Steve.? Very confusing CAT commands.

David

On 10/3/24 03:07, Steve, KB5AW wrote:

I tried your changes.
It seems to revert to the incorrect operation before the changes I submitted.
I don't see how your case statement can work for the modes. The only valid numbers in byte 6 are 0, 1, 2, 3, 4.
You use case numbers based on byte 6 ranging from 0 to 7 which correspond to the menu, but doesn't correspond to the data from the rig on byte 6.
For example, CW is 2 whether or not it is wide or narrow. In the menu, the numbers are 2 and 3 respectively.
?
So, I reverted to my version of FT890.cxx which worked for all of the non-narrow modes and added if statements to fix the narrow modes.
vfo-a now works correctly on all modes. Maybe you can do it in a better way or make any corrections.
I did not make the changes for vfo-b.
------------------------
? ? ? ? switch (replystr[6] & 0x07) {
? ? ? ? ? ? case 0: A.imode = ((replystr[6] & 0x40) == 0x40) ? 1 : 0; break; // LSB
? ? ? ? ? ? case 1: A.imode = ((replystr[6] & 0x40) == 0x40) ? 3 : 1; break; // USB
? ? ? ? ? ? case 2: A.imode = ((replystr[6] & 0x80) == 0x80) ? 5 : 2; break; // CW
? ? ? ? ? ? case 3: A.imode = ((replystr[6] & 0x80) == 0x80) ? 7 : 4; break; // AM
? ? ? ? ? ? case 4: A.imode = ((replystr[6] & 0x80) == 0x80) ? 9 : 6; break; // FM
? ? ? ? ? ? default: A.imode = 0;
? ? ? ? }
?
// After the base mode has been determined, we need to check for the narrow filters.
// We need to verify the base mode, as the narrow mode bits remain on until changed.
?
? ? ? ? if (((replystr[8] & 0x80) == 0x80) && (A.imode == 2)) {
? ? ? ? ? ? A.imode = 3; // CW-N
? ? ? ? }
? ? ? ? if (((replystr[8] & 0x40) == 0x40) && (A.imode == 4)) {
? ? ? ? ? ? A.imode = 5; // AM-N
? ? ? ? }
------------------------


Re: Guide to New Rig backend creation?

 

开云体育

Dave,

Look at src/Makefile.am

# Sources that we build. It is OK to have headers here.
flrig_SOURCES += \
??????? rigs/rigbase.cxx \
??????? rigs/rigs.cxx \
??????? rigs/elad/FDMDUO.cxx \
??????? rigs/elecraft/K2.cxx \
??????? rigs/elecraft/K3.cxx \
??????? rigs/elecraft/KX3.cxx \
??????? rigs/elecraft/K4.cxx \
??????? rigs/icom/ICbase.cxx \
...

David

On 10/2/24 12:01, Dave, G?WBX via groups.io wrote:

Hi again.

Looking into this now.? But...

These steps mentioned by Dave 'HKJ...

How to add a new transceiver to flrig

(A)
? Two new files will need to be added:
??? . src/include/RIGFAMILY/NEWRIG.h
??? . src/rigs/RIGFAMILY/NEWRIG.cxx
Done OK.? (Blank for now...)


(B)
? Three files will need to be modified:
??? . Makefile.am
?????? add the references to the two new files
Unable to even find references to any existing rig files, so at a loss what to add here.


(C)
??? . src/include/rigs.h
??? . src/rigs/rigs.cxx
?????? add the references to the new rig
Done, referencing the new rig's files created as the first step(A)


? RIGFAMILY might be icom, yaesu, elad, etc.
? NEWRIG might be IC-9999, FT-9999, etc.
Understood, but see above.

Suggest using an existing rig (.cxx, .h) files as a template for
the new rig.? Choose a file that will use similar CAT commands.

After the new files have been added and the three files updated
you will need to recreate the build scripts.? From the top level
flrig directory:

? $ autoreconf
? $ ./configure
? $ make

David


What exactly do I add to makefile.am?? As above, there is nothing there I can see, that references other rig files in an obvious way.

All that is in there at present, is :-

ACLOCAL_AMFLAGS = -I m4
SUBDIRS = src

if DARWIN
appbundle:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif

if HAVE_NSIS
nsisinst:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif

#EXTRA_DIST = build-aux/config.rpath


That to me, looks more like what platform to build for, not what sources to build from..

Or (again) have I missed something?


73.

Dave G0WBX.



-- 
Created on and sent from a Unix like PC running and using open source software:


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

I tried your changes.
It seems to revert to the incorrect operation before the changes I submitted.
I don't see how your case statement can work for the modes. The only valid numbers in byte 6 are 0, 1, 2, 3, 4.
You use case numbers based on byte 6 ranging from 0 to 7 which correspond to the menu, but doesn't correspond to the data from the rig on byte 6.
For example, CW is 2 whether or not it is wide or narrow. In the menu, the numbers are 2 and 3 respectively.
?
So, I reverted to my version of FT890.cxx which worked for all of the non-narrow modes and added if statements to fix the narrow modes.
vfo-a now works correctly on all modes. Maybe you can do it in a better way or make any corrections.
I did not make the changes for vfo-b.
------------------------
? ? ? ? switch (replystr[6] & 0x07) {
? ? ? ? ? ? case 0: A.imode = ((replystr[6] & 0x40) == 0x40) ? 1 : 0; break; // LSB
? ? ? ? ? ? case 1: A.imode = ((replystr[6] & 0x40) == 0x40) ? 3 : 1; break; // USB
? ? ? ? ? ? case 2: A.imode = ((replystr[6] & 0x80) == 0x80) ? 5 : 2; break; // CW
? ? ? ? ? ? case 3: A.imode = ((replystr[6] & 0x80) == 0x80) ? 7 : 4; break; // AM
? ? ? ? ? ? case 4: A.imode = ((replystr[6] & 0x80) == 0x80) ? 9 : 6; break; // FM
? ? ? ? ? ? default: A.imode = 0;
? ? ? ? }
?
// After the base mode has been determined, we need to check for the narrow filters.
// We need to verify the base mode, as the narrow mode bits remain on until changed.
?
? ? ? ? if (((replystr[8] & 0x80) == 0x80) && (A.imode == 2)) {
? ? ? ? ? ? A.imode = 3; // CW-N
? ? ? ? }
? ? ? ? if (((replystr[8] & 0x40) == 0x40) && (A.imode == 4)) {
? ? ? ? ? ? A.imode = 5; // AM-N
? ? ? ? }
------------------------


Re: Guide to New Rig backend creation?

 

开云体育

Hi again.

Looking into this now.? But...

These steps mentioned by Dave 'HKJ...

How to add a new transceiver to flrig

(A)
? Two new files will need to be added:
??? . src/include/RIGFAMILY/NEWRIG.h
??? . src/rigs/RIGFAMILY/NEWRIG.cxx
Done OK.? (Blank for now...)


(B)
? Three files will need to be modified:
??? . Makefile.am
?????? add the references to the two new files
Unable to even find references to any existing rig files, so at a loss what to add here.


(C)
??? . src/include/rigs.h
??? . src/rigs/rigs.cxx
?????? add the references to the new rig
Done, referencing the new rig's files created as the first step(A)


? RIGFAMILY might be icom, yaesu, elad, etc.
? NEWRIG might be IC-9999, FT-9999, etc.
Understood, but see above.

Suggest using an existing rig (.cxx, .h) files as a template for
the new rig.? Choose a file that will use similar CAT commands.

After the new files have been added and the three files updated
you will need to recreate the build scripts.? From the top level
flrig directory:

? $ autoreconf
? $ ./configure
? $ make

David


What exactly do I add to makefile.am?? As above, there is nothing there I can see, that references other rig files in an obvious way.

All that is in there at present, is :-

ACLOCAL_AMFLAGS = -I m4
SUBDIRS = src

if DARWIN
appbundle:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif

if HAVE_NSIS
nsisinst:
?? ?(cd src && $(MAKE) $(AM_MAKEFLAGS) $@)
endif

#EXTRA_DIST = build-aux/config.rpath


That to me, looks more like what platform to build for, not what sources to build from..

Or (again) have I missed something?


73.

Dave G0WBX.



-- 
Created on and sent from a Unix like PC running and using open source software:


Andy's Ham Radio Linux: v26b-beta has been RELEASED!

 

Hi Everybody,

There has been a LOT of interest in these most recent versions of AHRL.? Thank you for your support!

v26b-beta is out.? I've added a bunch of programs for the ARRL Teachers Institute, including their own menu.? Those programs also appear in other menus as appropriate.? Many of those programs are SDR related.? They work for me but please try them and let me know.

I've tested this on several flavors of Ubuntu Linux 24.04.1 as well as Debian 12.7.0 (XFCE) and Linux Mint 22 (Cinnamon).

WORKAROUND: for some reason, the audio occasionally gets into a state where only the Dummy Output appears.? I've seen a LOT of postings about this for various flavors of Ubuntu Linux.? I'm pretty confident that this is not specific to AHRL.? If this happens, I've created a script to workaround the issue.? /usr/local/bin/fix_sound OR look in the Workarounds menu.? If somebody finds a definitive fix, please let me know.

Here's the link:

Don't forget to read the GETTING_STARTED document.? :-)

Have fun and 73,
Andy
KB1OIQ ..


Re: FLRIG with Windows, Linux and the MAC

 

PS:-

Forgot to say...

Flrig 2.0.05.75, built from source on LMDE 6.? (Linux Mint Debian Edition.)
Controlling a Kenwood TS-870s via a "Prolific 2303" chipset USB<>Serial device running at 57600bd.

A Udev rule is configured, so that device reliably shows up to Flrig etc, as /dev/ttyTS870.

Also using DTR for PTT so the radio takes Fldigi (or other digimode) TX audio via the rear ACC port.
RTS/CTS handshaking is in use, as "is required" by the Kenwood.

73.

Dave G0WBX.

--
Created on and sent from a Unix like PC running and using open source software:


Re: FLRIG with Windows, Linux and the MAC

 

Using a Kenwood TS-870s and Flrig (also the .75 alpha)

I find that the BW filter LF cutoff setting is always reset to 300Hz whenever the high cutoff setting is changed.
It's not the rig, you can manually at the rig's front panel flip between LSB/USB without the filters being reset.
Also one can manually change either the High Cut, or Low Cut setting without affecting the other.

The LF setting is also replaced with the HF setting, after changing the LF setting in the Flrig UI.

Not noticed any unwanted working frequency changes, but the above is when just using Flrig ONLY (without Fldigi running & linked to it.)

I've not dug into that yet, but there are one or two other "odd" anomalies I've noticed.? I'll have to start gathering info as I find them.

As I had a part to play in that rig backend, I'll dig deeper as time permits. But I've a lot of other non radio stuff "on my plate" at present.

73

Dave G0WBX.



--
Created on and sent from a Unix like PC running and using open source software:


Re: FLRIG with Windows, Linux and the MAC

 

No one else is having this problem?
?
--
-----------------------------------
73/Rick
W4XA
Western? Wa


Re: flrig 2.0.05.75 alpha release

 

Hi Dave and team
?
I have been a long time and happy user of FLrig. Thank you.
?
Probably due to a combination of a recent change in my operating interests and updating to alpha version 2.0.05.75 I am encountering some bugs. Or are they features?!
?
  • 700 Hz frequency offset automatically inserted when changing modes away from USB/LSB. Annoying!
  • DNR button renamed to "NB" after first use. Rig under control is an Yaesu FT-891. Cosmetic issue.
  • When changing sideband's FLrig issues a command to turn off the narrow filter and change the bandwidth to 2800 Hz. Can this be turned off or made optional?
  • When FLrig has been running for a time it changes the mode to USB + 2800hz bw whenever the frequency is changed via FLrig or VFO knob. Restarting FLrig returns normal operations but within a few minutes the unwanted changing to USB is back.
  • FLrig sometimes not reporting the correct BW, mode, volume etc
?
Trace log below of a QSY down 1 KHz demonstrating the LSB to USB unwanted switch along with a BW change from 1150 Hz to 2800 Hz. Second part of log demonstrates the 700 Hz offset when changing mode from USB to AM. Third part is normal QSY without unwanted mode and bandwidth change.
?
73 Denis

QSY down 1KHz (abnormal operation)
19:01:36.403 : get split() S: ?ST; ?R: ?ST0;
19:01:36.406 : get_vfoA()
19:01:36.457 : ?S: ?FA; ?R: ?FA007180000;
19:01:36.457 : get_PTT()
19:01:36.507 : ?S: ?TX; ?R: ?TX0;
19:01:36.508 : read_vfo()
19:01:36.508 : vfoA active get vfo A
19:01:36.508 : get_vfoA()
19:01:36.558 : ?S: ?FA; ?R: ?FA007180000;
19:01:36.559 : vfoA active get vfo B
19:01:36.559 : get_vfoB()
19:01:36.609 : ?S: ?FB; ?R: ?FB014241000;
19:01:36.610 : read_bandwidth()
19:01:36.610 : get_bwA()
19:01:36.660 : ?S: ?SH0; ?R: ?SH0110;
19:01:36.661 : get_bwA(): 9
19:01:36.661 : read_volume()
19:01:36.661 : get_volume_control()
19:01:36.711 : ?S: ?AG0; ?R: ?AG0089;
19:01:37.212 : get_PTT()
19:01:37.262 : ?S: ?TX; ?R: ?TX0;
19:01:37.262 : read_smeter()
19:01:37.263 : get_smeter()
19:01:37.313 : ?S: ?SM0; ?R: ?SM0034;
19:01:37.313 : read_mode vfoA active
19:01:37.314 : get_modeA()
19:01:37.364 : ?S: ?MD0; ?R: ?MD01;
19:01:37.365 : get_sideband()
19:01:37.415 : ?S: ?EX1107; ?R: ?EX11071;
19:01:37.415 : read: 0
19:01:37.415 : read_auto_notch()
19:01:37.415 : get auto notch
19:01:37.466 : ?S: ?BC0; ?R: ?BC00;
19:01:37.523 : get split() S: ?ST; ?R: ?ST0;
19:01:37.529 : get_vfoA()
19:01:37.579 : ?S: ?FA; ?R: ?FA007180000;
19:01:37.663 : set_vfoA
19:01:37.713 : ?S: ?FA007179000; ?R: ?
19:01:37.966 : get_PTT()
19:01:38.017 : ?S: ?TX; ?R: ?TX0;
19:01:38.017 : read_vfo()
19:01:38.017 : vfoA active get vfo A
19:01:38.017 : get_vfoA()
19:01:38.068 : ?S: ?FA; ?R: ?FA007179000;
19:01:38.068 : vfoA active get vfo B
19:01:38.068 : get_vfoB()
19:01:38.119 : ?S: ?FB; ?R: ?FB014241000;
19:01:38.119 : read_bandwidth()
19:01:38.119 : get_bwA()
19:01:38.169 : ?S: ?SH0; ?R: ?SH0110;
19:01:38.170 : get_bwA(): 9
19:01:38.170 : read_notch()
19:01:38.170 : get_notch ON/OFF
19:01:38.220 : ?S: ?BP00; ?R: ?BP00000;
19:01:38.402 : get split() S: ?ST; ?R: ?ST0;
19:01:38.407 : get_vfoA()
19:01:38.457 : ?S: ?FA; ?R: ?FA007179000;
19:01:38.476 : set_vfoA
19:01:38.527 : ?S: ?FA007179000; ?R: ?
19:01:38.538 : set_modeA()
19:01:38.588 : ?S: ?MD02; ?R: ?
19:01:38.588 : set_sideband()
19:01:38.638 : ?S: ?EX11070; ?R: ?
19:01:38.638 : set_bwA()
19:01:38.689 : ?S: ?NA00;SH0118; ?R: ?
19:01:38.693 : set_vfoA
19:01:38.743 : ?S: ?FA007179000; ?R: ?
19:01:38.744 : get_PTT()
19:01:38.794 : ?S: ?TX; ?R: ?TX0;
19:01:38.794 : read_smeter()
19:01:38.794 : get_smeter()
19:01:38.845 : ?S: ?SM0; ?R: ?SM0034;
19:01:38.845 : read_mode vfoA active
19:01:38.845 : get_modeA()
19:01:38.895 : ?S: ?MD0; ?R: ?MD02;
19:01:38.895 : get_sideband()
19:01:38.946 : ?S: ?EX1107; ?R: ?EX11070;
19:01:38.946 : read: 1
19:01:38.946 : read_if_shift()
19:01:38.947 : get_if_shift()
19:01:38.997 : ?S: ?IS0; ?R: ?IS00+0000;
19:01:39.404 : get split() S: ?ST; ?R: ?ST0;
19:01:39.410 : get_vfoA()
19:01:39.460 : ?S: ?FA; ?R: ?FA007179000;
?
Mode change to AM
19:03:13.404 : get split() S: ?ST; ?R: ?ST0;
19:03:13.409 : get_vfoA()
19:03:13.460 : ?S: ?FA; ?R: ?FA007179000;
19:03:13.484 : get_PTT()
19:03:13.534 : ?S: ?TX; ?R: ?TX0;
19:03:13.535 : read_vfo()
19:03:13.535 : vfoA active get vfo A
19:03:13.535 : get_vfoA()
19:03:13.586 : ?S: ?FA; ?R: ?FA007179000;
19:03:13.586 : vfoA active get vfo B
19:03:13.586 : get_vfoB()
19:03:13.637 : ?S: ?FB; ?R: ?FB014241000;
19:03:13.637 : read_bandwidth()
19:03:13.637 : get_bwA()
19:03:13.688 : ?S: ?SH0; ?R: ?SH0118;
19:03:13.688 : get_bwA(): 17
19:03:13.688 : read_rfgain
19:03:13.688 : get_rf_gain()
19:03:13.738 : ?S: ?RG0; ?R: ?RG0030;
19:03:14.239 : get_PTT()
19:03:14.289 : ?S: ?TX; ?R: ?TX0;
19:03:14.289 : read_smeter()
19:03:14.289 : get_smeter()
19:03:14.339 : ?S: ?SM0; ?R: ?SM0002;
19:03:14.339 : read_mode vfoA active
19:03:14.339 : get_modeA()
19:03:14.389 : ?S: ?MD0; ?R: ?MD02;
19:03:14.390 : get_sideband()
19:03:14.440 : ?S: ?EX1107; ?R: ?EX11070;
19:03:14.440 : read: 1
19:03:14.490 : get split() S: ?ST; ?R: ?ST0;
19:03:14.490 : read_split() OFF
19:03:14.544 : get split() S: ?ST; ?R: ?ST0;
19:03:14.547 : get_vfoA()
19:03:14.597 : ?S: ?FA; ?R: ?FA007179000;
19:03:14.991 : get_PTT()
19:03:15.042 : ?S: ?TX; ?R: ?TX0;
19:03:15.042 : read_vfo()
19:03:15.042 : vfoA active get vfo A
19:03:15.042 : get_vfoA()
19:03:15.092 : ?S: ?FA; ?R: ?FA007179000;
19:03:15.093 : vfoA active get vfo B
19:03:15.093 : get_vfoB()
19:03:15.143 : ?S: ?FB; ?R: ?FB014241000;
19:03:15.144 : read_bandwidth()
19:03:15.144 : get_bwA()
19:03:15.194 : ?S: ?SH0; ?R: ?SH0118;
19:03:15.194 : get_bwA(): 17
19:03:15.194 : read_nr()
19:03:15.195 : get_noise_reduction()
19:03:15.245 : ?S: ?NB0; ?R: ?NB01;
19:03:15.245 : get_noise_reduction_val()
19:03:15.296 : ?S: ?NL0; ?R: ?NL0001;
19:03:15.403 : get split() S: ?ST; ?R: ?ST0;
19:03:15.410 : get_vfoA()
19:03:15.461 : ?S: ?FA; ?R: ?FA007179000;
19:03:15.796 : get_PTT()
19:03:15.846 : ?S: ?TX; ?R: ?TX0;
19:03:15.846 : read_smeter()
19:03:15.846 : get_smeter()
19:03:15.897 : ?S: ?SM0; ?R: ?SM0006;
19:03:15.897 : read_mode vfoA active
19:03:15.897 : get_modeA()
19:03:15.948 : ?S: ?MD0; ?R: ?MD02;
19:03:15.948 : get_sideband()
19:03:15.999 : ?S: ?EX1107; ?R: ?EX11070;
19:03:15.999 : read: 1
19:03:15.999 : read_noise()
19:03:15.999 : get_noise()
19:03:16.050 : ?S: ?NR0; ?R: ?NR00;
19:03:16.050 : get_nb_level()
19:03:16.101 : ?S: ?RL0; ?R: ?RL009;
19:03:16.403 : get split() S: ?ST; ?R: ?ST0;
19:03:16.408 : get_vfoA()
19:03:16.458 : ?S: ?FA; ?R: ?FA007179000;
19:03:16.601 : get_PTT()
19:03:16.651 : ?S: ?TX; ?R: ?TX0;
19:03:16.651 : read_vfo()
19:03:16.652 : vfoA active get vfo A
19:03:16.652 : get_vfoA()
19:03:16.703 : ?S: ?FA; ?R: ?FA007179000;
19:03:16.703 : vfoA active get vfo B
19:03:16.703 : get_vfoB()
19:03:16.753 : ?S: ?FB; ?R: ?FB014241000;
19:03:16.754 : read_bandwidth()
19:03:16.754 : get_bwA()
19:03:16.804 : ?S: ?SH0; ?R: ?SH0118;
19:03:16.805 : get_bwA(): 17
19:03:16.805 : read_compression()
19:03:16.805 : get_compression()
19:03:16.855 : ?S: ?PL; ?R: ?PL025;
19:03:16.855 : get comp level
19:03:16.906 : ?S: ?PR0; ?R: ?PR01;
19:03:16.906 : get_compression: ON(1), comp PL=25
19:03:17.000 : set_modeA()
19:03:17.051 : ?S: ?MD05; ?R: ?
19:03:17.051 : set_sideband()
19:03:17.051 : ?S: ?MD05; ?R: ?
19:03:17.404 : get split() S: ?ST; ?R: ?ST0;
19:03:17.406 : get_PTT()
19:03:17.456 : ?S: ?TX; ?R: ?TX0;
19:03:17.457 : read_smeter()
19:03:17.457 : get_smeter()
19:03:17.507 : ?S: ?SM0; ?R: ?SM0131;
19:03:17.507 : read_mode vfoA active
19:03:17.508 : get_modeA()
19:03:17.558 : ?S: ?MD0; ?R: ?MD05;
19:03:17.558 : read: 4
19:03:17.558 : get_vfoA()
19:03:17.609 : ?S: ?FA; ?R: ?FA007179700;
19:03:17.637 : set_vfoA
19:03:17.688 : ?S: ?FA007179700; ?R: ?
19:03:17.703 : set_modeA()
19:03:17.753 : ?S: ?MD02; ?R: ?
19:03:17.753 : set_sideband()
19:03:17.804 : ?S: ?EX11070; ?R: ?
19:03:17.804 : set_bwA()
19:03:17.854 : ?S: ?NA00;SH0118; ?R: ?
19:03:17.857 : set_vfoA
19:03:17.908 : ?S: ?FA007179700; ?R: ?
19:03:18.060 : get_PTT()
19:03:18.110 : ?S: ?TX; ?R: ?TX0;
19:03:18.110 : read_vfo()
19:03:18.110 : vfoA active get vfo A
19:03:18.111 : get_vfoA()
19:03:18.161 : ?S: ?FA; ?R: ?FA007179700;
19:03:18.161 : vfoA active get vfo B
19:03:18.162 : get_vfoB()
19:03:18.212 : ?S: ?FB; ?R: ?FB014241000;
19:03:18.212 : read_bandwidth()
19:03:18.212 : get_bwA()
19:03:18.263 : ?S: ?SH0; ?R: ?SH0118;
19:03:18.263 : get_bwA(): 17
19:03:18.401 : get split() S: ?ST; ?R: ?ST0;
19:03:18.763 : get_PTT()
19:03:18.814 : ?S: ?TX; ?R: ?TX0;
19:03:18.814 : read_smeter()
19:03:18.814 : get_smeter()
19:03:18.864 : ?S: ?SM0; ?R: ?SM0032;
19:03:18.864 : read_mode vfoA active
19:03:18.864 : get_modeA()
19:03:18.915 : ?S: ?MD0; ?R: ?MD02;
19:03:18.915 : get_sideband()
?
QSY down 1KHz after FLrig restart (Normal operation)
?
19:45:14.020 : ?S: ?SM0; ?R: ?SM0140;
19:45:14.020 : read_mode vfoA active
19:45:14.020 : get_modeA()
19:45:14.071 : ?S: ?MD0; ?R: ?MD01;
19:45:14.073 : get_sideband()
19:45:14.124 : ?S: ?EX1107; ?R: ?EX11071;
19:45:14.124 : read: 0
19:45:14.124 : read_auto_notch()
19:45:14.124 : get auto notch
19:45:14.175 : ?S: ?BC0; ?R: ?BC00;
19:45:14.676 : get_PTT()
19:45:14.727 : ?S: ?TX; ?R: ?TX0;
19:45:14.727 : read_vfo()
19:45:14.727 : vfoA active get vfo A
19:45:14.727 : get_vfoA()
19:45:14.778 : ?S: ?FA; ?R: ?FA007180000;
19:45:14.778 : vfoA active get vfo B
19:45:14.778 : get_vfoB()
19:45:14.828 : ?S: ?FB; ?R: ?FB014241000;
19:45:14.829 : read_bandwidth()
19:45:14.829 : get_bwA()
19:45:14.879 : ?S: ?SH0; ?R: ?SH0110;
19:45:14.879 : get_bwA(): 9
19:45:14.879 : read_notch()
19:45:14.880 : get_notch ON/OFF
19:45:14.930 : ?S: ?BP00; ?R: ?BP00000;
19:45:15.431 : get_PTT()
19:45:15.481 : ?S: ?TX; ?R: ?TX0;
19:45:15.481 : read_smeter()
19:45:15.481 : get_smeter()
19:45:15.532 : ?S: ?SM0; ?R: ?SM0131;
19:45:15.532 : read_mode vfoA active
19:45:15.532 : get_modeA()
19:45:15.582 : ?S: ?MD0; ?R: ?MD01;
19:45:15.583 : get_sideband()
19:45:15.633 : ?S: ?EX1107; ?R: ?EX11071;
19:45:15.633 : read: 0
19:45:15.633 : read_if_shift()
19:45:15.633 : get_if_shift()
19:45:15.683 : ?S: ?IS0; ?R: ?IS00+0000;
19:45:15.684 : set_vfoA
19:45:15.734 : ?S: ?FA007179000; ?R: ?
19:45:16.184 : get_PTT()
19:45:16.234 : ?S: ?TX; ?R: ?TX0;
19:45:16.234 : read_vfo()
19:45:16.235 : vfoA active get vfo A
19:45:16.235 : get_vfoA()
19:45:16.285 : ?S: ?FA; ?R: ?FA007179000;
19:45:16.285 : vfoA active get vfo B
19:45:16.285 : get_vfoB()
19:45:16.336 : ?S: ?FB; ?R: ?FB014241000;
19:45:16.336 : read_bandwidth()
19:45:16.336 : get_bwA()
19:45:16.386 : ?S: ?SH0; ?R: ?SH0110;
19:45:16.386 : get_bwA(): 9
19:45:16.388 : read_power_control()
19:45:16.389 : get_power_control()
19:45:16.439 : ?S: ?PC; ?R: ?PC100;
19:45:16.939 : get_PTT()
19:45:16.989 : ?S: ?TX; ?R: ?TX0;
19:45:16.989 : read_smeter()
19:45:16.990 : get_smeter()
19:45:17.040 : ?S: ?SM0; ?R: ?SM0116;
19:45:17.040 : read_mode vfoA active
19:45:17.041 : get_modeA()
19:45:17.091 : ?S: ?MD0; ?R: ?MD01;
19:45:17.092 : get_sideband()
19:45:17.142 : ?S: ?EX1107; ?R: ?EX11071;
19:45:17.142 : read: 0
19:45:17.142 : read_preamp_att() ?1
19:45:17.142 : get_preamp()
19:45:17.192 : ?S: ?PA0; ?R: ?PA01;
?


CTY-3434 Country Files - 27 September 2024

 

The Country (CTY) Files were updated on 27 September 2024:



For installation instructions, start at:



Hover your mouse over the word Contest in the menu, then select the
software you are using.

To install the file, follow the link to your software at the top of the page.

If you are interested in a bigger CTY.DAT for everyday logging, you can get
it here:



Note that the release notes (and Version Entity) for this larger file are
different than what is shown below. There is a separate link to them.

As a reminder, there is an RSS feed of the latest country file announcements:



Here are the release notes:

27 September 2024 (CTY-3434)
VER20240927, Version entity is East Malaysia, 9M6

Added/changed Entities/Prefixes/Callsigns:

* 9M67M is West Malaysia, 9M2
* 9M67MQ and 9M67MS are both East Malaysia, 9M6
* BG2LTC/0 is China, BY in CQ zone 23
* VP8ADE is Antarctica, CE9 in ITU zone 73
* E51D is North Cook Islands, E5/n in ITU zone 63
* EA6XQ/P and EA9PD are both Spain, EA
* GB2ZL is Scotland, GM
* IK7YTQ/LNX is Italy, I
* IR0ROLB is Sardinia, IS
* KL0S and KL0SS are both United States, K in CQ zone 5, ITU zone 8
* K1JHR is Hawaii, KH6
* R50DSN, R8FF/6 and RA9ULL/6 are all European Russia, UA
* UA9XK/1 is European Russia, UA in ITU zone 19
* RI42SP is European Russia, UA in CQ zone 40
* RV1CC/2 is Kaliningrad, UA2
* RA9WU/P is Asiatic Russia, UA9 in CQ zone 16
* R2CC/0 and RX3AMI/0 are both Asiatic Russia, UA9 in CQ zone 19, ITU zone 34

Removed Entities/Prefixes/Callsigns:

* BD4QB/0 in China, BY
* EA5IYX/6 in Balearic Islands, EA6
* TO973FY in French Guiana, FY
* GB2OWM in Scotland, GM
* GB5VAS in Guernsey, GU
* GB0CAS and GB0ESM in Wales, GW
* IO0C in Sardinia, IS
* KM6RJA and WB4JTT in Hawaii, KH6
* K7WJH, KE0WDR and KG7GSU in Alaska, KL
* LU4ERM/D in Argentina, LU
* R0AD/3/P, R1641AZ, R8FF, RA9WU/P, RI0POL and UB5O/1 in European Russia, UA
* R0FBA/9, R5GA/9, R95MAG, RA/EA8RM/P, RW0CE/9, UA5B/0 and UA9CTT/P
in Asiatic Russia, UA9

Though I am subscribed to this reflector so that I can make these
announcements, I do not see most messages posted to it. If you have
any comments or corrections to the country file, please contact me
directly.

73 - Jim AD1C

--
Jim Reisert AD1C, <jjreisert at alum.mit.edu>,


Re: Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)

 

I had it working once after my rigpi had a corrupted card. If i remember correctly the pi serial 0 device is tied to a login terminal by default. And you have to use the config program to disable the login terminal serial so it will be available for the keyer board to use.


Re: Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)

 

开云体育

No, RigPi uses a K1EL WinKeyer 3 IC.
Steve K1EL?

On Sep 27, 2024, at 8:29?AM, GW0WZL via groups.io <gowzel@...> wrote:

?
I should have added I think it uses the K3NG arduino software on an AVR microcontroller chip


Re: Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)

 

I should have added I think it uses the K3NG arduino software on an AVR microcontroller chip


Anyone got rigpi rigkeyer to work without rigpi software (Winkeyer)

 

I have a rigpi3, but as the software used on it now is so out of date ie wsjtx and the pi os I have set up another sd card with bookworm, and have installed flrig as a radio control and wsjtx 2,70 rc6 flrig jscall etc.
I can use fldigi on all its modes including cw just using the usb cat port on my ftdx3000. But I would like to use the keyer board on the rigpi. It is based on the Winkeyer 3 IC and according to the rigpi manual is on serial port /devttyS0 at 1200 baud, but I have so far failed to get it to work on Fldigi apart from very occasional dits and dahs from the rigpi's speaker which were non reproducable.
Has anyone any idea or better still had it working without rigp os.


Re: #flrig flrig not working with my FT-890 FTDI Programming Cable #flrig

 

开云体育

Steve,

I read through the CAT pages for the FT-890 and I think this is what you want for the mode/width code:

enum {FT_LSB, FT_USB, FT_CWW, FT_CWN, FT_AMW, FT_AMN, FT_FM};

static std::vector<std::string>FT890modes_;
static const char *vFT890modes_[] = {
?? ???? "LSB", "USB", "CW-W", "CW-N", "AM-W", "AM-N", "FM" };
static const int FT890_mode_val[] =? { 0, 1, 2, 3, 4, 5, 6 };

...

?? ???? switch (replystr[6] & 0x07) {
?? ???? ??? case 0: A.imode = FT_LSB; break;
?? ???? ??? case 1: A.imode = FT_USB; break;
?? ???? ??? case 2: case 3: A.imode = ((replystr[8] & 0x80) == 0x80) ? FT_CWN : FT_CWW; break;
?? ???? ??? case 4: case 5: A.imode = ((replystr[8] & 0x40) == 0x40) ? FT_AMN : FT_AMW; break;
?? ???? ??? case 6: case 7: A.imode = FT_FM;
?? ???? }

?? ???? B.iBW = (replystr[9] & 1);
?? ???? B.freq = 10 * ((((replystr[10] & 0xFF) * 256 +
?? ???? ??? ??? ?? (replystr[11] & 0xFF) ) * 256 +
?? ???? ??? ??? ?? (replystr[12] & 0xFF) ) );

?? ???? switch (replystr[15] & 0x07) {
?? ???? ??? default:
?? ???? ??? case 0: B.imode = FT_LSB; break;
?? ???? ??? case 1: B.imode = FT_USB; break;
?? ???? ??? case 2: case 3: B.imode = ((replystr[17] & 0x80) == 0x80) ? FT_CWN : FT_CWW; break;
?? ???? ??? case 4: case 5: B.imode = ((replystr[17] & 0x40) == 0x40) ? FT_AMN : FT_AMW; break;
?? ???? ??? case 6: case 7: B.imode = FT_FM;
?? ???? }





see attached.

David, W1HKJ

On 9/24/24 19:55, Steve, KB5AW wrote:

Thanks for looking at this.
?
Yes, those are the changes that I made.
I don't understand your menu system and all that are in these statements, so you should review approve them.
The changes do not take into consideration the filter bandwidth, so something needs to be done about that. There should be something for CW-N and AM-N. I don't think that FM-N exists.
It all comes from the mode information is different between the reading and writing of it.
?


Re: For all you RTTY / Teletype fans out there..

 

开云体育

I am thankful that the Air Force kept me as a TTY tech. for 20 years, because I had no problem finding a job in my retirement. Msgt Donald Casillo USAF (ret)

On 9/25/24 08:21, Bo, W4GHV wrote:

Interesting bio! I think doing a single specialty for a long time would be great if you loved it. I had 4 in the USAF since they love to shuffle you around about the time you love a skill/job. USAF '58-'78


Re: For all you RTTY / Teletype fans out there..

 

Interesting bio! I think doing a single specialty for a long time would be great if you loved it. I had 4 in the USAF since they love to shuffle you around about the time you love a skill/job. USAF '58-'78


Re: Guide to New Rig backend creation?

 

Thanks Dave.
?
I'll see how I get on.
?
No doubt I'll be back here again at somepoint soon.
?
All the best.
?
Dave G0WBX.