[aprssig] IS-to-RF proposal (rev b)

Andre aprs at pe1rdw.demon.nl
Thu Dec 29 19:16:51 EST 2011

Op 30-12-2011 0:21, Steve Dimse schreef:
> On Dec 29, 2011, at 5:50 PM, Andre wrote:
>> Any linux or native windows tablet phone or notebook can be used for it
> In that case you have completely missed the point of Bob's latest proposal. The idea is for the user to do nothing outside of the normal use of their client, and furthermore his focus is largely on the Apple iOS and Google Android devices that are becoming just the tiniest bit more popular than Windows and Linux phones and tablets!
Android is a linux variation, it's just a bit broken. And reading back 
it looks to me that unless clients get rewritten the users have to do 
more then just use their client normaly, first the tocall needed to be 
set, then the path was to be altered and now he will have to insert a 
voice frequentie in his beacon and his desired path.
>> connected to agwpe or linux ax25 interface.
>> For linux setup axipd to connect to a hub or directly to a gate, agwpe uses the axip driver from lu7did http://www.qsl.net/lu7did/bin/axipdrv/axipdrv.txt.
>> both the hub and gateway use digined with agwpe and axipdrv or axipd.
>> The gate is set to digipeat anything to be digied trough it's call from internet to rf: digipeat: 1,2 DIGI_CALL 1
>> The hub is set to digipeat anything to all ports but the one it recieved on: digipeat: all * allbut keep0
>> limiting is done with keep_time: 300 for 5 minutes
> This may not survive our cross-cultural QSO, but in the US there is a phrase: "There's Your Problem!"
> Some people have failed to appreciate the influence Apple has had on the rest of the computing world. Users want things that "just work" now (actually they always did, they just didn't know it!) The systems that thrive today, like Android, do so because they emulate this central tenet of Apple's philosophy. As long as it takes the above kind of effort to make something work it is not going to catch on beyond a tiny circle of people that want things to be complex.
> It actually isn't a new idea, Apple has been promoting simplicity for a quarter century. I'd been influenced by that for a decade when I created the mechanism for internet to RF messaging. I made sure it worked without modification to the clients nor required any special actions on the users' part. An intercontinental QSO through the internet looked exactly the same as one with their neighbor over 2 meters. It would not have caught on if the user had to buy new hardware and install new software and drivers, then decide where to connect to have two way messaging.
> You may want to reconsider your user experience if you want this to be popular.
> Steve K4HG
 From a user experiance it will be no harder then setting agwpe up for a 
tnc, he does not have to setup a hub or gate unless he wants to.
the steps for an average user is almost the same as setting up an rf 
station, only now he is not fiddeling with audio levels txd setting etc, 
but installs a driver for a virtual tnc, in the future clients can 
support axudp just like they can suport aprs-is and setup different tncs 
but we have to start somewhere, we did not start with aprs clients 
autoconfiguring tncs either, in fact we started with a very limited tnc 
suport, only 2 tnc interfaces where suported at first.
Also do keep in mind that the aim is very different from messaging 
trough aprs-is, back then the aim was sending messages, now the aim is 
for internet users to participate as a normal rf station, something 
aprs-is was never intended for.
Bob's idea is still long way from being more then an idea, my idea is 
already in opperation right now, to me that indicates that my idea is a 
lot simpler to implement then Bob's idea.
To borrow a saying from Steve Waterman, if 3 frogs decide to jump of a 
log how many frogs are left? answer: all 3, they did not do it.
Actions speak louder then words.

Anyway, I just keep perfecting my idea and when the time is right to 
move it beyond a small scale network interfacing axudp with aprs clients 
might have become as simple as interfacing with aprs-is.

73 Andre PE1RDW

More information about the aprssig mailing list