Differences

This shows you the differences between two versions of the page.

--- blog:2021-01-02:js8call_hf_net_process [2021/01/06 21:23] – va7fi
+++ blog:2021-01-02:js8call_hf_net_process [2021/06/05 12:22] (current) – va7fi
@@ Line 2: / Line 2: @@
 Over on groups.io, there's a discussion in the JS8Call group about using JS8 to run a Net.  Gordon Gibby (KX4Z NCS521) [[https://groups.io/g/js8call/topic/net_communications_using_js8/79148254?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,79148254 |opened the discussion on Dec 22, 2020]]:
-<WRAP indent>
+<QUOTE>A few volunteers are giving a try at creating a protocol for a communications NET managed using JS8.
-<<A few volunteers are giving a try at creating a protocol for a communications NET managed using JS8.
 The impetus came from observing the difficulties of voice net check-ins spread over a wide geographic area, with some stations unable to hear the net control station (and vice versa)  [likely due to picking a higher operating frequency to get better strength signals, but then having to deal with SKIP ZONES], stations on top of each other in the time domain, difficulties understanding some stations, and on and on.
@@ Line 10: / Line 9: @@
 This protocol uses a primary and backup net control (the policy of the voice nets of this group) and then has the primary NCS list all of the recognized stations in a message to the backup.   All stations could copy this message, and then reply at the same time as the backup, with callsigns missed by the primary NCS at the first attempt.
-Anyone ever done this before or have improved suggestions?>>
+Anyone ever done this before or have improved suggestions?</QUOTE>
-</WRAP>
 A few days later, someone else jumped in with a helper program called NetControlJS8: