开云体育

I know this is a stupid question but how to I install the V2 software in the V1 DE. I have SN: 0053 which I just took out of the box. I intend to purchase a V2 board in the near future.

Dan KD3CEU

Hi Dan;

I just did this with my DE this afternoon - the new web based GUI is happily running on my DE right now, receiving lots of FT-8 signals on 20 meters.

Recommend trying the radio for at least a short time using the original software / image, just to make sure everything is basically working, and to establish an internet connection to your sBitx.

I started the process with a fresh sBitx image burned to a 128 GB MicroSD card using Balena Etcher running on Linux. Pop the MicroSD card into the Raspberry Pi, confirm that it boots, and that you can start the sBitx application and hear signals.

You will also want to have a USB keyboard and USB mouse plugged into the Raspberry Pi. I use a wireless keyboard and mouse.

Close the sBitx program if you still have it open.

Open a terminal window, and cd into the sbitx directory:? cd sbitx

cd into the data directory: cd data

Move the user_settings.ini file:? mv user_settings.ini user_settings.ini.bak

go back up to the sbitx directory:? cd ..

Run the update script - note there's a period before the forward slash - it's required:?? ./update

Open up the install.txt file for reference:? geany install.txt &

The install.txt file will be displayed, and you will still be able to enter commands into the terminal.
Since the image has already been configured to run the legacy sbitx application, you can skip most of the steps in install.txt.

Update the apt database to the latest by entering the command below in the terminal. When asked for the password, it's hf12345:
sudo apt update

Drop down to step #8 of the install.txt file and run the two commands shown in the terminal:
sudo apt install ntp
sudo apt install ntpstat

Run the commands in step #9:
sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8080
sudo iptables -t nat -I OUTPUT -p tcp -d 127.0.0.1 --dport 80 -j REDIRECT --to-ports 8080
sudo apt-get install iptables-persistent --fix-missing

Run the commands in step #11. You can skip the update command because you did that earlier:
sudo apt install sqlite3
sudo apt install libsqlite3-dev

Go back into the data directory and create the log database:
cd data
sqlite3 < create_db.sql

Now it's time to build the new sbitx application. Go back up one directory level to the sbitx directory:
cd ..

Build the new sbitx application. Be sure to put the period before the forward slash in the command below:
./build sbitx

One more step - in order to be consistent with how web access commands work, you will want to change the name of raspberry pi computer from raspberrypi to sbitx. The easy way to do that is from the desktop.
Click on the raspberry in the top left corner of the desktop, and scroll down to Preferences.
In Preferences, select Raspberry Pi Configuration. A Raspberry Pi Configuration window will open.
Select the System tab. It will probably be selected when the Raspberry Pi Configuration window is opened.
Look for the Hostname option. and change the entry from raspberrypi to sbitx. Select the OK box in the bottom right corner of the window.
A popup will appear telling you that the changes you have made require the Raspberry Pi to be rebooted to take effect, and asking if you would like to reboot now. Select No.

You can now try launching your new sbitx application from the terminal window. Once again, the period before the forward slash is important.:
./sbitx

After a few seconds, and with a little luck you will see a screen that looks almost exactly like the legacy sbitx program. Give it 10 seconds or so, and you'll see a web browser open.

The browser will request a pass key. Note the instructions provided on the web page, and use 123 initially. Select the Blue "Start" button to continue.

You can then create a new pass key to secure access to the sBitx control webpage.

Play, enjoy your new V2 software!

Then press escape or tap the up/down arrows in the top right corner to get to the browser window controls, and tap the X in the right corner to close the browser window.

You'll see the legacy sbitx screen has been running in the background. Tap the X in the top right corner to close it.

Now reboot your sbitx, When you're back to the desktop, start the sbitx application again, and when the browser opens, enter your new passkey when requested, and click on the blue "Start" button.

Now you can see what all this was for! Go to another computer on your network, and enter into the url field:
sbitx.local:8080

You should see a familiar screen asking for your passkey. Enter your passkey and click on the blue "Start" button.

If all went well, you will now be in control of your sBitx from a remote browser, and you will hear audio as well!

Hope these instructions help. I've probably made a mistake or two in capturing these instructions, so holler if you have problems.

73; Steve, N3SB

Hi Steve,

I also have a V1 DE and I have a question for you. Would you mind posting a copy of your image or explaining in detail how you made the image?

Thank you in advance,

Robert, AG6LK

Steve,

???? Thank you. Now I realize what my problem is. I'm not running a sBitx image. I purchased this radio from another ham who did not finish the kit. I'll start over with a new image.

Dan KD3CEU

?

Hi Robert;

Have a look at

There you will find a link to the Raspberry Pi image containing the legacy sBitx program, as well as a link to the raspberrypi.com website with instructions on how to burn that image to a microsd card using Raspberry Pi Imager, which is available for Windows, Mac, and Linux,

From there you can update to the latest sBitx program using the instructions I posted yesterday.

There -may- be a way to capture those steps into a script that just does it all with one command. I'll see if I can come up with something. Do note that most of the commands I posted came right out of Farhan's install.text file that will be in the sbitx directory when you run ./update so you can open the install.txt file in geany, and highlight the commands one at a time and copy them (i just use the control-c key combination) then past them into the terminal window using the shift-control-v combination, or selecting edit --> paste at the top of the terminal window.

