Date   

Re: New Duo X

Chris Mackerell
 

I don't see anything there that matches my DUO-R.

Everyone has the right to buy what they want, where they
want to. No need to complain here.

Cheers, Chris

On 2020-10-14 00:42, Antony Watts via groups.io wrote:
Yes ELAD is dropping back in speed of action, information, development and software. Just found SunSDR, for example, with Mac OS support and about the same specs and price…

Mac user

Antony M0IFA





Re: ELAD S3 Performance

John Freeman <cbcausgrid@...>
 

I am selling my Elad because I don’t like using Windows. 
It was a pain to setup and continues to give me trouble. 
 

On 2 Oct 2020, at 4:32 pm, Shane Justice <justshane@...> wrote:

Hi Paul,

Well, let me know when Elad has OSX or Linux support, and I will be here to buy a radio from Elad. As you have said, just not right now.

73,
Shane


On Oct 1, 2020 at 21:20, Paul Jones <support@...> wrote: 

Shane,

I think you are over estimating the amount of Mac/Linux users that it would bring in, 1000’s more compared to your “few hundred” we have right now. 

I won’t tell you our exact amount, same as most sellers would not do, but I can assure you it is WAY WAY more than several hundred. 

And finally no one said it would not be fine at some point just not right now!!

Paul EladUSA




On Oct 1, 2020, at 21:13, Shane Justice <justshane@...> wrote:

All,

What may be missing from this discussion is the list opportunity cost of not providing Linux and Mac OS versions of SW2-

Mac people, in particular, don't mind spending more money for their computers, because they generally just work, whereas frequently, Windows gets lots of hiccups, broken divers on OS upgrades, weird behaviors, non-deterministic actions, etc., That are rare to non existent with Unix based platforms.

Lad is likely missing out on sales from people who have the money to buy Elad products, but don't like all the| issues that comes with having to host windows, even partially, on their Mac, and will avoid any product that insists it be hosted on a Windows platform. (I'm one of these people). 

So Elad may only have a few hundred sales now, but may be missing out on thousands more sales because they aren't catering to Unix environments. 

I was contemplating buying a Duo, but I will not do so, now that I know there is no possibility that Elad will support my hardware investment. In fact, I have several thousand dollars of DMR equipment that I am going to sell, as the company who makes it (Hytera) doesn't support Linux configurators. I have decided to go with Rfinder, as it requires no computers to configure the radio. Also, I'll be selling my Motorola and Hytera repeaters, for the same reason and replace them with hotspots, where needed.

Just my $ 0.02 worth.

73,
Shane
KE7TR


Re: New Duo X

Antony Watts
 

Yes ELAD is dropping back in speed of action, information, development and software. Just found SunSDR, for example, with Mac OS support and about the same specs and price…

Mac user

Antony M0IFA


Re: The Next S3 Question

Vianney Colombat
 


We are working on it, it is expected by the end of the year.

Vianney


Il 12/10/2020 19:48, Pete ha scritto:
I am one of the lucky ones who have received, and enjoy a new S3. Thanks Paul.
The next question is; when will the new downconverter module be available and what will be the cost?
With that asked I recommend that documentation of the downconverter's installation, capabilities and operation be posted prior to its release.
I hope we don't have to endure the same scenario we had with getting an FDM S3.

Pete
_._,_._,_


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.


Re: New Duo X

Guillermo
 

Oh, yes.  You can expect this to be a looong wait.  I am changing my subscription to "Special Notices only" as I find the "news" incredibly boring!  At Elad things seem to "move" at a snail's pace.  New and exiting radios are coming out fromother manufacturers.  I already have 2 new ones and the Duo has taken a third seat.  Sad.


Re: FDM-SW2 v3.042 Keyboard Tuning

Jerry
 

On Mon, Oct 12, 2020 at 04:26 PM, Paul Jones wrote:
Can you post a screen shot of the main screen for me?
Hi Paul,

Here's the screenshot.


Re: FDM-SW2 v3.042 Keyboard Tuning

Jerry
 

On Mon, Oct 12, 2020 at 04:25 PM, Bill Nollman wrote:

Is Lock to CF set on/off?

Change that and see if it helps.

Hi Bill,

Lock to CF is set to OFF. I normally have that set to OFF and Lock ABS set to ON.

When I set Lock to CF to ON, things work as I expect them to, e.g. I can type in a frequency, hit Enter, and the RX will tune immediately to that frequency, even if that frequency is considerably different from the current frequency. Thanks for the suggestion.

I would like it to work that way when I have Lock ABS set to ON, but for now the workaround is to turn it off and turn Lock to CF on and enter the new frequency.


Re: FDM-SW2 v3.042 Keyboard Tuning

Paul Jones
 

Jerry, 

Can you post a screen shot of the main screen for me?

Paul EladUSA 


On Oct 12, 2020, at 19:11, Jerry <jerry@...> wrote:

On Mon, Oct 12, 2020 at 03:59 PM, Paul Jones wrote:

As long as the main window is the active window, you can just type the frequency in, no need to hot the space bar

If you have set to khz in the set/graphics/general settings if you want 9420khz, just type in 9420 and hit enter

Hi Paul,

That's how it used to work in v3.027. When I installed v3.042 today I noticed that it behaves differently.

Let's say I'm listening to 6860 kHz and the BW is set to 1.536 MHz so the main display is showing 6252 - 7472 kHz. Now I type in 9420 and hit enter, the tuned frequency jumps to 7472. If I was on 6862 and typed in 5450 and hit enter, the tuned frequency jumps to 6260. So it seems that I cannot enter any frequency that's not within the frequency range currently being displayed in the main window. If I do, the frequency will jump to either the highest or lowest frequency displayed in the main window depending on whether the frequency I enter is either higher or lower than the frequencies being displayed. This doesn't seem like logical behavior. 

I do have it set to "khz" in the set/graphics/general settings.


Re: FDM-SW2 v3.042 Keyboard Tuning

Bill Nollman
 

Jerry;

 

Is Lock to CF set on/off?

Change that and see if it helps.

 

Bill

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Jerry
Sent: Monday, October 12, 2020 7:11 PM
To: EladSDR@groups.io
Subject: Re: [EladSDR] FDM-SW2 v3.042 Keyboard Tuning

 

On Mon, Oct 12, 2020 at 03:59 PM, Paul Jones wrote:

As long as the main window is the active window, you can just type the frequency in, no need to hot the space bar

If you have set to khz in the set/graphics/general settings if you want 9420khz, just type in 9420 and hit enter

Hi Paul,

That's how it used to work in v3.027. When I installed v3.042 today I noticed that it behaves differently.

Let's say I'm listening to 6860 kHz and the BW is set to 1.536 MHz so the main display is showing 6252 - 7472 kHz. Now I type in 9420 and hit enter, the tuned frequency jumps to 7472. If I was on 6862 and typed in 5450 and hit enter, the tuned frequency jumps to 6260. So it seems that I cannot enter any frequency that's not within the frequency range currently being displayed in the main window. If I do, the frequency will jump to either the highest or lowest frequency displayed in the main window depending on whether the frequency I enter is either higher or lower than the frequencies being displayed. This doesn't seem like logical behavior. 

I do have it set to "khz" in the set/graphics/general settings.


Re: FDM-SW2 v3.042 Keyboard Tuning

Jerry
 

On Mon, Oct 12, 2020 at 03:59 PM, Paul Jones wrote:

As long as the main window is the active window, you can just type the frequency in, no need to hot the space bar

If you have set to khz in the set/graphics/general settings if you want 9420khz, just type in 9420 and hit enter

Hi Paul,

That's how it used to work in v3.027. When I installed v3.042 today I noticed that it behaves differently.

Let's say I'm listening to 6860 kHz and the BW is set to 1.536 MHz so the main display is showing 6252 - 7472 kHz. Now I type in 9420 and hit enter, the tuned frequency jumps to 7472. If I was on 6862 and typed in 5450 and hit enter, the tuned frequency jumps to 6260. So it seems that I cannot enter any frequency that's not within the frequency range currently being displayed in the main window. If I do, the frequency will jump to either the highest or lowest frequency displayed in the main window depending on whether the frequency I enter is either higher or lower than the frequencies being displayed. This doesn't seem like logical behavior. 

I do have it set to "khz" in the set/graphics/general settings.


Re: FDM-SW2 v3.042 Keyboard Tuning

Paul Jones
 

Jerry,

As long as the main window is the active window, you can just type the frequency in, no need to hot the space bar

If you have set to khz in the set/graphics/general settings if you want 9420khz, just type in 9420 and hit enter

 

Have a Radiolutionary Day!
Paul

--

Paul Jones - Elad USA Sales & Technical Support (USA)

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

Visit http://www.eladit.com for the full range of Elad Products or USA Sales : https://shop.elad-usa.com/

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

Sales Phone: 312.320.8160

Support Email: support@... Sales Email: sales@...
Personal Email: Paul@...
 
 

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Jerry
Sent: Monday, October 12, 2020 18:42
To: EladSDR@groups.io
Subject: [EladSDR] FDM-SW2 v3.042 Keyboard Tuning

 

Before I installed SW2 v3.042, I could tune via the keyboard by hitting the spacebar and typing the new frequency in kHz into the dialog that popped up and the RX would tune to the new frequency anywhere from 0-30 MHz.

After installing v3.042, when I hit space, I get the "Advanced Tuning" dialog, but it no longer displays the manual input box. If I type digits on the keyboard, even without the advanced tuning dialog open, I can change the frequency, but only within the current frequency span shown in the main window. For example, if the BW is set to 1536 kHz and I'm in the MW band and listening to a station on 980 kHz, I can only enter a frequency on the keyboard between 490 and 1710 kHz. If I want to jump all the way up to 11282 kHz, for example, and enter 1-1-2-8-2 on the keyboard, it jumps right back to the frequency it's already on when I hit <Enter>. :-(

Is there a way to get the old dialog back where I can type in the frequency on the keyboard? The SW2 user's manual on the Elad website dates back to 2018, so it's no help.


FDM-SW2 v3.042 Keyboard Tuning

Jerry
 

Before I installed SW2 v3.042, I could tune via the keyboard by hitting the spacebar and typing the new frequency in kHz into the dialog that popped up and the RX would tune to the new frequency anywhere from 0-30 MHz.

After installing v3.042, when I hit space, I get the "Advanced Tuning" dialog, but it no longer displays the manual input box. If I type digits on the keyboard, even without the advanced tuning dialog open, I can change the frequency, but only within the current frequency span shown in the main window. For example, if the BW is set to 1536 kHz and I'm in the MW band and listening to a station on 980 kHz, I can only enter a frequency on the keyboard between 490 and 1710 kHz. If I want to jump all the way up to 11282 kHz, for example, and enter 1-1-2-8-2 on the keyboard, it jumps right back to the frequency it's already on when I hit <Enter>. :-(

Is there a way to get the old dialog back where I can type in the frequency on the keyboard? The SW2 user's manual on the Elad website dates back to 2018, so it's no help.


Re: FDM-SW2 Recording -- Empty File

Bill Nollman
 

For what it’s worth I used to be able to duplicate that problem by rebooting the PC. The first recording would fail more often than not.

Bill

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Jerry
Sent: Monday, October 12, 2020 5:25 PM
To: EladSDR@groups.io
Subject: Re: [EladSDR] FDM-SW2 Recording -- Empty File

 

I just installed v3.042 and it seems to be running normally. It's the first software (other than OS updates) that I've installed in years that required a reboot.

I'll try setting the same scheduled recording tonight and see what happens.


Re: FDM-SW2 Recording -- Empty File

Jerry
 

I just installed v3.042 and it seems to be running normally. It's the first software (other than OS updates) that I've installed in years that required a reboot.

I'll try setting the same scheduled recording tonight and see what happens.


Re: ELAD FDM-S2

VE7IBI
 

My harsh response was not warranted.  I apologize to you.  I have always been excited by the idea that there may be a way around the old adage that "The more metal in the air, the better the antenna." Alas it may me true,  but I enjoy hunting for unicorns.  I wasn't trying to talk Denis into selling his home and investing in Mini-whip futures, just trying to convey the kick I get from swimming slightly outside of the mainstream on occasion. In the end whatever works best is the one to go with.

Antennas have been a frustration for me since I moved into a small retirement home with very little open ground for a "real" antenna.  Hence my multi-band vertical. I am still fond of loop antennas including ferrites. I have looked up the new eco-whip you mentioned, and I see on your (?) Facebook page.

By the way your English is excellent.  To use your term, sadly, far better than many native English speakers I know.

73,

Jim

VE7IBI


On 10/12/2020 2:43 AM, Ron Liekens wrote:
Jim, my 50 years of antenna experience is just to point out that I'm not a rookie ;-) And, yes you rare right about Chinese copies, but the point I wanted to make is that Roelof Bakker keeps the development of the MiniWhip going and it now has a new low voltage model called EcoWhip which is in its second revision. The Ecowhip I now use is only a few weeks old and is the last revision. I have compared it to the former models to find a real improvement in SNR figures, measured and in normal use. I'm so lucky that I can compare it to the other operational antennas to see its true value. Is it the way I wrote that was bothering you? English is not my native language, so I apologize for this.

Ulli, To be honest, the LIRA is working very well, above my expectations and the 200 m short Beverage is working well. Lately I could erect this Beverage to 350 m and its signal output became stronger than expected but the SNR was only marginally better but has not gained compared to the LIRA. When me and some friends are on a weekend trip we use 450 to 550 m Beverages and I have a 53 meter sized LIRA ready to compare, but Covid-19 problems does form a problem here.
The difference of the LIRA against the Beverage is its better suppression of the back and the side lobes. The produced signal is indeed very small but the FDM-S2 is coping with it very well due to its good sensitivity and low noise level. The power of a good SDR. My use of a Beverage and the LIRA is not based on use of the HAM bands so I guess that my vision is a bit different from yours. I will send you some more info via PM.

73' Ron
ON2RON


Re: FDM-SW2 Recording -- Empty File

Otso Ylönen
 

A friend of mine has had the very problem. I will ask what version of SW2 he had when it happened. Anyway, I think it has been either hardware or OS related.
I had it also years ago, but (fingers crossed) it has been ok for quite some time.
 
BR, Otso
 
Gesendet: Montag, 12. Oktober 2020 um 18:12 Uhr
Von: "Jerry" <jerry@...>
An: EladSDR@groups.io
Betreff: [EladSDR] FDM-SW2 Recording -- Empty File
I set up a scheduled recording (by right clicking on the "record" icon) last night to record the MW band starting at 8:59pm local time on 10/11 and ending at 3:01am local time the next morning (10/12). Center frequency and LO frequency of 1100 kHz. 1536 kHz bandwidth, demod: AM.

I have the maximum file size set to 2GB and the maximum number of files set to 120.

The recording started as expected at 8:59. When I looked at the directory it was saving the files to this morning, I was expecting to see a bunch of 2GB files. Instead, I see a single file named SchedRec_2020_10_12_03_59_00_1110000_FDMSW2_Rec_RF_000.wav with a file size of 0 bytes. It appears from the filename that the first file in the set was created at 0359 UTC (which corresponds to 8:59pm local time), but nothing was saved in it.

This is the first time I've tried recording for more than about an hour. Is there some configuration issue that I'm missing here that would cause the recording to either not to be made or to be zeroed out at the end of the recording period? As a test, I set up a scheduled recording this morning with the same parameters (except start and end times) and it's been running for about 25 minutes now and I see several 2GB files in the recordings directory, so it seems to be working, but it remains to be seen whether the files are still there after the recording ends.

System: 16-core AMD Threadripper CPU, 128 GB RAM, Samsung 960 Pro SSD, Windows 10 Pro. The system is set to never go to sleep.
Receiver: FDM-S2
Software: FDM-SW2 v3.027


Re: FDM-SW2 Recording -- Empty File

Bill Nollman
 

It’s all under test. What software these days isn’t?  Yes, just run the v3.042 update over v3.027.

If you are concerned about doing an upgrade make a backup copy of the ELAD folder in your user directory – for example C:\Users\[your-name]\Documents\ELAD

If everything goes south you can uninstall SW2, delete the ELAD folder, install v3.027 again and copy back the original ELAD folder.

Bill

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Jerry
Sent: Monday, October 12, 2020 2:38 PM
To: EladSDR@groups.io
Subject: Re: [EladSDR] FDM-SW2 Recording -- Empty File

 

Bill,

I'm running SW2 v3.027. That's the only version I've ever run, so there shouldn't be any mismatch with components from an earlier version.

I'm generally leery of running "software under test" -- is v3.042 stable enough so this isn't a concern? If you think it is, I'll give it a try.

If I do install v3.042, do I just run the installer and let it install over v3.027?


Re: FDM-SW2 Recording -- Empty File

Jerry
 

Bill,

I'm running SW2 v3.027. That's the only version I've ever run, so there shouldn't be any mismatch with components from an earlier version.

I'm generally leery of running "software under test" -- is v3.042 stable enough so this isn't a concern? If you think it is, I'll give it a try.

If I do install v3.042, do I just run the installer and let it install over v3.027?


Re: FDM-SW2 Recording -- Empty File

Bill Nollman
 

Jerry;

 

What version of SW2 are you using? I used to have that problem a lot way back in the v1.xxx SW2.

Since upgrading to v3.xxx (I recommend v3.042) the recording scheduler has been nearly perfect.

 

The latest updates and v3.042 are here.

http://eladit.com/download/sdr/FDM-sw2%20Software/Under%20test/index.php?lang=EN

 

But you need to install the v3.027 full version first to get all the other required software before doing the update.

http://eladit.com/download/sdr/FDM-sw2%20Software/Current%20release/index.php?lang=EN

 

Bill

 

 

From: EladSDR@groups.io <EladSDR@groups.io> On Behalf Of Jerry
Sent: Monday, October 12, 2020 2:12 PM
To: EladSDR@groups.io
Subject: [EladSDR] FDM-SW2 Recording -- Empty File

 

I set up a scheduled recording (by right clicking on the "record" icon) last night to record the MW band starting at 8:59pm local time on 10/11 and ending at 3:01am local time the next morning (10/12). Center frequency and LO frequency of 1100 kHz. 1536 kHz bandwidth, demod: AM.

I have the maximum file size set to 2GB and the maximum number of files set to 120.

The recording started as expected at 8:59. When I looked at the directory it was saving the files to this morning, I was expecting to see a bunch of 2GB files. Instead, I see a single file named SchedRec_2020_10_12_03_59_00_1110000_FDMSW2_Rec_RF_000.wav with a file size of 0 bytes. It appears from the filename that the first file in the set was created at 0359 UTC (which corresponds to 8:59pm local time), but nothing was saved in it.

This is the first time I've tried recording for more than about an hour. Is there some configuration issue that I'm missing here that would cause the recording to either not to be made or to be zeroed out at the end of the recording period? As a test, I set up a scheduled recording this morning with the same parameters (except start and end times) and it's been running for about 25 minutes now and I see several 2GB files in the recordings directory, so it seems to be working, but it remains to be seen whether the files are still there after the recording ends.

System: 16-core AMD Threadripper CPU, 128 GB RAM, Samsung 960 Pro SSD, Windows 10 Pro. The system is set to never go to sleep.
Receiver: FDM-S2
Software: FDM-SW2 v3.027


FDM-SW2 Recording -- Empty File

Jerry
 

I set up a scheduled recording (by right clicking on the "record" icon) last night to record the MW band starting at 8:59pm local time on 10/11 and ending at 3:01am local time the next morning (10/12). Center frequency and LO frequency of 1100 kHz. 1536 kHz bandwidth, demod: AM.

I have the maximum file size set to 2GB and the maximum number of files set to 120.

The recording started as expected at 8:59. When I looked at the directory it was saving the files to this morning, I was expecting to see a bunch of 2GB files. Instead, I see a single file named SchedRec_2020_10_12_03_59_00_1110000_FDMSW2_Rec_RF_000.wav with a file size of 0 bytes. It appears from the filename that the first file in the set was created at 0359 UTC (which corresponds to 8:59pm local time), but nothing was saved in it.

This is the first time I've tried recording for more than about an hour. Is there some configuration issue that I'm missing here that would cause the recording to either not to be made or to be zeroed out at the end of the recording period? As a test, I set up a scheduled recording this morning with the same parameters (except start and end times) and it's been running for about 25 minutes now and I see several 2GB files in the recordings directory, so it seems to be working, but it remains to be seen whether the files are still there after the recording ends.

System: 16-core AMD Threadripper CPU, 128 GB RAM, Samsung 960 Pro SSD, Windows 10 Pro. The system is set to never go to sleep.
Receiver: FDM-S2
Software: FDM-SW2 v3.027

1461 - 1480 of 19764