[arm-allstar] RB-USB-Lite / AllStar / Direwolf

David McGough kb4fxc at inttek.net
Thu Oct 26 12:42:37 EST 2017


Hi Fred,

Yes, the direwolf software is excellent.

As for the AllStar APRS support, it's pretty limited in operational scope,
and I don't typically use it. Where I want to send out APRS beacons, etc.,
I just use the stand-alone aprx software, which is full featured and in
the hamvoip-packet-tools package.

More details about the AllStar APRS support can be found here:

http://docs.allstarlink.org/drupal/node/14


73, David KB4FXC




On Wed, 25 Oct 2017, Fred Hillhouse wrote:

> I am pleased John, WB2OSZ, added the PTT via CM108/CM119 to his codebase!
> The soundcard can now be installed inside many radios with only the need for
> an USB cable to a RPi! In my case (non-Allstar), the RPi0-W and soundcard
> will fit in the radio. Not sure of the effect it might have yet since I
> haven't pushed that far yet.
> 
> I have seen frequency reporting for Allstar stations. I could not determine
> if they were being generated by Allstar. I didn't look into it since I
> assumed they were getting generated by some other means. It sounds like I am
> wrong in that assumption. Hee haw. Just a note that may be of interest, my
> interest in Allstar started because of seeing the W1FVB Allstar stations on
> my APRSIS32 map.
> 
> Since data is sent to the APRS-IS (APRS Internet Servers) you have some of
> what is needed assuming it isn't going out RF yet. The text packet would
> need to be converted to KISS and sent to Direwolf using port 8001. I suspect
> there could be a reason for bi-direction packet flow. I'd make the KISS
> routine is bi-direction. Although to support incoming packets more code
> would be needed.
> 
> The APRS client APRSIS32 is really simple to connect. I create a
> "SimplyKISS" port and connect to the correct IP/port(8001) and I am done. If
> Direwolf is on the same device as Allstar, then localhost should work. My
> Direwolf instance is on a separate RPi so I just point to its IP address.
> 
> Direwolf also supports the AGW TCPIP interface. I have not tried it.
> 
> I don't know if Allstar has its own TOCALL
> (http://www.aprs.org/aprs11/tocalls.txt). If not, A quick dialog with Bob,
> WB4APR, would get you one for this particular application and make it part
> of the APRS specification. Once it has one, the APRS applications would
> recognize the Allstar application from now on!
> 
> 
> Best regards,
> Fred N7FMH
> 
> 
> -----Original Message-----
> From: David McGough [mailto:kb4fxc at inttek.net] 
> Sent: Wednesday, October 25, 2017 12:12 PM
> To: Fred Hillhouse
> Cc: '"Fred Hillhouse via arm-allstar"'
> Subject: RE: [arm-allstar] RB-USB-Lite / AllStar / Direwolf
> 
> 
> Hi Fred,
> 
> Thanks for this info. Yes, I got the latest direwolf version from github
> master branch, in August. I just looked at the dev branch and see the
> enhancements.
> 
> I'll pull against the dev branch and do a build based on that code, too, and
> add to the package.
> 
> AllStar doesn't currently have a way to interface with direwolf, etc., for
> APRS. The APRS info sent by AllStar goes out via TCP/IP, using whatever
> Internet connection you've got. So, this info could be used for APRS
> frequency reporting, I think---I haven't looked at the code in a while.
> 
> 
> 73, David KB4FXC
> 
> 
> 
> 
> On Wed, 25 Oct 2017, Fred Hillhouse wrote:
> 
> > Note: The latest Direwolf "stable" version does not have this ability 
> > while the DEV version 1.5 does.
> > 
> > I haven't moved my Allstar project forward yet. I have looked through 
> > the documents and didn't noticed how it might interact with Direwolf.
> > 
> > Can Allstar use Direwolf for sending packets over RF (144.390MHz)?
> > 
> > Specific packets would be frequency objects 
> > (http://www.aprs.org/info/freqspec.txt)? This would be a very useful 
> > feature for travelers to use a Allstar system they may travel within range
> of?
> > Posting these to the APRS-IS is nice but sending over RF is excellent! 
> > I was traveling recently to an area with Allstar but I never saw 
> > packets on my radio, a D72. The D72, as well as other radios, can QSY 
> > to the frequency for immediate use.
> > 
> > Another useful packet is for displaying range circles
> > (http://www.aprs.org/phg.html) around the station. I know many Allstar 
> > stations might use an HT with little range while others are complete 
> > repeater systems.
> > 
> > For the repeater systems, the above packets make sense. I am not so 
> > sure about those stations that one must park in a driveway to use.
> > 
> > Best regards,
> > Fred N7FMH
> > 
> > 
> > -----Original Message-----
> > From: David McGough [mailto:kb4fxc at inttek.net]
> > Sent: Wednesday, October 25, 2017 11:01 AM
> > To: "Fred Hillhouse via arm-allstar"
> > Cc: Fred Hillhouse
> > Subject: Re: [arm-allstar] RB-USB-Lite / AllStar / Direwolf
> > 
> > 
> > Hi Fred,
> > 
> > Thanks for the feedback. And, BTW, I updated the hamvoip-packet-tools 
> > package near the end of August, and it now includes the latest 
> > versions of direwolf, aprx and LinuxRMS software.
> > 
> > Note that when the package gets installed, all the binaries, etc., are 
> > subdirectories under the /usr/local/aprs-tools folder.
> > 
> > As for the RX audio setting for de-emphasis, I've always used the "FLAT" 
> > audio (no de-emphasis) setting---jumper JU551 in position "A".
> > 
> > Anyone else got thoughts about this???
> > 
> > 
> > 73, David KB4FXC
> > 
> > 
> > 
> > On Wed, 25 Oct 2017, "Fred Hillhouse via arm-allstar" wrote:
> > 
> > > 
> > > This weekend I connected the RB-USB-Lite to a Raspberry Pi Zero W 
> > > and was able to control PTT through the USB interface. The latest 
> > > Direwolf dev
> > build
> > > includes PTT control through the RB-USB-Lite without the addition of
> > hamlib.
> > > So it looks like potential one-stop interface shopping for Allstar 
> > > and/or Direwolf if that interest you.
> > > 
> > > While setting up the RB-USB-Lite, I ended up changing the POT 
> > > setting (MIC input). It wasn't unexpected. It turns out I needed to 
> > > adjust the POT
> > almost
> > > to the bottom. This was before playing with the input gain. It was 
> > > already set very low. Apparently the 1200 data output requires both 
> > > the POT and
> > GAIN
> > > to be set very low. Again not necessarily surprised. It did lead me 
> > > to
> > look
> > > at the GM300 in comparison to the FT1500 I am using.
> > > 
> > > Which led me to another question: what jumper setting (JU551) is 
> > > typical
> > for
> > > the GM300? A (350mVrms/ not de-emphasized) or B (600mVrms/
> de-emphasized)?
> > > 
> > > Thanks!
> > > 
> > > Best regards,
> > > Fred N7FMH
> > > 
> > > -----Original Message-----
> > > From: David McGough [mailto:kb4fxc at inttek.net]
> > > Sent: Wednesday, June 21, 2017 5:45 PM
> > > To: "Fred Hillhouse via arm-allstar"
> > > Cc: Fred Hillhouse
> > > Subject: Re: [arm-allstar] RB-USB-Lite / AllStar / Direwolf
> > > 
> > > 
> > > Hi Fred,
> > > 
> > > I haven't tried that interface with direwolf, but it'll probably work.
> > > 
> > > As for packet radio tools, I've already got a pre-built package for 
> > > the
> > > V1.5 hamvoip release that includes direwolf, aprx and various other 
> > > utilities that I use. I've got the Linux RMS gateway software built, 
> > > too, but, haven't yet added it to the package.
> > > 
> > > You can grab this package via pacman like this:
> > > 
> > > pacman -Sy hamvoip-packet-tools
> > > 
> > > 73, David KB4FXC
> > > 
> > > 
> > > On Wed, 21 Jun 2017, "Fred Hillhouse via arm-allstar" wrote:
> > > 
> > > > Greetings,
> > > > 
> > > >  
> > > > 
> > > > While looking through radio interface options I saw the RB-USB-Lite. 
> > > > In the interest of saving time, I am considering it. I can build 
> > > > the interface but that would delay things.
> > > > 
> > > >  
> > > > 
> > > > It looks like a radio does not need any programming for CTCSS. Is 
> > > > this
> > > true?
> > > > 
> > > > The interface handles de-emphasis appropriately since the notes 
> > > > seem to hint at connection to the discriminator. Is this true?
> > > > 
> > > >  
> > > > 
> > > > I found schematics but no instructions.
> > > > 
> > > >  
> > > > 
> > > > Since I like standardization a bit and the interface seems to have 
> > > > everything at a reasonable price and I am asking questions, has 
> > > > anyone use one of these interfaces for APRS with 
> > > > Raspbian/Direwolf? Since this last question is OT, feel free to answer
> direct.
> > > > 
> > > >  
> > > > 
> > > > Thank you all!
> > > > 
> > > >  
> > > > 
> > > > Best regards,
> > > > 
> > > > Fred N7FMH
> > > > 
> > > >  
> > > > 
> > > >  
> > > > 
> > > > 
> > > > 
> > > > ---
> > > > This email has been checked for viruses by Avast antivirus software.
> > > > https://www.avast.com/antivirus
> > > > _______________________________________________
> > > > 
> > > > arm-allstar mailing list
> > > > arm-allstar at hamvoip.org
> > > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > > 
> > > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > 
> > > arm-allstar mailing list
> > > arm-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > > 
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > > 
> > 
> > 
> > 
> 
> 
> 



More information about the arm-allstar mailing list