Optimal setting is AGC ON, fast, and use a filter matching the bandwidth of the
signal.

Rein PA0R

> -----Ursprüngliche Nachricht-----
> Von: digitalradio@yahoogroups.com
> Gesendet: 27.07.07 21:22:04
> An: digitalradio@yahoogroups.com
> Betreff: [digitalradio] AGC and Digital Modes


>
>
>
>
> I would like to query the digital mode users regarding the AGC setting.
> I'm currently running PowerSDR 1.9.1 beta (original SVN), DXLabs
> Commander interfaced via VComm to a test version of Multipsk. I
> currently have the AGC set to MED, and I notice that when a strong PSK
> signal appears in the bandwidth, the AGC really cuts the signals back. I
> know it's supposed to do that, but I'm curious as to what is an optimal
> setting for digi modes. Thanks for any help and suggestions.
>
> 73... Jon W1MNK
>
>
>

--
http://pa0r.blogspirit.com

in the vhf listing 156.525Mhz is out side the ham bands, do you mean
146.525Mhz?

Dr. Dana-Renee Lee PhD

Hi,

GMDSS DSC is receive only in Multipsk and the frequency mentioned was
correct...corresponds to channel "70" on the marine VHF allocations.

Am sure someone will correct me if this is not correct....

73,

Bill  N9DSJ
--- In digitalradio@yahoogroups.com, "Dr. Lee" <drlee6530@...> wrote:
>
> in the vhf listing 156.525Mhz is out side the ham bands, do you mean
> 146.525Mhz?
>
> Dr. Dana-Renee Lee PhD
>

BETTER CHECK THIS ....

--- Tony Heatwole <tony@...> wrote:

> TARA's "Grid Dip PSK-RTTY" contest is Saturday,
> August 5, 2006,
>
> from 00:00 UTC to 23:59 UTC. See:
>
>
>
> http://www.n2ty.org/seasons/tara_grid_rules.html
>
>
>
> for the full contest information. I hope that you
> can join us!
>
>
>
> 73, de Tony Heatwole, N3FX
>
>
>
>




________________________________________________________________________________\
____
Building a website is a piece of cake. Yahoo! Small Business gives you all the
tools to get online.
http://smallbusiness.yahoo.com/webhosting

----- Original Message -----

From: Bill McLaughlin

To: digitalradio@yahoogroups.com

Sent: Thursday, August 02, 2007 2:44 AM

Subject: [digitalradio] Re: [hflink] New release (4.4) of Multipsk

Hi,

GMDSS DSC is receive only in Multipsk and the frequency mentioned was
correct...corresponds to channel "70" on the marine VHF allocations.

Am sure someone will correct me if this is not correct....

73,

Bill N9DSJ
--- In digitalradio@yahoogroups.com, "Dr. Lee" <drlee6530@...> wrote:
>
> in the vhf listing 156.525Mhz is out side the ham bands, do you mean
> 146.525Mhz?
>
> Dr. Dana-Renee Lee PhD
>

----- Original Message -----

From: Patrick Lindecker

To: digitalradio@yahoogroups.com

Sent: Thursday, August 02, 2007 3:00 PM

Subject: Re: [digitalradio] Re: [hflink] New release (4.4) of Multipsk

Hello Bill,

 

The GMDSS frequencies are the following:

 

GMDSS DSC in MF/HF (navy) (USB)
2182.0; 2187.5, 8414.5, 4207.5 kHz, 6312 kHz, 12577.0, 16804.5 Khz with a central AF frequency of 1700 Hz +/-85 Hz (1615 - 1785 Hz)

 

GMDSS DSC in VHF (navy) (FM)

 

156.525 MHz (channel 70).

 

The channel 70, as far as I know, is common to Europ and America.

 

73

Patrick

 

 

----- Original Message -----

From: Bill McLaughlin

To: digitalradio@yahoogroups.com

Sent: Thursday, August 02, 2007 2:44 AM

Subject: [digitalradio] Re: [hflink] New release (4.4) of Multipsk

Hi,

GMDSS DSC is receive only in Multipsk and the frequency mentioned was
correct...corresponds to channel "70" on the marine VHF allocations.

Am sure someone will correct me if this is not correct....

73,

Bill N9DSJ
--- In digitalradio@yahoogroups.com, "Dr. Lee" <drlee6530@...> wrote:
>
> in the vhf listing 156.525Mhz is out side the ham bands, do you mean
> 146.525Mhz?
>
> Dr. Dana-Renee Lee PhD
>

how can you get the hf standard messages to be set when first switching
to jt65a? it always comes up in eme style.

david/wd4kpd

Hi Andy,

Any news about this "new digital protocol" ?

73 de LA5VNA Steinar




Andrew O'Brien wrote:
> OK, now that you have bought the new Harry Potter book, what more is
> there to look forward to with excitement. A new digital protocol is
> due to be tested in the next few weeks that will be of interest to
> many. Watch this space .
>
> Andy K3UK
>
>

2:00 PM Presentation in the SLAC Panofsky Auditorium
"ALE For International Amateur Radio Emergency / Disaster Relief
Communications" by Bonnie Crystal, KQ6XA

AM-TECH DAY - Saturday 04 August 2007 - CALIFORNIA
AM-TECH-DAY Location: SLAC
Stanford Linear Accelerator Center
Menlo Park (Near Palo Alto) CA, USA
Talk in: N6NFI Repeater: 145.230- PL=100

Presentation Description-
"ALE Automatic Link Establishment on HF and VHF, is a versatile and
exciting new method of connecting radio operators on the air for voice
SSB, text messaging, and HF email. A "force multiplier" for hams in
emergency scenarios, ALE is the international standard for initiating
and sustaining HF interoperative communications. With ALE, operators
can maintain "24/7/365 hot standby nets", on demand... call up one or
multiple stations as needed... without nets or skeds, on the best HF
band for that moment."
Info about ALE: http://hflink.com
About the author:
http://www.fars.k6ya.org/people/bios#kq6xa

About Am-Tech Day-
Amateur Radio Technology Day is an open monthly event for ham radio,
technology, portable operation, a great meeting place for hams in
California.

Everyone is welcome, attendance is free. Picnic tables for radio set
ups... trees and lawns for antennas... forums and presentations in the
auditorium.

Food: Grilled hot dogs, donuts, drinks, snacks, etc.

WEBSITE for Am-tech Day:
http://www.fars.k6ya.org/amtechday/

There are usually several portable HF stations set up at
Amateur Radio Technology Day. It is the perfect chance to meet other
operators in person, see new equipment, exchange new ideas, tell
stories, and operate radios. The presentations on all kinds of ham
radio subjects in the academic-style auditorium are always
interesting. We set up radios on the picnic tables and put up antennas
in the trees or temporary poles in the grassy area. We can put our
radios on the tables just inside the building's patio doors and run
feedlines (100ft to 200ft coax) out to the normal antenna areas.

MAP:
http://www.fars.k6ya.org/amtechday/images/slacmap.png

GOOGLE EARTH: http://www.hfpack.com/qth/AMTECHDAY.kmz

N 37.419830
W 122.204568

==END OF MESSAGE==
73 Bonnie KQ6XA

Folks,

Due to some significant enhancements in PC-ALE, new features in
Multipsk, and major experiments with ALE email and SMS forwarding, you
will note a significant increase in  ALE on the amateur bands.  Here
is my log from the past few hours.


