开云体育

So, I built my brother a shari and it's linked to mine pretty much 24/7. We usually chat while he walks the dog, etc. Our experience with the range he has is kind of confusing and I'm looking for ideas from you all of what we should be looking at. Here's our experience: Once he gets a certain distance from his house, in any direction, his Shari starts dropping out. The weird thing is his signal is very strong into the Shari and he has no issue receiving my signal from his Shari. Our last test was in a new direction, and when referencing a map, it's only about 500' from his house. It seems to be about 500' in any direction this starts happening. Some things we have tried: He will switch HT from 1w out to 5w out - no change Tried different PL tones Tried no PL tone at all Moved shari location to avoid possible interference Moved shari to 2nd floor What we have not tried is changing shari frequency. We're in Wisconsin and the Wisconsin band plan recommends going below 430mhz (don't have it in front of me) for links/hotspots. His Shari is around 425mhz. We have put the Shari antenna on a VNA and noted that it is not optimal for 425mhz, but again, the issue is with the Shari rx, not tx. He can hear the Shari perfectly from further than he can tx into it with 5w. We've talked about testing a frequency above 430mhz, but does anyone have any other ideas to offer? I've read a lot of posts about range, and I'm not expecting miles here, just more than 500'.

Hello: This message is about the excellent customer support by the great folks at Kits4Hams. A while back I ordered a SHARI-Pi and there was a problem with the delivery/order. I advised Kits4Hams and Deb got right back to me. After some detective work we understood the problem. Deb and the owners at Kits4Hams went above and beyond in their response and I am very happy to recommend them for their great support. I have been a licensed ham since 1956 and hav had a lot of interaction with makers and Kits4Hams is as good as it gets. Thanks to Deb and the other K4H folks. V73, Larry Hower VK7WLH W0LH

