Category Archives: Discussion

Digital, Discussion, Emergency Communications, FLx/FLDigi, Packet

Outbrief – 15 Feb 2015 Digital Workshop

On Saturday, February 14, 2014, the Digital Working Group met along with some other interested parties to discuss the current state of the digital technologies, as well as  try and find a road map for implementation within the PWCARES framework.  After introductions, we went through some presentations.

The Presentations
Rick, KJ4ZIH
  • Evolution from a discussion about “is there a role” for digital in ARES to  clearly there is, especially the farther west in the US you go.
  • Rick has issues getting from his home in Haymarket getting to the repeaters (WWI/OHV) on voice
  • EOC is currently VHF/UHF oriented
  • Two parts of the story – the tools (FLx) and how the PA group is using them (NBEMS)
  • Rick went the route of the SignaLink, but there is software that can do the same thing with your built in sound cards (mostly inexpensive)
  • Similar to a fax machine over a telephone line – stuck pig sounds
  • Multiple ways to move the noise – usually mic and speaker, with the right cables to make the connection

NBEMS

  • Ran through the NBEMS presentation
  • Digital is accurate in the information being transmitted
  • FEC in a number of them protocols
  • Served agencies are moving along the digital message paths
  • NBEMS is an application of the FLx programs
  • Flamp – broadcast message to all
  • Open Source, multi-platform
  • Fldigi – encoder/decoder, with multiple codex
  • Sometimes you need to tweak the time calibration of your soundcard
  • MT-63 is robust, quick, FEC, used by MARS, resistant to noise
  • Good for increased distance performance
  • Olivia is preferred on HF.  Sounds like a flute in the air. Stands out
  • Flmsg is pre-formatted, good fill in the blank ability
  • Text based, self-limiting to 3KB files, with a 3 minute limit for transmission
Derek, KV4SH
HSMM-MESH/Broadband
  • High-speed Mobile Mesh
  • Now called “Broadband hamnet”
  • Autoconfiguation fault tolerant ham radio coverage (part 15/part 97)
  • Because it is mess, it it multipath
  • High bandwidth
  • Transmits IP
  • Not limited by size of file
  • upto 150mb/sec depending on quality
  • Need to flash your router with a new image, configure, put on the air
  • Infrastructure based set up
  • There is the ability to get the hook up on to the Internet…there are issues with doing this
  • LinkSys, Ubuiquiti brand (www.ubnt.com)
  • Under 1 watt of power out of the repeater
  • Until you boost power, you are covered by part 15. Once you boost, you fall into part 97
  • Under part 97, no encryption, no WPA, no SSL/HTTPS/Encrypted chat
  • Coverage up to 10 miles but realistically, much more reduced
  • Emcomm – videos, large images, web cams
  • A discussion of the nuts and bolts of Internet vs Mesh set ups – ssid/esid vs IP address

David, KG4GIY

  • David reviewed the packet and WinLink
  • Packet is still a viable technology, but with a high learning curve.
  • Some masking is done by Outpost, a Windows-based piece of software.
  • Store and forward as well as direct connect. Also has the ability to hopscotch from node-to-node to improve connectivity.
  • Heavy infrastructure requirement, most packet nodes are no longer active.
  • WinLink is a long running, Windows-based message service.
  • Many have had success with it.

The Direction

After the presentations, we made some decisions. To wit:

OS: Windows (for now)

Mode: Ad Hoc

Band: VHF/UHF (for now)

With that as the preconception, the FLx stack of programs makes the most sense to implement. So:

OpMode: MT-63 2KL (2000L)

Freq: 146.475 (ARES VHF 2)

The Concept of Operations

At this point, digital messages are being utilized in experimental mode. While it is desirable to have a digital node at each location, until we are completely comfortable with operation, it may not yet be possible.

Further, these are the identified (but not exclusive) types of messages that could be passed by digital methods.

  1. Bulletins. These are messages that are sent out from NCS regarding the state of the operation, active locations, operational period data, weather updates, etc. that are necessary for all stations but could utilized excessive bandwidth on voice.
  2. POD Supply lists. These are lists that may include equipment and supplies needed at a Point of Distribution, either basics or medicinals.
  3. Low priority messages. These are messages that would take up unnecessary bandwidth on voice but still need to be passed.

While these are not all the types of messages that can, or could be sent by digital, it is a good start.

