Re: @G8BPQ -- UZ7HO soundmodem for linux
All audio is handled in the KAM so the Pi only sees serial data decoded by the KAM. Look at your KAM manual to adjust audio levels. You may be swamping the KAM with excess audio from the radio.
Perry K4PWO?
Sent from my T-Mobile 4G LTE Device
Get
toggle quoted message
Show quoted text
John, can alsamixer be used to increase the input audio from KAM plus (using serial/USB connection)? the reason I ask is, on HF i sometimes find my Mark and Space lights are solid from a HF station, however my BPQ software dose not code the data......
Bret
KB5YZB
On 6/12/2022 3:04 AM, John G8BPQ wrote:
No, but make sure you've selected the right audio device in QtSM and that there is sufficient audio drive to trigger the PTT circuit on the SignaLink. Check the audio levels - I use alsamixer.
73,
John
On 12/06/2022 05:06, Brett Williams wrote:
Thanks Lee and John. I have the Program working well and receiving packet. The only issue im having now is transmit. QtSoundModem is receiving the command from QtTerm TCP, however the signallink is not keying. Is there an extra driver for the signal link?
On 6/10/2022 12:09 PM, Lee Bengston wrote:
Brett,
The sudo commands I provided were the "extra's" needed for compiling, but in hindsight you were probably missing the standard prerequisites for running the binary version.
It's all documented nicely here:
Good to know you have it working.? John was right in saying it's easier to just download the binary version and run it, and I should have mentioned that yesterday.
73,
Lee K5DAT
On Thu, Jun 9, 2022 at 11:38 PM Brett Williams < KB5YZB@...> wrote:
Thanks
I ran the SUDO command successfully.
I also have the file unzip on the pi.
I issued the "qmake" command and the following is reported...
qmake: could not find a Qt installation of ''
Lee Im not sure what went wrong.......
|
Re: @G8BPQ -- UZ7HO soundmodem for linux
John, can alsamixer be used to increase the input audio from KAM
plus (using serial/USB connection)? the reason I ask is, on HF i
sometimes find my Mark and Space lights are solid from a HF
station, however my BPQ software dose not code the data......
Bret
KB5YZB
On 6/12/2022 3:04 AM, John G8BPQ wrote:
toggle quoted message
Show quoted text
No, but make sure you've selected the right audio device in QtSM
and that there is sufficient audio drive to trigger the PTT
circuit on the SignaLink. Check the audio levels - I use
alsamixer.
73,
John
On 12/06/2022 05:06, Brett Williams
wrote:
Thanks Lee and John. I have the Program working well and
receiving packet. The only issue im having now is transmit.
QtSoundModem is receiving the command from QtTerm TCP, however
the signallink is not keying. Is there an extra driver for the
signal link?
On 6/10/2022 12:09 PM, Lee Bengston
wrote:
Brett,
The sudo commands I provided were the "extra's" needed
for compiling, but in hindsight you were probably missing
the standard prerequisites for running the binary version.
It's all documented nicely here:
Good to know you have it working.? John was right in
saying it's easier to just download the binary version and
run it, and I should have mentioned that yesterday.
73,
Lee K5DAT
On Thu, Jun 9, 2022 at
11:38 PM Brett Williams < KB5YZB@...>
wrote:
Thanks
I ran the SUDO command successfully.
I also have the file unzip on the pi.
I issued the "qmake" command and the following is
reported...
qmake: could not find a Qt installation of ''
Lee Im not sure what went wrong.......
|
Re: @G8BPQ -- UZ7HO soundmodem for linux
John that worked. Thanks. So now I think I have a port conflict.
I start my pi, BPQ. working fine....I did try to start
qtsoundmodem from command line (putty), says it running, however
qt Term report"tnc is not ready" for the new qtSM port...... Log
into the pi, run the qtSM from command line on the pi, all is
working BPQ and qtsound modem. until the qt soundmodem executes? a
command to transmit, after that BPQ will not respond for the ports
for the KAMplus which is VHF amd 20 meters, the new signal link
port will be 30 or 40 meters.
Again, thanks for help. I'm almost 100%
Brett
KB5YZB
?
On 6/12/2022 3:04 AM, John G8BPQ wrote:
toggle quoted message
Show quoted text
No, but make sure you've selected the right audio device in QtSM
and that there is sufficient audio drive to trigger the PTT
circuit on the SignaLink. Check the audio levels - I use
alsamixer.
73,
John
On 12/06/2022 05:06, Brett Williams
wrote:
Thanks Lee and John. I have the Program working well and
receiving packet. The only issue im having now is transmit.
QtSoundModem is receiving the command from QtTerm TCP, however
the signallink is not keying. Is there an extra driver for the
signal link?
On 6/10/2022 12:09 PM, Lee Bengston
wrote:
Brett,
The sudo commands I provided were the "extra's" needed
for compiling, but in hindsight you were probably missing
the standard prerequisites for running the binary version.
It's all documented nicely here:
Good to know you have it working.? John was right in
saying it's easier to just download the binary version and
run it, and I should have mentioned that yesterday.
73,
Lee K5DAT
On Thu, Jun 9, 2022 at
11:38 PM Brett Williams < KB5YZB@...>
wrote:
Thanks
I ran the SUDO command successfully.
I also have the file unzip on the pi.
I issued the "qmake" command and the following is
reported...
qmake: could not find a Qt installation of ''
Lee Im not sure what went wrong.......
|
Re: @G8BPQ -- UZ7HO soundmodem for linux
No, but make sure you've selected the right audio device in QtSM and
that there is sufficient audio drive to trigger the PTT circuit on
the SignaLink. Check the audio levels - I use alsamixer.
73,
John
On 12/06/2022 05:06, Brett Williams
wrote:
toggle quoted message
Show quoted text
Thanks Lee and John. I have the Program working well and
receiving packet. The only issue im having now is transmit.
QtSoundModem is receiving the command from QtTerm TCP, however
the signallink is not keying. Is there an extra driver for the
signal link?
On 6/10/2022 12:09 PM, Lee Bengston
wrote:
Brett,
The sudo commands I provided were the "extra's" needed
for compiling, but in hindsight you were probably missing
the standard prerequisites for running the binary version.
It's all documented nicely here:
Good to know you have it working.? John was right in
saying it's easier to just download the binary version and
run it, and I should have mentioned that yesterday.
73,
Lee K5DAT
On Thu, Jun 9, 2022 at
11:38 PM Brett Williams < KB5YZB@...>
wrote:
Thanks
I ran the SUDO command successfully.
I also have the file unzip on the pi.
I issued the "qmake" command and the following is
reported...
qmake: could not find a Qt installation of ''
Lee Im not sure what went wrong.......
|
Re: Picking up B messages at non HA node
You can only pick up bulls if they have been queued to you on that
node. So to pick up bulls on other nodes you'd have to define all
users as BBS on all your Nodes, with the same TO or AT lists. Only
one should be defined as Home BBS.
73,
John
On 11/06/2022 16:51, Ray Spreier-KG7AV
wrote:
toggle quoted message
Show quoted text
Is it possible for a user to pick up B messages by connecting to a
node at which they are not homed?
Running in a network of several nodes.?? Local users are checked
as a BBS, as are the other node calls.? In forwarding, all BBS
have an entry for their call and group bull names under TO calls.?
The other nodes have the same, plus all of the other callsigns
homed on that remote node.?? Forwarding of P and B messages has
been working great, and a user connecting to their home node picks
up everything as expected.? We're not doing any geographical based
forwarding.
In some controlled tests, recently discovered that a user
connecting to a different node than their HA node will not get B
messages.? Not a case of BID rejection because they already got it
off their HA node - it doesn't offer up any unread B msgs.? Don't
know if I've just been incorrectly assuming that users could grab
B msgs anywhere, or if I'm missing a nuance in the forwarding
setup.
Many thanks / Ray KG7AV
|
?administers 12 million routable IPv4 addresses (44.0.0.0 - 44.127.255.255) for amateur radio applications.? They can be used for such things as remote station control, repeater internet linking, amateur radio non-commercial websites, etc.
To better understand the current? and desired use of this address space, ARDC is running a survey at??(link will redirect to Qualtrics). Please take a few minutes and complete the survey.? It is available in English, German, French, and Japanese so share widely.? ARDC would like to have responses by the end of June.
|
Re: @G8BPQ -- UZ7HO soundmodem for linux
Thanks Lee and John. I have the Program working well and
receiving packet. The only issue im having now is transmit.
QtSoundModem is receiving the command from QtTerm TCP, however the
signallink is not keying. Is there an extra driver for the signal
link?
On 6/10/2022 12:09 PM, Lee Bengston
wrote:
toggle quoted message
Show quoted text
Brett,
The sudo commands I provided were the "extra's" needed for
compiling, but in hindsight you were probably missing the
standard prerequisites for running the binary version.
It's all documented nicely here:
Good to know you have it working.? John was right in saying
it's easier to just download the binary version and run it,
and I should have mentioned that yesterday.
73,
Lee K5DAT
On Thu, Jun 9, 2022 at 11:38
PM Brett Williams < KB5YZB@...>
wrote:
Thanks
I ran the SUDO command successfully.
I also have the file unzip on the pi.
I issued the "qmake" command and the following is
reported...
qmake: could not find a Qt installation of ''
Lee Im not sure what went wrong.......
|
Google Less Secure Apps Ended
Noticed that login and password no longer works for ISP Interface.? I assume it is because Google no longer supports less secure apps.
Is there a work around?
Thanks,
Harmen VE3EMA
|
Re: Picking up B messages at non HA node
Thanks, Mark.? Yes, John's documentation is pretty thorough on all of the options available for geographic / hierarchical based routing.??? Our situation is a distributed club, yes.?? Users HA with a particular node based on proximity / best path.?? But within the club there are interest groups, and the membership in these groups varies, even within an HA user list.
My understanding of the routing you explain is that it seems to be granular at the node/BBS level.??? That's why by marking our local users as BBS, we can take advantage of the forwarding rules to add the interest groups to which they belong under the TO column in addition to their own callsign.??? Users won't download B messages for groups to which they don't belong.
The downside is that when connecting to a node other than their HA, there is no "mailbox" of theirs, and thus no B messages related to the interest groups for them to download.
We could have each node flag everyone as a BBS, but that would stop the routing of P messages.
Hence my wondering if there is a middle way.?? And, of course, I could be misreading, or be ignorant of how to properly take advantage of the flexibility in the geographic routing. ?
Thanks again for your response.
Ray KG7AV
|
Re: Picking up B messages at non HA node
It seems to me your network topology looks like a club of several nodes.? John has some examples of club forwarding in the documentation. Have you seen that? I don't think I would mark any local user as a BBS that was not actually a BBS. I think you will get unexpected results, and the results may vary depending on the user software used. If your network of nodes is not forwarding to any outsiders, then addressing your B messages as all@ww would keep the messages within the network, and all BBSs would be sent all messages. If any BBS connected to the outside world then your messages might get sent out in the wild. Addressing them to ALL@GROUP might be better.? GROUP will need to be in the AT field of each BBS in your network. Users could pick up messages from any node, and the software would normally filter any messages already received at other nodes. Using a terminal program and accessed another node you probably would get offered messages that you already picked up.? But using Outpost PMM for example, you would not because Outpost and other softwares uses BIDS to download messages. P messages would best be distributed using a group alias in the AT field. So a personal message could be addressed to call@group and it would be distributed to all nodes that forward to GROUPNAME in the AT field, I think.? P messages could then be picked up at any node. That is, if I am reading your query right and understanding your network right. Mark
|
Picking up B messages at non HA node
Is it possible for a user to pick up B messages by connecting to a node at which they are not homed?
Running in a network of several nodes.?? Local users are checked as a BBS, as are the other node calls.? In forwarding, all BBS have an entry for their call and group bull names under TO calls.? The other nodes have the same, plus all of the other callsigns homed on that remote node.?? Forwarding of P and B messages has been working great, and a user connecting to their home node picks up everything as expected.? We're not doing any geographical based forwarding.
In some controlled tests, recently discovered that a user connecting to a different node than their HA node will not get B messages.? Not a case of BID rejection because they already got it off their HA node - it doesn't offer up any unread B msgs.? Don't know if I've just been incorrectly assuming that users could grab B msgs anywhere, or if I'm missing a nuance in the forwarding setup.
Many thanks / Ray KG7AV
|
John, et al...
I have one install that although is connected to the internet it is only for my convenience and not for traffic or any public connections. Ever,
I run RMS Relay in the local post office mode along side of BPQ so that it holds all messages. Nothing is ever forwarded to the internet or over RF.
I have it working fine, and has been for years, but I would like to change it so that the BBS acts as relay. It must hold all messages and never, ever try to forward them.
The present config file includes this in the Telnet port:
?? CMS=1????????????????????????????? ;;;;;;;;;;;;;;;;;;;;
?? CMSCALL=WA5EOC???????? ;; Are these even necesary?
?? CMSPASS=xxxxxxxxx????????? ;;;;;;;;;;;;;;;;;;;;;
RELAYHOST=10.109.47.133 8773
And the Application line is this:
APPLICATION 3,RELAY,C 3 RELAY,WA5EOC-10,EOCRMS,0
Relay is set to accept connection on
10.109.47.133 on port 8773
Again all works well, I just need to change it so that the BBS acts as relay.? I'm working remotely so I thought it much easier to ask and fix it in one remote session rather than trial and error, and error, and error....
And an FYI, changing out the computer is what solved my RF connection issue. No clue what it was....
Thanks
Mark
|
Re: Is this expected behavior on linbpq Version 6.0.22.70?
Well, John - that makes perfect sense.? I upgraded to stop the errors I was getting with a number of my downlink partners, but hadn't upgraded for a while previously.? Now I know how the line is processed, so that makes sense as well.? Thanks for the explanation!??
--
Charlie (N4NVD)
|
Re: @G8BPQ -- UZ7HO soundmodem for linux
Brett,
The sudo commands I provided were the "extra's" needed for compiling, but in hindsight you were probably missing the standard prerequisites for running the binary version.
It's all documented nicely here:
Good to know you have it working.? John was right in saying it's easier to just download the binary version and run it, and I should have mentioned that yesterday.
73, Lee K5DAT
On Thu, Jun 9, 2022 at 11:38 PM Brett Williams < KB5YZB@...> wrote:
Thanks
I ran the SUDO command successfully.
I also have the file unzip on the pi.
I issued the "qmake" command and the following is reported...
qmake: could not find a Qt installation of ''
Lee Im not sure what went wrong.......
|
Re: @G8BPQ -- UZ7HO soundmodem for linux
Thanks John, I have it working now. Now I have to set up the
port(s) in BPQ to match the device info qt sound modem.
Brett
On 6/10/2022 1:08 AM, John G8BPQ wrote:
toggle quoted message
Show quoted text
Unless you need to compile your own version you would be better
off installing a binary version - QtSoumdModem for x86 Linux or
piQtSoundModem for the Raspberry Pi.
73,
John
On 10/06/2022 00:51, Brett Williams
wrote:
Downloaded the file(s)/ moved the dir over to the Pi. What is
the execution file to start the program.??
Thanks?
Brett
|
Re: Deleting all messages & bulletins
It looks like housekeeping does work if I do it via the terminal. Running it via the web ui does not work.
|
Re: Deleting all messages & bulletins
Shut down Mail, delete DIRMES.SYS and the contents of the Mail
directory then restart.
73,
John
On 10/06/2022 12:39, Ross Wardrup
wrote:
toggle quoted message
Show quoted text
Is there a way to completely clear my mail? My node was down for a
few months and now that it's up, it wants to send a bunch of old
bulletins to folks.
I'd like to just nuke my mail. I've run "km" successfully, but it
looks like housekeeping isn't removing anything.
|
Re: Deleting all messages & bulletins
I tried that but everything is still there.
|
Re: Deleting all messages & bulletins
Try going to Housekeeping under the Main Configuration, then set
all lifetimes to something you would prefer such as 15 days. Then
run Housekeeping twice.
On 6/10/2022 7:39 AM, Ross Wardrup
wrote:
toggle quoted message
Show quoted text
Is there a way to completely clear my mail? My node was down for a
few months and now that it's up, it wants to send a bunch of old
bulletins to folks.
I'd like to just nuke my mail. I've run "km" successfully, but it
looks like housekeeping isn't removing anything.
|
Deleting all messages & bulletins
Is there a way to completely clear my mail? My node was down for a few months and now that it's up, it wants to send a bunch of old bulletins to folks.
I'd like to just nuke my mail. I've run "km" successfully, but it looks like housekeeping isn't removing anything.
|
John Hays - K7VE / WRJT-215
Ray Spreier-KG7AV