Crap, I just re-read this and you said you didn't get the com working
through the rig. Hummm.. Ok, you said you had rig control set to 64h in
mmtty.. Was that writelog? Disable computer rig control in mmtty, don't
want that! Could be the issue. Rig control is ONLY in the setup/ports of
Writelog. A note here. Now I've got a pro2 and a pro3, but I changed the
hex address on the 3 to 64 h and selected the pro2. Go into the rig menu,
set the baud rate for 9600, not auto. Set the Writelog program for 9600, no
higher and not auto.
I learned a couple of things about the rig control. The pro2 and pro3,
although they can be set for auto baud, are not very good at "renegotiating"
their speed. In a greed rush, I set Writelog for 19200, and it would work
just fine. However, if I exited writelog and got into either Dxkeeper OR
ACLog (my old logging program), rig control would not function until I
turned off the rig and turned it back on. This forced it back into the
autobaud routine or whatever its called, and it would work fine. I could
exit DXKeeper, get into wl and it still worked fine. Get out of wl and back
into dxk, and nothing. Setting the rig to 1 baud rate and sticking with it,
and then setting all of the other programs to the same speed, cleared that
problem right up.
The other note is that Don sent me an email asking about how I got comptt to
work with an Icom. I just turned it on. It works, does in my Pro2 and my
Pro3. The command is in the command set, so I guess it's always worked.
There's also a RIT clear command, but its kinda hazy as to what it may or
may not do. Wayne may have a better undertanding of it, but Command 1A Sub
Command 0565 states that its "Send/read quick RIT/(delta)TX clear function
(0=off, 1=on)" I don't know if this means there's a RIT clear command in
the icom or not, but sounds like it. If this is true, I'd sure like this to
be added to the rig control command set for the Pro2 and Pro3 so that we can
use it just like we did on the Kenwoods and Yaesus.
Charlie
KI5XP
> -----Original Message-----
> From: Ian [mailto:ik7565@verizon.net]
> Sent: Tuesday, January 10, 2006 7:40 PM
> To: cfmorris@bellsouth.net; rtty@contesting.com
> Subject: RE: 756p2, rigblaster pro, mmtty
>
> Charlie - thanks for all the hints here! I set jumper P16 to
> diagram #4 and ran my COM2 (my one real serial port) to the
> RBPro's Serial A. PTT is set to 'COM2' and Radio Command is
> set to 'None' in MMTTY. I am keying the rig now FSK! Both
> PTT and CW lights are on steady and the FSK light shows
> keying. Some issues remain though. My other com port on my
> laptop is a USB-Serial Converter that sets up as COM5 - this
> goes to the RBPro Serial B.
> MMTTY is very slow to transition from TX to RX after a macro
> completes. I set the PTT timer to zero but didn't seem to
> help. Also set the Com-TXD/USB setting to other selections
> but nothing improved. The booklet for the USB-Serial device
> says that it does not support 'interrupt transfer mode' -
> maybe that's a problem. I also have a Belkin F5U103 serial
> adapter that is suppose to be fb for RTTY but it won't
> install on my Windows 2000 laptop - I get a 'function driver'
> error. I'm thinking about upgrading the OS to WinXP
> - maybe that will get the Belkin going. Anyhow I'm not
> reading the freq/mode from the 756P2 through COM5 in my
> logging program (Win-EQF) either
> - was fine via COM2. The CI-V address is set to 64h in MMTTY.
>
> 73, Ian N8IK
>
>
> -----Original Message-----
> From: Charles Morrison [mailto:cfmorris@bellsouth.net]
> Sent: Sunday, January 08, 2006 10:57 PM
> To: ik7565@verizon.net
> Subject: RE: 756p2, rigblaster pro, mmtty
>
> Ian,
>
> Did you set the RBPro J16 for the last selection on page 29
> of the manual?
> FSK/PTT/CW all on your onboard serial port, and Rig Control
> on the other.
>
> Notes about WL and MMTTY. The FSK port is the port you
> select in RittyWrite. PTT comes from whatever port you
> select in the PTT section of MMTTY. CW port can not be
> shared with the FSK/PTT port. You have to go into WL, and
> select the last selection, underneath all of the LPT1 ports,
> in the CW column (thus disabling CW on ALL ports) during rtty
> operation. If you want to do a CW contest, you simply go
> back in and enable the "dot" in
> the ROW of Comm2, under the CW column. Make sure Rig control is NOT
> sharing the port, make sure that CW is not sharing the port
> (and if it is, then you have to do as above, select the last
> dot underneath all of the lpt's, click ok, click setup, save
> configuration and EXIT the program completely. Then get back
> in and your RTTY should be fine.
>
> The problem arises if the CW port in Writelog is set to the
> same as the comport in RittyWrite/MMTTY. The second the Rtty
> windows open, you'll get an error and the port is locked
> until you exit. So, you just simply disable the port and you
> should be good.
>
> Email me back if you have any other issues. Worked with
> WW4LL on this the
> other night for about 4 hours and got it figured out. I
> also have a pro2
> and pro3, RBPro, and have all of the connections always
> connected to the rig. I switch back and forth from ssb to cw
> to rtty with just a few simple changes in WL.
>
> Charlie
> KI5XP
>
>
> > ------------------------------
> >
> > Message: 5
> > Date: Sat, 07 Jan 2006 09:50:57 -0500
> > From: "Ian" <ik7565@verizon.net>
> > Subject: [RTTY] 756p2, rigblaster pro, mmtty
> > To: <rtty@contesting.com>
> > Message-ID: <000c01c61399$c5c76160$6502a8c0@desktop>
> > Content-Type: text/plain; charset=us-ascii
> >
> > I have an IC-756Pro2 and a Rigblaster Pro and can't seem to
> transmit
> > FSK.
> > I'm pretty sure all the cabling is correct. Rig control
> through CI-V
> > is no problem. I can decode RTTY just fine in MMTTY on my laptop.
> > The laptop has
> > one serial and one USB port so I use a USB-serial converter
> that sets
> > up as
> > COM5 and use that on the Serial-A of the RBPro. The real
> serial port
> > (COM2) goes to the RBPro Serial-B for FSK control. Also
> have the WMR
> > cable that plugs into ACC1 and provides level audio and FSK control.
> > Been through the
> > MMTTY help and AA5AU's web site but I'm missing something.
> Any ideas?
> >
> > Many thanks & 73,
> > Ian N8IK
> >
> >
> >
> >
> >
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > RTTY mailing list
> > RTTY@contesting.com
> > http://lists.contesting.com/mailman/listinfo/rtty
> >
> >
> > End of RTTY Digest, Vol 37, Issue 11
> > ************************************
> >
>
>
>
>
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|