This is a multi-part message in MIME format.
------=_NextPart_000_0087_01C18F0F.721DEDD0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Also using a Pro2 here. No problems at all. CT-17 converter, W5XD =
keyer, ver 10.29. Settings 4800 baud, poll=3Dyes, Comm PTT=3DYES. Make =
sure that the radio CI-V address is 5Ch. This is not the PRO2 default. =
BTW, I find 4800 baud with a poll interval of 1000 ms to work well. =
Faster poll or baud rates seem to interfere with Ant <-> ANt/R =
switching. Seems like the rate of rig to computer interaction affects =
toggle speed of this feature (e.g., you have to push the button several =
times to make it work at faster speeds). A poll interval of 1000 ms =
doesn't slow down my run rate HI.
73,=20
Bob=20
bob@n6rfm.com
http://www.n6rfm.com
----- Original Message -----=20
From: Matt Burke=20
To: Writelog@Contesting. Com ; Ben Grokett=20
Sent: Thursday, December 27, 2001 17:41
Subject: RE: [WriteLog] more 756 Pro II
I am using a PRO2 and Writelog with no problems. I changed the CIV =
address of my PRO2 to the default for the PRO and set the rig comm to =
the PRO in the Port setup of Writelog. It has worked fine in that =
configuration for several contests now. I am using a homebrew lever =
converter. I have been able to jump to packet spots, jump to a freq in =
the bandmap, and Writelog has been successful in getting the freq data =
when logging. Everything is working the same as it did when I was using =
my previous rig (TS-930).
73,
Matt Burke - N5KR
-----Original Message-----
From: writelog-admin@contesting.com =
[mailto:writelog-admin@contesting.com]On Behalf Of Ben Grokett
Sent: Thursday, December 27, 2001 10:52
To: writelog@contesting.com
Subject: [WriteLog] more 756 Pro II
After checking out the CT-17 level convertor and finding it to be =
ok.... and see polling signals coming from the assigned com port from =
Writelog.... I called Icom (several days ago).
The tech service person I spoke with at Icom said that the 756 =
Pro II uses a different data format than the 756 Pro and this format is =
also different from the 756. At this point it appears that Writelog =
will require a "rig" update before it can properly address the 756 Pro =
Mark II. I was able to properly send and receive data from the radio =
when using a dumb program.
I will copy the appropriate data from the user manual of the Pro =
II and send it along to Ron (DJ) in hope that at some point in the =
future if/when Wayne has the time he will be able to provide a rig =
driver for the Pro II in Writelog. I don't know what the data format =
differences are between the Pro and Pro II are but I suspect they are =
relatively minor and will therefore be relatively easy to modify from =
the 756 Pro driver that is presently included in Writelog.
Thanks to all who provided suggestions/comments about this =
problem.
73 Ben, KR6E
kr6e@thevine.net
------=_NextPart_000_0087_01C18F0F.721DEDD0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Also using a Pro2 here. No problems at all. =
CT-17=20
converter, W5XD keyer, ver 10.29. Settings 4800 baud, poll=3Dyes, =
Comm=20
PTT=3DYES. Make sure that the radio CI-V address is 5Ch. =
This is not=20
the PRO2 default. BTW, I find 4800 baud with a poll interval of =
1000 ms to=20
work well. Faster poll or baud rates seem to interfere with Ant =
<->=20
ANt/R switching. Seems like the rate of rig to computer =
interaction=20
affects toggle speed of this feature (e.g., you have to push the button =
several=20
times to make it work at faster speeds). A poll interval of 1000 =
ms=20
doesn't slow down my run rate HI.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>73, </FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV>Bob </DIV>
<DIV><A href=3D"mailto:bob@n6rfm.com";>bob@n6rfm.com</A><BR><A=20
href=3D"http://www.n6rfm.com";>http://www.n6rfm.com</A><BR></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Ddallasdawg@earthlink.net =
href=3D"mailto:dallasdawg@earthlink.net";>Matt=20
Burke</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3Dwritelog@contesting.com=20
href=3D"mailto:Writelog@Contesting. Com">Writelog@Contesting. Com</A> =
; <A=20
title=3Dkr6e@thevine.net href=3D"mailto:kr6e@thevine.net";>Ben =
Grokett</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, December 27, =
2001=20
17:41</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> RE: [WriteLog] more =
756 Pro=20
II</DIV>
<DIV><BR></DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial =
color=3D#0000ff size=3D2>I am=20
using a PRO2 and Writelog with no problems. I changed the CIV =
address of=20
my PRO2 to the default for the PRO and set the rig comm to the PRO in =
the Port=20
setup of Writelog. It has worked fine in that configuration =
for=20
several contests now. I am using a homebrew lever =
converter. I=20
have been able to jump to packet spots, jump to a freq in the bandmap, =
and=20
Writelog has been successful in getting the freq data when =
logging. =20
Everything is working the same as it did when I was using my previous =
rig=20
(TS-930).</FONT></SPAN></DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>73,</FONT></SPAN></DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial =
color=3D#0000ff size=3D2>Matt=20
Burke - N5KR</FONT></SPAN></DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B>=20
writelog-admin@contesting.com =
[mailto:writelog-admin@contesting.com]<B>On=20
Behalf Of </B>Ben Grokett<BR><B>Sent:</B> Thursday, December 27, =
2001=20
10:52<BR><B>To:</B> writelog@contesting.com<BR><B>Subject:</B> =
[WriteLog]=20
more 756 Pro II<BR><BR></FONT></DIV>
<DIV><FONT size=3D2>After checking out the CT-17 level convertor and =
finding=20
it to be ok.... and see polling signals coming from the assigned com =
port=20
from Writelog.... I called Icom (several days ago).</FONT></DIV>
<DIV><FONT size=3D2> The tech service person I =
spoke with at=20
Icom said that the 756 Pro II uses a different data format than the =
756 Pro=20
and this format is also different from the 756. At this point =
it=20
appears that Writelog will require a "rig" update before it can =
properly=20
address the 756 Pro Mark II. I was able to properly send and =
receive=20
data from the radio when using a dumb program.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2> I will copy the appropriate =
data from=20
the user manual of the Pro II and send it along to Ron (DJ) in hope =
that at=20
some point in the future if/when Wayne has the time he will be able =
to=20
provide a rig driver for the Pro II in Writelog. I don't know =
what the=20
data format differences are between the Pro and Pro II are but I =
suspect=20
they are relatively minor and will therefore be relatively easy to =
modify=20
from the 756 Pro driver that is presently included in =
Writelog.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2> Thanks to all who provided=20
suggestions/comments about this problem.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>73 Ben, KR6E</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2><A=20
href=3D"mailto:kr6e@thevine.net";>kr6e@thevine.net</A></FONT></DIV>
<DIV> </DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0087_01C18F0F.721DEDD0--
|