Date   

Re: SW2 issues with FDM-Duo & FDM-DuoR

Kjell-Goran SM4GRP
 

Paul,

I too did a USB 4.09 reinstall with no change. The error is still there.
73 / Kjell-Goran

2018-03-06 18:09 GMT+01:00 Paul Jones <support@...>:

Roger,

 

It is possible that the USB controller in the Duo is corrupted, try reloading the 4.9 software for the Duo, this is one thing we are looking at
http://sdr.eladit.com/FDM-DUO/Firmware%20Releases/USB%20Interface%20Firmware/index.php?lang=EN

 

Let me know if this works..

 

--

Paul Jones - Elad Technical Support (USA)

FDM-Duo, Duo-Art, FDM-DUOR,  FDM-S3, FDM-S2, FDM-SW2

Visit http://www.eladit.com for the full range of Elad Products

Email Support Group - https://groups.io/g/EladSDR

 

Work Email: support@...
Home Email: Paul@... 
 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Roger Parsons via Groups.Io
Sent: Tuesday, March 6, 2018 12:01
To: EladSDR@groups.io
Subject: Re: [EladSDR] SW2 issues with FDM-Duo & FDM-DuoR

 

It appears that I am not the only one suffering from this problem, and I am very pleased to hear that Elad is taking a serious look at it. Hopefully a result will appear soon.

 

A little bit more information about my situation. I too tried deleting everything related to Elad that I could find, including using CCleaner and restarting between each deletion, and it made no difference. When I reloaded the program - same error message. I then took a separate hard drive on the same PC, formatted it, and loaded a fresh copy of Windows 7. Then installed SW2, and immediately had the same error message. This was before I allowed any Windows updates. I then installed Windows updates in batches of 10 (I would have done them individually but there were hundreds..). At no point did SW2 play nicely with the Duo. Oh, and I initially disabled Windows firewall - not that I can see that it could make any difference. Finally, I took another separate hard drive on a different PC, formatted it and loaded a fresh copy of Windows 7. I then loaded the Elad software, and had the problem straight away. Didn't think that slowly going through updates was worth the effort twice.

 

So I am fairly confident that the problem is not related to:

 

(a) The physical machine;

(b) Something hidden remaining after SW2 is un-installed;

(c) Windows 7 relative to Windows 10;

(d) Windows updates.

 

73 Roger

VE3ZI



Re: SW2 issues with FDM-Duo & FDM-DuoR

Paul Jones
 

Roger,

 

It is possible that the USB controller in the Duo is corrupted, try reloading the 4.9 software for the Duo, this is one thing we are looking at
http://sdr.eladit.com/FDM-DUO/Firmware%20Releases/USB%20Interface%20Firmware/index.php?lang=EN

 

Let me know if this works..

 

--

Paul Jones - Elad Technical Support (USA)

FDM-Duo, Duo-Art, FDM-DUOR,  FDM-S3, FDM-S2, FDM-SW2

Visit http://www.eladit.com for the full range of Elad Products

Email Support Group - https://groups.io/g/EladSDR

 

Work Email: support@...
Home Email: Paul@... 
 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Roger Parsons via Groups.Io
Sent: Tuesday, March 6, 2018 12:01
To: EladSDR@groups.io
Subject: Re: [EladSDR] SW2 issues with FDM-Duo & FDM-DuoR

 

It appears that I am not the only one suffering from this problem, and I am very pleased to hear that Elad is taking a serious look at it. Hopefully a result will appear soon.

 

A little bit more information about my situation. I too tried deleting everything related to Elad that I could find, including using CCleaner and restarting between each deletion, and it made no difference. When I reloaded the program - same error message. I then took a separate hard drive on the same PC, formatted it, and loaded a fresh copy of Windows 7. Then installed SW2, and immediately had the same error message. This was before I allowed any Windows updates. I then installed Windows updates in batches of 10 (I would have done them individually but there were hundreds..). At no point did SW2 play nicely with the Duo. Oh, and I initially disabled Windows firewall - not that I can see that it could make any difference. Finally, I took another separate hard drive on a different PC, formatted it and loaded a fresh copy of Windows 7. I then loaded the Elad software, and had the problem straight away. Didn't think that slowly going through updates was worth the effort twice.

 

So I am fairly confident that the problem is not related to:

 

(a) The physical machine;

(b) Something hidden remaining after SW2 is un-installed;

