Friday Night HAM Radio NET

  • HTML tutorial

Unbound4R

Rank IV
Launch Member

Influencer II

1,213
Leander, TX, USA
First Name
Mike
Last Name
Binder
Member #

15582

Ham/GMRS Callsign
W6UXD / WSHR980
  • Like
Reactions: KD7WCD

KD7WCD

Rank VI
Founder 500
Member
Investor

Influencer I

3,002
Tempe, AZ, USA
First Name
Jayson
Last Name
Adamsen
Member #

399

Ham/GMRS Callsign
KD7WCD
I'll do all I can to make it. It is at 7PM so that is in the middle of a trasit time.
 

Unbound4R

Rank IV
Launch Member

Influencer II

1,213
Leander, TX, USA
First Name
Mike
Last Name
Binder
Member #

15582

Ham/GMRS Callsign
W6UXD / WSHR980
I'll do all I can to make it. It is at 7PM so that is in the middle of a trasit time.
This is why I’ve got it on EchoLink and Allstar this time around. Lots of ways to connect with that combination and you can ask your local repeater to connect to the AllStarLink. My local repeater invited me to connect to their reapeter during it.
 

Prerunner1982

Local Expert, Oklahoma USA
Launch Member
Member

Member III

3,372
Navina, Oklahoma
First Name
Jon
Last Name
B
Member #

16274

Hi everyone,

Getting everything finalized for the net this Friday! Just a quick heads-up that I needed to update the connection details I previously shared due to some tweaks during testing and a correction on my initial information. Please make sure to check the connection details below carefully before joining the net.

Looking forward to chatting with you all as we work on bringing some life back to this net!

Connection Details:
  • EchoLink Node: W6UXD-R (Node 448622)
  • Allstar Node: 64658
Connecting via Allstar: Allstar users can connect to node 64658. If you are using a connected radio, you will typically dial *3 followed by the node number (e.g., *364658) to connect. If you are using an Allstarlink interface on your computer, you can usually enter the node number directly.

EchoLink Information: If you're new to EchoLink, you'll need to register your call sign with EchoLink and have your license validated by them. Once that's done, you can connect using their software on your phone, tablet, or computer.

Why the change? To make the net accessible to a wider audience, including those on Allstar, we're using both EchoLink and Allstar. It's important to note that EchoLink's rules prevent conference nodes from being directly linked to other VoIP systems.
Is W6UXD-R only visible when when the net is active. I passed the word around and someone reached out saying they don't see that node, even had them try 448622 with no luck.
Thank you
Jon
 

Unbound4R

Rank IV
Launch Member

Influencer II

1,213
Leander, TX, USA
First Name
Mike
Last Name
Binder
Member #

15582

Ham/GMRS Callsign
W6UXD / WSHR980
Hi everyone,

Getting everything finalized for the net this Friday! Just a quick heads-up that I needed to update the connection details I previously shared due to some tweaks during testing and a correction on my initial information. Please make sure to check the connection details below carefully before joining the net.

Looking forward to chatting with you all as we work on bringing some life back to this net!

Connection Details:
  • EchoLink Node: W6UXD-R (Node 448622)
  • Allstar Node: 64658
Connecting via Allstar: Allstar users can connect to node 64658. If you are using a connected radio, you will typically dial *3 followed by the node number (e.g., *364658) to connect. If you are using an Allstarlink interface on your computer, you can usually enter the node number directly.

EchoLink Information: If you're new to EchoLink, you'll need to register your call sign with EchoLink and have your license validated by them. Once that's done, you can connect using their software on your phone, tablet, or computer.

Why the change? To make the net accessible to a wider audience, including those on Allstar, we're using both EchoLink and Allstar. It's important to note that EchoLink's rules prevent conference nodes from being directly linked to other VoIP systems.
Is W6UXD-R only visible when when the net is active. I passed the word around and someone reached out saying they don't see that node, even had them try 448622 with no luck.
Thank you
Jon
Thank for letting me know. It looks like it was having issues connecting to the EchoLink servers. Fixed now.
 
  • Like
Reactions: Prerunner1982