Hi again.

Thanks for that info David.

Checking off what you described...

It was:-
??? src/rigs/rigs.cxx:??? &rig_ICR71,??? ??? // 63

That escaped my radar.? (Of course, I've used? "&rig_ICR9000" .)
(Do I guess right, that the // 63 comment is just a human convenience count reference?? At present, the R9000 is a the bottom of the list sporting? // 111 after it.)

Anyway..? It now appears in the selection list and other than errors when trying to initialise, it generates C-IV traffic that currently is ignored by the R9000, so I should be good for some late nights with the R9000 C-IV manual, and a warm computer, for a while...

I think, the closest TRX, is the IC-781, from the same era as the R9000.

Hamlib has both, so I'll be comparing stuff in the back-ends there too.? I have found that Grig via Hamlip works with the R9000, but there are some "funnies" with filter selections etc.?? Maybe the two are not so similar.?? More to learn...

Best Regards David, your help is very much appreciated.

Oh, I'm doing all this with the sources for? flrig-2.0.05.75

73.

Dave G0WBX.


PS:??? The build warnings I see, are for a FT2000

---

rigs/yaesu/FT2000.cxx: In member function ‘virtual void RIG_FT2000::set_rf_gain(int)’:
rigs/yaesu/FT2000.cxx:1124:52: warning: ‘%03d’ directive output may be truncated writing between 3 and 9 bytes into a region of size 5 [-Wformat-truncation=]
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG0%03d;", val * 255 / 100);
????? |??????????????????????????????????????????????????? ^~~~
rigs/yaesu/FT2000.cxx:1124:48: note: directive argument in the range [-21474836, 21474836]
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG0%03d;", val * 255 / 100);
????? |??????????????????????????????????????????????? ^~~~~~~~~~
rigs/yaesu/FT2000.cxx:1124:25: note: ‘snprintf’ output between 8 and 14 bytes into a destination of size 8
?1124 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG0%03d;", val * 255 / 100);
????? |???????????????? ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
rigs/yaesu/FT2000.cxx:1119:52: warning: ‘%03d’ directive output may be truncated writing between 3 and 9 bytes into a region of size 5 [-Wformat-truncation=]
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG1%03d;", val * 255 / 100);
????? |??????????????????????????????????????????????????? ^~~~
rigs/yaesu/FT2000.cxx:1119:48: note: directive argument in the range [-21474836, 21474836]
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG1%03d;", val * 255 / 100);
????? |??????????????????????????????????????????????? ^~~~~~~~~~
rigs/yaesu/FT2000.cxx:1119:25: note: ‘snprintf’ output between 8 and 14 bytes into a destination of size 8
?1119 |???????????????? snprintf(szcmd, sizeof(szcmd), "RG1%03d;", val * 255 / 100);
????? |???????????????? ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---

--

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

Dave,

I have been using FLdigi-4.2.05.24 successfully for several months now.?

I am going to have to upgrade my MacOS to the latest and greatest (Sequoia 15.0.1) in the near future.

Have you done any testing with Sequoia?

73,

John WA5NJG

On May 29, 2024, at 2:25 PM, Dave, W1HKJ <w1hkj@...> wrote:

Index of /alpha/fldigi

Author: dave-w1hkj <w1hkj@...>
Date:?? Wed May 29 13:48:38 2024 -0500

??? Micro modems
?? ?
????? * change name to avoid double word parsing issues with
??????? frequencies2.txt

Author: dave-w1hkj <w1hkj@...>
Date:?? Tue May 28 00:33:23 2024 -0500

??? colors and scheme
?? ?
????? * allow user to select default background and foreground
??????? colors
??????? . supplements command line usage

...

see readme.txt for complete list of commits.

73, David, W1HKJ

On May 29, 2024, at 2:25 PM, Dave, W1HKJ <w1hkj@...> wrote:

Index of /alpha/fldigi

Author: dave-w1hkj <w1hkj@...>
Date:?? Wed May 29 13:48:38 2024 -0500

??? Micro modems
?? ?
????? * change name to avoid double word parsing issues with
??????? frequencies2.txt

Author: dave-w1hkj <w1hkj@...>
Date:?? Tue May 28 00:33:23 2024 -0500

??? colors and scheme
?? ?
????? * allow user to select default background and foreground
??????? colors
??????? . supplements command line usage

...

see readme.txt for complete list of commits.

73, David, W1HKJ

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
? ? ? ? }

------------------------

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: