Date   
FLDigi, a very frustrating experience so far.

Francesco Lancellotta
 

I have always been fond of digital modes rx, in particular rtty and fax from utility and naval stations. I always have been able to receive them using my phone put near the rig's speaker with the app droid tty running. No problems in seeing faxes and rtty.
A couple of days ago I installed fldigi and the experience, so far, has been really frustrating. I tuned in the 10100 khz frequency and while on my phone I could perfectly see the rtty text, I couldn't do so via fldigi. More, it doesn't support the 450 hz spacing so I have to enter the configuration every time, modify it just the have the two markers sit on top of the emission in the waterfall but still no demodulation. In my little lovely droidtty there is a function called "reverse" and I keep it flagged. Maybe it depends on this, who knows but where to look in fldigi? The software is very very difficult to manage for me anyone can help? Believe me, I have been looking everywhere on the web but to no avail.

TT Orion II

Lee Parsons
 

Hi Dave,
I just downloaded Flrig. Could you give me the parameters for this rig. Or get me pointed in the right direction. I went with what I could but it isn’t working.
I have been using Fldigi,Flmsg and Flamp with good results for years.
Thank You,
Lee N3LPJ

Re: FLamp Throws a visual c++ run-time error

Cliff
 

In Standard User check Microphone permissions.

73,
Cliff, AE5ZA

On Jan 19, 2019, at 16:40, Rick Hanzlik via Groups.Io <n7ngk@...> wrote:

Ok. I'm getting closer to some answers. Looks a combination of Windows 7 things. When logged into the computer as the administrator, FLDIGI and wsjt work fine with the exception of the FLAMP program not starting and giving the c++ runtime error. 
When logging in as a standard user with admin rights, flamp starts without issue however, the USB CODEC for the audio do not deliver the audio to either fldigi or wsjt.  So I think I''m down to a user permission issue but have no idea how to fix this. any suggestions? And switching to linux is not a solution. been there done that.

Re: FLDigi Optimal Audio Sample Rate?

Dave
 

16 bit 44100, or 16 bit 48000 is sufficient.  24 bi 96000 is an overkill.

Dave

On 1/19/19 2:06 PM, Ed via Groups.Io wrote:
Dave,
Some sound cards and adapters can now do 24 bits at 96000 Hz.  Can you tell us what the optimal sample rate for fldigi processing is?

Thanks & 73,
Ed
N2BHD

Re: FLamp Throws a visual c++ run-time error

Rick Hanzlik
 

Ok. I'm getting closer to some answers. Looks a combination of Windows 7 things. When logged into the computer as the administrator, FLDIGI and wsjt work fine with the exception of the FLAMP program not starting and giving the c++ runtime error. 
When logging in as a standard user with admin rights, flamp starts without issue however, the USB CODEC for the audio do not deliver the audio to either fldigi or wsjt.  So I think I''m down to a user permission issue but have no idea how to fix this. any suggestions? And switching to linux is not a solution. been there done that.

FLDigi Optimal Audio Sample Rate?

Ed
 

Dave,
Some sound cards and adapters can now do 24 bits at 96000 Hz.  Can you tell us what the optimal sample rate for fldigi processing is?

Thanks & 73,
Ed
N2BHD

Re: FLamp Throws a visual c++ run-time error

Rick Hanzlik
 

I use FLRIG to control my radio and I launch flamp from fldigi ( there is a place in the setup to launch other programs)I get this error everytime I launch fldigi and when I launch Flamp by itself. FLamp never actually runs so I'm not able to look at any configurations.

Rick Hanzlik
KR7V
N7NGK@...


On Saturday, January 19, 2019, 6:01:51 AM MST, Dave <w1hkj@...> wrote:


