Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Xiegu-X6100
- Messages
Search
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Markus,
thanks for reporting the problem with FT8 TX. Last night I started looking at why in the new buildroot the sun8i-a33-audio soundcard gets reported as 'alsa_card.0' instead of 'alsa_card.platform-sound' like in Georgy's buildroot. Hopefully when I figure that out, I'll also be able to explain the problem with TX. I am starting to see that the Linux sound system is rather complex.
?
Frank,
thanks for the nice words. Unfortunately I don't have a GSOC and my free time is very limited these days, so I won't be able to help you much, but hopefully someone else with a GSOC can take a look at what we found out and did so far and figure out the changes to make it work with the GSOC. Also I suspect that most of this work applies to the new X6200 as well - I am not in that group but hopefully someone there is already making progress on something similar for the X6200.
?
Georgy,
the issue with libsndfile and lame (and mpeg123) is that in buildroot lame has a dependency on libsndfile (), so that when both BR2_PACKAGE_LAME=y and BR2_PACKAGE_LIBSNDFILE=y, then buildroot builds libsndfile first (which gets built without lame) and then lame (because of that dependency). I haven't looked at mpeg123, but I suspect there might be something similar going on there too.
?
73,
Franco |
Re: Setting FT8 with firmware v0.28.0
toggle quoted message
Show quoted text
On 16 Dec 2024, at 15:13, HB9FBG via groups.io <hb9fbg@...> wrote:
|
Setting FT8 with firmware v0.28.0
Hello, everyone,
I need a little help. To be honest I've only been using the x6100 on CW but as I'll probably be taking a few days holiday I'd like to do FT8 with firmware v0.28.0. I have everything configured and everything seems to work very well in reception... but I can't get it to transmit. It doesn't seem to take the impulse to go to transmit (the TC tag appears). I guess it's stupid but I've tried several ways and can't get it to transmit. I also looked for a manual but couldn't find it Thanks in advance for any indication 73 Mauro HB9FBG |
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Franco and others,
?
Thank you all for your work on improving the abilities of the x6100 hardware. It is much appreciated!
?
A wish for the New Year: similar efforts applied to the GSOC device, now gone into non-supported mode by Xiegu.
?
73,
?
Frank
K4FMH |
Re: Problems charging internal battery / R1CBU/R2RFE firmware
Thanks to all for your suggestions! Everything very interesting!
?
My X6100 still has a valid warranty so I'll try Radioddity first before opening the seals...
We'll see and I'll let you know about every good solution.
?
Tnx again and a merry xmas - Uli / DK9TZ
?
? |
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Hi Franco,
with this patch CW Decode and FT8 is working again.
?
For me, I like it when a newer buildroot is used, because the currently used one needs e.g. patches to work with actual Compilers, here gcc-14.2
Thanks for your work. ?
And of course thanks to all the people you have already mentioned here to make the x6100 a better device.
?
73 de Markus, DB2ZW
|
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Markus,
I found out that sometime between the buildroot version used by Oleg/Georgy and the latest 2024.11 version, PulseAudio changed the names of their devices. For instance what used to be called 'alsa_input.platform-sound.stereo-fallback' is now called 'alsa_input.0.stereo-fallback' and what used to be called 'alsa_output.platform-sound.stereo-fallback' is now called 'alsa_output.0.stereo-fallback'.
Since those names are hardcoded in the source file 'audio.c' in 'x6100_gui', I just added another patch to 'x6100-gui' that fixes those names ().
?
Since I only changed 'x6100-gui', you don't have to rebuild everything from scratch. You can just run these commands:
?
cd x6100-buildroot git pull ?
Then in the build directory:
?
export BR2_EXTERNAL="$PWD/x6100-buildroot" rm -fr output/build/x6100-gui-v0.28.0 make ?
With that change I am now able to see the waterfall in the FT8 dialog. I haven't tried decoding though, because I don't have an antenna here in my office.
?
?
Rui,
thanks for the kind words and thanks for all the research and pioneering work you and Oleg did a couple of years ago!
And also thanks to the many others who helped like Steve of Temporarily Offline,? WheezyE, DreamNik, crazycats100, jose_can_u_c, and the many others on #xiegu-x6100-hacking in the TOADs Discord server.
?
73,
Franco K4VZ
? |
Re: X-6100 and Xiegu XPA125B
I've been checking it out. At 10 Watts and the amp off it transmits 10 W.? Looking at the waterfall, I could see the signal.
I switched on the amp and switched off the PA. The amp reported ~3 Watts.? I don't think that reflects the actual power since the signal is just going through the amp. FWIW, the waterfall showed the same as when the amp was off.
I don't know that the waterfall shows the TRANSMIT power, but I really do think you are getting the full 10 W whether the amp is off or on.
73
--
Mike - KD9YKI |
Radio gets noise on RX when on Battery Alternative Firmware v0.28.0
I have a strong noise on all bands when using Battery with Alternative Firmware v0.028.0
-Problem is shown on RX.
-I don't see that on TX but I hear my own voice on the speaker if I call SSB. Monitoring level is at 0.
-Shows up at beginning of the band and at the end.
-With or without antenna.
-Noise goes to minimal, but still there, when the screen dims out after a few seconds not touching the VFO or any button in the radio.
-Goes up again, as soon as I wake up the radio by touching the VFO or any other button.
-Goes off as soon as I plug in the external power.
?
In brief: The problem is not there or does not show up if using external power.
With Battery the radio shows 7.8V on the screen.
With external power shows 13.6V on the screen
Happens in all bands.
Not happening with standard Xiegu Firmware
App V1.1.9 Sept 14 2024 12:11:57, Base V1.1.8 Sept 15 2024, 15:22:37 ?
I made a video that shows the problem live for you to see.
?
Suggestions what could be happening are welcome.?
?
73
Rob
YS1RS |
Re: Problems charging internal battery / R1CBU/R2RFE firmware
The name "Shadow charging" was invented by Oleg, after my suggestion of the feature.
Stock fw only had options Charger On or Charger Off.
If you wanted to charge the battery with the supplied external charger you had to turn "Charger On" in the settings each time you turned the radio off.
Likewise you had to go to settings and turn "Charging Off" before transmitting, as it was recommended to NOT CHARGE BATTERIES WHILE TRANSMITTING.
I suggested the feature of "automatically turning charging on when powering radio of" and vice versa.
And Oleg implemented it ? |
Re: Buildroot 2024.11 for R1CBU/R2RFE firmware
Georgy, I understand 100% and, as you can see in the comments here, there are still bugs with FT8 and CW that I need to figure out.
?
This said, I think you may still want to look at the patch I wrote for 'x6100_gui' to make it compile with gcc 14 without errors: - there were a couple of minor issues, but in one case the variable 'qth_val' is defined as an array of pointers to char, instead of a char array (i.e. a C string).
?
Franco |
Re: Problems charging internal battery / R1CBU/R2RFE firmware
Regarding the charging of the internal battery of the X6100, you may want to take a look at my post ten or so days ago: /g/xiegu-x6100/message/6468 and perhaps collect some information on the battery charge process by running the 'monitor-charging' Python script while the X6100 is charging (runs on Linux and needs the USB cable connected to the 'DEV' port).
?
These are my findings from that post:
- in my case too the LED stayed solid green while the battery was charging, so I don't know if it really matters (as long as it is not completely off)
- if you look at the plot of the battery voltage and charge vs time, the logic of the internal charger of the X6100 is very simple: constant current (about 177mA) until the voltage reaches about 8.43V, then constant voltage. At constant voltage it looks like the battery is still being charged at about 35mA
- I am not a battery expert, but it looks like the batteries (there are actually two of them in the X6100 connected in series) can be overcharged above 6000mAh - in my case the firmware was showing up to 6600mAh, but looking at that plot I suspect it could have gone even higher
?
73,
Franco K4VZ |
to navigate to use esc to dismiss