[aprssig] ICOM ID 51A HT

Wed Mar 27 16:29:25 EDT 2013

As I understand it as a user of both DStar and APRS, DPRS is simply a 
gateway of the position information from a DStar radio to the APRS 
network. DPRS is NOT APRS.

DPRS does not support APRS messaging and you cannot at this time at 
least, take information from APRS back into the DStar network. In fact, 
I am not sure you would want to do that anyway.

DPRS does what it is supposed to do and it works fine for what it is, 
but DPRS is clearly not APRS. Apples and oranges comparison.

Duffy
www.wb8nut.com
> Steve Dimse <mailto:steve at dimse.com>
> March 27, 2013 4:18 PM
> Actually, you are dead wrong here. APRS is a registered trademark 
> owned by Bob. If he says something isn't APRS, then it isn't APRS. Period.
>
> It isn't just semantics and legalese. Bob has been very generous with 
> allowing people to use the trademark, however he does require some 
> interoperability. DStar's implementation does not have that 
> interoperability, and there should not be called APRS. If DPRS were to 
> become fully interoperable with APRS they might find themselves in a 
> position to be blessed by Bob, but make no mistake, if Bob doesn't say 
> it is APRS then it is not APRS.
>
>
> Steve K4HG
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
> Pat Cook <mailto:kb0oxd at gmail.com>
> March 27, 2013 4:08 PM
> Bob - To say that DPRS isn't APRS simply isn't (At least entirely) 
> true.  D-STAR, like APRS, is also built on RF.  The only difference is 
> D-STAR is DIGITAL RF while APRS is ANALOG RF !!  Nevertheless, it's 
> STILL RF (That's a point that also needs to be reinforced).
>
> Now turning to DPRS - Sounds to me like those who are working behind 
> the scenes still have yet to find a way to bridge the gap between the 
> two.  As a result, those who aren't "In the know" (MYSELF INCLUDED) 
> are left giving thoughts & opinions which may not even be REMOTELY 
> CLOSE to something resembling knowledgeable about how the two 
> interface & interact with one another
>
> And we wonder why most people don't bother with Ham Radio?  LOOK AT US 
> !!!  Most people who aren't the least bit interested in Ham Radio 
> wouldn't even mess with a mode of communications like this
>
> Getting off the soapbox, I think I'm gonna have to seek input from 
> those within the D-STAR community as well since they have D-STAR 
> radios.  I say this because the vast majority of people here (Or at 
> least SOME people here as I said before) DO NOT even own a D-STAR 
> radio (Some probably don't even consider to be "Real" radio, even 
> though that's a myth).  As such, they're offering so-called "Expert" 
> information on a radio using technology THEY KNOW NOTHING ABOUT !!!  
> That (As I also said before) isn't very useful
>
> It'll likely be more ACCURATE too
>
> Again, NOT trying to bite the hands feeding me BUT there's nothing 
> useful about someone posting information on something when they 
> (Likely) know NEXT TO NOTHING about that something.  Not very 
> productive or useful.  Again just saying.....
>
> Cheers & 73 :-)
>
>
>
>
>
> -- 
> Pat Cook, KB0OXD
> Denver, CO
> KB0OXD Cybershack - http://www.wix.com/kb0oxd/kb0oxd/
> KB0OXD Cybershack Soap Box - http://kb0oxd.blogspot.com/
> EchoLink Node No. 19905 (LINK COMING SOON - 147.465 Mhz. Simplex/100.0 
> Hz PL)
> APRS TRACKER ( NEW !!! ) - http://aprs.fi/KB0OXD (Usually on as 
> KB0OXD-5 Via APRSDroid)
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
> Pat Cook <mailto:kb0oxd at gmail.com>
> March 27, 2013 3:38 PM
> Well I got the external TNC so that's no problem.  However if the 
> local D-STAR repeater has software that allows for APRS-like packets 
> to be sent via D-PRS, then TXing those packets shouldn't be a problem 
> IF it's installed properly by the trustee of the repeater, control 
> operator and/or the technical crew so therefore, I fail to see how 
> "Kerchunking" the repeater would somehow be frowned upon since it 
> wouldn't be detectable anyway & would be well within the norm
>
> Let's seperate the wheat from the chaffe a bit here.....
>
> Sounds like *Some* people on here don't know much about D-STAR & how 
> it operates & probably need to learn (Others OTOH on here DO).  Not 
> knocking anybody or biting the hands feeding me BUT if you're NOT 
> informed or educated on D-STAR & how D-STAR radios operate & integrate 
> with APRS, PLEASE move on.  You're not helping things any.  I'm not 
> educated much on either BUT am interested in learning before buying my 
> next radio.  Just saying...... :-)
>
> Cheers & 73 :-)
>
>
>
>
>
> -- 
> Pat Cook, KB0OXD
> Denver, CO
> KB0OXD Cybershack - http://www.wix.com/kb0oxd/kb0oxd/
> KB0OXD Cybershack Soap Box - http://kb0oxd.blogspot.com/
> EchoLink Node No. 19905 (LINK COMING SOON - 147.465 Mhz. Simplex/100.0 
> Hz PL)
> APRS TRACKER ( NEW !!! ) - http://aprs.fi/KB0OXD (Usually on as 
> KB0OXD-5 Via APRSDroid)
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
> ------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20130327/bf9c7fd4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20130327/bf9c7fd4/attachment.jpg>