[00:10:44][FRQ 10136500][SND][               ][TIS][KF4
][AL0] BER 26 SN 06
[00:10:20][FRQ 10136500][SND][               ][TWS][VE2FXL
][AL0] BER 24 SN 05
[00:09:29][FRQ 07099500][SND][               ][TIS][KF4IN
][AL0] BER 25 SN 07
[00:00:49][FRQ 14109500][SND][               ][TWS][W1CDO
][AL0] BER 30 SN 08
[23:57:08][FRQ 10145500][SND][               ][TIS][KK7IF
][AL0] BER 26 SN 06
[23:56:50][FRQ 14100500][SND][               ][TWS][W1CDO
][AL0] BER 28 SN 06
[23:34:12][FRQ 10145500][SND][               ][TWS][WD8ARZ
][AL0] BER 26 SN 06
[23:28:55][FRQ 07102000][TO ][VE2FXL         ][TIS][N1CPE
][AL0] BER 28 SN 08
[23:19:49][FRQ 10140500][SND][               ][TIS][KF4IN
][AL0] BER 28 SN 09
[23:19:29][FRQ 10140500][SND][               ][TIS][KF4IN
][AL0] BER 26 SN 08
[23:15:43][FRQ 07065000][SND][               ][TIS][KF4
][AL0] BER 24 SN 06
[23:14:27][FRQ 10145500][SND][               ][TWS][VE2FXL
][AL0] BER 27 SN 04
[23:14:20][FRQ 10145500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 05
[23:13:27][FRQ 07102000][SND][               ][TIS][KB2M
][AL0] BER 26 SN 06
[23:12:20][FRQ 10140500][SND][               ][TWS][VE2FXL
][AL0] BER 28 SN 06
[23:10:49][FRQ 10136500][SND][               ][TIS][KF4IN
][AL0] BER 28 SN 08
[23:07:22][FRQ 07110500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 10
[23:06:39][FRQ 10145500][SND][               ][TIS][KF4IN
][AL0] BER 27 SN 04
[23:06:25][FRQ 07102000][SND][               ][TWS][VE2FXL
    ][AL0] BER 30 SN 10
[23:05:48][FRQ 07110500][SND][               ][TIS][KF4IN
][AL0] BER 26 SN 08
[23:05:23][FRQ 07099500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 10
[23:05:16][FRQ 07099500][SND][               ][TWS][VE2FXL
][AL0] BER 28 SN 10
[22:57:47][FRQ 14109500][SND][               ][TWS][W1CDO
][AL0] BER 28 SN 06
[22:41:33][FRQ 14109500][TO ][WD8ARZ         ][TIS][W1CDO
][AL0] BER 30 SN 08
[22:30:09][FRQ 14109500][SND][               ][TWS][W1CDO
][AL0] BER 30 SN 10
[22:25:57][FRQ 07102000][SND][               ][TWS][WD8ARZ
][AL0] BER 30 SN 11
[22:22:24][FRQ 14112000][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 07
[22:22:17][FRQ 14112000][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 06
[22:21:24][FRQ 14109500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 06
[22:21:17][FRQ 14109500][SND][               ][TWS][VE2FXL
][AL0] BER 27 SN 05
[22:20:47][FRQ 10140500][SND][               ][TIS][KF4
][AL0] BER 21 SN 05
[22:20:37][FRQ 10140500][SND][               ][TIS][KF4
][AL0] BER 29 SN 09
[22:20:25][FRQ 10140500][SND][               ][TIS][KF4
][AL0] BER 19 SN 07
[22:19:19][FRQ 14109500][SND][               ][TWS][K7EK
][AL0] BER 30 SN 06
[22:16:26][FRQ 14100500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 06
[22:16:19][FRQ 14100500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 08
[22:14:27][FRQ 10145500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 08
[22:13:27][FRQ 07102000][SND][               ][TIS][KB2M
][AL0] BER 30 SN 08
[22:13:19][FRQ 10140500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 06
[22:12:25][FRQ 10136500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 08
[22:10:44][FRQ 10136500][SND][               ][TIS][KF4IN
][AL0] BER 30 SN 12
[22:10:23][FRQ 14109500][SND][               ][TWS][W1CDO
][AL0] BER 30 SN 09
[22:08:23][FRQ 07110500][SND][               ][TWS][VE2FXL
][AL0] BER 25 SN 08
[22:07:05][FRQ 10145500][SND][               ][TIS][N0ET
][AL0] BER 30 SN 06
[22:06:27][FRQ 07099500][SND][               ][TWS][VE2FXL
][AL0] BER 28 SN 07
[22:06:19][FRQ 07099500][SND][               ][TWS][VE2FXL
][AL0] BER 30 SN 07
[22:04:14][FRQ 14109500][SND][               ][TWS][EA2AFR
][AL0] BER 25 SN 06
[22:04:07][FRQ 14109500][SND][               ][TWS][EA2AFR
][AL0] BER 30 SN 07
[22:03:56][FRQ 14109500][SND][               ][TWS][EA2AFR
][AL0] BER 25 SN 06
[22:02:39][FRQ 14100500][TO ][KQ6XA          ][TIS][W1CDO
][AL0] BER 30 SN 09
[21:51:37][FRQ 07099500][SND][               ][TWS][WD8ARZ
][AL0] BER 27 SN 06
[21:36:16][FRQ 14112000][SND][               ][TWS][W1CDO
][AL0] BER  0 SN 00
[21:36:16][FRQ 14109500][SND][               ][TWS][W1CDO
][AL0] BER 30 SN 06
[21:34:40][FRQ 14109500][SND][               ][TWS][WD8ARZ
][AL0] BER 30 SN 08
[21:34:33][FRQ 14109500][SND][               ][TWS][WD8ARZ
][AL0] BER 23 SN 06
[21:30:51][FRQ 10145500][SND][               ][TWS][WD8
][AL0] BER 25 SN 14
[21:30:34][FRQ 10145500][SND][               ][TWS][WD8ARZ
][AL0] BER 24 SN 12
[21:26:41][FRQ 07102000][SND][               ][TWS][WD8ARZ
][AL0] BER 20 SN 06
[21:26:36][FRQ 07102000][SND][               ][TWS][WD8ARZ
][AL0] BER 24 SN 07
[21:21:44][FRQ 10140500][SND][               ][TIS][KF4
][AL0] BER 30 SN 04
[21:21:33][FRQ 10140500][SND][               ][TIS][KF4IN
][AL0] BER 27 SN 05
[21:11:24][FRQ 10145500][SND][               ][TIS][KF4
][AL0] BER 14 SN 03
[21:10:49][FRQ 10136500][SND][               ][TIS][KF4IN
][AL0] BER 29 SN 07
[21:10:30][FRQ 10136500][SND][               ][TIS][KF4
][AL0] BER 29 SN 07
[21:09:27][FRQ 10145500][SND][               ][TIS][KB2M
][AL0] BER 30 SN 08
[21:08:27][FRQ 07102000][SND][               ][TIS][KB2M
][AL0] BER 30 SN 08
[20:32:55][FRQ 10145500][SND][               ][TWS][WA3MEZ
][AL0] BER 30 SN 06
[20:31:52][FRQ 07102000][SND][               ][TWS][WA3MEZ
][AL0] BER 22 SN 05
[20:31:39][FRQ 10145500][SND][               ][TWS][WD8ARZ
][AL0] BER 30 SN 06
[20:31:28][FRQ 10145500][SND][               ][TWS][WD8ARZ
][AL0] BER 22 SN 05
[20:26:38][FRQ 07102000][SND][               ][TWS][WD8ARZ
][AL0] BER 20 SN 03
[20:26:31][FRQ 07102000][SND][               ][TWS][WD8ARZ
][AL0] BER 22 SN 05
[20:26:24][FRQ 07102000][SND][               ][TWS][WD8ARZ
][AL0] BER 26 SN 05
[20:18:27][FRQ 14109500][SND][               ][TIS][KB2M
][AL0] BER 30 SN 07

Hi Andrew, yes it was busy today!! I didn't copy you, but I captured

[Call] [from W1CDO] [to K3UK] (his BER=30 + SINAD= 5)

And this block is VERY interesting:

[FAE] [from EA2AFR] (his BER=23 + SINAD= 2)
[Sounding THIS WAS] [from EA2AFR] (his BER=29 + SINAD= 2)
AFR[Sounding THIS WAS] [from EA2AFR] (his BER=26 + SINAD= 2)
AFR[Sounding THIS WAS] [from EA2] (his BER=27 + SINAD= 2)
AFR[Sounding THIS WAS] [from EA2AFR] (his BER=21 + SINAD= 2)

You are using Multipsk, correct? If so, how did you turn on the time
stamp? Thanks.

73... Jon W1MNK

RAC Draft HF Band Plan (July 8, 2007)

The RAC HF Band Planning Committee has prepared a draft document
covering the bands 160m to 10m.
This plan has been fashioned using the IARU Regional plans as a model
wherever possible. The previous
RAC HF Band Plan had not been revised for some time. The recent
changes in band allocations by the
United States Federal Communications Commission and changes in IARU
Region 1 allocations have
necessitated changes in the Canadian plan. This draft document is
being made available to the Amateur
Radio operators of Canada and also to the members of the IARU Region 2
HF Band Planning Committee.
No plan can remain static as International regulations and technology
advances. At this time the IARU
Region 2 HF BP Committee is also revising their plan. Since Canada is
in region 2, our plan must be
congruent with the overall plan for North and South America. This
Canadian plan uses some of the
information from an early Region 2 draft but will have to be updated
when the final version of the Region 2
plan is released. It is also hoped that some of the ideas generated by
the Canadian committee might be
useful to the Region 2 committee. On 80 metres, the use of phone below
3.600 MHz, as it is being
contemplated in Region 2, is included provisionally in the Canadian
plan despite strong reservations by the
Committee that it conflicts with expected growth in usage of digital
modes. The Committee has submitted a
position paper asking for possible Region 2 reconsideration of this
move. It is anticipated that major
revisions to the 40m plan may be necessary when Short Wave
Broadcasting is eliminated worldwide from
the band 7.100 to 7.200 MHz.
There are some unique features of the Canadian plan that need special
attention. On 40 metres a phone DX
window has been specified, something that the committee researched and
has included as a first. On 80
metres, in consideration of the major expansion of phone frequencies,
special attention has been given to
the phone DX window, expanding it to 3.775 to 3.800 MHz from two hours
before dusk until two hours
after dawn, local time. As well as specifying Emergency frequencies
and DX windows, activity centres for
IOTA operations, QRP Operation, AM phone and others, the plan includes
very narrow band digital
frequency bands within existing digital assignments.
Your comments and suggestions are valuable in helping the HF Band
Planning Committee to make this
document a useful tool for Canadian operators. Please send them to the
following e-mail address:
rac.hfbpc.poll@...
Page 2
DRAFT 160m BAND PLAN
(Mar. 23, 2007)
1800 - 1810
CW, Narrow band digital (Notes 1)
1810 - 1840
CW (Notes 1 & 2)
1840 - 1999
CW, Phone (Notes 3 & 4)
1999 - 2000
Beacons
NOTES:
1 -
1800 - 1840
CW may be used anywhere in the band but is normally used only up to
1840MHz
2 -
1830 - 1835
DX Window
3 -
1905 - 1915
JA CW DX Listening Window
4 -
1850 - 1999
Includes AM and SSTV modes
In addition, the following "Centres of Activity" are recognized:
1810
QRP CW Centre of Activity
1900
QRP SSB Centre of Activity
GENERAL NOTES:
•
Where Notes are shown, these activities have priority over other activities.
•
During major weekend Contest activities, activity in certain modes can
spill over into other
segments.
•
Sideband Usage Below 10MHz use lower sideband (LSB)
•
Phone modes should not operate closer than 3000Hz to the lower band edge.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
Page 3
DRAFT 80m BAND PLAN
Rev. 7
(June 26, 2007)
3500 - 3525
CW (Note 1)
3525 - 3570
CW, Phone (Note 2)
3570 - 3580
CW, Phone, Narrow band digital (Note 2)
3580 - 3600
CW, Phone, Wide band, Narrow band digital (Notes 2, 3 & 4)
3600 - 3840
CW, Phone (Notes 5 & 6)
3840 - 3850
CW, Phone, SSTV, FAX
3850 - 4000
CW, Phone
NOTES:
1 -
3500 - 3510
DX CW window common to all IARU regions
2 -
3525 - 3600
Intercontinental Phone permitted on a non-interference basis only.
3 -
3580 - 3583
PSK-31 Very Narrow Band Digital
4 -
3590
RTTY DX
5 -
3760
Emergency Centre
6 -
3790 – 3800
Phone DX Window, expands to 3775-3800 from 2 hours before dusk until 2
hours after dawn local time
In addition, the following "Centres of Activity" are recognized:
3530
IOTA CW Centre of Activity
3555
QRS CW Centre of Activity
3560
QRP CW Centre of Activity in IARU Regions 1 and 2, 3530 MHz in Australia
3690
QRP SSB Centre of Activity
3735
Image Centre of Activity
3755
IOTA SSB of Activity
3885
AM Phone Centre of Activity
3985
QRP SSB Centre of Activity
GENERAL NOTES:
•
Where Notes are shown, these activities have priority over other activities.
•
During major weekend Contest activities, activity in certain modes can
spill over into other segments.
•
Sideband Usage Below 10MHz use lower sideband (LSB)
•
Phone modes should not operate closer than 3000Hz to the lower band edge.
•
Wide band digital refers to any digital mode using more than 500Hz bandwidth.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
•
Image modes: Any analogue or digital image using bandwidth up to 2700Hz.
Page 4
DRAFT 40m BAND PLAN
Rev. 4
(Mar. 19, 2007)
7000 - 7035
CW (Note 1)
7035 - 7040
CW, Narrow Band Digital with other Regions (Note 2)
7040 - 7050
CW, Phone, Narrow Band Digital with other Regions
7050 - 7080
CW, Phone (Notes 3 and 4)
7080 - 7125
CW, Phone, Narrow Band digital (Note 4)
7125 - 7165
CW, Phone
7165 - 7175
CW, Phone, SSTV, FAX
7175 - 7300
CW, Phone (Notes 5 and 6)
Notes
1 -
7000 - 7025
DX CW Window common to all IARU regions
2 -
7035 - 7038
PSK-31 Very Narrow Band Digital
3 -
7060
SSB Emergency Centre 1
4-
7065 – 7090
SSB DX Window
5 -
7240
SSB Emergency Centre 2
6 -
7295
SSB Emergency Centre 3
In addition, the following "Centres of Activity" are recognized:
7030
QRP and IOTA CW Centre of Activity
7043
Image Centre of Activity 1
7055
IOTA SSB Centre of Activity 1
7090
SSB QRP Centre of Activity 1
7165
Image Centre of Activity 2
7255
IOTA SSB Centre of Activity 2
7285
SSB QRP Centre of Activity 2
7290
AM Centre of Activity
GENERAL NOTES:
a) Where Notes are shown, these activities have priority over other activities.
b) During major weekend Contest activities, activity in certain modes
can spill over into other
segments.
c) Sideband Usage Below 10MHz use lower sideband (LSB)
d) Phone modes should not operate closer than 3000Hz to the lower band edge.
e) Wide band digital refers to any digital mode using more than 500Hz bandwidth.
f) Narrow band digital modes: All modes using up to 500Hz bandwidth.
g) Image modes: Any analogue or digital image using bandwidth up to 2700Hz.
Page 5
DRAFT 30m BAND PLAN
(Mar. 23, 2007)
10100-10130
CW
10130-10140
CW, Narrow band digital
10140-10150
CW, Narrow band and Wide band digital
Note:
1 -
10142 - 10145
PSK-31 Very Narrow Band Digital
In addition, the following "Centres of Activity" are recognized:
10115
IOTA CW Centre of Activity
10116
CW QRP Centre of Activity
GENERAL NOTES:
•
Where Notes are shown, these activities have priority over other activities.
•
Wide band digital refers to any digital mode using more than 500Hz bandwidth.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
Page 6
DRAFT 20m BAND PLAN Rev 1 (Mar. 23, 2007)
14000 - 14070
CW
14070 - 14080
CW, Narrow band digital (Note 1)
14080 - 14090
CW, Narrow Band digital
14090 - 14099.5
CW, Narrow band and Wide band digital
14099.5 - 14100.5
Beacons
14100.5 - 14112
CW, Narrow band and Wide band digital
14112 - 14350
CW, Phone (Notes 2 & 3)
14225 - 14235
CW, Phone, SSTV, FAX
Notes:
1 -
14070 - 14073
PSK-31 Very Narrow Band Digital
2 -
14190 - 14200
SSB DXpedition priority
3 -
14300
Global Emergency Centre
In addition, the following "Centres of Activity" are recognized:
14040
IOTA CW
14055
CW QRS Centre of Activity
14060
CW QRP Centre of Activity
14140
Canadian Cross-country SSB Centre of Activity
14260
IOTA SSB
14285
SSB QRP Centre
14300
Global Emergency Centre
GENERAL NOTES:
•
Where Notes are shown, these activities have priority over other activities.
•
During major weekend Contest activities, activity in certain modes can
spill over into other
segments.
•
Phone modes should not operate closer than 3000Hz to the upper band edge.
•
Wide band digital refers to any digital mode using more than 500Hz bandwidth.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
•
Image modes: Any analogue or digital image using bandwidth up to 2700Hz.
Page 7
DRAFT 17m BAND PLAN
(Mar. 23, 2007)
18068-18095
CW
18095-18100
CW, Narrow band and Wide band diigtal
18100-18109.5
CW, Narrow band digital (Note 1)
18109.5-18110.5
Beacons
18110.5-18168
CW, Phone (Note 2)
Notes:
1- 18100-18103
PSK-31 Very Narrow Band Digital
2-
18160
Global Emergency Center
In addition, the following "Centres of Activity" are recognized:
18086
CW QRP center
18098
IOTA CW
18128
IOTA SSB
18130
SSB QRP Center
GENERAL NOTES:
•
Phone modes should not operate closer than 3000Hz to the upper band edge.
•
Wide band digital refers to any digital mode using more than 500Hz bandwidth.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
Page 8
DRAFT 15m BAND PLAN
(July 8, 2007)
21000-21070
CW
21070-21080
CW, Narrow band and Wide band digital (Note 1)
21080-21095
CW, Narrow band digital
21095-21149.5
CW, Narrow band and Wide band digital
21149.5-21150.5
Beacons
21150.5-21450
CW, Phone, SSTV, FAX (Note 2)
Notes:
1 - 21070 – 21073
PSK-31 Very Narrow Band Digital
2 -
21360
Global Emergency Center
In addition, the following "Centres of Activity" are recognized:
21040
IOTA CW Center of Activity
21055
CW QRS Center of Activity
21060
CW QRP Center of Activity
21260
IOTA SSB Center of Activity
21285
SSB QRP Center of Activity
21340
Image Center of Activity center
21385
SSB QRP Center of Activity
GENERAL NOTES:
•
Where Notes are shown, these activities have priority over other activities.
•
During major weekend Contest activities, activity in certain modes can
spill over into other
segments.
•
Phone modes should not operate closer than 3000Hz to the upper band edge.
•
Wide band digital refers to any digital mode using more than 500Hz bandwidth.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
•
Image modes: Any analogue or digital image using bandwidth up to 2700Hz.
Page 9
DRAFT 12m BAND PLAN
(Mar. 23, 2007)
24890-24920
CW
24915-24920
CW, Narrow band and Wide band digital
24920-24925
CW, Narrow band digital (Note 1)
24925-24929.5
CW, Narrow band and Wide band digital
24929.5-24930.5
Beacons
24930.5-24990
CW, Phone
Note:
1 -
24920-24923
PSK-31 Very Narrow Band Digital
In addition, the following "Centres of Activity" are recognized:
24906
CW QRP center
24920
IOTA CW
24950
IOTA SSB
24950
SSB QRP center
GENERAL NOTES:
•
Where Notes are shown, these activities have priority over other activities.
•
Phone modes should not operate closer than 3000Hz to the upper band edge.
•
Wide band digital refers to any digital mode using more than 500Hz bandwidth.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
Page 10
DRAFT 10m BAND PLAN
(Mar 23, 2007)
28000-28070
CW
28070-28080
CW, Narrow band and Wide band digital
28080-28120
CW, Narrow band digital
28120-28189.5
CW, Narrow band and Wide band digital (Note 1)
28199.5-28200.5
Beacons
28200.5-29300
CW, Phone (Notes 2, 3 & 4)
28300-28320
CW, Narrow band and Wide band digital
29300-29510
Satellites
29520-29590
FM repeater inputs
29600
FM simplex
29620-29690
FM repeater outputs
Notes:
1 -
28120-28123
PSK-31 Very Narrow Band Digital
2 -
28670-28690
SSTV, FAX
3 -
29000-29200
AM
4 -
29200-29300
Narrow band and Wide band digital
In addition, the following "Centres of Activity" are recognized:
28040
IOTA CW Centre of Activity
28055
CW QRS Centre of Activity
28060
CW QRP Centre of Activity
28385
QRP SSB Centre of Activity
28460
IOTA SSB Centre of Activity 1
28560
IOTA SSB Centre of Activity 2
28680
Image Centre of Activity
GENERAL NOTES:
•
Where Notes are shown, these activities have priority over other activities.
•
During major weekend Contest activities, activity in certain modes can
spill over into other
segments.
•
SSB and AM Phone modes should not operate closer than 3000Hz to an
upper band edge.
•
FM Bandwidth is not to exceed 6000Hz.
•
Wide band digital refers to any digital mode using more than 500Hz bandwidth.
•
Narrow band digital modes: All modes using up to 500Hz bandwidth.
•
Image modes: Any analogue or digital im

I think previous postings here indicated that AQC ALE is unlikely to
filter down to amateur transceivers.  Does anyone know what the AQC
Enable feature within PC-ALE does ?

Andy K3UK

GM Andy,

In PC-ALE the AQC-ALE operation differs from MARS-ALE for some time
now, however with both tools selecting AQC-ALE means that all
Soundings and Calls originated by your station will be in AQC-ALE
mode, which differs from NORMAL ALE and which can only be decoded by
an ALE modem that supports AQC-ALE.

The way in which G4GUO implemented AQC-ALE in PC-ALE regardless of
wether you are actually in AQC-ALE or not, it will decode and display
AQC-ALE channel acty and respond to either type of call made to your
station. However I have found this to be a problem with falsing on
bad ALE words and processing NORMAL ALE linking calls as AQC-ALE
which is just wrong and I changed MARS-ALE to only do so when
actually in AQC-ALE where the standard mandates backward support in
the event of an incoming NORMAL ALE call when in AQC-ALE mode.

I also changed MARS-ALE so that when in AQC-ALE scan rates of 2
ch/sec and above are supported as that is my interpretation of the
standard,  whereas in PC-ALE only 5 ch/sec is supported.

AQC-ALE is far superior to NORMAL ALE, its 2G+ and is much more
reliable and fast at establishing and maintaining an ALE linked state
under severe channel conditions. It is only to be found in the most
expensive Military ALE transceivers to date, its use is tactical
rather than 24/7 networks and it offer many additional operational features.

/s/ Steve, N2CKH

At 11:56 PM 8/3/2007, you wrote:
>I think previous postings here indicated that AQC ALE is unlikely to
>filter down to amateur transceivers.  Does anyone know what the AQC
>Enable feature within PC-ALE does ?
>
>Andy K3UK

This has been the same problem I have with my ICOM 756 Pro 2. It scans
reasonably well although it goes into split operation when you boot up
the program and does not return to normal operation without manual
intervention, but it can not transmit.

I was surprised that no one else is using this model transceiver for
ALE, or at least was willing to help solve the problem., assuming that
the rig can actually operate with PC-ALE. It does fine with Multipsk.
One wonders if there really are hundreds or thousands of ALE users as
has been claimed.

73,

Rick, KV9U



slamat ali wrote:
> Dear All
>
> I try to use pc ale with my ft 1000 mp mark V. I already can scan my
> frequency however
> i have hard time to ptt my radiousing Cat. Are there any one can help me.
>
> ------------------------------------------------------------------------
> Got a little couch potato?
> Check out fun summer activities for kids.
>
<http://us.rd.yahoo.com/evt=48248/*http://search.yahoo.com/search?fr=oni_on_mail\
&p=summer+activities+for+kids&cs=bz>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.476 / Virus Database: 269.11.4/935 - Release Date: 8/3/2007 5:46
PM
>

Hello Ali,

The current version of PC-ALE is really RTS/DTR PTT based, the reason
being that it has long proven  to be much more reliable whereas CAT
PTT has not, RF into the radio can lock a rig into TX using CAT PTT
and other issues come into play, if you notice most rigs do not
support CAT PTT on the data/digital/aux ports.

Anyhow, G4GUO started to add CAT PTT to PC-ALE as many users were
requesting it, to date through the current release version of PC-ALE
the following radios are supported:  FT100, FT817, FT847, FT897,
SKANTI 8250, Ten Tec TT516 and TT550.

However, I have now integrated the radio control library from
MARS-ALE into the latest ALPHA version of PC-ALE which has just been
released to the HFlink test group where all radios which support CAT
PTT allow for its use if that is what the user desires as their PTT method.

The updated PC-ALE supports the Quiet Scanning/Sounding (QS/S) method
of MARS-ALE were all make/model radios that either via SPLIT VFO
operation or a radio specific BYPASS command disable the RF PA
section spectral purity filter relays from activation during Scanning
automatically and upon the first TX event allow their operation again
and when Scanning is stopped, the radios go back to single channel mode.

Also now supported are the various dedicated data ports where other
than USB/LSB is used etc. such as with the FT817 family and ICOM PRO models.

Those interested in PC-ALE and testing the ALPHA build of the next
release should consider joining
http://tech.groups.yahoo.com/group/pcale/ as the more that sign up to
test the ALPHA, the better it will met everyone's needs when released.

Below is a list of all make/model radios that are supported at the
moment by their "Radio Type" menu selection moniker and other models
the selection supports, there are more to come like the MICOM H,
SEA235 and others for which I have yet to write drivers.

DX77T           < NOTE: Also use for DX-77, DX-77EQ, DX-701 and DX-707
FT450
FT450HS < NOTE: RTS/CTS handshaking support
FT600           < NOTE: Also Vertex System 600
FT650           < NOTE: Also FT655
FT757GX
FT767GX
FT817                   < NOTE: Supports FT817x, FT857x, FT897x
FT817DIG                < NOTE: DIG port support for all models in
this sub family
FT847
FT890                   < NOTE: Also FT-100, FT-747, FT-80C, FT-840, FT-890,
FT-900, SB-1400
FT920
FT920DATA               < NOTE: Supports data port, AFSK-FSK switch to AFSK
                          and setup the radio for the +2125hz offset
in the U-45 setup
FT990                   < NOTE: QS/S support where FT-990 requires
ROM version 1.2 or later.
FT980
FT1000MP
FT2000          < NOTE: Also for FT-2000D
FT2000HS                < NOTE: As FT2000 above but RTS/CTS handshaking support
FTDX9000
GENERIC ICOM    < Mostly obsolete now but still supported, CAT PTT
and QS/S support provided.
IC78
IC703
IC706
IC706MkII
IC706MkIIG
IC707
IC718
IC725                   < NOTE: Factory addressing is used, WRT
address diodes D57-D63, only D60 and
                          D62 should be in place for the factory
address of 28h. Diode D64 for transceive
                          operation should no be installed either.
9600 baud is being used, not the factory
                          default 1200 baud. As such, the CI-V Baud
Rate diode, D2 must be in place and
                          D3 must be empty. Also diode D4, the factory
default, must be in place for standard
                          5 byte frequency data.
IC726                   < NOTE: Factory addressing is used, WRT
address diodes D57-D63, only D61 and
                          D62 should be in place for the factory
address of 30h. Diode D64 for transceive
                          operation should no be installed either.
9600 baud is being used, not the factory
                          default 1200 baud. As such, the CI-V Baud
Rate diode, D2 must be in place and
                          D3 must be empty. Also diode D4, the factory
default, must be in place for standard
                          5 byte frequency data.
IC728                   < NOTE: Factory addressing is used, WRT
address diodes D57-D63, only D60, D61
                          and D62 should be in place for the factory
address of 38h. Diode D64 for transceive
                          operation should no be installed either.
9600 baud is being used, not the
factory                       default 1200 baud. As such, the CI-V
Baud Rate diode, D2 must be in place and
                          D3 must be empty. Also diode D4, the factory
default, must be in place for standard
                          5 byte frequency data.
IC729                   < NOTE: Factory addressing is used, WRT
address diodes D57-D63, only D58, D60,
                          D61 and D62 should be in place for the
factory address of 3Ah. Diode D64 for                    transceive
operation should no be installed either. 9600 baud is being used, not the
                          factory default 1200 baud. As such, the CI-V
Baud Rate diode, D2 must be in place
                          and D3 must be empty. Also diode D4, the
factory default, must be in place for
                          standard 5 byte frequency data.
IC735
IC736
IC737                   < NOTE: Also use for IC-737A
IC738
IC746
IC746PRO                < NOTE: Also use for IC-7400
IC751                   < NOTE: Also use for IC-750. These models
will not work correct under GENERIC                   ICOM due to the
order of settig Fo/Mode
IC756
IC756PRO                < NOTE: Also use for Signal One Milspec 1030E-DSP
IC756PROII
IC756PROIII
IC761
IC765
IC775DSP
IC781                   < NOTE: Also use for IC-780 and Signal One
Milspec 1030C
IC7000
IC7800
ICF7000         < NOTE: Radio address must be set to 9.
ICM700PRO               < NOTE: Radio address must be set to 2.
ICM710          < NOTE: Radio address must be set to 1.
ICM710RT                < NOTE: Radio address must be set to 3.
ICM801E                 < NOTE: Radio address must be set to 7.
ICM802          < NOTE: Radio address must be set to 8.
JST245          < NOTE: Also for JST-145
K2_100
K505DSP
KENWOOD         < NOTE: Supports 4800 baud 8N2 operation by default.
KENWOOD_HS      < NOTE: As KENWOOD above but adds RTS/CTS support.
RF350ALK                < NOTE: Supports Harris RF-350, RF-350K,
RT-1446 URC, AN/URC-119, AN/URC-121(V)
RF350ALK_TNC     < NOTE: As RF350ALK above but also supports aux port
interfacing for PCSDM or hardware TNC/Modem
RF350KWT                < NOTE: Supports Key West model
RF5022          < NOTE: Supports RF-5022, RF-5020, AN/TRC-510(V),
RT-5104(P)/U, RF-5200, RF-5800, AN/PRC-138
SDR1000         < NOTE: Supports PowerSDR console v1.3.x and later
and ZZ commands as of February 2007
SGC2000         < NOTE: Also supports PRC2250MIL
SKANTI-8250
TT516                   < NOTE: Due to low baud rate this model just
memory channel support
TT538                   < NOTE: Supports Jupiter and OMNI VII using
Jupiter command set.
TT550                   < NOTE: MIC port only
TT550MA         < NOTE: MIC port for Voice and rear AUX port ALE
TT565                   < NOTE: Supports ORION I and also
TT566/TT566AT ORION II
TT585                   < NOTE: Requires use of Null Modem cable.
TT586                   < NOTE: Ten Tec extended command supported for CAT PTT

Receivers:

AR5000;AR5000;AR7030;EK890;EK896;FRG100;FRG8800;HF1000;HF2050BRD;LCR2000;NRD345;\
NRD525;NRD535;NRD535D;NRD545;PCR1000;PCR1500;R8;R8A;R8B;R71;R72;R75;R7000;R7100;\
R8500;R9000;R9500;RA6790GM;RA6830JD;R3030STX1;R3030STX2;R3030STX3;RF590;RF590A;R\
X320;RX330;RX331;RX340;RX350;TCI8174;VR5000;WJ8711;

NOTE: For the Kenwood R5000, KENWOOD or KENWOOD_HS should be selected.



/s/ Steve, N2CKH

At 10:55 AM 8/4/2007, you wrote:
>Dear All
>
>I try to use pc ale with my ft 1000 mp mark V. I already can scan my
>frequency however
>i have hard time to ptt my radiousing Cat. Are there any one can help me.

Hi Rick,

I have replied to your comments many times on these matters:

1. PC-ALE as released does not specifically support the PRO2, the
next release will. For now if you are not interested in ALPHA testing
the next release, its the use of the GENERIC ICOM interface and
DTR/RTS for PTT. It works for everyone else that has a PRO2, I can't
see why you should have any problems unless you have something out of
the ordinary configured.

2. As hard as you may find it to believe, there is a lot of ALE
activity on the Amateur Bands.

Sincerely,

/s/ Steve, N2CKH



At 11:51 AM 8/4/2007, you wrote:
>This has been the same problem I have with my ICOM 756 Pro 2. It scans
>reasonably well although it goes into split operation when you boot up
>the program and does not return to normal operation without manual
>intervention, but it can not transmit.
>
>I was surprised that no one else is using this model transceiver for
>ALE, or at least was willing to help solve the problem., assuming that
>the rig can actually operate with PC-ALE. It does fine with Multipsk.
>One wonders if there really are hundreds or thousands of ALE users as
>has been claimed.
>
>73,
>
>Rick, KV9U

Hi Andy,

It is the same 8FSK modem, however it uses shorter bursts for calling
and sounding and there is a PSK burst mode as well which uses the
MIL-STD-188-110 modem for generation.

/s/ Steve, N2CKH

At 09:26 AM 8/4/2007, you wrote:
>Thanks Steve.  Is the AQC-ALE a different digital mode, different
>tone characteristics?
>
>
>Andy K3UK

Hello All


just curious of any one has found what the best receive setting for
digital modes using USB

Many interested in the optimum settings for vhf and uhf using WJST

The radio is an ICOM 746 PRO

Thanks VE7IRA

Thanks for your comments, Steve,

I understood that it did support the ICOM 756 Pro 2, including CAT
control, and was told by someone in the ALE world that I needed to check
the CAT box which I of course did. Maybe I missed it, but I did not
realize that this particular rig can not even operate at this time with
CAT control, because if I did, I would not have spent quite so many
hours trying to get it to key with PTT CAT:( I don't have any hardware
PTT plans at this time as other programs work reasonably well and it
simplifies the cabling requirements.

What I  understood was that the current program is defective with
setting up the split function properly. It sets it up the split when you
boot the program, not when you scan, and it does not return to non-split
mode either when you stop scanning or when you leave the program. My
understanding was that this will be fixed in the new version, although
it is still in Alpha at this time.

Your list of the many different rigs is very helpful and this kind of
information needs to be easily located on ALE websites so that there is
no misunderstanding of what a given "supported" rig can or can not do at
any given time. It doesn't make sense to me why this would not be
heavily promoted.

As far as activity, I suppose it depends upon your definition. I
monitored for several hours today with scanning with the ICOM 756 Pro 2
and heard the following:

KK7IF
VE2FXL
WD8ARZ
KM4BA
LU8EX
VE6OG

Of course there can be other areas of the world and those with better
antennas who may be able to copy more test signals and calls.Most of
these were soundings but some appeared to be calls. I don't know if you
actually can receive any messages being sent by others when in this
scanning mode, but I have not actually printed anything like that.

Again, it seems that it is difficult to find information of this kind on
the internet and I rather expect it to be very openly available and very
clear and concise.






Steve Hajducek wrote:
> Hi Rick,
>
> I have replied to your comments many times on these matters:
>
> 1. PC-ALE as released does not specifically support the PRO2, the
> next release will. For now if you are not interested in ALPHA testing
> the next release, its the use of the GENERIC ICOM interface and
> DTR/RTS for PTT. It works for everyone else that has a PRO2, I can't
> see why you should have any problems unless you have something out of
> the ordinary configured.
>
> 2. As hard as you may find it to believe, there is a lot of ALE
> activity on the Amateur Bands.
>
> Sincerely,
>
> /s/ Steve, N2CKH
>
>

I received a suggestion that I create a Worked All Counties
interactive web page similar to my popular SKCC Helper and the Digital
Modes pages .  I took a look at the activity of my Worked All States
interactive page and decided to add the Counties page to it.  The
Worked All States page gets active at times, but not as active as the
others, thus the decision to merge State and County Hunting in to one.
  You can find it at
http://www.obriensweb.com/wac/wac.php


Effective immediately, those pointing their browser to the WAS page
will be redirected to the WAS and WAC page.  Former WAS users will
have to briefly re-enter their user info, since I have added a county
field that will be displayed to all others logged on (via a mouse
over).

I have added suggested calling frequencies for Digital, CW and
SSB-Phone State and County hunters, but users can post any frequencies
they may be listening on.  I will add more frequencies later.

Additionally, the ALE interactive page that I created is now directed
to the new page created by HFLINK.  Back channel ALE traffic is
welcome on the main digital mode interactive page, but users are
encouraged to use the HFLINK page at http://hflink.net/qso/

Andy K3UK
CW :                  http://www.obriensweb.com/skccsked/skccsked.php
Digital                http://www.obriensweb.com/drsked/drsked.php
ALE                   http://hflink.net/qso/
WAS/Counties :  http://www.obriensweb.com/wac/wac.php

Hi Rick,

At 07:01 PM 8/4/2007, you wrote:
>Thanks for your comments, Steve,
>
>I understood that it did support the ICOM 756 Pro 2, including CAT
>control, and was told by someone in the ALE world that I needed to check
>the CAT box which I of course did. Maybe I missed it, but I did not
>realize that this particular rig can not even operate at this time with
>CAT control, because if I did, I would not have spent quite so many
>hours trying to get it to key with PTT CAT:( I don't have any hardware
>PTT plans at this time as other programs work reasonably well and it
>simplifies the cabling requirements.

The PC-ALE versions that have been out for years provides support for
any ICOM radios address, baud rate
etc. and SPLIT VFO operation via the GENERIC ICOM interface, but not
CAT PTT ever, originally PTT was
only RTS or DTR as in the past for one thing CAT PTT was not common
in radios and hardware PTT it was much more reliable than CAT PTT.
Also, most all of the radios with dedicated digital ports do NOT
support the use of CAT PTT via those ports.

Any, I have updated PC-ALE for the next release with CAT PTT for all
radios that support it.


>What I  understood was that the current program is defective with
>setting up the split function properly. It sets it up the split when you
>boot the program, not when you scan, and it does not return to non-split
>mode either when you stop scanning or when you leave the program. My
>understanding was that this will be fixed in the new version, although
>it is still in Alpha at this time.

No defect, nothing to fix, for ICOM radios only in the past and via
the GENERIC ICOM interface only, you could enable SPLIT VFO all the
time to defeat those pesky PA spectral purity relays during Scanning.

In the current PC-ALE in ALPHA testing I have applied a new approach
similar to that which I developed for MARS-ALE where for any radio
that supports SPLIT VFO ( and a radio specific BYPASS command) where
it will tame those pesky relays for scanning, that when scanning is
started the issue is addressed and when scanning is stopped normal
operation of those relays resume. Its an enhancement, not a fix.


>Your list of the many different rigs is very helpful and this kind of
>information needs to be easily located on ALE websites so that there is
>no misunderstanding of what a given "supported" rig can or can not do at
>any given time. It doesn't make sense to me why this would not be
>heavily promoted.

Its all posted at HFlink.

For the next release a page has been created by the webmaster at:

http://hflink.com/pcale/pcaleradio.html


>As far as activity, I suppose it depends upon your definition. I
>monitored for several hours today with scanning with the ICOM 756 Pro 2
>and heard the following:
>
>KK7IF
>VE2FXL
>WD8ARZ
>KM4BA
>LU8EX
>VE6OG
>
>Of course there can be other areas of the world and those with better
>antennas who may be able to copy more test signals and calls.Most of
>these were soundings but some appeared to be calls. I don't know if you
>actually can receive any messages being sent by others when in this
>scanning mode, but I have not actually printed anything like that.
>
>Again, it seems that it is difficult to find information of this kind on
>the internet and I rather expect it to be very openly available and very
>clear and concise.
>

Again, the proper venue is Hflink.com, if you can't find what you
want, just ask the web master.

/s/ Steve, N2CKH





>Steve Hajducek wrote:
> > Hi Rick,
> >
> > I have replied to your comments many times on these matters:
> >
> > 1. PC-ALE as released does not specifically support the PRO2, the
> > next release will. For now if you are not interested in ALPHA testing
> > the next release, its the use of the GENERIC ICOM interface and
> > DTR/RTS for PTT. It works for everyone else that has a PRO2, I can't
> > see why you should have any problems unless you have something out of
> > the ordinary configured.
> >
> > 2. As hard as you may find it to believe, there is a lot of ALE
> > activity on the Amateur Bands.
> >
> > Sincerely,
> >
> > /s/ Steve, N2CKH
> >
> >
>
>
>Announce your digital presence via our Interactive Sked Page at
>http://www.obriensweb.com/drsked/drsked.php
>
>Yahoo! Groups Links
>
>
>

Steve and those interested in the ICOM rigs for ALE:

I had asked Steve:

> I am using the default hex address 64 with CAT PTT selected.
And he responded with information on the new Alpha version:

For the new ALPHA  version of PC-ALE you still need to select CAT PTT if
that is your desire, I have coded CAT PTT for all make/model radios
where supported.

- - - - -

I must have misinterpreted what he said, but to me, this means that if
you "still need to select CAT PTT" which definitely is my desire, then
it was available earlier as well.  Especially since someone else
confirmed this a while back that I needed to check the right box. Sorry
that there was this unfortunate miscommunication or lack of knowledge on
someone's part.

With new software coming out my hope is that we will be able to control
the PTT CAT which is a mandatory issue with me as I just will not use
software that can not support this feature since the top digital
software has been doing this for some time and I suppose you get "spoiled."

I do consider the fact that the PC-ALE software could not go into split
when you scanned and return to normal operation as a defect or at least
a shortcoming when the new software is going to correct that. Steve, you
must be in marketing in your day job to claim this is not even a fix:).

Just as an example of what can happen, if you are using your rig to do
ALE scanning and forget about the split operation,    and I have been
doing a lot of this lately, you may be operating illegally when you
switch to another software program, such as Multipsk, if you do not
remember to return the transceiver to normal operation!! This actually
happened to me on Friday so it is not something theoretical:(

HFlink does not seem to have all the information that I need, nor have I
had much luck in asking, thus I have been asking in the larger digital
group. I have been thinking about the possibility of forming an ALE
related group which does not have an agenda and will be more open to
problems and questions.

Even then, I have been a bit surprised that almost no one other than the
regular ALE folks, have tried to assist or even have ever mentioned
their experiences with ALE, and nothing yet on the single tone modems.
Maybe over time, there will be a critical mass of operators so some of
these digital modes can be explored? I know that I want to try them out
to see if they really can compete with existing modes.

Most recent ALE scanning from 1617 Z to 1836Z with lowest frequency 40
meters and highest frequency 12 meters and some stations received
multiple times and bands:

K7EK
AF6 to KQ6XA
KB3FN to KF4IN
NOCALLSIGN
NJ7C
VE2FXL
KF4IN
KQ6XA
VE2FXL to W9WIS
EA2AFR

Maybe try and call some of these or see if anyone is around. I am still
not sure if you see connections when you monitor because thus far I have
only see soundings or someone that appears to be calling "to" someone
but no apparent response.

Have I got that right?

73,

Rick, KV9U




Steve Hajducek wrote:
> Hi Rick,
>
> At 07:01 PM 8/4/2007, you wrote:
>
>> Thanks for your comments, Steve,
>>
>> I understood that it did support the ICOM 756 Pro 2, including CAT
>> control, and was told by someone in the ALE world that I needed to check
>> the CAT box which I of course did. Maybe I missed it, but I did not
>> realize that this particular rig can not even operate at this time with
>> CAT control, because if I did, I would not have spent quite so many
>> hours trying to get it to key with PTT CAT:( I don't have any hardware
>> PTT plans at this time as other programs work reasonably well and it
>> simplifies the cabling requirements.
>>
>
> The PC-ALE versions that have been out for years provides support for
> any ICOM radios address, baud rate
> etc. and SPLIT VFO operation via the GENERIC ICOM interface, but not
> CAT PTT ever, originally PTT was
> only RTS or DTR as in the past for one thing CAT PTT was not common
> in radios and hardware PTT it was much more reliable than CAT PTT.
> Also, most all of the radios with dedicated digital ports do NOT
> support the use of CAT PTT via those ports.
>
> Any, I have updated PC-ALE for the next release with CAT PTT for all
> radios that support it.
>
>
>
>> What I  understood was that the current program is defective with
>> setting up the split function properly. It sets it up the split when you
>> boot the program, not when you scan, and it does not return to non-split
>> mode either when you stop scanning or when you leave the program. My
>> understanding was that this will be fixed in the new version, although
>> it is still in Alpha at this time.
>>
>
> No defect, nothing to fix, for ICOM radios only in the past and via
> the GENERIC ICOM interface only, you could enable SPLIT VFO all the
> time to defeat those pesky PA spectral purity relays during Scanning.
>
> In the current PC-ALE in ALPHA testing I have applied a new approach
> similar to that which I developed for MARS-ALE where for any radio
> that supports SPLIT VFO ( and a radio specific BYPASS command) where
> it will tame those pesky relays for scanning, that when scanning is
> started the issue is addressed and when scanning is stopped normal
> operation of those relays resume. Its an enhancement, not a fix.
>
>
>
>> Your list of the many different rigs is very helpful and this kind of
>> information needs to be easily located on ALE websites so that there is
>> no misunderstanding of what a given "supported" rig can or can not do at
>> any given time. It doesn't make sense to me why this would not be
>> heavily promoted.
>>
>
> Its all posted at HFlink.
>
> For the next release a page has been created by the webmaster at:
>
> http://hflink.com/pcale/pcaleradio.html
>
>
>
>> As far as activity, I suppose it depends upon your definition. I
>> monitored for several hours today with scanning with the ICOM 756 Pro 2
>> and heard the following:
>>
>> KK7IF
>> VE2FXL
>> WD8ARZ
>> KM4BA
>> LU8EX
>> VE6OG
>>
>> Of course there can be other areas of the world and those with better
>> antennas who may be able to copy more test signals and calls.Most of
>> these were soundings but some appeared to be calls. I don't know if you
>> actually can receive any messages being sent by others when in this
>> scanning mode, but I have not actually printed anything like that.
>>
>> Again, it seems that it is difficult to find information of this kind on
>> the internet and I rather expect it to be very openly available and very
>> clear and concise.
>>
>>
>
> Again, the proper venue is Hflink.com, if you can't find what you
> want, just ask the web master.
>
> /s/ Steve, N2CKH
>
>
>

Rick,

Please continue the discussion here, or start a new group.  The
censorship and agenda that takes place on the hflink group will do more
to harm the modes future in the amateur environment than anything else.

Open discussion and community participation are key to the adoption of
new technologies.  I know I'm not alone, in spending my time composing
responses and framing questions for group discussion on hflink, only to
have my posts end up apparently in /dev/null.  Its almost humorous, as
some of the personalities that run the hflink group are fairly notorious
as bullies on other groups, complaining that they are being censored,
when their posts don't show up minutes after they click their mail
clients send buttons.

When the hflink crowd wants the participation and support of the amateur
community for ale, I hope they let us know, as it certainly won't be
something I find out via the hflink group anytime soon.


73,

Erik, N7HMS
IRLP Node 3804 445.975 Simp PL103.5
North Bend, WA CN97ck

Emails sent directly to this address instead of going through a yahoo
group are automatically processed as junk mail, so I never see them.  If
you want to email me directly, please use 'mycall' at 12bars dot com,
thanks.


Rick wrote:
>  I have been thinking about the possibility of forming an ALE
> related group which does not have an agenda and will be more open to
> problems and questions.
>

Hi Rick,

At 02:38 PM 8/5/2007, you wrote:
>Steve and those interested in the ICOM rigs for ALE:
>
>I had asked Steve:
>
> > I am using the default hex address 64 with CAT PTT selected.
>And he responded with information on the new Alpha version:
>
>For the new ALPHA  version of PC-ALE you still need to select CAT PTT if
>that is your desire, I have coded CAT PTT for all make/model radios
>where supported.
>
>- - - - -
>
>I must have misinterpreted what he said, but to me, this means that if
>you "still need to select CAT PTT" which definitely is my desire, then
>it was available earlier as well.  Especially since someone else
>confirmed this a while back that I needed to check the right box. Sorry
>that there was this unfortunate miscommunication or lack of knowledge on
>someone's part.

In PC-ALE you actually need to check a box for CAT PTT. In MARS-ALE
if RTS or DTR are not checked for PTT then CAT PTT is by default
selected, thus you see my mind set in my wording.


>With new software coming out my hope is that we will be able to control
>the PTT CAT which is a mandatory issue with me as I just will not use
>software that can not support this feature since the top digital
>software has been doing this for some time and I suppose you get "spoiled."

It may be mandatory with you Rick however the bulk of all Amateurs
that I have had contact with over the years to include myself do not
use CAT PTT for digital ops.


>I do consider the fact that the PC-ALE software could not go into split
>when you scanned and return to normal operation as a defect or at least
>a shortcoming when the new software is going to correct that. Steve, you
>must be in marketing in your day job to claim this is not even a fix:).

It can't be a fix when it was not designed to do anything other than
be in SPLIT VFO all the time if the user selected SPLIT VFO now can it?

You may not realize it, but the majority of all radios designed for
ALE are basically always in duplex operation as you need to program
in both an RX and TX frequency and often a mode for each, although
many just use a common mode, this is also true of most Military,
Commercial and Marine grade HF SSB transceivers, even many Amateur
transceivers are like that when if comes to computer control, e.g.
FT-600 and Ten Tec Jupiter and Pegasus. So when G4GUO started to
provide SPLIT VFO for ICOM radios as they were at the time the most
popular make being used for ALE and it was known that it would hold
off the pesky PA relays for a number of models, being in duplex all
the time when selected was rather natural. Don't forget, the tool
asks you for both RX and TX frequency and mode in setup.


>Just as an example of what can happen, if you are using your rig to do
>ALE scanning and forget about the split operation,    and I have been
>doing a lot of this lately, you may be operating illegally when you
>switch to another software program, such as Multipsk, if you do not
>remember to return the transceiver to normal operation!! This actually
>happened to me on Friday so it is not something theoretical:(

Well that was an oversight in previous versions of PC-ALE as the
GENERIC ICOM selection is not even part of the
"radio_de_initialise_module" which would have placed the radio back
into simplex. However it is a pretty easy thing for a user to get
used to doing and all must as I have never heard anyone complain
about it before, I take it that you don't do much DX  voice work on 40 meters?

>HFlink does not seem to have all the information that I need, nor have I
>had much luck in asking, thus I have been asking in the larger digital
>group. I have been thinking about the possibility of forming an ALE
>related group which does not have an agenda and will be more open to
>problems and questions.
>
>Even then, I have been a bit surprised that almost no one other than the
>regular ALE folks, have tried to assist or even have ever mentioned
>their experiences with ALE, and nothing yet on the single tone modems.
>Maybe over time, there will be a critical mass of operators so some of
>these digital modes can be explored? I know that I want to try them out
>to see if they really can compete with existing modes.

Posturing aside, ask away as I have no agenda's when it comes to ALE
and Amateur Radio other than being of assistance when asked and
providing to the best of my abilities the correct information on the
subject matter that I can.


>Most recent ALE scanning from 1617 Z to 1836Z with lowest frequency 40
>meters and highest frequency 12 meters and some stations received
>multiple times and bands:
>
>K7EK
>AF6 to KQ6XA
>KB3FN to KF4IN
>NOCALLSIGN
>NJ7C
>VE2FXL
>KF4IN
>KQ6XA
>VE2FXL to W9WIS
>EA2AFR

That station running NOCALLSIGN needs to linked with and informed
that they have forgot to change they SELCAL properly.


>Maybe try and call some of these or see if anyone is around. I am still
>not sure if you see connections when you monitor because thus far I have
>only see soundings or someone that appears to be calling "to" someone
>but no apparent response.
>
>Have I got that right?

What you see with ALE depends on the system being used and your
selection of configuration parameters. With PC-ALE out of the box you
will see all Soundings and if configured to do so see and respond to
all linking calls. As to monitoring traffic, of the ALE protocols,
you will only be able to display the AMD traffic when not a party to
the link as the tool is written, the DTM and DBM traffic is not
displayed otherwise, this is also true of the MIL-STD-188-110 modem
with FS-1052 protocols. This in ability to monitor 3rd party acty
that one is not involved in using ALE is due to the way in which the
standards are written and most all ALE hardware was designed, it
would be true also of AMTOR, GTOR and PACTOR I if it were not for the
fact that being Amateurs, a LISTEN mode was incorporated, which I
have done for MARS-ALE as to DTM and DBM by the way and which G4GUO
has indicated to me he likes the idea of doing for PC-ALE as well. By
the way, ALE hardware radios do not even allow you to display AMD
data between stations when you are not linked, at least I have not
determined that any do!

./s/ Steve, N2CKH

>73,
>
>Rick, KV9U