Date   
REU DSC logs

peter
 

Hi all,

Recent DSC logs.  004661010 Doha Radio QAT seems to have been absent in the logs since mid-November last.

Session Report for Peter Conway, G3UFI
Listening Location: Hastings UK, JO00gv (50°52'54"N   000°34'40"E)
Report Created On Jan 26, 2019
Receiver(s): WiNRADiO 313i/R1000/RSP1A/Spyverter
Antenna(s): ALA100M/ALA1530 Loops/Dipoles/Discone
Software: Multipsk 4.33 + other software
Report Sorted by Freq in Ascending order, Frequency Range 100.00 - 156525.00 kHz
--------------------------------------------------------------------------------------------------
YYYY-MM-DD UTC    kHz     Call       km    New Location
--------------------------------------------------------------------------------------------------
2019-01-25 15:17 2177.0   002241022  1079      Coruna Radio, ESP
2019-01-25 10:17 2177.0   002050480  159       Oostende Radio, BEL
2019-01-25 04:23 2177.0   002570000            Public Correspondance, NOR
2019-01-25 07:57 2177.0   002570300  923       Rogaland Radio, NOR
2019-01-25 06:45 2187.5   002470123  1298      Civitavecchia Radio, ITA
2019-01-25 06:09 2187.5   002470128  1749      Mazara del Vallo Radio, ITA
2019-01-25 18:12 2187.5   002470124  1840      Crotone Radio, ITA
2019-01-25 01:54 2187.5   002733700  2042      Saint Petersburg Radio, RUS
2019-01-25 04:14 2187.5   002711000  2425      Istanbul Radio, TUR
2019-01-25 03:50 2187.5   002320001  1036      Shetland Radio, SHE
2019-01-25 00:56 2187.5   002275400  955       CROSS La Garde, FRA
2019-01-25 01:26 2187.5   002241026  2909      Las Palmas Radio, CNR
2019-01-25 05:02 2187.5   002734446  2736      Taman Radio, RUS
2019-01-25 21:55 6312.0   007100002  7391      Recife Radio, BRA
2019-01-25 00:05 6312.0   004122100  9224      Shanghai Radio, CHN
2019-01-25 19:22 6312.0   006221111  3253      Alexandria Radio, EGY
2019-01-25 10:14 8414.5   002091000  3149      Cyprus Radio, CYP
2019-01-25 10:31 8414.5   002640570  2223      Constanta Radio, ROU
2019-01-25 00:00 8414.5   004122100  9224      Shanghai Radio, CHN
2019-01-25 00:31 8414.5   004162019  9792      Chilung Keelung Radio, TWN
2019-01-25 00:32 8414.5   005742030  9808      Da Nang Radio, VTN
2019-01-25 01:16 8414.5   006010001  9567      Cape Town Radio, AFS
2019-01-25 04:53 8414.5   006221111  3253      Alexandria Radio, EGY
2019-01-25 04:48 8414.5   007100001  9289      Rio de Janerio Radio, BRA
2019-01-25 00:16 8414.5   007100002  7388      Recife Radio, BRA
2019-01-25 12:57 12577.0  002371000  2209      Olympia Radio, GRC
2019-01-25 11:22 12577.0  002711000  2223      Istanbul Radio, TUR
2019-01-25 08:47 12577.0  004122100  9224      Shanghai Radio, CHN
2019-01-25 07:36  156525  002288217  124       Fecamp Signal station, FRA
--------------------------------------------------------------------------------------------------
Output Generated By WWSU 6.4 (2013, Alex Wiecek - VE3GOP, http://www.ve3gop.com)
29 stations logged during this Session (0 new)
Total number of DSC stations logged   -   721

73,

Peter   g3ufi


Virus-free. www.avast.com

219016306 activity

peter
 

Hi all,

Received a note from Dorte of 219016306 SIMAC Svendborg DNK that he will be running his first GMDSS course of the year - weeks 5/6 starting this coming Monday - so that is one to look out for.


73,    Peter

Virus-free. www.avast.com

REU DSC logs

peter
 

Hi all,

Recent DSC logs. 

Session Report for Peter Conway, G3UFI
Listening Location: Hastings UK, JO00gv (50°52'54"N   000°34'40"E)
Report Created On Jan 25, 2019
Receiver(s): WiNRADiO 313i/R1000/RSP1A/Spyverter
Antenna(s): ALA100M/ALA1530 Loops/Dipoles/Discone
Software: Multipsk 4.33 + other software
Report Sorted by Freq in Ascending order, Frequency Range 100.00 - 156525.00 kHz
--------------------------------------------------------------------------------------------------
YYYY-MM-DD UTC    kHz     Call       km    New Location
--------------------------------------------------------------------------------------------------
2019-01-24 06:08 2187.5   002470133  1270      Porto Torres Radio, ITA
2019-01-24 01:03 2187.5   002734414  2748      Arkhangelsk Radio, RUS
2019-01-24 06:29 2187.5   002733700  2042      Saint Petersburg Radio, RUS
2019-01-24 23:04 2187.5   002510100  1967      Reykjavik Radio, ISL
2019-01-24 04:05 2187.5   003313000  3417      Aasiaat Radio, GRL
2019-01-24 03:51 2187.5   002311000  1317      Torshavn Radio, FRO
2019-01-24 05:23 2187.5   002470002  1738      Palermo Radio, ITA
2019-01-24 01:19 2187.5   002630100  1562      Lisboa Radio, POR
2019-01-24 00:53 2187.5   002241026  2909      Las Palmas Radio, CNR
2019-01-24 17:23 2187.5   002712000  2906      Samsun Radio, TUR
2019-01-24 04:26 6312.0   007100002  7391      Recife Radio, BRA
2019-01-24 23:56 6312.0   004122100  9224      Shanghai Radio, CHN
2019-01-24 00:01 6312.0   005741040  9290      Hai Phong Radio, VTN
2019-01-24 23:27 6312.0   005743030  10241     Ho Chi Minh Ville Radio, VTN
2019-01-24 11:32 8414.5   002640570  2223      Constanta Radio, ROU
2019-01-24 00:04 8414.5   004122100  9224      Shanghai Radio, CHN
2019-01-24 00:07 8414.5   004162019  9792      Chilung Keelung Radio, TWN
2019-01-24 02:06 8414.5   005671000  9529      Bangkok Radio, THA
2019-01-24 00:01 8414.5   005741040  9290      Hai Phong Radio, VTN
2019-01-24 19:19 8414.5   006010001  9567      Cape Town Radio, AFS
2019-01-24 13:15 8414.5   006221111  3253      Alexandria Radio, EGY
2019-01-24 02:32 8414.5   007100002  7388      Recife Radio, BRA
2019-01-24 10:46 12577.0  002371000  2209      Olympia Radio, GRC
2019-01-24 10:07 12577.0  002711000  2223      Istanbul Radio, TUR
2019-01-24 10:04 12577.0  002241022  1079      Coruna Radio, ESP
2019-01-24 10:30 16804.5  002711000  2223      Istanbul Radio, TUR
2019-01-24 10:40 16804.5  005030001  14978     Charleville/Wilun R, AT, AUS
2019-01-24 10:09 16804.5  007100002  7388      Recife Radio, BRA
--------------------------------------------------------------------------------------------------
Output Generated By WWSU 6.4 (2013, Alex Wiecek - VE3GOP, http://www.ve3gop.com)
28 stations logged during this Session (0 new)
Total number of DSC stations logged   -   721

73,

Peter    g3ufi



Virus-free. www.avast.com

YaDDNet Data accuracy

John Pumford-Green
 

Hello all,

Following on from previous posts about accurate reporting of DSC Frequency on messages sent to YaDDNet...

I accept that occasionally mistakes can be made when setting up DSC monitoring, especially if you frequently change bands etc. and I don't want to dissuade anyone from sending data to YaDDNet.

There is no inbuilt "registration" process - anyone can set up their copy of YaDD (and DSC Decoder too, if they know what is required) to send data at any time.

This encourages participation and is A GOOD THING...

However with free and easy access comes the increased chance of "bad data" entering the database. In the past I knew all the participants, and if I spotted an error I could contact them, make sure they correct things at their end, and I would even make corrections to the YaDDNet database where possible, to retain the maximum amount of correct data.

Now there are many contributors and no way of letting many of them know they are sending duff data.

I want YaDDNet to be a repository of accurate DSC Message history - so that anyone might look up, for example "the last messages sent from Cross Corsen" or "has Lyngby been reported on HF this year?" .... etc...etc....

I have had to delete VERY MANY messages, that were otherwise useful, when it's evident that the reported frequency was wrong. I can't justify the additional time and effort needed to work out the correct frequency for the false data and apply corrections.

Deleting is the only option.

PLEASE, PLEASE, PLEASE be very careful to make sure YaDD and your Receiver are both set to the same frequency, BEFORE enabling remote log uploads.

If you use SCANNING in YaDD - PLEASE, PLEASE, PLEASE confirm that the receiver is ACTUALLY scanning BEFORE enabling remote log uploads.

Just enabling "SCANNING" within YaDD is not sufficient - you need to have the correct remote control functionality already working between your PC and your Receiver. YaDD will send frequency change instructions to a Perseus or other Icom CiV protocol receiver, but you MUST be certain you have set this up correctly. YaDD will not "magically" give you remote control of your receiver simply by enabling "SCANNING".

Today I see that one contributor, Gabriele1090swl, is still submitting data on ALL MF & HF bands, when it's obvious he's only tuned to 2187.5kHz.

He has got YaDD in "SCANNING" mode but his receiver IS NOT changing frequency!

This causes many false reports.

I have taken measures to DELETE all new logs from Gabriele1090swl automatically, every 10 minutes. I would rather lose one participant's data than to poison the database.

If Gabriele1090swl is reading this list - please TURN OFF SCANNING and remote log uploads.

Then...

Set YaDD to match the actual frequency of your receiver BEFORE you re-start remote log uploads, otherwise all your data will continue to be deleted.

If you NEED to use SCANNING - please sort out the remote control for your receiver BEFORE you start remote log uploads!

I will do the same when I spot any other long-term mis-reporting from any other participants.

Sorry for the bandwidth.

I'm very happy to see so many participants to YaDDNEt.

Please lets all play nicely otherwise the value of the database we've built up over the last 5+ years is diminished.

Cheers,

John

REU DSC logs

Andy <do1dxx@...>
 

Hi all,
 Recent DSC logs. Vy 73 - Andy - DO1DXX
***********************************************************
 Session Report for Andy Ibold, DO1DXX
 Listening Location: Alpen-GERMANY-JO31fn
 Position: 51°33,75'N  006°27,5' E
 Receiver(s): PERSEUS, ELAD FDM S2
 Antenna(s): HyEndFed Monoband for 80m, Miniwhip @5.8 m, TA53M Beam
 Software: Multipsk 4.31 - MS Excel
 ----------------------------------------------------------
DD-MM-YYYY - UTC MMSI kHz MRCC - Location ITU
 ----------------------------------------------------------
24/01/2019 14:14 002050480 2187,5 MRCC Oostende, BEL
24/01/2019 14:17 002191000 2187,5 MRCC Arhus - Lyngby, DNK
24/01/2019 14:18 002610210 2187,5 MRCC Gdynia - Witowo, POL
24/01/2019 14:22 002442000 2187,5 Netherland CG Radio, HOL
24/01/2019 14:26 002653000 2187,5 JRCC Sweden Rescue, SWE
24/01/2019 14:36 002111240 2187,5 Bremen Rescue Radio, DEU
24/01/2019 14:40 002241024 2187,5 MRCC Valencia, ESP
24/01/2019 14:41 002320024 2187,5 MRSC Stornoway, SCO
24/01/2019 14:41 002320007 2187,5 MRSC Humber, ENG
24/01/2019 14:59 002320014 2187,5 MRCC Falmouth, ENG
24/01/2019 14:59 002241022 2187,5 MRCC Finisterre - Coruna, ESP
24/01/2019 15:07 002470124 2187,5 Crotone Radio, ITA
24/01/2019 15:17 002570000 2187,5 All Norwegian Stations, NOR
24/01/2019 15:53 002570300 2187,5 MRCC Stavanger - Rogaland, NOR
24/01/2019 16:16 002470123 2187,5 Civitavecchia Radio, ITA
24/01/2019 16:26 002275100 2187,5 CROSS Gris Nez, FRA
24/01/2019 16:28 006221113 2187,5 RCC Cairo - Port Said, EGY
24/01/2019 16:35 002371000 2187,5 JRCC Piraeus - Olympia Radio, GRC
24/01/2019 17:06 002734446 2187,5 MRCC Novorossiysk - Taman, RUS
24/01/2019 17:14 002320004 2187,5 MRCC Aberdeen, SCO
24/01/2019 17:45 005671000 2187,5 RCC Bangkok - Bangkok (Nonthaburi), THA
24/01/2019 18:02 002320001 2187,5 MRSC Shetland, SCO
24/01/2019 18:47 002470002 2187,5 Palermo var. MRSC, ITA
24/01/2019 20:03 002275400 2187,5 CROSS La Garde, FRA
24/01/2019 21:33 002734411 2187,5 MRCC Novorossiysk, RUS
24/01/2019 21:42 002711000 2187,5 MRCC Ankara - Istanbul, TUR
24/01/2019 22:03 002241026 2187,5 MRCC Las Palmas, CNR
24/01/2019 23:06 002510100 2187,5 JRCC Iceland, ISL
24/01/2019 23:11 002712000 2187,5 MRCC Ankara - Samsun, TUR
25/01/2019 00:33 002320021 2187,5 MRSC Belfast, NIR
25/01/2019 02:38 002734419 2187,5 MRSC Astrakhan, RUS
25/01/2019 02:43 002652000 2187,5 MRCC Goteborg - Stockholm, SWE

24/01/2019 15:34 002241022 4207,5 MRCC Finisterre - Coruna, ESP
24/01/2019 16:36 004122100 4207,5 MRCC Shanghai, CHN
24/01/2019 21:23 003669995 4207,5 Portsmouth CAMSLANT, MRCC Portsmouth, VA, USA
24/01/2019 22:07 002711000 4207,5 MRCC Ankara - Istanbul, TUR
24/01/2019 23:56 003669991 4207,5 MRCC Boston, MA/MRCC Norfolk, VA, USA

24/01/2019 15:16 004310001 6312 Tokyo Sea Patrol Radio JCG HQ, JPN
24/01/2019 15:16 005030001 6312 Charleville/Wiluna RCC Australia, AUS
24/01/2019 15:17 002711000 6312 MRCC Ankara - Istanbul, TUR
24/01/2019 20:32 004122100 6312 MRCC Shanghai, CHN
24/01/2019 22:03 007100002 6312 MRCC Brazil - Recife, BRA
24/01/2019 23:29 005743030 6312 MRCC Vung Tau - Ho Chi Minh Ville, VTN

DSC CeNE Log 24 Jan 2019

Don
 

DSC "Dx" logs.

No 2 or 6 mHz logs.



Session Report for Don Tomkinson, KPC6NDB
Listening Location: Gothenburg, NE, DN90ww (40°56'24"N   100°09'27"W)
Report Created On Jan 24, 2019
Receiver(s): Perseus WR-G31DDC
Antenna(s): DXE-ARAV3-1P
Software: Spectran WWSU YaDD
Report Sorted by Freq in Ascending order, Frequency Range 40.00 - 29,700.00 kHz
--------------------------------------------------------------------------------------------------+
YYYY-MM-DD  UTC   kHz     Call        mi       Location
--------------------------------------------------------------------------------------------------+
2019-01-24 00:17 4207.5   003669990  1219      CAMSPAC Pt Reyes NMC, CA, USA
2019-01-24 00:39 4207.5   003669995  1329      NMN CAMSLANT Chesapeake, VA, USA
2019-01-24 05:04 4207.5   007251860  5427      Valparaiso Radio, CHL
2019-01-24 07:35 4207.5   003669997  1550      NMA COMMSTA Miami, FL, USA
2019-01-24 07:38 4207.5   002241022  4454      Coruna Radio, ESP
2019-01-24 08:04 4207.5   003669991  1531      NMF COMMSTA Boston, MA, USA
2019-01-24 08:06 4207.5   003669998   954      NMG COMMSTA New Orleans, LA, USA

2019-01-24 02:04 8414.5   007100002  5337      Recife Radio, BRA
2019-01-24 04:23 8414.5   007251860  5427      Valparaiso Radio, CHL
2019-01-24 08:23 8414.5   005030001  8580      Charleville / Wiluna Radio, QD, AUS
2019-01-24 10:28 8414.5   002241022  4454      Coruna Radio, ESP

2019-01-24 20:21 12577.0  003669997  1550      NMA COMMSTA Miami, FL, USA
2019-01-24 20:41 12577.0  003669998   954      NMG COMMSTA New Orleans, LA, USA

2019-01-24 19:37 16804.5  003669998   954      NMG COMMSTA New Orleans, LA, USA
2019-01-24 19:54 16804.5  003669990  1219      CAMSPAC Pt Reyes NMC, CA, USA
2019-01-24 20:59 16804.5  007100002  5337      Recife Radio, BRA
--------------------------------------------------------------------------------------------------+
Output Generated By WWSU 6.4.0.17 (2013, Alex Wiecek - VE3GOP, http://www.ve3gop.com)
16 stations logged during this Session (0 new)
Total number of stations logged from all listening locations -  2344  (1823 NDB, 32 Navtex, 134 DGPS, 
                                                                       437 DSC, 21 HAM, 72 OTHER)


-- 
A terrific Winter day in Nebraska!

Don


More Live Radio Fun and a Whole Lot More!

Don KPC6NDB
Gothenburg, NE
N40.9 W100.1 2600ft
BC1206CM Bearcat DX1000 FRG-100B
FunCube Dongle Pro+ ICF2010 Perseusx3
WR-G303e WR-G31DDCx7 SDRplay RSP2pro
R70 R71A w/250Hz R75x2 w/250Hz PRN1000x2
SDR-IQ SPR-4 SSR-1 w/NDB mod
SR-AF & LPF DSP599zx MFJ-784B HD-1418 AF-1 MSB-1
PA0RDT-MW @24ft DXE-ARAV3-1P @16ft
RYOAA McKay Dymek DA-100 AAx3
Z1501F Russian MW
80+ Vintage ADF/RDF
2344 Lifetime logs +64k logs submitted




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com


Re: Yet another uploader error ?

John Pumford-Green
 

Thanks Bob,

This confirms what I've always thought.

My recent "message" from 005030001, and Michael's from some years ago, can only have been a mis-decode that beat the mathematical error checks of the DSC Protocol.

Or someone with a misconfigured DSC system, which has been seen before too - the cargo ship Medi Kobe masquerading as Chennai / 004194401 springs to mind!


Cheers,

John

On 24/01/2019 22:36, Bob wrote:
John
The Australian government agency, ACMA, who are responsible for frequency management, have no assignments for 2187.5KHz.
My DSC logs on the RWW datbase go back to 2007 and I have never logged Charleville/Wiluna Radio on that frequency.
Regards
Bob
Adelaide, South Australia

Re: Yet another uploader error ?

Bob
 

John

The Australian government agency, ACMA, who are responsible for frequency management, have no assignments for 2187.5KHz.
My DSC logs on the RWW datbase go back to 2007 and I have never logged Charleville/Wiluna Radio on that frequency.

Regards
Bob
Adelaide, South Australia

On 24/01/2019 20:30, John Pumford-Green wrote:


On 24/01/2019 19:51, Mats A wrote:
To bad we don't have any contributors from these parts of the world.
Hi Mats,

We have in the past had a one or two from New Zealand, and still no reports of RCC Australia on MF.


Re: Yet another uploader error ?

Michael Oexner
 

Re: Yet another uploader error ?

Michael Oexner
 

Hi John,


Back in 2013 around the same time of the year I received the following
on 2187.5:


<17:40:27> <Selective call to a particular individual station>
<17:40:27> Called MMSI station address: 567287000 [Ship] (Thailand)
<17:40:27> Category: Safety
<17:40:27> MMSI self-identifier: 005030001 [Coast station: Charleville/Wiluna RCC Australia] (Australia)
<17:40:27> Telecommand 1: J3E telephony
<17:40:27> Telecommand 2: No information
<17:40:27> Neither RX/TX frequencies nor position supplied
<17:40:27> Check Sum: OK
<17:40:34> Date and time of decoding: 07/01/2013 17:40:34


At that time I was also wondering if it was a genuine reception, but
it certainly looked that way.



On 24/01/2019 08:46, John Pumford-Green via Groups.Io wrote:

Oddly, running the search for the first time in months I see that I've
made it to the list myself with a report of RCC Australia on 2187.5.

I know for a fact that my RX is on 2187.5, as I haven't touched it for
many months now, so perhaps this is a genuine one, or perhaps a very
subtle combination of errors that passed the parity and ECC checks in
DSC Decoder?

I've deleted a lot of erroneous loggings from the YaDDNet database, but
I'm still left with an odd one of my own - RCC Australia 005030001 on
2187.5kHz on January 11th at 16:50
One method I use to check for errors is to try and correlate the
loggings being reported by the "dubious" reporter with those from the
rest of the YaDDNet participants, and this usually shows which frequency
a reporter is *REALLY* tuned to. Even when the message under
investigation may not have been picked up elsewhere I assume that if
many messages before and after correlate with other loggings then I can
be confident in knowing which was the true frequency.
My record of RCC Australia on 2MHz wasn't received by anyone else on
another band at the same time, and all the adjacent logs I'd sent around
that time correlated with other peoples' 2MHz loggings, so I'm fairly
sure the receiver (it's out in a shed and untouched by human hands since
last summer) hadn't jumped to another band un-intended. It's an AR7030
with no remote/computer control, so once it's tuned it stays put.
From the DSCDecoder log files:

"raw":
120 120 56 30 06 70 00 108 00 50 30 00 10 118 126 126 126 126 126 126
126 122 [19-01-11 16:50:33]
"Formal":
563006700;(safety);from;005030001; test ACK;19-01-11 16:50:33;2187.5kHz
"Decoded":
563006700-SNG;(safety);from;[RCC Australia]-AUS; test ACK;19-01-11
16:50:33;2187.5kHz
I can only assume it's a rare case of a decode error that isn't detected
by the DSC protocol, and that the message really came from elsewhere?


Back to the question of falsely reported loggings in YaDDNET....
After much work this morning I've cleared out (and DELETED) as many
erroneous logs from the database as I can find. Most seem to be from
people who forget to set the correct frequency on YaDD after changing
the receiver, or change the frequency on YaDD and forget to change the
receiver.
Also it appears many come from people who are using YaDD in "Scanning"
mode, YaDD reports the frequency it *thinks* the receiver is on, and the
receiver sits on one frequency, unmoving.
YaDD does NOT perform any "handshaking" with a receiver, it sends the
new frequency command and blindly hopes that the receiver has obeyed.
If using YaDD's "Icom/Perseus" scanning feature PLEASE check that the
receiver is actually scanning before ticking "Remote Log Upload"...
The best method to handle a change of frequency is to firstly to turn
off the Remote Log Upload. Then change the receiver and change YaDD's
frequency selection box to match the new receiver frequency. And only
then should you re-enable Remote Logging uploads.
I'll continue to DELETE (rather than to attempt to correct) logs that
are obviously wrong, but I won't be doing it very often, as it's quite a
tedious job.
Cheers,
John

--
vy 73 + gd DX,

Michael

Re: Yet another uploader error ?

Mats A
 

On Thu, Jan 24, 2019 at 09:30 PM, John Pumford-Green wrote:
It would have been interesting if the DSC Protocol itself encoded the time into the message as it was transmitted, perhaps?
The protocol itself was "invented" when clocks were analog onboard ships, and to change the protocol to include time would be a major challenge as it would break the DSC function on lots and lots of ships. We just have to live with it.
However there are discussions in IMO to include some kind of ALE function within the DSC protocol to ease the burden on the sailors to establish a J3ETP connection considering various conditions such as propagation. Perhaps this protocol will be a bit smarter.

Brgds
//Mats

Re: Yet another uploader error ?

John Pumford-Green
 

On 24/01/2019 19:51, Mats A wrote:
To bad we don't have any contributors from these parts of the world.
Hi Mats,

We have in the past had a one or two from New Zealand, and still no reports of RCC Australia on MF.

On the timestamp issue - For YaDDNet Dirk was very insistent that YaDD would not timestamp the messages, that the timestamps be added by the "remote logging server" to ensure a degree of certainty - he wanted to avoid problems with individual contributors not setting their PC clocks correctly.

This means that the times shown on the messages are the times that the UDP message is processed here, after travelling across the internet - and occasionally there might be a 1 or two second discrepancy on identical messages, as the propagation delay of the internet is rather elastic.

It would have been interesting if the DSC Protocol itself encoded the time into the message as it was transmitted, perhaps?

I might not be able to keep the database "clean" continuously, but every now and then I spend a few hours trying to get rid of mistakes.

It's easy enough to set YaDD up correctly so that the data is right, but it's also too easy to make a mistake, and then to send days, and days, and days worth of mis-reported messages, which takes me a bit of time to weed out!

Cheers,

John

Re: Yet another uploader error ?

John Pumford-Green
 

On 24/01/2019 18:53, Alan Gale wrote:
It could be genuine, at 1650 UTC there was a Greyline path to that are
Hello Alan

My qualms over RCC Australia on 2MHz aren't due to doubts over whether I could receive something on 2MHz from Australia - I'm fairly confident I'd have heard them many times by now over the years, given the right conditions - it's that they aren't active on MF, to the best of my knowledge.

No-one else has ever reported them and none of the official GMDSS documents show them as having a capability on 2MHz.

While I was clearing out the duff data this morning I found some other reports of RCC Australia on 2MHz, but these were easily discounted when I compared the what other reporters were hearing at the same time, it became obvious that there was a mistake with the reported frequency.

My own logging is "genuine" - in that all the other loggings I made around that time correlate with other peoples' 2MHz reports, and with none of their HF reports. So I'm confident I was on 2MHz.

I can only assume it was one of those rare cases of a collection of errors that still gave the correct overall Error Checksum calculation. I've seem plenty of others over the years that slip through the error checking. DSC is good, but it's not totally foolproof....

Unless someone else can provide a fragment of the same message that I might use to do some number crunching with, I think I'll delete my record from the database, as it can only be an error.

Cheers,

John

Re: Yet another uploader error ?

Mats A
 

Hi all.

I'm impressed by the efforts you put into this, and I appreciate it.

I support your decision to delete rather than to correct loggings being reported by the "dubious" reporters.
One neat function to better correlate wrong records would be if the correct time of reception would be encoded in the message (blitzortung.org do it with great success), however as we know there are other soft- and hardware variables affecting the timing.

Regarding RCC Australia on 2187.5 MHz sounds dubious as neither GMDSS MASTER PLAN or ITU-MARS has any records fo DSC on MF.
I have met some of the persons from the Australian maritme and telecom administration, and my impression was that these Aussies know what they do.

Anyway, as we know coast stations may not always be used as they are listed..

Best regards
//Mats
To bad we don't have any contributors from these parts of the world.

Re: Yet another uploader error ?

Alan Gale
 

At 12:58 24/01/2019, you wrote:


Hi John,

It could be genuine, at 1650 UTC there was a Greyline path to that area, and of course many of
the hams are often sat around the top end of 80 metres around that time waiting for the short
DX window to that area which often produces New Zealand and Australian contacts. Although the
frequency is slightly lower, RCC Australia are probably running higher power, so at this stage
of the sunspot cycle it certainly wouldn't be impossible for it to be heard here.

I'm also using a 7030 as well, and as you said, it isn't easy to get the wrong frequency
without making the effort, and if it had been on a higher frequency then there should have been
other logs showing it on there that same time.


73 for now, Alan.




On 24/01/2019 08:46, John Pumford-Green via Groups.Io wrote:
Oddly, running the search for the first time in months I see that I've made it to the list myself with a report of RCC Australia on 2187.5.
I know for a fact that my RX is on 2187.5, as I haven't touched it for many months now, so perhaps this is a genuine one, or perhaps a very subtle combination of errors that passed the parity and ECC checks in DSC Decoder?

I've deleted a lot of erroneous loggings from the YaDDNet database, but I'm still left with an odd one of my own - RCC Australia 005030001 on 2187.5kHz on January 11th at 16:50

One method I use to check for errors is to try and correlate the loggings being reported by the "dubious" reporter with those from the rest of the YaDDNet participants, and this usually shows which frequency a reporter is *REALLY* tuned to. Even when the message under investigation may not have been picked up elsewhere I assume that if many messages before and after correlate with other loggings then I can be confident in knowing which was the true frequency.

My record of RCC Australia on 2MHz wasn't received by anyone else on another band at the same time, and all the adjacent logs I'd sent around that time correlated with other peoples' 2MHz loggings, so I'm fairly sure the receiver (it's out in a shed and untouched by human hands since last summer) hadn't jumped to another band un-intended. It's an AR7030 with no remote/computer control, so once it's tuned it stays put.

From the DSCDecoder log files:


"raw":

120 120 56 30 06 70 00 108 00 50 30 00 10 118 126 126 126 126 126 126 126 122 [19-01-11 16:50:33]

"Formal":

563006700;(safety);from;005030001; test ACK;19-01-11 16:50:33;2187.5kHz

"Decoded":

563006700-SNG;(safety);from;[RCC Australia]-AUS; test ACK;19-01-11 16:50:33;2187.5kHz

I can only assume it's a rare case of a decode error that isn't detected by the DSC protocol, and that the message really came from elsewhere?



Back to the question of falsely reported loggings in YaDDNET....

After much work this morning I've cleared out (and DELETED) as many erroneous logs from the database as I can find. Most seem to be from people who forget to set the correct frequency on YaDD after changing the receiver, or change the frequency on YaDD and forget to change the receiver.

Also it appears many come from people who are using YaDD in "Scanning" mode, YaDD reports the frequency it *thinks* the receiver is on, and the receiver sits on one frequency, unmoving.

YaDD does NOT perform any "handshaking" with a receiver, it sends the new frequency command and blindly hopes that the receiver has obeyed.

If using YaDD's "Icom/Perseus" scanning feature PLEASE check that the receiver is actually scanning before ticking "Remote Log Upload"...

The best method to handle a change of frequency is to firstly to turn off the Remote Log Upload. Then change the receiver and change YaDD's frequency selection box to match the new receiver frequency. And only then should you re-enable Remote Logging uploads.

I'll continue to DELETE (rather than to attempt to correct) logs that are obviously wrong, but I won't be doing it very often, as it's quite a tedious job.

Cheers,

John

REU DSC logs

peter
 

Hi all,

Recent DSC logs.

Session Report for Peter Conway, G3UFI
Listening Location: Hastings UK, JO00gv (50°52'54"N   000°34'40"E)
Report Created On Jan 24, 2019
Receiver(s): WiNRADiO 313i/R1000/RSP1A/Spyverter
Antenna(s): ALA100M/ALA1530 Loops/Dipoles/Discone
Software: Multipsk 4.33 + other software
Report Sorted by Freq in Ascending order, Frequency Range 100.00 - 156525.00 kHz
--------------------------------------------------------------------------------------------------
YYYY-MM-DD UTC    kHz     Call       km    New Location
--------------------------------------------------------------------------------------------------
2019-01-23 16:56 2177.0   002570100  1143      Tjome Radio, NOR
2019-01-23 01:57 2187.5   002470123  1298      Civitavecchia Radio, ITA
2019-01-23 17:32 2187.5   002715000  2465      Izmir Radio, TUR
2019-01-23 19:32 2187.5   002610210  1146      Witowo Radio, POL
2019-01-23 01:20 2187.5   002652000  1476      Stockholm Radio, SWE
2019-01-23 00:04 2187.5   002570700  1974      Bodoe Radio, NOR
2019-01-23 21:17 2187.5   006052110  1595      Alger Radio, ALG
2019-01-23 05:38 2187.5   002570600  1519      Orlandet Radio, NOR
2019-01-23 21:57 2187.5   002712000  2906      Samsun Radio, TUR
2019-01-23 18:36 2187.5   002770330  1469      Klaipeda RCC, LTU
2019-01-23 21:38 6312.0   003669990  8699      Point Reyes Radio, CA, USA
2019-01-23 21:06 6312.0   003669995  6057      Portsmouth Radio, VA, USA
2019-01-23 18:19 6312.0   005030001  14325     Charleville/Wilun R, AT, AUS
2019-01-23 18:12 6312.0   005743030  10241     Ho Chi Minh Ville Radio, VTN
2019-01-23 21:04 8414.5   003669995  6057      Portsmouth Radio, VA, USA
2019-01-23 00:03 8414.5   004122100  9224      Shanghai Radio, CHN
2019-01-23 00:26 8414.5   005671000  9529      Bangkok Radio, THA
2019-01-23 00:01 8414.5   006010001  9567      Cape Town Radio, AFS
2019-01-23 06:32 8414.5   006221111  3253      Alexandria Radio, EGY
2019-01-23 01:52 8414.5   007100002  7388      Recife Radio, BRA
2019-01-23 12:20 12577.0  004122100  9224      Shanghai Radio, CHN
2019-01-23 10:31 16804.5  002711000  2223      Istanbul Radio, TUR
2019-01-23 17:22  156525  002320014  406       Falmouth Radio, ENG
2019-01-23 04:11  156525  002275200  219       CROSS Jobourg, FRA
2019-01-23 02:48  156525  002320011  45        Solent Radio, ENG
--------------------------------------------------------------------------------------------------
Output Generated By WWSU 6.4 (2013, Alex Wiecek - VE3GOP, http://www.ve3gop.com)
25 stations logged during this Session (0 new)
Total number of DSC stations logged   -   721

73,

Peter   g3ufi


Virus-free. www.avast.com

Re: Yet another uploader error ?

John Pumford-Green
 

On 24/01/2019 08:46, John Pumford-Green via Groups.Io wrote:
Oddly, running the search for the first time in months I see that I've made it to the list myself with a report of RCC Australia on 2187.5.
I know for a fact that my RX is on 2187.5, as I haven't touched it for many months now, so perhaps this is a genuine one, or perhaps a very subtle combination of errors that passed the parity and ECC checks in DSC Decoder?

I've deleted a lot of erroneous loggings from the YaDDNet database, but I'm still left with an odd one of my own - RCC Australia 005030001 on 2187.5kHz on January 11th at 16:50

One method I use to check for errors is to try and correlate the loggings being reported by the "dubious" reporter with those from the rest of the YaDDNet participants, and this usually shows which frequency a reporter is *REALLY* tuned to. Even when the message under investigation may not have been picked up elsewhere I assume that if many messages before and after correlate with other loggings then I can be confident in knowing which was the true frequency.

My record of RCC Australia on 2MHz wasn't received by anyone else on another band at the same time, and all the adjacent logs I'd sent around that time correlated with other peoples' 2MHz loggings, so I'm fairly sure the receiver (it's out in a shed and untouched by human hands since last summer) hadn't jumped to another band un-intended. It's an AR7030 with no remote/computer control, so once it's tuned it stays put.

From the DSCDecoder log files:


"raw":

120 120 56 30 06 70 00 108 00 50 30 00 10 118 126 126 126 126 126 126 126 122 [19-01-11 16:50:33]

"Formal":

563006700;(safety);from;005030001; test ACK;19-01-11 16:50:33;2187.5kHz

"Decoded":

563006700-SNG;(safety);from;[RCC Australia]-AUS; test ACK;19-01-11 16:50:33;2187.5kHz

I can only assume it's a rare case of a decode error that isn't detected by the DSC protocol, and that the message really came from elsewhere?



Back to the question of falsely reported loggings in YaDDNET....

After much work this morning I've cleared out (and DELETED) as many erroneous logs from the database as I can find. Most seem to be from people who forget to set the correct frequency on YaDD after changing the receiver, or change the frequency on YaDD and forget to change the receiver.

Also it appears many come from people who are using YaDD in "Scanning" mode, YaDD reports the frequency it *thinks* the receiver is on, and the receiver sits on one frequency, unmoving.

YaDD does NOT perform any "handshaking" with a receiver, it sends the new frequency command and blindly hopes that the receiver has obeyed.

If using YaDD's "Icom/Perseus" scanning feature PLEASE check that the receiver is actually scanning before ticking "Remote Log Upload"...

The best method to handle a change of frequency is to firstly to turn off the Remote Log Upload. Then change the receiver and change YaDD's frequency selection box to match the new receiver frequency. And only then should you re-enable Remote Logging uploads.

I'll continue to DELETE (rather than to attempt to correct) logs that are obviously wrong, but I won't be doing it very often, as it's quite a tedious job.

Cheers,

John

REU DSC logs

Andy <do1dxx@...>
 

Hi all,
 Recent DSC logs. Vy 73 - Andy - DO1DXX
***********************************************************
 Session Report for Andy Ibold, DO1DXX
 Listening Location: Alpen-GERMANY-JO31fn
 Position: 51°33,75'N  006°27,5' E
 Receiver(s): PERSEUS, ELAD FDM S2
 Antenna(s): HyEndFed Monoband for 80m, Miniwhip @5.8 m, TA53M Beam
 Software: Multipsk 4.31 - MS Excel
 ----------------------------------------------------------
DD-MM-YYYY - UTC MMSI kHz MRCC - Location ITU
 ----------------------------------------------------------
23/01/2019 17:29 002320001 2187,5 MRSC Shetland, SCO
23/01/2019 17:29 002320018 2187,5 MRSC Holyhead, WLS
23/01/2019 17:33 002711000 2187,5 MRCC Ankara - Istanbul, TUR
23/01/2019 17:34 002712000 2187,5 MRCC Ankara - Samsun, TUR
23/01/2019 17:34 002610210 2187,5 MRCC Gdynia - Witowo, POL
23/01/2019 17:36 002320024 2187,5 MRSC Stornoway, SCO
23/01/2019 17:39 002442000 2187,5 Netherland CG Radio, HOL
23/01/2019 17:40 002371000 2187,5 JRCC Piraeus - Olympia Radio, GRC
23/01/2019 17:55 002191000 2187,5 MRCC Arhus - Lyngby, DNK
23/01/2019 18:04 002275400 2187,5 CROSS La Garde, FRA
23/01/2019 18:06 002570000 2187,5 All Norwegian Stations, NOR
23/01/2019 18:35 002770330 2187,5 Klaipeda Rescue Centre, LTU
23/01/2019 19:55 002275100 2187,5 CROSS Gris Nez, FRA
23/01/2019 19:59 002713000 2187,5 MRCC Ankara - Antalya, TUR
23/01/2019 20:06 002510100 2187,5 JRCC Iceland, ISL
23/01/2019 20:10 002470002 2187,5 Palermo var. MRSC, ITA
23/01/2019 20:11 002320004 2187,5 MRCC Aberdeen, SCO
23/01/2019 20:35 002241024 2187,5 MRCC Valencia, ESP
23/01/2019 21:12 002570300 2187,5 MRCC Stavanger - Rogaland, NOR
23/01/2019 21:26 002734487 2187,5 MRCC Novorossiysk - Taganrog, RUS
23/01/2019 21:53 002050480 2187,5 MRCC Oostende, BEL
23/01/2019 21:55 002734419 2187,5 MRSC Astrakhan, RUS
23/01/2019 22:06 002470124 2187,5 Crotone Radio, ITA
23/01/2019 22:11 002470120 2187,5 Augusta Radio, ITA
23/01/2019 22:28 002130100 2187,5 MRSC Batumi, GEO
23/01/2019 22:30 002320007 2187,5 MRSC Humber, ENG
23/01/2019 23:05 002320010 2187,5 MRCC Dover, ENG
23/01/2019 23:54 002470125 2187,5 Genova Radio, ITA
24/01/2019 00:11 002652000 2187,5 MRCC Goteborg - Stockholm, SWE
24/01/2019 00:41 002241022 2187,5 MRCC Finisterre - Coruna, ESP
24/01/2019 00:55 002241026 2187,5 MRCC Las Palmas, CNR
24/01/2019 01:41 002640570 2187,5 Constanta Hbr Master, ROU
24/01/2019 02:38 002275200 2187,5 CROSS Jobourg, FRA
 
23/01/2019 17:24 004122100 4207,5 MRCC Shanghai, CHN
23/01/2019 17:33 002711000 4207,5 MRCC Ankara - Istanbul, TUR
23/01/2019 18:06 002640570 4207,5 Constanta Hbr Master, ROU
23/01/2019 19:21 005030001 4207,5 Charleville/Wiluna RCC Australia, AUS
23/01/2019 19:22 006221111 4207,5 RCC Cairo - Alexandria, EGY
23/01/2019 23:54 002241022 4207,5 MRCC Finisterre - Coruna, ESP
24/01/2019 00:02 005741040 4207,5 MRCC Hai Phong, VTN
24/01/2019 00:41 003669995 4207,5 Portsmouth CAMSLANT, MRCC Portsmouth, VA, USA
 
23/01/2019 18:09 005030001 6312 Charleville/Wiluna RCC Australia, AUS
23/01/2019 18:14 005743030 6312 MRCC Vung Tau - Ho Chi Minh Ville, VTN
23/01/2019 23:21 004122100 6312 MRCC Shanghai, CHN
24/01/2019 00:15 002711000 6312 MRCC Ankara - Istanbul, TUR
 

Re: Yet another uploader error ?

John Pumford-Green
 

Rich, all.

I have always hoped that YaDDNEt would be a real-time repository of as much of the MF/HF DSC traffic as possible, and BE ACCURATE, so we might be confident when seeing a DSC Message that it was on the frequency reported.

I've spend MANY, MANY, MANY hours detecting errors in reported frequency in n attempt to keep the data as accurate as possible. Initially I corrected reported frequency errors when I could work out what the true frequency really was, but more recently I've simply DELETED entries that are obviously wrongly reported.

Even more recently I've just given up looking for them, as it's simply too time consuming.

I've even written a script to search of "dubious" entries, which I use to give me an idea of where mistakes may have made it into the database:

http://gm4slv.plus.com:8000/pages/php/test/sanity_3.php

This doesn't catch everything, but it uses a set of search terms that show where things might be wrong.

Oddly, running the search for the first time in months I see that I've made it to the list myself with a report of RCC Australia on 2187.5.

I know for a fact that my RX is on 2187.5, as I haven't touched it for many months now, so perhaps this is a genuine one, or perhaps a very subtle combination of errors that passed the parity and ECC checks in DSC Decoder?

However, the number of "dubious" results from the last 30 days shows there are many people who need to take more care in setting up YaDD and tuning their radios to make sure they match!

I might, if I can be bothered, spend a couple of hours today and go through the database to DELETE any data that is obviously wrongly attributed, but even so, I'm sure it won't take too long before the errors return if people can't take more care when setting up YaDD.

Cheers,

John

On 23/01/2019 21:56, Richard Ware wrote:
Folks
This is getting silly (see attachment)
Alger now on 16Mc/s?

DSC logs from Bari - South Italy - 20190124

edoardo nicoletti
 

Listening Report for Edoardo Nicoletti, SWL I7-082/BA
Listening Location: Bari, JN81kd
Report Generated On Jan 23 2019
Equipment
Receiver(s): Perseus SDR
Antenna(s): Wellbrook ALA 1530LNP - MaxiWhip
Software: YaDD
------------------------------------------------------------------------------------------------------------
20190123 0737 16804.5 004122100 Shanghai Radio, CHN, 8887 Km
20190123 0753 16804.5 005030001 Charleville / Wiluna Radio, AUS, 13006 Km
20190123 0824 16804.5 004310001 Tokyo Coast Guard Radio, JPN, 9691 Km
20190123 0900 16804.5 005743030 Ho Chi Minh Ville Radio, VTN, 9283 Km
20190123 1558  8414.5 004122100 Shanghai Radio, CHN, 8887 Km
20190123 1613  8414.5 002241022 Coruna Radio, ESP, 2048 Km
20190123 1649  8414.5 005741040 Hai Phong Radio, VTN, 8447 Km
20190123 1651  8414.5 002371000 Olympia Radio, GRC, 690 Km
20190123 1705  8414.5 005671000 Bangkok Radio, THA, 8501 Km
20190123 1802  2187.5 002275400 CROSS La Garde, FRA, 905 Km
-------------------------------------------------------------------------------------------------------------
73, Edoardo