Date   
Re: Meteor Scatter

Joe K1YOW
 

Hi Tony,

I probably missed your original post. I operate some meteor scatter mainly
on 6M. 2M is much more difficult, since the ping times are around 1/8th the
time one gets on 6M. I use WSJT-X and for 6M and 2M can use an IC-746PRO
with a RIGblaster or if on 6M only, my TS-590SG. My antenna is a small 6 ft
boom log periodic antenna, 21 elements, but it probably only uses 2-3
elements on each band.

I find that my setup on 6M meteor scatter is marginal. While I do work
stations, folks running bigger 6M beams and 200W to 1KW do much, much better
than my 100W. On 2M I have heard some pings, but no QSOs yet.

If you check out DX Maps, every morning, you will see meteor scatter QSOs in
blue lines on the map. Morning is best.

Joe, K1YOW

-----Original Message-----
From: main@digitalradio.groups.io [mailto:main@digitalradio.groups.io] On
Behalf Of Anthony Bombardiere
Sent: Monday, January 22, 2018 6:37 PM
To: main@digitalradio.groups.io
Subject: Re: [digitalradio] Meteor Scatter

All:

I was wondering what the consensus is among the group regarding meteor
scatter?
I guess there's no interest?

Tony -K2MO

Re: Meteor Scatter

Tony
 

All:

I was wondering what the consensus is among the group regarding meteor scatter?
I guess there's no interest?

Tony -K2MO

Shortwave Radiogram, 20-21 Jan

kd9xb
 

Shortwave Radiogram this weekend is mostly the usual MFSK32, but there is one item in Thor 22 so that we can practice processing images in this mode. Any slant and phase errors can be adjusted quickly. 

Stories this weekend, each with an image, and all good arguments for maintaining shortwave:

Iranian MPs want to prevent use of foreign apps*
Uganda might launch its own social media platforms* 
Russian moves towards creation of independent internet*
 
Details and schedule:
 
 
Kim
KD9XB
 

Re: Time to end the digital charade on 60M ? #JT65

Andrew O'Brien
 

Sorry to hear that news . I am traveling in Europe for a few days but will attend to this when I get back.

Andy .

On Jan 10, 2018, at 2:16 AM, Ken Sprouse <wa3fkg@...> wrote:

Ken wa3fkg died November of 2015. Please release him from your group.
His wife
Linda

Sent from my Kindle Fire
Life without God is like an un-sharpened pencil. It has no point.
The app said Windows 7 or better. So I installed Linux!
Beretta - The ultimate point and click user interface.


Re: Meteor Scatter

Joe
 

On 1/13/2018 4:49 PM, Anthony Bombardiere wrote:
Could be the lack of publicity or the old stigma associated with MS with many believing it takes big power and large antennas. Not the case anymore thanks to Joe Taylor's WSJT modes.

Any ideas?
This article might interest you.

Truckers Communicate With Dispatchers Via Meteors

<http://articles.orlandosentinel.com/1989-04-30/news/8904305494_1_meteor-scatter-meteor-trails-dispatchers>

Joe

Meteor Scatter

Tony
 

All:

I was wondering what the consensus is among the group regarding meteor scatter? It's arguably the most fascinating digital modes in ham radio (what's not fascinating about bouncing signals off of ionized meteor trails?) yet there's been little gain in popularity over the years.

Could be the lack of publicity or the old stigma associated with MS with many believing it takes big power and large antennas. Not the case anymore thanks to Joe Taylor's WSJT modes.

Any ideas?

Tony -K2MO

Re: Time to end the digital charade on 60M ? #JT65

Ken Sprouse <wa3fkg@...>
 

Ken wa3fkg died November of 2015. Please release him from your group.
His wife
Linda

Sent from my Kindle Fire
Life without God is like an un-sharpened pencil. It has no point.
The app said Windows 7 or better. So I installed Linux!
Beretta - The ultimate point and click user interface.

ARIM Messaging Program v1.1

Bob NW8L
 

Hello,
 
ARIM v1.1 is available for download:
 
https://www.whitemesa.net/arim/arim.html#inst
 
