ik1xpv / extio_sddc Goto Github PK

Hello,

Receiver: RX888
Software: HDSDR v2.80 installer with OmniRig V2 support. (March 19, 2020)
DLL: ExtIO_sddc_v1.1RC1.zip from https://github.com/ik1xpv/ExtIO_sddc/releases/download/v1.1/ExtIO_sddc_v1.1RC1.zip
OS: Windows 10 1909

If you are stubborn like me, you tend to set the "Lo" to Bandwidth / 2 and lock.

It might be nice to note somewhere that when you want to use the edges correctly like LF MF, you have to lower the LO even to see the frequencies <0hf and of course AGC on OFF.

73 F4HTB

I received a request from Joanne Dow.

Two RX888s on the same system at the same time?
Is there a way to change the serial number on one of them so that they can be unambiguously selected?

I'm using this in SDR Sharp V1700. Is it possible to create a DLL version that has both the RF and IF gain defaulting to maximum rather than minimum and if possible saving all the DLL values between sessions?

selecting lower samplerates in VHF should automatically reduce the R820T-tuners' IF bandwidth - to avoid oversteering of ADC

I would like to further abstract the hardware and make the extio not getting to the details of hardware. As we are working on the new revision of hardware, it will be painful to get the PC software to adopt the changes in order to support it.

My proposal, (i actual have some code locally)

1. Remove radio type from pc hardware, instead of having a set of capability structure to describe the hardware. For example, Frequency Range (like 0.1M - 64M etc), Att range ( -32db to 100 db), AGC support (like yes/no), Hardware Sampling Rate( for example, RX888 can support from 32M to 128M, other may fixed 64M, etc)
2. Change the interface of USB to more functional orientated. Remove GPIO support, replaced with LED update, ATT update, etc.
3. Still keep the concept HF and VHF, but replace it with the new concept of ZIF mode and IF mode. In the item 1, we will return each mode frequency range, bandwidth, ATT range.

In the new revision of hardware, we plan to change the tuner with big bandwidth, add dedicate chip for ATT/LNA, has the CMOS switch for HF and VHF. all above items are some sort of requirement in order to keep most of current EXTIO investment.

arm-none-eabi-ld obj/cyfx_gcc_startup.o obj/cyfxtx.o obj/DebugConsole.o obj/i2cmodule.o obj/RunApplication.o obj/StartStopApplication.o obj/StartUP.o obj/Support.o obj/USBdescriptor.o obj/USBhandler.o obj/Si5351.o obj/adf4351.o obj/rd5815.o obj/tuner_r82xx.o obj/pcal6408a.o obj/hf103.o obj/bbrf103.o obj/rx888.o obj/rx999.o obj/rx888r2.o obj/rx888r3.o obj/rxlucy.o --entry CyU3PFirmwareEntry -L ../SDK/fw_lib/1_3_4/fx3_release -lcyu3sport -lcyu3lpp -lcyfxapi -lcyu3threadx /usr/lib/arm-none-eabi/lib/libc.a /usr/lib/gcc/arm-none-eabi/4.8.1/libgcc.a -T ../SDK/fw_build/fx3_fw/fx3_512k.ld -d --gc-sections --no-wchar-size-warning -Map SDDC_FX3.map -o SDDC_FX3.elf
arm-none-eabi-ld: cannot find /usr/lib/arm-none-eabi/lib/libc.a: No such file or directory
arm-none-eabi-ld: cannot find /usr/lib/gcc/arm-none-eabi/4.8.1/libgcc.a: No such file or directory
make: *** [makefile:76: SDDC_FX3.elf] Error 1

To extend the reception to LW  up to now we  used different solutions.

Initially a button on the Extio GUI  selects LW or HF mode in BBRF103.
In ExtIO_sddc_v1.01 we tried to use the tuning value to switch LWMODE but it is was not straightforward to use.
In ExtIO_RX888 the toggle switch  selects Zero-IF
When it is set a half of the spectrum in HDSDR is unused.

This discussion is separated by Optimize r2iq one as it seems more related to the user interface than to the technique  used inside the DDC.
I made an experimental branch " Tuning_of_LW_MW_HF " to exercise on this topic. 
It is designed and tested with HDSDR.
There is a single mode HFMODE for LW NW HF from near 0 to 30 MHz and no switch in the GUI.
The goal will be also to switch off HDSDR and switch it back up with the exact same layout.
The idea is to upshift the input complex stream by 1 MHz during the ddc tuning.
At this moment the code has bugs in the reference frequency correction, in the sampling rate switching and ....