(c) Windows 7 relative to Windows 10;

(d) Windows updates.

 

73 Roger

VE3ZI


Re: SW2 issues with FDM-Duo & FDM-DuoR

Roger Parsons
 

It appears that I am not the only one suffering from this problem, and I am very pleased to hear that Elad is taking a serious look at it. Hopefully a result will appear soon.

A little bit more information about my situation. I too tried deleting everything related to Elad that I could find, including using CCleaner and restarting between each deletion, and it made no difference. When I reloaded the program - same error message. I then took a separate hard drive on the same PC, formatted it, and loaded a fresh copy of Windows 7. Then installed SW2, and immediately had the same error message. This was before I allowed any Windows updates. I then installed Windows updates in batches of 10 (I would have done them individually but there were hundreds..). At no point did SW2 play nicely with the Duo. Oh, and I initially disabled Windows firewall - not that I can see that it could make any difference. Finally, I took another separate hard drive on a different PC, formatted it and loaded a fresh copy of Windows 7. I then loaded the Elad software, and had the problem straight away. Didn't think that slowly going through updates was worth the effort twice.

So I am fairly confident that the problem is not related to:

(a) The physical machine;
(b) Something hidden remaining after SW2 is un-installed;
(c) Windows 7 relative to Windows 10;
(d) Windows updates.

73 Roger
VE3ZI


Re: SW2 crashed. Can't get it up and running

Kjell-Goran SM4GRP
 

Hello,

Franco and his programmer has asked for a remote session maybe tomorrow. It seems they (ELAD) are also thinking that it has to do with a W10 update.
73/Kjell-Goran

2018-03-06 17:47 GMT+01:00 Raimund <raimund.forstmeier@...>:

Hi Kjell,
thanks x sending me the Error Log file.

In fact the Debugger is reading:
************** Exception Text **************
System.OverflowException: Value was either too large or too small for an unsigned byte.
   at System.Convert.ToByte(Char value)
   at ELADSampler.Form1.InitDemodClass()
   at ELADSampler.Form1.MainFormInit()
   at ELADSampler.Form1.Form1_Load(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnLoad(EventArgs e)

This is the point for your case when the program is opening > MainForminit > Form1_Load:
" System.OverflowException: Value was either too large or too small for an unsigned byte"
The code should be within a  " Try and Exeption " procedure as explained previously. Byte-Values must be checked before using them.
Unfortunately i don't know which value is causing this error and for what it is used.

It would be possible to debug the SD2 exe-file but this is a quite consuming time work.

For me the problem is that there is no "Debugger Error" and the SD2 is just closing the Omni-Rig access in [Remote Ctrl] and i can't get read of the message " Omnirig is not correctly installed!! ".

I'm using Win10 like you. Win10 is updated. Framework is updated that should be also considered when compiling the SD2 program.

It is possible that the whole has to do with a Windows-Update. But only for you ???

Personally i'm convinced that this can't be the only software issue.

Today i will send the Forum references-nr to Mr. Franco. It is important that a software check doesn't concentrate only on 1 issue.

73 Raimund
.





Re: SW2 crashed. Can't get it up and running

 

Hi Kjell,
thanks x sending me the Error Log file.

In fact the Debugger is reading:
************** Exception Text **************
System.OverflowException: Value was either too large or too small for an unsigned byte.
at System.Convert.ToByte(Char value)
at ELADSampler.Form1.InitDemodClass()
at ELADSampler.Form1.MainFormInit()
at ELADSampler.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)

This is the point for your case when the program is opening > MainForminit > Form1_Load:
" System.OverflowException: Value was either too large or too small for an unsigned byte"
The code should be within a " Try and Exeption " procedure as explained previously. Byte-Values must be checked before using them.
Unfortunately i don't know which value is causing this error and for what it is used.

It would be possible to debug the SD2 exe-file but this is a quite consuming time work.

For me the problem is that there is no "Debugger Error" and the SD2 is just closing the Omni-Rig access in [Remote Ctrl] and i can't get read of the message " Omnirig is not correctly installed!! ".

I'm using Win10 like you. Win10 is updated. Framework is updated that should be also considered when compiling the SD2 program.

It is possible that the whole has to do with a Windows-Update. But only for you ???

Personally i'm convinced that this can't be the only software issue.