flamp (and it's other flxxx peers) do not depend on any Microsoft libraries.  The error report is bogus.  Is fldigi executing when you try to start flamp?  It should be.

David

On 1/18/19 10:52 PM, Rick Hanzlik via Groups.Io wrote:
Found I didn't have any Visual C++ runtime libraries installed on my computer. Seems like I have installed just about everyone I can find but I am still getting the error. Does anybody know which c++ library FLAMP needs?


Re: mode field in fldigi logging

Dave
 

Which version of fldigi please.

David

On 1/19/19 10:34 AM, N S via Groups.Io wrote:
Another thing I'm noticing is when operating CONTESTIA mode.  The logging program is having problems with the length of the field.   The next time fldigi is opened it instructs the operator to open and re-save the logbook.  Something not quite right there and I'm not sure exactly what's going on.

Norm

Re: mode field in fldigi logging

N S
 

Another thing I'm noticing is when operating CONTESTIA mode.  The logging program is having problems with the length of the field.   The next time fldigi is opened it instructs the operator to open and re-save the logbook.  Something not quite right there and I'm not sure exactly what's going on.

Norm

Re: FlRig 1.3.41 Transceiver not responding.

Dave
 

Glad to hear it is working OK Steve.  Come back to the well if you need more help.

David

On 1/19/19 8:00 AM, Steve Jones via Groups.Io wrote:
David

Well at this point I appear to have totally embarrassed myself.
FlRig V1.3.41 is working seamlessly.

I did as you requested: I deleted files from 'flrig.files', then restarted and setup the IC-718 @ COM3.

I do not know if this made any difference, but previously I had erased the entire folder
'flrig.files' and that did not seem to work (but now I am doubting myself!).

Thanks for your support and I look forward to using FlDigi.

73 DE KA6PRW (Steve)


On Saturday, January 19, 2019, 5:35:50 AM UTC, Steve Jones via Groups.Io <stvnjns51@...> wrote:


Will do this in morning, Saturday. 

Thanks,
Steve

On Jan 18, 2019, at 16:41, Dave <w1hkj@...> wrote:

Please proceed as follows.
  1. delete the files in flrig.files
  2. start flrig 1.3.41
  3. open the configuration dialog to the trace tab
    <ganihmgjkjlccaad.png>
    configure as above and press "View Trace"
  4. change to the Xcvr tab and set up the IC718 on COM3.  Press the Init button.
  5. Close down flrig

Send me the files "trace.txt" and debug_log.txt that are in the flrig.files folder.

David, W1HKJ


On 1/18/19 1:38 PM, Steve Jones via Groups.Io wrote:
Sorry if this has been covered - did not find (successfully) a resolution to this issue.

Background:
  Win 7 Pro
  Was successfully using FlRig 1.3.40.79 (Still in seperate directory and still works).
  Trying to run FlRig 1.3.41 (new install - different directory from 1.3.40.79)

   I am NOT a regular user of FlDigi/FlRig  - I have never transmitted using FlDigi but have successfully received and decoded using FlDigi.
   I have been doing Ft8 and was trying out some of the older digital modes. 
   Please excuse some amount of ignorance. 

  Each time I attempt to start new install of FlRig (1.3.41) , I get the screen:
<dummyfile.0.part>

I do NOT get this screen when I run FlRig 1.3.40.79.

So what I have tried:
1) Reboot
2) Uninstall FlRig and download another new copy from web site (yes - both old and new chksum'd the same).
3) Tried set the IC-718 values in FLRig and when I hit 'init' button, same error (Transceiver not responding)
4) Port 'Com3' which is the IC-718, is happy in the Computer's : Device Manager.
5) When I run WSJT-X, the IC-718 connects and is happy (again using Com3)
       Completely shut down WSJT-X and rebooted.
6) Per another message stream ion this site: Removed the files "flrig.files"  from my home directory and restarted FlRig 1.3.41
      -  Setup the Rig parameters the same as FlRig 1.3.40.79.
      -  Same issue - "Tranceiver not responding".
7) Went back to FlRig 1.3.40.79 - It still works.
8) Yes - I made sure to close ALL programs before starting the programs above, in all cases.
9) My installation directories for both versions are:
      (Old)  C:\Program Files (x86)\Ham\flrig-1.3.40.79\
      (New) C:\Program Files (x86)\Ham\flrig-1.3.41\

I know, if it hurts - Don;t do it.  Sometimes I am a little slow.

Any help would be appreciated.

