hi Bob,
?
So I went ahead and removed gpsd, renamed the modem manager, and double checked all of the perms for dialout and tty. I removed the ampersand, and the extra v's and rebooted- checking the USB's again, the radio was now on USB0 and 1, so I tried both:
?
yields no errors- but doesn't do anything else. just opens an empty line with a blinking cursor.
ctrl c and then:
yields the same effect. No scripts, no errors, no anything.
?
I'm hoping this is a better outcome than the errors? or just because of the lack of extra v's.
I did confirm that I have 60. as 19200 on the rig as well.? I am pretty sure the only way that I am starting rigctld is manually through these commands- I haven't to my knowledge, set anything else up.
I am planning to go through David's document, hoping to find something trivial that I just overlooked.
?
|
It must be that the D710 is internal to the ISS hull which is
radiation/rf-protective, and no external GPS antenna was interfaced
to the radio. Thank you.
On 8/25/24 08:47, I wrote:
toggle quoted message
Show quoted text
One would not expect instrumentation on the ISS to be limited to
the 60,000 ft. max GPS elevation restriction of many civilian
units. Even a TinyTrak-3 has provided high-altitude balloon
elevations > 92,000 ft., and certainly rocket scientists could
modify the D710. There must be a reason why they did not?
On 8/25/24 08:38, Thomas Leibold via
groups.io wrote:
Hi,
If this is the internal GPS receiver inside the
Kenwood D710 keep in mind that most such terrestrial GPS
receivers are intentionally limited at which altitude and
velocity they are operating (to prevent repurposing them for
military use).
GPS receivers for aviation use have a wider
range but still won't work in LEO.
Just my guess,
Thomas
KK6FPP
Get
Greetings, I'm wondering why the ISS PBEACON always
indicates ~0.0 lat/lon. Is GPS disabled due to rf electrical
or security concerns? From direwolf 1.8D:
...
0,1724595363,2024-08-25T14:16:03Z,RS0ISS,RS0ISS,16(2/2),0,',RS0ISS,IS,0.005500,0.166667,0.0,,,,,,Kenwood
TM-D710,Special,,ARISS-International Space Station
...
RS0ISS audio level = 16(2/2)??? ___||____
[0.3 07:16:03 25Aug2024]
RS0ISS>0P0PS3,APRSAT:'v&<0x1c>l
<0x1c>SI]ARISS-International Space Station=<0x0d>
MIC-E, Satellite/Pacsat w/overlay I, Kenwood TM-D710, Special
N 00 00.3300, E 000 10.0000, 0 km/h (0 MPH)
ARISS-International Space Station
...
Thank you.
|
But that would void the warranty.? If damaged during the mod, shipping cost back to Kenwood would be enormous <grin>
On Sunday, August 25, 2024 at 11:47:14 AM EDT, Rusty Travis <rusytravis19@...> wrote:
One would not expect instrumentation on the ISS to be limited to the
60,000 ft. max GPS elevation restriction of many civilian units.
Even a TinyTrak-3 has provided high-altitude balloon elevations >
92,000 ft., and certainly rocket scientists could modify the D710.
There must be a reason why they did not?
On 8/25/24 08:38, Thomas Leibold via
groups.io wrote:
Hi,
If this is the internal GPS receiver inside the
Kenwood D710 keep in mind that most such terrestrial GPS
receivers are intentionally limited at which altitude and
velocity they are operating (to prevent repurposing them for
military use).
GPS receivers for aviation use have a wider range
but still won't work in LEO.
Just my guess,
Thomas
KK6FPP
Get
Greetings, I'm wondering why the ISS PBEACON always indicates
~0.0 lat/lon. Is GPS disabled due to rf electrical or security
concerns? From direwolf 1.8D:
...
0,1724595363,2024-08-25T14:16:03Z,RS0ISS,RS0ISS,16(2/2),0,',RS0ISS,IS,0.005500,0.166667,0.0,,,,,,Kenwood
TM-D710,Special,,ARISS-International Space Station
...
RS0ISS audio level = 16(2/2)??? ___||____
[0.3 07:16:03 25Aug2024]
RS0ISS>0P0PS3,APRSAT:'v&<0x1c>l
<0x1c>SI]ARISS-International Space Station=<0x0d>
MIC-E, Satellite/Pacsat w/overlay I, Kenwood TM-D710, Special
N 00 00.3300, E 000 10.0000, 0 km/h (0 MPH)
ARISS-International Space Station
...
Thank you.
|
One would not expect instrumentation on the ISS to be limited to the
60,000 ft. max GPS elevation restriction of many civilian units.
Even a TinyTrak-3 has provided high-altitude balloon elevations >
92,000 ft., and certainly rocket scientists could modify the D710.
There must be a reason why they did not?
On 8/25/24 08:38, Thomas Leibold via
groups.io wrote:
toggle quoted message
Show quoted text
Hi,
If this is the internal GPS receiver inside the
Kenwood D710 keep in mind that most such terrestrial GPS
receivers are intentionally limited at which altitude and
velocity they are operating (to prevent repurposing them for
military use).
GPS receivers for aviation use have a wider range
but still won't work in LEO.
Just my guess,
Thomas
KK6FPP
Get
Greetings, I'm wondering why the ISS PBEACON always indicates
~0.0 lat/lon. Is GPS disabled due to rf electrical or security
concerns? From direwolf 1.8D:
...
0,1724595363,2024-08-25T14:16:03Z,RS0ISS,RS0ISS,16(2/2),0,',RS0ISS,IS,0.005500,0.166667,0.0,,,,,,Kenwood
TM-D710,Special,,ARISS-International Space Station
...
RS0ISS audio level = 16(2/2)??? ___||____
[0.3 07:16:03 25Aug2024]
RS0ISS>0P0PS3,APRSAT:'v&<0x1c>l
<0x1c>SI]ARISS-International Space Station=<0x0d>
MIC-E, Satellite/Pacsat w/overlay I, Kenwood TM-D710, Special
N 00 00.3300, E 000 10.0000, 0 km/h (0 MPH)
ARISS-International Space Station
...
Thank you.
|
Hi,
If this is the internal GPS receiver inside the Kenwood D710 keep in mind that most such terrestrial GPS receivers are intentionally limited at which altitude and velocity they are operating (to prevent repurposing them for military use).
GPS receivers for aviation use have a wider range but still won't work in LEO.
Just my guess,
Thomas
KK6FPP
Get
toggle quoted message
Show quoted text
Greetings, I'm wondering why the ISS PBEACON always indicates ~0.0 lat/lon. Is GPS disabled due to rf electrical or security concerns? From direwolf 1.8D:
...
0,1724595363,2024-08-25T14:16:03Z,RS0ISS,RS0ISS,16(2/2),0,',RS0ISS,IS,0.005500,0.166667,0.0,,,,,,Kenwood TM-D710,Special,,ARISS-International Space Station
...
RS0ISS audio level = 16(2/2)??? ___||____
[0.3 07:16:03 25Aug2024] RS0ISS>0P0PS3,APRSAT:'v&<0x1c>l <0x1c>SI]ARISS-International Space Station=<0x0d>
MIC-E, Satellite/Pacsat w/overlay I, Kenwood TM-D710, Special
N 00 00.3300, E 000 10.0000, 0 km/h (0 MPH)
ARISS-International Space Station
...
Thank you.
|
Greetings, I'm wondering why the ISS PBEACON always indicates ~0.0
lat/lon. Is GPS disabled due to rf electrical or security concerns?
From direwolf 1.8D:
...
0,1724595363,2024-08-25T14:16:03Z,RS0ISS,RS0ISS,16(2/2),0,',RS0ISS,IS,0.005500,0.166667,0.0,,,,,,Kenwood
TM-D710,Special,,ARISS-International Space Station
...
RS0ISS audio level = 16(2/2)??? ___||____
[0.3 07:16:03 25Aug2024]
RS0ISS>0P0PS3,APRSAT:'v&<0x1c>l
<0x1c>SI]ARISS-International Space Station=<0x0d>
MIC-E, Satellite/Pacsat w/overlay I, Kenwood TM-D710, Special
N 00 00.3300, E 000 10.0000, 0 km/h (0 MPH)
ARISS-International Space Station
...
Thank you.
|
Oh and forgot to mention. Be wary using the 9100 monitor, as the
TX audio then comes back into the DW RX. I have no idea if that
can cause a problem beyond just displaying on the terminal and
log, but just to keep in mind.
Bob
|
Hi David
Well my setup is Pulseaudio so very different;
(DONT USE THESE CASSIE)
#ADEVICE
ACHANNELS 2
RATE 48000
CHANNEL 0
MODEM 300 B+
PTT RIG 2 localhost:4532
CHANNEL 1
MODEM 1200
#No PTT so complains at start about using VOX
I assume that the ADEVICE settings default to the one stereo
soundcard. The left channel is main, right is sub. I used
pavucontrol for the initial device choice, but I also have some
pactl commands in the direwolf start script that sets device and
application volumes as they always revert to 100%, which is
probably now well beyond the OP topic. It's also possible to
define the audio device with an environment variable. eg
PULSE_PROP_APPLICATION_NAME=DIREWOLF
PULSE_SINK=alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
PULSE_SOURCE=alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
direwolf
Onto your initial setup Cassie I suggest you just use;
ADEVICE plughw:2,0
ACHANNELS2
ACHANNEL 2
CHANNEL 0
MODEM 1200 (or whatever it is)
PTT RIG 2 localhost:4532
......... etc
ACHANNEL 2
CHANNEL 1
MODEM 1200 (same as Ch0)
........... etc
Which is exactly what David suggested and the simplest way.
And assuming the sat uses 2m, run the rig 2m main and 70cm sub
both in FM-D mode, but NOT in satellite mode. The 70cm side will
not initially be tuned/used. If you really wanted to use rig
satmode the left/right channels toggle with the main/sub change so
no direwolf changes are needed. The main use of the 9100 sat mode
though is to track the main/sub VFOs when using the dial/knob and
run full duplex, so not really relevant to DW use. Further, if you
were to use gpredict to Doppler track the sat freq actually set it
to half duplex & VFO Up/Down not applicable, so as not to
touch the sub operating frequency at all.
Cheers Bob VK2YQA
On 24/8/24 07:07, David Ranch via
groups.io wrote:
toggle quoted message
Show quoted text
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
|
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
|
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:
toggle quoted message
Show quoted text
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
|
I restarted the system, disconnected all the rig, turned it
off, rebooted ubuntu, plugged it all back in, and turned on the
radio, still same message. I've got something not set up right,
now to find it.
How are you starting rigctld?? Manually?? Via some script?? I would
recommend to do this manually until you prove things are working at
the basic levels.
I did make sure the user is on the dialout list, immediately
after the command, it first shows:
and then followed by a continuous time out list, and after
several minutes, It did update with this at the bottom:
Opened rig model 3068, 'IC-9100'
binding failed (trying next interface): Network error 98:
Address already in use
binding failed (trying next interface): Network error 98:
Address already in use
main: bind error - no available interface
?
This seems to me that you have multiple rigctld daemons running.?
You should only have one.? However it might start.. the radio should
be ON and connected via USB first.
--David
KI6ZHD
|
I did make sure the user is on the dialout list, immediately after the command, it first shows:
and then followed by a continuous time out list, and after several minutes, It did update with this at the bottom:
Opened rig model 3068, 'IC-9100'
binding failed (trying next interface): Network error 98: Address already in use
binding failed (trying next interface): Network error 98: Address already in use
main: bind error - no available interface
?
I restarted the system, disconnected all the rig, turned it off, rebooted ubuntu, plugged it all back in, and turned on the radio, still same message. I've got something not set up right, now to find it.
?
running ps ax|grep rigctld:
1083837 pts/0 ? ?S ? ? ?0:00 rigctld -m 3068 -vvv -r /dev/ttyUSB0 -s 19200 -c 0x7c
1087081 pts/0 ? ?S+ ? ? 0:00 grep --color=auto rigctld
?
?
|
yields a whole lot of time outs, with a final line of
connection, but then nothing. I'm assuming it's because I only
downloaded the utils from hamlib, and will probably need other
packages, so I will start working on that. but. I'm hopeful!
Beyond just the timeouts, did rigctld say anything else when it
first started?? Did you fix the permissions of of the serial ports
as I mentioned?
??
I did also update the dw config file, so as soon as I feel
like the rigctl is working, I'll run dw and cross some fingers.
Btw.. once you get rigctl working, you might need to increase the
direwolf.conf "TXDELAY" variable as processing all of this will take
longer.? Btw.. you might consider trying to increase the CI-V serial
port speed to the maximum reliable speed since it seems you might
want to do VFO frequency changes to deal with doppler shift as the
satellite moves.? A faster CI-V serialization rate will make a
difference here.
--David
KI6ZHD
|
Ok, so I found info on hamlib, was able to download libhamlib_utils and ran rigctl -l using grep to locate 9100 to make it easier, and now I see where the 3068 number came from. So now, running:
rigctld -m 3068 -vvv -r /dev/ttyUSB0 -s 19200 -c 0x7c &
?
yields a whole lot of time outs, with a final line of connection, but then nothing. I'm assuming it's because I only downloaded the utils from hamlib, and will probably need other packages, so I will start working on that. but. I'm hopeful!
?
?
I did also update the dw config file, so as soon as I feel like the rigctl is working, I'll run dw and cross some fingers.
?
|
Hello Cassie,
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.
You're welcome and there are many other people here on the list who
can help, offer other unique insights, etc.
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...
Sounds like that was a student but the instructor forgot to mandate
that this person DOCUMENT as they go!
?
"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.
That command line would need to be started BEFORE you start
Direwolf.? You can start all of these things via a shell script
(simplistic way), you could do it via creating new systemd units
(more proper yet complex way), etc.? What's you're preference?? You
can see some examples of all this by searching for "start up" or
"systemd" in the email list archives.
?I did the dmesg and confirmed the radio is USB0 and USB1-
so, would I use /dev/USB0 in the rigctld line?
Per the email response from VK2YQA who has a 9100, you would use
/dev/ttyUSB0 once your radio is configured to enable CI-V commands.?
You would use something like the command:
?? rigctld -m 3068 -vvv -r /dev/ttyUSB0 -s 19200 -c 0x7c &
?? - The path to the rigctld program might need to be set depending
on how you install Hamlib
?? - the Unix group permissions to use the /dev/ttyUSB0 device might
need to be set to "dialout" (and then log out, log back in to get
the new permsissions)
?? - Find examples on the Internet to use the "rigctl" command on to
confirm you can remotely control the radio as expected
?
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.
It looks like you will want to use "card 2" so the proper
direwolf.conf file setting would be:
--
ADEVICE plughw:2,0
--
--David
KI6ZHD
|
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
|
Hi Cassie (and David)
The 9100 effectively has a sound card and 2 serial port UARTS on
the end of its USB hub, so only the USB A-B cable is needed.
Re the audio, I think it worthwhile for initial simplicity to
start with what you already have. ie if it installed Pipewire,
Pulseaudio or the basic ALSA then start there. I have my own
reasons for sticking with Pulseaudio that are well beyond this
topic!
You might want to set 60. CI-V Baud Rate to 19200 rather than
rely on the default "Auto". Also 62. CI-V Transceive to Off (which
I wont elaborate on)
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 &
You will probably need /dev/ttyUSB0 as I created a special link
name. Once again hot plugging and looking at dmesg will tell you
what the port number is.
Then in the actual config file the PTT line is;
PTT RIG 2 localhost:4532
It is also possible to direct rig connect, not using rigctld, but
that stops sharing the rig with other applications. I actually use
it to have the rig QSY and do other things so more flexible. The
User Guide link David suggested has working examples of that, but
using rig number 3068.
Hope this helps
Cheers Bob VK2YQA
On 23/8/24 05:28, David Ranch via
groups.io wrote:
toggle quoted message
Show quoted text
Hello Cassie,
Thank you both for the reply. I inherited this
project (with of course zero knowledge of any of this) and am
trying to make sense out of what they had started (granted none
of their set up was working when I came in).
A great way to learn and you've come to the right place.? Lots of
very smart users, developers, etc. are here on this list.
I adjusted the cabling... ditched the rigblasters and
looked over the 9100 settings- FM/D, 55 squelch off, 56 mod
level is on 50%, 59 data mod USB.
Any other settings I should be looking out for?
I would say that once you start direwolf and start decoding some
packets, send us the direwolf startup output to see if there might
be any initial tunings needed
They also have 2 connections to the computer, they have the
USB bus and also have the DATA2 connection- are both of those
necessary?
I'm not an IC9100 but in browsing the manual yesterday, it seems
like the USB connection should be able to do it all
I'm in the process of adjusting the direwolf config file to
match the new setup, and I'm not quite sure what you mean by
not having ADEVICE? are all of those lines commented for you?
or do you have a line for ADEVICE default?
Also- we are currently running on Ubuntu desktop, 22.04.3
The ADEVICE aka "Audio Device" is what Direwolf connects to for
hearing and sending the audio.? Direwolf is very flexible on which
audio "device" it will interact with.? I personally recommend to
try and keep Pipewire, PulseAudio, etc. out of it if possible in
the spirit of keeping things simpler.? To Identify the USB audio
device from the IC9100, I would recommend to :
?? #1 - Shutdown direwolf
?? #2 - disconnect the IC9100 USB port from the Ubuntu computer
?? #3 - re-connect the IC9100 USB port and then run "sudo dmesg"
on the Ubuntu computer to see what sound and serial devices were
recognized
?? #4 - follow the instructions from:
? ? ? See Section 9.1.3
?????
For PTT, it sounds like you will need to select the second serial
port presented by the IC9100 which you would have been told about
in item #3 above.
--David
KI6ZHD
|
Hello Cassie,
Thank you both for the reply. I inherited this project
(with of course zero knowledge of any of this) and am trying to
make sense out of what they had started (granted none of their set
up was working when I came in).
A great way to learn and you've come to the right place.? Lots of
very smart users, developers, etc. are here on this list.
I adjusted the cabling... ditched the rigblasters and looked
over the 9100 settings- FM/D, 55 squelch off, 56 mod level is on
50%, 59 data mod USB.
Any other settings I should be looking out for?
I would say that once you start direwolf and start decoding some
packets, send us the direwolf startup output to see if there might
be any initial tunings needed
They also have 2 connections to the computer, they have the
USB bus and also have the DATA2 connection- are both of those
necessary?
I'm not an IC9100 but in browsing the manual yesterday, it seems
like the USB connection should be able to do it all
I'm in the process of adjusting the direwolf config file to
match the new setup, and I'm not quite sure what you mean by not
having ADEVICE? are all of those lines commented for you? or do
you have a line for ADEVICE default?
Also- we are currently running on Ubuntu desktop, 22.04.3
The ADEVICE aka "Audio Device" is what Direwolf connects to for
hearing and sending the audio.? Direwolf is very flexible on which
audio "device" it will interact with.? I personally recommend to try
and keep Pipewire, PulseAudio, etc. out of it if possible in the
spirit of keeping things simpler.? To Identify the USB audio device
from the IC9100, I would recommend to :
?? #1 - Shutdown direwolf
?? #2 - disconnect the IC9100 USB port from the Ubuntu computer
?? #3 - re-connect the IC9100 USB port and then run "sudo dmesg" on
the Ubuntu computer to see what sound and serial devices were
recognized
?? #4 - follow the instructions from:
? ? ? See Section 9.1.3
?????
For PTT, it sounds like you will need to select the second serial
port presented by the IC9100 which you would have been told about in
item #3 above.
--David
KI6ZHD
|
Thank you both for the reply. I inherited this project (with of course zero knowledge of any of this) and am trying to make sense out of what they had started (granted none of their set up was working when I came in).
I adjusted the cabling... ditched the rigblasters and looked over the 9100 settings- FM/D, 55 squelch off, 56 mod level is on 50%, 59 data mod USB.
Any other settings I should be looking out for? They also have 2 connections to the computer, they have the USB bus and also have the DATA2 connection- are both of those necessary? I'm in the process of adjusting the direwolf config file to match the new setup, and I'm not quite sure what you mean by not having ADEVICE? are all of those lines commented for you? or do you have a line for ADEVICE default?
Also- we are currently running on Ubuntu desktop, 22.04.3
?
Again, thank you both so much for taking the time to reply.
Cassie
KJ5HMK
|
Hello Cdres,
I agree with VK2YQA that if your radios have built-in
sound devices, you should use those and NOT use anything external
like a RigBlaster.? Yes, they can be made to work but it only will
make things more complicated than required.
Assuming you try to alter your setup to us the USB-connected
built-in IC9100 sound device, here are a few thoughts on your email:
However, the radio B is also connected with a second
rigblaster to computer B, which while running with run code
'direwolf' shows no received information.
You say you're using Ubuntu on these computers.? Which version of
Ubuntu and is it the full desktop version or the Server version?? If
you're using the Desktop version, you might need to use the
pavucontrol program to route the IC9100 sound input/output to
Direwolf.
I have also tried to tune both radio set ups to 144.39 which
I was told was a national APRS frequency and that I should be
able to receive packets from it. While tuned, I can hear the
transmissions, but again, neither setup of direwolf is showing
any kind of received information.
In addition to sound routing, you also need to make sure the audio
levels set by the radio itself are high enough.? There might be some
level of control on the IC9100 itself but there should also be the
audio levels set on the computer side as well.? Your goal here
should be to "hear" packets at a Direwolf reported level of 50.?
It's important to open up the squelch on the IC9100 full time for
best packet performance.
I am not sure if the issue lies in the config file or if it
has something to do with our aux jack set-up... The rigblaster
has an input and output aux jack, while our computers have a
combo input/output jack. I believe we are using a splitter that
should solve that issue and allow both to be plugged in, but-
maybe I'm wrong?
No.. only use one sound card and never connect them together.? Leave
the computer's built-in sound device for various local notifications
and then use say the IC9100's sound device only for packet usage.
?
PTT /dev/ttyUSB0 RTS DTR
For PTT, it's unlikely to be both RTS and DTR at the same time.? The
most common default is "RTS"
AGWPORT 8000
KISSPORT 8001
Beyond doing APRS with Direwolf, do you plan on using any external
programs with Direwolf?? If not, I recommend to turn off these other
network ports with:
AGWPORT 0
KISSPORT 0
FX25TX 1
Do you plan on doing 300bps packet over HF?? If not, REMOVE this
line for standard APRS needs.
PERSIST 63
SLOTTIME 12
RETRY 5
FRACK 5
MAXFRAME 4
PACLEN 128
DWAIT 0
For initial setup, you don't need to set any of these items.
TXDELAY 50
TXTAIL 40
These timers for transmit and "release of transmit" are far to
long.? For your IC9100, I would recommend to start with say:
TXDELAY 20
TXTAIL 10
Once things are working, I would recommend to research what are the
fastest times this radio supports and use those.? This can also be
figured out via a service monitor if you have access to one.
--David
KI6ZHD
|
