I did the same thing, installed the excellent 64bit enhanced V3 image, it ran fine. Updated the linux (146 updates) then sbitx would no longer start.

Here's what happens when we try sbitx:

root@sbitx:/home/pi# cd sbitx
root@sbitx:/home/pi/sbitx# ./sbitx
sbitx v3.02
Unable to load ~/sbitx/data/hw_settings.ini
Loading default_hw_settings.ini instead
synchronised to unspecified at stratum 4?
? ?time correct to within 61 ms
? ?polling server every 512 s
Checking for valid NTP time ...Syncing RTC to 2024-06-01 15:40:00
Mode: LSB
Mode: LSB
Mode: USB
Unable to load ~/sbitx/data/user_settings.ini
Loading default.ini instead
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
Unable to save /root/sbitx/data/user_settings.ini : No such file or directory
root@sbitx:/home/pi/sbitx#?

Now, the first time I did all this yesterday, I also tried to update with

cd ~/sbitx
./update

And clicking the sbitx icon didn't do anything anymore.?

I'm not terribly linux proficient, but this is my experience.?

This minor glitch notwithstanding, I really appreciate your work on this!

73,

Chuck? W9MDO/VE1MDO/4E1MDO


?

On Sat, Jun 1, 2024 at 06:53 AM, Bruce W4BRU wrote:

Thanks for the quick response, JJ. Here's what I got.

~/sbitx $ ./sbitx
sbitx v3.02
gpio: Unable to open GPIO direction interface for pin 17: No such file or directory
wiringPiISR: unable to open /sys/class/gpio/gpio17/value: No such file or directory
pi@sbitx:~/sbitx $?

73, Bruce, W4BRU

Ok thanks for sending that. Something in wiringPi was overwritten or a function is missing.

You can try this in terminal to resolve the issues.

cd $HOME
sudo rm -rf WiringPi/
cd $HOME
git clone https://github.com/WiringPi/WiringPi.git
cd WiringPi
./build

then? reboot.


-JJ

I got into where you said but there is no sbitx folder or shortcut I have less than 15 min on this thing and I am not impressed especially if I can't start the radio?

On Sat, Jun 1, 2024 at 09:09 AM, Bruce W4BRU wrote:

On a plain Pi I know how to control display sizes but things seem different with the sBitX version. I don't know if your screen-size manipulation is affected by 32- or 64-bit versions. I'm currently trying JJ's 64-bit version with Toolbox? that is not going so well for me. If I cannot get that going by June 7 I'll revert to 32-bit V3 code. I intend to play radio with the sBitX at the beach!

73, Bruce

I am curious to know of the problems you have with the 64 bit version? What type of issues are you having? It is difficult to improve my product without honest feedback :(

The sBitx behaves similar to any other Pi with a DSI display connected. Some manipulation is required to connect an external HDMI display while using the built-in DSI display on ANY Pi.

Here are some references found on the Wiki page that may help. /g/BITX20/topic/99957650 /g/BITX20/topic/sbitx_v2_external_monitor/99966620?


Another way to effectively use the sBix is by utilizing the VNC connection option over wireless so you don't have to worry about cables. The VNC connection pairs well with the screen resizer in Toolbox. It is available for Windows, MacOS, Linux, and Pi.

Here is how to utilize VNC (Sorry for the scribbles, I had hand surgery on Wednesday)













-JJ

开云体育

I realized this morning that this question had been asked before.. in my defense it was 3am when I posted that…
Any direction to the portion of code that handles that would be greatly appreciated.?

On Fri, May 31, 2024 at 12:17 PM, HA3HZ wrote:

Thank you, Gyula, I will try it.

How did you get the increased content on your HDMI large screen example? The holiday beach condo has a large screen TV with HDMI connection, I have the cable for a second display, and it works well. On a plain Pi I know how to control display sizes but things seem different with the sBitX version. I don't know if your screen-size manipulation is affected by 32- or 64-bit versions. I'm currently trying JJ's 64-bit version with Toolbox? that is not going so well for me. If I cannot get that going by June 7 I'll revert to 32-bit V3 code. I intend to play radio with the sBitX at the beach!

73, Bruce

Thanks, Margaret.

73, Bruce

Thanks for the quick response, JJ. Here's what I got.

~/sbitx $ ./sbitx
sbitx v3.02
gpio: Unable to open GPIO direction interface for pin 17: No such file or directory
wiringPiISR: unable to open /sys/class/gpio/gpio17/value: No such file or directory
pi@sbitx:~/sbitx $?

73, Bruce, W4BRU

The difference of taking TX from pin 2 to 74LS08 (5v) and exiting Q9 (12V)? makes a delay Q10,Q101 and Q9?

If my information is correct, this sealed box contains the same circuit that is installed here. The difference is that the metal box shields the 150 kHz. Since the box cannot be opened without destroying it, identification is not easy. If someone sacrifices a piece and unwraps it, we know more. It follows from the pricing that the closed Drock buck converter is increased by the price of the metal housing and mass.
Hopefully the EN pin is boosted to Vin with a 100k resistor, as the IC documentation refers to.
--
Gyula HA3HZ

Carlo,

Gordon KX4Z dealt with the topic, you can find his description here.
Make sure the disconnection is correct.
--
Gyula HA3HZ

ps.: If you don't know how to do this, I'll describe it:
You start the File Manager, then find the sBitx icon in the /usr/share/applications folder, which you select for copying.
After that, go to the /home/pi/ Desktop folder and paste the icon here.
Programmers would certainly do this from a terminal. This is an easy way to put any icon on the Desktop.
--
Gyula HA3HZ

Hey gang I haven't started the deep dive yet, But I am looking for any way to narrow the TX bandwidth under digital mode.

The low/high settings work great for RX, but to be a good steward I'd like to see about tightening up the TX side too.?
Is this an available setting via Telnet? Or worst case a tweak to the code somewhere?

Thanks!

-Jon
W2JON

Try running it from the terminal:
cd sbitx
./sbitx
If it starts up fine, then your icon file is damaged.
The error message also says this. It points to an unknown path for me.
If you know the File Manager, you can fix it so that the correct icon is on the Desktop.
--
Gyula HA3HZ