Steve

--
de KA6PRW 73

--
de KA6PRW 73

--
de KA6PRW 73

Re: flmsg 4.0.8.03

Dave
 

Please test 4.0.8.04 posted at http://www.w1hkj.com/alpha/flmsg/

David

On 1/18/19 1:12 PM, Ed via Groups.Io wrote:
If I launch flmsg 4.0.8.03 without including a --flmsg-dir argument, flmsg does not use C:\Users\<username>\NBEMS.files, but instead creates a set of subfolders (ARQ, CSV, etc.) under the root user folder C:\Users\<username>.  I'm running under Windows 7 Pro.

73,
Ed
N2BHD

Re: FlRig 1.3.41 Transceiver not responding.

Steve Jones
 

David

Well at this point I appear to have totally embarrassed myself.
FlRig V1.3.41 is working seamlessly.

I did as you requested: I deleted files from 'flrig.files', then restarted and setup the IC-718 @ COM3.

I do not know if this made any difference, but previously I had erased the entire folder
'flrig.files' and that did not seem to work (but now I am doubting myself!).

Thanks for your support and I look forward to using FlDigi.

73 DE KA6PRW (Steve)


On Saturday, January 19, 2019, 5:35:50 AM UTC, Steve Jones via Groups.Io <stvnjns51@...> wrote:


Will do this in morning, Saturday. 

Thanks,
Steve

On Jan 18, 2019, at 16:41, Dave <w1hkj@...> wrote:

Please proceed as follows.
  1. delete the files in flrig.files
  2. start flrig 1.3.41
  3. open the configuration dialog to the trace tab
    <ganihmgjkjlccaad.png>
    configure as above and press "View Trace"
  4. change to the Xcvr tab and set up the IC718 on COM3.  Press the Init button.
  5. Close down flrig

Send me the files "trace.txt" and debug_log.txt that are in the flrig.files folder.

David, W1HKJ


On 1/18/19 1:38 PM, Steve Jones via Groups.Io wrote:
Sorry if this has been covered - did not find (successfully) a resolution to this issue.

Background:
  Win 7 Pro
  Was successfully using FlRig 1.3.40.79 (Still in seperate directory and still works).
  Trying to run FlRig 1.3.41 (new install - different directory from 1.3.40.79)

   I am NOT a regular user of FlDigi/FlRig  - I have never transmitted using FlDigi but have successfully received and decoded using FlDigi.
   I have been doing Ft8 and was trying out some of the older digital modes. 
   Please excuse some amount of ignorance. 

  Each time I attempt to start new install of FlRig (1.3.41) , I get the screen:
<dummyfile.0.part>

I do NOT get this screen when I run FlRig 1.3.40.79.

So what I have tried:
1) Reboot
2) Uninstall FlRig and download another new copy from web site (yes - both old and new chksum'd the same).
3) Tried set the IC-718 values in FLRig and when I hit 'init' button, same error (Transceiver not responding)
4) Port 'Com3' which is the IC-718, is happy in the Computer's : Device Manager.
5) When I run WSJT-X, the IC-718 connects and is happy (again using Com3)
       Completely shut down WSJT-X and rebooted.
6) Per another message stream ion this site: Removed the files "flrig.files"  from my home directory and restarted FlRig 1.3.41
      -  Setup the Rig parameters the same as FlRig 1.3.40.79.
      -  Same issue - "Tranceiver not responding".
7) Went back to FlRig 1.3.40.79 - It still works.
8) Yes - I made sure to close ALL programs before starting the programs above, in all cases.
9) My installation directories for both versions are:
      (Old)  C:\Program Files (x86)\Ham\flrig-1.3.40.79\
      (New) C:\Program Files (x86)\Ham\flrig-1.3.41\

I know, if it hurts - Don;t do it.  Sometimes I am a little slow.

Any help would be appreciated.

Steve

--
de KA6PRW 73

--
de KA6PRW 73

--
de KA6PRW 73

Re: FLamp Throws a visual c++ run-time error

Dave
 

