Hey Cassie,
It's great to see Bob's real world experience with the IC-9100 and
what you need to consider when working with that radio.? One thing
that wasn't clear to me from Bob's message is which "audio
channel" the main band vs. sub-band audio is heard on.? If you
read:
?? #PDF page 59
??
You can see how Direwolf maps it's MONO channels to different
audio channels.? Ultimately, you need to find out if you need to
use:
?? #the left audio channel from the IC9100
?? ADEVICE plughw:2,0
?? ACHANNEL 2
?? CHANNEL 0
vs.
?? #the right audio channel from the
IC9100
?? ADEVICE plughw:2,0
?? ACHANNEL 2
?? CHANNEL 1
The other points that Bob brings up are super critical but are
technically not Direwolf's issue.? Since you're new to Linux and
maybe a bunch of these pitfalls, my Direwolf on Raspberry Pi document (aka.. anything debian
based) might be helpful in some of these areas (gpsd,
modem-manager, etc)
??
There are other guides out there on the Internet as well
though I can't speak to their accuracy, being up to date, etc.
--David
KI6ZHD
On 08/23/2024 01:52 PM, Bob Cameron
wrote:
toggle quoted message
Show quoted text
Hi Cassie
It looks like David has answered all. I am on the other side of
the world so some sleeping delay involved. Some notes;
One trap you might fall into later and should just keep in mind
is that the audio device in the 9100 is split left/right (ie
stereo) between the main and sub bands. In general terms that
means the top frequency display on the rig is main and the lower
one is sub. The sub band in normal "non satellite" mode is RX
only. I for example TX/RX on 30m whilst concurrenty RX only on
2mFM.?
In rig satellite mode however the sub band is the one that
TX/RX's and the main is RX only. For satellite half duplex it is
unlikely you'd use satellite mode, but one day you might want to
run both 70cm and 2m for sats or even concurrently listen on HF
for something. This will also tend to get confusing if you use a
satellite tracking, operating frequency program to compensate
for Doppler.
As mentioned, just keep in mind for later.
Regarding the non Icom response and bind/in use error. I have
found (in Debian) that the GPS daemon (gpsd) often grabs the
first USB port regardless. It actually happens before the daemon
even starts and is to do with a socket allocation on finding an
external USB device. Sorry I don't remember all the details. I
assume you will eventually want to connect a GPS device. If not
I suggest you remove gpsd from the installation as a quick way
out. If you eventually need to (eventually) connect a GPS unit
get back to me for assist. The other bind/conflict problem is
the dialup modem manager. If you don't use a dialup modem, the
easy workaround is to rename /sbin/ModemManager to
/sbin/ModemManager.disabled. Yes there are nicer ways but that
works.
I assume you changed the rigs serial speed from Auto to 19200?
That along with setting dialout perms might also be the reason
for no response.
When testing with rigctld in a separate shell/window there is
no need to background the process. ie omit the ampersand (&)
from the command end. (Backgrounding is what the [1] response
line indicates) It's only really needed if you have inserted it
early in the direwolf startup script. I cant really comment
where that is on your system. The -vvv command option is a log
verbosity thing so reducing that to (say) -v or even omitting
might eventually be in order.
Cheers Bob VK2YQA
On 24/8/24 01:08, cdres wrote:
You both are just wealths of knowledge here. I will be
apologizing at multiple points for what I see as very 'noob'
questions. I am just so grateful to have someone know what I'm
talking about. The? only person who had a strong sense of any
of this project graduated last semester, so I have a lot to
catch up on. For reference, the end goal of this project is to
have this 9100 and computer set as a ground station for a cube
satellite that will be flying with a TRX-VU radio board. Just
to put things in perspective for you all. Now on to the
updates...
?
Referencing the section you posted below, a few questions.
?
"When using the USB only connection the PTT goes in on
the first serial port as an Icom CI-V command. The 9100 does
not support RTS etc PTT signalling. The easiest way to
handle that IMO is to install hamlib and run the rigctld
daemon before starting direwolf. In my case I have the
following in the dw startup;
/usr/local/bin/rigctld -m 3068 -vvv -r /dev/icom9100a -s
19200 -c 0x7c &?? "
?
Forgive me if this is a really embarrassing question, but
where would I add that line with the correct dev into the
direwolf startup? I will install hamlib, too. once I figure
out which version to download... I'll work on that this
afternoon.?
?
I did the dmesg and confirmed the radio is USB0 and USB1-
so, would I use /dev/USB0 in the rigctld line?
?
Going into the instructions on the 9.1.3, when I use
arecord/aplay -l commands, it only shows two cards-
arecord -l
?
Since I haven't actually finalized the direwolf config
file, I won't try to run it quite yet. I'd like to make sure
I get the PTT line correct and make sure I get hamlib
installed in order to have that run appropriately.
?
That's all I have at the moment... but I will be back in
the lab this afternoon to try to hammer out something
beneficial. Again, I appreciate your help, and you patience
as I try to get caught up on what this all means.
?
Thanks again,
Cassie
KJ5HMK
aplay -l:
?
Then going into