Date   

Auto Notch

Brent Mcl
 

Dose this work on others radios on mine all  the audio is distorted no matter were the slide control sits  .


Re: Phase noise or front end overload #elad

Patrick Bouldin KM5L <patrick@...>
 

Hey Clint, thanks for responding. Gosh with so much crowding during field day I don't think I could answer those questions. I see the ADC flash now and then, always have, I thought I heard that was "normal". Didn't notice the DUO PK light but I'll start to look.

Your last comment, what is that, a high pass filter that blocks anything lower than 160 meters? Tell me about the filter!

Thanks and 73,
Patrick KM5L


Re: DUO up/down band change

Andy G4JNT
 

AH-HA____
Missed that.     192 + rssi etc.   or 0x32 + ....
and just checked the vol. settings and other bytes and yes, it's all been carefully thought-out to avoid 0x01 31 and 0x00 30 sequences - neat. 

As I never use dual VFO, I failed to appreciate my keypad only changes VFO-A.  If I read the status,  it could be arranged to change whichever VFO is in use.  But not really worth it for  microwave and VLF operations 



On Sun, 12 Jul 2020 at 17:28, Neil Smith G4DBN <neil@...> wrote:

The values in the 1024-byte spectrum have a range of 50 to 255 decimal, so you can't get a value lower than 0x32 as part of the spectrum, so the spectrum control block header pattern and parameter control block headers cannot be sent as spectrum values.

The values in the VFO A/B are encoded as 8-byte pseudo-ascii, so can't have a 0x01 or 0xF3 for example.

To guard against sync loss, you read in the number of bytes specified in the header and if any of the ASCII values are out of range, bail out of decoding and look for a new header.

It's a while since I messed with interfacing, but it worked OK and seemed robust, but the test would be to cause some glitches and see if the decoder can recover.  If you read in a 1024 byte spectrum and byte 3 was 0x00 because of a long glitch, then so long as your parser can restart decoding at that point and doesn't have to discard the buffer, you would be able to recover gracefully.  Otherwise just ditch the lot and scan for another valid header frame.

Neil G4DBN


On 12/07/2020 16:48, Andy G4JNT wrote:
Having looked at the EXTIO protocol I'm now a bit confused.
There is an attempt to make a header for Spectrum and  Parameter data  ,   0x00 30 [30 30 34 30]   and  0x01 31 [3F 31 30 30] respectively, but as far as I can see it is not necessarily unique;   there is nothing to stop that series of bytes appearing in either the body of the spectrum data, which is just 8 bit byte values, or in some of the parameter fields.

I feel sure I've missed some point somewhere, as it clearly does work in practice with the Blue Duo etc,  but why doesn't framing go wrong ?

If the frame pattern is unique, then extracting just small amounts of parameter data is merely a case of looking for the frame, then counting bytes until the wanted ones arrive.   A small circular buffer a low as 31 bytes long would suffice for that - and any small processor like a PIC  could do it.



On Sat, 11 Jul 2020 at 08:24, Giovanni Franza <gfranza@...> wrote:

[Edited Message Follows]

Hi Andy,
the band of the spectrum is 192kHz and the bins are of 192/1024 kHz, because 192 kS/s is the sampling rate at which the internal SDR operates.
On the spectrum you can see the effect of the windowing as "shoulders" on the ending of the spectrum.
In BlueDUO I use and display only 160 kHz because I prefer not to show the part of band afflicted by the windowing.
Do not trust the spectrum timing. It is computed when the internal cpu has time, not on precise istants, even if the timings are more or less those.
Reards,

Giovanni - HB9EIK
_._,_._,


Re: DUO up/down band change

Giovanni Franza
 

Hi Andy,
for the sketch length the problem is not only the buffer length (see later) but also variables and code itself.
For the buffer: sometimes the protcol has been modified, and it is possibile that more parameters will be added in the future.
If you plan to use a buffer for data receprion, remember to use a bigger one or to limit byte reading to buffer length
and to discard other data if the protocol report a length greater than buffer length.
My sketch is far perfect, it was built ony to solve a specific problem, and I left code only to help people that are willing to erite ther own code.
Regards,

Giovanni - HB9EIK


Re: DUO up/down band change

Giovanni Franza
 

Hi Neil,
your explanation is perfect, both in BlueDUO and other projects I don't have problem with sincronization, even if I start serial progam, and receprion, at "wrong time".

Giovanni - HB9EIK


Re: DUO up/down band change

Neil Smith G4DBN
 

The values in the 1024-byte spectrum have a range of 50 to 255 decimal, so you can't get a value lower than 0x32 as part of the spectrum, so the spectrum control block header pattern and parameter control block headers cannot be sent as spectrum values.