flamp (and it's other flxxx peers) do not depend on any Microsoft libraries.  The error report is bogus.  Is fldigi executing when you try to start flamp?  It should be.

David

On 1/18/19 10:52 PM, Rick Hanzlik via Groups.Io wrote:
Found I didn't have any Visual C++ runtime libraries installed on my computer. Seems like I have installed just about everyone I can find but I am still getting the error. Does anybody know which c++ library FLAMP needs?


Re: FLamp Throws a visual c++ run-time error

Renee Culver
 

It runs on my system and I have visual studio 2015 installed.

Renee KC3NG

 

From: winfldigi@groups.io [mailto:winfldigi@groups.io] On Behalf Of Rick Hanzlik via Groups.Io
Sent: January 18, 2019 11:52 PM
To: winfldigi@groups.io
Subject: Re: [winfldigi] FLamp Throws a visual c++ run-time error

 

Found I didn't have any Visual C++ runtime libraries installed on my computer. Seems like I have installed just about everyone I can find but I am still getting the error. Does anybody know which c++ library FLAMP needs?

 

Re: FlRig 1.3.41 Transceiver not responding.

Steve Jones
 

Will do this in morning, Saturday. 

Thanks,
Steve

On Jan 18, 2019, at 16:41, Dave <w1hkj@...> wrote:

Please proceed as follows.
  1. delete the files in flrig.files
  2. start flrig 1.3.41
  3. open the configuration dialog to the trace tab
    <ganihmgjkjlccaad.png>
    configure as above and press "View Trace"
  4. change to the Xcvr tab and set up the IC718 on COM3.  Press the Init button.
  5. Close down flrig

Send me the files "trace.txt" and debug_log.txt that are in the flrig.files folder.

David, W1HKJ


On 1/18/19 1:38 PM, Steve Jones via Groups.Io wrote:
Sorry if this has been covered - did not find (successfully) a resolution to this issue.

Background:
  Win 7 Pro
  Was successfully using FlRig 1.3.40.79 (Still in seperate directory and still works).
  Trying to run FlRig 1.3.41 (new install - different directory from 1.3.40.79)

   I am NOT a regular user of FlDigi/FlRig  - I have never transmitted using FlDigi but have successfully received and decoded using FlDigi.
   I have been doing Ft8 and was trying out some of the older digital modes. 
   Please excuse some amount of ignorance. 

  Each time I attempt to start new install of FlRig (1.3.41) , I get the screen:
<dummyfile.0.part>

I do NOT get this screen when I run FlRig 1.3.40.79.

So what I have tried:
1) Reboot
2) Uninstall FlRig and download another new copy from web site (yes - both old and new chksum'd the same).
3) Tried set the IC-718 values in FLRig and when I hit 'init' button, same error (Transceiver not responding)
4) Port 'Com3' which is the IC-718, is happy in the Computer's : Device Manager.
5) When I run WSJT-X, the IC-718 connects and is happy (again using Com3)
       Completely shut down WSJT-X and rebooted.
6) Per another message stream ion this site: Removed the files "flrig.files"  from my home directory and restarted FlRig 1.3.41
      -  Setup the Rig parameters the same as FlRig 1.3.40.79.
      -  Same issue - "Tranceiver not responding".
7) Went back to FlRig 1.3.40.79 - It still works.
8) Yes - I made sure to close ALL programs before starting the programs above, in all cases.
9) My installation directories for both versions are:
      (Old)  C:\Program Files (x86)\Ham\flrig-1.3.40.79\
      (New) C:\Program Files (x86)\Ham\flrig-1.3.41\

I know, if it hurts - Don;t do it.  Sometimes I am a little slow.

Any help would be appreciated.

Steve

--
de KA6PRW 73


--
de KA6PRW 73

Re: FLamp Throws a visual c++ run-time error

Rick Hanzlik
 

Found I didn't have any Visual C++ runtime libraries installed on my computer. Seems like I have installed just about everyone I can find but I am still getting the error. Does anybody know which c++ library FLAMP needs?

Re: RSID will not change modes

Ed
 

