# Get Started with AllStar - Hardware Requirements

**URL:** https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015
**Category:** AllStarLink
**Created:** [January 2, 2021, 8:36pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015 "2021-01-02T20:36:21Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![KD5BS](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/47e85d/32.png) [@KD5BS](https://community.allstarlink.org/u/KD5BS)
#### Post date: [January 2, 2021, 8:36pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/1 "2021-01-02T20:36:21Z")

</div>

I am considering using AllStar to link two Club repeaters together. I have read pretty much all of the Wiki information regarding the Software setup and installation so am prepared for that effort.  
What is unclear to me is the actual hardware and connection requirements. Let me explain a bit…  
We have two Yaesu DR-2X repeaters that are about 10 miles apart - one is a 2 meter machine and the other is a 440 machine. Both have Internet available.  
I am prepared to build AllStar nodes (which are already registered) on Raspberry Pi 4 SBCs. I haven’t run across any documentation the details the actual hardware requirements Is there a document that describes and shows a schematic of how to put together a connection to a repeater including any RPi Hats, Interface devices, cables etc. If someone has undertaken this project with a Yaesu DR02X repeater, I would very much appreciate your guidance and input on how to proceed.  
;I might also mention that we want to implement a DVSwitch capability to bridge DMR to Analog for these repeaters as well so any details about this implementation would also be appreciated. For example, 1) should the DVSwitch be installed on a separate RPi?, 2) if repeaters are in separate locations is it necessary to have a separate RPi at each repeater or can one RPi support both repeaters and if so, how?  
I realize that this is basic stuff for many of you and believe me, I would not be asking this if I had found information that describes my particular scenario.  
If anyone can provide some assistance and Elmering on this project, I would appreciate it.  
Thanks

---

<div class="post-metadata">

### Author: ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)
#### Post date: [January 3, 2021, 12:37am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/2 "2021-01-03T00:37:13Z")

</div>

Welcome to AllStar. You have a fun journey in front of you.

1. I’m no DVSwitch expert but I’m pretty sure it has to be on the same host.

2. With a “sound fob” like the ones below you do need a computer at each repeater location.

