[TangerineSDR] Quiet weekend, some progress

[David Witten]

Dave,

I hope that you are all well.

*Disclaimer: The following relate to work initiated on my own.  They are
intended to inform but not conflict with efforts by the
HamSCI/TangerineSDR software development team.*

I have spent the last few days working on a strategy to allow runMag and/or
multiMag in a way that addresses several goals:

1) Allow real time interaction with the 'device in the ground' to either
'tune' an installation in one of two ways:

   - Present animation of the measured magnetic vectors to optimize the
   unit's orientation WRT the earth's  field by physical manipulation
   (Twisting).
   - Accumulate data over time to calculate baseline normalizing vector
   offsets to an existing installation without physical intervention.

2) Allow logging, replication to linode instance, etc. while also
presenting a real-time updated presentation of vector and total data graphs
to the owner of the local network.  Owner of the local network may choose
to make these visualizations available to others by allowing access through
her/his firewall if desired.

3) Aggregation of raw real time data by higher level sites would be
possible if desired by individual owners.  This could provide network
station online/offline indication and a global view of network status, as
well as higher level visualization of phenomena.

4)  For the multiMag utility, these changes will allow access to stored
configuration data to be entered on the local network via  a web interface.

This work involves small changes to the runMag and multiMag utilities to
allow them to pipe output to a Web/WebSocket server running on the local
host while not interfering with current operating modes.

In multiMag, the challenge is allowing data reports to flow from multiple
magnetometers to logs and interfaces in a coordinated way.

At the present the data available to the end user will be in the form of
template Web pages presented by a 'civetweb' Web server. Data updates and
interaction will be handled by a WebSockets connection to the same server.
Even on local connections the intent is to use secured sessions wherever
possible, using https:// and wss:// (TLS1.3) wherever possible.

This work is meant to address specific immediate requests for function that
I have heard from others and some that I just wish to pursue for myself.

Specific software elements are likely to change, as is the overall
architecture as I gain experience.

 There are many other ways to provide this functionality, some of them
seemingly much simpler.  All the component technologies are available in
Python, Go, node,js, Take your pick...

I am working primarily in C, with tiny bits of HTML, Javascript, Lua, and
whatever gets in the way.  Some strategic pieces have been 'fuzzed' and
checked for validation against appropriate standards, so my bias is toward
using these known quantities.

Dave Witten, KD0EAG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/tangerinesdr_lists.tapr.org/attachments/20210621/846c196f/attachment.html>