开云体育

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

QtSoundModem on a separate host: changing radios


 

My IC-7100 stopped transmitting power.
I want to use my IC-7300 in its place.
I have been running pilinbpq (on a rpi;-) since December 2020 and
QtSoundModem64 on a tiny x86 laptop for about 2 years.
I am no longer familiar with how to select my radio's serial port; /dev/ttyUSB73 .

'aplay -l/arecord -l' reports my IC-7300 on "Card 2" ("hw:2,0" ?).
My IC-7100 was "Card 1" ("hw:1,0 ?)

I cannot find a reference to "/dev/ttyUSB" nor "hw:#,0" in QtSoundModem.ini.

I found a previous reference to "hw:1,0" in
(GUI) QtSoundModem64 -> Settings -> Setup Devices -> Dialog -> Sound Card.
I changed that to 'hw:2,0'.

BPQ did set my IC-7300 to 7.101 MHz, so maybe something is working.

My IC-7100 uses CI-V address 88h, my IC-7300 uses CI-V address 94h.
Where to I edit this setting?

73, Chuck


 

GM Chuck,

On Tue, Jan 21, 2025 at 10:00?AM Chuck Gelm via <nc8q-aredn=[email protected]> wrote:
My IC-7100 stopped transmitting power.
I want to use my IC-7300 in its place.
I have been running pilinbpq (on a rpi;-) since December 2020 and
QtSoundModem64 on a tiny x86 laptop for about 2 years.
I am no longer familiar with how to select my radio's serial port;
/dev/ttyUSB73 .

'aplay -l/arecord -l' reports my IC-7300 on "Card 2" ("hw:2,0" ?).
My IC-7100 was "Card 1" ("hw:1,0 ?)

I cannot find a reference to "/dev/ttyUSB" nor "hw:#,0" in QtSoundModem.ini.

I found a previous reference to "hw:1,0" in
(GUI) QtSoundModem64 -> Settings -> Setup Devices -> Dialog -> Sound Card.
I changed that to 'hw:2,0'.

That should be correct for the sound device in QtSM based on what was reported via aplay and arecord.

BPQ did set my IC-7300 to 7.101 MHz, so maybe something is working.

My IC-7100 uses CI-V address 88h, my IC-7300 uses CI-V address 94h.
Where to I edit this setting?

That should be in the rig control area in bpq32.cfg. Assuming you are using the "new method" per , you would need a line like this for the IC7300, and there should be an old one for the IC7100. I'm assuming /dev/ttyUSB73 is the serial port for CAT control on the 7300.
RADIO 1
/dev/ttyUSB73 9600 ICOM IC7300 94
For the most part I don't know either radio, but I do know that the 7300 has built-in sound. Based on what you mentioned above, it sounds like the 7100 does also. I'm not sure how you had PTT set up in QtSM with the 7100. With QtSM running on a different machine than BPQ, it can be set to use Hamlib for PTT, which will connect to BPQ's hamlib emulator. Then QtSM's PTT via hamlib is converted by BPQ to CAT commands for PTT. In that case the rig control line would need to include invoking the hamlib emulator:
RADIO 1
/dev/ttyUSB73 9600 ICOM IC7300 94 HAMLIB=4532
- and QtSM will need to be set to use hamlib for PTT using the IP address of the BPQ machine.
For all I know you may already be using the hamlib method with the 7100 given QtSM and BPQ are on separate computers.

73,
Lee K5DAT


 

BPQ controls the radio, so you set CI-V address and serial port in the Radio or RigConfig sections of bpq32.cfg.

In QtSM change the Sound Card setting to match your new hw: number.

73, John

On 21/01/2025 16:00, Chuck Gelm wrote:
My IC-7100 stopped transmitting power.
I want to use my IC-7300 in its place.
I have been running pilinbpq (on a rpi;-) since December 2020 and
QtSoundModem64 on a tiny x86 laptop for about 2 years.
I am no longer familiar with how to select my radio's serial port; /dev/ttyUSB73 .

'aplay -l/arecord -l' reports my IC-7300 on "Card 2" ("hw:2,0" ?).
My IC-7100 was "Card 1" ("hw:1,0 ?)

I cannot find a reference to "/dev/ttyUSB" nor "hw:#,0" in QtSoundModem.ini.

I found a previous reference to "hw:1,0" in
(GUI) QtSoundModem64 -> Settings -> Setup Devices -> Dialog -> Sound Card.
I changed that to 'hw:2,0'.

BPQ did set my IC-7300 to 7.101 MHz, so maybe something is working.

My IC-7100 uses CI-V address 88h, my IC-7300 uses CI-V address 94h.
Where to I edit this setting?

73, Chuck







 

开云体育

Hi Chuck,

Qtsoundmodem running on different machine. 44.137.31.76

QtSoundModem.ini

[Init]
CM108Addr=
DispMode=1
DualChan=1
DualPTT=1
FLRigHost=127.0.0.1
FLRigPort=12345
HamLibHost=44.137.31.76
HamLibPort=4532
MinimizetoTray=0
PTT=HAMLIB
PTTBAUD=19200
PTTMode=17
PTTOffString=
PTTOnString=
RXSampleRate=12000
SCO=1
SndRXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"
SndTXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"
SoundMode=0
TXPort=8884
TXRotate=0
TXSampleRate=12000
UDPClientPort=8888
UDPHost=127.0.0.1\n
UDPServer=0
UDPServerPort=8884
WaterfallMax=3300
WaterfallMin=0
Wisdom=(fftw-3.3.8 fftwf_wisdom #x4a633eef #xb5a95564 #x91014bdd #x9c85ce5f\n? (fftwf_codelet_n1fv_3_neon 0 #x30bff #x30bff #x0 #xd8eb4fc2 #xb4b7ddcb #xc648e13b #x97a64eef)\n? (fftwf_dft_vrank_geq1_register 0 #x30bff #x30bff #x0 #x86ba2fc3 #xd9d37881 #xffbbb400 #x20032685)\n? (fftwf_dft_vrank_geq1_register 0 #x30bff #x30bff #x0 #xb1615290 #x725e2d62 #xa4c41a4d #x764c835f)\n? (fftwf_codelet_t1fuv_6_neon 0 #x30bff #x30bff #x0 #xa1dae1f9 #xcf4175ca #x165c93d4 #x431b4b4f)\n? (fftwf_dft_vrank_geq1_register 0 #x31bff #x31bff #x0 #x51999523 #x06be4b5b #xc7d1dd51 #x53b6199d)\n? (fftwf_rdft_rank0_register 2 #x31bff #x31bff #x0 #xff75c762 #x3a0ee093 #x5b78d592 #x6b6be60e)\n? (fftwf_codelet_t1fv_3_neon 0 #x30bff #x30bff #x0 #xf6ecde88 #x78652c9c #xfb4aeade #xb66f7fb6)\n? (fftwf_codelet_t3fv_16_neon 0 #x31bff #x31bff #x0 #x466cbe30 #x384c6da7 #x95d87b8c #xe3cecc25)\n? (fftwf_dft_r2hc_register 0 #x31bff #x31bff #x0 #xe57fac2b #x1a805e91 #x77bebbbf #xc7df4f55)\n? (TIMEOUT 0 #x1040 #x11bdd #x11c #xd124ca6c #xeb82cd90 #x28cd6189 #x0412976b)\n? (fftwf_dft_bluestein_register 0 #x31bff #x31bff #x0 #x95391a46 #xf3b5f154 #x7e4c9611 #x9c236d23)\n? (fftwf_dft_nop_register 0 #x31bff #x31bff #x0 #xdf288e01 #x21687a96 #xf5aa97df #x2b6cb1e3)\n? (fftwf_dft_buffered_register 1 #x31bff #x31bff #x0 #x48f7cedd #x5ddc4b78 #xe6834056 #xf22ff7fa)\n)\n
darkTheme=false
multiCore=1
onlyMixSnoop=false
pttGPIOPin=17
pttGPIOPinR=17
txLatency=50
useKISSControls=false

Use hamlib for TX (also on the qtsoundmodem machine, there is where your ic7300 is connected)

/usr/local/bin/rigctld -m 3073 -r /dev/ttyUSB0 -s 19200 -T 44.137.31.76 -t 4532

On my BPQ32 machine

bqp32.cfg

; My Radio Number 1 that automatically switches bands and updates frequency every 5 seconds
RADIO 1
HAMLIB 44.137.31.76:4532
00:00
5,14.102300,USB,F1,D,P123
06:00
5,7.049450,USB,F1,D,P123
19:00
5,14.102300,USB,F1,D,P123
****

Running QtSoundModem and bpq32 on the same machine

HamLibHost=44.137.31.70
HamLibPort=4532
PTT=HAMLIB
SndRXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"
SndTXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"


bpq32.cfg

; My Radio Number 1 that automatically switches bands and updates frequency every 5 seconds
RADIO 1
/dev/ttyUSB0 19200 ICOM IC7300 94 PTT_SETS_INPUT AUX HAMLIB=4532
00:00
5,14.102300,USB,F1,D,P123
06:00
5,7.049450,USB,F1,D,P123
19:00
5,14.102300,USB,F1,D,P123
****

The above works well for me.

73 Niels PD9Q

Op 21-1-2025 om 17:00 schreef Chuck Gelm:

My IC-7100 stopped transmitting power.
I want to use my IC-7300 in its place.
I have been running pilinbpq (on a rpi;-) since December 2020 and
QtSoundModem64 on a tiny x86 laptop for about 2 years.
I am no longer familiar with how to select my radio's serial port; /dev/ttyUSB73 .

'aplay -l/arecord -l' reports my IC-7300 on "Card 2" ("hw:2,0" ?).
My IC-7100 was "Card 1" ("hw:1,0 ?)

I cannot find a reference to "/dev/ttyUSB" nor "hw:#,0" in QtSoundModem.ini.

I found a previous reference to "hw:1,0" in
(GUI) QtSoundModem64 -> Settings -> Setup Devices -> Dialog -> Sound Card.
I changed that to 'hw:2,0'.

BPQ did set my IC-7300 to 7.101 MHz, so maybe something is working.

My IC-7100 uses CI-V address 88h, my IC-7300 uses CI-V address 94h.
Where to I edit this setting?

73, Chuck










 

开云体育

On 1/21/25 11:37, Lee Bengston via groups.io wrote:
GM Chuck,

On Tue, Jan 21, 2025 at 10:00?AM Chuck Gelm via <nc8q-aredn=[email protected]> wrote:
My IC-7100 stopped transmitting power.
I want to use my IC-7300 in its place.
I have been running pilinbpq (on a rpi;-) since December 2020 and
QtSoundModem64 on a tiny x86 laptop for about 2 years.
I am no longer familiar with how to select my radio's serial port;
/dev/ttyUSB73 .

'aplay -l/arecord -l' reports my IC-7300 on "Card 2" ("hw:2,0" ?).
My IC-7100 was "Card 1" ("hw:1,0 ?)

I cannot find a reference to "/dev/ttyUSB" nor "hw:#,0" in QtSoundModem.ini.

I found a previous reference to "hw:1,0" in
(GUI) QtSoundModem64 -> Settings -> Setup Devices -> Dialog -> Sound Card.
I changed that to 'hw:2,0'.

That should be correct for the sound device in QtSM based on what was reported via aplay and arecord.

BPQ did set my IC-7300 to 7.101 MHz, so maybe something is working.

My IC-7100 uses CI-V address 88h, my IC-7300 uses CI-V address 94h.
Where to I edit this setting?

That should be in the rig control area in bpq32.cfg. Assuming you are using the "new method" per , you would need a line like this for the IC7300, and there should be an old one for the IC7100. I'm assuming /dev/ttyUSB73 is the serial port for CAT control on the 7300.
RADIO 1
/dev/ttyUSB73 9600 ICOM IC7300 94
For the most part I don't know either radio, but I do know that the 7300 has built-in sound. Based on what you mentioned above, it sounds like the 7100 does also. I'm not sure how you had PTT set up in QtSM with the 7100. With QtSM running on a different machine than BPQ, it can be set to use Hamlib for PTT, which will connect to BPQ's hamlib emulator. Then QtSM's PTT via hamlib is converted by BPQ to CAT commands for PTT. In that case the rig control line would need to include invoking the hamlib emulator:
RADIO 1
/dev/ttyUSB73 9600 ICOM IC7300 94 HAMLIB=4532
- and QtSM will need to be set to use hamlib for PTT using the IP address of the BPQ machine.
For all I know you may already be using the hamlib method with the 7100 given QtSM and BPQ are on separate computers.

73,
Lee K5DAT

Hi, Lee:

Many thanks.

For ~2 years, the only think I have in the 'rig control area of bpq32.cfg' is

RADIO 1
HAMLIB 10.78.196.98:4532
# IP address of QtSoundModem (my tiny x86 laptop).

For ~2 years before that I ran QtSoundModem on the same RPI as pilinbpq:

RADIO 1
HAMLIB 10.174.162.40:4532
# IP address of pilinbpq (RPI)
-----

In
rigctld -vv -m 3073 -s 19200 -r /dev/ttyUSB73 -T 10.78.196.98 F 7101000 M PKTUSB 3000
I thought '-m 3073' pulls the '94h' from a rigctld library for my IC-7300 like my previous
rigctld -vv -m 3070 -s 19200 -r /dev/ttyUSB71A -T 10.78.196.98 F 7101300 M PKTUSB 3000
pulled '88h' from a rigctld library for the IC-7100.

Is it rigctld/QtSoundModem on the laptop that needs to know the C-IV port and not bpq32.cfg on the RPI?

I am going to set some 'styling' on my coding so that is looks different than my comments.
?
73, Chuck





 

On 1/21/25 13:18, Niels PD9Q wrote:
[Init]
CM108Addr=
DispMode=1
DualChan=1
DualPTT=1
FLRigHost=127.0.0.1
FLRigPort=12345
HamLibHost=44.137.31.76
HamLibPort=4532
MinimizetoTray=0
PTT=HAMLIB
PTTBAUD=19200
PTTMode=17
PTTOffString=
PTTOnString=
RXSampleRate=12000
SCO=1
SndRXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"
SndTXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"
SoundMode=0
TXPort=8884
TXRotate=0
TXSampleRate=12000
UDPClientPort=8888
UDPHost=127.0.0.1\n
UDPServer=0
UDPServerPort=8884
WaterfallMax=3300
WaterfallMin=0
Wisdom=(fftw-3.3.8 fftwf_wisdom #x4a633eef #xb5a95564 #x91014bdd #x9c85ce5f\n? (fftwf_codelet_n1fv_3_neon 0 #x30bff #x30bff #x0 #xd8eb4fc2 #xb4b7ddcb #xc648e13b #x97a64eef)\n (fftwf_dft_vrank_geq1_register 0 #x30bff #x30bff #x0 #x86ba2fc3 #xd9d37881 #xffbbb400 #x20032685)\n (fftwf_dft_vrank_geq1_register 0 #x30bff #x30bff #x0 #xb1615290 #x725e2d62 #xa4c41a4d #x764c835f)\n? (fftwf_codelet_t1fuv_6_neon 0 #x30bff #x30bff #x0 #xa1dae1f9 #xcf4175ca #x165c93d4 #x431b4b4f)\n? (fftwf_dft_vrank_geq1_register 0 #x31bff #x31bff #x0 #x51999523 #x06be4b5b #xc7d1dd51 #x53b6199d)\n (fftwf_rdft_rank0_register 2 #x31bff #x31bff #x0 #xff75c762 #x3a0ee093 #x5b78d592 #x6b6be60e)\n? (fftwf_codelet_t1fv_3_neon 0 #x30bff #x30bff #x0 #xf6ecde88 #x78652c9c #xfb4aeade #xb66f7fb6)\n? (fftwf_codelet_t3fv_16_neon 0 #x31bff #x31bff #x0 #x466cbe30 #x384c6da7 #x95d87b8c #xe3cecc25)\n (fftwf_dft_r2hc_register 0 #x31bff #x31bff #x0 #xe57fac2b #x1a805e91 #x77bebbbf #xc7df4f55)\n? (TIMEOUT 0 #x1040 #x11bdd #x11c #xd124ca6c #xeb82cd90 #x28cd6189 #x0412976b)\n (fftwf_dft_bluestein_register 0 #x31bff #x31bff #x0 #x95391a46 #xf3b5f154 #x7e4c9611 #x9c236d23)\n? (fftwf_dft_nop_register 0 #x31bff #x31bff #x0 #xdf288e01 #x21687a96 #xf5aa97df #x2b6cb1e3)\n? (fftwf_dft_buffered_register 1 #x31bff #x31bff #x0 #x48f7cedd #x5ddc4b78 #xe6834056 #xf22ff7fa)\n)\n
darkTheme=false
multiCore=1
onlyMixSnoop=false
pttGPIOPin=17
pttGPIOPinR=17
txLatency=50
useKISSControls=false
Hi, Niels:

I ran a diff from 'Init' through UDPServerPort:
You are '<', I am '>'.
diff 0 1
2c2
< CM108Addr=
---
CM108Addr=/dev/hidraw0 ; I wonder if this should be void or
'/dev/hidraw1' ?
4d3
< DualChan=1 ; You do not use this.
8c7
< HamLibHost=44.137.31.76
---
HamLibHost=10.78.196.98 ; These IP addresses look good to me.
10c9
< MinimizetoTray=0
---
MinimizetoTray=1
15c14
< PTTOnString=
---
PTTOnString=10.78.196.98 ; My PTT command goes elsewhere.
17,19c16,18
< SCO=1
< SndRXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"
< SndTXDeviceName="hw:1,0 USB Audio(USB Audio CODEC)"
---
SCO=0
SndRXDeviceName="hw:2,0 USB Audio(USB Audio CODEC)"
SndTXDeviceName="hw:2,0 USB Audio(USB Audio CODEC)"
25c24
< UDPHost=127.0.0.1\n
---
UDPHost=192.168.1.255 ; I am not sure about this value. If this is
'UDP Sound Server', mine is not enabled. ?
28,30c27,29

73, Chuck


 

开云体育

Update 20250121 19:41 UTC:


rpi-model3B:
bpq32.cfg:
...
HAMLIB 10.78.196.98:4532 ; <---- I think QtSoundModem picks up C-IV from 'rigctld -m 3073' parameter...not from bpq32.cfg. ???
00:00
99,3.5957,USB-D,F1,D
11:59
99,7.101,USB-D,F1,D
16:00
99,14.102,USB-D,F1,D
20:00
99,7.101,USB-D,F1,D
****
...
The Icom IC-7300 is following the 'RADIO 1' commands from BPQ
and apparently switching from Rx to Tx and back when executing
'Mail for:' and forwarding scripts, although no TX/audio is heard.
-----
tiny x86 laptop:
In separate command terminals:

Terminal A:
#IC-7100
#rigctld -vv -m 3070 -s 19200 -r /dev/ttyUSB71A -T 10.78.196.98 F 7101300 M PKTUSB 3000
#
#IC-7300
rigctld -vv -m 3073 -s 19200 -r /dev/ttyUSB73 -T 10.78.196.98 F 7101000 M PKTUSB 3000

Terminal B:
QtSoundModem64

Terminal C:
sudo x11vnc -passwd blahblahblah -many -display :0
-----

QtSoundModem:
Still no TX/RF/audio, but
the GUI is displaying and decoding from the IC-7100 if it is turned on! <---- ?
Else, if the IC-7100 is off, QtSoundModem waterfall is blank.

There is no RX/audio output from the IC-7300 while monitoring with the IC-7100 or a Kenwood TS-50.
QtSoundModem displays TX data from BPQ, radio PTT works, but no apparent RF/audio.

Issues:
  • PTT, but no RF/audio out from QtSoundModem.
  • No waterfall indication so no audio in from IC-7300 to QtSoundModem.

73, Chuck


 


On Tue, Jan 21, 2025 at 1:22?PM Chuck Gelm via <nc8q-aredn=[email protected]> wrote:

Hi, Lee:

Many thanks.

For ~2 years, the only think I have in the 'rig control area of bpq32.cfg' is

RADIO 1
HAMLIB
# IP address of QtSoundModem (my tiny x86 laptop).

For ~2 years before that I ran QtSoundModem on the same RPI as pilinbpq:

RADIO 1
HAMLIB
# IP address of pilinbpq (RPI)
-----

In
rigctld -vv -m 3073 -s 19200 -r /dev/ttyUSB73 -T 10.78.196.98 F 7101000 M PKTUSB 3000
I thought '-m 3073' pulls the '94h' from a rigctld library for my IC-7300 like my previous
rigctld -vv -m 3070 -s 19200 -r /dev/ttyUSB71A -T 10.78.196.98 F 7101300 M PKTUSB 3000
pulled '88h' from a rigctld library for the IC-7100.

Is it rigctld/QtSoundModem on the laptop that needs to know the C-IV port and not bpq32.cfg on the RPI?

I am going to set some 'styling' on my coding so that is looks different than my comments.
?
73, Chuck


OK Chuck, so now I know you were using hamlib with the 7100. There are different ways to get this to work actually. Continuing to use hamlib is probably the most straightforward path, which is what Niels was pointing to. He had a better crystal ball than I did with respect to what you were already doing with the 7100. In your rigctld, 3073 looks like it is the right number for the 7300, and Niels' example matches that.

> Is it rigctld/QtSoundModem on the laptop that needs to know the C-IV port and not bpq32.cfg on the RPI?
?
Yes, rigctld needs to know the C-IV port and not BPQ in this case. QtSM uses hamlib as Niels example showed.
?
73,
Lee K5DAT


 

Update 20250121 2300Z

BPQ/QtSoundModem +IC-7100 +IC-7300
has PTT on the IC-7300 but no RF output
is decoding on the IC-7100.

I am going to add another laptop QtSoundModem instance hopefully to segregate issues.
The IC-7100 fails to TX on HF, but did work on 2m VHF FM.

73, Chuck


 

开云体育

Are you sure your icom7300 is set up correctly?

menu - set - connectors
Data MOD - USB
ACC/USB Output select - AF
USB Serial function - CI-V
USB MOD Level - 35%
Data off MOD - MIC

And is your 7300 in USB-D mode


HAMLIB 10.78.196.98:4532
00:00
99,3.5957,USB-D,F1,D
11:59
99,7.101,USB-D,F1,D
16:00
99,14.102,USB-D,F1,D
20:00
99,7.101,USB-D,F1,D
****
I think this has to be

HAMLIB 10.78.196.98:4532
00:00
99,3.5957,USB,F1,D
11:59
99,7.101,USB,F1,D
16:00
99,14.102,USB,F1,D
20:00
99,7.101,USB,F1,D
****

mode USB / Filter 1 / Data mode

Op 22-1-2025 om 12:03 schreef Chuck Gelm:

Update 20250121 2300Z

BPQ/QtSoundModem +IC-7100 +IC-7300
has PTT on the IC-7300 but no RF output
is decoding on the IC-7100.

I am going to add another laptop QtSoundModem instance hopefully to segregate issues.
The IC-7100 fails to TX on HF, but did work on 2m VHF FM.

73, Chuck








 

Hi, Niels:

Thank you.
...

On 1/22/25 08:54, Niels PD9Q wrote:
Are you sure your icom7300 is set up correctly?
Let me check...

menu - set - connectors
Data MOD - USB
Check
ACC/USB Output select - AF
Check
USB Serial function - CI-V
Check
USB MOD Level - 35%
50% I note this difference.
Data off MOD - MIC
Check

And is your 7300 in USB-D mode
Check


HAMLIB 10.78.196.98:4532
00:00
99,3.5957,USB-D,F1,D
11:59
99,7.101,USB-D,F1,D
16:00
99,14.102,USB-D,F1,D
20:00
99,7.101,USB-D,F1,D
****
I think this has to be

HAMLIB 10.78.196.98:4532
00:00
99,3.5957,USB,F1,D
11:59
99,7.101,USB,F1,D
16:00
99,14.102,USB,F1,D
20:00
99,7.101,USB,F1,D
****
The (broken IC-7100) QtSoundModem is 10.78.196.98 (host=nc8q-qj) Old RADIO 1
The (IC-7300) new QtSoundModem host is 10.78.196.104 (host=nc8q-qt) New RADIO 2

Aha! I will sub 'USB' for 'USB-D'.

mode USB / Filter 1 / Data mode
I am not sure about the above line.

73, Chuck


 

Missing closer.

./linbpq
G8BPQ AX25 Packet Switch System Version 6.0.24.42 August 2024
Copyright ? 2001-2024 John Wiseman G8BPQ
Current Directory is /home/pi/linbpq
Log Directory is /home/pi/linbpq
Making Directory /home/pi/linbpq/logs
Configuration file Preprocessor.
Using Configuration file /home/pi/linbpq/bpq32.cfg
Conversion (probably) successful

PORTS 0x2bac50 LINKS 0x2c3038 DESTS 0x2cafb8 ROUTES 0x2e4fb8 L4 0x2e69b8 BUFFERS 0x2ed690

Initialising Port 01???? AXIP
Initialising Port 02???? TCPKISS IP 0.0.0.0 Port 8300 Chan A
Initialising Port 03???? Telnet Server
Initialising Port 04???? AXIP
Initialising Port 05???? UZ7HO Host 10.78.196.98 Port 8000 Chan B ; RADIO 1 IC-7100 VHF/UHF
Initialising Port 06
UZ7HO Host 10.78.196.104 Port 8000 Chan A ; RADIO 2 IC-7300
Initialising Port 07
UZ7HO Host 10.78.196.104 Port 8000 Chan B
Initialising Port 08
UZ7HO Host 10.78.196.104 Port 8000 Chan C
Initialising Port 09
UZ7HO Host 10.78.196.104 Port 8000 Chan D

Next I need to run rigctl(d) on each QtSoundModem instance.

73, Chuck


 

开云体育


Hi Chuck,

I was try to explane the line of rigcontrol.

99,7.101,USB,F1,D ; (seconds,frequency,mode,filter,data)

mode USB / Filter 1 / Data mode

99,7.101,USB-D,F1,D ; (seconds,frequency,USB Data,filter1,Data) I think this line is double, maybe it works.

I'm sure this line is ok for USB-D mode :? 99,7.101,USB,F1,D

Looks good to me...

Initialising Port 01???? AXIP
Initialising Port 02???? TCPKISS IP 0.0.0.0 Port 8300 Chan A
Initialising Port 03???? Telnet Server
Initialising Port 04???? AXIP
Initialising Port 05???? UZ7HO Host 10.78.196.98 Port 8000 Chan B ; RADIO 1 IC-7100 VHF/UHF
Initialising Port 06
UZ7HO Host 10.78.196.104 Port 8000 Chan A ; RADIO 2 IC-7300
Initialising Port 07
UZ7HO Host 10.78.196.104 Port 8000 Chan B
Initialising Port 08
UZ7HO Host 10.78.196.104 Port 8000 Chan C
Initialising Port 09
UZ7HO Host 10.78.196.104 Port 8000 Chan D

73 Niels

Op 22-1-2025 om 20:18 schreef Chuck Gelm:

Aha! I will sub 'USB' for 'USB-D'.

mode USB / Filter 1 / Data mode

I am not sure about the above line.

73, Chuck


 

开云体育

On 1/22/25 15:27, Niels PD9Q wrote:

Hi Chuck,

I was try to explane the line of rigcontrol.

99,7.101,USB,F1,D ; (seconds,frequency,mode,filter,data)

Hi, Niels and John W. :

Thank you.

I kept at this today and now have my IC-7300 transceiving on HF and
my IC-7100 transceiving on VHF/UHF.

I need to automate my rigctl scripts.

I am running 2 instances of QtSoundModem...1 for each radio/laptop.

I will try to run one 1200 baud FX/AX.25 and one 1200 baud IL2P on VHF/UHF on the same channel.

73, Chuck


 

Chuck,

I have had this happen on the 7100 before too. I had to do a factory reset FYI. In my case that the usb port just stopped accepting audio and toggling it in the menus was not working. May be some kind of firmware bug.


 

On 1/23/25 08:27, N9SEO via groups.io wrote:

Chuck,

I have had this happen on the 7100 before too. I had to do a factory reset FYI. In my case that the usb port just stopped accepting audio and toggling it in the menus was not working. May be some kind of firmware bug.
Hi, Kayne:

Thanks.
I see a 'Partial Reset' and a 'Full Reset', but not a 'factory reset'.
Nothing 'factory' found yet using my favorite search engine on the internet.
I have a 2 year old 'save to SD card', so I will try those 2 'soft' resets.

73, Chuck


 

On 1/23/25 08:27, N9SEO via groups.io wrote:

Chuck,

I have had this happen on the 7100 before too. I had to do a factory reset FYI. In my case that the usb port just stopped accepting audio and toggling it in the menus was not working. May be some kind of firmware bug.
Hi, Kayne:

IC-7100 Basic Manual does not mention 'factory', but
IC-7100_AdvancedInstructions.pdf page 19-4 shows:

After performing the All reset
All reset clears all programming and returns all settings
to their factory defaults.
Therefore, the repeater list, Memory channel contents,
filter setting and so on will be cleared, so you will need
to reprogram your operating settings.

So, that indicates a 'factory' reset.

;-)

73, Chuck


 

Yea, different vendors love to have different phrasing for the same thing. :D There is also a partial but I did the ALL. It has been a while.

For me I am not worried about memory presets as you can always download this in Chirp if you need and reapply.