Hello,

Receiver: RX888
Software: HDSDR v2.80 installer with OmniRig V2 support. (March 19, 2020)
DLL: ExtIO_sddc_v1.1RC1.zip from https://github.com/ik1xpv/ExtIO_sddc/releases/download/v1.1/ExtIO_sddc_v1.1RC1.zip
OS: Windows 10 1909

When we use the db RF selection in the (F8) SDR-Device.
First time we see -19 or -18db RF.
I have increase to 0db but i can comme back to -9 only.
Unable to set less.

On the main windows of hdsdr, when it is set to -9, i see RF-10.
When i set the gain here, i can set rf-20 and the extIO_sddc.dll screen is set to -19db RF.

I dont no if it's hdsdr or the dll who has a bug.

Many Thanks.

Many thanks to Bjarne Mjelde from http://kongsfjord.no/.
He signalled this behaviour:
"...RX888: I downloaded the latest dll, and tested the RX888 with RC1.2, and 1.1 dll. I also tested with HDSDR 2.81a8 (?), and the latest 2.81b4. Unfortunately, when testing all variations of the software mentioned, I noticed much crackling noise as if it was overloading. I did both 10 and 20 dB attenuation without any luck. Since this was when using another PC than previously, I suspect that the CPU above 50-60 % is what makes it. It was even worse (a lot worse!) when I used the SDR Console. After I freed some CPU, it was better. .."

If you get in similar situations please check also the release v1.1.0 dll . If you are using latest HDSDR beta versions select a spectrum RBW in the range of 100-500Hz not to overload the CPU. Select an ADC sampling frequency of 64M to verify if it depends on overclocking.

• Oscar

Many thanks to Igor Sedov from http://coherent-receiver.com/ for signalling this FX3 code bug:

"... in (https://github.com/ik1xpv/ExtIO_sddc/blob/master/SDDC_FX3/USBhandler.c ) wLength is uint16_t and it is not obvious that the I2CTransfer in https://github.com/ik1xpv/ExtIO_sddc/blob/master/SDDC_FX3/i2cmodule.c has just unit8_t.
As a result, the provided code on host will not work properly and it will be not clear why (especially if it is a new designed hardware board). It took me about a day to find this issue.
There are no big I2C transfers in the current hardware (e.g. rx888 or lucy) and therefore it seems to be irrelevant now but the situation can change in the future."

Mark Pettifor described this bug in  https://groups.io/g/NextGenSDRs/message/318
and made the following investigation, making comparison with v1.01.see following messages.I thank you a lot for pointing it out.I replicated the problem using my sine wave generator -25 dBm level, 64MHz ADCclock, 32M sample rate , -10dB att.

Hereafter the old v1.01 dll

The problem is difficult to notice on low level signals coming from the antenna.It seems to me like there is some problem in ordering sample's buffers ? 

There are one big drawback with our current approach using FFT/iFFT to do iq demod. When running extio with SDR#, we can not tune to exact frequency the application requests, the UI looks odd. As I change the freq, the whole spectrum didn't change.

This limitation is comes from one tunebin represent couple of HZ. In the higher sampling rate (like 128M ADC), the issue is even worse.

We need to find a solution to this while still keeping the computation efficiency.

Hello,

Is there any plans to separate libsddc from the ExtIO?
Not only would this make the code much cleaner with clean separation between the device library and the ExtIO interface,
but it would also allow developers of SDR applications that do not support ExtIO to interface with the SDDC devices easily.

Regards,
Alex

I try to use my RX-888 with qt-dab. The driver ExtIO_sddc doesn't allow to reduce the sampling frequency below 50MHz and the qt-dab expect something much lower.

Any solutions or indications what should be modified in the code?

It would be great to have a SoapySDR driver to be able to use RX666, RX888, RX888 MK2, etc with more open source SDR app like GQRX, CubicSDR, and many others.

It would bring support for theses SDRs on other OS than Windowe: Linux, Mac, BSD.

Hello,

Receiver: RX888
Software: HDSDR v2.80 installer with OmniRig V2 support. (March 19, 2020)
DLL: ExtIO_sddc_v1.1RC1.zip from https://github.com/ik1xpv/ExtIO_sddc/releases/download/v1.1/ExtIO_sddc_v1.1RC1.zip
OS: Windows 10 1909

I have try to set the ppm correction compared to the 9.996MHZ beacon.
I have set the signal to hear on 1khz BF.
The frequency in hdsdr is 9994331hz.
When i go to calibration settings, i have :
Current Tune Frequency [hz] 9994331,00
Correct Tune Frequency: 9995000

