Re: Possible 006010060
Hi Peter,toggle quoted messageShow quoted text
My feeling is that your message is a errored version of a call from Capetown 006010001
YaDDNet shows a TEST call FROM the same vessel at 03:00 addressed to Capetown (reported by OE3WYC). I doubt if there was also a TEST request sent by the vessel to 006010060 at the same time that might have caused the transmission you're hoping to have received to have been sent from 006010060.
I don't know how MutiPSK indicates the various errors, but it's obvious that your message has some problem(s). I'm not sure which symbol is being reported as having parity errors in DX and RX copies (Error (DX=0111011001 RX=0001011001) )
The final "3" in the sender MMSI is doubtful though.
0 60 10 6 3
00 60 10 06 03 => 006010060 since the final digit is usually zero and always ignored in MultiPSK, DSCDecoder and YaDD. SeaTTY does show the final hidden digit, and Rich can perhaps confirm that in >99% of cases it's a zero. Although some senders DO have a non-zero final digit to indicate a sub-station on a larger vessel, I don't think this is the case here.
I'm afraid it's too dubious, especially with the matching TEST REQuest to Capetown reported by OE3WYC, to think it's from 006010060 / Imtech.
On 07/04/2019 16:57, peter via Groups.Io wrote: