¿ªÔÆÌåÓý

Yes, I have seen this several times, but not frequently.? It does seem to happen more when using a remote web interface than when everything is on the RPi 4.? I do not have a solution to the problem.

73
Evan
AC9TU??

Hello Everybody,
Kit comes as in the picture above, all SMD soldered and ready to work.

Only need to add :

an ILI9341 SPI Display + a Box.

In the website you find the manual

and 3D files to print the box.

I would add some info:
Panadapter is just like an SDR receiver made with:
Quadrature digital mixer + SI5351 + Codec 16 bit/192 KHz and can go up to 150 MHz.
It is present an audio stereo output with I/Q signals, so you can connect your PC (sound card input) and use one of SDR programs available to have a receiver.
Because the mixer has a very high IMD , you can use the panadapter directly connected to the antenna and PC, without the radio.

Have fun, Luca IW2NDH

?

?

I have the same problem.

Has anyone had the sBitx DE, with mods 1 and 2 installed, lockup when switching bands?? ? This only seems to happen when I use the direct sBitx interface and not the web interface.

Sam,
Thanks for sharing this with us. ?One additional question. ?The website just indicates the availability of the kit but not what is required to assemble it. ?Are the major compost pre soldered or is it up to the kit builder to solder everything? ?Thanks

Dave, KA4DKU

The cat control is somehow working after a hard reboot with disconnecting the HDMI monitor--for some reason it continues to supply power to the Raspberry Pi and has to be unplugged for a proper reboot. I now see frequency displayed and the TUNE button works. But that only happens on DIGITAL mode, not FT8 mode, and even on DIGITAL mode the maximum output is only 3.5 watts with Drive = 100. CW output is set at 24 watts.
Has anyone got WSJT-X working via FT8 mode selection? And if it has to be done with the DIGITAL mode, how can the power be increased?
Jack, N6LN

I've got the dual monitor problem solved--thanks, Evan AC9TU--but I still can't reliably get rig control with WSJT-X. Audio and decode is fine, but not tune, transmit or frequency readout--most of the time.
Sometimes it works--but most of the time I get no rig control. I'm not sure why it sometimes connects and sometimes it doesn't. I have followed the instructions of KE8KYP Scott, but again it usually doesn't result in rig control. See my photos.
Iv'e tried first exiting FLDIGI, then starting sbitx from a terminal, even rebooting. The video syas "I don't need FLDIGI" and exits. Does FLDIGI interfere if it's running or does it not matter?
Any suggestions??
Jack, N6LN

Thanks Joerg, that's great info. I have in the past used a USB Sound Baster SB0490 into a laptop PC which is limited to 48kHz b/w - looks like yours is the same.
I was hoping to make a small package by using a top hat module for the Pi, and would like a greater receive bandwidth. I have got used to my AirSpy capturing the IF from an ICOM 7100. Looking at the I/Q o/p circuit of the RS-HFIQ, it looks like it has quite a wide b/w. I have an original R Pi touch screen display, so lots of kit already to make a compact box.
Let's see where this goes.
73
Tony

Mark,

Yes the Panadapter Board has the processor for the display on it.

So no need indeed. Bitbanging in userland is not an issue per se.

Is nobody else experiencing this tuning lag on a DE? It's driving me crazy, it takes me a few minutes of tuning past where I want to go to get where I want to be. While tuning slowly, the frequency display just stops and then starts up again only it goes right on by the spot I wanted to stop at, so I turn it back and then it stops again then starts back up and goes right on by where I wanted to stop again. This is very annoying and makes it very hard to use. Does anybody have any ideas what is causing this? It's not the Raspberry Pi 4, I installed a new one, same thing.

Joel
N6ALT

Hello Tony,

the sBitx RPi code will be of very limited use for the RS-HFIQ, as the RS-HFIQ delivers I/Q-audio signals and particularly expects I/Q-audio signals for the TX part.
The sBitx software processes just single channel (no I/Q) audio signals.

Instead you can use one of the available SDR/SDT software packages, to make the RS-HFIQ a fully functional transceiver.
I am running Quisk () on the Raspberry Pi with this overall architecture


For the bi-directional Audio stereo (I/Q-signals !) interfaces to the RS-HFIQ I am using either a Behringer UFO202 or UCA202 interface, which is in the €25 price range.
To interface to the microphone and the headset, I am using an additional low-cost USB Audio interface, which will be in the €5-15 price range.
I have been lucky, to find an interface which has 2 3.5mm connectors for the microphone and the headset. In addition it has a 4-pole 3.5mm connector for a combined smartphone headset.

For the display you can either use a standard HDMI monitor or you buy e.g. a 7" HDMI TFT-display with touch, that can be connected and power supplied through the raspberry.
I am using a display with a 1024*600 physical resolution, but which also accepts a full HD signal via HDMI.

With such a display, you would be able to operate Quisk, but it might be a bit challenging, as Quisk is not touch optimized.
I would recommend that you connect a mouse to the Raspberry via Bluetooth and with that you will be able to use the mouse wheel as the tuning knob.

For Quisk you will need a hardware configuration file "hardware_usbserial.py" for the RS-HFIQ, which you can find e.g. .
You will have to configure the audio interface in Quisk appropriately (in the UFO202 and UCA202 one audio channel is one cycle behind the other, which must be configured in Quisk) and then everything will work nicely.

I am using this configuration for quite some time now.
The nice thing is, that you can also fully remotely operate the Raspberry with a RealVNC client, that can even run on your smartphone or tablet.
Audio can be transported through Mumble. You can also run in parallel to Quisk WSJT-X on the Raspberry.

There are a lot o things, that can be done with this configuration and if you get over the initial hump, you will have learned a lot about Linux and its sound systems, hi.

It could finally look like this (without the 7" display but with a USB-C PD powerbank supplying the 12V for the RS-HFIQ and 5V for the Raspberry Pi and Audio and a passive USB hub):


Feel free to contact me, if you have any configuration questions.

--
73, Joerg - DB2OO

Thank you for the offer.? I do not use my DE portable, so I always have a network connection to sync time.? I have other projects pending, so I will put this on the back burner.

73
Evan
AC9TU

So you should get rid of the i2cbb.c in case you want system I2C. It is an easy change. I can help, in case you want RTC as system clock.

Rafael,

There are three devices on the DE i2cbb bus:
1 - The Si5351
2 - The RTC
3 - The SWR/PWR meter (if added)

I believe that the v2 is the same.? I do not have one to verify (I have found discrepancies on the DE schematics, so I do not trust the v2 schematics without a v2 for reference).

I am not sure that it is worth the effort to remove the i2cbb bus.? To have the RTC on the system, adding a third bus may be the easiest.

Again, thank you for the information.
73
Evan
AC9TU

I completely replaces i2cbb.c, unless you want to keep some i2c bitbanging for the Si5351A (are they in the same i2c bus?). What exactly is your setup in the DE? The RTC is in a different i2c bus than the Si5351A?

- Rafael

Hello Rafael,

Thank you for the information.? It will take me some time to digest it.

One quick question: Does this replace the i2cbb.c bus, or is it added to allow the RTC module to connect directly to the system?

73
Evan
AC9TU

Hi Evan,

I did here. Use this as reference:

I just removed fake_hwclock package here.