Fwd - Winmor update
Bill V WA7NWP
wa7nwp at gmail.com
Thu Feb 4 10:49:56 PST 2010
FYI - here's some comments from Mr Winmor. I'm forwarding this here
partially because it is interesting and useful development work and
partially because I'm hoping that it's a little kick in the pants for
us digital folks interested in more 'open' and 'amateur radio centric'
Bill - WA7NWP
---------- Forwarded message ----------
From: Rick Muething <rmuething at cfl.rr.com>
Date: Thu, Feb 4, 2010 at 8:16 AM
Subject: RE: [WINMOR] Winmor group clutter
To: WINMOR at yahoogroups.com
Our initial Beta testing of the RMS Express client and the WINMOR protocol
is certainly transitioning. Sure there are some remaining bugs and they
will be tracked down and fixed as time goes on but for the most part we have
proved the RMS Express client and the WINMOR protocol are a viable
alternative to Pactor as a way to move messages and attachments over HF.
We still have some important RMS Express and Protocol features in the works
that will need testing and tweaking and that comes from user feedback. These
1) Radio control in RMS Express
2) Keyboard to keyboard mode with WINMOR in RMS Express (this could be
either with ARQ (no errors but only two in the QSO) or via FEC (unproto
forward error correcting) which could support keyboard "nets" but won't
insure error free delivery. Vic and I are working on this.
3) FEC Broadcast mode including text files. This will be part of the
functionality and may be useful for some applications.
4) Propagation prediction for connecting to RMS WINMOR stations based on
Grid squares, time of day, frequency and Sun Spot number. This will be done
using the popular ITSHF (or ICECAP) public prediction program.
5) Auto update of the WinmorChannels.xml file when connected to the
internet. This file can already be downloaded via Telnet or RF connection
as described in the RMS Express Help on Frequency Lists.
We should have a new version of RMS Express with most of these new features
out in a few weeks depending on available time and alpha testing.
There is also some room for additional optimization of the protocol by
"tweaking" some internal protocol parameters but this fine tuning really can
only be done using controlled repeatable A-B type comparisons using a HF
simulator. It is just not possible to do this kind of tweaking over the air
with propagation constantly changing. As I have time I will look into this
and also try and compile some good engineering measurements of throughput
vs. S/N and channel type using the simulator. These measurements can be used
for comparisons with Pactor or other HF connected modes.
In our initial testing there were many that weren't familiar with message
forwarding and client to server connections. Now many better understand this
and how client to server connections eliminate the problem of frequency and
time co ordination we find in casual peer-to-peer connections. WINMOR was
designed and optimized for these client-server type of forwarding sessions
but may also have a place in peer to peer connections especially with
keyboard and FEC modes supported. We'll see in our testing of this how it
works and is accepted by users.
Finally we have made the WINMOR TNC windows "helper" application available
with documentation to aid other Windows programmers develop other client or
server applications. The WINMOR TNC basically implements the WINMOR
protocol and interfaces to the application much like a conventional hardware
TNC does. Those interested in using this tool to develop new applications
are welcome to contact me or Vic with ideas or questions.
Thanks for all your help, support and feedback. We have made a lot of
progress in a relatively short time through your efforts.
More information about the Seatcp