Thanks Joe,
This is the pattern from the software , should be the same !
Symbol time is important , the data clock needs to be as good as
possible , by 'good' that is as good as a 'pc' not as in uHz , clock
drift and/or pulse width will affect the minimum decode s/n ,
Good luck 73-G..
Symbol times
Opera05: 0.128 s
Opera1: 0.256 s
Opera2: 0.512 s
Opera4: 1.024 s
Opera8: 2.048 s
Opera32: 8.192 s
VO1NA
11011010100101010110100101100110100101011001100110101010101010100110011001100101100101101001011001011010011010101010101010101010100110101010101010010101011010010110101010011001100110011010101010101001011001010110010110010110100101101001101
--------------------------------------------------
From: <[email protected]>
Sent: Thursday, June 20, 2013 11:14 PM
To: <[email protected]>
Subject: LF: VO1NA OP32
Dear Group,
With many thanks to the group members for their kind assistance, Markus
and Graham in particular, A satisfactory exciter is presently QRV
and will be returning the OP32 code (that Makus recently sent by email)
on 137.555 kHz starting tonight 20 June at 2359 utc. The back-yard photon
flux will be ~10^30/s.
Good luck to any who will be monitoring and please feel free to let
me know if you receive an indication of the sigs.
73
Joe
This electronic communication is governed by the terms and conditions at
http://www.mun.ca/cc/policies/electronic_communications_disclaimer_2012.php
|
