This is a multi-part message in MIME format.
------=_NextPart_000_0060_01C18EF5.545CE3B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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_0060_01C18EF5.545CE3B0
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 5.50.4522.1800" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<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 have=20
been able to jump to packet spots, jump to a freq in the bandmap, and =
Writelog=20
has been successful in getting the freq data when logging. =
Everything is=20
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 =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial color=3D#0000ff =
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial color=3D#0000ff =
size=3D2>73,</FONT></SPAN></DIV>
<DIV><SPAN class=3D811143322-27122001><FONT face=3DArial color=3D#0000ff =
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 =
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] more=20
756 Pro II<BR><BR></FONT></DIV>
<DIV><FONT size=3D2>After checking out the CT-17 level convertor and =
finding it=20
to be ok.... and see polling signals coming from the assigned com port =
from=20
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 =
appears=20
that Writelog will require a "rig" update before it can properly =
address the=20
756 Pro Mark II. I was able to properly send and receive data =
from the=20
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 the=20
user manual of the Pro II and send it along to Ron (DJ) in hope that =
at some=20
point in the future if/when Wayne has the time he will be able to =
provide a=20
rig driver for the Pro II in Writelog. I don't know what the =
data format=20
differences are between the Pro and Pro II are but I suspect they are=20
relatively minor and will therefore be relatively easy to modify from =
the 756=20
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></BODY></HTML>
------=_NextPart_000_0060_01C18EF5.545CE3B0--
|