Re: Sibtx v3, the open source Hybrid SDR is released
The sbitx boards are available on
On Fri, Dec 15, 2023, 6:23 PM Alistair - M5ASF < liverpudd@...> wrote: Great work Ashar.
Dare I ask if anyone has designed PCB's or offering kits for theSibtx?
|
Re: Sibtx v3, the open source Hybrid SDR is released
Great work Ashar.
Dare I ask if anyone has designed PCB's or offering kits for theSibtx?
|
So somehow your logger connects to flrig? For me I use Fllog and it connects directly to fldigi and flrig connects directly to fldigi. I suppose your logger has some special features that are helpful for you. If it works enjoy!
toggle quoted message
Show quoted text
On Dec 14, 2023, at 16:07, Philip Rose, GM3ZZA via < gm3zza@...> wrote:
Hi Cliff,
Hamlib has as one of its rigs: FlRig.
Hamlib can drive the xmlrpc interface to flrig. I found that easier to use than trying to control the xmlrpc from within my logger.
BTW I've made progress on my original problem - in a separate response.
Phil
Phil,?
Can you help me understand the connection between flrig and Hamlib? If fldigi only one or the other will be operational at any one time. On Dec 14, 2023, at 15:02, Philip Rose, GM3ZZA via ??< gm3zza@...> wrote:
I have recently bought a new rig IC705 in addition to the IC7300 I already have.
I have created two aliases for flrig to access the two rigs using --config-dir. I have configured each instance of flrig to listen to different ports :12345 for the IC7300 and :12346 for the IC705.?
I have only twice managed to connect my logging app (zzalog) since, and both times to the IC705 instance. I think it was when I started the IC705 then started zzalog. I am using hamlib to connect to flrig. I tried WSJT-X and that also failed to connect. Hamlib seems to timeout on the connection after a couple of minutes.
I did originally make the mistake of not changing the port number on the new instance of flrig, so maybe there is some memory of this lingering about. My OS is debian bookworm on a converted Dell laptop.
When I next get time, I'll try some more measured tries.
Phil GM3ZZA
|
Progress (I hope).
I realised my logger is attempting to connect to the rig that was used for the last QSO even if it's not connected. I suffered the hamlib timeout every time I start my logger
?
If I don't do this and only try to connect to it once I've started flrig for any or all of the rigs then I seem to connect OK. I've tried this from a standing start and connected to both rigs OK.
I now need to try this with all the apps.
Phil GM3ZZA
toggle quoted message
Show quoted text
I have recently bought a new rig IC705 in addition to the IC7300 I already have.
I have created two aliases for flrig to access the two rigs using --config-dir. I have configured each instance of flrig to listen to different ports :12345 for the IC7300 and :12346 for the IC705.
I have only twice managed to connect my logging app (zzalog) since, and both times to the IC705 instance. I think it was when I started the IC705 then started zzalog. I am using hamlib to connect to flrig. I tried WSJT-X and that also failed to connect. Hamlib
seems to timeout on the connection after a couple of minutes.
I did originally make the mistake of not changing the port number on the new instance of flrig, so maybe there is some memory of this lingering about. My OS is debian bookworm on a converted Dell laptop.
When I next get time, I'll try some more measured tries.
Phil GM3ZZA
|
Hi Cliff,
Hamlib has as one of its rigs: FlRig.
Hamlib can drive the xmlrpc interface to flrig. I found that easier to use than trying to control the xmlrpc from within my logger.
BTW I've made progress on my original problem - in a separate response.
Phil
toggle quoted message
Show quoted text
Phil,?
Can you help me understand the connection between flrig and Hamlib? If fldigi only one or the other will be operational at any one time.
On Dec 14, 2023, at 15:02, Philip Rose, GM3ZZA via < gm3zza@...> wrote:
I have recently bought a new rig IC705 in addition to the IC7300 I already have.
I have created two aliases for flrig to access the two rigs using --config-dir. I have configured each instance of flrig to listen to different ports :12345 for the IC7300 and :12346 for the IC705.
I have only twice managed to connect my logging app (zzalog) since, and both times to the IC705 instance. I think it was when I started the IC705 then started zzalog. I am using hamlib to connect to flrig. I tried WSJT-X and that also failed to connect. Hamlib
seems to timeout on the connection after a couple of minutes.
I did originally make the mistake of not changing the port number on the new instance of flrig, so maybe there is some memory of this lingering about. My OS is debian bookworm on a converted Dell laptop.
When I next get time, I'll try some more measured tries.
Phil GM3ZZA
|
Phil,?
Can you help me understand the connection between flrig and Hamlib? If fldigi only one or the other will be operational at any one time.
toggle quoted message
Show quoted text
On Dec 14, 2023, at 15:02, Philip Rose, GM3ZZA via < gm3zza@...> wrote:
I have recently bought a new rig IC705 in addition to the IC7300 I already have.
I have created two aliases for flrig to access the two rigs using --config-dir. I have configured each instance of flrig to listen to different ports :12345 for the IC7300 and :12346 for the IC705.
I have only twice managed to connect my logging app (zzalog) since, and both times to the IC705 instance. I think it was when I started the IC705 then started zzalog. I am using hamlib to connect to flrig. I tried WSJT-X and that also failed to connect. Hamlib seems to timeout on the connection after a couple of minutes.
I did originally make the mistake of not changing the port number on the new instance of flrig, so maybe there is some memory of this lingering about. My OS is debian bookworm on a converted Dell laptop.
When I next get time, I'll try some more measured tries.
Phil GM3ZZA
|
Hi Bruce,
A couple of things to check:
The Transmit Attenuator for fldigi, lower right hand corner, adjusts the power out, not anything on the rig unless you want to limit the rig. Set the rig to full power out the adjust fldigi to give you the power you want out. This is basically adjusting the audio drive to the rig.
Regarding the 7100, it may not export a reading for S-meter so if that is the case then there will be no S-meter indication.
Decoding is based on audio input to fldigi. Wsjtx needs far less audio input so make sure the volume on the built in sound card in the 7100 is at 100%.
I heartedly recommend that you look at the online help for flrig and especially the how-to for setting up the 7100.
toggle quoted message
Show quoted text
On Dec 14, 2023, at 14:50, Bruce W4BRU < w4bru@...> wrote:
I am setting up fldigi and wstj-x for a friend on his Windows 10 computer connected to an IC-7100. I can't get fldigi to work correctly.
- fldigi is using flrig as its rig control. The controls on flrig seems to work correctly based on 7100 indicators.
- flrig shows no s meter level.
- There is no fldigi decode and a weak looking waterfall. The sound from the IC-7100 speaker appears to be as expected for PSK31. I tried several bands with the same result.
- With a power out setting of 20 watts on flrig the power meter reads 2 watts using fldigi a CQ transmission. No matter the power setting on flrig, the power out is 10% of the setting.
By comparison, WSTJ-X works, decodes etc with the same rig and sound card settings. It is and IC-7100, flrig-2.0.04, fldigi-4.2.03, Windows 10; I'm a Linux not Windows person so I'm struggling with the OS but with WSTJ-X working I suspect an issue with the "fls". What tools are available to diagnose this in Windows 10?
|
I have recently bought a new rig IC705 in addition to the IC7300 I already have.
I have created two aliases for flrig to access the two rigs using --config-dir. I have configured each instance of flrig to listen to different ports :12345 for the IC7300 and :12346 for the IC705.
I have only twice managed to connect my logging app (zzalog) since, and both times to the IC705 instance. I think it was when I started the IC705 then started zzalog. I am using hamlib to connect to flrig. I tried WSJT-X and that also failed to connect. Hamlib seems to timeout on the connection after a couple of minutes.
I did originally make the mistake of not changing the port number on the new instance of flrig, so maybe there is some memory of this lingering about. My OS is debian bookworm on a converted Dell laptop.
When I next get time, I'll try some more measured tries.
Phil GM3ZZA
|
I am setting up fldigi and wstj-x for a friend on his Windows 10 computer connected to an IC-7100. I can't get fldigi to work correctly.
- fldigi is using flrig as its rig control. The controls on flrig seems to work correctly based on 7100 indicators.
- flrig shows no s meter level.
- There is no fldigi decode and a weak looking waterfall. The sound from the IC-7100 speaker appears to be as expected for PSK31. I tried several bands with the same result.
- With a power out setting of 20 watts on flrig the power meter reads 2 watts using fldigi a CQ transmission. No matter the power setting on flrig, the power out is 10% of the setting.
By comparison, WSTJ-X works, decodes etc with the same rig and sound card settings. It is and IC-7100, flrig-2.0.04, fldigi-4.2.03, Windows 10; I'm a Linux not Windows person so I'm struggling with the OS but with WSTJ-X working I suspect an issue with the "fls". What tools are available to diagnose this in Windows 10?
|
Re: Sibtx v3, the open source Hybrid SDR is released
Very nicely done Sir's.
73.
Dave G0WBX.
--
Sent from a MicroSoft free zone:
|
Re: DE19 + Quadra + WSJTX = PROBLEMS
helped a friend with the same issue open alasmixer, select the de19 and unmute it
|
Sibtx v3, the open source Hybrid SDR is released
As some in this group may know, that I have been working on an open source SDR that uses FLDigi in the backend. The sBitx is based on the Raspberry Pi.? The v3 version of the software works even on the Raspberry Zero 2W that costs just $15. It offers many features including N1MM style logging, FT8, CW and supports on-board FLDigi. You can view the source code and the circuit at?, the manual is available on? The interesting part is that I took a different route and implement the SDR using convolution method. I have detailed?this approach on my website at? Here is a video of the sbitx running FT8? Here is a video of the sbitx running CW with?macros, logging, decoding, etc
|
Re: First Post !!! FLDIGI on Raspberry Pi 400
Like that quote !!! As a retired ee i can relate.
|
Re: DE19 + Quadra + WSJTX = PROBLEMS
I used the DE-19 with a Raspberry PI and its version of Ubuntu Linux without any problems. The issue for you may be BRITTY service. BRITTY takes over modem device (cell phone or modem). You may need to disable the BRITTY service. Use dmesg to see if this is happening. If it is then a Internet search for "disable linux britty" should give you the instructions to disable or remove britty.
Enjoy Life, Greg
Live Well, Laugh Often, Love Much
toggle quoted message
Show quoted text
On 12/13/2023 23:48, Bo, W4GHV wrote: I found the DE19 does not work with Linux. I resorted to the CE 19 and soundcard,
|
Re: First Post !!! FLDIGI on Raspberry Pi 400
Yes, but the dialog shown on StackExchange shows a submenu. First choose 6 the advanced menu, then A6 for the Wayland to X11 conversion...
Then after the X11 setting is active do a reboot and then in a terminal do: sudo apt update && sudo apt dist-upgrade
in order to install all the missing things for X11.
Log off/log on or reboot.
If you did any settings for the Upper screen bar in Wayland:
They will all be lost and you end up with an empty bar.
73,
Peter - PA0PJE
Op 2023-12-13 om 18:08 schreef WF5W:
toggle quoted message
Show quoted text
I second the motion to not use wayland yet.
As bad as X11 is code wise. It just works well for the user.
see this link for how to do that:
extremely easy.
Jerry
----
Extra Ham Radio Operator: WF5W
Registered Linu=x User: 275424
3D CAD designer
The most exciting phrase to hear in science - the one that heralds new
discoveries - is not "Eureka" but "That's funny...". - Isaac. Asimov
On Wed, Dec 13, 2023 at 8:19?AM Cliff, AE5ZA <ae5zaham@...> wrote:
The issue is Xwayland. Go back to the last version it runs great with
fldigi etc. Been doing it for years. Xwayland is *not* ready for prime
time on the Pi. I'm running 64bit PiOS on my Pi-400. I also have an install
of Manjaro which runs great as well on the Pi-400. It's very similar to
PiOS, but a bit more refined interface.
73,
Cliff, AE5ZA
On Dec 13, 2023, at 07:30, sdegroff, W8SRD via groups.io <
sdegroff@...> wrote:
Weell. The saga continues...
Installed Ubuntu on ssd. Still slow. Xwayland still hogs cpu.
Then wrote over ubuntu with pi-os. Still same. Xwayland hogging cpu. I
guess I'm about done trying to run fldigi on pi 4.
Will run only wsjtx on it and still run fldigi on lap top(s). Thanks for
your help.
73
W8SRD
|
Re: DE19 + Quadra + WSJTX = PROBLEMS
I found the DE19 does not work with Linux. I resorted to the CE 19 and soundcard,
|
Quadra Armbian audio help
Noted this is the Win fldigi group. Is there a Linux group?
Whoops. I found it and will post there.
Anyhow, a simple question for Linux fans.
fldigi displays the audio connections of the top picture. It does not work.?
Wsjtx, js8call show what's in the second picture. And WORKS.
System is a quadra Armbian 64 bit ?Linux system
 