Today i will send the Forum references-nr to Mr. Franco. It is important that a software check doesn't concentrate only on 1 issue.

73 Raimund
.


SW2 issues with FDM-Duo & FDM-DuoR

Paul Jones
 

Request, is anyone else having issues running FDM-SW2 with the Duo or DuoR, under Windows10, I know about Kjell and Roger, anyone else?

We are actively working on this fault, but was just wondering if anyone else is having same issue, SW2 with the FDM-S2 seems ok

Just answer here or raise a support ticket at http://support.eladit.com

 

 

Paul

 

--

Paul Jones - Elad Technical Support (USA)

FDM-Duo, Duo-Art, FDM-DUOR,  FDM-S3, FDM-S2, FDM-SW2

Visit http://www.eladit.com for the full range of Elad Products

Email Support Group - https://groups.io/g/EladSDR

 

Work Email: support@...
Home Email: Paul@... 
 

 


Re: SW2 crashed. Can't get it up and running

Kjell-Goran SM4GRP
 

That sounds great Paul. I will stand by with no further action from my side until directions are given by ELAD.
Waiting patiently :-) / Kjell-Goran

2018-03-06 15:40 GMT+01:00 Paul NN4F <paul@...>:


It’s possible that this is tied to a recent windows update as we now have 3 errors the same, Franco is freeing up one of the programmers to look at this today or tomorrow, but trust that we are working on this fault ASAP
--
Paul Jones - Elad USA



> On Mar 6, 2018, at 08:40, Raimund <raimund.forstmeier@fastwebnet.it> wrote:
>
> Kjell,
> pls. send me the Error Exception Data via E-mail.
>
> Raimund
> .
>
>
>






Re: SW2 crashed. Can't get it up and running

Paul NN4F
 

It’s possible that this is tied to a recent windows update as we now have 3 errors the same, Franco is freeing up one of the programmers to look at this today or tomorrow, but trust that we are working on this fault ASAP
--
Paul Jones - Elad USA

On Mar 6, 2018, at 08:40, Raimund <raimund.forstmeier@...> wrote:

Kjell,
pls. send me the Error Exception Data via E-mail.

Raimund
.



Re: SW2 crashed. Can't get it up and running

 

Kjell,
pls. send me the Error Exception Data via E-mail.

Raimund
.


Re: SW2 crashed. Can't get it up and running

 

I'm programming since 30 years. I know C++ and VisualBasic.
Now, myself i can't resolve the SD2 Software error as explained here:

https://groups.io/g/EladSDR/message/12875

I canceled any trace of the software on my PC. Yet, no result. I checked all *.xml files, no chance.
I'm connecting SD2 with my own software ' RadioFrequency '. Programming around the error i resolved. The Elad SD2 software error is not resolved.
A normal user can't get around such problems.

One of the most LOGICAL errors with the SD2 Software is in fact :
"Unhandled exception has occured in your application"

When coding the Author must be aware of possible Errors and "logical errors" that are not the same as "Errors".
The Exception can handle this with a Advice or just "nothing".

Example coding:
Try
'here is the code that could result in a Error message

Catch ex As Exception
'a message can return the C++ (or else) message
'my own message
'or just "Nothing"
End Try

I invite ELAD to reply with a precise specification where the SD2 Software is holding/saving data.
- within the radio memory
- within the default folder (*.xml files)
- somewhere else
- within the Windows Register (RegEdit)

It is useless to say: " i never had some problems ". One day you get it. Just we don't know why it occurs and how can we resolve it.

Such a fantastic Radio can't be degraded just by software errors.

Nota:
I'm leaving just about 50 km far from Elad. I wrote to Elad, no replay by Mr. Franco. I did not phone yet as i'm expecting a clear answer with details that can help.

Coding is not that simple without errors. No one is perfect.

73
Raimund
.


Re: SW2 crashed. Can't get it up and running

Paul
 

Just a thought, have you tried to run a registry cleaner to remove any traces of SW2 before trying a re-install?

I don't use SW2, so I have no direct experience with this problem, but I have used CCleaner or JV16 Power Tools to clean out the registry after I remove something.

paul
WB9HCO


Re: ELAD FDM-S3

Otso Ylönen
 

Continuing off-topic:

I have tested Elad FDM-S2 against SDRplay rsp1, rsp2pro and the AirSpy on the FM broadcast band in my home location, some 5 km away from the closest local FM stations. I have a hi-gain aerial and a good mast-head ampflifier.

 

