Date   

Welcome

david
 

Hi

I came across fldigi some time ago but never used it as it was a Linux
based platform. However that has changed in 2008 it is now ported to
run in Windows 2K, XP, or Vista. The build in the version I have
started with is 3.01, and Dave W1HJK is working on constant updates
together I guess with other dedicated developers. It ran up without
any particular hitch except for the fact it is limited in it's com
port recognition. I have a US Navigator USB based interface which has
com ports allocated for ptt, cat, fsk, etc etc. Fldigi would recognise
the cat port and utilise it, but would not recognise the seperate ptt
port or have the ability to select more than one port for each
function. I couldn't get ptt to work and as I use the IC706MKIIG which
doesn't support a CAT command string for tx/rx then I couldn't use CAT
to ptt.
So I opted for vox ptt which works fine. I have no doubts that over
time these problems will be tackled. Unfortunately I have no
programming skills otherwise I would have had a go myself :-). In any
event the software is multi mode, and does what it says very well. The
only other curiosity is the best way I can describe it is the attack,
and delay time of the squelch which allows a percentage of decoded
noise to creep in on the screen as text. No doubt everyone is familiar
with that when playing with squelch settings in other software, but
this is different, and I haven't found the right spot to set it so to
say. It may be that it is down to my particular setup, and may not be
a general problem or curiosity :-). If you see the same maybe you
could mention it.

A free software developed by fellow hams in their own time has to be
applauded absolutely no question, and I have no desire to be critical
of fldigi at all, simply my comments are aimed at airing what can be
modified in future builds.

I hope you enjoy using fldigi too, and follow up with your thoughts.

Best Regards, and thanks for joining.

Dave G3VFP

http://www.g3vfp.org


Re: Welcome

david
 

I should add that I now have fldigi working okay. With com port ptt,
and cat.

Dave


Typical XP setup

david
 

Hi guys. I have taken some screenshots off my XP system here. To show
the typical folder layout on my xp system. Fldigi has a folder called
fldigi files, usually located in the Documents And Settings area which
contains all it's configuration files, and it's main program folder
which simply has fldigi.exe, flarq.exe, and cygwin1.dll contained in
it. In order to eliminate problems, there should be no other instance
of cygwin1.dll anywhere on the pc.

In any event take a look at the pictures in the photos folder here,
and you will see how mine is configured.

Cheers

Dave G3VFP


Re: Typical XP setup

david
 

OOPS! they are in the Files area not Photos. Sorry about that :-)

de Dave


rig control of ts570

cliff wiginton <wb5bsg@...>
 

I run fldigi on my laptop using PuppyLinux, and it does a good job...I
am trying to get the Windoze version to work on my laptop, and have it
all working except the rig control....
I downloaded the xml file for the 570 and after much head banging...did
an edit job using openoffice 2.0, and saved it back to the fldigi folder
under the name "rig.xml"......It doesn't work yet.....
Can anyone walk me through this thing, I am not the sharpest html man
out here, and I like the program......would like to get it going if I
can....Thanks in advance....
Cliff....................WB5BSG.........


Re: rig control of ts570

david
 

Hi Cliff

Just to recap on what we discussed.

Check the baud rate and number of stop bits in the TS570's menu, and
ensure it coincides with the rig.xml file.

Also check to see if the rig xml file has RTS CTS handshaking set, and
see if it is also a menu selectable item in the TS570's menu setup.

Personally I would not have handshaking set, and would disable it in
both the rig.xml, and also in the TS570. Pins 7 and 8 in the TS570
data plug represent RTS, and CTS respectively, and they can be linked
together if there is no menu option, effectively giving the radio a
permanent handshake scenario.

Hope this helps, as it can be a little off putting when playing with
the PTT and CAT options. I know I wondered about the stability of it
myself, but in the end it worked, and has done ever since :-).

As an aside but maybe of interest is that I found the radio must be
switched on and connected of course when booting up fldigi. In my case
with the IC706MKIIG I had forgotten to switch the radio on, and fldigi
couldn't find the cat before it's timeout. When I switched on the 706
fldigi was already running but without cat. So I closed it down, and
reopened it. Still no cat !. I rebooted xp and when it came up the cat
was fine. It serves to show some of the peculiarities which are not
present in other true Windows software. This may not happen with
anyone else, as we usually have our radios on, before we run any
software, but then you never know :-). Maybe modifying the rig xml
file to remove the cat timeout, so it keeps trying, may be a solution
but I haven't tried it...maybe I will hi.

Do keep us posted on what you find though, as I am sure we will all be
interested in compiling as much info on win fldigi as we can.

Cheers

Dave

--- In win-fldigi@..., cliff wiginton <wb5bsg@...> wrote:

I run fldigi on my laptop using PuppyLinux, and it does a good job...I
am trying to get the Windoze version to work on my laptop, and have it
all working except the rig control....
I downloaded the xml file for the 570 and after much head banging...did
an edit job using openoffice 2.0, and saved it back to the fldigi folder
under the name "rig.xml"......It doesn't work yet.....
Can anyone walk me through this thing, I am not the sharpest html man
out here, and I like the program......would like to get it going if I
can....Thanks in advance....
Cliff....................WB5BSG.........


Build 3.02

david
 

You guys may already know, but just in case.

Fldigi has a new build version 3.02 with added com port
support and hamlib built in.

They work fast WOW!.

http://www.w1hkj.com/Fldigi.html

Cheers

Dave


no luck

wb5bsg <wb5bsg@...>
 

