|
Hello all, I have merged almost all the pull requests that fixed a number of small and big issues with the v 3.0 software. These work very well and it has eliminated?many nagging issues.? Most of this heavy lifting?was by Steve Beckman, N3SB. We are all very thankful to him for these. Rafael, has cleaned up the code of the swr bridge?to prevent a race condition. All these changes are transparent to the users. I urge you all to run an update and enjoy the better version.? A few feature upgrades are pending, including a new form of AGC control. I will discuss this with Steve before merging it in. For those interested, there is an online devcon being planned in the coming weeks to gather the nascent development community together. - f
|
Farhan
Just to clear up some confusion. ?To update V3 it is only necessary to run ./update, correct?
I’m sure I’ve seen a few emails indicating a ./build is also required, but I didn’t think that was necessary.?
Thx
73 Roy
On Fri, Jan 19, 2024 at 07:12, Ashhar Farhan via groups.io < farhanbox@...> wrote: Hello all, I have merged almost all the pull requests that fixed a number of small and big issues with the v 3.0 software. These work very well and it has eliminated many nagging issues. Most of this heavy lifting was by Steve Beckman, N3SB. We are all very thankful to him for these. Rafael, has cleaned up the code of the swr bridge to prevent a race condition. All these changes are transparent to the users. I urge you all to run an update and enjoy the better version. A few feature upgrades are pending, including a new form of AGC control. I will discuss this with Steve before merging it in. For those interested, there is an online devcon being planned in the coming weeks to gather the nascent development community together. - f
|
Yes, ./update should do it. - f
Farhan
Just to clear up some confusion.? To update V3 it is only necessary to run ./update, correct?
I’m sure I’ve seen a few emails indicating a ./build is also required, but I didn’t think that was necessary.?
Thx
73 Roy
On Fri, Jan 19, 2024 at 07:12, Ashhar Farhan via < farhanbox@...> wrote: Hello all, I have merged almost all the pull requests that fixed a number of small and big issues with the v 3.0 software. These work very well and it has eliminated many nagging issues. Most of this heavy lifting was by Steve Beckman, N3SB. We are all very thankful to him for these. Rafael, has cleaned up the code of the swr bridge to prevent a race condition. All these changes are transparent to the users. I urge you all to run an update and enjoy the better version. A few feature upgrades are pending, including a new form of AGC control. I will discuss this with Steve before merging it in. For those interested, there is an online devcon being planned in the coming weeks to gather the nascent development community together. - f
|
On Fri, Jan 19, 2024 at 10:57 AM, Ashhar Farhan wrote:
Yes, ./update should do it.
Well, yes, should. A good idea is to make a backup first, because doing ./update does its update in-place.?? I agree it should work, but if it does something unexpected, people probably want a way to go back to a known working state. ? -- Regards, Dave, N1AI
|
Absolutely back up. You can NOT have too many backup copies. ?If you have the available SD cards, keep more than one copy of the same backup. ?
In my years of running a home server network, I had a main drive failure. ?The backup rsync’ed drive failed. The first DVD backup failed. ?It was only the 3rd?backup that would completely restore my system. ?Yes I lost some data as the working backup was older than the rest.?
On Fri, Jan 19, 2024 at 10:44, Dave, N1AI via groups.io < n1ai@...> wrote: On Fri, Jan 19, 2024 at 10:57 AM, Ashhar Farhan wrote:
Yes, ./update should do it.
Well, yes, should.
A good idea is to make a backup first, because doing ./update does its update in-place.??
I agree it should work, but if it does something unexpected, people probably want a way to go back to a known working state.
?
--
Regards,
Dave, N1AI
|
Absolutely back up. You can NOT have too many backup copies. ?If you have the available SD cards, keep more than one copy of the same backup. ?
In my years of running a home server network, I had a main drive failure. ?The backup rsync’ed drive failed. The first DVD backup failed. ?It was only the 4th?
On Fri, Jan 19, 2024 at 10:44, Dave, N1AI via groups.io < n1ai@...> wrote: On Fri, Jan 19, 2024 at 10:57 AM, Ashhar Farhan wrote:
Yes, ./update should do it.
Well, yes, should.
A good idea is to make a backup first, because doing ./update does its update in-place.??
I agree it should work, but if it does something unexpected, people probably want a way to go back to a known working state.
?
--
Regards,
Dave, N1AI
|
That's great to hear, and you are all doing such a wonderful job with all these mods and updates. I wonder if it is possible to implement, 1, an adjustable change in cw text size, for older people like me with bad eyes sometime? and 2, I wonder if there's a way to make the cw/logging text box smaller when the usb or lsb buttons are selected, to give it as much as possible a larger waterfall screen only in these modes? Just a thought guys. Owen G0RCL
On Fri, 19 Jan 2024 at 16:44, Dave, N1AI < n1ai@...> wrote: On Fri, Jan 19, 2024 at 10:57 AM, Ashhar Farhan wrote:
Yes, ./update should do it.
Well, yes, should.
A good idea is to make a backup first, because doing ./update does its update in-place.??
I agree it should work, but if it does something unexpected, people probably want a way to go back to a known working state.
?
--
Regards,
Dave, N1AI
|
I wonder if it is possible to implement, 1, an adjustable change in cw text size, for older people like me with bad eyes sometime?? Just a thought guys. Owen G0RCL
@Owen. Please checkout sBITX Manager as it offers larger text font sizes for CW decoding until the sBitx software matures.?? - JJ
|
toggle quoted message
Show quoted text
On Sat, Jan 20, 2024, 12:04 AM JJ - W9JES < w9jes@...> wrote:
I wonder if it is possible to implement, 1, an adjustable change in cw text size, for older people like me with bad eyes sometime?? Just a thought guys. Owen G0RCL
@Owen. Please checkout sBITX Manager as it offers larger text font sizes for CW decoding until the sBitx software matures.??
- JJ
|
First experiences with sBitx v3.02: The first QSO now creates a correct LOG file. In the previous version, the LOG save message appeared twice on the screen. It was saved once in the LOG. What is still an error, when I receive a CALL MYCALL 73 message from the station, the program wants to give a report again. However, saving to the LOG file and changing the report had already taken place previously. -- Gyula HA3HZ  
|
If anyone is interested in making copies. I do it like this:
I currently have 4 versions and the folder name distinguishes them. I use one of these, in chronological order:
sbitx
sbitxv3
sbitxv301
sbitxv301+
In this latter, I tested the pull request files.
When the changes reach the usable version, I delete the previous ones.
By definition, the currently used folder is the sbitx folder.
I installed this by cloning and using ./build sbitx, then I copy the entire data folder from the most recently used folder and the .mc files from the web folder.
With this, my previous settings and log file will be used from now on.
Backup is also an option to preserve the previously well-functioning version. You don't have to do it this way, it worked for me.
These operations can be achieved using the built-in File Manager. In many cases, I monitor the error report by running gdb.
Here I only had a buffer overflow in one case.
--
Gyula HA3HZ
|
Thanks to the team for the update ..
When starting sbitx from a terminal, should the software be reporting the incremented version?? IE: "sbitx v3.02"? ??
After the update, mine still reports : "sbitx v3.0"
--
Pete VK3PYE
|
Peter, I have fixed that and also added the wisdom files to the repo. Update again and check? - f
On Sat, Jan 20, 2024 at 6:33?AM Peter VK3PYE < vk3pye@...> wrote: Thanks to the team for the update ..
When starting sbitx from a terminal, should the software be reporting the incremented version?? IE: "sbitx v3.02"? ??
After the update, mine still reports : "sbitx v3.0"
--
Pete VK3PYE
|
Peter,
after the update and in all cases when changes are made to the files necessary for the program to work, it must be included.
Use ./build sbitx from the terminal to build.
You should then also see the version number change.
When you change the macro (.mc) and data files, it is enough to restart the program (sbitx).
--
Gyula HA3HZ
|
Upgraded from v3.0 using ./upgrade?
Changing the bandwidth causes audio issues. Found this when running debug. Ideas on a cause and fix?
Starting program: /home/pi/sbitx/sbitx?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[Detaching after fork from child process 1511]
[Detaching after fork from child process 1512]
[Detaching after fork from child process 1513]
[New Thread 0xb4932200 (LWP 1514)]
[New Thread 0xb3fff200 (LWP 1515)]
[New Thread 0xb34ff200 (LWP 1516)]
[Detaching after fork from child process 1517]
[New Thread 0xb2aff200 (LWP 1518)]
[Detaching after fork from child process 1519]
[New Thread 0xb22fe200 (LWP 1520)]
[New Thread 0xb1afd200 (LWP 1524)]
[New Thread 0xb108d200 (LWP 1526)]
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
[New Thread 0xb06ff200 (LWP 1527)]
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
[Detaching after fork from child process 1528]
synchronised to NTP server (69.89.207.199) at stratum 2?
? ?time correct to within 28 ms
? ?polling server every 64 s
Checking for valid NTP time ...Syncing RTC to 2024-01-20 08:16:21
Thanks
- JJ
|
Which mode were you?using and what was the bandwidth set? This has been reported earlier too. - f
On Sat, Jan 20, 2024, 1:52 PM JJ - W9JES < w9jes@...> wrote: Upgraded from v3.0 using ./upgrade?
Changing the bandwidth causes audio issues. Found this when running debug. Ideas on a cause and fix?
Starting program: /home/pi/sbitx/sbitx?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[Detaching after fork from child process 1511]
[Detaching after fork from child process 1512]
[Detaching after fork from child process 1513]
[New Thread 0xb4932200 (LWP 1514)]
[New Thread 0xb3fff200 (LWP 1515)]
[New Thread 0xb34ff200 (LWP 1516)]
[Detaching after fork from child process 1517]
[New Thread 0xb2aff200 (LWP 1518)]
[Detaching after fork from child process 1519]
[New Thread 0xb22fe200 (LWP 1520)]
[New Thread 0xb1afd200 (LWP 1524)]
[New Thread 0xb108d200 (LWP 1526)]
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
[New Thread 0xb06ff200 (LWP 1527)]
ALSA lib pcm.c:8424:(snd_pcm_recover) underrun occurred
[Detaching after fork from child process 1528]
synchronised to NTP server (69.89.207.199) at stratum 2?
? ?time correct to within 28 ms
? ?polling server every 64 s
Checking for valid NTP time ...Syncing RTC to 2024-01-20 08:16:21
Thanks
- JJ
|
On Sat, Jan 20, 2024 at 03:03 PM, Ashhar Farhan wrote:
Update again and check?
I tried the "./update" again (1015z today) and same result.? Both the terminal and the sbitx program report "v3.0". It seems to be running OK. Gyula HA3HZ suggests to do "./build" from the terminal after an update, is that correct?? Is it done from inside the sbitx directory? ? -- Pete VK3PYE
|
JJ - W9JES,
When I tested pull requests, I left this last. It was #69 that made the change in sbitx_sound.c. As far as I know, it is to eliminate the occasional error by rebooting.
The error was that the audio loop was not built and there were dark spots in the waterfall. This was the visible error.
I think it needs more time to really do its job well.
If you are completely disillusioned with it, you can return to the previous sbitx_sound.c. I saved this with the name .old and could return to it at any time.
Since I store all previous versions, I can easily go back. But as I wrote before, adding old makes the return faster.
If you need an earlier version of git, I can do that.
--
Gyula HA3HZ
|
Peter,
Yes, it must be done within the sbitx directory.
I don't use the update, because then the previous version is lost, I keep it until I see that everything works fine.
That's why I clone the newer version, before renaming the well-functioning used folder so that you don't clone it there.
--
Gyula HA3HZ
|
Peter,
So first rename the currently used folder, e.g. to sbitxv3 or whatever you are currently using. Then after that:
git clone https://github.com/afarhan/sbitx
cd sbitx
./build sbitx
then I copy the data folder from the one that worked well before, because it contains the log file, hardware and user settings.
I will copy it if you used the macro files before and modified them from the web folder.
After that I start sbitx.
--
Gyula HA3HZ
|
Dave, N1AI
HA3HZ
Peter VK3PYE