开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
Date

Re: Yaesu FT-2000

 

Rich - that is very kind and once the grey cells have digested the
most important points, I think I shall have a go. Problem is that I
never dealt with such syntax as - lazy me - I always used what was at
hand without giving it other thoughts.
If I get to any useful result I shall publish them here (but I guess
it will take its time, hihi...)
Thanks again
vy 73 Fred DL6XAZ



--- In win-fldigi@..., "rich" <richwa4sxz@...> wrote:


I have uploaded the explanation of the rig.xml to the files section
of
this group. I hope it will be enough to get you started. Remember
to
change the com port designation and baud rate to match your set up
when working with existing xml files of similar equipment. Most of
these were originated and tested on Linux but should be fine.

Rich
WA4SXZ

--- In win-fldigi@..., "Fred" <dl6xaz@> wrote:

Hi friends -
I must say: fldigi works a charm on my (radio-exclusive) AMD pc
with W-
XP SP3 through navigator interface with a FT-897. No problems
whichoever. Installed it, fiddled around a bit, discovered which
settings it needed, and it is in daily use now.
My question is: has anybody heard about the FT-2000.xml being
written
or published by someone else? The problem is not that fldigi
would not
work with it. To the contrary, also here through the navigator
and TTY-
PTT it is usable, though without the additional QRG-indication
etc.
When trying e.g. the FT-1000.xml the result was nonsense and
fldigi
said "byebye". I had to manually edit the fldigi.prefs to get rid
of
entries I did not want.
I looked into the CAT-handbook for the FT-2000 with all required
syntax
but got no clue how those xml files are construed. Therefore I
would
welcome any hint.
73 Fred DL6XAZ


Re: Save Config problem

 

Hi Fred


Well one important thing not to overlook is that there is not another
instance of cygwin1.dll residing on the drive. It is also important
to re initialise the ports after any changes. Not sure if then it is
neccesary to come out of the software after saving, and then re
run it, but that's what I have done.

The rigcat functions appear to be limited, as I think Hamlib may be.
In that they only seem to operate cat frequency functions, and a ptt
string I guess where that is required. I am no software developer
as you know, but the cat capability should have the ability to be
able to carry out other functions. Like being able to select the
radio's bandwidth filters irrespective of mode. But then that would
be useful if it could be addressed by a macro etc. I haven't found
a method for example of being able to switch from the ssb filter to
my cw filter within rigcat, and all this may be down to my understanding
of how it should work. I played with trying to insert the string into my
rigcat file but it didn't work :-).

Hey I am not complaining hi, the work already done with fldigi is great,
and if I had the skills to assist inworking with the code I would do.
Despite the limitations I really enjoy using fldigi. I did have a lockup
problem earlier in my playing, and what I did was to remove all the
config files, and allow the new version to rewrite them.
This isn't accepted as a neccesity I am told, but in my case it resolved
the problem.

Just a few thoughts :-)

Cheers

Dave

On 24/09/2008 17:11:58, Fred (dl6xaz@...) wrote:
Hi friends, -
my mate G0UZP Paul who is also keen on using fldigi as a future
substitute to MixW, alerted me to a problem he encounters on his W-XP
laptop. He expressly asked me to publish his query here (previously
he had asked the same question on the navigator group without
response):
quote
1b. Re: Fldigi & Navigator
Posted by: "paul_g0uzp" g0uzpham@... paul_g0uzp
Date: Fri Sep 19, 2008 2:00 pm ((PDT))

Hi all,
I have also experienced problems with fldigi ver3.03.
I installed it to my laptop winxp sp2 etc etc.
Everything seemed ok, got the rig cat working FT857D.
Did a test and after a few minutes fldigi locked up in a major way.
Did a reboot, again it worked ok then locked up.
On the third attempt, I noticed at the bottom of the screen it came
up
with I/O error. That only came up when I got the cat working...It was


Re: Yaesu FT-2000

rich
 

I have uploaded the explanation of the rig.xml to the files section of
this group. I hope it will be enough to get you started. Remember to
change the com port designation and baud rate to match your set up
when working with existing xml files of similar equipment. Most of
these were originated and tested on Linux but should be fine.

