On Tue, Jan 30, 2024 at 05:46 AM, Owen Baldwin wrote:
Ive tried to install it using the link above on Linux, but it doesn't install? taking into account, I am not a programmer and I am in my 80's. Maybe I should just give and concede....
Hi Owen. If you are comfortable with copying files from your computer to a USB drive, then I can make a zip file for you with instructions.. -JJ
|
Roy,
do you see what i see?
If the QSO is not completed because there are a lot of people in the 3 kHz band, you may not even notice that another station is on your signal. From then on, your signal will be suppressed, especially if it is a 100-watt "weak signal". You don't even notice this, because the other station is also receiving during the reception period. So you broadcast together on exactly the same frequency. Therefore, the QSO fails within two minutes. If the frequency spread also contributes to this, the completion time will be longer.
I just want to know where to increase this connection time. I would like to increase this so that there is no automatic entry in the log every two minutes.
I'm not even asking how many QSOs you've made. Everything can be seen from the pictures.
--
Gyula HA3HZ
|
Re: #sBitx on Raspberry Pi OS 64-bit
#sBitx
Thanks, that was the first thing I checked as that happened when the rig was shipped but I have updated to the 64-bit OS so different issue.
Am out doing a Support Dogs talk now so it will be tomorrow before i can check further. Its not a big issue as the JTDX software I am using has the right time but need to set time manually if I use the built-in FT8 software within the sbitx app
Regards
Paul G0KAO
|
I¡¯m running a stock v3 system and I do not have a multiple log entry problem.?
73 Roy
On Tue, Jan 30, 2024 at 11:31, HA3HZ via groups.io < gyula@...> wrote: What I mean? See the attached pictures:
--
Gyula HA3HZ
|
Re: #sBitx on Raspberry Pi OS 64-bit
#sBitx
Systems have shipped with a TZ being exported from the ¡°.profile¡± for the sbitx user.?
On Tue, Jan 30, 2024 at 10:56, JerryP via groups.io < jponko@...> wrote: So the system time is correct. If you open the terminal and run the 'date' command is the output correct for your time zone?
What about running the 'nptime' command. It should show the local date and time (24hr format) on the first line.
If the system time is correct, I can't imagine how the displayed time in sbitx is one hour off. Supposedly, sbitx
is reading the time from the sbitx clock module which should be in sync with internet time. I remember reading
about a time setting being changed in the .profile or .bashrc files that was setting India time but I doubt that would be the
case as the OS was setup by you in the instructions when you used the Raspberry imager.
I haven't paid any attention to the time displayed on the sbitx. Perhaps it's using UTC by default.
--
Jerry Ponko, AC9NM
|
Re: #sBitx on Raspberry Pi OS 64-bit
#sBitx
So the system time is correct. If you open the terminal and run the 'date' command is the output correct for your time zone?
What about running the 'nptime' command. It should show the local date and time (24hr format) on the first line.
If the system time is correct, I can't imagine how the displayed time in sbitx is one hour off. Supposedly, sbitx
is reading the time from the sbitx clock module which should be in sync with internet time. I remember reading
about a time setting being changed in the .profile or .bashrc files that was setting India time but I doubt that would be the
case as the OS was setup by you in the instructions when you used the Raspberry imager.
I haven't paid any attention to the time displayed on the sbitx. Perhaps it's using UTC by default.
--
Jerry Ponko, AC9NM
|
Re: SBITX v3 - Ability to use a Headset for phone modes
On Tue, Jan 30, 2024 at 05:02 AM, Dave, N1AI wrote:
The usable volume range is such that there is almost no audio until the volume control reaches a setting of 50+, a reasonably comfortable audio setting of about 86 is required to listen to the sbitx speaker.?
Might be partially due to arecord using 8 bit samples, not much dynamic range to work with.
this was on the SBITX speaker, not the headset, hence the headset is more comfortable to listen to once I can get the volume/gain level right and ideally adjustable, the headset volume is restricted by the amount of gain controlled by the loopback device used to test so headset volume adjusted to max and it was easy enough to listen on 40m SSB earlier today even weak signals were audible in the headset compared to listening on the sbitx speaker which is a good improvement really. The logical next step (for playback anyway) now is to get the audio out of audioinjectorpi into a separate loopback (maybe the unused spare perhaps) as well as the ones used for digital so as not to upset the digital functions that seem to work well so far but volume control fixed in those, need it to be variable in the new Loopback. While I can figure out and read code to some extent I am not a programmer, logically, I would probably copy the code that drives loopback 0(hw:1,0) from hw:0,0 and use it to drive loopback 2(would be hw:3:0) so that hw:0,0 plays audio output to both loopbacks at the same time. That way the changes to drive another audio device can be made in isolation related to the new loopback device. Repeat this process again for the Capture side of things if needed but just focusing on play for now. I did install gnuradio with a view to trying to draw this but bit of a learning curve :-) The art of drawing in text? :-) hw:0,0 >>>>>> Loopback,DEV=0 (hw:1,0) >>>>>>>> Loopback,DEV=1 (hw:1,1)? >>>>>>>>>>> Digital Software input hw:0,0 >>>>>> Loopback_2,DEV=0 (hw:3,0) >>>>>> Loopback_2,DEV=1 (hw:3,1) >>>>>>>>>> Alternative Audio Device input i.e. USB Headset Sort of makes sense to me but happy to be corrected Regards Paul G0KAO
|
Re: Strong click when switching on the transmission
#sBitx
I noticed this for the first time last evening using FT8.
Issue was also present in CW and SSB.
This morning I haven't noticed it.?
Seems like an audio burst when switching from receive to transmit.
Michael
|
Re: 73 Linux or Build-A-Pi support on the sBitx?
I greatly appreciate these.
It's not exactly how I wanted things to get going, because it's not nicely packaged.
Any ideas on how to get ardop going?
|
Well, mine just shipped out, and I am excited to check it out. Keep me informed on the progress.? Fldigi is used by my on my computer.
Scotty
On Tue, Jan 30, 2024, 10:20 AM Dean Souleles < dsouleles@...> wrote: Hi... I have a couple of questions / issues running FLdigi I stand alone with the SBITX.? I'm running the V3 SBITX version on my homebrew rig.? The FLdigi version is from the V2 image that Farhan made available a few months ago.
In the SBITX I have it set to digital mode.
In FLdigi? I see signals on the waterfall and I can set the main frequency in FLdigi and the SBITX tunes as expected.
First observation/ question... The FLdigi offset frequency seems to be locked to the SBITX pitch.? I can't change it in Fldigi.? I have to go to the sbitx screen to change the pitch.? Is this just the way it works?? Seems like I should be able to adjust the offset from the FLdigi control.
Second, so far I have only been able to de.code an RSID, but no other decode in Flfldigi.? I've tried different spans and bandwidth in SBITX but so far no luck. What is anyone else's experience with SBITX configuration for good FLDG decodes?
Third, when I change frequencies in FLDG using the FLDG frequency list the SBITX changes frequencies appropriately, but the FLdigi application locks up for 20 or 30 seconds before coming back.??
Fourth, just wondering how people set the waterfall in FLDG for best visual display... I'm referring to the upper signal and signal range settings on the bottom of the waterfall.
Thanks all... I am having a lot of fun with this.
73,
Dean
KK4DAS
|
Hi... I have a couple of questions / issues running FLdigi I stand alone with the SBITX.? I'm running the V3 SBITX version on my homebrew rig.? The FLdigi version is from the V2 image that Farhan made available a few months ago.
In the SBITX I have it set to digital mode.
In FLdigi? I see signals on the waterfall and I can set the main frequency in FLdigi and the SBITX tunes as expected.
First observation/ question... The FLdigi offset frequency seems to be locked to the SBITX pitch.? I can't change it in Fldigi.? I have to go to the sbitx screen to change the pitch.? Is this just the way it works?? Seems like I should be able to adjust the offset from the FLdigi control.
Second, so far I have only been able to de.code an RSID, but no other decode in Flfldigi.? I've tried different spans and bandwidth in SBITX but so far no luck. What is anyone else's experience with SBITX configuration for good FLDG decodes?
Third, when I change frequencies in FLDG using the FLDG frequency list the SBITX changes frequencies appropriately, but the FLdigi application locks up for 20 or 30 seconds before coming back.??
Fourth, just wondering how people set the waterfall in FLDG for best visual display... I'm referring to the upper signal and signal range settings on the bottom of the waterfall.
Thanks all... I am having a lot of fun with this.
73,
Dean
KK4DAS
|
Re: #sBitx on Raspberry Pi OS 64-bit
#sBitx
Thanks for the tips Jerry. I have come across a strange problem with the time on the sbitx app in that it is displaying 1 hour behind despite the fact that everything system wise is displaying the correct time. I have tried pretty much everything and the only way to get the correct time in the app is to set it manually using the utc command in the command window of the app. captured from starting the app in terminal window:
pi@sbitx:~ $ cd sbitx
pi@sbitx:~/sbitx $ ./sbitx
sbitx v3.02
Generating Wisdom File...
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
synchronised to unspecified at stratum 2?
? ?time correct to within 26 ms
? ?polling server every 64 s
Checking for valid NTP time ...Syncing RTC to 2024-01-30 14:41:49
Mode: LSB
Mode: LSB
Mode: USB
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
Mode: FT8
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8570:(snd_pcm_recover) underrun occurred
However the app is displaying 1 hour behind the result above - time in the UK at the moment is UTC (GMT) anyway separate captures from another terminal window:
pi@sbitx:~/sbitx $ ntpstat
synchronised to unspecified at stratum 2?
? ?time correct to within 26 ms
? ?polling server every 64 s
pi@sbitx:~/sbitx $?
?
pi@sbitx:~/sbitx $ ntpdate
2024-01-30 14:50:31.761634 (+0000) -0.000193 +/- 0.000518 localhost ::1 s2 no-leap
CLOCK: adj_systime: Operation not permitted
pi@sbitx:~/sbitx $?
pi@sbitx:~/sbitx $ sudo raspi-config?
?
Current default time zone: 'Europe/London'
Local time is now:? ? ? Tue Jan 30 14:52:32 GMT 2024.
Universal Time is now:? Tue Jan 30 14:52:32 UTC 2024.
?
pi@sbitx:~/sbitx $?
Did this last one just as a check, so at a system level everything is correct. What changed as a result of changing to cinnamon I wonder? As for the audio, making a bit of progress on that front and started a separate thread ( /g/BITX20/topic/sbitx_v3_ability_to_use_a/104041576?p=,,,20,0,0,0::recentpostdate/sticky,,,20,0,0,104041576,previd%3D1706625533301656191,nextid%3D1706279732445682699&previd=1706625533301656191&nextid=1706279732445682699) to track it and keep notes :-) I have better audio out of the USB headset than the speaker with the findings so far, just not loud enough yet :-) its a manual process at moment but its a start for output anyway
?
Regards Paul
|
Re: Strong click when switching on the transmission
#sBitx
?I hear the same click occasionally. No idea why.
Jonathan
|
Re: #sBitx on Raspberry Pi OS 64-bit
#sBitx
Paul.
You may want to expand the swapfile size from 100MB to 2048MB by editing the /etc/dphys-swapfile. You probably have enough disk space to afford the 2GB swapfile. The OS is setup to fit in the small SD size when initially installed on first boot until the file system is expanded to the maximum size on reboot but they leave the swapfile size at 100MB.
Change the /etc/dphys-swapfile settings to those below for a 2GB swapfile and then reboot. If you run out of real memory the virtual memory will be used and things may run slowly but not stop or give out of memory errors unless, of course, you run out of swap.
...
# set size to absolute value, leaving empty (default) then uses computed value
#?? you most likely don't want this, unless you have an special disk situation
#CONF_SWAPSIZE=100
# set size to computed value, this times RAM size, dynamically adapts,
#?? guarantees that there is enough swap without wasting disk space on excess
#CONF_SWAPFACTOR=2
# restrict size (computed and absolute!) to maximally this limit
#?? can be set to empty for no limit, but beware of filled partitions!
#?? this is/was a (outdated?) 32bit kernel limit (in MBytes), do not overrun it
#?? but is also sensible on 64bit to prevent filling /var or even / partition
CONF_MAXSWAP=2048
...
As far as the headset thing, you may want to use an externel bluetooth
remote sender/receiver pair like those used to provide wireless headphones for TVs.
You use a wired connection to the modules of course. I don't know of any that are
bidirectional so you'd need two and then there is the
ptt line to deal with unless you use VOX somehow. Sounds like an expensive and
complicated solution but I can't think of a way of not screwing up the sbitx sound
system otherwise.
--
Jerry Ponko, AC9NM
|
Re: SBITX v3 - Ability to use a Headset for phone modes
On Tue, Jan 30, 2024 at 04:24 AM, Paul wrote:
Thanks for this Dave
AS expected replacing your Device with my II worked at treat.
Wonderful!
Signal to noise level output not great and is worse in the headset than it is on the sbitx speaker, however its not great there on mine anyway.
Some of that could be due to the resampling that I mentioned.? Ideally plughw should not be used.? One should know the sampling rate of each signal and set up each program to match.?? Also the arecord | aplay pipeline is reprocessing the signal. From the arecord man page:  So it is using 8 bit samples at 8000 hz.?? Bottom line is I did not bother so far to see what sampling rate and sample size is being used in the sbitx_sound.c code when writing to the loopback device, but whatever it is, it would work better if they were all the same. Also as I said already, 'sox' would be more efficient and would let you set gain and add filtering as it implements various 'effects'.
Turning the volume up on the sbitx just seems to make it worse.
My EE professor would smile now.? Amplifying a bad signal only makes it worse.? He was an analog guy.? In modern terms, resampling a sample just makes it worse.
The usable volume range is such that there is almost no audio until the volume control reaches a setting of 50+, a reasonably comfortable audio setting of about 86 is required to listen to the sbitx speaker.?
Might be partially due to arecord using 8 bit samples, not much dynamic range to work with.
Word of warning for anyone following this thread and using the 64-bit OS. if you boot the sbitx up with the USB headset plugged in, the sbitx app will not start,, unplug the headset and reboot again if this happens.
On the stock v3 sbitx I had a slightly different experience in that if I booted the radio up with USB headset connected, the headset would work in parallel with the sbitx speaker.
This is the physical names vs logical names issue I mentioned earlier.??
this command produces better output in my headset than I get from the sbitx speaker:
arecord -D "plughw:CARD=Loopback,DEV=1" -f cd | aplay -D "plughw:CARD=II,DEV=0"
Ok, you are proving what I said above.? This uses 'CD' format so not 8 bits at 8000 hz, instead 16 bits at 44,000 hz.
Just need to increase the volume to it now, perhaps using the rig volume control to allow the headset volume control the local control for fine adjustment
A step in the right direction me thinks
Agree. ? -- Regards, Dave, N1AI
|
Re: SBITX v3 - Ability to use a Headset for phone modes
On Tue, Jan 30, 2024 at 04:14 AM, Rafael Diniz wrote:
I've being using gnuradio-companion too for simple testing.
I committed some .grc files here, which might be useful:
Thank you!? I have been using your grc files from doc folder in sbitx-core.? I did not know about 'qt gui sink' till I used your flowgraphs.? It's really nice!? You can switch between fft and waterfall or even constellation if you are using complex signals for digital work.? The waterfall has an 'auto gain' button to help you find the signal and a fft size control that lets you change size dynamically. Before this I used the 'qt gui frequency sink' and 'qt gui waterfall' independently.? This is much nicer! ? -- Regards, Dave, N1AI
|
Strong click when switching on the transmission
#sBitx
Sometimes a strong click when switching on the transmission.
As if there is a bad contact at a relay, although there is no relay of any kind.
Reducing the volume to 0 does not affect this sound.
It is also not affected if I reduce the transmitter driver level.
Has anyone experienced something similar?
Has anyone found a solution to make this noise disappear?
--
Gyula HA3HZ
|
Owen,
please make sure Python is installed as it is required for this to work. Whichever OS you use.
--
Gyula HA3HZ
|
Ive tried to install it using the link above on Linux, but it doesn't install? taking into account, I am not a programmer and I am in my 80's. Maybe I should just give and concede....
There are well known & important pieces of windows software out there (Not available on Linux) ?that emcomm & other users would wish to use with this radio¡. but those software do not support the sbitx.?
Examples include Winlink RMSexpress, WINLINK ?trimode, and WINLINK ?RMS relay, ION2G (ALE) and N3FJP (logging software that also keys radios in activates canned voice and Morse code in Icom ) ? ?(most of which we just used in winter field day but would not be able to use with this radio)?
Why not create an emulation of either a Yaesu or ICOM radio so this radio can be used immediately?? The uBitx series had this, which made it very attractive
Gordon KX4Z?
On Jan 30, 2024, at 03:40, HA3HZ <gyula@...> wrote:
?Yes, this is a good idea, the Compression level should be adjustable.
It's a shame that the availability of LOG has changed since the current working LOG, so it is not available with tools.
--
Gyula HA3HZ
|
There are well known & important pieces of windows software out there (Not available on Linux) ?that emcomm & other users would wish to use with this radio¡. but those software do not support the sbitx.?
Examples include Winlink RMSexpress, WINLINK ?trimode, and WINLINK ?RMS relay, ION2G (ALE) and N3FJP (logging software that also keys radios in activates canned voice and Morse code in Icom ) ? ?(most of which we just used in winter field day but would not be able to use with this radio)?
Why not create an emulation of either a Yaesu or ICOM radio so this radio can be used immediately? ?The uBitx series had this, which made it very attractive
Gordon KX4Z?
toggle quoted message
Show quoted text
On Jan 30, 2024, at 03:40, HA3HZ <gyula@...> wrote:
?Yes, this is a good idea, the Compression level should be adjustable.
It's a shame that the availability of LOG has changed since the current working LOG, so it is not available with tools.
--
Gyula HA3HZ
|
HA3HZ
JerryP
Scotty R
Dave, N1AI