FYI folks....
The new version of Logger (7.03) automatically takes a call from IZ8BLY
MT63 Terminal software and places it into your Logger logbook, if both
Logger and IZ8BLY MT63 are open at the same time(see below)
>To allow users of the IZ8BLY FeldHell and MT63 software to log directly to
the Logger databases, an invisible interface >has been implemented. If both
programs are running on the PC, the log data from the IZ8BLY program will
automatically >be entered into the Logger Logbook. Logger ignores the
Date/Time, and Mode from the IZ8BLY software, and defaults to >the
Date/Time, and Mode it is configured for. If Logger is configured for
control of the radio, and the radio supports PTT >by radio command. Then the
IZ8BLY software interface to Logger will key the radio PTT with the Logger
radio control >port.
Andy KB2EOQ
Hi,
just tested this feature in Logger 7.03. It works UFB. You must:
- open Logger
- open PSK31
- check Config - PTT with Radio Commad
- close PSK31
- check Config - Fast polling
- open IZ8BLY (Hell or MT63)
- check WD5GNR/LOGGER PTT
Nice feature for Laptops with only one or two Com ports.
73 Josef OK2WO
In my IZ8BLY MT63 software I frequently get an "invalid floating point"
error that requires me to then re-boot the software in order for it to work
properly. Any ideas on a fix for this? The problem has occurred on the
last two versions, the only versions I have tried.
Andy KB2EOQ
Hello,
I have the same problem on my Toshiba Laptop (Pentium 120) not on my desktop
(Pentium II 300). I think it is CPU problem
Josef
----- Original Message -----
From: Andrew J. O'Brien <obrienaj@...>
To: <MT63@onelist.com>
Sent: Thursday, March 02, 2000 1:33 PM
Subject: [MT63] Invalid Floating Point
> From: "Andrew J. O'Brien" <obrienaj@...>
>
> In my IZ8BLY MT63 software I frequently get an "invalid floating point"
> error that requires me to then re-boot the software in order for it to
work
> properly. Any ideas on a fix for this? The problem has occurred on the
> last two versions, the only versions I have tried.
>
> Andy KB2EOQ
>
>
> ------------------------------------------------------------------------
> GET A NEXTCARD VISA, in 30 seconds! Get rates
> as low as 0.0% Intro APR and no hidden fees.
> Apply NOW!
> http://click.egroups.com/1/975/2/_/524264/_/952000678/
> ------------------------------------------------------------------------
>
> << Have you tried DX PSK-Hell yet? >>
> << Visit http://www.qsl.net/zl1bpu >>
>
> - The MT63 Reflector -
> MT63@onelist.com
>
> (To unsubscribe. send email to
> MT63-unsubscribe@onelist.com)
>
>
I occasionally get the same message (with all the versions of MT63 that I
have tried). Sometimes the message keeps repeating itself over and over
again (i.e. multiple error message boxes all on top of each other!). It
seems to happen most often if I overload my sound card audio input when
first adjusting the audio levels.
Remember that MT63 is still in beta phase. Bugs are still possible. I am
sure Nino will iron out all the bugs soon.
Rob
VA2FB
>From: "Andrew J. O'Brien" <obrienaj@...>
>Reply-To: MT63@onelist.com
>To: <MT63@onelist.com>
>Subject: [MT63] Invalid Floating Point
>Date: Thu, 2 Mar 2000 07:33:47 -0500
>
>In my IZ8BLY MT63 software I frequently get an "invalid floating point"
>error that requires me to then re-boot the software in order for it to work
>properly. Any ideas on a fix for this? The problem has occurred on the
>last two versions, the only versions I have tried.
>
>Andy KB2EOQ
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
Josef,
As I mentioned earlier, I have the same error message with my Toshiba laptop
(using Pentium II at 300 Mhz). Maybe it is not a CPU problem but a problem
with Toshiba laptops - hi!
Rob
VA2FB
>From: "Josef Klimosz" <Josef.Klimosz@...>
>Reply-To: MT63@onelist.com
>To: <MT63@onelist.com>
>Subject: Re: [MT63] Invalid Floating Point
>Date: Thu, 2 Mar 2000 15:24:26 +0100
>
>From: "Josef Klimosz" <Josef.Klimosz@...>
>
>Hello,
>
>I have the same problem on my Toshiba Laptop (Pentium 120) not on my
>desktop
>(Pentium II 300). I think it is CPU problem
>
>Josef
>
>----- Original Message -----
>From: Andrew J. O'Brien <obrienaj@...>
>To: <MT63@onelist.com>
>Sent: Thursday, March 02, 2000 1:33 PM
>Subject: [MT63] Invalid Floating Point
>
>
> > From: "Andrew J. O'Brien" <obrienaj@...>
> >
> > In my IZ8BLY MT63 software I frequently get an "invalid floating point"
> > error that requires me to then re-boot the software in order for it to
>work
> > properly. Any ideas on a fix for this? The problem has occurred on the
> > last two versions, the only versions I have tried.
> >
> > Andy KB2EOQ
> >
> >
> > ------------------------------------------------------------------------
> > GET A NEXTCARD VISA, in 30 seconds! Get rates
> > as low as 0.0% Intro APR and no hidden fees.
> > Apply NOW!
> > http://click.egroups.com/1/975/2/_/524264/_/952000678/
> > ------------------------------------------------------------------------
> >
> > << Have you tried DX PSK-Hell yet? >>
> > << Visit http://www.qsl.net/zl1bpu >>
> >
> > - The MT63 Reflector -
> > MT63@onelist.com
> >
> > (To unsubscribe. send email to
> > MT63-unsubscribe@onelist.com)
> >
> >
>
>
>
>------------------------------------------------------------------------
>PERFORM CPR ON YOUR APR!
>Get a NextCard Visa, in 30 seconds! Get rates as low as
>0.0% Intro or 9.9% Fixed APR and no hidden fees.
>Apply NOW!
>http://click.egroups.com/1/2121/2/_/524264/_/952006726/
>------------------------------------------------------------------------
>
><< Have you tried DX PSK-Hell yet? >>
><< Visit http://www.qsl.net/zl1bpu >>
>
>- The MT63 Reflector -
> MT63@onelist.com
>
>(To unsubscribe. send email to
>MT63-unsubscribe@onelist.com)
>
>
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
On Thu, Mar 02, 2000 at 03:24:26PM +0100, Josef Klimosz wrote:
> I have the same problem on my Toshiba Laptop (Pentium 120) not on my desktop
> (Pentium II 300). I think it is CPU problem
If I leave the program running for quite a while I get a variety of
errors -- access violations mostly, sometimes floating point errors too.
My CPU is a Pentium MMX, but I don't think it is CPU related.
The software crashes particularly quickly if there is no audio input
eg I turn off the receiver but leave the software running.
Hamish
Yes, I think there is a relationship between the audio input level to the
sound card and MT63 program crashes.
I have found that floating point errors are more common when I turn off the
audio from the rig.
Rob
VA2FB
>From: Hamish Moffatt <hamish@...>
>Reply-To: MT63@onelist.com
>To: MT63@onelist.com
>Subject: Re: [MT63] Invalid Floating Point
>Date: Fri, 3 Mar 2000 07:56:43 +1100
>
>On Thu, Mar 02, 2000 at 03:24:26PM +0100, Josef Klimosz wrote:
> > I have the same problem on my Toshiba Laptop (Pentium 120) not on my
>desktop
> > (Pentium II 300). I think it is CPU problem
>
>If I leave the program running for quite a while I get a variety of
>errors -- access violations mostly, sometimes floating point errors too.
>My CPU is a Pentium MMX, but I don't think it is CPU related.
>
>The software crashes particularly quickly if there is no audio input
>eg I turn off the receiver but leave the software running.
>
>
>Hamish
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
> From: Hamish Moffatt <hamish@...>
> The software crashes particularly quickly if there is no audio input
> eg I turn off the receiver but leave the software running.
Golden words, Hamish! Usually I switch on my laptop WITHOUT radio and
everytime switch on my desktop WITH radio. Things are so simple...and I must
still learn. Very good for other hams who contact me with questions. Thanks.
Josef
Hi Gang....
Regarding the error messages mention by many, I have always experienced
these messages but only when I turn the audio input right down on the rig
(no signals on the soundcard input) and never when signals are present on
the soundcard input.
The new logging facility is good but would like to see the program "GRAB"
the callsign like it use to before this change was made. Something along the
lines of placing the cursor on required callsign and "double clicking" would
do the trick. Now one has to bring up the logbook and enter the callsign to
have the metacommand "OTHER" work - rather a long winded operation! - how
about it Nino? Still on the same subject, how about having "\" (back-slash)
when cursor is in the callsign field - clear this field...... instead of
numerous keystrokes of the delete key.
Regards to all
73 de Vic - G3GKI
On Fri, 3 Mar 2000 12:01:05 -0000, Victor Kershaw wrote:
> From: "Victor Kershaw" <v.kershaw@...>
>
> Hi Gang....
> Regarding the error messages mention by many, I have always experienced
> these messages but only when I turn the audio input right down on the rig
> (no signals on the soundcard input) and never when signals are present on
> the soundcard input.
I've never had the problem with any version. I just tried it on two
machines with audio removed, no problem with either.
Someone recently said they couldn't leave MT running long periods. I'm
not sure how long they were talking about, but I've left mine for two
days with no problem. The fact that you have to unload before you use
another sound program keeps it from being there very long.
> The new logging facility is good but would like to see the program "GRAB"
> the callsign like it use to before this change was made. Something along the
> lines of placing the cursor on required callsign and "double clicking" would
> do the trick. Now one has to bring up the logbook and enter the callsign to
> have the metacommand "OTHER" work - rather a long winded operation! - how
> about it Nino? Still on the same subject, how about having "\" (back-slash)
> when cursor is in the callsign field - clear this field...... instead of
> numerous keystrokes of the delete key.
I too am wishing the old way was back. I don't use the log feature, as
I already have a log book that I have a lot of time invested in. A
config setting to use the old F11 pop up with callsign only in it would
be nice. A key feature of the old method was the ability to hit F11,
type the callsign, hit enter, and keep going...no movement to the mouse,
hands never left my arms, etc. I might be interested in the log feature
if it had a way to EASILY and AUTOMATICALLY export directly to the EQF
data file.
Gary
ag0n at arrl dot net
--
Please notify your ISP if you don't receive this.
On Fri, 03 Mar 2000 07:26:40 -0700, Gary McDuffie, Sr. wrote:
> I might be interested in the log feature
> if it had a way to EASILY and AUTOMATICALLY export directly to the EQF
> data file.
I should also have added.. ...and a way to read frequency directly from
the radio interface like EQF does.
Gary
ag0n at arrl dot net
--
Please notify your ISP if you don't receive this.
I agree that it would be great to grab the call from the data screen using a
double click of the mouse and placing the call into the Call field of the
Logging screen.
But I would also like to see a "Right Click" mouse function found in some
terminal/logging programs. You "right click" a word on the data terminal
screen and then a pop up menu appears. You then click on "Call", "QTH",
"Name" etc to copy the word from the data screen into the appropriate field
of the logging screen.
This way you don't need to use the keyboard to copy ANY info into the
Logging screen.
I hope Nino considers adding these features to both his Hell and MT63
programs if it is not too difficult.
73's
Rob
VA2FB
Of course for Hell, you will need some sort of image to character
translation program in order to implement such advanced logging features in
Nino's Hell program.
73's
Rob
VA2FB
----- Original Message -----
From: "Rob Kennedy" <amtor@...>
To: <Hellschreiber@onelist.com>; <MT63@onelist.com>
Sent: Friday, March 03, 2000 10:16 AM
Subject: Improving Logging features in Hell and MT63 Programs
> I agree that it would be great to grab the call from the data screen using
a
> double click of the mouse and placing the call into the Call field of the
> Logging screen.
>
> But I would also like to see a "Right Click" mouse function found in some
> terminal/logging programs. You "right click" a word on the data terminal
> screen and then a pop up menu appears. You then click on "Call", "QTH",
> "Name" etc to copy the word from the data screen into the appropriate
field
> of the logging screen.
>
> This way you don't need to use the keyboard to copy ANY info into the
> Logging screen.
>
> I hope Nino considers adding these features to both his Hell and MT63
> programs if it is not too difficult.
>
> 73's
>
> Rob
> VA2FB
>
Rob wrote:
> I agree that it would be great to grab the call from the data screen using
a
> double click of the mouse and placing the call into the Call field of the
> Logging screen.
instead of "it would be", you can say "it is"... I mean that in V0.99h you
can simply transfer text from the terminal window into the "mini-log" window
using two double clicks (double click on source, then double click on
destination). This applies also to the "second channel" if the other
operator has setup a text with QRZ,Name,and QTH.
The "popup" menu you've suggested is not possible because the "selection" is
lost if data arrives in the meantime...
Regarding for Hell, a sort of OCR (optical character recognition) would be
needed. This leads to an old idea by Murray ZL1BPU, that is making a
"digital" decoder and compare performances with the "eyes/human brain"
decoder. An interesting approach could be of making a convolutional code
where the representation of each code is just the sequence of pixels
obtained from hell-character matrix.
73 de Nino IZ8BLY
Hi Gang -
For sometime I have been puzzle why very weak signals below the "noise floor
level" which is not even visible on the waterfall or even audible can
produce perfect solid copy - at times!
When pre-formed message streams like the signal report or any such loaded
function keys are being sent, in these below noise floor conditions they
always produce perfect copy but once the keyboard input is being sent then
only garbage is being produced.
The only difference which I am aware of is during keyboard input and when no
character is available for sending then the "secondary channel"
(ticker-tape)
is sent. This interleaving of both information streams constantly taking
place when using the keyboard. (unless a very efficient typist) Now could
this change from one coding to another or phase/sync change be upsetting the
reliability of MT63 for use under extreme weak signal condition. If this is
the case then there should be a means to disable the ticker tape other than
deleting the secondary text when the user wishes to exploit weak signal
communication.
These observations made on 28130.
Has anyone discovered a way to remove the "WINDOWS" type of the log window
other than coming out of the program? You not seen this window then double
click on the two vertical lines on the left of the log window.
73 de Vic
G3GKI
Josef,
It is impossible to set Fast Polling checkbox. If you set Fast Polling it is
re-set back to the Mid Polling.
The only one Mid Polling can be set. You try to set Fast Polling - Logger
set it back to Mid Polling.
I could find WHY - my speed in ICOM-746 is set to 19200B.
SP6NIN
Marek
----- Original Message -----
From: Josef Klimosz <josef.klimosz@...>
To: Hellschreiber List <Hellschreiber@onelist.com>; MT63 <MT63@onelist.com>;
Logger <logger@egroups.com>
Sent: Thursday, March 02, 2000 12:43 PM
Subject: [Logger] IZ8BLY -> Logger PTT
> Hi,
>
> just tested this feature in Logger 7.03. It works UFB. You must:
> - open Logger
> - open PSK31
> - check Config - PTT with Radio Commad
> - close PSK31
> - check Config - Fast polling
> - open IZ8BLY (Hell or MT63)
> - check WD5GNR/LOGGER PTT
>
> Nice feature for Laptops with only one or two Com ports.
>
> 73 Josef OK2WO
>
>
>
>
> ------------------------------------------------------------------------
> To UNSUBSCRIBE from this list, send a blank email message to:
> mailto:logger-unsubscribe@egroups.com
>
> Download Logger and other goodies at the GOLIST webpage:
> http://www.itis.net/golist/
>
> ------------------------------------------------------------------------
> Luck o' the Irish! Get your St. Paddy's day party supplies at
> GreatEntertaining.com today. Green salami, brew kits, shamrock
> confetti, gold coins, & more. Erin Go Bragh!
> http://click.egroups.com/1/2042/1/_/3545/_/951997749/
>
>
> eGroups.com home: http://www.egroups.com/group/logger
> http://www.egroups.com - Simplifying group communications
>
>
>
>
>
>
> --------------------------------------------------------------------------
------
> Od 21.02 do 5.03. aukcja charytatywna firmy Inter-Aukcja i Caritas Polska.
> Licytujemy samochody, sprzęt komputerowy oraz wiele innych ciekawych i
> cennych rzeczy. Spotkaj się z nami na stronie http://www.ia.pl lub na
serwerze
> Caritas - http://www.caritas.pl
>
_____________________________________________________
x86 Magazyn komputerowy http://www.x86.pl
NAJWIĘKSZA BAZA STEROWNIKÓW I WYGASZACZY W POLSCE
_____________________________________________________
I just heard someone calling on MT63 on 14.061 (dial frequency USB).
I couldn't copy the call. Please don't do that -- MT63 does not belong
in that part of the band, we have enough competition there as is!
Presently copying EI9FV and HB9BDM in QSO on PSK Hell 105.
Hamish VK3SB
The posting about MT63 on 14.061 reminded me of another pet peeve.
I sometimes monitor unattended and check the monitor now and then to see
if there has been any activity. I've noticed that many stations are not
operating on the even kilohertz frequencies as earlier suggested and
discussed. It turns out that most of them probably think they are, but
by the time you multiply their small calibration error up to 28MHz, it
is quite large. Remember, an error of 100 Hertz at 10MHz multiplies to
300 Hertz at 30MHz. Many stations are between 0 and 200 Hertz "off
channel" when they are on ten meters. My neighbor's rig was about 180
Hertz off until we calibrated it properly. I've seen as much as 300,
but no idea what the guy's dial read at the time.
Please check your calibration.
Gary
ag0n at arrl dot net
--
Please notify your ISP if you don't receive this.
On Tue, Mar 07, 2000 at 12:25:09PM -0600, Bruce wrote:
> Hamish
> In the interest of harmony, I feel I should point out
> that it's the person using the frequency, not the mode he chooses
> to us. Or, that if the amateur finds the frequency open,
> then he should be free to use the mode of his choice during the time
> he has the frequency. While he is using the frequency, it
> should not be available to anyone else during that time regardless
> of which mode he chooses to use.
> You may not agree, but it might be worth some
> thought, hi.
Bruce,
Usually yes -- but MT63 is a wide band mode and should not be operated
in the narrow band segment. Just as SSB (ie phone) is not welcome on
14.061 either.
It is better for everyone if we stick to the bandplan. I think MT63
operation on 14.061 would also be illegal due to part 97 rules in
the USA.
73
Hamish VK3SB
Hamish,
Reply to yours of 3:13,
1) The FCC space limit is 1000 hz for all data
modes,
and 2) digital operators have not yet agreed upon
and
made known a band plan different than the one we've
all been living with.
Although your replies did not actually relate to
what
I was talking about, I appreciate them and I hope
that
you understood what I was pointing at.
73, Bruce
-----Original Message-----
From: Hamish Moffatt
March 07, 2000 3:13 PM
To: Bruce; mt63@onelist.com
Subject: [MT63] Re: [Hellschreiber] mt63 on 14.062
Bruce,
Usually yes -- but MT63 is a wide band mode and
should not be operated
in the narrow band segment. Just as SSB (ie phone) is
not welcome on
14.061 either.
It is better for everyone if we stick to the
bandplan. I think MT63
operation on 14.061 would also be illegal due to part
97 rules in
the USA.
73
Hamish VK3SB
>On Tue, Mar 07, 2000 at 12:25:09PM -0600, Bruce
wrote:
> Hamish
> In the interest of harmony, I feel I should point
out
> that it's the person using the frequency, not the
mode he chooses
> to use. Or, that if the amateur finds the
frequency open,
> then he should be free to use the mode of his
choice during the time
> he has the frequency. While he is using the
frequency, it
> should not be available to anyone else during that
time regardless
> of which mode he chooses to use.
> You may not agree, but it might be worth some
> thought, hi.
>73
>Bruce
>ko5t@...
-----Original Message-----
From: Hamish Moffatt
On Tue, March 07, 2000 at 2:28 AM Hamish wrote:
To: mt63@onelist.com; hellschreiber@Onelist.com
Subject: [Hellschreiber] mt63 on 14.062
From: Hamish Moffatt <hamish@...>
I just heard someone calling on MT63 on 14.061 (dial
frequency USB).
I couldn't copy the call. Please don't do that --
MT63 does not belong
in that part of the band, we have enough competition
there as is!
Presently copying EI9FV and HB9BDM in QSO on PSK Hell
105.
Hamish VK3SB
Bruce,
On Tue, Mar 07, 2000 at 09:06:10PM -0600, Bruce wrote:
> From: "Bruce" <ko5t@...>
>
> Hamish,
> Reply to yours of 3:13,
> 1) The FCC space limit is 1000 hz for all data
> modes,
Really, that is news to me? Everybody on this list indicated
that MT63 was too wide for the data segment. Actually, with CW ID
on the bottom edge of the signal it is wider than 1kHz.
You should also consider the spirit of the rules and the band plan --
MT63 is not compatible with Hell and QRP CW on the same part of the band.
MT63 will just wipe those out.
Really, there is no need to operate MT63 on 14.06x. There are other
locations which are fine. 14.080-14.112 somewhere. It's just poor
operating.
Hamish vk3sb
Hi all
When launching MT63, Win2K tells me "audio device not found".
Probably due to incomplete AWE64 driver supplied with Win2K,
although system sounds etc are working fine.
Anybody successfully running Nino's MT63 soft under Win2K?
If so, please post what sound card you are using. Tnx!
73, Markus HB9BRJ
Bruce,
I think you guys are forgetting something -
While the FCC might well allow you to run 1 kHz wide modes on 14.063 MHz if
you live in the USA, the rest of the world could not care a fig what the FCC
say. We are bound by the IARU recommendations, at it is hoped that the US
Amateurs are cognisant of these too.
So, while you might be legally entitled to run any digital mode you like on
14.063 MHz, the rest of the world will take a dim view of it. The rest of
the world expects this area to be for narrow band CW style operation, much
of it QRP. In many countries the bandwidth is spelled out, and in some
countries operation is limited to Morse.
It might be that digital operators have not made any binding arrangement for
the use of modes such as MT63, but there sure are existing and very good
arrangements for other modes in the area 14.050 to 14.100 MHz.
I ask US digital operators to be good ambassadors for their country by
pleasing the rest of the world - remember, the USA is only one of hundreds
of countries which share the 20m band.
73,
Murray ZL1BPU
Hello, Markus!
No problems here with Win2K (beta version) and MT63. I am using MT63 by
Nino during some months. My setup:
Pentium with AMD-K5 166 MHz 64MB RAM,
Sound Card Creative AWE-64.
Also using this SC with a number of programs like MT63,HellShreiber,
DigiPan, Writelog, JVComm, Logger... Only one difference for MT63 (in
comparison to Win98) is considerable blinking of the last line in the
receiving window but it is possible to get accustomed to it...
May be the problem is in the AWE drivers, I get it from WWW...
73 - Giedrius, LY2CG
>Hi all
>When launching MT63, Win2K tells me "audio device not found".
>Probably due to incomplete AWE64 driver supplied with Win2K,
>although system sounds etc are working fine.
>Anybody successfully running Nino's MT63 soft under Win2K?
>If so, please post what sound card you are using. Tnx!
>
73, Markus HB9BRJ
------------------------------------------------------------------------
GET A NEXTCARD VISA, in 30 seconds! Get rates as low as 0.0%
Intro or 9.9% Fixed APR and no hidden fees. Apply NOW!
http://click.egroups.com/1/937/2/_/524264/_/952502568/
------------------------------------------------------------------------
<< Have you tried DX PSK-Hell yet? >>
<< Visit http://www.qsl.net/zl1bpu >>
- The MT63 Reflector -
MT63@onelist.com
(To unsubscribe. send email to
MT63-unsubscribe@onelist.com)
Bruce and all,
From the beginning of the avilability of the PC version of MT63, except
for a few very early QSOs on 14.347, and upon a closer reading of
pertinent parts of Part 97 of the FCC regulations (excertps posted
erlier on the reflector), MT63ers in the USA clearly agree that we
belong in what the FCC calls the "CW and Data" portion of 20 meters. I
won't go into some of the other conventions that have come into use in
the US below 14.150, but the area of 14.060-090 or so is populated with
signals of bandwidth below about 500 Hz. The area where we've settled
with Hellschreiber (~14.060-065 or so) is also a prime hangout for CW
QRP operation. Reasonable power Hellschreiber coexists well in this
area.
Because much MT63 operation is (starts, at least) with the 1 kHz
sub-mode we agreed from the outset that we would be good Amateur Radio
citizens and operate in the area above 14.110 (to about 14.114). (Some
European operation still remains around 14.347.) The need to minimize
QRM to other modes has been well discussed on this reflector each time
the subject arises. As it is, there has been significant criticism that
a wideband mode such as MT63 would cause havoc on the bands if it
proliferates. While MT63 itself is reasonably interference resistant it
can cause serious QRM to other modes. Thus the desire to continue our
MT63 experiments in an area where we can peacefully coexist with other
modes, most of which we ourselves also operate.
The ability that Nino IZ8BLY has placed in both his Hellschreiber and
MT63 programs to quickly switch between them can encourage operation of
both modes in the same frequency area, but on 20 meters this is NOT a
good idea.
There is, of course, the other advantage of having already established a
"calling frequency" area of sorts for MT63 (as we have for
Hellschreiber) so we 63ers know where to call and expect tht we'll be
heard and recognized, and this is around 14.112 +/-, on exact 1 kHz
multiples.
Let's not give MT63 a REAL bad name by operating MT63 in the area of
14.063 +/-, ignoring the convention we've established, and keep it above
14.110 where we've agreed to operate. We certainly don't want to be PUT
somewhere because of a rash of QRM complaints!
As new MT63 ops come on board they obviously don't know what's gone on
before, but it is the responbility of EACH of us to help them learn the
conventions and operating techniques.
73 and see you all on the digital modes.
John Hirth W2KI
I suspect that the 1 kHz bandwidth FCC regulation is an historical artefact.
Many many years ago, some HAMS were running RTTY with a wide shift (e.g. 850
Hz shift).
Yes, using RTTY with a wide shift is more robust than using RTTY with 170
Hz. But today, wide shift RTTY is STRONGLY discouraged especially on the
crowded 20 meter digital sub-band between 14.060 and 14.095 (even though
wide shift RTTY is still legal in the USA and other countries!). Almost all
the RTTY operation today is 170 Hz or 200 Hz.
I think we can draw parallels between MT63 and RTTY. Yes, 1 kHz MT63 is
more robust than 500 Hz MT63. But should we encourage 1 KHz MT63 on the
crowded 20 meter digital sub-band? We don't encourage wide shift RTTY, why
should we encourage 1 KHz MT63 in the crowded 20 meter digital subband? In
my view, we should encourage only narrow bandwidth modes (like 170 Hz RTTY,
PSK31 and MT63's 500 Hz mode) on the crowded 20 meter digital sub-band
(i.e. between 14.060 and 14.095 MHz)
Similarly, we don't encourage other wide band digital modes, like 1200 baud
packet, on the HF bands (except 10 meters) even though it is perfectly legal
to use 1200 baud packet in many countries around the world on ALL of the HF
bands. (I believe the US is the exception where it is only legal to run
1200 baud packet on one HF band -- 10 meters).
I agree with Hamish that in accordance with the SPIRIT of the rules and
regulations and in accordance with ESTABLISHED PRACTICE on the HF digital
sub-bands ONLY narrow bandwidth digital modes (like 170 Hz RTTY, 500 Hz MT63
etc) should be encouraged and used on the crowded digital HF sub-bands
(notwithstanding that it may be legal to use 1 KHz MT63 in the US and other
countries).
For North American operators, 14.112 MHz and 14.114 MHz have been pretty
good lately for MT63. But what it really needed is some spectrum set aside
EXCLUSIVELY for wide bandwidth digital modes. Perhaps, this is a pipe
dream - hi
73's
Rob
VA2FB
>From: Hamish Moffatt <hamish@...>
>Reply-To: MT63@onelist.com
>To: MT63@onelist.com
>Subject: Re: [MT63] Re: [Hellschreiber] mt63 on 14.062
>Date: Wed, 8 Mar 2000 18:47:39 +1100
>
>Bruce,
>
>On Tue, Mar 07, 2000 at 09:06:10PM -0600, Bruce wrote:
> > From: "Bruce" <ko5t@...>
> >
> > Hamish,
> > Reply to yours of 3:13,
> > 1) The FCC space limit is 1000 hz for all data
> > modes,
>
>Really, that is news to me? Everybody on this list indicated
>that MT63 was too wide for the data segment. Actually, with CW ID
>on the bottom edge of the signal it is wider than 1kHz.
>
>You should also consider the spirit of the rules and the band plan --
>MT63 is not compatible with Hell and QRP CW on the same part of the band.
>MT63 will just wipe those out.
>
>Really, there is no need to operate MT63 on 14.06x. There are other
>locations which are fine. 14.080-14.112 somewhere. It's just poor
>operating.
>
>Hamish vk3sb
Hi all,
I have uploaded newqpsk-0.0.3.tar.gz to hes.iki.fi. There is nothing very
special but a nasty bug that probably affected all OSS/Lite users should
be gone.
From ChangeLog:
2000-03-07 Tomi Manninen <tpm@...>
* Version 0.0.3
* The modem should now work with the standard kernel sound
drivers as well (I use ALSA drivers...)
* Added BCH(15,7) error correction code. See the supplied
soundmodem.conf sample file for details. (The code is from
Charles Brain G4GUO, I hope he doesn't mind...)
* Minor changes in the documentation
--
Tomi Manninen Internet: oh2bns@...
OH2BNS AX.25: oh2bns@...
KP20ME04 Amprnet: oh2bns@...
Hi Giedrius
Thanks for positive reply! Do you remember where you got your
Win2k AWE64 drivers from? At Creative there's nothing available yet.
73, Markus HB9BRJ
--- In MT63@onelist.com, "Giedrius Misiunas" <ly2cg@t...> wrote:
> May be the problem is in the AWE drivers, I get it from WWW...
> 73 - Giedrius, LY2CG
Send Email
