Keyboard Shortcuts
Likes
- BITX20
- Messages
Search
Re: SBITX v3 - Ability to use a Headset for phone modes
Paul
A little progress made to solve a bit of a thorny issue regarding what happens when the sbitx is rebooted when a usb device is connected like a headset. Sorry bit of a long post, but it needs to be.
Not much point in connecting things up if a reboot changes the order of devices, this has involved a fair amount of learning and research but hopefully it has been worth it.
I have now updated the /etc/rc.local file to create/amend the number of Loopback devices available: modprobe snd-aloop enable=1,1,1,1 index=1,2,3,4
(If you are not interested in connecting other headset devices e.g. USB or Bluetooth, I would amend this line to read modprobe snd-aloop enable=1,1 index=1,2 to remove the unwanted Loopback_2 interface to keep things simple and tidy.) Using this update creates 4 loopback interfaces so that when cat /proc/asound/cards is run you get a list of the available sound cards: pi@sbitx:~ $ cat /proc/asound/cards
?0 [audioinjectorpi]: audioinjector-p - audioinjector-pi-soundcard
? ? ? ? ? ? ? ? ? ? ? audioinjector-pi-soundcard
?1 [Loopback? ? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 1
?2 [Loopback_1? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 2
?3 [Loopback_2? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 3
?4 [Loopback_3? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 4
We know that audioinjectorpi (card 0) is used for the sbitx audio I/O We know that Loopback (card 1) is used for the output to digital software such as JTDX, FLDIGI etc. We know that Loopback_1 (card 2) is used as the capture interface from the digital software such as JTDX, FLDIGI etc. As delivered Loopback_2 (card 3) is not used for anything (that I can find anyway) So to mirror the digital audio I/O I created an additional Loopback interface using the update to /etc/rc.local Now for the device order problem: when I connected the USB headset after powering on the radio it would appear at the end of the list using cat /proc/asound/cards: pi@sbitx:~ $ cat /proc/asound/cards
?0 [audioinjectorpi]: audioinjector-p - audioinjector-pi-soundcard
? ? ? ? ? ? ? ? ? ? ? audioinjector-pi-soundcard
?1 [Loopback? ? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 1
?2 [Loopback_1? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 2
?3 [Loopback_2? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 3
?4 [Loopback_3? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 4
?5 [II? ? ? ? ? ? ?]: USB-Audio - Jabra EVOLVE 30 II
? ? ? ? ? ? ? ? ? ? ? GN Audio A/S Jabra EVOLVE 30 II at usb-0000:01:00.0-1.1, full speed
pi@sbitx:~ $?
However if I rebooted the radio with the USB device still connected then the listing would look like? pi@sbitx:~ $ pactl list cards short 54??????????????alsa_card.usb-GN_Audio_A_S_Jabra_EVOLVE_30_II_0000F358FA9E07-00????????????alsa 55??????????????alsa_card.platform-soc_sound??????????????????alsa 56??????????????alsa_card.platform-snd_aloop.2???????????????alsa 57??????????????alsa_card.platform-snd_aloop.1???????????????alsa pi@sbitx:~ $ NOTE the different command used, still achieves the same thing and this was being used before I got to my solution. The issue here is that the USB device is now top of the ordered list and prevents sbitx from accessing the audioinjectorpi card because the USB device is now hw:0,0 instead of the audioinjector pi device. Note also that a Loopback interface has also disappeared!if I unplug the USB device and reboot the correct order is resumed : pi@sbitx:~ $ pactl list cards short 54????????????? alsa_card.platform-soc_sound????????????????? alsa 55????????????? alsa_card.platform-snd_aloop.2?????????????? alsa 56????????????? alsa_card.platform-snd_aloop.0?????????????? alsa 57????????????? alsa_card.platform-snd_aloop.1?????????????? alsa pi@sbitx:~ $ connect headset: pi@sbitx:~ $ pactl list cards short 54????????????? alsa_card.platform-soc_sound????????????????? alsa 55????????????? alsa_card.platform-snd_aloop.2?????????????? alsa 56????????????? alsa_card.platform-snd_aloop.0?????????????? alsa 57????????????? alsa_card.platform-snd_aloop.1?????????????? alsa 106?????????? alsa_card.usb-GN_Audio_A_S_Jabra_EVOLVE_30_II_0000F358FA9E07-00??????????? alsa pi@sbitx:~ $ Reboot again with the headset connected just to prove the point: pi@sbitx:~ $ pactl list cards short 54????????????? alsa_card.usb-GN_Audio_A_S_Jabra_EVOLVE_30_II_0000F358FA9E07-00??????????? alsa 55????????????? alsa_card.platform-soc_sound????????????????? alsa 56????????????? alsa_card.platform-snd_aloop.2?????????????? alsa 57????????????? alsa_card.platform-snd_aloop.1?????????????? alsa pi@sbitx:~ $ After headscratching, extensive use of Google and testing and retesting here is the solution: In order to consistently achieve a correct order of devices a couple of commands were used to determine device names, note that I am totally focussed on using ALSA here to minimise complexity. What we need to achieve is this order whenever the device is rebooted: pi@sbitx:~ $ cat /proc/asound/modules
?0 (efault)
?1 snd_aloop
?2 snd_aloop
?3 snd_aloop
?4 snd_aloop
?5 snd_usb_audio
pi@sbitx:~ $?
or pi@sbitx:~ $ cat /proc/asound/cards
?0 [audioinjectorpi]: audioinjector-p - audioinjector-pi-soundcard
? ? ? ? ? ? ? ? ? ? ? audioinjector-pi-soundcard
?1 [Loopback? ? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 1
?2 [Loopback_1? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 2
?3 [Loopback_2? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 3
?4 [Loopback_3? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 4
?5 [II? ? ? ? ? ? ?]: USB-Audio - Jabra EVOLVE 30 II
? ? ? ? ? ? ? ? ? ? ? GN Audio A/S Jabra EVOLVE 30 II at usb-0000:01:00.0-1.1, full speed
pi@sbitx:~ $
The solution is straightforward when you know how and what it is but it took a bit of finding along with trial and error :-) Create this file (it doesn't exist on the delivered sbitx) using the command: sudo nano /etc/modprobe.d/alsa-base.conf? Add these lines to the file: options (efault) index=-2? ? ? ? ? ? ? ? ? ? ? ? ? #am sure this should say default in the brackets but that is how the hw:0,0 device we want was listed in the cat /proc/asound/modules command
options snd_usb_audio index=5
?
Do the check commands to ensure the USB device is at the bottom of the list (index=5) following reboots: pi@sbitx:~ $ cat /proc/asound/cards
?0 [audioinjectorpi]: audioinjector-p - audioinjector-pi-soundcard
? ? ? ? ? ? ? ? ? ? ? audioinjector-pi-soundcard
?1 [Loopback? ? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 1
?2 [Loopback_1? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 2
?3 [Loopback_2? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 3
?4 [Loopback_3? ? ?]: Loopback - Loopback
? ? ? ? ? ? ? ? ? ? ? Loopback 4
?5 [II? ? ? ? ? ? ?]: USB-Audio - Jabra EVOLVE 30 II
? ? ? ? ? ? ? ? ? ? ? GN Audio A/S Jabra EVOLVE 30 II at usb-0000:01:00.0-1.1, full speed
pi@sbitx:~ $ cat /proc/asound/modules ?0 (efault)
?1 snd_aloop
?2 snd_aloop
?3 snd_aloop
?4 snd_aloop
?5 snd_usb_audio
pi@sbitx:~ $?
?
Now that bit is sorted we can start to try and reliably route audio to a USB headset based on the knowledge that the device whether plugged in or not won't affect the core audio routing of the sbitx radio.?Just got to work that bit out now using the Loopback_2 for playback to the USB device and Loopback_3 for capture from the USB device microphone, that way we don't impact the digital functionality of the radio. Might need some coding help with that bit, logically I know it can be done having proved some of the routing via the command line earlier, but now need the output from the codec that feeds the speaker and Loopback(card 1) to also feed Loopback_3(card 3) for play with a volume control (maybe using the Master Volume)? capability to drive the headset with more audio.? Another option would be to take the output/input directly to/from the USB device but maybe that's a bit trickier I believe an alternative headset solution is now a bit nearer Regards |
Re: Software Dreaming
On Fri, Feb 2, 2024 at 03:21 PM, <ramerhar2@...> wrote:
I am signed into several groups looking for best practice for hardware/software design and I like this idea. I would like to experiment with bare-bones exe and work up add up to max capabilities. Thanks for bringing this up.Such a bare bones exe for you to start with already exists. See?this thread?and??from our friend Rafael, based on his code plus that of Farhan. The code has the ability to:
Take the code, redesign/rewrite/refactor it as much as you like, publish your fork. Add DSP, GUI, modems, whatever, keep going till you're happy. As for interesting SDR designs, I always thought?has/had???and?.?? The thing is, I never ran it so I have no idea about any of its dynamic properties i.e. latency etc. -- Regards, Dave, N1AI |
Re: Colorblind help.
Hi Joe.
You can change the colors of the sBitx local and web interfaces. Here is a starting point. To change the web interface:
To change the local interface: This involves a few more steps including recompiling the sBitx binary after modification. ?Here is where the colors are defined. The local file to change is /home/pi/sbitx/sbitx_gtk.c Here are the default color conditions for the file. They are in RGB saturation format where 0 is NO color and 1 is 100% color. The format is {RED,GREEN,BLUE}. For example, if you want pure gray, the the entry is {0.5,0.5,0.5} After you are finished modifying the file, save and close it. Then open terminal and run: cd sbitx I hope this helps! -JJ ? |
sbitx-main and modem code organization and arch questions
I am using VS Code on a windows pc to try to understand the moem code in SBITX-MAIN. I want to understand the code in modem.cw.c
I think modem.cw.c covers a lot of ground, so I'm thinking that it might be possible (and a great code example) to break up modem.cw.c into separate 'modem' pieces modem.straight-key.cw - modem.iambic.cw - modem.keyboard.cw - modem.decoder.cw - ???.cw modem.straight-key.cw should just poll the state of the straight key (with software debouncing) and transmit when key is down Transmitting should take care of the key-down and key-up waveform shaping. And is that all this super simple modem needs to do? As a first step, I thought I would take modems.cw.c and just start commenting out everything that wan't required for straight-key reception (I know, a lot of functionality would stop working like cw decoding and paddle keyer support). Is modems.c supposed to start and support the modem files that do the real work? I'm guessing somewhere in modems.c all of the modems would be started and initialized if required? How would I tell modems.c about my new modem_straight-key.cw ? Any comments? Encouragement? Warnings / "don't try it Mike!"? -- Mike KB2ML |
Re: #sbitx Almost no FT8 reception with V3.02
#sBitx
¿ªÔÆÌåÓýThanks JJ. I shall give it a go. ? Barry ? Sent from for Windows ? From: JJ - W9JES
Sent: Friday, February 2, 2024 1:34 PM To: [email protected] Subject: Re: [BITX20] #sbitx Almost no FT8 reception with V3.02 ? On Fri, Feb 2, 2024 at 09:35 AM, barry halterman wrote:
Hi Barry. ? |
Re: Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?
#sBitx
On Fri, Feb 2, 2024 at 11:12 AM, HA3HZ wrote:
I tested the programs listed in the table.Did you try 'cqrlog' with 'wsjt-x' for ft-8 instead of using Farhan's user interface and ft-8 implementation? If not, I recommend you give it a try, although as I said, you need a larger monitor to use it. ? -- Regards, Dave, N1AI |
Re: #sbitx Almost no FT8 reception with V3.02
#sBitx
On Fri, Feb 2, 2024 at 09:35 AM, barry halterman wrote:
Hi Barry. Checkout sBITX EZ Tools as part of my sBITX Toolbox software. You can easily upgrade or downgrade with the click of a button.?/g/BITX20/topic/sbitx_toolbox_a_great/104023600? -JJ |
Distorted audio on DE
My Sbitx DE now has scratchy distorted audio on receive. However, the audio is ok if I use listen using the earphone. The speaker is not the problem. It seems like I recall this problem coming up a few months ago but I didn¡¯t have the problem at that time and I can¡¯t seem to find the messages on this problem. |
Re: Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?
#sBitx
¿ªÔÆÌåÓýI am enjoying this thread. I never knew about Not1MM logger, going to have to check that out.I¡¯m primarily a Mac/Linux user (Linux since about 1999 and Mac since 2012) and really don¡¯t enjoy booting back into Windows if I can avoid it. I get that all the tech nerds 20-30 years ago used Windows (myself included) and still write programs for it. I¡¯ve been to several tech and developer conferences in the past 5-10 years, and you¡¯d be hard pressed ?to find more than 10% of the laptops running Windows. Much kudos to groups like WSJT-X and others that make their applications work on multiple platforms. I¡¯ve tried to get Winlink working through Wine on my Mac and never was able to make it work. I think it was a 32-bit executable or something, I don¡¯t recall, it¡¯s been a long time. I¡¯m not an open source purist, but would like some options in terms of platform. What drew me to the sbitx was Linux and Raspberry Pi. I have a Flex, but it still needs a computer for things like FT8 or logging. I also have an IC-705, and same issue. Both great radios, but I love that the sbitx is already wired up. 73, Jeremy / N0AW
|
Re: HF UUCP (Was: Re: [BITX20] Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?)
#sBitx
great stuff, Rafael!! On Fri, Feb 2, 2024 at 11:36?AM Rafael Diniz <rafael@...> wrote: Hi Gordon, |
Re: Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?
#sBitx
For windows software, hangover-wine, which includes box64 (which runs 32 binaries in wow mode) and wine, the fastest I could test. Vara is running pretty well. Packages available here:
toggle quoted message
Show quoted text
- Rafael On 2/2/24 15:53, Dave, N1AI wrote:
On Fri, Feb 2, 2024 at 09:15 AM, HA3HZ wrote: |
Re: #sbitx Almost no FT8 reception with V3.02
#sBitx
Joerg,
if the previous sbitx worked fine, try it as I wrote in message #108182, as I did. -- Gyula HA3HZ |
Re: HF UUCP (Was: Re: [BITX20] Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?)
#sBitx
Hi Gordon,
toggle quoted message
Show quoted text
Sure you can receive email. We worked quite a bit in the email system to provide the needs for our partners and communities in the field, be it in Amazon rainforest or Central Africa. I'm happy Winlink has all these human involvement and provides all these services over HF, and more importantly, keep it working! Btw, I never proposed a replacement to Winlink. I'm just commenting on UUCP over HF, including its uses in remote and war-torn areas, or just as backup communication. In terms of networking technology, it fits the purpose very well, while being well supported in any Linux distribution and email stacks (Postfix, Exim, sendmail). For eg., UUCP is ready to be installed / used from the app repository (including Debian / Raspberry OS), while being in use for 40+ years. Cheers, Rafael On 2/2/24 15:26, Gordon Gibby wrote:
FAscinating!? ?Does it work in reverse?? ?Can you RECEIVE email? |
Re: Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?
#sBitx
this is a Port, not port. Sorry
ps.: I forgot to mention that this YFKlog works well on the sBitx 7" LCD. Unfortunately, the author is busy with his work and cannot develop it. -- Gyula HA3HZ |
Re: Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?
#sBitx
I didn't write serial port anywhere, I wrote Port.
I tested the programs listed in the table. TQSL and Tuc are eliminated from this. I tried Xlog, Tlf and PyQSO, they are still up. I ended up sticking with YFK log when I couldn't use sBitx's LOG program. -- Gyula HA3HZ this is a port |
Re: #sbitx Almost no FT8 reception with V3.02
#sBitx
Joerg,
I am running V3.02 and have not noticed any loss of signal on FT8, granted I don't do digital much but I just went over to 7.074 and inside of a minute or so it filled the digital window with decodes. They sounded loud and clear. Joel N6ALT |
Re: Best way to use #sbitx with N3FJP, WINLINK, other Windows ham radio apps?
#sBitx
On Fri, Feb 2, 2024 at 09:15 AM, HA3HZ wrote:
There are a few LOG programs on github that work under Linux.There are several that can be installed with the Debian package managers (apt, etc). Link:?? For instance I have used 'cqrlog' for years and it is a good program. It is not as feature-rich as N3FJP, N1MM, DXLabs, etc but it is good enough for mainstream ham radio logging. It interfaces with wsjt-x so when wsjt-x is ready to log an entry, the cqrlog program pops up with all the fields populated and ready to log. This requires some work with set up, but I think they all do, no? Video, "WSJT-X Logging directly to CQRLOG"? :?? Directions:??? It can be installed with one Terminal command: $ sudo apt install cqrlog This may be one way to avoid your anger at Farhan's FT8 and logging code.? You will want to have an external monitor, the sbitx touch screen is too small for this software. You will also possibly want something faster than sd-card for storage. You will need to set up wsjt-x to use sbitx:?/g/BITX20/wiki/34287? As far as I know, the N3FJP AC program works under Windows.Yes --??... Wine or box86 seems to me to be highly OS dependent.Yes. Therefore, I think that communication through the port should be prioritized.The network should be used for rig control, not the serial port. -- Regards, Dave, N1AI |
Re: #sbitx Almost no FT8 reception with V3.02
#sBitx
I am not yet aware of how others do it, but I plan to keep a separate flash or usb on hand for each one...just in case. My limited understanding is that everything is on the flash drive. Please, someone correct any wrong assumptions I have! On Fri, Feb 2, 2024, 10:36 AM barry halterman <kthreebo@...> wrote:
|