The values in the VFO A/B are encoded as 8-byte pseudo-ascii, so can't have a 0x01 or 0xF3 for example.

To guard against sync loss, you read in the number of bytes specified in the header and if any of the ASCII values are out of range, bail out of decoding and look for a new header.

It's a while since I messed with interfacing, but it worked OK and seemed robust, but the test would be to cause some glitches and see if the decoder can recover.  If you read in a 1024 byte spectrum and byte 3 was 0x00 because of a long glitch, then so long as your parser can restart decoding at that point and doesn't have to discard the buffer, you would be able to recover gracefully.  Otherwise just ditch the lot and scan for another valid header frame.

Neil G4DBN


On 12/07/2020 16:48, Andy G4JNT wrote:
Having looked at the EXTIO protocol I'm now a bit confused.
There is an attempt to make a header for Spectrum and  Parameter data  ,   0x00 30 [30 30 34 30]   and  0x01 31 [3F 31 30 30] respectively, but as far as I can see it is not necessarily unique;   there is nothing to stop that series of bytes appearing in either the body of the spectrum data, which is just 8 bit byte values, or in some of the parameter fields.

I feel sure I've missed some point somewhere, as it clearly does work in practice with the Blue Duo etc,  but why doesn't framing go wrong ?

If the frame pattern is unique, then extracting just small amounts of parameter data is merely a case of looking for the frame, then counting bytes until the wanted ones arrive.   A small circular buffer a low as 31 bytes long would suffice for that - and any small processor like a PIC  could do it.



On Sat, 11 Jul 2020 at 08:24, Giovanni Franza <gfranza@...> wrote:

[Edited Message Follows]

Hi Andy,
the band of the spectrum is 192kHz and the bins are of 192/1024 kHz, because 192 kS/s is the sampling rate at which the internal SDR operates.
On the spectrum you can see the effect of the windowing as "shoulders" on the ending of the spectrum.
In BlueDUO I use and display only 160 kHz because I prefer not to show the part of band afflicted by the windowing.
Do not trust the spectrum timing. It is computed when the internal cpu has time, not on precise istants, even if the timings are more or less those.
Reards,

Giovanni - HB9EIK
_._,_._,


Re: DUO up/down band change

Andy G4JNT
 

Having looked at the EXTIO protocol I'm now a bit confused.
There is an attempt to make a header for Spectrum and  Parameter data  ,   0x00 30 [30 30 34 30]   and  0x01 31 [3F 31 30 30] respectively, but as far as I can see it is not necessarily unique;   there is nothing to stop that series of bytes appearing in either the body of the spectrum data, which is just 8 bit byte values, or in some of the parameter fields.

I feel sure I've missed some point somewhere, as it clearly does work in practice with the Blue Duo etc,  but why doesn't framing go wrong ?

If the frame pattern is unique, then extracting just small amounts of parameter data is merely a case of looking for the frame, then counting bytes until the wanted ones arrive.   A small circular buffer a low as 31 bytes long would suffice for that - and any small processor like a PIC  could do it.



On Sat, 11 Jul 2020 at 08:24, Giovanni Franza <gfranza@...> wrote:

[Edited Message Follows]

Hi Andy,
the band of the spectrum is 192kHz and the bins are of 192/1024 kHz, because 192 kS/s is the sampling rate at which the internal SDR operates.
On the spectrum you can see the effect of the windowing as "shoulders" on the ending of the spectrum.
In BlueDUO I use and display only 160 kHz because I prefer not to show the part of band afflicted by the windowing.
Do not trust the spectrum timing. It is computed when the internal cpu has time, not on precise istants, even if the timings are more or less those.
Reards,

Giovanni - HB9EIK


Re: Phase noise or front end overload #elad

Clint Chron
 

Hi Patrick,

 

If the problem signal was adjacent band, then external band pass filters will most likely help.  You need to know the source of the signal that was causing the problem.  If the signal was in-band, then a band pass filter will probably not help.

Did you see the “PK” light on the front of the Duo or the ADC Clip light on the SW-2 software?

 

At my home QTH, I get overload from the strong AM broadcast stations that are about 12 miles from my house.  I have an external AM band-stop filter on my Duo that gets rid of the overload.

 

73

Clint

W7KEC

 

From: EladSDR@groups.io [mailto:EladSDR@groups.io] On Behalf Of Patrick Bouldin KM5L
Sent: Sunday, July 12, 2020 7:33 AM
To: EladSDR@groups.io
Subject: [EladSDR] Phase noise or front end overload #elad

 

Greetings!