Rich
WA4SXZ

--- In win-fldigi@..., "Fred" <dl6xaz@...> wrote:

Hi friends -
I must say: fldigi works a charm on my (radio-exclusive) AMD pc with W-
XP SP3 through navigator interface with a FT-897. No problems
whichoever. Installed it, fiddled around a bit, discovered which
settings it needed, and it is in daily use now.
My question is: has anybody heard about the FT-2000.xml being written
or published by someone else? The problem is not that fldigi would not
work with it. To the contrary, also here through the navigator and TTY-
PTT it is usable, though without the additional QRG-indication etc.
When trying e.g. the FT-1000.xml the result was nonsense and fldigi
said "byebye". I had to manually edit the fldigi.prefs to get rid of
entries I did not want.
I looked into the CAT-handbook for the FT-2000 with all required syntax
but got no clue how those xml files are construed. Therefore I would
welcome any hint.
73 Fred DL6XAZ


Save Config problem

 

Hi friends, -
my mate G0UZP Paul who is also keen on using fldigi as a future
substitute to MixW, alerted me to a problem he encounters on his W-XP
laptop. He expressly asked me to publish his query here (previously
he had asked the same question on the navigator group without
response):
quote
1b. Re: Fldigi & Navigator
Posted by: "paul_g0uzp" g0uzpham@... paul_g0uzp
Date: Fri Sep 19, 2008 2:00 pm ((PDT))

Hi all,
I have also experienced problems with fldigi ver3.03.
I installed it to my laptop winxp sp2 etc etc.
Everything seemed ok, got the rig cat working FT857D.
Did a test and after a few minutes fldigi locked up in a major way.
Did a reboot, again it worked ok then locked up.
On the third attempt, I noticed at the bottom of the screen it came
up
with I/O error. That only came up when I got the cat working...It was
then I noticed that if I tried to alter anything in the configure
menu
of fldigi, the lock up happened.
This baffled me as it works perfectly in HRD/DM780. Then I tried
Mixw,
again all ok. It is only used for radio stuff now.
Laptop is a fujitsu-siemens amillio M series. Intel 1.8ghz 1 meg ram.

As the laptop had not been cleaned for over 4 years.. ie: wiped I
decided to do that as there was a lot of stuff that might of made the
conflict.
I have fdisked and reintalled xp, the only software now on it now is
HRD/DM780 & fldigi ver 3.03xp.
I will say I have it on my main computer running vista and it works
perfectly. With no gliches..
Regards
Paul G?UZP

unquote

Does this problem ring a bell with someone?
vy73 Fred DL6XAZ


Yaesu FT-2000

 

Hi friends -
I must say: fldigi works a charm on my (radio-exclusive) AMD pc with W-
XP SP3 through navigator interface with a FT-897. No problems
whichoever. Installed it, fiddled around a bit, discovered which
settings it needed, and it is in daily use now.
My question is: has anybody heard about the FT-2000.xml being written
or published by someone else? The problem is not that fldigi would not
work with it. To the contrary, also here through the navigator and TTY-
PTT it is usable, though without the additional QRG-indication etc.
When trying e.g. the FT-1000.xml the result was nonsense and fldigi
said "byebye". I had to manually edit the fldigi.prefs to get rid of
entries I did not want.
I looked into the CAT-handbook for the FT-2000 with all required syntax
but got no clue how those xml files are construed. Therefore I would
welcome any hint.
73 Fred DL6XAZ


Re: Using <ZDT> a in macro

w1ret
 

Thanks Dave.

I may have something set incorrectly here but I haven't found it. So
don't rule that out either!

Jim
--- In win-fldigi@..., w1hkj <w1hkj@...> wrote:

The developers will check to see if the time code behaves
differently on
the different OS.

Dave


Re: Using <ZDT> a in macro

w1hkj
 

The developers will check to see if the time code behaves differently on the different OS.

Dave


Using <ZDT> a in macro

w1ret
 

When I use <ZDT> (Zulu date time) in my SK macro I get this for a
date/time..

09/23/08 00:43 EST de W1RET sk

I don't know where the EST is coming from other than that is the
time zone I am in although right now it is EDT. I would think it
would be GMT or UTC or Z. The time and date shown are correct zulu
time and dates.