Of these three, only the Elad can handle these “urban” signal levels without saturation, the other three require constant adjustment of attenuation and amplification in order to yield any DX.

 

I know things change when little or no local signals are present. I am looking forward to do testing in such conditions later this year.

 

BR, Otso

 

 

Lähettäjä: dave_m1ctk
Lähetetty: maanantai 5. maaliskuuta 2018 14.30
Vastaanottaja: EladSDR@groups.io
Aihe: Re: [EladSDR] ELAD FDM-S3

 

Just to say yes the rsp1a is much better on airband / 137 mhz (weather sats) and Band II FM than the elad. Not so great on MW though but this is to be expected, the Elad as we all know is exceptional on this band and below LW

Dave

UK

 

On 5 March 2018 at 10:35, James Booth via Groups.Io <jbooth35@...> wrote:

Thank you all for the replies. Very interesting. Will await the S3 and see what it cane do. Hopefully will purchase when available. 

 

 

 


Re: SW2 crashed. Can't get it up and running

Kjell-Goran SM4GRP
 

I did a last try, deleting ver 3.002 and the associated ELAD folders in .../Program Files/... as well as in .../users/.../documents/... and after that restart both PC and DUO and then a full install of ver 1.150 without success. I have raised a support ticket in ELAD's support system. Let's see what happens. I will report back.
73 / Kjell-Goran SM4GRP


Re: SW2 crashed. Can't get it up and running

Neil Smith G4DBN
 

That is the same message reported a few days ago by someone.  Not sure if he managed to find a solution.

Guess it is time to test the new support URL.  Should be easy for Elad to find where the uncaught exception is happening and what the reason is.

Neil


On 06/03/2018 08:39, Kjell-G�ran Bergendahl wrote:

Hi
The factory reset (menu 81) didn't fix it.
Yes, the error message says that; "Value was either too large or too small for an unsigned byte".
73 / Kjell-Goran


Re: SW2 crashed. Can't get it up and running

Kjell-Goran SM4GRP
 

Hi
The factory reset (menu 81) didn't fix it.
Yes, the error message says that; "Value was either too large or too small for an unsigned byte".
73 / Kjell-Goran


Re: SW2 crashed. Can't get it up and running

Neil Smith G4DBN
 

Does a factory reset of the DUO settings have any effect? Is the error message about a byte value being too large or small? That was reported by another forum members a few days ago.
Neil G4DBN

On 6 Mar 2018, at 08:17, Kjell-G�ran Bergendahl <kg.bergendahl@...> wrote:

I also once deleted the ELAD folder in C:\Program Files (x86) after uninstalling the software and then installing from scratch again. No success. Error message was as before: "Unhandled exception has occured in your application".
73 / Kjell-Goran
_._,_._,


Re: SW2 crashed. Can't get it up and running

Kjell-Goran SM4GRP
 

I also once deleted the ELAD folder in C:\Program Files (x86) after uninstalling the software and then installing from scratch again. No success. Error message was as before: "Unhandled exception has occured in your application".
73 / Kjell-Goran


SW2 crashed. Can't get it up and running

Kjell-Goran SM4GRP
 

Hello,
SW2 crashed today. Sigh... It all started yesterday when I enabled transverter use. Everything ran fine (?) but the program always started at zero frequency. This morning SW2 crashed after the PC being off for the night, with a looong error list from W10,and I can get it up and running again. I have saved the error list if needed. I have tried this:

1) Go back to ver 1.150 (upgrade file only)
2) Delete SW2 from control panel and delete the ELAD folder in users/documents/...
3) Do a full install of ver 3.002
4) Click yes on "Repair visual C++" and repair "SW2"

Nothing helps. SW2 doesn't start, I just get the same error over and over again. If I start the program in spite of W10's warning the SW2 window looks very akward.
What to do? Help would be much appreciated.

73 / Kjell-Goran SM4GRP


RadioFrequency > ELAD SD2 > Icom Radio's Connection

 

A professional Freeware Program for HAM + SWL.
Including a Frequency dBase + dB-Converter + several useful features.

The latest update is ready in March 2018 for download. Version 1.6.0
Maybe you don't like the WebPage design. The Site is monitored by ClickTage and this solution was the only one to get visitors reading and not just Mouse-moving.
Download version 1.5.3: here : http://www.intrasystem.it/Frequency/Frequency.html

