<html><head></head><body style="zoom: 0%;"><div dir="auto">Hi Charles,<br><br></div>
<div dir="auto">Although I've read your past few emails in the thread, I, like Joe, am new to the WW convers concept and have a question. Forgive me...<br><br></div>
<div dir="auto">So I understand the purpose - logical allocation, assignment, maximal utilization of space/bandwidth, etc. But in reality/technical functionality, is this "channelizing" a schema that works as you said like AIM or IRC in the sense that it is literally a form of packetized, tagged or multiplexing sort of thing, or is it an RF/split spectrum sort of concept?<br><br></div>
<div dir="auto">In other words, as we discuss both RF and non-RF mediums here, is this something that would just multiplex (channelize) data over a single RF frequency (sort of like DMR or simar) or would it require a spread spectrum of multiple subfrequencies?<br><br></div>
<div dir="auto">I assume the former as you say this is over two decades old and already in practice and I doubt the practicality of finding 32768 different frequencies. :) I am just trying to "picture" it as conversations or channel data jump between one medium (internet/TCP/IP traffic) to another (RF) and back across the network...<br><br></div>
<div dir="auto">Sort of like Brandmeister or a channelized EchoLink, but the AMPRnet version?<br><br></div>
<div dir="auto">Regards,<br><br></div>
<div dir="auto">AJM<br><br><br><br><br></div>
<div dir="auto"><!-- tmjah_g_1299s -->Get <!-- tmjah_g_1299e --><a href="http://www.bluemail.me/r?b=16117"><!-- tmjah_g_1299s -->BlueMail for Android<!-- tmjah_g_1299e --></a><!-- tmjah_g_1299s --> <!-- tmjah_g_1299e --></div>
<div class="gmail_quote" >On Nov 28, 2020, at 2:13 PM, "Charles J. Hargrove" <<a href="mailto:n2nov@n2nov.net" target="_blank">n2nov@n2nov.net</a>> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="blue">Not a problem, but to encourage usage and in a logical fashion.<br>As someone from Europe pointed out, there are only a handful of<br>people on the system at one time. We use it here in NYC every<br>Monday during our weekly nets. By having participating systems<br>linked to regional hubs like Hub_NA or Hub_EU, the same channel<br>can be accessed in various areas for greater participation. The<br>statewide users on a particular channel like 68 for NY, can be a<br>meeting place for the state. Special interests like ATV in the<br>UK meet on channel 625 (named for the 625 scan lines of the PAL<br>TV standard). WWconvers has been around for over two decades and<br>the newer/younger hams most likely have never heard of it. It is<br>just exposure, explanation on how it works and encouragement to<br>use it.<br><br>On 11/28/2020 1:41 PM, Joe Cupano wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> <br> I saw a mention of WW convers in the link but no explanation.<br> What is the problem you are trying to solve with WWconvers?<br> <br> Thanks for taking the time to explain<br> <br> - Joe, NE2Z<br> <br> <br> <br> <br> Charles J. Hargrove:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Think of them as the same as IRC (Internet Relay Chat) or the old AOL<br> Instant Messenger (AIM). Rather than based on names, WWconvers is based<br> on numbers and is limited to 32768 although the source code might be<br> written to include more. With 0 reserved for a local default and not to<br> be relayed to others in the network, we get 32767 remaining. Here is <br> a 1996<br> FAQ on TNOS and mentions WWconvers <br> <a href="https://www.qsl.net/gb7dip/tnos/faq-96.html">https://www.qsl.net/gb7dip/tnos/faq-96.html</a><br><br> On 11/28/2020 12:31 PM, Joe Cupano wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #8ae234; padding-left: 1ex;"><br> I am lost as to the origins of WWconvers and "channelizing."<br> Is there a link?<br><br> The subject of "channels" has come up as applied to digital modes as a<br> while, voice and data, for UHF. Each has its own bandwidth requirements<br> and utilization.<br><br> 73,<br><br> - Joe, NE2Z<br><br><br> Charles J. Hargrove:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #fcaf3e; padding-left: 1ex;"> PROPOSED WWCONVERS CHANNEL SCHEME<br><br> There are 32767 possible channels in the WWconvers with channel 0 <br> reserved<br> for a local bbs to use as it's default when users log onto their <br> system.<br> Finding other stations by area, interest or any other special use <br> can get a<br> little confusing. Some countries have settled on a scheme where <br> their users<br> can find each other based on the second number of their assigned <br> 44Net (AMPR)<br> address. For example, Greece is assigned <a href="http://44.154.0.0/16">44.154.0.0/16</a> and they can <br> be found<br> on channel 154.<br><br> In the USA (because of sheer numbers of systems over the years) the <br> second<br> number in the address is typically an entire state with some having <br> multiple<br> subnets (California has 6). There has been an effort in recent <br> years to clean<br> up the numbers and subnets no longer in use and this resulted in the <br> range<br> from <a href="http://44.191.0.0/16">44.191.0.0/16</a> to <a href="http://44.255.0.0/16">44.255.0.0/16</a> to be sold to Amazon.<br><br> To make things easier, I am proposing a somewhat logical layout to the<br> channel usage, not only by the 44Net addresses but also by specilized<br> uses for activities and watering holes like HF/VHF/UHF frequencies.<br> As you can see, there will be plenty of space for adhoc arrangements.<br> Discussions are welcomed and encouraged as how to use this space for <br> the<br> benefit of many different groups and interests.<br><br> DEFAULT<br> Channel 0 – default local use and not propagated across the <br> WWconvers system.<br><br> REGIONAL<br> Channel 1 through 190 – based on second number in the 44Net/AMPR <br> addresses<br><br> MATCHING TO RF FREQUENCY USED<br> (ie: net on 7240 kHz would use channel 7240)<br> 1800-1999 160m Channels<br> 3500-3999 80m Channels<br> 7000-7299 40m Channels<br> 10100-10149 30m Channels<br> 14000-14349 20m Channels<br> 18068-18167 17m Channels<br> 21000-21449 20m Channels<br> 24890-24989 12m Channels<br> 28000-29699 10m Channels<br> 5000-5399 6m Channels<br> 14400-14799 2m Channels<br> 22200-22499 1.25m Channels<br> 4200-4499 70cm Channels<br> 9020-9279 33cm Channels<br> 12400-12999 23cm Channels<br><br> CURRENT SPECIALTY USERS<br> 625 – UHF Amateur TV Channel in UK<br> 10177 – OK2KOJ Club Channel in Czech Republic<br> 14736 – WC2OEM Channel for NYC Amateur Radio Emergency <br> Communications Service<br><br> SET AS LOCAL BBS USE (ie. JNOS Systems, etc)<br> 211 – Local NCS/ALT Channel for nets<br> 411 – Local WX Event Channel (Skywarn nets)<br> 911 – Local Emergency Net Activation Channel<br></blockquote></blockquote></blockquote></blockquote><br></pre></blockquote></div></body></html>