Includes bug fixes, more graceful handling of link loss
situations in ARQ operation, and a means for sending predefined
initialization commands to the ARDOP TNC when attaching to it.
This is useful for TNC commands not managed by ARIM, such as
radio control commands.
 
Details in change log excerpt below. Special thanks to Doug WB6VAC
for help in beta testing.
 
Files are also available at the ardop applications Files area at
groups.io:
 
https://ardop.groups.io/g/applications/files
 
and in the Files area at the arim-ham Yahoo group:
 
https://groups.yahoo.com/neo/groups/arim-ham/files
 
Station NW8L will be on dial 14.066 in daytime, 7.101 at night and
sometimes 10.131 for a while in-between, for testing.
 
73, Bob NW8L
 
 
v1.1  04Jan2018
---------------
1. Fix bug in ARQ mode where incoming commands were not
   parsed properly if split across multiple ARDOP ARQ frames.
   Reported by Doug, WB6VAC, thanks!
2. Ignore unexpected PINGACK frames received from TNC.
   Reported by Doug, WB6VAC, thanks!
3. In ARQ IRS state, if link is lost, print a "timeout" notice
   to the Traffic Monitor when ARIM times out and returns to
   the idle state.
4. During an ARQ inbound or outbound connection attempt, if
   link is lost, print a "timeout" notice to the Traffic
   Monitor when ARIM times out and returns to the idle state.
5. In pilot ping mode, increase delay between receipt of PINGACK
   frame and start of next transmission to guarantee that the
   TNC is ready to proceed.
6. Add facility to send arbitrary TNC initialization commands
   upon ATTACHING to a TNC. These commands are specified in the
   arim.ini configuration file, in the [tnc] section, using new
   parameter 'tnc-ini-cmd'. Up to 32 of these commands may be
   defined for each TNC, each with a maximum length of 128
   characters. For exammple:
      tnc-init-cmd = SLOWCPU TRUE
      tnc-init-cmd = DRIVELEVEL 90
   This is useful for passing commands which are not understood
   by ARIM, such as future radio control commands, and for TNC
   test and development purposes. Commands are send verbatim
   without validation of the command name or its parameters.
7. Move source code files into 'src' subdir, begin refactoring
   of protocol state machine and ARQ code.
8. Update PDF Help file.

Re: HRD Logbook Crash Fix

John Netro
 

No problem I just wanted to put that out, I have had the Logbook to stop working because of leaving it running to many days. I keep it running cause I work the JT modes and FT8 most of times.

John, N9WVM

On Sunday, December 31, 2017, 2:27:09 PM EST, Anthony Bombardiere <DXDX@...> wrote:


John:

The problem with the HRD logbook closing on it's own is a known issue. I contacted HRD support and they replied with the fix mentioned in the previous email.

It sounds like you've experienced something else that I've not seen yet, but thanks for the tip.

73, Tony -K2MO



On 12/31/2017 7:00 AM, John Netro via Groups.Io wrote:
I had a problem Yesterday, I have Windows 10 computer, while trying to use CW SSB in DM780 could not have the rig control running, wasn't able to click macros, call signs, wasn't decoding. close off the Rig control and dm780 CW SSB mode worked fine, I ended up late in the day and restarted the computer and windows 10 had an update, after that I started HRD up and every thing worked fine with CW SSB Mode.

Just a thought if having a problem might want to restart your computer.

John, N9WVM   

On Saturday, December 30, 2017, 5:10:45 PM EST, Anthony Bombardiere <DXDX@...> wrote:


All:

If you're using Ham Radio Deluxe, you might be experiencing a Logbook
crash. I'm testing the fix on a Windows-10 64 bit machine and so far so
good.

To apply the fix, access your HRD folder and right click the logbook.exe
file. Click on the compatibility tab and disable "Fullscreen
Optimizations" located at the bottom of the compatibility window.

73 and HNY.

Tony -K2MO





Re: HRD Logbook Crash Fix

Tony
 

John:

The problem with the HRD logbook closing on it's own is a known issue. I contacted HRD support and they replied with the fix mentioned in the previous email.

It sounds like you've experienced something else that I've not seen yet, but thanks for the tip.

73, Tony -K2MO



