开云体育

*My understanding of the X6100:* This in not a KX2 or KX3 or a IC-705 and it does not cost $1200 either. For me its better than a FT-818 and not better than IC-705. It is a cheap experimental radio and fun to play with. To hack and mod freely. To tinker and maybe to break it while doing it... Did you ever imagined it would be possible to modify the UI accordingly to your taste in a HF rig? Now you can. It should not be your first radio, it would be better if you spend more, or buy one of the big 3 used. I rather have the X6100 in one pocket and an efhw in the other and have QSOs in 2 minutes than to spend extra 140USD in a cage and extra 120 in a pelican case and extra 300 in an external ATU [like the IC-705] and be worried about not to scratch any part of its plastic case. *A note about the ATU* : I find its internal ATU very adequate to fool the rig on a resonant antenna on the lower [or upper] part of the bands for that matter. Any QRP operator understands that ANY tuner will insert losses, so all the antenas should be resonant. You use internal tuner if you want to work SSB or CW if your antenna is has narrow band, but not far from 1:3 SWR. When I want to use a random [not so] wire antenna, my ATU-100 sits right at the antenna feed point, and the coax runs from the rig to the tuner. I like it. Does it worth what you paid for it? YES Does it compare with your IC-705? Never wanted it to. Any of the existing bugs prevent you from using the rig? None. Have I seen a real use case to use WIFI or Bluetooth? None, and for CAT or logging or digi modes it will definitely drain the battery. Why are you complaining about a radio that you never owned or operated? Don't tell me its because of what you read on the interwebs?! In the /g/xiegu-x6100 group I never saw anyone complaining, just sharing their observations and wishes of improvements. Regarding on what can be done with the rig so far, tear down, and what might be done, please subscribe to this great channel "Temporarily Offline Ham Radio": https://www.youtube.com/c/temporarilyoffline And for your viewing pleasure I invite you to watch this video: https://youtu.be/AUNKxV52HMI Now go and press the PTT.

Please visit https://www.radioddity.com/pages/xiegu-x6100-discount to get your 30USD discount!

Hi! Has anyone here ever looked into the issue of inherent audio noise in the RX audio path of the Xiegu X6100? Lately, I’ve been listening to this device a lot on headphones, and I have to admit that, for example, compared to another QRP device I have on the bench — a transceiver based on Chris M0NKA's project — the Xiegu fares very poorly (the situation is similar when comparing the X6100 to the Elecraft KX3 — but of course, the KX3 is in a somewhat different league, so I’ll leave that comparison aside). I don't have any solid measurements to share right now, but simply plugging headphones into both transceivers with the VOL/AF Gain turned all the way down reveals huge differences! I say this with a heavy heart, but the X6100 sounds like a terrible noise box! When working with an external speaker, it’s not as noticeable, but with headphones, it's quite pronounced. Maybe there are people here with the appropriate engineering knowledge who have analyzed the design of the X6100's audio path and have some thoughts? Maybe, to some extent, this is an issue that could be addressed at the software/firmware level as well. 73 de Jarek SP9HGN

Hello, I am needing help connecting my X6100 running R1CBU to FLRIG. I am having issues with the computer connecting to the radio via USB. Any help is greatly appreciated! Thanks, Landon KQ4DAA

Where can I find the x6100 ip address for entering into WFView settings. I have looked in my router and see the x6100 but it does not give the ip address. My WiFi uses DHCP. My x6100 shows wifi connected. WiFi SWITCH set to ON

Hi. I do some more changes on 1.1.6 BASE firmware - fix AM transmit, add a soft limiter, output power control. I decide to track changes within github repo: https://github.com/gdyuldin/x6100_base_patch/tree/1.1.6 Current version is rev1 (r1) - this suffix will be shown in the system info instead of the build time for BASE version. Some details: * FM - depth of modulation increased 10 times. Output level configured to not "disturb" ALC (reduced for ~ 13 times). Output power remains the same. * AM - in theory carrier power should be 25% of the max output power with modulation depth equals to 1. I made it about 50% of configured output power. Guess, that positive peaks will be correct handled by ALC. * Soft limiter for AM - I added it to prevent overmodulation. It adds some distortion for a loud signal, but I guess it's a less evil than distortions due to overmodulation. * Output power is now affects a level of the generated IQ signals. Previously - changing output power only changes ALC level, without actual changing signal level. Perhaps, I'll try to add FM squelch in a future version. Also - I checked controlling compressor (on/off) from the alternative firmware - it's working. I guess, ratio control will be configurable too. -- Georgy // R2RFE

