Ham radio on the leading edge

Bill Vodall wa7nwp at gmail.com
Mon Jun 2 11:06:14 PDT 2014


How's it going?

Is this a Linux, Mac or Agnostic ap?

Keep in mind the existing APRS on *SK work done with APRS-Messenger.
Curt did some experimentation getting FLdigi to talk to APRS-MEssenger
but we all were distracted by other projects and it was never
finished..

Bill



On Sun, May 25, 2014 at 4:39 PM, Jeff Francis™ <jfrancis at gmail.com> wrote:
>   I finally trust the code enough to put it up as a "real" gem (so you can
> install with "sudo gem install fldigi" directly from the INTARWEBS).  I'll
> post more as I get the networking layer working.  First task is to get the
> UDP-ish code working 100%.
>
> Jeff N0GQ
>
>
>
> On Sun, May 25, 2014 at 4:14 PM, Steve <stevewa206 at gmail.com> wrote:
>>
>> Wow...this has great potential!
>>
>> Steve
>>
>>
>> On Saturday, May 24, 2014, Jeff Francis™ <jfrancis at gmail.com> wrote:
>>>
>>>   I've been spending a ton of time on airplanes lately (alas, not my own
>>> - that project has been pretty neglected for a bit with all the work travel
>>> I've been doing).  Airplane time is the only time in my life where I can
>>> give anything my undivided attention (no phone, no texts, no instant
>>> messages, no e-mail).  So I put that time to good use.  I wrote the building
>>> blocks for using FLDigi as a modem from arbitrary ruby code.  Basically, I
>>> abstracted the FLDigi XML-RPC calls into a simple fldigi object with simple
>>> methods to send, receive, control the radio, etc.  Now that I have this
>>> foundation, I can build whatever I like on top of it.  I can do e-mail, file
>>> transfer, etc.  I've still got some code to write, but it's actually
>>> surprisingly useful as it is.  You can snag the latest version at:
>>>
>>> http://fldigi.gritch.org
>>>
>>>   Right now, I've got a propnet client as well as a simple demo client
>>> that will call CQ and send arbitrary text.  I've almost got an HF APRS
>>> client working.  But the important thing is that I've got all the frequency,
>>> mode, modem, carrier, AFC, etc. stuff all working in the library.  It's as
>>> simple as doing:
>>>
>>> require 'fldigi'
>>> fldigi=Fldigi.new
>>> fldigi.call="N0GQ"
>>> fldigi.freq=14070000
>>> fldigi.carrier=1000
>>> fldigi.modem="BPSK31"
>>> fldigi.config()
>>> fldigi.cq()
>>>
>>>   I've got two more plane trips this week, with an additional two the
>>> following week.  With luck, I can add code to build packets/frames, along
>>> with checksums and acks.  My intent is to model IP and have the equivalent
>>> of UDP (unacknowledged) and TCP (acknowledged and sequenced) packets, along
>>> with something akin to sequence numbers and ports.  Once *that* task is
>>> done, doing things like reliable instant messaging/chat, file transfers,
>>> mail, and everything else are pretty straightforward.  I've got some of this
>>> already working, but not ready for prime time.  For the moment, I'm doing
>>> Base64 encoding of the packet data, and using CRC32 checksums.  I'm likely
>>> to change both of those, as Base64 isn't very bandwidth-friendly, and CRC32
>>> has too many collisions.  I'll probably also add compression, at which point
>>> Base64 might be tolerable.  I'm also planning on varying packet sizes based
>>> on error rates.  I also haven't quite worked out retransmission timers and
>>> packet/frame prioritization.  It would also be trivial to add network-level
>>> encryption, for countries where that kind of thing is legal (or for use on
>>> commercial radio).
>>>
>>>   Oh, and I'm also thinking of writing an "ALE-like" client, where you
>>> and N buddies can run the code, and all of the radios will periodically
>>> "ping" each other (and pass the equivalent of SMS messages) on each
>>> configured band to give you a real-time picture of propagation between all
>>> the points in your "network".  That's a pretty easy add-on, actually.  All
>>> it takes is time...
>>>
>>>   Anyway, I've been threatening to write a decentralized, open-source,
>>> non-Windows-proprietary replacement for Winlink for years.  I've finally
>>> taken the first serious step.
>>>
>>> Jeff N0GQ
>>>
>>>
>>>
>>> On Sun, May 4, 2014 at 4:31 PM, Bill Vodall <wa7nwp at gmail.com> wrote:
>>>>
>>>> Ok - Now I'm off the phone and have a keyboard...
>>>>
>>>> BPQ32 has been ported to Linux  (and Mac) thanks to the popularity of
>>>> the Raspberry PI.   The source isn't 'up front' but it is there.
>>>>
>>>> FLdigi has a full suite of tools using various soundcard modem modes
>>>> as well as for doing 'one-to-many' messaging.   (flamp -
>>>> http://www.w1hkj.com/flamp-help/ )
>>>>
>>>> Some of the latest development with BPQ32 has been testing it using
>>>> FLDigi (and all the various modes) as the underlying modem...
>>>>
>>>> It's nice to see these pieces all coming together...
>>>>
>>>>  The developers still are thinking more of 'messages' than of 'files'
>>>> but maybe one day we'll have a pressing need and that will change.
>>>>
>>>> 73,
>>>> Bill - WA7NWP
>>>>
>>>>
>>>> On Sun, May 4, 2014 at 12:32 PM, Jeff Francis™ <jfrancis at gmail.com>
>>>> wrote:
>>>> >   Honestly, I've never looked into BPQ32 as it has (in my opinion) two
>>>> > fatal strikes against it:
>>>> _______________________________________________
>>>> Seatcp mailing list
>>>> Seatcp at wetnet.net
>>>> http://wetnet.net/mailman/listinfo/seatcp
>>>
>>>
>>>
>>>
>>> --
>>> -=jeff=-
>>
>>
>> _______________________________________________
>> Seatcp mailing list
>> Seatcp at wetnet.net
>> http://wetnet.net/mailman/listinfo/seatcp
>
>
>
>
> --
> -=jeff=-
>
> _______________________________________________
> Seatcp mailing list
> Seatcp at wetnet.net
> http://wetnet.net/mailman/listinfo/seatcp


More information about the Seatcp mailing list