Hey I started out using the FDM DUO for Field day, almost all CW. Had to stop because with so much traffic something was creating a lot of phase noise, or just overload of some kind.

Have others experienced this? I don't have any of the external bandpass filters, maybe this will solve, what do you think?

73, 
Patrick KM5L


Phase noise or front end overload #elad

Patrick Bouldin KM5L <patrick@...>
 

Greetings!

Hey I started out using the FDM DUO for Field day, almost all CW. Had to stop because with so much traffic something was creating a lot of phase noise, or just overload of some kind.

Have others experienced this? I don't have any of the external bandpass filters, maybe this will solve, what do you think?

73, 
Patrick KM5L


Re: ART-120 Failure

Charles Ristorcelli
 

How did you open the fuse cap?

Did you use some type of sharp object to remove it?

Mine will not remove by just pulling or pressing it.

I am afraid of damaging it if I use a screwdriver or needle nose plioers.

--
73 de NN3V


Re: ART-60 Spectrum display #duo-art

Simon
 

Ah ok!!!!

Then u need an active loop antenna..lz1aq amp design is GOOD  

Use 4 square loops plus one set at 90 degrees to get 90 degree steering..and also a preferred homebrew noise canceller/ phaser..

I live in very built up london..s3-5 noise on active loop on 160..s5-7 on tx mag loop..

Simon 

On 11 Jul 2020, at 18:33, David KK7SS <d3j452@...> wrote:



Simon,
That's with the dummy load... just internally generated noise!
Quite noisy on my vertical - S6-S9 on 40M !
100ft from the main road intersection, street lights, power lines, traffic lights, etc.
Mercury and Sodium lights at the school 280 ft away!
And one of my neighbors has a plasma TV..
But it could be worse - I could be in an housing area with antenna bans  LOL

Dave KK7SS


Level Meter reading on alias products

Andy G4JNT
 

When using alias products on receive, ( eg at 144MHz), what does the level meter show when set to dBm ?

ie.  does it automatically take into account the SINC(X) loss



Noise from CAT input on revceive

Antony Watts
 

I have just connected up CAT & TX USB to my iMac, and am running Blackcat Systems SSTV app. Pictures are coming in fine on 14230kHz even among the wild SSB contest calls.

So I thought I would try to send something out too, so I configured the CAT for PTT to the USB port, and enabled RTS signalling. immediately the background "hiss' on receive rose by 1 S point. Why? Annoying.

Any ideas?


Re: ART-60 Spectrum display #duo-art

David KK7SS <d3j452@...>
 

Simon,
That's with the dummy load... just internally generated noise!
Quite noisy on my vertical - S6-S9 on 40M !
100ft from the main road intersection, street lights, power lines, traffic lights, etc.
Mercury and Sodium lights at the school 280 ft away!
And one of my neighbors has a plasma TV..
But it could be worse - I could be in an housing area with antenna bans  LOL

Dave KK7SS


Re: ART-60 Spectrum display #duo-art

Simon
 

-120 envious!!!


Re: ART-60 Spectrum display #duo-art

David KK7SS <d3j452@...>
 

Bob,
That helped a bit..
My DUO has a noise floor at about -120dBm
With my QTH and antenna I'm probably never going to get a signal above -30dBm.
I was trying to set those limits..
Had a stab at it this morning and gave up..
I can move the display up and down but can't seem to stretch it..
Such is life in the fast lane  Hi

73 de

Dave G.  KK7SS


Re: ART-60 Spectrum display #duo-art

Bob G3PJT <bob@...>
 

Yes it is a bit tricky but my notes say that 'Lev' sets the top line of the display.
Hope that helps
Bob G3PJT


Re: DUO up/down band change

Giovanni Franza
 
Edited

Hi Andy,
the band of the spectrum is 192kHz and the bins are of 192/1024 kHz, because 192 kS/s is the sampling rate at which the internal SDR operates.
On the spectrum you can see the effect of the windowing as "shoulders" on the ending of the spectrum.
In BlueDUO I use and display only 160 kHz because I prefer not to show the part of band afflicted by the windowing.
Do not trust the spectrum timing. It is computed when the internal cpu has time, not on precise istants, even if the timings are more or less those.
Reards,

Giovanni - HB9EIK


Re: DRM #fdm-sw2

Fred
 

Has there been any progress on the getting the new DRM decoder codecs to work .


ART-60 Spectrum display #duo-art

David KK7SS <d3j452@...>
 

My current Spectrum display range is from 0dBm to -110dBm.
Which parameter do I alter to get it to display -20dBm to -110dBm?
I can't seem to get it right !
Thanks..

3101 - 3120 of 20621