开云体育

Hello all.

I have been using fldigi on an XP operating system with no problems.
I recently upgraded to a new pc running Windows Vista Home Premium
with a 64 bit operating system. I have installed the latest v3.03
for Vista operting system (fldigi-3.03-winV.zip).

Everything runs fine for 5 to 10 minutess and then fldigi locks up.
The waterfall stops, and some of the funtion keys work. For examaple
it I select TX it will go into TX mode but it will take several
seconds before the function actually changes. You can never get it
back to RX. With Hamlib Controller you can change to a stored
frequency but the frequency display is incorrect on the controller.

Here are the specs on the new pc if it helps.

Model: HP Pavillion dv7 Notebook PC
Processor: AMD Turuion X@ Dual_Core Mobile RM-70 2 GHz
Memory (RAM): 4.00 GB
System type: 64-bit Operating System

I am using a RigExpert Plus USB interface which I have downloaded and
installed the latest drivers. I have downloaded and installed
Service Pack 1 for the Vista operating system. So I'm pretty sure
I've got evertything up to date and the radios are an IC-703 and FT-
1000MP.

Has anyone else had this or a similar problem? Any suggestions would
be appreciated as the old XP system has bit the dust and I'm
exclusively on the new PC.

Thanks and 73,

Jim W1RET

Hi guys and dolls,

Dave read the next link:



Hope it helps a little...

Reg.: jan


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

Hi guys

Just something which may or not resonate with other users. Since
running fldigi I always noticed that on running it there was never
any received audio. Checking the soundcard settings on my XP Pro, I
always found that the mic input level on the soundcard was set to
zero. Because I use a few other audio software(s) I thought it was
happening via another program resetting the soundcard. Nope it was
fldigi, or the portaudio module I guess causing it.

In the past I had always used the line input on my trusty old SBI
PCI128 soundcard, but then switched to the mic input when I needed
more audio gain for another software. Anyhow, I have since gone

back

to using the line input instead of mic, and no problems, the line

in

level doesn't get reset.

Not sure if this would still be a problem with sound cards only
having a mic input, but worth mentioning just in case anyone else

had

seen the problem.

Cheers

Dave G3VFP

Fully understood, Dave, and thanks for the quick reply. Since I am
slowly going away from MixW, where a certain selected value could be
selected and would be remembered, I was puzzled by the mentioned
observation. No problem!
73 Fred DL6XAZ

Not for now Fred. The default bandwidth (for the internal DSP filtering) is always set to the optimal value for the pixel rate.

Dave

Hi list,
when I go to "configure - modem - feld" and adjust the filter slider to
say 150 Hz, then "save config - close " nothing happens because when
then switching between any other mode and hellschreiber I got to adjust
the slider again. Is this intentional or not?
Evidently, for FSK Hell the slider got to be wider according to speed,
but for standard feldhell under noisy conditions I would like it to
stay on my setting as long as I run fldigi.
Any way around this?
73 Fred DL6XAZ

--- In win-fldigi@..., w1hkj <w1hkj@...> wrote:
Hi Dave,
thanks very much. Could you tell me how much is "within a few Hertz" to
give me a guideline?
Thank you
73 Fred DL6XAZ

Hi list,
has anybody encountered a similar little quirk: when I am receiving in
MFSK 8 or 16, AFC being active, it does not function; instead it is
necessary to manually adjust the two vertical lines exactly on the
received signal.
vy73 Fred DL6XAZ

All of the MFSK modes require that the initial signal acquisition be
within a few Hertz of the actual signal. Thereafter the AFC will

keep

the signal centered. The AFC loop has a fairly long time constant.

In

fldigi a process called puncturing is used to defeat the effect of

CWI.

73, Dave, W1HKJ

Hi list,
has anybody encountered a similar little quirk: when I am receiving in
MFSK 8 or 16, AFC being active, it does not function; instead it is
necessary to manually adjust the two vertical lines exactly on the
received signal.
vy73 Fred DL6XAZ

All of the MFSK modes require that the initial signal acquisition be within a few Hertz of the actual signal. Thereafter the AFC will keep the signal centered. The AFC loop has a fairly long time constant. In fldigi a process called puncturing is used to defeat the effect of CWI.

73, Dave, W1HKJ

Hi list,
has anybody encountered a similar little quirk: when I am receiving in
MFSK 8 or 16, AFC being active, it does not function; instead it is
necessary to manually adjust the two vertical lines exactly on the
received signal.
vy73 Fred DL6XAZ

Hi guys

Just something which may or not resonate with other users. Since
running fldigi I always noticed that on running it there was never
any received audio. Checking the soundcard settings on my XP Pro, I
always found that the mic input level on the soundcard was set to
zero. Because I use a few other audio software(s) I thought it was
happening via another program resetting the soundcard. Nope it was
fldigi, or the portaudio module I guess causing it.

In the past I had always used the line input on my trusty old SBI
PCI128 soundcard, but then switched to the mic input when I needed
more audio gain for another software. Anyhow, I have since gone back
to using the line input instead of mic, and no problems, the line in
level doesn't get reset.

Not sure if this would still be a problem with sound cards only
having a mic input, but worth mentioning just in case anyone else had
seen the problem.

Cheers

Dave G3VFP

--- In NBEMSham@..., w1hkj <w1hkj@...> wrote:

The timezone name does seem to be broken on cygwin (Windows Posix dll).
Looks like an old problem:



On my Vista computer:

<LDT> : 09/26/08 08:26 CDT
<ILDT> : 2008-09-26 08:26:58+0000
<ZDT> : 09/26/08 13:26 CST
<IZDT> : 2008-09-26 13:26:58Z

On my Linux computer

<LDT> : 09/26/2008 08:30 CDT
<ILDT> : 2008-09-26 08:30:48-0500
<ZDT> : 09/26/2008 13:30 GMT
<IZDT> : 2008-09-26 13:30:48Z

The next revision of fldigi will change the way that Zulu and Local
times are evaluated. The 4 date / time formats will be:

<LDT> : 09/26/2008 08:44 CDT
<ILDT> : 2008-09-26 08:44 (-0500)
<ZDT> : 09/26/2008 13:44Z
<IZDT> : 2008-09-26 13:44 (+0000)

In the meantime I suggest that you use the MACRO tag <IZDT> for Zulu
time expansion in your macros.

73, Dave, W1HKJ

--- End forwarded message ---

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the win-fldigi
group.

File : /Fldigi-DXKeeperGateway.zip
Uploaded by : g3vfp <g3vfp@...>
Description : Gateway to run DXKeeper with fldigi (see read me)

You can access this file at the URL:


To learn more about file sharing for your group, please visit:


Regards,

g3vfp <g3vfp@...>

I asked this before with no solutions offered, so I thought try again
in case someone new missed it. When I have radio control panel
displayed moving of the cursor in the waterfall causes it to disappear.
I have tried everything I know to no avail. Anyone else have this
problem and did you get it fixed ? Mike K9HCK

Thanks very much, Dave, I passed your message on to Paul. In case
there are further questions I shall revert to this problem.
Best regards
Fred DL6XAZ

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

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

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

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

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

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

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

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

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

Dave