--?
73, Bo W4GHV since '54
|
Re: First Post !!! FLDIGI on Raspberry Pi 400
I second the motion to not use wayland yet. As bad as X11 is code wise. It just works well for the user.
see this link for how to do that:
extremely easy.
Jerry ---- Extra Ham Radio Operator: WF5W Registered Linu=x User: 275424 3D CAD designer
The most exciting phrase to hear in science - the one that heralds new discoveries - is not "Eureka" but "That's funny...". - Isaac. Asimov
On Wed, Dec 13, 2023 at 8:19?AM Cliff, AE5ZA < ae5zaham@...> wrote: The issue is Xwayland. Go back to the last version it runs great with fldigi etc. Been doing it for years. Xwayland is not ready for prime time on the Pi. I'm running 64bit PiOS on my Pi-400. I also have an install of Manjaro which runs great as well on the Pi-400. It's very similar to PiOS, but a bit more refined interface.
On Dec 13, 2023, at 07:30, sdegroff, W8SRD via < sdegroff@...> wrote:
Weell. The saga continues...
Installed Ubuntu on ssd. Still slow.? Xwayland still hogs cpu.
Then wrote over ubuntu with pi-os. Still same.? Xwayland hogging cpu.? I guess I'm about done trying to run fldigi on pi 4.
Will run only wsjtx on it and still run fldigi on lap top(s).? Thanks for your help.
73
W8SRD
|
Re: First Post !!! FLDIGI on Raspberry Pi 400
The issue is Xwayland. Go back to the last version it runs great with fldigi etc. Been doing it for years. Xwayland is not ready for prime time on the Pi. I'm running 64bit PiOS on my Pi-400. I also have an install of Manjaro which runs great as well on the Pi-400. It's very similar to PiOS, but a bit more refined interface.
toggle quoted message
Show quoted text
On Dec 13, 2023, at 07:30, sdegroff, W8SRD via < sdegroff@...> wrote:
Weell. The saga continues...
Installed Ubuntu on ssd. Still slow.? Xwayland still hogs cpu.
Then wrote over ubuntu with pi-os. Still same.? Xwayland hogging cpu.? I guess I'm about done trying to run fldigi on pi 4.
Will run only wsjtx on it and still run fldigi on lap top(s).? Thanks for your help.
73
W8SRD
|
Re: First Post !!! FLDIGI on Raspberry Pi 400
Weell. The saga continues...
Installed Ubuntu on ssd. Still slow.? Xwayland still hogs cpu.
Then wrote over ubuntu with pi-os. Still same.? Xwayland hogging cpu.? I guess I'm about done trying to run fldigi on pi 4.
Will run only wsjtx on it and still run fldigi on lap top(s).? Thanks for your help.
73
W8SRD
|
Alistair - M5ASF
Philip Rose, GM3ZZA
Bruce W4BRU
Greg Majewski, KD1XI
Peter PA0PJE
Bo, W4GHV