开云体育

I'm in both groups.

Good afternoon everyone. When the X6100 group was formed I had one of the first X6100 radios and joined the group. I was also appointed as one of the admins at the time and was not asked if I wanted to do it. I did my best to keep up with the new moderated posts when the other moderator left the group. I was able to find a replacement who handled the admin duties for several months, and I did not leave the group, however I left all admin duties to the person who said they would take over. I recently saw moderated posts asking why their other posts aren't being approved and found out that person sold their x6100 and left the group. If I would have left a year ago we would have nobody moderating the group and doing the admin chores.

Once again, I would like someone to step up if possible and if I can get a hold of the Radioddity staff, I will submit your name to them. Please do not reply to this on the forum, please contact me via email privately. My email is good on QRZ.?

73 Scott
KN3A

I was just wondering if anyone here was also on the other X6100 group on groups.io?? ?I am trying to learn everything I can about this radio, so I tried to also join the other group.? However, I was rejected because it said my callsign and email address don't match my QRZ profile (they do).? ?Has anyone else run into this?

Jim

watch the power meter on the xiegu when I press the PTT button and holding the mic ...it modulates without saying anything...this only happens when the amplifier on the xiegu x125b is on....also when I select the built-in mic this problem doesn't occur even with the PA set to on ..only with the hand mic ..gain is set to 15 ..tried factory reset, swapping the mic cable the other way around ,trying a different cable nothing.. problem still occurs.
Update : i put a pair of headphones on and increased the monitor level to listen to the signal...all i hear is noise with some low level distorted audio in the background...and this issue also occurs when i select the built in mic and press the PTT.
In the beginning i thought it was a faulty hand mic but now that i se that the problem exists even built built in mic , i am starting to believe it is an amplifier issue...

I have the same experience as @scot forshaw, previous versions of the CW decoder worked amazingly well (especially compared with the Xiegu stock decoder).
Latest updates indeed do not function well, as Scott and I reported.

Thanks for all your good work,
Merry Xmas and a blessed New Year.

73, Reinier

On Mon, Dec 18, 2023 at 05:29 PM, Lon Lease wrote:

If knob velocity is greater than x step time 10 or 100?

Yes, that's understandable. I need to practically look at the rotation speed ranges and which multipliers are most convenient to use.

Forgot to mention... It was called "Variable Speed Tuning" back then.
You had a button to turn it on and off, of course.
Cause as you approached to your target frequency, was better to turn it off to avoid overshoot your intended frequency.
The weighted tuning wheel was very sensitive though.
Nowadays, we do this via SDR, thus can be controlled way much better.

Rob

First time I saw that feature was back in the year 2000-2001, implemented in the Patcomm PC-500 QRP radios, by Patcomm Corp.
Those radios were ahead of its time indeed.

Sure helps.

Rob

On Mon, Dec 18, 2023 at 02:27 PM, Lon Lease wrote:

It would be a very top end feature.? What do you think Oleg?

I don’t see any fundamental problems to implement this. I'll think about how this can be done beautifully

Hello Scot,

Hi Oleg,
I have a feature suggestion, I was wondering if it was possible to devise a fast slow dynamic tuning rate?

If you are on 10Hz and start to tune quickly it might step up to 100Hz then reduce back to 10Hz when the spinning slows down?

This is similar to the TECSUN PL-660 SW RX that has auto Slow/Fast tuning.?

For CW ops, it would be a massive help I think when you see a signal on the magnified spectrum but you are in 10HZ mode, it takes a long time to get top it without more button pressing.

I wonder if anyone else would like such a feature?
Thank you for you amazing work on this ?by the way, from one coder to another... it is very appreciated.

On Mon, Dec 18, 2023 at 09:52 AM, scot forshaw wrote:

Does your FW rely n the original base FW at all? I ask because I recently updated the the latest stock FW also..

Partially, all signal processing occurs in the BB processor - I cannot change this part yet. But I have installed BASE: V1.1.7 for a long time and everything works well.

Hi Oleg,
thanks for your reply.?

This morning I rolled back to V0.18 and found the same problem, at least on my radio. (decodes hang and mostly impossible to decode reliable)

So, I tried rolling back to V 0.171 and the CW decoder came back 100% perfect !!!?

For me V0.19 the decoder is not good in any but the best conditions - V 0.18 the same. V0.171 is amazingly good and every single QSO I tuned to (even bad signal) the decodes we quick, accurate and the text buffering was gone.?

The problem I see on 0.18,0.19 is that the decoder sometimes goes blank and never decodes, or it is so tight on the filtering notch that it is almost impossible to get the signal on frequency so that decoding starts.?
As soon as I loaded V0.171 my old amazing 6100 was back and tuning around almost any CW signal led to great performance.

?did try many many times with the the laster versions.?

?Does your FW rely n the original base FW at all? I ask because I recently updated the the latest stock FW also..

?there is anything you want me to try, ?am happy to oblige. Thanks, Scot

Hi Rainer, you are correct.

I have disconnected the internal battery.
On receive, no volume, BL lever 2:
External voltage versus current:
13.8 V / 342 mA (4,73 W)
9.0 V / 511 m A (4.6W)
With the nominal 7.7 V of the battery - I guess the current to be around 620 m A
With the 3 hours and 48 minutes this comes to a consumption of about 2360 mAh
This is 80 percent of the total capacity of 3000 mAh
And so my rig does not seem to be far off what we can expect.

73, Lorenz, HB9BMR

Another point to keep in mind is that the embedded system (Allwinner R16 quadcore) has its own power management chip with several DC/DC converters. When varying the supply voltage from 12 to 9V, you will see that the input current rises - DC/DC converters try to keep the input power constant, so the 330mA mentioned may be correct for 13.8V, but at 7V I would expect about double that value.
If you want to check whats going on during charging, the X6100 is transmitting the battery voltage, capacity and relative charge state on the second serial port. You have to connect via the "DEV" USB port, setting the UART to 115200, 8N1. Connect external power, turn on the radio, then turn on charging, then turn off the radio. You should see boot messages and then the charge status messages.

In my case (Win 10 laptop), the relevant serial ports are Com3 and Com4, the latter one for charging state.

With Olegs 0.19 software, my fully charged x6100 ran 4h 30min in receive mode, and after charging it showed 2900mAh. BTW the charging chip reported 100% charge state at around 1900mAh and 8V, that was the point when the blinking of the LED changed to permanent "ON" - but it kept charging until the battery was charged to 8.4V. I assume that several shallow discharge cycles confuse the Coulomb counter, but a few full discharge/charge cycles should correct that.
More info can be found in the bq24715 data sheet (available at the TI homepage). 8.4.6 Learn mode could be relevant here...

73,

Rainer DG1SMD

On Sat, Dec 16, 2023 at 09:57 AM, scot forshaw wrote:

Some updating to V0.19 I have been having a lot of difficulty in getting CW decodes working with any reliability. ini V 0.17 the decoder was an outright awesome improvement of the stock one, but I am really struggling to get the new one to play ball.?

Version 0.19.0 has exactly the same settings as in 0.17.0. Before the release, I checked the operation of the decoder.

Does anyone know what CW peak and CW noise BETA are? How to set them up

I guess I know (LOL).?These settings are set to optimal by default. I spent quite a lot of time on this. I should have removed them, but I left them for experimentation. Experiments have shown that it will not be possible to configure it even better.