Hello Dave,
Yes, the RemoteHams software provides a VoIP interface for the audio.  However during my test scenario, I was not using the RCForb Client for the audio interface.  I was only using the RCForb client for the virtual COM port.  During my test scenario, I had two instances of fldigi communicating via a pair of virtual audio cables, on the same computer.  I have used these virtual audio cables for years between fldigi and the RCForb client, without any problems decoding the actual data.  The decode of the audio RsID and data mode by the receiving instance of fldigi was perfect, when RigCAT was initialized by flgidi-def.xml to COM1.  But when RigCAT was initialized by fldigi-def.xml to COM8, the RsID would not be recognized, so the mode would not change in the receiving instance of fldigi.  However, if I preset the receiving fldigi instance to the correct mode, then the data message would be decoded perfectly.  I don't think the audio has anything to do with the problem, because I could make RsID work by simply changing RigCAT back to COM1.  Then the RsID and the message would be decoded correctly.  I think the problem has something to do with the code path fldigi takes when it starts up and reads the RigCAT COM port from the flgigi-def.xml file.

If there are any debug flags or logs that can be enabled to help trace fldigi's code path from when it starts until the first RsID is received, I'd be happy to work with you gather more information about it.  I have an old email address for you at bellsouth.net, if you would like to correspond offline.

Thanks & 73,
Ed
N2BHD

Re: RSID will not change modes

Dave
 

COM port selection should have zero effect on RsID decoding.

I am not very familiar with the RemoteHams software.  Does it also provide a virtual sound card interface using VOIP technology?  If yes, then that is the reason for the loss of RsID detection.  The VOIP audio is probably a  lossy interface (not tcpip) and any audio drop outs or sound rate conversion noise will seriously effect the RsID detection.  It's probably OK for CW, voice and even PSK-31.   MT63 and Olivia will probably also work OK on a VOIP audio connection.  Higher baud MFSK modems will probably fail to decode or have lots of decoding errors.

73, David, W1HKJ


On 1/18/19 3:17 PM, Ed via Groups.Io wrote:
I encountered the problem again, where RsID seemed to stop working.  This time it was on the station at my home.  I am running Windows 7 Pro, and fldigi 4.0.19.103.  Again, the problem was resolved by replacing the fldigi_def.xml file.  This time I decided to experiment with incrementally changing the configuration and saving the fldigi_def.xml file until I encountered the problem.  Each time I changed the configuration I saved it, checked to see if RsID worked, and closed fldigi.  When I reopened fldigi, I again checked to see if it would respond to a received RsID.  The last change I made was to modify the RigCAT COM port from COM1 to COM8.  RsID worked with COM8 before closing fldigi, but after reopening it, RsID no longer worked. If I changed the RigCAT COM port back to COM1, RsID began working again.  I repeated this several times, and the results were always the same.  If I opened fldigi when the fldigi_def.xml file was pointing to COM8, the RsID would not work.  I verified that the Device Manager indicated that COM8 was a functioning COM port, while I was conducting the experiment.  One interesting note is that COM1 is a hardware COM port, but COM8 is an ELTIMA virtual COM port.  The ELTIMA virtual COM port is spawned by the RemoteHams RCForb Client.  The RCForb client was actively running throughout this experiment.  I compared the fldigi_def.xml files and the only difference was the <XMLRIGDEVICE> tag.  The functioning fldigi_def.xml file contained <XMLRIGDEVICE>COM1</XMLRIGDEVICE>, while the disfunctional fldigi_def.xml  file contained <XMLRIGDEVICE>COM8</XMLRIGDEVICE>.  It is also worth noting, that the fldigi application at our club station is also interfacing to an ELTIMA virtual COM port, which is spawned by the RemoteHams RCForb Server.

I don't understand what the relationship might be between the RigCAT COM port, and the RsID decoding, but at least I think I can recover when I encounter the RsID problem again.

73,
Ed
N2BHD

Re: FlRig 1.3.41 Transceiver not responding.

Dave
 

Please proceed as follows.
  1. delete the files in flrig.files
  2. start flrig 1.3.41
  3. open the configuration dialog to the trace tab

    configure as above and press "View Trace"
  4. change to the Xcvr tab and set up the IC718 on COM3.  Press the Init button.
  5. Close down flrig

