Thanks for this JJ, I have a friend with an sbitx and he is not really Linux literate so for users like him this is a big bonus from a user perspective.
I have slimmed down the pi menu a bit by removing some of the apps that are clearly not required on a radio (for me anyway), so not too worried about the number of menu additions for useful utilities like these
Paul G0KAO

The first QSO after switching on is written twice on the screen, while making a LOG file entry once.
The solution is to look into the LOG file after starting sbitx and then close it.
After that, everything goes normally.
If I don't open the LOG file and close it, it says on the screen twice at the first QSO that it was entered in the LOG.
In reality, it only appears once.
But it happened that he did not enter the data even once.

Maybe it's a permission issue to get into the LOG file?
I don't know the spiritual world of OS, I'm just thinking out loud.
--
Gyula HA3HZ

Very neat solutions and I like them. These tools are excellent for those who do not want to get involved in the mysteries of the OS.
I'm just thinking out loud that it wouldn't be possible to put these utilities in one package and get what you need from the menu.
The pi folder from the utilities will slowly become bigger than it was before. :-)
--
Gyula HA3HZ

I've added two more utility applications to the W9JES Enhancements installer.??

?sBITX EZ Tools : Applications to manage version upgrades/downgrades, configuration backups, and more.

There are two applications that have been developed to ease the trouble of upgrading and downgrading sBitx software and managing backups of your hardware settings and the entire sbitx folder.


-JJ

On Wed, Jan 24, 2024 at 06:57 PM, Rafael Diniz wrote:

I'm talking about gpio permission errors from wiringpi, that sometimes happen.

Thank you for the clarification.

I agree the wiringpi permission thing sometimes happens.

I had it one time and could not figure it out, but then it just went away.

I hope it stays away!
?
--
Regards,
Dave, N1AI

Nice!
Beautifully done case.

--
73
??? Bob? KD8CGH

Hi Dave,

I disabled double click in the image. I'm talking about gpio permission errors from wiringpi, that sometimes happen.

Hi,

