----- Original Message -----
Sent: Friday, September 02, 2011 2:08
PM
Subject: Re: LF: ros
That's an unfortunate start to the
winter !
The MF mode has had very
little usage compared to the HF , so its quite
possible some bug's lurk within
as with the HF side,
operation is unique , however all be it
functional , its worth noting , the
whole mode/project is the
some work of one person ..
It is firstly a qso mode
, so as noticed the beacon side
tends to favour users of the channel ,
As noted by Gary , there was a
beacon-timer freeze problem with the previous
issue
Programme freeze , was that PC
lock , or just ROS ? not experienced any freeze
problems for some time now
Psk-Reporter can offer some
history data from the stats page, unique band
spots for 136/500
can be obtained by setting
the Band = unknown. but to date there is no
searchable data base
for the ros system.. ( A stored
history of the received text would be
useful....but not avilable)
Static problem's , a bit subjective
may be ? but if the same occurs in the
near future , an audio recording would be
useful for evaluation ,
The s/n indication is a
average value of the received frame , with the
'Margin' being the amount of signal over the
'limit of resolution'
so at the lower levels
its quite possible a % of the data was
under the threshold , low level decodes are rarely
100% crc , but it is a
live 'rtty' mode, structured
for data rate V s/n , at levels of -30 >
-33dB average it is predictable there will be a level
of corruption ?
Tnx all - G..
Sent: Friday, September 02, 2011 10:22 AM
Subject: Re: LF: ros
John & All,
Apparently the latest ROS version v6.6.9 has been changed to prevent
beacon mode stopping when other signals encountered.
73, Gary - G4WGT.
On 2 September 2011 06:39, John GM4SLV
<[email protected]>
wrote:
On Thu, 1 Sep 2011 15:45:19 -0800
Laurence KL7UK <
[email protected]>
wrote:
>
> KL7UK now ROS 500kHz for the night
-
>
>
ROS is NOT the mode for
this sort of test!
I came to the shack at 05:15 UTC to find the
regular beaconing had
stopped running. Apparently if a signal is received
the software stops
any beacon (to avoid causing QRM) and in this instance
it didn't restart
the beacon timer afterwards - therefore my log shows
that at 23:34 UTC
there was a (not correctly decoded) RX frame, and after
that no further
beacons were sent.
Sorry.
WSPR would seem
to be the mode for finding an opening, not ROS,
I won't be using it
again in anger. I find as a QSO mode it is very
ponderous, which I can
accept for the ability to resolve signals deep
in the noise, inaudible
even, but it didn't seem to perform very well in
the presence of
lightning QRN - requiring signals to be audible before
it decoded
them.
On top of that I find the actual software to be very difficult
to
drive. As Mal pointed out, the continuous appearance if spots
&
information of activity on every other band is very annoying,
and
seemingly can't be turned off. The Beacon functionality is
seriously
flawed for the use we put it to. The secret nature of the modem
means
no one else can integrate ROS into existing (more user
friendly)
software (fldigi, multipsk etc).
The PSKreporter
spot-collecting website, while a laudable project, is
no way as usable as
the WSPRNet online database, which makes finding
and tabulating reception
reports more difficult.
I'll stick with WSPR for beaconing, which is
what it was intended for,
and look into other MFSK modes for
QSOs.
Anyone interested in some MFSK-4 tests over the
weekend?
Cheers,
John
GM4SLV