When i clic on "Calculate" i get :
+66,94 for the ppm
Tune at 9995000hz

But the BF signal appear no to 1khz but at 1350hz.

Maybe I'm doing it wrong but I followed a youtube video to remind myself how to do it and it doesn't have the same effect.

Many Thanks.

Over on the NextGenSDRs group, Mark Pettifor reported he is receiving the warning 'SDR NOT FOUND' with this latest version: https://groups.io/g/NextGenSDRs/message/334

When I try to start HDSDR with this latest version, I get this message:

When I first plug it in, I hear the Windows "USB Connect" sound. But when I run HDSDR.exe, I hear two separate "USB disconnect" sounds from Windows, like something is being disconnected from USB.

Although, when I go to Device Manager, it still shows it connected (Cypress FX3 USB BootLoader Device).

Several previous ExtIOs still work. (One called RX888.dll and one called ExtIO_sddc_v1.01.dll.)

Hello,

Receiver: RX888
Software: HDSDR v2.80 installer with OmniRig V2 support. (March 19, 2020)
DLL: ExtIO_sddc_v1.1RC1.zip from https://github.com/ik1xpv/ExtIO_sddc/releases/download/v1.1/ExtIO_sddc_v1.1RC1.zip
OS: Windows 10 1909

This phenomenon appears in the high frequencies of HF. Between 22 and 32 mhz.
When I use my FM reception mode, there are less unwanted lines than in USB.
See the pictures.

Many Thanks.

