Keyboard Shortcuts
Likes
- SHARI
- Messages
Search
Re: Uninstall Supermon
You can run both they will not interfere with each other.? If you want to remove it on ASL it is located in the /var/www/html/supermon. Or on hamvoip /srv/http/supermon.? Just delete the directories and it will be gone On Thu, Mar 16, 2023, 12:01 AM Mark VE3JMR <ve3jmr@...> wrote: Anybody know how to do this and still leave Supermon2 intact? |
Uninstall Supermon
Anybody know how to do this and still leave Supermon2 intact?
<X><
73 75 Mark? VE3JMR | VE3MR Port Colborne, Ontario,?CANADA
Allstar Node# 531320??Echolink Node# 736666 LIFE has an EXPIRY date. No Trees were harmed in creating this message although many electrons were inconvenienced.
|
Re: Using the SHARI in Other Projects
#PiHat
Yes - as long as your app can use the CM108B USB sound chip.? DireWolf is an example of another? application that will run on a SHARI.
/g/direwolf |
Using the SHARI in Other Projects
#PiHat
I got to thinking about this, not that I have any immediate ideas, but is possible to control the SHARI using our own applications where we control the PTT without using the AllStar node?
Chris N9XCR |
Re: Connection to node on same Network failed
Final update.?
?It appears re-booting helps.? I can connect to all my nodes now expect cannot connect t 585243. Will boot that one tomorrow morning an expect it be that will take care of it. It took care of 585240 and 585241,. Thanks for everyone's help Dave/AD4UU |
Re: Updated SimpleUSB instructions
#SA818-prog
¿ªÔÆÌåÓýThanks Patrick. Well said. ? 73 from another screenreader user. Chris ? ? From: [email protected] <[email protected]> On Behalf Of Patrick Perdue
Sent: March 15, 2023 10:31 AM To: [email protected] Subject: Re: [SHARI] Updated SimpleUSB instructions #SA818-prog ? Hi Steve: I noticed that the suggested settings in this file are listed in an image, which isn't particularly useful for those of us with screen readers. I can scrape it with OCR, but it isn't very accurate. On all my HamVoIP systems, I like to turn the DSP value way down, usually from 999 to 200, then increase the Tx Channel A level to compensate for that. This results in far less clipped/squished TX audio from the SHARI. I also turn the rxaudiodelay value up, usually between 6 and 8, so people don't hear my squelch tail when I unkey. I've noted that many SHARI users don't do this. It isn't necessary, but it's nice. ? Just as an example, this is how that part of the PDF appears to my OCR scraping. It's pretty mangled. ? Reacrse Burst: n On 3/14/2023 9:06 AM, N8AR wrote:
|
Re: Updated SimpleUSB instructions
#SA818-prog
¿ªÔÆÌåÓýHi Steve: I noticed that the suggested settings in this file are listed in an image, which isn't particularly useful for those of us with screen readers. I can scrape it with OCR, but it isn't very accurate. On all my HamVoIP systems, I like to turn the DSP value way down, usually from 999 to 200, then increase the Tx Channel A level to compensate for that. This results in far less clipped/squished TX audio from the SHARI. I also turn the rxaudiodelay value up, usually between 6 and 8,
so people don't hear my squelch tail when I unkey. I've noted that
many SHARI users don't do this. It isn't necessary, but it's nice.
Just as an example, this is how that part of the PDF appears to
my OCR scraping. It's pretty mangled.
Reacrse Burst: n On 3/14/2023 9:06 AM, N8AR wrote:
Hi Mark, |
Re: Connection to node on same Network failed
Thank you all for your help.? ?I have made some progress.
Node 585240:? I can connect to 585241, This is the only connection I can make on all nodes.
?
585240 = [email protected]:4569/585240,NONE
585241 = radio@...:4568/585241,NONE?
585243 = radio@...:4566/585243,NONE
?
Node 585241
?
585241 = [email protected]:4568/585241,NONE
585240 = radio@...:4569/585240,NONE
585243 = radio@...:4566/585243,NONE
?
Node 585243
?
585243 = [email protected]:4566/585243,NONE
585241 = radio@...:4568/585241,NONE
585240 = radio@...:4569/585240,NONE |
Re: Connection to node on same Network failed
¿ªÔÆÌåÓýThe [nodes] section posted below indicate that all 3 nodes are on one server. I'm going to assume you want 3 different servers. Assuming this: 585240 = 192.168.1.9 Port = 4569 585241 = 192.168.1.8 Port = 4568 585243 = 192.168.1.7 Port = 4566 On node 585240, you should have this: 585240 = [email protected]:4569/585240,NONE
585241 = [email protected]:4568/585241,NONE ; This should be the LAN IP address of node 58241 585243 = [email protected]:4566/585243,NONE ; This should be
the LAN IP address of node 58243
|
Re: Connection to node on same Network failed
Bill KD2EOY
¿ªÔÆÌåÓýTry changing the ip address to the actual ip address of the nodes instead of the 127.0.0.1. That¡¯s how I got mine to work. ? Bill Paulus?? ? KD2EOY Allstar Node #526084 (609) 694-7976 Vice President SCARA? Southern Counties Amateur Radio Association ? ? ? From: [email protected] <[email protected]> On Behalf Of Dave Livesay ? Hello again, 585241 = [email protected]:4568/585241,NONE 585243 = [email protected]:4566/585243,NONE 585240 = [email protected]:4569/585240,NONE |
Re: Connection to node on same Network failed
Thank you Patrick. I have not done that.? I will give that a try.? Thank?you. On Tue, Mar 14, 2023 at 9:39?AM Patrick Perdue <borrisinabox@...> wrote:
|
Re: Connection to node on same Network failed
Hello again,
Made the following changes to the RPT.conf file.? ?I am still getting connection failed. 585241 = [email protected]:4568/585241,NONE
585243 = [email protected]:4566/585243,NONE
585240 = [email protected]:4569/585240,NONE |
Re: Connection to node on same Network failed
Dave: Have you defined each of the nodes on your LAN in the [nodes] section of every node in rpt.conf? Generally, you are only supposed to do this with private nodes, but it works just as well for connecting publicly accessible nodes that exist on the same LAN together. ? On 3/14/2023 9:05 AM, Dave Livesay wrote:
Hello all, |
Connection to node on same Network failed
Hello all,
I have three nodes and all have port forwarding enabled and They have no problem with an external connection. But when I try to connect to one another on my home network I get connection failed and the following message in the log file:? Any thoughts would be appreciated. Thanks Dave/AD4UU Mar 14 08:54:34] WARNING[26241] app_rpt.c: Node 585241 IP 67.232.183.171 does not match link IP 192.168.50.1!! |
Re: Updated SimpleUSB instructions
#SA818-prog
Hi Mark,
I have uploaded the document to the File section of this group. /g/SHARI/files/Suggested Change in SHARI Setup.pdf Steve - N8AR |
Updated SimpleUSB instructions
#SA818-prog
I purchased a PiZero Hat that included updated instructions for setting up the audio with simpleusb. I have misplaced those instructions. Is that document available or can the new settings be given here? Unless I missed it, I could not find an update instruction in Files for this group.
<X><
73 75 Mark? VE3JMR | VE3MR Port Colborne, Ontario,?CANADA
Allstar Node# 531320??Echolink Node# 736666 LIFE has an EXPIRY date. No Trees were harmed in creating this message although many electrons were inconvenienced.
|
Re: Channel changing script
¿ªÔÆÌåÓýchannel.sh is the script that I pasted in the email. ? You would need to create it and modify it with your desired channels and settings. ? -Michael ? From: [email protected] <[email protected]>
On Behalf Of Mark VE3JMR
Sent: Monday, March 6, 2023 12:28 AM To: [email protected] Subject: Re: [SHARI] Channel changing script ? Michael; <X>< Port Colborne, Ontario,?CANADA LIFE has an EXPIRY date. No Trees were harmed in creating this message although many electrons were inconvenienced. |
Re: Channel changing script
Michael;
I'm not a programmer but I can get through some things. I'm missing something with your instructions. 1. I cannot find "channel.sh" -- channel1 or --channel2 or --channel3 in /etc/asterisk/local nor can I find channel.sh? 2. What is the script called I have to make and put in /usr/bin/ ?? 3. Nothing in the script seems to point back to channel.sh I'm lost here. <X><
73 75 Mark? VE3JMR | VE3MR Port Colborne, Ontario,?CANADA
Allstar Node# 531320??Echolink Node# 736666 LIFE has an EXPIRY date. No Trees were harmed in creating this message although many electrons were inconvenienced.
|