On Tue, Jan 9, 2024 at 11:44 PM, JerryP wrote:

I couldn't get dual HDMI monitors to work so I had to comment out the dtoverlay=vc4-kms-v3d line in config.txt. Otherwise, sbitx would not run because of the dreaded simple.c error from alsa sound. It probably has to do with HDMI audio being available on the monitor but I don't know enough about the alsa sound system to fix it.

On Wed, Jan 10, 2024 at 08:13 AM, Rafael Diniz wrote:

Use this, Jerry:

dtoverlay=vc4-kms-v3d,noaudio

I believe the problem is that the sbitx_sound.c code uses the generic device name 'hw:0,0' assuming that it is the sound card for the radio data input/output.? This means you can't let other sound devices that may appear earlier claim that name.? The video stack loads incredibly early so it wins.? The simple.c assertion happens because the sbitx code is trying to set up a mixer device on top of HDMI audio instead of our codec and that doesn't work.?

The change Rafael gave tell the video stack to not enable HDMI audio so it doesn't claim that name.? I have some code that uses specific names so we don't have to disable HDMI audio in the future.? I'll do a PR at some point in the future when things quiet down.? If someone else fixes it first, that's fine by me.

My /boot/config.txt also comments out?dtparam=audio=on which disables the headphone jack audio.? I forget if this is mandatory or if it is something I did when I was trying out various other things.?

I believe that what Rafael says is correct, these issues aren't specific to Bookworm.?

--
Regards,
Dave, N1AI

Just upgraded to v3.02 - log DB (sbitx.db) no longer updated with new contacts.? How is the log managed now?
--
Mike WB5LLI

Could this be fixed with a 9T:2T transformer between C63 and the mixer pad, and rebiasing Q6 for a gain of 2-3?

And/or, could someone flesh out the emitter follower and specify which parts from the emitter of Q6 should be removed? (Just C62 and R64?)

? ?Thanks!
? ? ?73, Andy, KG5RKP/MM

@JJ-W9JES that did the trick, thank you!

Thanks Peter. I am glad you are enjoying it.


I also forgot to update the screen size for sBITX-Scanner from the Windows version. I fixed it on the repo. if you have it installed already, then go to the home/pi/sBITX-Scanner folder and rerun the installer. It will grab the changes and push them down.?


-JJ

Thanks JJ, I really like your screen brightness control app.
--

Pete VK3PYE

I tried to run an update by running ./update and ran into this error:

Sun 21 Jan 2024 03:25:06 PM MST Updating 7abd77d..a60313c error: Your local changes to the following files would be overwritten by merge:???????? sbitx Please commit your changes or stash them before you merge. Aborting

I also tried sudo ./update, and same result.? I'm running v3.0

When you see the error, type git stash then rerun the update

I tried to run an update by running ./update and ran into this error:

Sun 21 Jan 2024 03:25:06 PM MST Updating 7abd77d..a60313c error: Your local changes to the following files would be overwritten by merge:???????? sbitx Please commit your changes or stash them before you merge. Aborting

I also tried sudo ./update, and same result.? I'm running v3.0

On Sat, Jan 20, 2024 at 09:31 PM, Ashhar Farhan wrote:

Ok, here are a few comments:

I will offer what I think is constructive feedback, and hope it will be accepted as such.

1. The only tried and tested operating system for sbitx is 32 bit operating system. Those trying the 64 bit versions are encouraged to do so at their own risk. We will eventually move to 32 bits but the updates are tested on the operating system provided on the sd card - the 32 bit buster.

Re: At our own risk: The hfsignals.com web site makes it clear that after thirty days there is no support other than community-based efforts and points to this forum as the main location to interact with the community.

Re: Buster: Buster is Debian 10, two releases old, first released in 2019.? ?Security updates ended in 2022.? Long-term support ends in a few months.? It's definitely time to move on to something newer.