cozy@cozy-Z590-UD-AC:~/ExtIO_sddc/SDDC_FX3$ make
mkdir -p obj
arm-none-eabi-gcc -Wall -c -mcpu=arm926ej-s -mthumb-interwork -o obj/cyfx_gcc_startup.o cyfx_gcc_startup.S
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/cyfxtx.o cyfxtx.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/DebugConsole.o DebugConsole.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/i2cmodule.o i2cmodule.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/RunApplication.o RunApplication.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/StartStopApplication.o StartStopApplication.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/StartUP.o StartUP.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/Support.o Support.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/USBdescriptor.o USBdescriptor.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/USBhandler.o USBhandler.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/Si5351.o driver/Si5351.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/adf4351.o driver/adf4351.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/rd5815.o driver/rd5815.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/tuner_r82xx.o driver/tuner_r82xx.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/pcal6408a.o pcal6408a.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/hf103.o radio/hf103.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/bbrf103.o radio/bbrf103.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/rx888.o radio/rx888.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/rx999.o radio/rx999.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/rx888r2.o radio/rx888r2.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/rx888r3.o radio/rx888r3.c
arm-none-eabi-gcc -g -DTX_ENABLE_EVENT_TRACE -DDEBUG -DCYU3P_FX3=1 -D__CYU3P_TX__=1 -I. -I/home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/inc -I./radio -I./driver -Os -Wall -mcpu=arm926ej-s -mthumb-interwork -ffunction-sections -fdata-sections -c -o obj/rxlucy.o radio/rxlucy.c
arm-none-eabi-ld obj/cyfx_gcc_startup.o obj/cyfxtx.o obj/DebugConsole.o obj/i2cmodule.o obj/RunApplication.o obj/StartStopApplication.o obj/StartUP.o obj/Support.o obj/USBdescriptor.o obj/USBhandler.o obj/Si5351.o obj/adf4351.o obj/rd5815.o obj/tuner_r82xx.o obj/pcal6408a.o obj/hf103.o obj/bbrf103.o obj/rx888.o obj/rx999.o obj/rx888r2.o obj/rx888r3.o obj/rxlucy.o --entry CyU3PFirmwareEntry -L /home/cozy/Cypress/cyfx3sdk/fw_lib/1_3_4/fx3_release -lcyu3sport -lcyu3lpp -lcyfxapi -lcyu3threadx "$ARMGCC_INSTALL_PATH"/arm-none-eabi/lib/libc.a "$ARMGCC_INSTALL_PATH"/lib/gcc/arm-none-eabi/10.3.1/libgcc.a -T /home/cozy/Cypress/cyfx3sdk/fw_build/fx3_fw/fx3_512k.ld -d --gc-sections --no-wchar-size-warning -Map SDDC_FX3.map -o SDDC_FX3.elf
arm-none-eabi-ld: obj/RunApplication.o:/home/cozy/ExtIO_sddc/SDDC_FX3/RunApplication.c:36: multiple definition of Qevent'; obj/DebugConsole.o:/home/cozy/ExtIO_sddc/SDDC_FX3/DebugConsole.c:36: first defined here arm-none-eabi-ld: obj/StartStopApplication.o:/home/cozy/ExtIO_sddc/SDDC_FX3/StartStopApplication.c:16: multiple definition of Qevent'; obj/DebugConsole.o:/home/cozy/ExtIO_sddc/SDDC_FX3/DebugConsole.c:36: first defined here
arm-none-eabi-ld: obj/USBhandler.o:/home/cozy/ExtIO_sddc/SDDC_FX3/USBhandler.c:66: multiple definition of `Qevent'; obj/DebugConsole.o:/home/cozy/ExtIO_sddc/SDDC_FX3/DebugConsole.c:36: first defined here
make: *** [makefile:76: SDDC_FX3.elf] Error 1

Hello!

I have been attempting to get my RX888 working on Linux using libsddc. Everything built fine, I setup udev rules and downloaded the firmware from Github CI, ran
./libsddc/sddc_vhf_stream_test SDDC_FX3.img 3200000 10000 test.i16
The firmware was flashed successfully, but no samples were never actually pulled from the device.

frame_size = 138240, iso_packets_per_frame = 135
started streaming .. for 10000 ms ..

I then carried on to try #196, which either segfaults or returns the following :

normal FW binary executable image with checksum
FX3 bootloader version: 0x000000A9
writing image...
transfer execution to Program Entry at 0x40012a7c
ERROR - USB error LIBUSB_ERROR_ACCESS in find_usb_device at /home/alan/Downloads/rx888/ExtIO_sddc/Core/arch/linux/usb_device.c:462
ERROR - sddc_open() failed

Is this me doing something wrong? Both product IDs are set to be as chmod 666, and running as root does not help in any way. (And yes, this device works perfectly fine on HDSDR / Windows).

Otherwise, thanks for your work on this project!

Edit : I did try the firmware provided on Github, building it myself and extracting from the ExtIO. Same results in all cases.

I am thinking to remove HF/VHF mode. Instead introducing a new concept called frequency range. Each handware can have different range list and deal with the range with the different logic.

For example, HF103 can have one range. 0-32Mhz. most simple
Then, BBRF103 can have two ranges 0-32, 32-1.4G. range0 is Direct, range1 is r820 tuner based.
RX888 can have three ranges, 0-32, 32-64, 64-1.4G. Range0 is Direct with 64M ADC clocks, and range1 with 128M ADC clocks, range2 is tuner based.

thoughts?

The new extio file has clearly solved the problem of VHF singals in HF spectrum. Well done !
On my RX888 MKII unit I can still observe a significant amount of HF signals travelling into VHF and
creating a background pattern. I have attached a few photos to explain what I observe:
The first photo shows my HF spectrum at 32 MHz bandwidth. RF is set to 0 and IF is set to -25.
All is fine.

The second photo shows the VHF spectrum, also at 32 MHz bandwidth, that I see when I tune into
the FM broadcasting area.
The RF in VHF is set to 0. The IF is -5. One can see some week VHF signals and a pattern of a lot of HF
signals that seem to be mirrored into VHF.

When I tune within the VHF spectrum, the VHF signals move as expected but the background signal
pattern remains the same. The signals of the background pattern do not not move.

On the final photo one can see that the background pattern disappears completely when I
disconnect the HF antenna. Then only the VHF signals remain.

Not sure if this is a Bug or an issue with my MKII unit ?

I am trying to catch the bugs by appverifier. I consistently get one crash after about 7minute continues running:
VERIFIER STOP 0000000E: pid 0x11E1C: corrupted infix pattern for freed block

00000000 : Heap handle
129B6CC8 : Heap block
00000000 : Block size
129B6CCC : corruption address

Stack:
ExtIO_SDDC.dll!CCyUSBEndPoint::FinishDataXfer(unsigned char * buf, long & bufLen, _OVERLAPPED * ov, unsigned char * pXmitBuf, CCyIsoPktInfo * pktInfos) Line 2046 C++ Symbols loaded.
ExtIO_SDDC.dll!fx3handler::FinishDataXfer(void * * context) Line 333 C++ Symbols loaded.
ExtIO_SDDC.dll!RadioHandlerClass::AdcSamplesProcess() Line 74 C++ Symbols loaded.
[Inline Frame] ExtIO_SDDC.dll!RadioHandlerClass::Start::__l2::<lambda_7cefb8f6063e0d47b2fd49810a6203a8>::operator()(void *) Line 222 C++ Non-user code. Symbols loaded.
[Inline Frame] ExtIO_SDDC.dll!std::_Invoker_functor::_Call(RadioHandlerClass::Start::__l2::<lambda_7cefb8f6063e0d47b2fd49810a6203a8> &&) Line 1612 C++ Non-user code. Symbols loaded.
[Inline Frame] ExtIO_SDDC.dll!std::invoke(RadioHandlerClass::Start::__l2::<lambda_7cefb8f6063e0d47b2fd49810a6203a8> &&) Line 1612 C++ Non-user code. Symbols loaded.
ExtIO_SDDC.dll!std::thread::_Invoke<std::tuple<<lambda_7cefb8f6063e0d47b2fd49810a6203a8>,std::nullptr_t>,0,1>(void * _RawVals) Line 44 C++ Non-user code. Symbols loaded.

Hello,

Receiver: RX888
Software: HDSDR v2.80 installer with OmniRig V2 support. (March 19, 2020)
DLL: ExtIO_sddc_v1.1RC1.zip from https://github.com/ik1xpv/ExtIO_sddc/releases/download/v1.1/ExtIO_sddc_v1.1RC1.zip
OS: Windows 10 1909

When we start first time we have RBW 62 Hz, after change we can't set it under 122.1Hz.
Can we made something to get more thinness?

Many Thanks,

73 F4HTB

@fventuri

HDSDR shows the RF level in dBFS - assuming, that the I/Q samples it receives are really the sampled values.
strong signals, might get filtered out with the DDC step before HDSDR gets the I/Q data and computes the RF dBFS value shown in the upper right corner of the RF spectrum .. which now might be too low not indicating the correct value ..

Anyone tell me why I get this error with windows 10 64bit ? correct driver is installed as is the two files needed

Hello,
Since libsddc can now be used on Linux, I am implementing support in one of my projects. To do so, I need to get a complex float IQ stream of samples.

From my understanding, libsddc provides real samples only (at least from what I could find), so I ended up implementing my own conversion to an IQ stream... But digging a bit further, I seem to get 32M samples while the ADC is running at 64M, so perhaps I am mainly reading the samples wrong?

What format does the callback provide exactly?

Thanks!

I use a rx888 mk2 with HDSDR 2.80 with two separate antennas connected to it. One for HF, the other one for VHF/UHF.
When I start in HF and tune into VHF/UHF the lower frequency HF signal pattern is visible in the 8 MHz wide VHF/UHF window. The signals are even readable at these higher frequencies in AM mode. The stronger the amplification is set for HF, the stronger these signals appear also in the VHF/UHF window.
The opposite effect can also be observed. When the amplification in VHF/UHF is turned on, strong VHF/UHF signals are visible in the low frequency part of the HF spectrum but they disappear when the UHF/VHF amplification is turned down again.
I have not yet observed this with other SDRs and wonder if this effect is software related or indicates a hardware issue with my mk2 unit ?

Hello,

Receiver: RX888
Software: HDSDR v2.80 installer with OmniRig V2 support. (March 19, 2020)
DLL: ExtIO_sddc_v1.1RC1.zip from https://github.com/ik1xpv/ExtIO_sddc/releases/download/v1.1/ExtIO_sddc_v1.1RC1.zip
OS: Windows 10 1909

When i set 128M (i think for 128msps) for the ADC, i dont find how to have 64mhz of Bandwidth in hdsdr.
Normaly i clic on "Bandwidth [F6]" and on the select menu "Input" i must have 6400000, but i see 32000000 only.

Many Thanks for help.

When I select extio_sddc in SDR#, it tries to connect and crashes. This is my preferred software.
Using this with HDSDR, the output is too bad for use, especially decoders.
I would just like to have this working properly on SDR#.
Radio is RX888 mkII
SDRsharper (v0.5K)
ExtIO_sddc.dll Version "V1.2.0" date 18/3/2021
Thankyou Oscar

Thanks to Bjarne Mjelde, kongsfjord.no arcticdx.blogspot.com who signals this problem.
He use the SDR with a pc that is powered on remotely. His and my thought is that there is something in the design or maybe the driver that prevents the SDR from connecting to the PC. This happens under Windows OS.
It is complex problem as it interests hardware of both PC and SDR, software of drivers, operating system as well as FX3 firmware and re enumerating process.
It is serious for all the stand alone applications.
In some of my test I notice that the problem sometime rises also not using the SDR software but just the Cypress USB Control Center (v1,2,3,0) and the FX3 Superspeed Explorer kit. It seems in common the use of Cypress driver and renumbering with Windows OS.
I hope some indication will came from the Linux community solution.