开云体育

I was wondering if anyone has used a small lcd display for there Shari node. ?Maybe in a 3d printed case?

Fingers crossed I think I got it. Not sure where the RF is coming from but I switched to dcs and so far that seems to have fixed the probably. [email protected]> wrote:

There is a DMR VHF Repeater a block away from me, used by Local Police I catch occasional front end overload from it from time to time. That’s why my home AllStar node is 70cm ;-) Fred McGuire -

I had my node connected to a local repeater on allstar and got booted because it kept keying that system... Interested to see what fixes it.. Also if you have any additional installation software (ie

That is a digital (dmr, fusion, d-star) transmission.? Do you have a mmdvm node at your location on the same frequency (or nearby frequency that might be overloading the frontend of the SHARI

Colin, Are you running ASL 2 or ASL 3? Dean - KC9REN

Colin, I just watched Freddie Mac's video about this last night.? Here a link.? He's got a ton of informative videos out there on Allstar nodes. ?https://youtu.be/odYKcSzUqpE?si=uCNUVpC0zkYtzUAj

Is it a "sign-in"? feature or? "sing-in"? feature as you posted?

I have my shari node at home and would like to take it to work so while I'm at work for 10 hours a day I could get a chance to use it, right now it sits at home not even turned on, my question is how

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

In simpleusb be sure you set CTCSS FROM to 'no' Here is a link to our suggested settings for ASL3 on SHARI /g/SHARI/files/ASL3

I have 2 nodes that were running hamvoip. I downloaded a fresh asl3 image and went through the config. Everything looks good, but the node does not key up. I tried my other node, same thing. Not sure

I wanted to update this thread. I was able to resolve the issue by trying another SD card and downloading the very latest image from ASL. I did try updating the image I downloaded a couple weeks ago,

It was, but the problem seems to be fixed.73Steve KL7SB?Sent via the Samsung Galaxy S24 Ultra, an AT&T 5G smartphone

Patrick, your spotting of the IP address conflict was the issue. Nice work!! The problem has been resolved. I just spoke with the node operator, KB0P, and it turned out the IP conflict was caused by

It wouldnt happen to have been the East Coast Reflector, would it? there were fiber issues with their ndoes yesterday, and still lingering today...

Good luck. That node has been up for a long time, so maybe just restarting it will magically fix the registration thing.

Hi all, I am getting many "connection failed" when attempting to connect to different reflectors, but not always, and I don't see much of a pattern. I'm unable to connect to the East Coast reflector

Thanks for the excellent suggestions. 1. Confirming "Connection Failed": Thanks for trying the connection. Others having the same problem is somehow a good thing? lol 2. ASL3 Update Node List & Node

Greetings: For some reason, the reported address is not correct using nodes.allstarlink.org for node 48579. 48579.ip.hamvoip.org resolves to 204.38.204.189. This works. 48579.nodes.allstarlink.org,