开云体育

*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!

I agree with Roberto. Also, I believe that the X6100’s TX power comes down with reduced input voltage. I’ve found two things to help: Light, portable/rugged voltage converter, suitable for Sota/Pota. “DROK DC-DC Stabilizer, 9V-36V to 12V Boost Buck Converter 5A 60W Waterproof Auto Step Up Down Voltage Regulator 12V Volt Transformer” at Amazon US. Quiet, low power fan suitable for shack use. “ELUTENG Dual Cooling Fan - Whisper Quiet 80mm USB With 3 Adjustable High Speed USB Port” also on Amazon US. The fan is very quiet on lowest setting and keeps the X6100 ~ room temperature. Tony KE1TLg From: [email protected] <[email protected]> On Behalf Of Roberto - YS1RS via groups.io Sent: Saturday, March 29, 2025 6:58 PM To: [email protected] Subject: SPAM Re: [xiegu-x6100] x6100 Com ports not seen on my PCs. Regarding the Max voltage mentioned by Xiegu, yes, it might work above 13.8 Vdc. but the radio will run hotter. I wouldn't trust the Xiegu Max specs. The 11.0 Vdc, is just to make the radio run cooler. It will still give you 10W but with less heat and less electronic stress for the components. What a few of us have done, it that we use a small device called Drok Charging Module. You put in 13.8 and you can adjust the output down to 11 or less. It helps keeping down the heat. 75W NC Charging module/Adjustable Voltage Regulator DC 6~32V to 1.25~32V 5A Buck Driver Module DC 12V 24V Adapter/Driver Module With LCD Voltmeter/Ammeter/Capacity Indicator 75W NC Charging module/Adjustable Voltage Regulator DC 6~32V to 1.25~32V... It is a 75W NC Power Supply Module/Charger/Voltage Regulator, DC 6~32V, Output voltage: DC 1.25~32V, Output curr... It is very cheap and helps a lot. Make sure you order the case of it, if you want to try it.. In fact, the internal batteries in the Xiegu, only will give you 8 volts or less. That's why you only charge them with the original charger that came with the radio. If you charge them with 12 Volts, your batteries will charge, but won't last long. For you guys, in the US and/or Europe, it is easier to order a new radio when this one dies. You get a new one in 3 to 5 days. Warranty issues? no problem just send it back for repair/replacement. For me in YS, it is not easy. Even if I have active warranty for a radio, to send the radio for repair to China or the US/Europe is so expensive and takes a couple of months. No way! I try to take care of my radio as much as I can because for me, this is like a trip with no return. 73, Rob YS1RS On Saturday, March 29, 2025 at 04:00:57 PM CST, Yvon via groups.io <yduboistime@...> wrote: A lot of information, thank you Rob. Looks like the replacement board will not solve my problem. I have been through the radio's belly and couldn't find anything visually. I never use more than 3 watts when doing ft8 or I use an external amplifier. As for running the radio while charging I normally don't do it but sometimes might forget about it. What is more a problem is the external supply of maximum 11v. Most ham supplies output 13.8v as required by most Icom, Yaesu, Kenwood and others. Even the Bioenno batteries have a voltage above 11v. Isn't the Xiegu spec shows 15v max? The only thing on my 6100 that is a show stopper with the DEV port not working is that I cannot connect a GPS. Not a big deal I can synch with the internet at home. I don't do ft8 portable. 73, AE7YD

Hi everyone, Has anyone encountered problems using the X6100 in FM mode on 10m? Recently, I paired mine with a 4m transverter from UR3LMZ, and several of my contacts reported low modulation levels, even with the mic gain set to the maximum (50). Additionally, the received signals were noticeably noisy. At first, I suspected the transverter might be the issue, but after testing directly on the 10m band with another transceiver, I observed the same results. Interestingly, everything works perfectly in SSB mode. Has anyone else experienced similar behavior, or could there be something I'm overlooking?

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.

Had successful FT8 cq cntacts with Rc1CBU software. Removed the adi record of contact from the sd card and uploaded to the eQSL logging program. Further checked the software to confirm the record was in my outbox of eQSL. No luck! so, cotacted eQSL support for some insight. The following is their reply " >> Uplog is processed but not found in my out basket file - your logger is not recognized that is one thing : The author of the logging program needs to add it, we have a special form that he can use to enter the details, including header information so that the import routine here will recognize uploads from his program." I could probably enter the information manually with each qso but if automaticly it would be easier. Anyine with similar experience/solution? 73, K8SAR

Hi, As an experiment, I made a printed circuit board for a simplified (PTT-only) microphone and also a 3D-printed case for it. I built a few and they work although I have to turn the mic gain up a bit. This is probably related to the electret mic element that I used. The files to build this mic can be found here: https://github.com/scottlbaker/x6100-microphone Also I have a few extra circuit boards If anyone wants to try building one, please contact me by private message. 73, Scott KJ7NLA

First of all many thanks to Oleg and Georgy (and Rui Oliveira) for all their hard work on the custom firmware for the X6100! Over the last month or so I have been working on upgrading the base OS ('buildroot') of their firmware to the latest version; a few days ago buildroot released their version 2024.11, so I upgraded the base OS for their firmware to version 2024.11, and I think it is ready for others to play with. I just pushed my buildroot external tree to this repository: https://github.com/fventuri/x6100-buildroot For those running Linux, building a new SD card should be very easy - the instructions are here: https://github.com/fventuri/x6100-buildroot?tab=readme-ov-file#how-to-build This is a beta release for those who who are familiar with the software running on the X6100, and don't mind building from source; once the bugs are ironed out, I plan to build and publish an sdcard image. These are some of the highlights of this latest version: latest Linux kernel: 6.11.11 latest U-boot: 2024.10 newer version of liquidDSP x6100_gui version 0.28.0 (I had to patch it in a few places to make it build without errors - you can see my changes in the 'patches' directory) should always find the SD card as mmc0 thanks to mmc aliases in the device tree uses gpiolib instead of sysfs for controlling GPIO pins, because sysfs has been deprecated names for GPIO pins (instead of numbers), so now to power on Wifi you can just run 'gpioset -t 0 wifi=on' modified aether-x6100-control and x6100-gui to use 'gpioset' instead of working with device files under '/sys/class/gpio' disabled persistent network names, so now the Wifi network device is always wlan0 (instead of becoming wlan1, wlan2, etc after every on/off) There are more changes I made, but I think these are most important that I can think of. The usual (and important) caveat: this is still an early beta version and very likely has a few bugs, but if you are not afraid of trying new things (it won't brick your radio), please give it a try, and let me know if you find any problem. 73, Franco K4VZ