If I change to <IZDT> (ZDT in iso-8601 format) I get this for a date/
time....

2008-09-23 00:46:42Z de W1RET sk

A bit long but it shows the time as Z and not EST. Again time and
dates are correct for zulu time.

I wonder if <ZDT> is picking the time zone from the local PC clock?

Any ideas?

Thanks,

Jim W1RET


Re: fldigi 303

 

Hi Jim, and guys

Well I decided to have a play and see what dxkeeper was all about.
Really an excersise to see if it would run okay with fldigi, and true
to form it worked first time.

Ran fldigi up, and dxkeeper, then ran the gateway, and hey presto it
asked for the log transfer :-). Now that has to be a result guys.

Don't ask me any questions about dxkeeper as I haven't even read the
docs yet hi.

Cheers

Dave G3VFP

--- In win-fldigi@..., "w1ret" <w1ret@...> wrote:

There is a gateway that you can use for fldigi and DXKeeper.

Browse over to You will find
it under Bridges, Gateways, and Extenders. It is listed as Fldigi-
DXKeeper Gateway.

I've tried it a couple of time and it seems to work. It will take
qso's as they are entered into the fldigi log an place them into
DXKeeper. There is also a read me file associated with it that tells
you the order in starting everything.

Hope this helps.

73,

Jim W1RET


--- In win-fldigi@..., Art <wb4mnk@> wrote:

Thanks Rich.

73,
Art

rich wrote:


1: configure-video-view xmit signal

2: Qsk on right channel can be used to key before and unkey after,
but direct cw keying is not possible at this point. (shape factor
is
a function of the audio envelope)