---------------------------------------------
RadioFrequency Basic Connections
---------------------------------------------
- A - to Icom Radio via SerialPort. COM3/COM4... Direct connection. Read/Set Freq/Mode/S-Meter.
- B - to Icom Radio via Omni-Rig. Direct connection. Read/Set Freq/Mode.
- C - to ELAD SD (RX 2..4) via Virtual Serial Ports. Read Freq/Mode/S-Meter.
- D - to ELAD SD using Omni-Rig and Virtual Ports. Read SD data (Freq/Mode/S-Meter) + Send to Icom Radio (Freq/Mode).
The RadioFrequency Frequencies in List 1..3 can be selected and sent to the Radio.
- E - Elad SD and Icom Radio direct connection selecting the Elad SD [Remote Ctrl]>[OmniRig].
RadioFrequency Port selection could be connected to a Virtual Port. (RX 2..4)
RadioFrequency OmniRig can't be used x this configuration. (OmniRig conflict)
It is suggested to use instead configuration ' D '.

---------------------------------------------------------------------------
OMNI-RIG + SerialPort Conflicts - A Detail you should know
---------------------------------------------------------------------------
RadioFrequency is including:
the OmniRig coded Class + the Interop.OmniRig.DLL that is returning the correct return value.
The Elad SD is not returning the correct OmniRig return value.
Il the Elad SD is not able to connect to OmniRig the return value/error is:
" Omnirig is not correctly installed!! ". This is wrong when OmniRig is correctly installed.
The RadioFrequency/Omni-Rig correct error is reading: " Rig is not responding ".

It is not possible to clean up the COM Ports. When a ComPort or OmniRig conflict is reported you should
- follow the Message
- normally it is necessary to close a program and re-open.
- close the Radio and re-open when you change connection and RadioFrequency is not showing the actual data.
- Radio and Programs must be again initialized (closed and re-opened)

To avoid conflicts it is suggested to choose the right configuration when starting RadioFrequency.
If you know that OmniRig is used by RadioFrequency (not ELAD SD) then open Omnirig after opening RadioFrequency.
In case of error (previous use of same Port) close and re-open the Radio, Elad SD and RadioFrequency.
Re-Open 1. Radio than 2. RadioFrequency than 3. the ELAD SD. ELAD SD should NOT use "the OmniRig".

When the ELAD SD2 is opened before RadioFrequency, The ELAD Software could by Default access the OmniRig which is wrong. (it seems like that)

Also changing from SerialPort COM-Port to Omnirig accessing same COM can cause this error.
You can't access the same COMPort twice from different software.

The Virtual COM Port number may change on different computers, when you install additional devices,
or when you switch the USB connection to a different USB port.

Any ComPort Conflict is never caused by RadioFrequency. The conflict is a internal Windows Device matter.

There are several possibilities to connect a Icom Radio the ELAD SD Receiver and RadioFrequency.


-------------------
What You need
-------------------
- a SerialPort connection x connecting to your Icom Radio. See details in [ About ].
- the Omni-Rig (Freeware) installed x connecting to the Elad SD and as alternative to the Icom Radio.
- a Virtual Serial Ports Emulator (http://www.eterlogic.com) limited freeware or Full version (payware)
- a Virtual Audio Cable Software (http://software.muzychenko.net/eng/vac.htm) Freeware x 3 Cables.
not requested but very useful x connecting the SD2 to more then one Software like fldig, CWSkimmer ecc...
- A simple Audio Connection from the Icom Radio Audio output to the PC Mic-Input is possible.
It is suggested to use a professional Interface like the Mini-ProSC from ZLP Elettronics.
Supplier: http://www.g4zlp.co.uk/unified/DM_MiniPro_SC.shtml. Including a professional SoundCard.

73
Raimund
.


Re: ELAD FDM-S3

dave_m1ctk
 

Just to say yes the rsp1a is much better on airband / 137 mhz (weather sats) and Band II FM than the elad. Not so great on MW though but this is to be expected, the Elad as we all know is exceptional on this band and below LW

Dave
UK

On 5 March 2018 at 10:35, James Booth via Groups.Io <jbooth35@...> wrote:
Thank you all for the replies. Very interesting. Will await the S3 and see what it cane do. Hopefully will purchase when available. 


7801 - 7820 of 20722