On 12/31/2017 7:00 AM, John Netro via Groups.Io wrote:
I had a problem Yesterday, I have Windows 10 computer, while trying to use CW SSB in DM780 could not have the rig control running, wasn't able to click macros, call signs, wasn't decoding. close off the Rig control and dm780 CW SSB mode worked fine, I ended up late in the day and restarted the computer and windows 10 had an update, after that I started HRD up and every thing worked fine with CW SSB Mode.

Just a thought if having a problem might want to restart your computer.

John, N9WVM   

On Saturday, December 30, 2017, 5:10:45 PM EST, Anthony Bombardiere <DXDX@...> wrote:


All:

If you're using Ham Radio Deluxe, you might be experiencing a Logbook
crash. I'm testing the fix on a Windows-10 64 bit machine and so far so
good.

To apply the fix, access your HRD folder and right click the logbook.exe
file. Click on the compatibility tab and disable "Fullscreen
Optimizations" located at the bottom of the compatibility window.

73 and HNY.

Tony -K2MO





Re: HRD Logbook Crash Fix

John Netro
 

I had a problem Yesterday, I have Windows 10 computer, while trying to use CW SSB in DM780 could not have the rig control running, wasn't able to click macros, call signs, wasn't decoding. close off the Rig control and dm780 CW SSB mode worked fine, I ended up late in the day and restarted the computer and windows 10 had an update, after that I started HRD up and every thing worked fine with CW SSB Mode.

Just a thought if having a problem might want to restart your computer.

John, N9WVM   

On Saturday, December 30, 2017, 5:10:45 PM EST, Anthony Bombardiere <DXDX@...> wrote:


All:

If you're using Ham Radio Deluxe, you might be experiencing a Logbook
crash. I'm testing the fix on a Windows-10 64 bit machine and so far so
good.

To apply the fix, access your HRD folder and right click the logbook.exe
file. Click on the compatibility tab and disable "Fullscreen
Optimizations" located at the bottom of the compatibility window.

73 and HNY.

Tony -K2MO




HRD Logbook Crash Fix

Tony
 

All:

If you're using Ham Radio Deluxe, you might be experiencing a Logbook crash. I'm testing the fix on a Windows-10 64 bit machine and so far so good.

To apply the fix, access your HRD folder and right click the logbook.exe file. Click on the compatibility tab and disable "Fullscreen Optimizations" located at the bottom of the compatibility window.

73 and HNY.

Tony -K2MO

Re: Time to end the digital charade on 60M ? #JT65

Graham
 

Tnx  Ev,

Will have a look at that , could  try that ,  set  up  fldigi in beacon mode  , not  used psk on 5  for a  long time . 

though I must admit,  psk  might  not give  a true indication  of  local , short distance communications,  most  data  modes fall  over  , I remember trying , when the  band was first  released [uk] rtty  with the  pk232 , only to watch a  s9 signal . just print nonsense,  using the [ new then]  software  RTTY  decoder  from  Japan  MMTTY , improved  copy , but it  was only with the  introduction  of  mt63 and later olivia , that  reliable contacts could be  made , perhaps the  mfsk systems , of their   time,  did  perform better . 

To track  band  conditions , opera  provides a  unique solution . being  good s/n and  single pass , it  provides a  'what you see  is what  you get' , its also  immune to doppler and survives 'disturbed propagation' , I often see  spots  from  Russia , Moscow area 2000 miles, with  20  watts /40 ft vert  in the  night , which is  another  aspect , the  vertical performers very  well  for  Dx , something  worth noting  , as most  use lon low  systems  ..    

This was a  qrp  test  with  ros-4  on 5  meg  ,  240 miles  , via  web-sdr  >   you  tube  >  5 meg 1 watt
some  data  loss , but 100% print at  -16 dB  average , note also  being  spotted  at 400 miles  by SWL

73-Graham
G0NBD

Re: K3SIW , transmitting Opera Op32 on lowFER Band #opera

Graham
 


New spots  from AC4IU last night
Just  about  reached the  east  coast, 627 Miles ,  thats 1009  Kmt 
how far is this  going ? 

73-G.

K3SIW AC4IU 2200m OPERA 627 miles 11:58:52

