Not technically Linuxham related, more adjacent to the topics on here.
?
My slusb8r cable for my Icom IC-718's RJ45 broke. It was the plastic spring on the connector that broke, not the 13 pin itself. Now I have some spare RJ45 and a tool to connect the wires and keep them in place. But it seems there is a misunderstanding on my part as to the internal wiring for the cable. Some look to be twisted together while some are nearly the same colour and looks like they they are either in one pin or another. It is hard to make out the wiring from the connection itself.
?
So has anyone got the wiring layout and are some twisted together or are they all separate? Would like to have this fixed and not buy another cable only for it to do the same problem again.
?
Any information will be grateful.
?
Will
2M0WHN
|
Re: FLrig FT-991A Memory Channels
>Win4Yaesu has this functionality, so I think it's safe to assume FLrig does too. I just can't find it.
?
It does not. Fortunately its easy to implement? and put into use as per Cliff 's example.
?
Screen shot from the FT-891 manual:
?
|
Re: FLrig FT-991A Memory Channels
Like in the email I sent with the screenshot of flrig, you need to get the 991A manual and find the list of commands and then enter those into flrig. Then it will do what you want. Flrig does not have all the rig's commands built into it.
toggle quoted message
Show quoted text
On Oct 12, 2024, at 09:28, va3jpx via < va3jpx@...> wrote:
Thanks for all the great replies. I would like to make clear that I do not want to program the 991A, I simply want FLrig to send a cat command to the 991A to either change the 'already programmed' memories that reside inside the 991A. Just like using the up/down controls on the mic or using the MCH dial - up or down.
?
I know nothing about cat commands or how to read write these things to/from the radio.
?
Win4Yaesu has this functionality, so I think it's safe to assume FLrig does too. I just can't find it.
?
VA3JPX
?
?
|
Re: FLrig FT-991A Memory Channels
Thanks for all the great replies. I would like to make clear that I do not want to program the 991A, I simply want FLrig to send a cat command to the 991A to either change the 'already programmed' memories that reside inside the 991A. Just like using the up/down controls on the mic or using the MCH dial - up or down.
?
I know nothing about cat commands or how to read write these things to/from the radio.
?
Win4Yaesu has this functionality, so I think it's safe to assume FLrig does too. I just can't find it.
?
VA3JPX
?
?
|
Ok, I did that and it seems to be working so far. Thank you for the help ?
|
Re: FLrig FT-991A Memory Channels
Yes, you can set a number of commands ready to go in flrig. See my screen shot. Very handy. I do this on a 7300, but it works for most rigs that are supported by flrig.
toggle quoted message
Show quoted text
On Oct 11, 2024, at 19:05, Denis - EI6IF via < ei6if@...> wrote:
I don't own a at FT-991 but I would expect the menu system to be similar to the FT-891. The FT-891 memories can be programmed through the FLrig's "send command" in the "config" menu. As? an example the following is an extract from the CAT manual of the FT-891. Clunky but has its uses.
?
<inline.0.part>
?
73 Denis
|
Re: FLrig FT-991A Memory Channels
I don't own a at FT-991 but I would expect the menu system to be similar to the FT-891. The FT-891 memories can be programmed through the FLrig's "send command" in the "config" menu. As? an example the following is an extract from the CAT manual of the FT-891. Clunky but has its uses.
?
?
73 Denis
|
Re: FLrig FT-991A Memory Channels
I use RT Systems ADMS-991A software with the RT-42 data cable.
toggle quoted message
Show quoted text
On Oct 11, 2024, at 12:50?PM, Richard Shaw, KF5OIM <hobbes1069@...> wrote:
? Hey Folks,
?
I have just started using FLrig for my FT-991A. I am wondering if there is a way to change memory channels that are stored in the 991A from within FLrig. Thoughts?
I don't think so, that would take a program like CHIRP which doesn't yet support the 991A.
Thanks, Richard KF5OIM
|
Re: fldigi 4.2.05.24 development version posted at
I confirm that Dave’s workaround below works on my configuration (4.2.05.24 on a M2 MacBook Air/ Sequoia 15.0.1) ? Thanks Dave!
I confirm that I too have zero issues with the mic access on my three Debian Bookworm boxes. ? I only have the mic problem when I byte the Apple :-(
toggle quoted message
Show quoted text
On Oct 11, 2024, at 09:07, Dave, W1HKJ <w1hkj@...> wrote:
I am the original and principal developer of fldigi.? I run the program on several different Apple h/w and OS versions.? The issue described below is only associated with the latest h/w and OS releases, including Sonoma
14.6.1 on all both Intel and Apple silicon.? I too count exactly 43 clicks to get past the microphone gate keeper.? I do not know what process in fldigi's start up code is causing the problem.? I can tell you how to avoid the gatekeeper.
- open a terminal window and execute the following set of commands:
- $ cd /Applications/fldigi 4.2.06 (for latest version)
- $ cd Contents
- $ cd MacOS
- $ cp fldigi ~
- $ cd
- $ ls (you should see the contents of your home folder with the fldigi binary present)
- run this copy of fldigi in one of two ways
- from the terminal window
- or from the finder
- open finder to the home directory and double click on the fldigi binary icon
- Either way, fldigi will open as a terminal application.? Be sure that you have granted microphone access to the the terminal.? You do this in the System Settings for "Privacy and Security"/Microphone.
- you may minimize the terminal window, but do not close it or fldigi will also close.
73, David,
W1HKJ
On 10/7/24 18:33, John Biccum, N7TIN wrote:
No, sadly nothing new on this issue in this version.
I’m running??4.2.05.24 on a M2 MacBook Air (Sequoia 15.0.1) and confirm the "FLDigi would like to access the microphone” issue IS still present in this version.
It still takes *exactly* 43 (forty-three) clicks of the “Allow” button before the “microphone” (IC7300 in my case) is allowed access.
I wonder why it *always* works after the 43rd “Allow”??
Could that number be helpful in find the the cause of this issue?
Anything new on the "FLDigi would like to access the microphone" problem?
|
Re: Guide to New Rig backend creation?
Hi again.
I also to, have two PCR-1000 receivers.? So I did take a look into their support needs.
Unfortunately, the "language and protocol" is utterly different to the CI-V driven radio's, not just the IC-R9000.
(Chalk and Cheese as we'd say this side of the puddle...)
It also seems the R9k has a rather limited selection of settings that can be altered over the CI-V bus, that could make things a little easier for me.?? Based on using a terminal emulator (CuteCom) to monitor what the radio spits out down the wire with the bus in "Transceive" mode, when something is changed on its front panel.
(I've yet to find a definitive CI-V "manual" specific to the IC-R9000, if such ever existed.)
Basically, Frequency, Mode, and Filter choice.? And the same basic command string is used for both mode and Filter setting.
Anyway, I'm making some, if slow progress, but one thing eludes me, and it's nothing to do with the coding for the radio.
I see now, that Flrig when you "make" it, (re)builds everything, needed or not.?? ISTR, that earlier versions used to (by default) only rebuild and re-link based on the file(s) that changed since the last "Make".
Is there an "adjustment" I can make to allow rebuilds to only recompile and re-link based on changed files since the last "make", so that I don't have to wait many minutes for it to complete!? (Long enough to make a fresh cup-o-tea!)
Or is that something now imposed by the current compiler and linker tools, as a security measure?
Sorry, but I don't understand the contents of the makefile, and there's heck of a lot of it!
If not, this is going to take me a long time to do.
Cheers and 73 to All.
??? Dave G0WBX.
--
Created on and sent from a Unix like PC running and using open source software:
|
Time to learn Unix commands.
?
Open terminal. That is your home directly (the prompt will have ~ in it), if not sure, type cd <enter> that puts you back to home.
?
ls -ahl
?
This will list a bunch of stuff.
?
You should see something like:
?
lonney@office-mac1 ~ % ls -ahl ? ? ?
total 152
drwxr-x---+ 40 lonney ?staff ? 1.3K Oct 11 08:53 .
drwxr-xr-x ? 5 root ? ?admin ? 160B Jul 17 02:49 ..
drwxr-xr-x ?25 lonney ?staff ? 800B Oct ?5 15:18 .fldigi
drwxr-xr-x ?18 lonney ?staff ? 576B Oct ?1 08:01 .flrig
?
Rename:
?
lonney@office-mac1 ~ % mv .fldigi .fldigi.old
?
Start Fldigi again.
?
- Lonney
|
Re: FLrig FT-991A Memory Channels
Hey Folks,
?
I have just started using FLrig for my FT-991A. I am wondering if there is a way to change memory channels that are stored in the 991A from within FLrig. Thoughts?
I don't think so, that would take a program like CHIRP which doesn't yet support the 991A.
Thanks, Richard KF5OIM
|
FLrig FT-991A Memory Channels
Hey Folks,
?
I have just started using FLrig for my FT-991A. I am wondering if there is a way to change memory channels that are stored in the 991A from within FLrig. Thoughts?
?
Thanks,
?
VA3JPX
?
|
When I run the fldigi exec file in terminal it gives this warning:?
?
Caught signal 11
Aborting fldigi due to a fatal error.
Please report this to: ? fldigi-devel@...
or file a bug report at:
?
I think this has something to do with a "shared memory segment" whatever that means. maybe that's the issue?
|
Re: fldigi 4.2.05.24 development version posted at
I am the original and
principal developer of fldigi.? I run the program on several
different Apple h/w and OS versions.? The issue described below
is only associated with the latest h/w and OS releases,
including Sonoma 14.6.1 on all both Intel and Apple silicon.? I
too count exactly 43 clicks to get past the microphone gate
keeper.? I do not know what process in fldigi's start up code is
causing the problem.? I can tell you how to avoid the
gatekeeper.
- open a terminal window
and execute the following set of commands:
- $ cd
/Applications/fldigi 4.2.06 (for latest version)
- $ cd Contents
- $ cd MacOS
- $ cp fldigi ~
- $ cd
- $ ls (you should see
the contents of your home folder with the fldigi binary
present)
- run this copy of fldigi
in one of two ways
- from the terminal
window
- or from the finder
- open finder to the
home directory and double click on the fldigi binary
icon
- Either way, fldigi
will open as a terminal application.? Be sure that you
have granted microphone access to the the terminal.? You
do this in the System Settings for "Privacy and
Security"/Microphone.
- you may minimize the
terminal window, but do not close it or fldigi will also
close.
73, David,
W1HKJ
On 10/7/24 18:33, John Biccum, N7TIN
wrote:
toggle quoted message
Show quoted text
No, sadly nothing new on this issue in this version.
I’m running??4.2.05.24 on a M2 MacBook Air (Sequoia 15.0.1) and
confirm the "FLDigi would like to access the microphone” issue
IS still present in this version.
It still takes *exactly* 43 (forty-three) clicks of the “Allow”
button before the “microphone” (IC7300 in my case) is allowed
access.
I wonder why it *always* works after the 43rd “Allow”??
Could that number be helpful in find the the cause of this
issue?
Anything new on the "FLDigi would like to access the
microphone" problem?
|
Ok, I'm not sure where my home directory is... where would I find it?
|
Index of /files/fldigi
and at
Refer to readme.txt for list of changes since 4.2.05.
73, David
W1HKJ
|
Re: FLRIG with Windows, Linux and the MAC
Works as expected on macOS 12.7.6 here, run it 24/7 year in year out.
|
I'm on 12.7.6, been running Flrig and Fldigi for years on this Mac, no problems.
?
Try renaming the .fldigi folder in your home directory. Setup Fldigi again.
?
Lonney
K1LH
|
flrig development version 2.0.05.77 posted at
Index of /alpha/flrigs
Tested with Icom 7300 and QRP L:abs QMX+ transceivers.
73, David,
W1HKJ
|
Richard Shaw, KF5OIM
Dave, W1HKJ