Send me the files "trace.txt" and debug_log.txt that are in the flrig.files folder.

David, W1HKJ


On 1/18/19 1:38 PM, Steve Jones via Groups.Io wrote:
Sorry if this has been covered - did not find (successfully) a resolution to this issue.

Background:
  Win 7 Pro
  Was successfully using FlRig 1.3.40.79 (Still in seperate directory and still works).
  Trying to run FlRig 1.3.41 (new install - different directory from 1.3.40.79)

   I am NOT a regular user of FlDigi/FlRig  - I have never transmitted using FlDigi but have successfully received and decoded using FlDigi.
   I have been doing Ft8 and was trying out some of the older digital modes. 
   Please excuse some amount of ignorance. 

  Each time I attempt to start new install of FlRig (1.3.41) , I get the screen:


I do NOT get this screen when I run FlRig 1.3.40.79.

So what I have tried:
1) Reboot
2) Uninstall FlRig and download another new copy from web site (yes - both old and new chksum'd the same).
3) Tried set the IC-718 values in FLRig and when I hit 'init' button, same error (Transceiver not responding)
4) Port 'Com3' which is the IC-718, is happy in the Computer's : Device Manager.
5) When I run WSJT-X, the IC-718 connects and is happy (again using Com3)
       Completely shut down WSJT-X and rebooted.
6) Per another message stream ion this site: Removed the files "flrig.files"  from my home directory and restarted FlRig 1.3.41
      -  Setup the Rig parameters the same as FlRig 1.3.40.79.
      -  Same issue - "Tranceiver not responding".
7) Went back to FlRig 1.3.40.79 - It still works.
8) Yes - I made sure to close ALL programs before starting the programs above, in all cases.
9) My installation directories for both versions are:
      (Old)  C:\Program Files (x86)\Ham\flrig-1.3.40.79\
      (New) C:\Program Files (x86)\Ham\flrig-1.3.41\

I know, if it hurts - Don;t do it.  Sometimes I am a little slow.

Any help would be appreciated.

Steve

--
de KA6PRW 73

FlRig 1.3.41 Transceiver not responding.

Steve Jones
 

Sorry if this has been covered - did not find (successfully) a resolution to this issue.

Background:
  Win 7 Pro
  Was successfully using FlRig 1.3.40.79 (Still in seperate directory and still works).
  Trying to run FlRig 1.3.41 (new install - different directory from 1.3.40.79)

   I am NOT a regular user of FlDigi/FlRig  - I have never transmitted using FlDigi but have successfully received and decoded using FlDigi.
   I have been doing Ft8 and was trying out some of the older digital modes. 
   Please excuse some amount of ignorance. 

  Each time I attempt to start new install of FlRig (1.3.41) , I get the screen:


I do NOT get this screen when I run FlRig 1.3.40.79.

So what I have tried:
1) Reboot
2) Uninstall FlRig and download another new copy from web site (yes - both old and new chksum'd the same).
3) Tried set the IC-718 values in FLRig and when I hit 'init' button, same error (Transceiver not responding)
4) Port 'Com3' which is the IC-718, is happy in the Computer's : Device Manager.
5) When I run WSJT-X, the IC-718 connects and is happy (again using Com3)
       Completely shut down WSJT-X and rebooted.
6) Per another message stream ion this site: Removed the files "flrig.files"  from my home directory and restarted FlRig 1.3.41
      -  Setup the Rig parameters the same as FlRig 1.3.40.79.
      -  Same issue - "Tranceiver not responding".
7) Went back to FlRig 1.3.40.79 - It still works.
8) Yes - I made sure to close ALL programs before starting the programs above, in all cases.
9) My installation directories for both versions are:
      (Old)  C:\Program Files (x86)\Ham\flrig-1.3.40.79\
      (New) C:\Program Files (x86)\Ham\flrig-1.3.41\

I know, if it hurts - Don;t do it.  Sometimes I am a little slow.

Any help would be appreciated.

Steve

--
de KA6PRW 73