2017-12-30 11:58:52 K3SIW AA AC4IU 0 136 -38 Op32__~38dB
2017-12-30 06:58:52 K3SIW AA AC4IU 0 136 -37 Op32_||_~37dB
2017-12-30 05:58:53 K3SIW AA AC4IU 0 136 -38 Op32__~38dB
2017-12-30 04:58:54 K3SIW AA AC4IU 0 136 -43 Op32__~43dB..........Deep-S 
2017-12-30 03:58:53 K3SIW AA AC4IU 0 136 -37 Op32_||_~37dB
2017-12-30 02:58:53 K3SIW AA AC4IU 0 136 -36 Op32_||||_~36dB....

Re: Time to end the digital charade on 60M ? #JT65

Ev Tupis
 

Graham,
If you're interested in a group of folks that use PSK31 as a propagation indicator...and may even be interested in giving 60 meters a try...visit http://www.PropNET.org

If you formatted your TX's like a PropNET ID, you may find people in the USA willing to be RXing around the clock to document when the band is open across the Atlantic.

'just making the offer.

Cheers,
Ev, W2EV



On Friday, December 29, 2017, 4:13:02 PM EST, Graham <g0nbd@...> wrote:


Andy,

An interesting  exchange   between  k6qi  and the  fcc  a while back over the  emissions allowable  on the  , then new, 5 meg  band,  ending  in simplicity , with  the  FCC pointing out that the  band  was under the  direct  control  of NITA and as such, it  was nothing  to  do  with  them 'squire' 

This post  from wa1wa would indicate, this  still  to  be the  case , as long  as it fits in b/w ,  anything go's ,  [this  reflects  rest of world regulations on this  subject] .

http://www.wa1wa.net/filespdf/NTIAClarifiesPositionon60MeterDigitalPrivileges.pdf

The wording of the fcc  document linked, may  reflect this  , as its appears to  be  comparative  as opposed to directive ,  'pactor 111 technique , I assume to  loosely infers  mfsk type ,  similarly for  psk31 psk carrier ?

 Commission restricts emission designator 2K80J2D to data using PACTOR-III technique and emission designator 60H0J2B to data using PSK31 technique.

I don't know, what propagation  is  like at the  moment,  but Ive certainly managed  a psk31 beacon  decode to the  usa , Opera  to  yourself ? and  VK with the  help  of vk3kck as rx   [ no tx permit in vk]  , 

can set  up if  anyone  wants  to try to uk ?

73-Graham
G0NBD

Re: K3SIW , transmitting Opera Op32 on lowFER Band #opera

Graham
 

K3SIW , Sending Opera op32 on the lowFER band ,

 QRG  =  [Dial set usb] 183.680 KHz Upper Side band,

Looking for RX stations ! , to join in , download Opera , set to 136 KHz , [ de select cat control !] set RX to ['Dial USB'] 183.680 KHz Upper Side band,

KU4XR at 794 Kmt  range  is  providing  reliable spots  at 35/36 dB , which are  + 10 dB  over the  lower  limit,  exactly how far k3siw is  reaching  has yet to be  measured ,  but for  1  watt dc input and restricted Ae , that's  quite a  signal  0.1 watt would work ..

Looking  for  RX monitors  at  range  ?

Tnx-G,

2017-12-29 18:58:59 K3SIW AA KB9PWQ EN52WA 0 136 -22 Op32_|||||||||||||||||||||||_~22dB
2017-12-28 03:58:58 K3SIW EN52TA KU4XR EM75XR 794 136 -43 Op32__~43dB
2017-12-28 02:58:52 K3SIW EN52TA SWL/K9 EN61AB 112 136 -15 Op32_||||||||||||||||||||||||||_~15dB
2017-12-28 00:58:54 K3SIW EN52TA K3SIW EN52TA 0 136 -10 Op32_||||||||||||||||||||||||||||||||||||_~10dB<<<<LOCAL COPY 
2017-12-28 00:58:53 K3SIW EN52TA NK9M EN51UQ 38 136 5 Op32_||||||||||||||||||||||||||||||||||||||||_5dB

KU4XR ,reliable decodes , at + 10 dB over the lower limit . 794 Kmt range