Dave....thanks for your email help, but I just can't get Fldigi to
initialze the rig control and hold it....
I downloaded the 3.02 version, and it0 now will initialize t1he 570,
but after about 10 seconds, the CTL goes off on the 570 readout....
This radio works fine on cat control on all of the other programs, so
it should work on this program also..
Guess I'll just wait until someone spots the problem...I have tried
everything I know of...may have just had a glitch in the old
brain...har....tnx again.
CLiff...........wb5bsg...


Re: no luck

david
 

Hi Cliff

Sorry to hear that. It seems strange that what looks like a handshaking
problem is so erratic. Have you tried stopping RigCat, and using
Hamlib instead ?. I have tried both here since 3.02 came out and both
work fine for me with the little 706MKIIG. Not sure what you mean by
it0 as Windows only refers to serial ports as COM ports. Albeit of
course fldigi is running under cygwin it should still give you com
port numbers.

Hope someone comes up with a brain wave :-).

Cheers

Dave

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

Dave....thanks for your email help, but I just can't get Fldigi to
initialze the rig control and hold it....
I downloaded the 3.02 version, and it0 now will initialize t1he 570,
but after about 10 seconds, the CTL goes off on the 570 readout....
This radio works fine on cat control on all of the other programs, so
it should work on this program also..
Guess I'll just wait until someone spots the problem...I have tried
everything I know of...may have just had a glitch in the old
brain...har....tnx again.
CLiff...........wb5bsg...


Rig Frequency Display

mac2251 <k9hck@...>
 

I got the program to work perfectly except when the freq display is on.
Changing the freq in the waterfall makes the display disappear. Is
this normal or do I need to change something? Mike K9HCK


Re: Rig Frequency Display

david
 

Hi Mike

I haven't seen anything like that here, but you may try slowing the waterfall
refresh rate to slow or Normal.

You could also try going into Windows Task Manager, and look in
Processes for fldigi.exe. Highlight it then right click on the mouse and
set it's priority to high. That gives it cpu preference. Just in case something
else you have running is causing the effect.

That's all I can think of here Mike.

Best Regards,

Dave G3VFP

On 28/08/2008 00:53:01, mac2251 (k9hck@...) wrote:
I got the program to work perfectly except when the freq display is on.
Changing the freq in the waterfall makes the display disappear. Is
this normal or do I need to change something? Mike K9HCK


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

Yahoo! Groups Links


Re: no luck

wb5bsg <wb5bsg@...>
 

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

Hi Cliff

Sorry to hear that. It seems strange that what looks like a handshaking
problem is so erratic. Have you tried stopping RigCat, and using
Hamlib instead ?. I have tried both here since 3.02 came out and both
work fine for me with the little 706MKIIG. Not sure what you mean by
it0 as Windows only refers to serial ports as COM ports. Albeit of
course fldigi is running under cygwin it should still give you com
port numbers.

Hope someone comes up with a brain wave :-).

Cheers

Dave



O.K. Dave....I installed it on my XP machine, and running my Ten-Tec
Omni VI+ and it works perfect.....
So it appears that the problem is with the laptop and Vista.....I have
tried running it as Administrator, and in the XP mode, etc....
Got it to come up and work fine, by uninstalling everything, and
reinstalling, and then carefully setting up in Rigcat...but just as
soon as I save it and then shut the program down...it will not come up
right again, nor will it let me setup and save the cat section again
until I uninstall & reinstall....
So, maybe someone who is a Vista expert may can help me...
Cliff............WB5BSG....


Re: Rig Frequency Display

mac2251 <k9hck@...>
 

Thanks for the input Dave, neither solution worked but will keep
trying.......Mike K9HCK






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

Hi Mike

I haven't seen anything like that here, but you may try slowing the
waterfall
refresh rate to slow or Normal.

You could also try going into Windows Task Manager, and look in
Processes for fldigi.exe. Highlight it then right click on the mouse
and
set it's priority to high. That gives it cpu preference. Just in case
something
else you have running is causing the effect.

That's all I can think of here Mike.

Best Regards,

Dave G3VFP


On 28/08/2008 00:53:01, mac2251 (k9hck@...) wrote:
> I got the program to work perfectly except when the freq display is
on.
> Changing the freq in the waterfall makes the display disappear. Is
> this normal or do I need to change something? Mike K9HCK
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>


fldigi

Robert Dickerson <k3hif@...>
 

I have downloaded fldigi and have the ptt working, but thats all, in
looking at Daves post I see several files that do not exist in my
download,
what Im saying is that rig control does not function-so Im missing
something basic to the program.the rig is an Icom 746 and the op
systam is windows vista. any help would be appreciated...
Bob
k3hif@...


Re: fldigi

david
 

Hi Bob

When first installing fldigi it creates two folders. One in the
default folder. and the other fldigi-files.

If you are running build 3.02 ignore rigcat and goto hamlib. Go down
the list of transceivers supported and enter your 746.

That should get your cat running.

Cheers

Dave

--- In win-fldigi@..., "Robert Dickerson" <k3hif@...> wrote:

I have downloaded fldigi and have the ptt working, but thats all, in
looking at Daves post I see several files that do not exist in my
download,
what Im saying is that rig control does not function-so Im missing
something basic to the program.the rig is an Icom 746 and the op
systam is windows vista. any help would be appreciated...
Bob
k3hif@...


IC-703 PTT

w1ret <w1ret@...>
 

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

david
 

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

http://hamlib.sourceforge.net/

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

w1ret <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

http://hamlib.sourceforge.net/

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
>
>
>
>
> ------------------------------------


fldigi-3.03 posted

w1hkj <w1hkj@...>
 

Look on the web site, http://www.w1hkj.com

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


Fldigi Log

david
 

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.