I have a old TS940S with the Piexx board with the DB9 connector coming out
of the board. I want to hook it up to my old computer that has a LPT port,
Can I use adapator to make this work. So I can have the RS232 going to the
computer. Has anyone done this in a while. Really dont want to buy another
FT1000 anything right now. thanks PTL bill brown K0UK
----- Original Message -----
From: <writelog-request@contesting.com>
To: <writelog@contesting.com>
Sent: Friday, March 11, 2005 10:00 AM
Subject: WriteLog Digest, Vol 27, Issue 14
> Send WriteLog mailing list submissions to
> writelog@contesting.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.contesting.com/mailman/listinfo/writelog
> or, via email, send a message with subject or body 'help' to
> writelog-request@contesting.com
>
> You can reach the person managing the list at
> writelog-owner@contesting.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WriteLog digest..."
>
>
> Today's Topics:
>
> 1. Re: Four serial port PCI Board $29 shipped (David Hachadorian)
> 2. Re: PTT problem with Icom 756proIII (Ron Stordahl)
> 3. Re: PTT problem with Icom 756proIII (Richard Zalewski)
> 4. Re: PTT problem with Icom 756proIII (Bob Lafont)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 10 Mar 2005 10:14:34 -0700
> From: "David Hachadorian" <K6LL@adelphia.net>
> Subject: Re: [WriteLog] Four serial port PCI Board $29 shipped
> To: <writelog@contesting.com>
> Message-ID: <005801c52594$a5bb9a10$0402a8c0@cyberpower>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
> reply-type=response
>
>
> ----- Original Message -----
> From: "Ron Stordahl" <ron.stordahl@digikey.com>
> To: "David Hachadorian" <K6LL@adelphia.net>
> Cc: <writelog@contesting.com>
> Sent: Thursday, March 10, 2005 7:01 AM
> Subject: Re: [WriteLog] Four serial port PCI Board $29 shipped
>
>
>> Did this boards software allow you to specify what COM ports it would
>> create?
>> For example, if your computer has 1 built in COM port (COM1), then it
>> would be
>> nice to create COM2,3,4 and 5 using this board. But it that is not
>> possible,
>> then perhaps 5,6,7,8.
>> One difficulty with some add in com boards is that they end up with very
>> unusual port numbers, often higher than typical application software will
>> support. I have seen this happen both with add in cards and with the USB
>> to
>> Serial adapter cables.
>> Often you can dig around and find a solution, but if the manfacturer is
>> considerate they will document how to resolve this issue.
>>
>> Does SYBA document a solution to this?
>>
>
>>From the driver installation instructions (with latest downloaded
>>drivers):
>
> "Some versions of Windows, and some drivers, will allow the user to change
> some
> of
> the settings for the new ports, while other versions will not. Things that
> might
> be
> able to be changed are: The port number (COM5>>COM2 for example)..."
>
> In my XP installation, I had com1 and com2 on the motherboard, and a modem
> on
> com3.
> The new ports were automatically assigned coms 4,5,6 and 7. In device
> manager/ports/
> properties/port settings/advanced, you can reassign the port assignment to
> any
> unused
> com port between com 1 and com 256. I reassigned com 7 temporarily to com
> 8, and
> the
> new assignment registered ok in device manager. I didn't test it.
>
>
> Dave Hachadorian, K6LL
> Yuma, AZ
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> .
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 10 Mar 2005 17:37:49 -0600
> From: Ron Stordahl <ron.stordahl@digikey.com>
> Subject: Re: [WriteLog] PTT problem with Icom 756proIII
> To: Marc Ressler <marc.ressler@verizon.net>
> Cc: writelog@contesting.com
> Message-ID: <4230DA4D.6080308@digikey.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Anyone know the default hex address (as from the factory) for the Pro III?
>
> Ron, N5IN
>
> Marc Ressler wrote:
>
>>Pete,
>>
>>There is a lockup problem on transmit related to trying to drive the icom
>>CI-V
>>interface for everything if you have an additional serial interface on
>>another comm port. I don't know which "PTT" you selected, but here is
>>something I have that works with both Logger32 (running PSK and MMTTY) and
>>Writelog. This requires TWO serial ports. One is dedicated to rig control,
>>and the other does PTT, CW, and supports FSK.
>>
>>My rig control is through a modified CT-17 that I added CW keying to (but
>>DO NOT use). The other port control is through a modified Buxcomm Rascal
>>that supports CW, PTT, FSK, and provides the audio interfacing for PSK,
>>RTTY, and computer Voice Keyer ops.
>>
>>To get this to work you must check the box "All mode PTT on CW port RTS".
>>If this box is not checked, and the interface is connected, the rig gets
>>keyed all the time. (DO NOT try to set the ports control to try and
>>support
>>two serial ports for the same rig - this will lock your rig into transmit
>>and the only thing that will stop it is powering down the rig and/or
>>restarting the computer). You can select CW PTT by command for the newer
>>Icom rigs. However, since the transmit and receive data line is shared,
>>the
>>most reliable way to make this work is to select SYNC under the CommPTT
>>box
>>for the rig. You will also find that performance will be much better if
>>you
>>go into the 756 "OTHERS" menu and set CI-V TRANSCEIVE to OFF (this is
>>wayyy down the list). NOTE: some programs (but NOT any of the ones
>>mentioned above) rely on CI-V TRANSCEIVE "ON" to work at all, and some
>>AUTO
>>speed sense programs use this as well. To get past the speed sensing
>>problem, set the rig and Writelog baudrates to 19200 (unless your computer
>>can keep up with that - then select a slower speed for both).
>>
>>The correct hex addresses for Icom 756 rigs are:
>>756 - 50
>>756 Pro - 5C
>>756 Pro II - 64
>>
>>There is no support for the Pro III yet, so one of these should do, but
>>the
>>best bet would be to use the Pro II, as the available features are most
>>likely to be compatible If you only have this working with hex 50, you may
>>be running an older version of the WriteLog (rig control info used to be
>>in
>>the INI file, it is now in a DLL - see the May 22 2002 for info on how
>>things were changed then to support the Pro II when it was new).
>>
>>
>>
>>
>>
>>>>Hi, I am new to this reflector so sorry if this has been asked before, I
>>>>have looked through the archives and not found it.
>>>>I have a 756 proIII I selected on the Ports 756proII ticked the PTT box,
>>>>
>>>>
>>>rig
>>>
>>>
>>>>control works fine showing frequency and mode, but the ptt puts the rig
>>>>
>>>>
>>>onto
>>>
>>>
>>>>transmit all the time. I have tried both DTR and RTS, RTS keeps the line
>>>>high even when WL is closed down.
>>>>I am using a 4n23 optoisolater and the set-up works fine with Logger and
>>>>MMTTY stand alone. BTW the rig will only talk to the computer when the
>>>>address on the rig is set to 50h, not other address that have been
>>>>quoted.
>>>>Also how do I make the rig key for FSK? once I get the ptt sorted.
>>>>Thanks
>>>>
>>>>
>>>in
>>>
>>>
>>>>anticipation, 73 Pete
>>>>
>>>>
>>
>>MarC, K3NCO
>>marc.ressler@verizon.net
>>_______________________________________________
>>WriteLog mailing list
>>WriteLog@contesting.com
>>http://lists.contesting.com/mailman/listinfo/writelog
>>WriteLog on the web: http://www.writelog.com/
>>
>>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 10 Mar 2005 16:59:24 -0700
> From: Richard Zalewski <dick.w7zr@gmail.com>
> Subject: Re: [WriteLog] PTT problem with Icom 756proIII
> To: ron.stordahl@digikey.com
> Cc: Marc Ressler <marc.ressler@verizon.net>, writelog@contesting.com
> Message-ID: <836fd22a0503101559122100a0@mail.gmail.com>
> Content-Type: text/plain; charset=US-ASCII
>
> 6e is the default address but I use 64 and use the pro II in setup.
>
> 73
> Dick W7ZR
>
>
> On Thu, 10 Mar 2005 17:37:49 -0600, Ron Stordahl
> <ron.stordahl@digikey.com> wrote:
>> Anyone know the default hex address (as from the factory) for the Pro
>> III?
>>
>> Ron, N5IN
>>
>> Marc Ressler wrote:
>>
>> >Pete,
>> >
>> >There is a lockup problem on transmit related to trying to drive the
>> >icom CI-V
>> >interface for everything if you have an additional serial interface on
>> >another comm port. I don't know which "PTT" you selected, but here is
>> >something I have that works with both Logger32 (running PSK and MMTTY)
>> >and
>> >Writelog. This requires TWO serial ports. One is dedicated to rig
>> >control,
>> >and the other does PTT, CW, and supports FSK.
>> >
>> >My rig control is through a modified CT-17 that I added CW keying to
>> >(but
>> >DO NOT use). The other port control is through a modified Buxcomm Rascal
>> >that supports CW, PTT, FSK, and provides the audio interfacing for PSK,
>> >RTTY, and computer Voice Keyer ops.
>> >
>> >To get this to work you must check the box "All mode PTT on CW port
>> >RTS".
>> >If this box is not checked, and the interface is connected, the rig gets
>> >keyed all the time. (DO NOT try to set the ports control to try and
>> >support
>> >two serial ports for the same rig - this will lock your rig into
>> >transmit
>> >and the only thing that will stop it is powering down the rig and/or
>> >restarting the computer). You can select CW PTT by command for the newer
>> >Icom rigs. However, since the transmit and receive data line is shared,
>> >the
>> >most reliable way to make this work is to select SYNC under the CommPTT
>> >box
>> >for the rig. You will also find that performance will be much better if
>> >you
>> >go into the 756 "OTHERS" menu and set CI-V TRANSCEIVE to OFF (this is
>> >wayyy down the list). NOTE: some programs (but NOT any of the ones
>> >mentioned above) rely on CI-V TRANSCEIVE "ON" to work at all, and some
>> >AUTO
>> >speed sense programs use this as well. To get past the speed sensing
>> >problem, set the rig and Writelog baudrates to 19200 (unless your
>> >computer
>> >can keep up with that - then select a slower speed for both).
>> >
>> >The correct hex addresses for Icom 756 rigs are:
>> >756 - 50
>> >756 Pro - 5C
>> >756 Pro II - 64
>> >
>> >There is no support for the Pro III yet, so one of these should do, but
>> >the
>> >best bet would be to use the Pro II, as the available features are most
>> >likely to be compatible If you only have this working with hex 50, you
>> >may
>> >be running an older version of the WriteLog (rig control info used to be
>> >in
>> >the INI file, it is now in a DLL - see the May 22 2002 for info on how
>> >things were changed then to support the Pro II when it was new).
>> >
>> >
>> >
>> >
>> >
>> >>>Hi, I am new to this reflector so sorry if this has been asked before,
>> >>>I
>> >>>have looked through the archives and not found it.
>> >>>I have a 756 proIII I selected on the Ports 756proII ticked the PTT
>> >>>box,
>> >>>
>> >>>
>> >>rig
>> >>
>> >>
>> >>>control works fine showing frequency and mode, but the ptt puts the
>> >>>rig
>> >>>
>> >>>
>> >>onto
>> >>
>> >>
>> >>>transmit all the time. I have tried both DTR and RTS, RTS keeps the
>> >>>line
>> >>>high even when WL is closed down.
>> >>>I am using a 4n23 optoisolater and the set-up works fine with Logger
>> >>>and
>> >>>MMTTY stand alone. BTW the rig will only talk to the computer when the
>> >>>address on the rig is set to 50h, not other address that have been
>> >>>quoted.
>> >>>Also how do I make the rig key for FSK? once I get the ptt sorted.
>> >>>Thanks
>> >>>
>> >>>
>> >>in
>> >>
>> >>
>> >>>anticipation, 73 Pete
>> >>>
>> >>>
>> >
>> >MarC, K3NCO
>> >marc.ressler@verizon.net
>> >_______________________________________________
>> >WriteLog mailing list
>> >WriteLog@contesting.com
>> >http://lists.contesting.com/mailman/listinfo/writelog
>> >WriteLog on the web: http://www.writelog.com/
>> >
>> >
>> _______________________________________________
>> WriteLog mailing list
>> WriteLog@contesting.com
>> http://lists.contesting.com/mailman/listinfo/writelog
>> WriteLog on the web: http://www.writelog.com/
>>
>
>
> --
> Tnx es 73
> Dick W7ZR
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 10 Mar 2005 18:29:53 -0600
> From: "Bob Lafont" <blafont@frontiernet.net>
> Subject: Re: [WriteLog] PTT problem with Icom 756proIII
> To: <ron.stordahl@digikey.com>, "'Marc Ressler'"
> <marc.ressler@verizon.net>
> Cc: writelog@contesting.com
> Message-ID: <001301c525d1$72be64c0$6601a8c0@bob>
> Content-Type: text/plain; charset="us-ascii"
>
> Ron,
>
> The Pro III CI-V default hex address is 6eh.
>
> I don't have the Pro but thought I'd check around for you and found that
> there is an online manual out there now. Let me know if you would like me
> to
> send it to you.
>
> 73-Bob
> WA2MNO
>
>
> -----Original Message-----
> From: writelog-bounces@contesting.com
> [mailto:writelog-bounces@contesting.com] On Behalf Of Ron Stordahl
> Sent: Thursday, March 10, 2005 5:38 PM
> To: Marc Ressler
> Cc: writelog@contesting.com
> Subject: Re: [WriteLog] PTT problem with Icom 756proIII
>
>
> Anyone know the default hex address (as from the factory) for the Pro III?
>
> Ron, N5IN
>
> Marc Ressler wrote:
>
>>Pete,
>>
>>There is a lockup problem on transmit related to trying to drive the
>>icom CI-V interface for everything if you have an additional serial
>>interface on another comm port. I don't know which "PTT" you selected,
>>but here is something I have that works with both Logger32 (running PSK
>>and MMTTY) and Writelog. This requires TWO serial ports. One is
>>dedicated to rig control, and the other does PTT, CW, and supports FSK.
>>
>>My rig control is through a modified CT-17 that I added CW keying to
>>(but
>>DO NOT use). The other port control is through a modified Buxcomm Rascal
>>that supports CW, PTT, FSK, and provides the audio interfacing for PSK,
>>RTTY, and computer Voice Keyer ops.
>>
>>To get this to work you must check the box "All mode PTT on CW port
>>RTS".
>>If this box is not checked, and the interface is connected, the rig gets
>>keyed all the time. (DO NOT try to set the ports control to try and
>>support
>
>>two serial ports for the same rig - this will lock your rig into transmit
>>and the only thing that will stop it is powering down the rig and/or
>>restarting the computer). You can select CW PTT by command for the newer
>>Icom rigs. However, since the transmit and receive data line is shared,
>>the
>
>>most reliable way to make this work is to select SYNC under the CommPTT
>>box
>
>>for the rig. You will also find that performance will be much better if
>>you
>
>>go into the 756 "OTHERS" menu and set CI-V TRANSCEIVE to OFF (this is
>>wayyy down the list). NOTE: some programs (but NOT any of the ones
>>mentioned above) rely on CI-V TRANSCEIVE "ON" to work at all, and some
>>AUTO
>
>>speed sense programs use this as well. To get past the speed sensing
>>problem, set the rig and Writelog baudrates to 19200 (unless your computer
>>can keep up with that - then select a slower speed for both).
>>
>>The correct hex addresses for Icom 756 rigs are:
>>756 - 50
>>756 Pro - 5C
>>756 Pro II - 64
>>
>>There is no support for the Pro III yet, so one of these should do, but
>>the
>>best bet would be to use the Pro II, as the available features are most
>>likely to be compatible If you only have this working with hex 50, you may
>>be running an older version of the WriteLog (rig control info used to be
>>in
>
>>the INI file, it is now in a DLL - see the May 22 2002 for info on how
>>things were changed then to support the Pro II when it was new).
>>
>>
>>
>>
>>
>>>>Hi, I am new to this reflector so sorry if this has been asked
>>>>before, I have looked through the archives and not found it. I have a
>>>>756 proIII I selected on the Ports 756proII ticked the PTT box,
>>>>
>>>>
>>>rig
>>>
>>>
>>>>control works fine showing frequency and mode, but the ptt puts the
>>>>rig
>>>>
>>>>
>>>onto
>>>
>>>
>>>>transmit all the time. I have tried both DTR and RTS, RTS keeps the
>>>>line high even when WL is closed down. I am using a 4n23 optoisolater
>>>>and the set-up works fine with Logger and MMTTY stand alone. BTW the
>>>>rig will only talk to the computer when the address on the rig is set
>>>>to 50h, not other address that have been quoted. Also how do I make
>>>>the rig key for FSK? once I get the ptt sorted. Thanks
>>>>
>>>>
>>>in
>>>
>>>
>>>>anticipation, 73 Pete
>>>>
>>>>
>>
>>MarC, K3NCO
>>marc.ressler@verizon.net
>>_______________________________________________
>>WriteLog mailing list
>>WriteLog@contesting.com
>>http://lists.contesting.com/mailman/listinfo/writelog
>>WriteLog on the web: http://www.writelog.com/
>>
>>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web: http://www.writelog.com/
>
>
>
> ------------------------------
>
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
>
>
> End of WriteLog Digest, Vol 27, Issue 14
> ****************************************
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|