On Sat, Aug 07, 1999 at 05:42:58PM +0100, Riley Williams wrote:
>
> > Sound can be disabled by using 0 as tone frequency (e.g.
> > cwkeyset 0 100)
>
> I have to admit that there are times when I'm using the PC to record
> something, with the recording software playing what it's recording
> over the PC's speaker so I can monitor it for anything odd, and I'm
> using morse separately with my transceiver providing the sidetone. Is
> this compatible with doing the above ???
>
When you enter 0 frequency driver goes to mute state and does nothing
with PC speaker output, so I guess it will work ok with your software
playing on speaker.
> >> 2. Output either straight keying or tone encoded. Whilst HF
> >> tends to use direct keying of the transmitter, VHF and
> >> above tends to use a tone that is modulated by the keying
> >> signal, being 0 Hz for off and anywhere between 600-1500
> >> Hz when on. The PTT is thus keyed for the entire message.
>
> > I can make an option for PTT but from where should come the
> > sound? From PC speaker - requires hardware intervention (read:
> > soldering wires inside PC) or from sound blaster - requires some
> > more learning :-))
>
> To give an example of my preferred option using the parallel port, I
> would designate D0 as PTT and D1 as Audio In. Presumably something
> similar could be done with the serial port ???
>
If you are satisfied by quality of sound that can be generated by switching
state from 0 to 5V (on parallel port and PC speaker) or -12 to +12V on
serial port, than it can be done in both cases.
If you are thinking about MS (Meteor Scatter) work when saying that
"...VHF and above tends to use a tone that is modulated by the keying
signal..." you are right. Because speed of CW key input is somewhat limited
on transmiters few of them could reach speeds used on MS nowdays, but I am not
sure would quality of this "switching generated" tone be OK for this
purpose. My oppinion is that it would be much better to use sound blaster
or perhaps some very low cost custom made external device.
BTW when refering to "Audio In" do you mean Audio out from PC and Audio in
into transciever ?! , or I have understood something completly wrong?
Sorry, but english is not my native language.
> >> 3. Choice of port to use. From the description, you've used
> >> a specific serial port for the morse output, but that is
> >> probably less than optimal.
>
> > At the moment you can (or you should be able to) use COM1 or
> > COM2 for keying. It is done by "make cwup1" for COM1 and "make
> > cwup2" for COM2.
>
> So if I need to change the port, I have to recompile? I would much
> prefer a command-line option. In fact, the attachen manpage describes
> the interface I would like to see...
>
Maybe my solution is somehow missleading. You *DON'T* have to recompile,
it is just matter of parameter definition while loading driver. As it
can be seen in Makefile "make cwup1" does following :
setserial /dev/ttyS0 uart none
insmod cwkeyer.o iobase=0x3f8 irq=4
and "make cwup2" :
setserial /dev/ttyS1 uart none
insmod cwkeyer.o iobase=0x2f8 irq=3
As you see, it doesn't compile anything. I have used make as an easy way to
do all and to avoid numerous programs to do this and that, but maybe it
would be better to do exactly that, create shell scripts, create configuration
files,.... and simplicity would be lost. But hey, I wanted to hear from you.
Something that is normal or easy for me doesn't have to be the same for others
and that's why your feedback is so important to me.
GL , HPE CUAGN
Ivo.
