I had a similar problem. The X6100 is sensitive to SWR and will reduce power a lot if SWR is over 2.

To be 100% sure the ATU is locked in do the following.

Make sure TX CQ and TX call are disabled.

Long press ATU.

When ATU is finished reenable TX CQ and TX Call.

If the antenna is still out of range of the ATU you will not get the full 5 Watts.

?

Hope this helps.

OK - following on from the FT8 questions..

?

For some reason, since this morning, I have not been able to get more that 2w out on FT8 / FT4 and when tuning the ATU.

I have tried updating the X6100's base firmware and also created another R1CBU Firmware disk (multiple SD cards used) which does not overcome the problem.

?

If I run the native firmware everything seems to work OK and the output levels are normal - But as soon as I boot into the R1CBU Firmware things do not seem to work as they used to.

I have also noticed that the "Output Power Reduced to 5W" message is missing.

?

Can someone suggest a fix please ?

Mine works but will only transmit at 2w and there’s no Reducing Power to 5w message

Does it transmit at all?? SSB?? AM? CW?

The same thing just happened to me this evening. I'll be following this thread for sure.

?

?

I found a value to adjust FM modulation level. In attached base firmware it's increased 3 times. Hope it will be enough.

--

Georgy // R2RFE

There is a discussion about saving/restoring settings on the github: https://github.com/gdyuldin/x6100_gui/discussions/20

--

Georgy // R2RFE

Another option that I thought of to keep the data persistent across R1CBU firmware upgrades would be store it somewhere in the internal MMC device instead of the SD card.

I wrote the attached S01mount_data script which can be used in lieu of S01create_data, and the data will be stored in the radio itself.

?

Of course one of the issues with this approach is that if the X6100 dies and needs to be replaced, that data is gone too; also backing up this data is doable but it is a little trickier.

?

Franco

?

?

Let me add, if you are using Windows, when you put the card back in your PC to copy back your backed up data, the Data partition may not show up as a drive.? That is a Windows issue.? You need to go into Disk Management, find the correct drive, right click on the Data partition and add drive letter.? You can now copy back the data to it.

?

Also note that this does not back up Wifi passwords.? That is covered in another message thread.??

Randy,

if you are familiar with Linux, you could add these few lines to the '/etc/init.d/S01create_data' script that should hopefully preserve the existing DATA partition on your SD card:

?

These lines need to be added after you write a new R1CBU firmware upgrade to the SD card, and before you put that card with the new firmware in the X6100.

?

Basically right after you write the SD card, you have to mount /dev/sdX2 somewhere on your Linux PC, edit the file <mountpoint>/etc/init.d/S01create_data, add those lines in the same place as in the link above, and finally eject the card (eject /dev/sdX).

?

You may want to make a backup first, should something go wrong.

?

73,

Franco K4VZ

?

Thank you, Lance!

73, Randy K7RAN

P.S. I previously buried this question in a barely-related thread and got no traction, so I thought it better to create a topic.

Yesterday I updated to firmware 1.1.9 but now the lower buttons have a malfunction. If I press RADIO SETTING1 the SYSTEM SETTING menu appears.. if I press EXIT .. the RADIO SETTING1 menu appears regularly. If I press RADIO SETTING2 the MEMORY menu appears.. if I press EXIT RADIO SETTING2 appears regularly. Unfortunately, as regards the CW menu (KEY button) now the two buttons on the left do not work correctly and I cannot change the type of button or speed. If instead I connect a mouse to the USB port and select the various menus from the display .. everything works regularly. I also tried to do a FACTORY RESET and return to the old firmware (1.1.7) but the problem remains. Has this happened to anyone of you?

Tonight I figured out that the problem with the soundcard not being identified as 'alsa.platform-sound' was actually a problem due to udev (which in buildroot is implemented by 'eudev') where one of the rule files: '78-sound-card.rules' had a line that made it skip assigning ID_PATH and ID_PATH_TAG to the platform sound card. The offending line was introduced by this commit:

Reverting that commit for that specific udev rule file (i.e. commenting out line 56 in '78-sound-card.rules') fixes the problem with the PulseAudio sound device name that I found over the weekend.

?

To work around the circular dependency between libsndfile and lame/mpeg123, I also created a new package called 'libsndfile-with-lame-and-mpeg13', which uses the same version number and all the other attributes of 'libsndfile' but has additional dependencies on lame and mpeg3:

This way the package 'libsndfile-with-lame-and-mpg123' gets built (and installed in the target directory) after lame and mpg123 have been built, and therefore has everything it needs to work with those libraries. I then made x6100-gui select the new 'libsndfile-with-lame-and-mpg123' package.

?

I just committed these two changes to the x6100-buildroot repository:

?

73,

Franco

This is a hardware design issue. I just live with it?

73 Ron n9ee

The problem is that I have that strong noise you saw on the video in all bands and, when moving the VFO, both signals, the one at the beginning of the band width shown in the screen and the one at the end, both follows the movement up or down. Those two are always present on the screen, no matter which band you are on. Again, this only happens when on battery and only when the alternative firmware is in use.

?

73

Rob

YS1RS

On Tue, Dec 17, 2024 at 04:13 PM, Franco Venturi wrote:

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.

I know, but I thought there is a better solution.

--

Georgy // R2RFE

Hi Gang,? ?I'm loving the R1CBU et al firmware running on a memory card.? Since I started playing with it I've logged 288 FT8 contacts.? It's surprising what 5 watts can do and it will be great for POTA and other uses.? No extra toys other than an antenna required.

Thanks to all who worked on this project and continue working.

?

73, Gregg W9DHI