While we are working through the process and procedures, there are some additional issues we need to keep in the back of our minds.

  • Printers? What is the need for being able to print out these digital messages? Do we need to arrange for access to printers? What sort?
  • Directed Net? Does digital operations require a directed net? How would that operate?
  • Time segments? Would it make more sense to have a time slice management plan instead of a directed net. For example, in any 15 minute segment, the first x period is reserved for priority or emergency traffic, the rest of the period is a free for all?
  • Can fldigi be set to auto select operational mode? If so how so?

Finally, there was a decision to try and set up smaller hands on working groups to configure and test configurations before we take it to the field. There also needs to be a separate effort to create a quick reference guide. This can be managed via the digital list or this site.  If someone would like to volunteer to host a working group, please identify yourself and we will get it on the calendar.

Resources:

Here is a link to the presentations and other information from the working group.

NBEMS

Broadband-hamnet

 

 

Amateur Radio Emergency Service, Digital, Discussion, Emergency Communications, Emergency Preparedness, Packet, PWCARES

The Goals for a Good Digital Solution

1 Comment

Here are my goals:

  1. Low cost of entry.  This means that whatever solution we choose, it should not cost the average operator a lot of money to participate. This means that the code needs to be open source or low cost, the hardware footprint needs to be light and it should work with the majority of radios out there.
  2. Easy configuration. The selected software should be easy to configure and it should be easy to bring up a node without needing to be a networking professional.  It would be nice if we can do the following a) have a running “full time” network and b) be able to link into that network quickly in an emergency, like the old packet system as an example.
  3. Easy to use. At the end of the day, it has to be easy to use by anyone for sending the common message forms (ICS-213 minimum) and possibly be able to pass the message from a terminal at the “site” to the “systems” being used by the EOC (the biggest example would be a 213 cut and pasted into WebEOC).

You will note that I don’t care a lot about HF or VHF or UHF.  That being said, I expect that local transmissions will likely be done by the lowest common license class – Technician, which makes HF pretty much a non-starter for emergency communications within the county.  Under my desire to have a functioning full time network, HF uplinks to digital nets (like VEN/D or WinLink) would be expected, but are not a requirement at this point. Let me also say that the general rule of thumb that HF would be done by those more permanent stations is still the working model.

There are advantages to store and forward.  It has been proven over the last forty years as being a stable method for passing messages. There are advantages to the fldigi model of send it once.  And there are disadvantages.

If I was building it (in a vacuum) I would use a bit of both.  I currently have a packet node up and running. I connect to it with a simple console connection.  I would love to be able to connect to it with a terminal session from my smart phone, but so far I haven’t found a cable that will let me. I used to be able to do it with my Palm though :).  I have played with fldigi/flmsg and Outpost with limited success (yes, I know they are for different purposes).  I have never had a lot of success with WinLink, or D-Rats.

At the end of the day, we need to arrive at the following:

  1. Frequencies we want to use.  These are, ideally, 2m/440. We may also want to consider supporting 6m/220/1.2 and D-Star.
  2. Protocol. What protocol will work best to ship the message and will all the software support it?
  3. Message types. What types of messages should we expect to be sending via this model?

I think, once we define these things, the rest should at least become more clear in direction.

Additional Background

At one point we tested 1.2 DD with D-Star (just for grins and giggles).  We actually tested the connection between a remote station and WebEOC and it worked nicely, if slowly.

Brian, myself, and others, were trained in using packet and have gear that still works with the technology. I think we could better link with other protocols to better node types (I am thinking something like HSMM and Raspberry Pis for example, that would facilitate a number of good things in a radio digital network beyond just “email”)

I would rather see a number of nodes around the county rather than trying to link two nodes from one end to the other, for redundancy if nothing else.

To that end:

There will be a voluntary meeting of the cadre on Saturday, February 15, 2014 at the EOC at 0900 for us to sit down and walk through the issues and technologies associated with using digital systems in the ARES network. This will be as much a discussion/open forum as it will be a class on the technologies.

The agenda is as follows. I need a few more presenters please (and I have probably lost a couple of emails with volunteers, so remind me if you had already put your hand up

  1. Presentation (Talk about the tech, bring in toys, bring up sample network?)
    1. WinLink
    2. Fldigi/msg (Rick, KJ4ZIH)
    3. Packet
    4. HSMM (Derek, KV4SH)
    5. SignaLink (Rick, KJ4ZIH)
    6. NBEMS (Rick, KJ4ZIH)
  2. Build a concept of operations: What do we want to do with it?
  3. Workshop
    1. Build a network, without protocol, identify locations for nodes, both desired and possible.
    2. Map concept of operations to network

Everyone is welcome. Feel free to bring gear!