Just released V2 of my sBitx case design. It now has mounting holes for a speaker (https://www.amazon.com/gp/product/B09R9WY9R6 and many other places) as well as support for Bob KD8CGH's tilting leg solution.



Available on thingiverse:


and my github

https://github.com/AJ6CU/3d-printer-models/tree/main/sBitx-v3-case

73
Mark

--
AJ6CU/7
KD8CEC 2.0, Nextion Screens,? and open source uBITX Raduino boards for Arduino IOT, BLE, RP2040, Teensy 4.0, and Raspberry Pi Pico
https://github.com/aj6cu

Bob,

Added support for your tilting legs to my 3d case for the sBitx.? Thanks for the work!

73
Mark

--
AJ6CU/7
KD8CEC 2.0, Nextion Screens,? and open source uBITX Raduino boards for Arduino IOT, BLE, RP2040, Teensy 4.0, and Raspberry Pi Pico
https://github.com/aj6cu

开云体育

You just need to change to a electret cartridge that has -24DB?

On Wed, Jan 24, 2024 at 11:23 AM, Paul wrote:

I would like to know the answer to this one too as I would love to be able to use my USB headset with the radio. However, I suspect this may not be easily achievable having had a brief play around as the audio primarily appears to be hardwired to deliver/accept audio to the sockets on the side of the radio or the physical speaker within (Arfan correct me please if I am wrong).
It may be possible using the loopback device capabilities but this seems a little complicated at first glance and needs some clearer description on how to route the audio from maybe one of the loopback devices to the USB or Bluetooth connected device.

?shows the usage of the sound devices from Linux's point of view:



Lines 72/73 show the hardware device is being used in an unconventional way, left channel for the receive path, right channel for the transmit path.

/g/BITX20/topic/103407266#107146?explains more via the documentation which is at?

The Sound System

The details of sound sytem are all hidden in. There are a few things to remember

1. The sampling rate is fixed at 96,000 samples per second. Each sample read or written to the hardware is a signed 32-bit integer. The audio hardware works in full duplex at all times.

2. The digital IF is centered on 24 KHz, staritng from 12.5 KHz to 37.5 KHz.

3. The left channel?is dedicated to receive. It gets its samples from the demodulator (Actually, the downconverter that moves the 40 MHz IF to 24 KHz, which is kind of “audio” range, handled by the audio codecs). After processing it writes the samples back to the?speaker.

4. The right channel?is dedicated to transmit. It gets its samples from the?mic, processes them and writes the transmit signal samples to the right channel.

Since this is the hard-wired setup, this is the starting point to work from.

My first coffee of the day hasn't fully kicked in yet, but my current thinking is this unconventional setup means you can't use conventional methods to attach a headset to the radio.

The 'sbitx' application has opened 'hw0' and there is no device sharing in ALSA.? There is mixing available but that's more overhead and complexity to deal with.

In theory you could use a program like 'sox' ( described in /g/BITX20/topic/103407266#107146?) to fill the role 'wsjt-x' is doing above i.e. take sound to/from a conventional device and read/write it to the loopback devices (hw1 and hw2) in a place where the 'sbitx' application expects it.? ?Or maybe you can configure ALSA/PulseAudio/PipeWire/whatever to do this.? Maybe someone else knows the answer to this, but I don't.

In theory the 'sbitx' application could do in voice mode what it does in digital mode, uses the loopback devices to read/write sound samples from external program/devices, but I don't think it is coded to do that right now.

Note that all this copying of samples within the application is really inefficient. Farhan has said that profiling shows this is where the CPU spends most of its time.? Ideally all these use cases would be examined to see if the could not be done more efficiently.? I think this is measured criticism.? The application works.? It largely does what its manual says it will do.? It stays within the performance envelope of the hardware.? It's just that there could very well be ways to do it more efficiently and provide more functionality without writing much more code.

My immediate approach is to work on getting a PC headset working via the connectors on the side of the radio at the moment using a splitter based approach that is wired from a small project box to house the TRRS connector that most PC headsets can use and the box has the PTT button on it as well. This approach works so far but the audio level on SSB is too low to get the power out of the radio (commented on many times elsewhere in the forum), this I am hoping to solve using a microphone pre-amplifier based on an SSM2167 module that I will fit into the radio, need to find a suitable 4-5v tapping point to power it - to be continued. will perhaps start a separate thread for this one once I have it sorted.? ?I would like to know though if it is possible to use either Bluetooth(built into the pi) or USB type headsets as it will add to the versatility of the radio especially for portable voice communications which is how I would like to primarily use this radio, Paul G0KAO

Until someone decides to investigate the software stuff I just wrote about above and finds, codes, tests and publishes a solution, I think going to external hardware will be needed.

I've been playing with Linux and SDR for a few years now, and I see the same thing over and over again: the radio stuff is easier than one thinks, and the audio stuff is MUCH harder than one thinks.? Most people say "I can play music and record music, it's got to be simple".? No, far from it.

This also supports the stuff I've been saying about the lack of maturity and completeness of the sbitx software and the lack of using best practices.? Wanting to use a wireless headset is a pretty normal thing these days.? ?We've seen inquiries about this for a while now.? It'd be nice if we were using something like Github Issues to track these requests and share ideas on how to satisfy them.? Having stuff show up on groups.io and being kicked around for a while is not a best practice. The afarhan repo has some open Issues but they don't seem to be getting much attention.? Being able to tag Issues as defect reports vs enhancement requests would be nice.? They won't get much attention till a larger developer community forms around this radio, but at least the information would be captured and available if/when someone is available to work on it.
?
--
Regards,
Dave, N1AI

I would like to know the answer to this one too as I would love to be able to use my USB headset with the radio. However, I suspect this may not be easily achievable having had a brief play around as the audio primarily appears to be hardwired to deliver/accept audio to the sockets on the side of the radio or the physical speaker within (Arfan correct me please if I am wrong).
It may be possible using the loopback device capabilities but this seems a little complicated at first glance and needs some clearer description on how to route the audio from maybe one of the loopback devices to the USB or Bluetooth connected device.
My immediate approach is to work on getting a PC headset working via the connectors on the side of the radio at the moment using a splitter based approach that is wired from a small project box to house the TRRS connector that most PC headsets can use and the box has the PTT button on it as well. This approach works so far but the audio level on SSB is too low to get the power out of the radio (commented on many times elsewhere in the forum), this I am hoping to solve using a microphone pre-amplifier based on an SSM2167 module that I will fit into the radio, need to find a suitable 4-5v tapping point to power it - to be continued. will perhaps start a separate thread for this one once I have it sorted. I would like to know though if it is possible to use either Bluetooth(built into the pi) or USB type headsets as it will add to the versatility of the radio especially for portable voice communications which is how I would like to primarily use this radio, Paul G0KAO

Re the wireless headset question - I would like to know the answer to this one too as I would love to be able to use my USB headset with the radio. However, I suspect this may not be easily achievable having had a brief play around as the audio primarily appears to be hardwired to deliver/accept audio to the sockets on the side of the radio or the physical speaker within (Arfan correct me please if I am wrong).
It may be possible using the loopback device capabilities but this seems a little complicated at first glance and needs some clearer description on how to route the audio from maybe one of the loopback devices to the USB or Bluetooth connected device.
My immediate approach is to work on getting a PC headset working via the connectors on the side of the radio at the moment using a splitter based approach that is wired from a small project box to house the TRRS connector that most PC headsets can use and the box has the PTT button on it as well. This approach works so far but the audio level on SSB is too low to get the power out of the radio (commented on many times elsewhere in the forum), this I am hoping to solve using a microphone pre-amplifier based on an SSM2167 module that I will fit into the radio, need to find a suitable 4-5v tapping point to power it - to be continued. will perhaps start a separate thread for this one once I have it sorted. I would like to know though if it is possible to use either Bluetooth(built into the pi) or USB type headsets as it will add to the versatility of the radio especially for portable voice communications which is how I would like to primarily use this radio, Paul G0KAO

On Wed, Jan 24, 2024 at 03:41 AM, Rafael Diniz wrote:

It is "normal" if Farhan's sbitx does not open first tap

The intention is to have open on first tap so that the touchscreen is easier to use.

says:


?
--
Regards,
Dave, N1AI

Ashhar
? For such an large change I don't think just a leg angle change would work. I think you would have to shorten the legs quite a bit. I think you would need a design for that angle.
? To get a lot of angle adjustment I think you would have to leave the compact, portable, case attached design and go to something that looks more like my first desktop design.


--
73
??? Bob? KD8CGH

While I plan on eventually using a printed tilt stand, I'm currently using a folding laptop stand. It's actually pretty nice, with many tilt adjustment points. No matter how it's positioned, the sBitx heat sink causes the radio to sit a bit lop-sided in it, but it's still stable and works well.


I bought mine locally (at a grocery store, of all places), but ebay & other sites have the same:

Btw, when doing a git pull in the image I did, please use (inside /home/pi/sbitx):
git pull --rebase

I had to rebase my fork, which contains the same code of upstream's Farhan sbitx, but with fixed build system[1].

[1] PR:

- Rafael

Hi Hank,

I'm not sure what it could be. Are you using the sBitx with a Pi 4?

It is "normal" if Farhan's sbitx does not open first tap, as there are some permission / udev issues which will be solved when we run everything as root (gpiolib needs root anyway, so the path is really to run the software as superuser).

- Rafael

On Wed, Jan 24, 2024 at 12:28 AM, Hank Beisheim wrote:

The desktop shortcut does not directly open sbitx. It asks to execute etc first.

From one of my notes files:


?
--
Regards,
Dave, N1AI