I am getting snagged up with some intermittent serial port connectivity to the SA818 module on a Pi 5 with: "Linux allstar 6.6.62+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.6.62-1+rpt1 (2024-11-25) aarch64 GNU/Linux" "Model : Raspberry Pi 5 Model B Rev 1." using the basic sa818 program (https://allstarlink.github.io/adv-topics/sa818modules/#sa818-menu), which is used by sa818-menu. I see this (below) when issuing a simple command to query the firmware version of the device. The program flops back an forth from successful to an error. I have "console=ttyAMA0,115200" at the end of /boot/firmware/cmdline.txt, and dtparam=uart0 dtoverlay=disable-bt set in /boot/firmware/config.txt. Could the problem be that my soldering on the TP68 or TP69 "pins" is less than ideal, or could this be from something else? An aside, ttyAMA0 is never symlinked to /dev/serial0, but ttyAMA10 is, i.e., /dev/serial0 -> ttyAMA10. Any pro tips would be appreciated. Examples: root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version') SA818: DEBUG: Serial<id=0x7fff5267b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False) SA818: DEBUG: Sending: AT+DMOCONNECT SA818: DEBUG: Port /dev/ttyAMA0 not SA818: Connection error root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version') SA818: DEBUG: Serial<id=0x7fff9bb2b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False) SA818: DEBUG: Sending: AT+DMOCONNECT SA818: DEBUG: Sending: AT+VERSION SA818: WARNING: device reports readiness to read but returned no data (device disconnected or multiple access on port?) root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version') SA818: DEBUG: Serial<id=0x7fff7b65b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False) SA818: DEBUG: Sending: AT+DMOCONNECT +DMOERRORBUG: Port /dev/ttyAMA0 not SA818: D Connection error root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version') SA818: DEBUG: Serial<id=0x7ffed2b3b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False) SA818: DEBUG: Sending: AT+DMOCONNECT SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR Connection error root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version') SA818: DEBUG: Serial<id=0x7fff5568b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False) SA818: DEBUG: Sending: AT+DMOCONNECT SA818: DEBUG: Sending: AT+VERSION SA818: INFO: Firmware SA818, version: V5.5_MM root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version') SA818: DEBUG: Serial<id=0x7fff2458b940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False) SA818: DEBUG: Sending: AT+DMOCONNECT SA818: DEBUG: Port /dev/ttyAMA0 not SA818: +DMOERROR Connection error root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA818: DEBUG: Namespace(debug=True, port='/dev/ttyAMA0', speed=9600, func='version') SA818: DEBUG: Serial<id=0x7fff7bdfb940, open=True>(port='/dev/ttyAMA0', baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0, xonxoff=False, rtscts=False, dsrdtr=False) SA818: DEBUG: Sending: AT+DMOCONNECT SA818: DEBUG: Sending: AT+VERSION SA818: INFO: Firmware SA818, version: V5.5_MM root@allstar:# sa818 --debug --port /dev/ttyAMA0 version SA

Hey Folks, I'm using ASL3 on my SHARI PiZero, everything's up to date. When I de-key there's a gap of about 1 second while the node sends back silence, then the courtesy tone. I'd like that gap to be much shorter but the only way I can find of doing it is changing duplex to 0 from 1. I quite like the courtesy tones, just not the gap. Any ideas? rpt.conf:duplex = 1 rpt.conf:hangtime = 0 rpt.conf:althangtime = 0 rpt.conf:;nounkeyct = 0 ; Set to a 1 to eliminate courtesy tones and associated delays. simpleusb.conf:rxondelay = 0 simpleusb.conf:txoffdelay = 0 simpleusb.conf:rxaudiodelay = 10 ; experimental - does this do anything? GD5MUP

Mark: I do, in fact, use usbradio instead of simpleusb on ASL3, mostly for one reason... squelch tail elimination. HamVoIP's version of simpleusb has a parameter, called rxaudiodelay, which can effectively eliminate the squelch tail from your transmissions to the network. ASL's version doesn't have this feature, but usbradio has an equivalent, called rxsquelchdelay. This parameter in ASL is set in milliseconds, wherein HamVoIP's simpleusb equivalent is set in frames, which are 20 milliseconds long each. So, rxaudiodelay=5 in HamVoIP's simpleusb.conf would be like rxsquelchdelay=100 in ASL's usbradio.conf. I noticed a fun thing. N8AR could provide more info here, but I guess at some point, something about the SA818's changed. IT must have been in pretty recent times. I've had several SHARIs, mostly from 2019/2020. I recently bought a SHARI pihat for a friend, and discovered that it actually does pass discriminator audio, or close enough to it, unlike all of mine prior to this one. The PL tone came all the way through with the filters off, which I have never heard with any of my SHARIs. It's always had a high pass, even with the high pass filter disabled. So, theoretically, you could use usbradio's CTCSS decoder (not sure about the encoder) which may or may not be better than using the one in the radio itself, assuming you can completely open the squelch on the SHARI with CTCSS disabled (untested by me). This particular SHARI isn't in my possession anymore, so I can't test further, as none of mine have that much audio bandwidth. My Hotspotradios full duplex box doesn't exhibit this wider audio bandwidth behavior, either. Maybe Steve has some special sauce for the SHARI design? I made a few non-standard changes to my usbradio configuration. Because I like the way it sounds, I disabled de-emphasis/pre-emphasis and the high and low pass filters on the SHARI (which is flat, even though it doesn't look like it should be), enabled the equivalent of pre/de-emphasis in usbradio (actually, it's like that by default, because it expects flat repeater audio), turned the rxmixer audio down a bit to avoid clipping with a raw PL hitting the sound fob all the time, then biased it back up very slightly in software, as usbradio can do that in it's DSP. It sounds fantastic with my TYT MD-UV380. Here is an example configuration file, where you can see what I did specifically for that node. It's pretty non-standard, but I really like the way it sounds, and DTMF decoding is right where it should be. I did this all by ear, can't see scopes and such, I programmed the SHARI thus, using almost none of the recommended settings: volume 5, pre-emphasis/de-emphasis disabled, high pass filter disabled, low pass filter disabled. NOTE: If you have an older SHARI from before whatever happened to make them sound better happened, you will probably want to just go with all of N8AR's recommended settings, I.E. volume 6, HPF/LPF and pre/de-emphasis enabled, at least from what I remember. For this particular radio, I prefer how this sounds, though. Note that all these settings are specific to the node, so anything higher that isn't explicitly defined will be ignored, as is generally the case with ASL3 configuration files. Almost all of these changes were done by hand, because usbradio-tune is... kinda broken. Try these at your own risk. YMMV. No warranty, expressed or implied, etc. ***snip*** [508420](node-main) txlimonly = no rxondelay = 10 rxboost = no txmixa = voice carrierfrom = usbinvert ctcssfrom = no ;;;;; Tune settings ;;;;; devstr = ; the actual devstr left blank in this example, as your ID will most likely be different. It can be found with sudo asl-find-sound and placed here rxmixerset = 400 txmixaset = 700 txmixbset = 700 rxvoiceadj = 1.400000 ; rxvoiceadj might be a little off here, not sure. I have another configuration with rxmixerset = 550 and rxvoiceadj = 1.250000 rxctcssadj = 0.500000 txctcssadj = 0 rxsquelchadj = 0 fever = 1 rxsquelchdelay=100 txtoctype = no ; Transmit tone control type: no,phase,notone ; no - CTCSS tone encoding with no hang

I have ASL3 on my Shari Node. When I use the sudo command with the 1st user (UID 1000), I am NOT asked for my password...Perfect! IF I add a 2nd user (UID 1001), when I use the sudo command, it WILL ask me for my password, I don't want that to happened. Both users are members of all the same groups, including SUDO I would like to get rid of the 1st user, use the 2nd user and not be asked for my password when using a SUDO command or if I can rename the 1st user and just delete the 2nd user, that would be fine too How do I fix this? 73 Tim

I upgraded my Shari PiHatU to ASL3. Everything works great except I don't get the IP announcement anymore. Is there a fix for this Thanks, Tim 73

I want to run all star link on my quantar. There is no clear answer on how this connects. Can I use this SHARI device on my input and output of my machine or does this work directly connected to my quantar repeater.

I have had my Shari Pi3U up and running since mid 2022 (nearly 3 years) without any issues until recently. The node will transmit but will not receive, I did not make any changes or adjustments from when it did receive to when it stopped receiving. First step I tried a reboot (incl from backup image), but no dice. Next I tried to reprogram the SA 818 (ran SA818-prog) everything took just fine but no go still no receive. I checked the receive by toggling COS in the simple USB tune menu and the software side is good (supermon status, curiosity tones, etc.) however the COS LED on the Shari does not illuminate. This lack of COS LED illumination on the actual Shari leads me to believe I have a hardware not a software issue. This is where I have reached the end of my testing abilities to troubleshooting this issue and hoping someone can provide some recommendations or guidance.

Hello, Upon reading this "https://www.hamvoip.org/howto/howto-broadcast-your-allstar-node.pdf", I tried to apply this to my node, however, I ran ezstream -qvc /etc/ezstream.xml and link connected to the [stream a], so I tx, and nothing is heard from the stream. I rechecked the lines and have the "outstreamcmd = /bin/sh,-c,/usr/bin/lame --preset cbr 16 -r -m m -s 8 --bitwidth 16 - - | /usr/bin/ezstream -qvc /etc/ezstream.xml" to my node. Does anyone know what I am missing to get this working? Many thanks in advance, Abby

All of a sudden my node started to key itself up randomly. I have tried increasing the squelch and changing the frequency on it. If I leave it connected to a parrot node that is the sound it broadcasts but when I listen to the frequency input I never hear any rf going into the pi4U. Tried replacing power supply and even tried a new pi but still having issues. Not sure If it's time for a new pi4U or what else it could be.

Hello, I’m using a Shari Pi Hat Allstar node with Supermon for almost 2 years and it’s working fine. I now want to make some modifications to my Supermon favorites list. I’ve used MobaXterm in the past to do this. Since last using MobaXterm, I’ve upgraded my PC to Windows 11 from 10 and added a new main router. Now when I access Mobaxtem, the admin menu does not automatically pop up so I cannot make the edits. Plus, I noticed that the Shari node’s IP address has changed and my password from the previous IP address no longer works. As I stated above, the node is working fine, it’s just getting MobaXterm to cooperate and let me make changes. Is there a work around or command that I can use to bring that menu up? Something else? Thanks in advance for any advice you might have to help me out. 73s, Dan

Hi All, not sure if this has been asked before, but my Pi3BU USB Shari transmits noise 50KHz off the frequency, for example 439.100 is is the main freq, but every time it transmits it opens up radios nearby on 439.150 with lots of noise Is this a "known" issue? Art

Is there some strange setting we are missing? My friend can connect to my node at my house when I have my SHARI connected, but when I replace it with my Clearnode, he cannot connect with his SHARI node. Thanks for reading. -- Brian WA6JFK Los Angeles

Has anyone here seen this issue with WiFi Manager in ASL3? I'm exploring AllStarLink with a SHARI PiHatU build. Didn't run into any issues during a fairly simple assembly. On a Windows 10 PC, using Raspberry Pi Imager v1.9, I burned a new image for a Pi4 4GB using the current ASL3 image download (allstar3-arm64-3.0.15.img.xz). I very carefully followed both the ASL3 and SHARI instructions from start to finish including adding my home WiFi details and region (US) info to the initial install. The new node booted, connected to my home network via WiFi normally, and found no updates. Looking at my ASL3 Web Admin Portal I see two issues... 1) My logs show a single error entry: "nl80211: kernel reports: Registration to specific type not supported" (wpa_supplicant). This is interesting as I'm told ASL3 uses it's own WiFi Manager and not wpa_supplicant so the latter shouldn't be running. 2) My WiFi Manager's Configured WiFi Networks section doesn't show my home network "Preconfigured" as it should. Instead I see "WiFi set failed" in red. Further, When I go to add other known WiFi networks it says "successful" even though they don't show as saved. I've posted about this issue over on the AllStarLink Community. After answering a number of questions about my install no solutions have emerged so far. I seem to be able to use my node, connecting/disconnecting to and talking on other nodes, without issue. However, given the intent of this node is to be portable, not being able to reliably add other WiFi networks I often encounter is a non-starter. As a troubleshooting step I tried a re-image with "allstar3-arm64-3.0.15.img.xz"... the same issues arose. I then used a new card and the slightly older "allstar3-arm64-3.0.14.img.xz" file. The node booted, found no updates, and I ended up with the same issues again. I then tried using the slightly older still "allstar3-arm64-3.0.13.img.xz" file. The node booted, found no updates, and this time the WiFi manager seems to be working normally. However, I still see the above mentioned error in my log ("nl80211: kernel reports: Registration to specific type not supported" (wpa_supplicant). At this point I welcome any thoughts and/or troubleshooting advice someone might be able to offer.

Hi all. I've successfully upgraded my Pi3U node to ASL after watching numerous videos and scanning this group. I now want to upgrade my Pi3V node to ASL. Can I copy my Pi3U SD card and load it on the Pi3V and make needed changes such as node number, sa818-menu, etc. vs. starting from scratch? Thoughts? Thx 73 K5LK

Hi I was testing a new HT and antenna set up on SHARI and I wanted to see how well it worked. I tried to connect my node to 55553 as recommended in the SHARI instructions to test the sound quality and as soon as the last DTMF tone is sent and the PTT is released I get the hung high pitch sound that will not stop until I unplug the SHARI and plug it in again. This seems to repeat every time. I noticed when I connect to the echolink parrot server I do not get the high pitch and everything works just fine. It's just the 55553 one that does that. I don't know if it's the server having problems or either my radio or HT. Has anyone encountered this?