> **[Masters Communications](https://www.masterscommunications.com)**

However you can use an RTCM at each location and one computer at any location. Ask me for more info if interested.

---

<div class="post-metadata">

### Author: ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)
#### Post date: [January 3, 2021, 1:11am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/3 "2021-01-03T01:11:50Z")

</div>

To add to Tim’s reply…  
Get the allstar running as needed, the working hardware interface’s etc, then add your dvswitch

When you get to that spot… join dvswitch forum on [www.groups.io](http://www.groups.io)

Welcome aboard !

---

<div class="post-metadata">

### Author: ![KD5BS](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/47e85d/32.png) [@KD5BS](https://community.allstarlink.org/u/KD5BS)
#### Post date: [January 3, 2021, 6:03am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/4 "2021-01-03T06:03:42Z")

</div>

Thank you for the replies.

I agree on the approach recommended that the AllStar device should be up and running first before adding DVSwitch. That is the plan. However, what I am quite unsure about are the components that are needed to get the AllStar device working.

- I have a Raspberry Pi 4 already
- I have downloaded the image from [AllstarLink.org](http://AllstarLink.org)
- Tim indicated that a sound fob was needed and provided a link to a site but there are lots of devices for sale so a specific recommendation would be appreciated. Is it possible that there is an RPi HAT available to provide this sound fob function or must it be a USB device?
- Tim also indicted that I could use an RTCM at each location and an RPi computer at only one location. I’m not sure what an RTCM is but would assume that it is some sort of radio interface.
- I would also assume that there are cables needed – what kind, I don’t know.
- I have Yaesu DR-2X repeaters

Right now, I am assuming I will use:

- 2 x Raspberry Pi computers – one at each repeater site.
- 2 x Sound Fobs – one at each location
- 2 x Cables from the DB9 connector on the Sound Fob to the Repeater (probably custom made)

Assuming that this will get AllStar running and connected to the repeaters, is ther anything else that will be needed to LINK the two repeaters together via Analog?

Sure wish there was some sort of technical schematic available, even is a simple form that would help explain this basic hardware requirement. I realize that there are lots of different scenarios out there and that schematics or block diagrams for each would be problematic to maintain but hoping that someone has documented this to make it easier for noobs.

If I could get a specific recommendation on the Sound Fob, that would be a great start. If a HAT for the RPi is available that would make for a clener installation.

Thanks and I’m sure I’ll be asking for more help, especially regarding the DVSwitch and how to implement that.

Regards to all.

> **···**
>
> **From:** Mike via AllStarLink Discussion Groups [noreply@community.allstarlink.org](mailto:noreply@community.allstarlink.org)  
> **Reply-To:** AllStarLink Discussion Groups [replies+6f217c37b264720fbe60009f3eb17d34@community.allstarlink.org](mailto:replies+6f217c37b264720fbe60009f3eb17d34@community.allstarlink.org)  
> **Date:** Saturday, January 2, 2021 at 7:21 PM  
> **To:** Robert Stroud [rstroud@istroud.com](mailto:rstroud@istroud.com)  
> **Subject:** [AllStarLink Discussion Groups] [App\_rpt-users] Get Started with AllStar - Hardware Requirements
> 
> |   
>   
> ![https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/45/1569_2.png](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/45/1569_2.png)  
>   
> |   
>   
> [**Mike**](https://community.allstarlink.org/u/mike)  
> January 3  
>   
> |
> | --- | --- |
> 
> To add to Tim’s reply…  
> Get the allstar running as needed, the working hardware interface’s etc, then add your dvswitch
> 
> When you get to that spot… join dvswitch forum on [**www.groups.io**](http://www.groups.io)
> 
> Welcome aboard !
> 
> * * *
> 
> [**Visit Topic**](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/3) or reply to this email to respond.
> 
> To unsubscribe from these emails, [**click here**](https://community.allstarlink.org/email/unsubscribe/44c88db9747542d5d4852a422f4c559b320e1296380cead318a791fff15587a9).

---

<div class="post-metadata">

### Author: ![KM4VPG](https://community.allstarlink.org/user_avatar/community.allstarlink.org/km4vpg/32/1268_2.png) [@KM4VPG](https://community.allstarlink.org/u/KM4VPG)
#### Post date: [January 3, 2021, 7:12am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/5 "2021-01-03T07:12:13Z")

</div>

You can get a URI or CM-119 sound fob but you have to modify it and URI does not have to be modified. [hamovip.org](http://hamovip.org) tells how to do everything to set up an allstar node. I have used this web page 2 times to set up 2 nodes.

> **···**
>
> On Sun, Jan 3, 2021 at 12:13 AM Robert Stroud via AllStarLink Discussion Groups \<[noreply@community.allstarlink.org](mailto:noreply@community.allstarlink.org)\> wrote:
> 
> > > ![](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/47e85d/45.png "KD5BS") | [KD5BS](https://community.allstarlink.org/u/kd5bs)  
> > > January 3 |
> > > 
> > > - | - |
> > 
> > Thank you for the replies.
> > 
> > I agree on the approach recommended that the AllStar device should be up and running first before adding DVSwitch. That is the plan. However, what I am quite unsure about are the components that are needed to get the AllStar device working.
> > 
> > - I have a Raspberry Pi 4 already
> > - I have downloaded the image from [AllstarLink.org](http://AllstarLink.org)
> > - Tim indicated that a sound fob was needed and provided a link to a site but there are lots of devices for sale so a specific recommendation would be appreciated. Is it possible that there is an RPi HAT available to provide this sound fob function or must it be a USB device?
> > - Tim also indicted that I could use an RTCM at each location and an RPi computer at only one location. I’m not sure what an RTCM is but would assume that it is some sort of radio interface.
> > - I would also assume that there are cables needed – what kind, I don’t know.
> > - I have Yaesu DR-2X repeaters
> > 
> > Right now, I am assuming I will use:
> > 
> > - 2 x Raspberry Pi computers – one at each repeater site.
> > - 2 x Sound Fobs – one at each location
> > - 2 x Cables from the DB9 connector on the Sound Fob to the Repeater (probably custom made)
> > 
> > Assuming that this will get AllStar running and connected to the repeaters, is ther anything else that will be needed to LINK the two repeaters together via Analog?
> > 
> > Sure wish there was some sort of technical schematic available, even is a simple form that would help explain this basic hardware requirement. I realize that there are lots of different scenarios out there and that schematics or block diagrams for each would be problematic to maintain but hoping that someone has documented this to make it easier for noobs.
> > 
> > If I could get a specific recommendation on the Sound Fob, that would be a great start. If a HAT for the RPi is available that would make for a clener installation.
> > 
> > Thanks and I’m sure I’ll be asking for more help, especially regarding the DVSwitch and how to implement that.
> > 
> > Regards to all.
> > 
> > ··· [(click for more details)](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/4)
> > 
> > * * *
> > 
> > [Visit Topic](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/4) or reply to this email to respond.
> > 
> > * * *
> > 
> > #### In Reply To
> > 
> > > ![](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/45/1569_2.png "Mike") | [Mike](https://community.allstarlink.org/u/mike)  
> > > January 3 |
> > > 
> > > - | - |
> > 
> > To add to Tim’s reply… Get the allstar running as needed, the working hardware interface’s etc, then add your dvswitch When you get to that spot… join dvswitch forum on [www.groups.io](http://www.groups.io) Welcome aboard !
> > 
> > * * *
> > 
> > [Visit Topic](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/4) or reply to this email to respond.
> > 
> > You are receiving this because you enabled mailing list mode.
> > 
> > To unsubscribe from these emails, [click here](https://community.allstarlink.org/email/unsubscribe/816219f3eea7fb66c288bfc2a099cd12839d53ee4ab168c1fdb8ffb1106bc7a0).

---

<div class="post-metadata">

### Author: ![larry](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/l/47e85d/32.png) [@larry](https://community.allstarlink.org/u/larry)
#### Post date: [January 3, 2021, 8:08am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/6 "2021-01-03T08:08:09Z")

</div>

Robert,

I’m not sure if this has been overcome so this is a caution.

Perhaps someone in the know will chime in. The ASL version was not able  
to run on the Pi4 so if someone doesn’t chime and tell us differently  
you will need to run the Hamvoip version if you must install on a Pi4.  
If you have a Pi3 you should be okay.

I know Pi4 for ASL issue was being worked on by the members here but I  
personally haven;t seen where the ASL version is ready for the Pi4.

Hopefully I’m wrong but wanted to make you aware so you don’t have  
unexpected issues.

Larry - N7FM

> **···**
>
> On 1/2/21 12:46 PM, Robert Stroud via AllStarLink Discussion Groups wrote:
> 
> > [KD5BS] KD5BS [https://community.allstarlink.org/u/kd5bs](https://community.allstarlink.org/u/kd5bs)  
> > January 2
> > 
> > I am considering using AllStar to link two Club repeaters together. I  
> > have read pretty much all of the Wiki information regarding the Software  
> > setup and installation so am prepared for that effort.  
> > What is unclear to me is the actual hardware and connection  
> > requirements. Let me explain a bit…  
> > We have two Yaesu DR-2X repeaters that are about 10 miles apart - one is  
> > a 2 meter machine and the other is a 440 machine. Both have Internet  
> > available.  
> > I am prepared to build AllStar nodes (which are already registered) on  
> > Raspberry Pi 4 SBCs. I haven’t run across any documentation the details  
> > the actual hardware requirements Is there a document that describes and  
> > shows a schematic of how to put together a connection to a repeater  
> > including any RPi Hats, Interface devices, cables etc. If someone has  
> > undertaken this project with a Yaesu DR02X repeater, I would very much  
> > appreciate your guidance and input on how to proceed.  
> > ;I might also mention that we want to implement a DVSwitch capability to  
> > bridge DMR to Analog for these repeaters as well so any details about  
> > this implementation would also be appreciated. For example, 1) should  
> > the DVSwitch be installed on a separate RPi?, 2) if repeaters are in  
> > separate locations is it necessary to have a separate RPi at each  
> > repeater or can one RPi support both repeaters and if so, how?  
> > I realize that this is basic stuff for many of you and believe me, I  
> > would not be asking this if I had found information that describes my  
> > particular scenario.  
> > If anyone can provide some assistance and Elmering on this project, I  
> > would appreciate it.  
> > Thanks
> > 
> > * * *
> > 
> > Visit Topic  
> > [https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/1](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/1)  
> > or reply to this email to respond.
> > 
> > You are receiving this because you enabled mailing list mode.
> > 
> > To unsubscribe from these emails, click here  
> > [https://community.allstarlink.org/email/unsubscribe/acb8d2633d9db9c9642cfaf642a6c297980efbcc9d92cad92cc7658b0838322f](https://community.allstarlink.org/email/unsubscribe/acb8d2633d9db9c9642cfaf642a6c297980efbcc9d92cad92cc7658b0838322f).

---

<div class="post-metadata">

### Author: ![W3KKC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w3kkc/32/442_2.png) [@W3KKC](https://community.allstarlink.org/u/W3KKC)
#### Post date: [January 3, 2021, 1:31pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/7 "2021-01-03T13:31:09Z")

</div>

Since you have the Yaesu DR-2X, I recommend the Masters Communications RA-DR1X radio adapter interface. The DMK URI doesn’t have enough TX audio to modulate your repeater to full deviation without doing a lot of work. The RA-DR1X is compatible with the DR-2X repeater, and has the necessary audio. Additionally - all Masters Communications ASL compatible radio adapters use the genuine C-Media CM119A chipset. This has proven to be the best as there are plenty of issues with the CM119B that some manufacturers have chosen. I won’t get into those - unless someone want’s me to elaborate.

Full Disclosure - I’m a Board member at ASL, Inc. I financially profit from the sales of Masters Communications products. I donate 25% of my ASL product sales profit to ASL Inc., to financially support the project, and I have since 2008.

Kevin W3KKC

---

<div class="post-metadata">

### Author: ![W3KKC](https://community.allstarlink.org/user_avatar/community.allstarlink.org/w3kkc/32/442_2.png) [@W3KKC](https://community.allstarlink.org/u/W3KKC)
#### Post date: [January 3, 2021, 1:35pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/8 "2021-01-03T13:35:20Z")

</div>

Larry,

There are (at least) two Pi4 compatible client releases - not including HV. We can post links to them until we get the official ASL Git account straightened out.

---

<div class="post-metadata">

### Author: ![larry](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/l/47e85d/32.png) [@larry](https://community.allstarlink.org/u/larry)
#### Post date: [January 3, 2021, 4:22pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/9 "2021-01-03T16:22:12Z")

</div>

Kevin, Thanks for the feedback

I’ll look forward to seeing them once things get back to normal.

73  
Larry - N7FM

> **···**
>
> On 1/3/21 5:45 AM, Kevin Custer via AllStarLink Discussion Groups wrote:
> 
> > [kuggie] kuggie [https://community.allstarlink.org/u/kuggie](https://community.allstarlink.org/u/kuggie) Board Member  
> > January 3
> > 
> > Larry,
> > 
> > There are (at least) two Pi4 compatible client releases - not including  
> > HV. We can post links to them until we get the official ASL Git account  
> > straightened out.
> > 
> > * * *
> > 
> > Visit Topic  
> > [https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/8](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/8)  
> > or reply to this email to respond.
> > 
> > * * *
> > 
> > ```
> > In Reply To
> > 
> > ```
> > 
> > [larry] larry [https://community.allstarlink.org/u/larry](https://community.allstarlink.org/u/larry)  
> > January 3
> > 
> > Robert, I’m not sure if this has been overcome so this is a caution.  
> > Perhaps someone in the know will chime in. The ASL version was not able  
> > to run on the Pi4 so if someone doesn’t chime and tell us differently  
> > you will need to run the Hamvoip version if you must install on a Pi4.  
> > If you have a…
> > 
> > ```
> > Previous Replies
> > 
> > ```
> > 
> > [kuggie] kuggie [https://community.allstarlink.org/u/kuggie](https://community.allstarlink.org/u/kuggie) Board Member  
> > January 3
> > 
> > Since you have the Yaesu DR-2X, I recommend the Masters Communications  
> > RA-DR1X radio adapter interface. The DMK URI doesn’t have enough TX  
> > audio to modulate your repeater to full deviation without doing a lot of  
> > work. The RA-DR1X is compatible with the DR-2X repeater, and has the  
> > necessary audio. Additionally - all Masters Communications ASL  
> > compatible radio adapters use the genuine C-Media CM119A chipset. This  
> > has proven to be the best as there are plenty of issues with the CM119B  
> > that some manufacturers have chosen. I won’t get into those - unless  
> > someone want’s me to elaborate.
> > 
> > Full Disclosure - I’m a Board member at ASL, Inc. I financially profit  
> > from the sales of Masters Communications products. I donate 25% of my  
> > ASL product sales profit to ASL Inc., to financially support the  
> > project, and I have since 2008.
> > 
> > Kevin W3KKC
> > 
> > [larry] larry [https://community.allstarlink.org/u/larry](https://community.allstarlink.org/u/larry)  
> > January 3
> > 
> > Robert,
> > 
> > I’m not sure if this has been overcome so this is a caution.
> > 
> > Perhaps someone in the know will chime in. The ASL version was not able  
> > to run on the Pi4 so if someone doesn’t chime and tell us differently  
> > you will need to run the Hamvoip version if you must install on a Pi4.  
> > If you have a Pi3 you should be okay.
> > 
> > I know Pi4 for ASL issue was being worked on by the members here but I  
> > personally haven;t seen where the ASL version is ready for the Pi4.
> > 
> > Hopefully I’m wrong but wanted to make you aware so you don’t have  
> > unexpected issues.
> > 
> > Larry - N7FM
> > 
> > ··· (click for more details)  
> > [https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/6](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/6)  
> > [KM4VPG] KM4VPG [https://community.allstarlink.org/u/km4vpg](https://community.allstarlink.org/u/km4vpg)  
> > January 3
> > 
> > You can get a URI or CM-119 sound fob but you have to modify it and URI  
> > does not have to be modified. [hamovip.org](http://hamovip.org) [http://hamovip.org](http://hamovip.org) tells how  
> > to do everything to set up an allstar node. I have used this web page 2  
> > times to set up 2 nodes.
> > 
> > ··· (click for more details)  
> > [https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/5](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/5)  
> > [KD5BS] KD5BS [https://community.allstarlink.org/u/kd5bs](https://community.allstarlink.org/u/kd5bs)  
> > January 3
> > 
> > Thank you for the replies.
> > 
> > I agree on the approach recommended that the AllStar device should be up  
> > and running first before adding DVSwitch. That is the plan. However,  
> > what I am quite unsure about are the components that are needed to get  
> > the AllStar device working.
> > 
> > - I have a Raspberry Pi 4 already
> > - I have downloaded the image from [AllstarLink.org](http://AllstarLink.org)  
> > [http://AllstarLink.org](http://AllstarLink.org)
> > - Tim indicated that a sound fob was needed and provided a link to a  
> > site but there are lots of devices for sale so a specific  
> > recommendation would be appreciated. Is it possible that there is an  
> > RPi HAT available to provide this sound fob function or must it be a  
> > USB device?
> > - Tim also indicted that I could use an RTCM at each location and an  
> > RPi computer at only one location. I’m not sure what an RTCM is but  
> > would assume that it is some sort of radio interface.
> > - I would also assume that there are cables needed – what kind, I  
> > don’t know.
> > - I have Yaesu DR-2X repeaters
> > 
> > Right now, I am assuming I will use:
> > 
> > - 2 x Raspberry Pi computers – one at each repeater site.
> > - 2 x Sound Fobs – one at each location
> > - 2 x Cables from the DB9 connector on the Sound Fob to the Repeater  
> > (probably custom made)
> > 
> > Assuming that this will get AllStar running and connected to the  
> > repeaters, is ther anything else that will be needed to LINK the two  
> > repeaters together via Analog?
> > 
> > Sure wish there was some sort of technical schematic available, even is  
> > a simple form that would help explain this basic hardware requirement. I  
> > realize that there are lots of different scenarios out there and that  
> > schematics or block diagrams for each would be problematic to maintain  
> > but hoping that someone has documented this to make it easier for noobs.
> > 
> > If I could get a specific recommendation on the Sound Fob, that would be  
> > a great start. If a HAT for the RPi is available that would make for a  
> > clener installation.
> > 
> > Thanks and I’m sure I’ll be asking for more help, especially regarding  
> > the DVSwitch and how to implement that.
> > 
> > Regards to all.
> > 
> > ··· (click for more details)  
> > [https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/4](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/4)  
> > [Mike] Mike [https://community.allstarlink.org/u/mike](https://community.allstarlink.org/u/mike)  
> > January 3
> > 
> > To add to Tim’s reply…  
> > Get the allstar running as needed, the working hardware interface’s etc,  
> > then add your dvswitch
> > 
> > When you get to that spot… join dvswitch forum on [www.groups.io](http://www.groups.io)  
> > [http://www.groups.io](http://www.groups.io)
> > 
> > Welcome aboard !
> > 
> > * * *
> > 
> > Visit Topic  
> > [https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/8](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/8)  
> > or reply to this email to respond.
> > 
> > You are receiving this because you enabled mailing list mode.
> > 
> > To unsubscribe from these emails, click here  
> > [https://community.allstarlink.org/email/unsubscribe/b13d6188392a85e24ce7017dd034de3cc9dd1595c460233e4586059b0dd27e73](https://community.allstarlink.org/email/unsubscribe/b13d6188392a85e24ce7017dd034de3cc9dd1595c460233e4586059b0dd27e73).

---

<div class="post-metadata">

### Author: ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)
#### Post date: [January 3, 2021, 4:38pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/10 "2021-01-03T16:38:55Z")

</div>

One of the Pi releases @W3KKC mentioned is in limited Alpha test. There have been many improvements under the hood and it runs really, really well. It also runs on Intel and hosted VMs. I’m very excited about this version and hope we can start Beta release soon.

---

<div class="post-metadata">

### Author: ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)
#### Post date: [January 3, 2021, 5:39pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/11 "2021-01-03T17:39:19Z")

</div>

I might suggest you take your time and think it all through before making moves.  
It all is going to be dependent on how much you wish to roll up your sleeves to achieve what you think you want.

Before I would choose a RIM (radio interface module) I would want to talk to someone who actually uses it with the Pi/PC you are going to be using it on. Everyone has a favorite.

I am suggesting you use the tried and proven methods while you are learning what it all is and how it all works. Most especially if you are not currently ‘linux savy’. It’s a lot to take in for a starter.  
More difficult when it is not working to find your issue. And perhaps fewer folks to help you find it.

---

<div class="post-metadata">

### Author: ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)
#### Post date: [January 3, 2021, 6:43pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/12 "2021-01-03T18:43:28Z")

</div>

Good advice from @Mike. AllStar has a pretty steep learning curve. Baby steps at the beginning are advised.

Another alternative to the Masters Communications products is the URI from DMK Engineering. These are long proven devices and long time friend of the AllStar inventor Jim Dixon, WB6NIL. See the link below if interested.

> **[DMK Engineering - Home of URI](https://dmkeng.com)**

Personally, I’m a big fan of the RTCM. The web site is down due to what I’ll call a business dispute. But the product is still available. PM me if interested. I would say that the RTCM adds another level of complications that may not be desirable to beginners. However, it’s voting capabilities among other features are where you want to be eventually.

---

<div class="post-metadata">

### Author: ![WB6OZD](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/977dab/32.png) [@WB6OZD](https://community.allstarlink.org/u/WB6OZD)
#### Post date: [January 4, 2021, 12:19am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/13 "2021-01-04T00:19:45Z")

</div>

I’ll echo Tim’s suggestion for using RTCM’s. You can use any of the other interfaces listed, but you will then need your node computer (Pi) at the same location where the repeater is. With the RTCM’s, it can be nearly anywhere and the same node can service both of your repeaters. Additionally, the RTCM’s can be configured to allow for local repeat functionality if for some reason your internet connection goes down. The other huge benefit of RTCM’s is doing multi-receiver voting.

I just purchased 3 new RTCM’s in the last month, so there is no issue getting them.

Here’s a link to info on the RTCM’s in the wiki: [https://wiki.allstarlink.org/wiki/RTCM\_Client](https://wiki.allstarlink.org/wiki/RTCM_Client)

---

<div class="post-metadata">

### Author: ![KD5BS](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/47e85d/32.png) [@KD5BS](https://community.allstarlink.org/u/KD5BS)
#### Post date: [January 4, 2021, 2:52am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/14 "2021-01-04T02:52:39Z")

</div>

Jon and Tim,

Thank you both for your suggestions. I have seen the URI device before but was not aware of its capabilities or how to think about using it. I especially appreciate your explanation of why the RTCM devices are preferred and the “end state” approach you recommended. That is the kind of input I need.

Have either of you implemented this device with a Yaesu DR-2X repeater? I’m assuming that the cable between the URI and the DR-2X would have to be custom built – or, is there a pre-built cable available for this repeater.

To your knowledge will this URI device be appropriate in a solution where DVSwith is implemented at a future date?

Thanks again, I really appreciate the feedback and help.

Robert

KD5BS

> **···**
>
> **From:** Jon Welfringer via AllStarLink Discussion Groups [noreply@community.allstarlink.org](mailto:noreply@community.allstarlink.org)  
> **Reply-To:** AllStarLink Discussion Groups [replies+58217c53506651719813f9d30d641534@community.allstarlink.org](mailto:replies+58217c53506651719813f9d30d641534@community.allstarlink.org)  
> **Date:** Sunday, January 3, 2021 at 6:29 PM  
> **To:** Robert Stroud [rstroud@istroud.com](mailto:rstroud@istroud.com)  
> **Subject:** [AllStarLink Discussion Groups] [App\_rpt-users] Get Started with AllStar - Hardware Requirements
> 
> |   
>   
> ![https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/977dab/45.png](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/977dab/45.png)  
>   
> |   
>   
> [**WB6OZD**](https://community.allstarlink.org/u/wb6ozd)  
> January 4  
>   
> |
> | --- | --- |
> 
> I’ll echo Tim’s suggestion for using RTCM’s. You can use any of the other interfaces listed, but you will then need your node computer (Pi) at the same location where the repeater is. With the RTCM’s, it can be nearly anywhere and the same node can service both of your repeaters. Additionally, the RTCM’s can be configured to allow for local repeat functionality if for some reason your internet connection goes down. The other huge benefit of RTCM’s is doing multi-receiver voting.
> 
> I just purchased 3 new RTCM’s in the last month, so there is no issue getting them.
> 
> Here’s a link to info on the RTCM’s in the wiki: [**https://wiki.allstarlink.org/wiki/RTCM\_Client**](https://wiki.allstarlink.org/wiki/RTCM_Client)
> 
> * * *
> 
> [**Visit Topic**](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/13) or reply to this email to respond.
> 
> To unsubscribe from these emails, [**click here**](https://community.allstarlink.org/email/unsubscribe/c60810aefa4f2ee201c247bf37ff5d2e4ed231f4ff8a29491f1cd9c6c7aa5a84).

---

<div class="post-metadata">

### Author: ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)
#### Post date: [January 4, 2021, 3:18am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/15 "2021-01-04T03:18:49Z")

</div>

> [@KD5BS](#):
>
> Have either of you implemented this device with a Yaesu DR-2X repeater? I’m assuming that the cable between the URI and the DR-2X would have to be custom built – or, is there a pre-built cable available for this repeater.

I can recommend uricables. He built a couple of RTCM cables for me. He can make anything to anything. They are really nice.

> **[URI Cables](http://www.uricables.com)**
>
> URI Cables

---

<div class="post-metadata">

### Author: ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)
#### Post date: [January 4, 2021, 3:24am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/16 "2021-01-04T03:24:35Z")

</div>

> [@KD5BS](#):
>
> To your knowledge will this URI device be appropriate in a solution where DVSwith is implemented at a future date?

No, I don’t think so. You need a mmdvm for digital. It’s a modem and has it’s own analog connections. I sorta remember there being some talk about a new mmdvm that would support both analog and digital. But I don’t pay that close attention to digital.

---

<div class="post-metadata">

### Author: ![Pierre\_Martel](https://community.allstarlink.org/user_avatar/community.allstarlink.org/pierre_martel/32/575_2.png) [@Pierre\_Martel](https://community.allstarlink.org/u/Pierre_Martel)
#### Post date: [January 4, 2021, 3:41am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/17 "2021-01-04T03:41:09Z")

</div>

The development of the FM branch on the mmdvm is not in the main branch. From what I understand it is also highly demanding to the modem so not all mode can or should be enabled while FM is. This is not yet confirmed.

Also the linking to an analog network is not finished yet but Steve N4IRS is talking about coding a “reflector” to link the analog parts of the mmdvm modem.

> **···**
>
> Le dim. 3 janv. 2021 à 22:34, Tim Sawyer via AllStarLink Discussion Groups \<[noreply@community.allstarlink.org](mailto:noreply@community.allstarlink.org)\> a écrit :
> 
> > > ![](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/45/5_2.png "wd6awp") | [wd6awp](https://community.allstarlink.org/u/wd6awp) ASL Admin  
> > > January 4 |
> > > 
> > > - | - |
> > 
> > > ![](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/47e85d/40.png)KD5BS:
> > > 
> > > To your knowledge will this URI device be appropriate in a solution where DVSwith is implemented at a future date?
> > 
> > No, I don’t think so. You need a mmdvm for digital. It’s a modem and has it’s own analog connections. I sorta remember there being some talk about a new mmdvm that would support both analog and digital. But I don’t pay that close attention to digital.
> > 
> > * * *
> > 
> > [Visit Topic](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/16) or reply to this email to respond.
> > 
> > * * *
> > 
> > #### In Reply To
> > 
> > > ![](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/45/5_2.png "wd6awp") | [wd6awp](https://community.allstarlink.org/u/wd6awp) ASL Admin  
> > > January 4 |
> > > 
> > > - | - |
> > 
> > I can recommend uricables. He built a couple of RTCM cables for me. He can make anything to anything. They are really nice.
> > 
> > * * *
> > 
> > [Visit Topic](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/16) or reply to this email to respond.
> > 
> > You are receiving this because you enabled mailing list mode.
> > 
> > To unsubscribe from these emails, [click here](https://community.allstarlink.org/email/unsubscribe/ba97aefd360a0de7197783e27f367200aa450d82d08fc8e80c65233144f2039b).

---

<div class="post-metadata">

### Author: ![KD5BS](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/k/47e85d/32.png) [@KD5BS](https://community.allstarlink.org/u/KD5BS)
#### Post date: [January 4, 2021, 4:06am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/18 "2021-01-04T04:06:03Z")

</div>

How do I contact the company to inquire about the RTCM device if the site is down?

Robert

> **···**
>
> **From:** Tim Sawyer via AllStarLink Discussion Groups [noreply@community.allstarlink.org](mailto:noreply@community.allstarlink.org)  
> **Reply-To:** AllStarLink Discussion Groups [replies+a7baef3b0294ba2ca8d1936ece2e5008@community.allstarlink.org](mailto:replies+a7baef3b0294ba2ca8d1936ece2e5008@community.allstarlink.org)  
> **Date:** Sunday, January 3, 2021 at 12:53 PM  
> **To:** Robert Stroud [rstroud@istroud.com](mailto:rstroud@istroud.com)  
> **Subject:** [AllStarLink Discussion Groups] [App\_rpt-users] Get Started with AllStar - Hardware Requirements
> 
> |   
>   
> ![https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/45/5_2.png](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/45/5_2.png)  
>   
> |   
>   
> [**wd6awp**](https://community.allstarlink.org/u/wd6awp) ASL Admin  
> January 3  
>   
> |
> | --- | --- |
> 
> Good advice from [**@Mike**](https://community.allstarlink.org/u/mike). AllStar has a pretty steep learning curve. Baby steps at the beginning are advised.
> 
> Another alternative to the Masters Communications products is the URI from DMS Engineering. These are long proven devices and long time friend of the AllStar inventor Jim Dixon, WB6NIL. See the link below if interested.
> 
> [**dmkeng.com**](https://dmkeng.com)
> 
> **Error! Filename not specified.**
> 
> ### [DMK Engineering - Home of URI](https://dmkeng.com)
> 
> Personally, I’m a big fan of the RTCM. The web site is down due to what I’ll call a business dispute. But the product is still available. PM me if interested. I would say that the RTCM adds another level of complications that may not be desirable to beginners. However, it’s voting capabilities among other features are where you want to be eventually.
> 
> * * *
> 
> [**Visit Topic**](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/12) or reply to this email to respond.
> 
> To unsubscribe from these emails, [**click here**](https://community.allstarlink.org/email/unsubscribe/4e76215e4e932fd3a3386f6e998102f96f7df25a79df5d78be0cb7779f906e61).

---

<div class="post-metadata">

### Author: ![WD6AWP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wd6awp/32/5_2.png) [@WD6AWP](https://community.allstarlink.org/u/WD6AWP)
#### Post date: [January 4, 2021, 4:16am UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/19 "2021-01-04T04:16:23Z")

</div>

Write to mark at micro-node dot com.

---

<div class="post-metadata">

### Author: ![AF5LW](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/a/a4c791/32.png) [@AF5LW](https://community.allstarlink.org/u/AF5LW)
#### Post date: [January 5, 2021, 6:24pm UTC](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015/20 "2021-01-05T18:24:40Z")

</div>

@W3KKC  
Kevin,  
I am struggling with a new pi4b that won’t boot on the legacy Pi image. I would greatly appreciate a link to whichever of the compatible client releases would work best with a dvswitch bridge.

Thank you in advance,  
AF5LW

[Next page](https://community.allstarlink.org/t/get-started-with-allstar-hardware-requirements/18015.md?page=2)