Re: 64 bits:? Support for a 64-bit OS for Pi has been mainstream since Debian 11 ( Bullseye, 2021 ) which has already been succeeded by Debian 12 ( Bookworm, 2023 ).? Windows dropped support for 32-bit machines in 2020 and new smartphone ARM cores have dropped 32-bit OS support since last year.? ?They may have some ability to run 32-bit apps, but that is fading away fast as well.? Linux itself has had 64-bit support since the 1990s and runs on everything from phones to supercomputers, so it is very mature and robust.? Most apps benefit from processing data 64 bits at a time and using instructions and registers that don't exist in 32-bit mode.? ?Dropping support for 32-bit mode makes CPUs cheaper and faster, so the trend will accelerate.

2. The sbitx does everything that the ic 705 does with the same stability. It is the things that no other radio does (like keyboard macros and logging) that are at a higher level that any other radios, those continue to report errors.

I agree the sbitx is more innovative than IC-705.? You should be congratulated and celebrated for that. I certainly want the innovation to continue.? I'm willing to put up with bugs as a side effect of innovation.??

I think the integration of FT8 as a first-class citizen is a wonderful idea. I personally like the large touchscreen and its UI, including its on-screen keyboard and macro support, and hope that it continues to be developed.?

I have purchased two sbitx radios.? I could have bought a IC-705 instead but did not.? I respect and admire your work.? I am using my dollars and my time to support your work.? I respect and admire you as a person.? ?I think the project shows your decades-long experience at work after creating several innovative radios from scratch.

I introduced the IC-705 to show an example of high-quality release notes.

I'm not sure what kind of stability you are referring to.? I would suggest the IC-705 software is more robust than the sbitx software and suggest that the recent bug fixes pretty much prove that point.? I doubt Icom has ever released hallucinating FFT software, if not it's been a very long time.

I am concerned about the sbitx software's robustness and pace of development.? Whatever unique ideas you have will probably get copied soon enough.? It feels to me like we are months behind where we could be if bug fixes and functional improvements were being taken in efficiently.? It feels to me some have walked away from this product both as customers and developers due to concerns about software completeness, robustness, and pace of development.? Yet I feel much of this can be improved dramatically, and am hopeful that it will be.

3. There will be many edge cases like turning the taskbar on/off or using other on-screen keyboards like the matchbox, etc., that will continue to throw up errors.

This is why software-intense commercial products are expensive.? It takes a robust software team to find fixes for edge cases and deliver them to customers in a timely fashion and in a format that they can use without disrupting their current setup. Most of these people want to be paid, thus the cost.? It's no secret that most of the key Linux developers are being paid to work on Linux one way or the other.? It's a real challenge in the hobbyist space to keep up with that kind of effort.? It is why we need to adopt the best practices sooner rather than later.

4. The 3.02 software is not yet a release. We do not have a release cycle yet. V3.0 is the stable software for those who just need a radio that works.

It's very hard for end users to understand what is a release and what is not a release.? This V3.02 thread started with "I urge you all to run an update and enjoy the better version" which sounds like a release to most people.? The git repo has no tags to indicate what the releases are.? ?The github release facility is not being used.? Git branching is not being used.? Release notes similar to the ones I showed for IC-705 are not being issued.? Upgrade and downgrade strategies are not being documented consistently and effectively.? IMO this thread provides several examples of why these areas need attention.
?
--
Regards,
Dave, N1AI

Bravo Dave - Your comments are spot on and I agree 100% with your suggestions and observations.?

On a side note.. I chuckled with the OP's comparison to the IC-705 since I currently own one of those as well. It seems like a grossly miscalculated statement to compare the sBitx to the Icom.


- JJ

On Sun, Jan 21, 2024 at 03:58 PM, Mark Hatch wrote:

Thanks for the recommendations! I had actually printed a longer leg for my kx2 several years back. It seemed strong enough.? I was actually thinking of two legs, one on either side that had a crossbar attachment (think of an "H"). Having two unconnected legs is a real pain on flat surfaces as they are never aligned and the radio wables. On the otherhand, there are advantages to that for pota applications because surfaces are never flat...? Easy to make the crossbar an optional piece..

I think the H concept is good, but I'll have to see an image when one becomes available (no rush at all).