2017-12-28 09:58:57 K3SIW EN52TA KU4XR EM75XR 794 136 -36 Op32_||||_~36dB
2017-12-28 08:58:57 K3SIW EN52TA KU4XR EM75XR 794 136 -34 Op32_||||||||_~34dB
2017-12-28 07:58:57 K3SIW EN52TA KU4XR EM75XR 794 136 -35 Op32_||||||_~35dB
2017-12-28 06:58:57 K3SIW EN52TA KU4XR EM75XR 794 136 -35 Op32_||||||_~35dB
2017-12-28 05:58:57 K3SIW EN52TA KU4XR EM75XR 794 136 -37 Op32_||_~37dB
2017-12-28 04:58:57 K3SIW EN52TA KU4XR EM75XR 794 136 -36 Op32_||||_~36dB
2017-12-28 03:58:58 K3SIW EN52TA KU4XR EM75XR 794 136 -43 Op32__~43dB

Download from :
https://rosmodem.wordpress.com/2011/01/10/ros-2/

Re: Time to end the digital charade on 60M ? #JT65

Graham
 

Andy,

An interesting  exchange   between  k6qi  and the  fcc  a while back over the  emissions allowable  on the  , then new, 5 meg  band,  ending  in simplicity , with  the  FCC pointing out that the  band  was under the  direct  control  of NITA and as such, it  was nothing  to  do  with  them 'squire' 

This post  from wa1wa would indicate, this  still  to  be the  case , as long  as it fits in b/w ,  anything go's ,  [this  reflects  rest of world regulations on this  subject] .

http://www.wa1wa.net/filespdf/NTIAClarifiesPositionon60MeterDigitalPrivileges.pdf

The wording of the fcc  document linked, may  reflect this  , as its appears to  be  comparative  as opposed to directive ,  'pactor 111 technique , I assume to  loosely infers  mfsk type ,  similarly for  psk31 psk carrier ?

 Commission restricts emission designator 2K80J2D to data using PACTOR-III technique and emission designator 60H0J2B to data using PSK31 technique.

I don't know, what propagation  is  like at the  moment,  but Ive certainly managed  a psk31 beacon  decode to the  usa , Opera  to  yourself ? and  VK with the  help  of vk3kck as rx   [ no tx permit in vk]  , 

can set  up if  anyone  wants  to try to uk ?

73-Graham
G0NBD

Re: Time to end the digital charade on 60M ? #JT65

 

Thanks for the welcome. ARRL needs to get more involved in the "gentlemen agreement" on the band plans. It will be interesting to see how this plays out.

73,
KI4VMK


On Dec 21, 2017, at 6:33 PM, Andrew O'Brien <andrewobrie@...> wrote:
Welcome . The 60m situation is Indeed a mess. This group was at a major factor in gathering evidence to overcome the ARRL’s earlier claim that only PSK31 and PACTOR were allowed on 60m. It is time the nonsensical limits on practice are replaced with a more common sense approach that includes acknowledgment that current common practice of multi signals at same time are allowed on each channel. 

Andy K3UK



On Dec 21, 2017, at 5:53 PM, Charles Odom < ki4vmk@...> wrote:

I'm new to the group and was looking through these hashtags. I like the 60 meter band and would like to see it expanded and more oversight by the ARRL.
73,
KI4VMK 

Re: Time to end the digital charade on 60M ? #JT65

Andrew O'Brien
 

Welcome . The 60m situation is Indeed a mess. This group was at a major factor in gathering evidence to overcome the ARRL’s earlier claim that only PSK31 and PACTOR were allowed on 60m. It is time the nonsensical limits on practice are replaced with a more common sense approach that includes acknowledgment that current common practice of multi signals at same time are allowed on each channel. 

Andy K3UK



On Dec 21, 2017, at 5:53 PM, Charles Odom <ki4vmk@...> wrote:

I'm new to the group and was looking through these hashtags. I like the 60 meter band and would like to see it expanded and more oversight by the ARRL.
73,
KI4VMK 

Re: Time to end the digital charade on 60M ? #JT65

 

I'm new to the group and was looking through these hashtags. I like the 60 meter band and would like to see it expanded and more oversight by the ARRL.
73,
KI4VMK