This post is mainly addressed to the authors of the alternative firmware for the X6100, who have gave a new lease of life to our favorite radios: Oleg R1CBU and Georgy R2RFE. However, others are also welcome to join the discussion! It has become common to refer to the alternative firmware for the X6100 as "R1CBU's firmware" - and while this name was absolutely appropriate for a long time, now that Georgy has taken over the development of the software, it feels a bit problematic to me. After all, the software is no longer solely Oleg's work, but also Georgy's! Personally, out of respect for both colleagues, I use the name "R1CBU/R2RFE's firmware" in my statements, but I feel this name isn't perfect. Hence my question - do the esteemed Authors plan to give their project some kind of "codename"? On the one hand, it's a rather trivial and minor matter, but on the other hand, it could help improve communication a bit. Once again, thank you both - Oleg and Georgy - for the tremendous work you've done and continue to do in developing this software! 73 de Jarek SP9HGN

My X6100 came with Mar 7, 2023 APP V1.1.6 and BASE V1.1.6. Currently, Radioddity has 2024-09-23 APP V1.1.9 and BASE V1.1.8 available for download. I'm thinking about loading these. Are there any cautions I need to be aware of? If these updates go well, I’d like to try the great-looking APP software being developed by contributors to this group. On another subject, my biggest issue right now is getting WSJT working. It worked okay with my old laptop. My new Dell laptop has USB-C ports only, and my X6100 doesn't seem to like a USB-C cable connection alone. Using a USB-A to USB-C adapter at the laptop interface, and then a USB-A to USB-C cable, allows my Dell to recognize the two USB ports on the X6100. I’m using data cables. Sometimes it will receive FT8 but not transmit. Other times, it doesn't work at all. I've tried various cables and adapters. Is it a driver issue with the X6100 not being compatible with USB-C standards? Reversing the cable with the adapter apparently also reverses which unit is acting as the host, so it's a one-way data path. In my case, things only worked when the USB-C to USB-A adapter was used on the laptop end—not on the X6100 end. This is all very frustrating for an old analog ham who doesn’t have any hair left to pull out. Has anyone successfully gotten their X6100 to interface with WSJT using only a USB-C cable between the DEV port and their laptop? If so, what firmware/software were you using? -- Mike NN3I

Inspired by wicknix's color changes, I came up with the idea of allowing anyone to customize color, styles, palette, etc by just editing (say with notepad) a simple text file in the DATA partition. The file is called 'styles_custom.txt', and it uses a very simple key = value format like this: # test styles customization # Franco Venturi K4VZ # Sun Apr 6 10:00:25 AM EDT 2025 wf_palette = gauss #bg_color = 0x27313a bg_color = 0x56a346 btn_bg_img = images/btn_dark.bin msg_bg_img = images/btn_dark.bin clock_bg_img = images/top_short_dark.bin info_bg_img = images/top_short_dark.bin The above example just changes the background color to green, but you can see how it works (lines beginning with '#' are just comments and are ignored). This is mostly still a proof of concept, so I just put a dozen or so settings from the 'simple' style in it, but the possibilities are endless. For instance you can even customize your waterfall palette by creating an entry called 'wf.palette' with a list of 256 values (see the file 'styles_custom_palette.txt' for an example, where I just reverted the list of the colors to create a 'negative' waterfall palette, just for fun). For those who want to use a more organized way of managing those settings, I also created a simple Python script called 'toml2txt.py' that you can use to convert from a file in TOML format (https://toml.io/en/) to 'styles_custom.txt'. All these example styles customizations and the Python script are here: https://github.com/fventuri/x6100_gui/tree/styles-custom/styles An SD card image based on the 'x6100_gui' version by wicknix plus the styles customizations code I wrote is available here: https://github.com/fventuri/x6100-buildroot/releases/tag/20250408-styles-custom Pease let me know what other settings you would like to be able customize or other enhancements you would like to see. Give it a try and have fun! 73, Franco K4VZ

I originally posted about this in the buildroot 2024.11 thread, but figured it'd soon get buried as new versions of buildroot come to light. Anyway, i wasn't a fan of some of the default colors. Was hard on my eyes at times. This is not part of upstream, or official. It's just my personal build that i built using Franco's 2024.11 buildroot that i'm sharing in case others want to give it a try. This is my 3rd and last color revision. There won't be any more changes as I'm happy with it now. If upstream wants to merge my color changes they are welcome to it. Otherwise i will continue to build with these color changes when new versions of the firmware are released. Download here.

Dears, as I had done it for me I would like to share the R1CBU X6100 FW image with you. I have applied the patch 20.1. and extended the third partition to 2GB if someone needed more space as the default configuration of 512MB. The image is published at filetransfer.io under the corresponding link listed below. https://filetransfer.io/data-package/O1vSQ5zQ#link an alternative file storage link https://gofile.io/d/bZLAml Unfortunately available only for 21 days as I'm not a registered member. Hopefully this image is useful for someone who run in problem to install the 20.1 patch. Image is around 2.7GB and have to be unpacked first form the zip compression. vy73 Markus DL8MBY