I haven't seen the Elecraft setup so I don't know what it looks like ( I know, how could I have lived this long without seeing that ? ).

Something that can tuck away is important for POTA, my V2 radio lives in a backpack.?

The current legs work quite well but are a bit problematic in terms of being kept in a backpack, I'm afraid they will break since they don't store flat.

One of my favorite radios ever had a U-shaped handle, but it could not double as a stand, although I have seen some that can.

Below is an image of that radio, for the nostalgic among us.?

My dad had one when I was a kid, and I stole it a lot because it could pick up the "beat frequency" of the local two meter FM repeater on its public service band!

I found some on eBay a few years ago, bought one for me and my brother so we could think warm thoughts about our late father.

?

?
--
Regards,
Dave, N1AI

Hello.

I created another app based on a request for the sBitx platform.

• Provides a user-friendly interface for interacting with the sBITX transceiver
• Enables user input for defining the frequency range, tuning step, and wait time
• Bidirectional Scan by defining the start and end frequencies means you can scan up or down
• Continuous Loop scanning in the defined range
• Pause allows the user to pause the scan function
• Displays the current frequency being scanned to aid in identifying RF activity
• Background color can be changed for better readability and visibility

There is also a Windows version..



I also created an AIO installer for the apps that I developed.





I've also added uninstallers to the individual apps and the AIO app.



- JJ

Dave,

Thanks for the recommendations! I had actually printed a longer leg for my kx2 several years back. It seemed strong enough.? I was actually thinking of two legs, one on either side that had a crossbar attachment (think of an "H"). Having two unconnected legs is a real pain on flat surfaces as they are never aligned and the radio wables. On the otherhand, there are advantages to that for pota applications because surfaces are never flat...? Easy to make the crossbar an optional piece..

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

Ashar,

Clearing the PRs is good. was watching Mark Erbaugh's github as he seemed to be workng his way through a lot of the siignal processing code and cleaning things up a bit. But, he never made any pull requests so you didn't geet any of those. t seems too bad to not try to include some of that work!

His repo is at

--
Mike KB2ML

I don't know if this helps, but:

• Link to my earlier thread on sbitx mechanicals and batteries

I looked for the link to the legs someone bolted to the heatsink but came up empty.

--
Regards,
Dave, N1AI

On Sun, Jan 21, 2024 at 02:35 PM, Gerald Sherman wrote:

Dave - your idea of a leanable case is an excellent idea.? I have a few other QRP radios, and some of them have leaning cases.? Perhaps adding legs to the existing case somehow?

It was Mark's idea first -- "I also want to add a brace -- like what Elecraft provides for their KX2/KX3 -- so the sBitx can tilt back slightly."

There are a few ideas I've seen on this group too.? There are the 3D printed legs that were posted here that I had printed, and some have simply drilled holes in the heat sink and used that to secure legs that let the radio lean.

Since you mentioned batteries, perhaps those who have used them would like to comment on battery capacity and operating time per charge.? Might be interesting for new users.

Battery tech is a deep topic and I am a total newbie when it comes to battery topics.

Having said that, I purchased?, they were a good value at the time of purchase, and having a spare seemed like a good idea to me.

I haven't operated with them long enough to quantify their longevity other than to say they lasted for a couple two-hour POTA outings and that's about as long as I want to operate.

I used "industrial velcro" to attach them right to the area above the heat sink on back of the sbitx.

The power lead is long enough to reach the sbitx's jack so they worked out nicely for my sbitx POTA setup.
?
--
Regards,
Dave, N1AI

Vhf version of sbitx??has some interesting thoughts from Farhan and others on this group.

?may also be of interest.

I first found out about sbitx via "Solder Smoke",??.?

--
Regards,
Dave, N1AI

开云体育

Dave - your idea of a leanable case is an excellent idea.? I have a few other QRP radios, and some of them have leaning cases.? Perhaps adding legs to the existing case somehow?

Since you mentioned batteries, perhaps those who have used them would like to comment on battery capacity and operating time per charge.? Might be interesting for new users.

Gerry Sherman

Sent by the Windows 11 Thunderbird