3: This ia an area that is being worked on by the developers, but
I
cannot answer (I don't know).

Rich
WA4SXZ

--- In win-fldigi@...
<mailto:win-fldigi%40yahoogroups.com>, "wb4mnk" <wb4mnk@> wrote:

I have three questions:

Can you keep the waterfall active during transmit ?
When transmitting CW can you use RTS to key the transmitter ? I
could
only get CW to transmit by using the sound card.
I use DXKeeper for my final log book and wanted to know if it
can be
set up as a real time log with fldigi 303 ?

I am using XP with a Dell 500hz computer with 768 megs of ram.

73,
Art
WB4MNK

------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG -
Version: 8.0.169 / Virus Database: 270.7.0/1681 - Release Date:
9/19/2008 3:54 PM


Re: fldigi 303

Art
 

Hi Jim,

The Gateway seems to do the job except for the frequency which I think Rick is working on. I do not use cat so I am going to wait till Rick gets the frequency working with out cat. Thanks for the help.

73,
Art

w1ret wrote:


There is a gateway that you can use for fldigi and DXKeeper.

Browse over to <> You will find
it under Bridges, Gateways, and Extenders. It is listed as Fldigi-
DXKeeper Gateway.

I've tried it a couple of time and it seems to work. It will take
qso's as they are entered into the fldigi log an place them into
DXKeeper. There is also a read me file associated with it that tells
you the order in starting everything.

Hope this helps.

73,

Jim W1RET

--- In win-fldigi@... <mailto:win-fldigi%40yahoogroups.com>, Art <wb4mnk@...> wrote:

Thanks Rich.

73,
Art

rich wrote:


1: configure-video-view xmit signal

2: Qsk on right channel can be used to key before and unkey after,
but direct cw keying is not possible at this point. (shape factor
is
a function of the audio envelope)

3: This ia an area that is being worked on by the developers, but
I
cannot answer (I don't know).

Rich
WA4SXZ

--- In win-fldigi@...
<mailto:win-fldigi%40yahoogroups.com>
<mailto:win-fldigi%40yahoogroups.com>, "wb4mnk" <wb4mnk@> wrote:

I have three questions:

Can you keep the waterfall active during transmit ?
When transmitting CW can you use RTS to key the transmitter ? I
could
only get CW to transmit by using the sound card.
I use DXKeeper for my final log book and wanted to know if it
can be
set up as a real time log with fldigi 303 ?

I am using XP with a Dell 500hz computer with 768 megs of ram.

73,
Art
WB4MNK

----------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - <>
Version: 8.0.169 / Virus Database: 270.7.0/1681 - Release Date:
9/19/2008 3:54 PM

------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - Version: 8.0.169 / Virus Database: 270.7.0/1681 - Release Date: 9/19/2008 3:54 PM


Re: fldigi 303

w1ret
 

There is a gateway that you can use for fldigi and DXKeeper.

Browse over to You will find
it under Bridges, Gateways, and Extenders. It is listed as Fldigi-
DXKeeper Gateway.

I've tried it a couple of time and it seems to work. It will take
qso's as they are entered into the fldigi log an place them into
DXKeeper. There is also a read me file associated with it that tells
you the order in starting everything.

Hope this helps.

73,

Jim W1RET


--- In win-fldigi@..., Art <wb4mnk@...> wrote:

Thanks Rich.

73,
Art

rich wrote:


1: configure-video-view xmit signal

2: Qsk on right channel can be used to key before and unkey after,
but direct cw keying is not possible at this point. (shape factor
is
a function of the audio envelope)

3: This ia an area that is being worked on by the developers, but
I
cannot answer (I don't know).

Rich
WA4SXZ

--- In win-fldigi@...
<mailto:win-fldigi%40yahoogroups.com>, "wb4mnk" <wb4mnk@> wrote:

I have three questions:

Can you keep the waterfall active during transmit ?
When transmitting CW can you use RTS to key the transmitter ? I
could
only get CW to transmit by using the sound card.
I use DXKeeper for my final log book and wanted to know if it
can be
set up as a real time log with fldigi 303 ?

I am using XP with a Dell 500hz computer with 768 megs of ram.

73,
Art
WB4MNK

------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG -
Version: 8.0.169 / Virus Database: 270.7.0/1681 - Release Date:
9/19/2008 3:54 PM


Re: fldigi 303

Art
 

Thanks Rich.

73,
Art

rich wrote:



1: configure-video-view xmit signal

2: Qsk on right channel can be used to key before and unkey after,
but direct cw keying is not possible at this point. (shape factor is
a function of the audio envelope)

3: This ia an area that is being worked on by the developers, but I
cannot answer (I don't know).

Rich
WA4SXZ

--- In win-fldigi@... <mailto:win-fldigi%40yahoogroups.com>, "wb4mnk" <wb4mnk@...> wrote:

I have three questions:

Can you keep the waterfall active during transmit ?
When transmitting CW can you use RTS to key the transmitter ? I could
only get CW to transmit by using the sound card.
I use DXKeeper for my final log book and wanted to know if it can be
set up as a real time log with fldigi 303 ?

I am using XP with a Dell 500hz computer with 768 megs of ram.

73,
Art
WB4MNK
------------------------------------------------------------------------


No virus found in this incoming message.
Checked by AVG - Version: 8.0.169 / Virus Database: 270.7.0/1681 - Release Date: 9/19/2008 3:54 PM


Re: fldigi 303

rich
 

1: configure-video-view xmit signal

2: Qsk on right channel can be used to key before and unkey after,
but direct cw keying is not possible at this point. (shape factor is
a function of the audio envelope)

3: This ia an area that is being worked on by the developers, but I
cannot answer (I don't know).

Rich
WA4SXZ

--- In win-fldigi@..., "wb4mnk" <wb4mnk@...> wrote:

I have three questions:

Can you keep the waterfall active during transmit ?
When transmitting CW can you use RTS to key the transmitter ? I could
only get CW to transmit by using the sound card.
I use DXKeeper for my final log book and wanted to know if it can be
set up as a real time log with fldigi 303 ?

I am using XP with a Dell 500hz computer with 768 megs of ram.

73,
Art
WB4MNK


fldigi 303

wb4mnk
 

I have three questions:

Can you keep the waterfall active during transmit ?
When transmitting CW can you use RTS to key the transmitter ? I could
only get CW to transmit by using the sound card.
I use DXKeeper for my final log book and wanted to know if it can be
set up as a real time log with fldigi 303 ?

I am using XP with a Dell 500hz computer with 768 megs of ram.

73,
Art
WB4MNK


ADIF Lookup

rich
 

This program is made to import an ADIF and lookup information that you
may need to add to the log entry. While it was not made for Fldigi,
it may very well work with the logbook. I don't contest so I haven't
tried it myself. I would be interested in hearing if it is useful.
Link is:



It's free and the author works where I do, so I know he keeps the
program updated. He also keeps a massive collection of manuals.

Rich
WA4SXZ


Re: fldigi-3.03 posted

rich
 

For those who are having some difficulty with virtual com ports this
version has been reported to work properly with Rigexpert, Navigator,
and Rigblaster USB interfaces.

Rich
WA4SXZ

--- In win-fldigi@..., w1hkj <w1hkj@...> wrote:

Look on the web site,

for the latest versions of fldigi and NBEMS,

The changes from 3.02 to 3.03 include:

* Changes to socket server to correct shutdown process
* Added event logging and an event viewer - to assist in debugging
* Added QRZ cdrom / database location specifier with auto-search
* Bug fix for sound on OS X 10.4
* Bug fix for Socket Server. Added error checking for listen().
* Update to build scripts. Corrected compiler flags for
building universal binary on OS X. Changed to a more reliable way
of linking hamlib statically. Updated app bundling script.
* Set tooltip font - tooltip changed to use same font and size
selected with the command line switch --font. Set default font
sizes on OS X.
* Inhibit Tx / Rx of higher speed MFSKpic modes on slower computers
* Added color selection for Rx/Tx text panels
o Normal text
o Transmitted text
o Control character text
o Skipped text
o Alternate (quick view) text
o Background
* Changed the way that RTS/DTR PTT is used with rig.xml files
* Updated regular expression parser
* Modified <EXEC> passing of fd's to child processes. Added $LOC
locator field to <EXEC>...</EXEC> calls for return values ($NAME
$QTH $LOC).
* Changed "no color" buttons to background vice background2 (white).
Setting -bg <color> on command line switch now controls the "no
color" value for the macro buttons.
* Fixed macro timer to properly reset if <TIMER> re-invoked
during timeout period.
* Fixed broken access to on-line subscriber Hamlog data base
* Removed trailing spaces from frequency field in ADIF file
* Changes to rigio thread loop to disable reads during transmit
* Improved serial port discovery
* Added History replay option - when enabled; right click on
waterfall replays audio history buffer.
* OS X resize handle / button overlay fixed
* Modified sound port Event Log message.
* Added Callsign to Title Bar "NO CALLSIGN SET" if the MyCallsign
is void.
* Added "log.clear" to xmlrpc command set - clears the data in
the logbook fields.
* If compiled into the executable the xmlrpc server is always
started. ARQ server is also started. Both can be serviced
concurrently.
* Increased RTTY cross-hair scope sensitivity
* Modified Generate/Playback file to be closer to Capture in signal
level.
* Modified "view transmit" signal level to be closer in amplitude
to Rx signal level.
* Fixed XMLRPC bug in mode.set_by_id and mode.set_by_name calls.
* Added "tlf", The Left Foot, contest program support. fldigi
accepts tx data and returns rx data to tlf. (Linux primarily).

The development and alpha test teams have been busy. You should
contact
one of the development team if you desire to write an application that
uses any of the various schemes to interface to fldigi for logging, and
remote access and control of fldigi. We would like to know the
level of
interest of fldigi related development so that we can share ideas,
concepts, problems and solutions.

73, Dave, W1HKJ


Fldigi Log

 

Hi John

Yes of course it does save all parameters, and when saving it will put
the adif file called fldigi.adif within your fldigi.files folder. So
you should then be able to export it no problem. I haven't done it
myself by the way as I only require simplistic log keeping, not being
a contester etc hi. But I do agree that such activity requires much
more information keeping, of course I understand that completely.
Pity, but as far as I know there is no other multifunctional logging
software which interfaces with the windows version of fldigi directly.

Keep me posted, and do copy to the group of course rather than direct
to me if the adif poses a problem, but I shouldn't think it will.

Take care out there John.

Cheers,

Dave.


fldigi-3.03 posted

w1hkj
 

Look on the web site,

for the latest versions of fldigi and NBEMS,

The changes from 3.02 to 3.03 include:
  • Changes to socket server to correct shutdown process
  • Added event logging and an event viewer - to assist in debugging
  • Added QRZ cdrom / database location specifier with auto-search
  • Bug fix for sound on OS X 10.4
  • Bug fix for Socket Server. Added error checking for listen().
  • Update to build scripts.? Corrected compiler flags for building?universal binary on OS X. Changed to a more reliable way of linking?hamlib statically.? Updated app bundling script.
  • Set tooltip font - tooltip changed to use same font and size selected?with the command line switch --font.? Set default font sizes on OS X.
  • Inhibit Tx / Rx of higher speed MFSKpic modes on slower computers
  • Added color selection for Rx/Tx text panels
    • Normal text
    • Transmitted text
    • Control character text
    • Skipped text
    • Alternate (quick view) text
    • Background
  • Changed the way that RTS/DTR PTT is used with rig.xml files
  • Updated regular expression parser
  • Modified passing of fd's to child processes. ?Added $LOC locator field to ... calls for return?values ($NAME $QTH $LOC).
  • Changed "no color" buttons to background vice background2 (white). ?Setting -bg on command line switch now controls the "no color" value for the macro buttons.
  • Fixed macro timer to properly reset if re-invoked during?timeout period.
  • Fixed broken access to on-line subscriber Hamlog data base
  • Removed trailing spaces from frequency field in ADIF file
  • Changes to rigio thread loop to disable reads during transmit
  • Improved serial port discovery
  • Added History replay option - when enabled; right click on waterfall replays audio history buffer.
  • OS X resize handle / button overlay fixed
  • Modified sound port Event Log message.
  • Added Callsign to Title Bar "NO CALLSIGN SET" if the MyCallsign is?void.
  • Added "log.clear" to xmlrpc command set - clears the data in the?logbook fields.
  • If compiled into the executable the xmlrpc server is always started. ?ARQ server is also started.? Both can be serviced concurrently.
  • Increased RTTY cross-hair scope sensitivity
  • Modified Generate/Playback file to be closer to Capture in signal level.
  • Modified "view transmit" signal level to be closer in amplitude to?Rx signal level.
  • Fixed XMLRPC bug in mode.set_by_id and mode.set_by_name calls.
  • Added "tlf", The Left Foot, contest program support.? fldigi accepts?tx data and returns rx data to tlf. (Linux primarily).
The development and alpha test teams have been busy.? You should contact one of the development team if you desire to write an application that uses any of the various schemes to interface to fldigi for logging, and remote access and control of fldigi.? We would like to know the level of interest of fldigi related development so that we can share ideas, concepts, problems and solutions.

73, Dave, W1HKJ


Re: IC-703 PTT

w1ret
 

Thanks for the quick reply Dave.

I will try to confirm this as you suggest.

This isn't a show stopper as I have a RigExpert Plus interface that
can perform the PTT for me. I normally use CAT interface for other
programs. Plus it looks way to dangerous for me to attempt any
changes on my own!

73,

Jim W1RET

--- In win-fldigi@..., David <g3vfp@...> wrote:

Hi Jim

It isn't actually fldigi which selects that option. It is built into the
hamlib file for the IC703 which has from 3.02 been compiled
into fldigi. Whoever wrote the hamib IC703 contribution I guess
would have know the string for ptt. I may be wrong, but I think
you would have to get hold of whoever wrote that portion for
hamlib, and ask that question. As once it is in the library, and
that library is compiled I guess is the right word for insertion into
fldigi it is cast in stone until a new version is available.

I would confirm that with Dave W1HKJ though as I am no
software expert.

Fldigi does support COM port ptt either from RTS or DTR, and
that can be setup individually in the RigCat setup by inserting the
port used for ptt control if you have that as a seperate entity in
your interface.

Interestingly enough for Icoms and others as long as RTS/CTS
handshaking isn't used, you can use the same com port for
CAT radio control and ptt. As CAT uses txd, and rxd data
lines and ptt uses as I say RTS or DTR. So you could wire
the same com port for both.

In my case the IC706 series doesn't have a cat command string
for ptt, so I have no choice but to select a port for ptt using tty
(in windows jargon that would say com port), and a port for
cat control of other functions. I actually use a USB Navigator
and have COM5 for CAT, and COM6 for ptt for example.

In the final analysis you can use the XML file for the IC703
edit it using Notepad for your CAT port, baud rate etc.
Leave RTS set to true but not DTR. Then save it as rig.xml
in your fldigi.files folder. Leave RigCat to find that port, and
in the rig setup in fldigi put your ptt port and as I say tty. Then
you should have both ptt and CAT .... I hope :-).

Hmmmm just looked at the Hamlib file for the IC706 and it
does say "can get ptt Y" which assumes it was written with it
in. But it also shows that file as untested, so I think you would
have to find out who wrote it.

Take a look at this url Jim



It will explain what Hamlib is all about, and how software writers
can incorporate it into their own software for rig control. The item
for supported rigs shows number 355 as being the one for the IC703.

I hope this helps rather than confuses hi.

Best Regards,

Dave G3VFP

www.g3vfp.org




On 31/08/2008 13:24:06, w1ret (w1ret@...) wrote:
> Does fldigi 3.02 support CAT PTT? I
> haven't been able to find a
> combination that works.
>
> I have rig configuration done and tried various options in it. My
> present settings are Hamlib, use HamLib, use Hamlib PTT. The the rig,
> comm port and baud rate are selected. I know that the selection is
> correct because the Hamlib controller works fine. I just can't
> get it
> to issue a PTT via the CAT.
>
> Any suggestions?
>
> 73,
>
> Jim W1RET
>
>
>
>
> ------------------------------------


Re: IC-703 PTT

 

Hi Jim

It isn't actually fldigi which selects that option. It is built into the
hamlib file for the IC703 which has from 3.02 been compiled
into fldigi. Whoever wrote the hamib IC703 contribution I guess
would have know the string for ptt. I may be wrong, but I think
you would have to get hold of whoever wrote that portion for
hamlib, and ask that question. As once it is in the library, and
that library is compiled I guess is the right word for insertion into
fldigi it is cast in stone until a new version is available.

I would confirm that with Dave W1HKJ though as I am no
software expert.

Fldigi does support COM port ptt either from RTS or DTR, and
that can be setup individually in the RigCat setup by inserting the
port used for ptt control if you have that as a seperate entity in
your interface.

Interestingly enough for Icoms and others as long as RTS/CTS
handshaking isn't used, you can use the same com port for
CAT radio control and ptt. As CAT uses txd, and rxd data
lines and ptt uses as I say RTS or DTR. So you could wire
the same com port for both.

In my case the IC706 series doesn't have a cat command string
for ptt, so I have no choice but to select a port for ptt using tty
(in windows jargon that would say com port), and a port for
cat control of other functions. I actually use a USB Navigator
and have COM5 for CAT, and COM6 for ptt for example.

In the final analysis you can use the XML file for the IC703
edit it using Notepad for your CAT port, baud rate etc.
Leave RTS set to true but not DTR. Then save it as rig.xml
in your fldigi.files folder. Leave RigCat to find that port, and
in the rig setup in fldigi put your ptt port and as I say tty. Then
you should have both ptt and CAT .... I hope :-).

Hmmmm just looked at the Hamlib file for the IC706 and it
does say "can get ptt Y" which assumes it was written with it
in. But it also shows that file as untested, so I think you would
have to find out who wrote it.

Take a look at this url Jim



It will explain what Hamlib is all about, and how software writers
can incorporate it into their own software for rig control. The item
for supported rigs shows number 355 as being the one for the IC703.

I hope this helps rather than confuses hi.

Best Regards,

Dave G3VFP

www.g3vfp.org

On 31/08/2008 13:24:06, w1ret (w1ret@...) wrote:
Does fldigi 3.02 support CAT PTT? I
haven't been able to find a
combination that works.

I have rig configuration done and tried various options in it. My
present settings are Hamlib, use HamLib, use Hamlib PTT. The the rig,
comm port and baud rate are selected. I know that the selection is
correct because the Hamlib controller works fine. I just can't
get it
to issue a PTT via the CAT.

Any suggestions?

73,

Jim W1RET




------------------------------------