Topics

Problems with FDM-SW2 3.027 #fdm-sw2 #fmd-s2


Jeff Patterson
 

This was a first-time install on a high-end HP laptop running 64-bit Windows 7 


The install ran to successful completion. When I run FDM-SW2 I always get this error:



The GUI doesn't show CPU usage


A more serious error (system crash) occurs when I try to play back a recording.

Finally, and this maybe operator error, I cannot get out of "Lock To CF" mode for Rx1. The icon shows it is activated but it is unresponsive to either a mouse click or "K" keyboard short cut. The other recievers work normally. This is annoying since Sync-AM doesn't work with Lock to CF mode active.


Vianney Colombat
 

 
Hello Jeff,
 
see this FAQ for the first issue : http://support.eladit.com/kb/faq.php?id=32
 
If the other issues persist, can you open a support ticket here http://support.eladit.com/open.php?&lang=en_us and provide some screenshots please ?
 
Thank you,
 
Vianney
 
 
From: "Jeff_patterson via Groups.Io" <Jeff_patterson@...>
To: EladSDR@groups.io
Date: Thu, 19 Dec 2019 08:54:55 -0800
Subject: [EladSDR] Problems with FDM-SW2 3.027 #fdm-sw2 #fmd-s2

This was a first-time install on a high-end HP laptop running 64-bit Windows 7 


The install ran to successful completion. When I run FDM-SW2 I always get this error:



The GUI doesn't show CPU usage


A more serious error (system crash) occurs when I try to play back a recording.

Finally, and this maybe operator error, I cannot get out of "Lock To CF" mode for Rx1. The icon shows it is activated but it is unresponsive to either a mouse click or "K" keyboard short cut. The other recievers work normally. This is annoying since Sync-AM doesn't work with Lock to CF mode active.
 

Le informazioni contenute in questo messaggio di posta elettronica sono riservate e confidenziali e ne è vietata la diffusione in qualunque modo eseguita (DL 196/2003). Qualora Lei non fosse la persona a cui il presente messaggio è destinato, La invitiamo ad eliminarlo e a non leggerlo, dandone gentilmente comunicazione al mittente.

The information contained in this e-mail and any attachments is confidential and may well also be legally privileged (DL 196/2003). If you are not among the named recipients, please notify the sender immediately by reply e-mail and then delete this message from your system, do not use the contents for any purpose whatsoever nor disclose them to anyone else.


Neil Smith G4DBN
 

Hi Jeff, the performance counter error  is a common Windows fault.  Easy to fix using lodctr /r from a Windows command prompt. You may need to chage to the SysWOW64 directory:

What exactly happens when you play back a recording?  What are the recording settings?

I use a DUO, so the CF settings are different, but if I unlock the CF lock to the DUO, I can click on the Lock to CF button and it goes off and works fine in Sync AM

One of the S2 owners will be able to advise you on the specifics.

Neil G4DBN



On 19/12/2019 16:54, Jeff_patterson via Groups.Io wrote:
This was a first-time install on a high-end HP laptop running 64-bit Windows 7 


The install ran to successful completion. When I run FDM-SW2 I always get this error:



The GUI doesn't show CPU usage


A more serious error (system crash) occurs when I try to play back a recording.

Finally, and this maybe operator error, I cannot get out of "Lock To CF" mode for Rx1. The icon shows it is activated but it is unresponsive to either a mouse click or "K" keyboard short cut. The other recievers work normally. This is annoying since Sync-AM doesn't work with Lock to CF mode active.

-- 
Neil
<a href="http://g4dbn.uk/"><small>g4dbn.uk</small></a>


Jeff Patterson
 

The performance counter was fixed using the method in the FAQ (thanks!)
I fixed the audio crash by increasing the Soundcard Play Buffer Size (Audio tab in set-up) from 50ms to 1200ms 

Thanks
Jeff


Neil Smith G4DBN
 

Hi Jeff, did you have to change to the SysWOW64 folder, or did it work OK in system32?  Would be useful to note so others will find the solution, and maybe we can update the FAQ.  Mine definitely fails in system32 admin command window with an error 2, and in a non-admin command window with error 5, but works perfectly as admin in SysWOW64

Neil G4DBN

On 19/12/2019 17:41, Jeff_patterson via Groups.Io wrote:
The performance counter was fixed using the method in the FAQ (thanks!)
I fixed the audio crash by increasing the Soundcard Play Buffer Size (Audio tab in set-up) from 50ms to 1200ms 

Thanks
Jeff
-- 
Neil
<a href="http://g4dbn.uk/"><small>g4dbn.uk</small></a>


Jeff Patterson
 

Hi Neil,

If you are referring to the performance counter issue, I just ran the command prompt as admin and executed >lodctr /R in C:\Windows\system32

 

The audio issue was fixed in the audio tab of the set-up panel in FDM-SW2. I had reduced this to 50 ms when I was trying to minimize my audio latency before I realized that this value applies to playback only. Evidently, if the buffer value is set too small the buffer overruns and causes the program to crash. Unfortunately I don’t recall what the default value was but 1200 seems  to work.

 

73

Jeff NG6X

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Neil Smith G4DBN
Sent: Thursday, December 19, 2019 9:47 AM
To: EladSDR@groups.io
Subject: Re: [EladSDR] Problems with FDM-SW2 3.027 #fdm-sw2 #fmd-s2

 

[EXTERNAL]  

Hi Jeff, did you have to change to the SysWOW64 folder, or did it work OK in system32?  Would be useful to note so others will find the solution, and maybe we can update the FAQ.  Mine definitely fails in system32 admin command window with an error 2, and in a non-admin command window with error 5, but works perfectly as admin in SysWOW64

Neil G4DBN

On 19/12/2019 17:41, Jeff_patterson via Groups.Io wrote:

The performance counter was fixed using the method in the FAQ (thanks!)
I fixed the audio crash by increasing the Soundcard Play Buffer Size (Audio tab in set-up) from 50ms to 1200ms 

Thanks
Jeff

-- 
Neil
<a href="http://g4dbn.uk/"><small>g4dbn.uk</small></a>