One thing I always do with these images is turn off the pulse audio multicast function. This seems to be the default behavior for the raspberry pi OS, and it generates a lot of needless network traffic. Using WiFi it's enough traffic to severely degrade the network. The function can be turned off at the raspberry pi by running the paprefs command, then selecting the Multicast/RTP tab, then clicking to remove the checkmark next to Enable Multicast/RTP sender.

73; Steve, N3SB

On Sun, Apr 30, 2023 at 02:33 AM, Robert AG6LK wrote:

Hi Steve,

I also have a V1 DE and I have a question for you. Would you mind posting a copy of your image or explaining in detail how you made the image?

Thank you in advance,

Robert, AG6LK

Robert,

???? I guess I was tired last night. When I searched the forum this morning I found it no problem.

/g/BITX20/wiki#sBITX-Topics

Dan KD3CEU

Hi Steve,
This works great! Thanks so much for posting these instructions.?
--
Bob AA4FJ

Hi Steve,

thank you for all the information. I’ll get right on it, I truly appreciate it.

73, thank you again,
Robert, AG6LK

Steve,

???? Thanx for the info. I was able to install the software and getting it running due to your instructions. WooHoo!!!

?

Dan KD3CEU

?

Steve, prior to making this post I have tried your steps to put the downloaded image starting with a the 1.0 image from the VU2ESE website and upgrading per your detailed instructions. I can't get my sBitx Developer's Edition to start the sbitx program. I stop the lingering Fldigi program each time too.
could you please take a look at my output error text and perhaps suggest what to do next?
At this point I can't even find an old image that still works.

Jack
N6LN

Jack - it looks like your loopback devices may not be set up.

From a terminal, type:

aplay -l | grep Loopback

You -should- see three cards listed, #1 thru #3, with two devices for each, numbered 0 and 1, for a total of six.

If you don't see those devices, try a system reboot first.

If that does not work, then refer to Step #5 "INSTALLING LOOPBACK" in the install.txt file that's in the sbitx directory.

73; Steve, N3SB

On Sun, May 14, 2023 at 08:34 AM, Steve Beckman wrote:
Jack - it looks like your loopback devices may not be set up.

From a terminal, type:

aplay -l | grep Loopback

You -should- see three cards listed, #1 thru #3, with two devices for each, numbered 0 and 1, for a total of six.

If you don't see those devices, try a system reboot first.

If that does not work, then refer to Step #5 "INSTALLING LOOPBACK" in the install.txt file that's in the sbitx directory.

73; Steve, N3SB

////////////

Steve, I of course have rebooted. And sudo modprobe snd-aloop enable=1,1,1 index=1,2,3 is in /etc/rc.local.
I've followed all the steps and the changes in /boot/config.txt.
here is the output from aplay -l and again the error msgs from ./sbitx. Still no luck.

Jack
N6LN

Jack - what result do you get from the groups command?

Are you able to start alsamixer from the command line? If so, what result do you get when you press the F6 function key?

73; Steve, N3SB

what is the groups command? How can I start the alsamixer from the command line? I'll let you know shortly what happens when I press the F6 key, but what does that do?
Jack
N6LN

Jack - the groups command will list the groups that the user running the command is a member of. Just enter "groups" without the quotes in a terminal window.

The alsamixer command is also a command entered into the terminal window. For now, skip it.

All the ALSA error messages are coming from fldigi. However your logfile isn't showing a "normal" startup for fldigi.

What result do you get from the command ls ~/.fldigi?? ??

73; Steve, N3SB

Here is what I get when I start alsamixer.
Jack
N6LN

Jack - going back through the forum archives - I see that you are sending the error messages to a logfile when you start the sbitx application.

Unfortunately there are lots of other helpful debug messages that are not sent to the stderr stream when sbitx is started. Those messages would be helpful in troubleshooting your issue. I think the ALSA error messages are a red herring. Al the other messages from fldigi that I was expecting to see in your logfile don't end up there because those messages are sent to stdout not stderr, so they don't get redirected to the logfile.

If you change the mode to 2TONE, turn the drive down all the way, then key the transmitter, do you hear the two tones in the speaker?

73; Steve, N3SB

Steve, here is the list of groups by the groups command,
and also ~/.fldigi doesn't work. nor ./fldigi. But plain fldigi does start. All I hear is the wifi buzz (haven't disabled it yet in this sd card's /boot/config.txt) but other than that, silence.
I couldn't get a .txt output from starting fldigi by fldigi 2>&1 | tee flgigioutput.txt so I took screenshots 1 through 5 of the output.
Also I did a screenshot of the configuration window in the audio tab of fldigi.

I hope this is helpful information!
73,
Jack
N6LN

Those screenshots look too small, so I converted them to pdf files which can be enlarged on a browser.
Jack N6LN

Steve, I restarts the sbitx program (without a reboot) and it came alive with audio, and finally with 2tone audio (it was silent before). And with drive increase I got a maximum 2-tone output of 6 (six) watts out to a dummy load.
I didn't change anything. Somehow it works now. all I did was run fldigi alone.
I attached a .txt file of the output when it was called with ./sbitx. Running ./sbitx still runs and works by restarting the program without a reboot.

Is there any clue in the txt files about what happened? I have heard others saying that sometimes it works, and sometimes it doesn't.
Jack
N6LN