Re: x6100 WFSERVER ip address
I can see the x6100 in my Eero6 router, but it doesn't show any ip address. So I entered an IP Reservation 192.168.5.12
I put that ip into the WFView settings. Still no connection.
I have tried the WFView forum without resolving the issue.
|
x6100 WFSERVER ip address
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
|
Re: Modified BASE firmware - rev1
I am also running 1.9 and 1.6 r1. The first time I tried it yesterday it was giving me the low wattage readings, milliwatts. I redownloaded the r1 firmware and reinstalled it and power is back to normal 10 watts on am and fm also.
|
Re: R1CBU / R2RFE - FT8 issue with prefixed callsign
I had considered that option as well, but I wanted to avoid writing the logic from scratch to verify whether a callsign is valid in FT8. However, now that you¡¯ve suggested it, I do think it would be a good idea to use ft8_lib for this purpose - for example, when saving a callsign, run a few tests with ft8_lib to check whether a CQ call with that callsign can be properly encoded and decoded, etc.
I¡¯ll think it over and try to come up with a solution!
|
Re: R1CBU/R2RFE firmware's codename?
I like "OpenX6100" also. But the work on the new UI app made it's way into Oleg's new project "TRX Brass". Brass is made of Copper (Cu) and Zinc (Zn), and the X6100 and the TRX Brass are related to each other - thus "CuZn-6100" (Cousin).
?
(This is 99.9% tongue-in-cheek!)
|
Re: R1CBU/R2RFE firmware's codename?
Being a non-programmer, I don't know the customary methods of code-naming forked open-source projects.
I think it depends on whatever the author(s) want to call it.
In my opinion, R1CBU with version number + whatever hasn't caused too much confusion for most people.
?
Having said that, I suspect there are still people out there using 0.20 since they don't know about the forked versions.
I see them on FB and Discord. I post videos on YouTube about newer forked versions but my viewership is very small. We need to spread the word.
I am not fond of the suggested code name but that's just my opinion. Being a geek, I prefer what's being used now.
?
I appreciate all the work done to improve our beloved radio. I am still hoping one day BT audio with X6100 works and I can rest easy.
?
crazycats100
|
Re: R1CBU / R2RFE - FT8 issue with prefixed callsign
Thanks! I'll check it detailed a bit later.
But I guess it might be better to add something to check whole CQ message with entered callsign encoding/decoding right after closing editor. Encoding FT8 is a bit complicated, agree. For example -? /P took only 1 bit, but /QRP - much more.
You right about hashes - at least CQ should be sent without hash, otherwise no one will know your real callsign.
--
Georgy // R2RFE
|
Re: R1CBU / R2RFE - FT8 issue with prefixed callsign
After a deeper analysis of the issue, I¡¯ve come to the conclusion that with ft8_lib, smaller or larger problems with encoding/decoding a callsign may occur whenever a QSO involves callsigns longer than 6 characters. In such cases, ft8_lib employs various data compression strategies to fit the information into the FT8 frame.
?
While investigating the issue, I noticed that even WSJT-X is unable to properly encode a callsign like SV9/SP9HGN/P - it truncates part of the callsign, which results in an incomplete frame being transmitted over the air. In my case, it was: ¡°CQ SV9/SP9HGN/¡± - missing the final "P":
?
As part of my proposed solution, I implemented two things:
- I added logic to detect the use of a callsign with a country prefix (e.g., SV9/SP9HGN). In such cases, whether in CQ or in a response to someone¡¯s call, the application will skip appending the grid locator to save precious data bits.
- I added a warning that appears when a callsign longer than 6 characters is set. For callsigns longer than 6 characters (e.g., HF100IARU), the application will be forced to use hashes in QSO, which may also be problematic (see:
Pull request:
I think, @Georgy, that would be good to cover such scenario with unit tests - I see your tests in repo, but I had some issues with executing them locally. I know it's rude to left someone with unit tests implementation, but if you'd have some free time, please, take a look on my changes and help me with writing units for them :)
Generally speaking, encoding long callsigns - especially those with prefixes or suffixes - in FT8 is a far more complex issue than I initially thought. To be on the safe side, a good practice is not to go overboard and stick to callsigns that do not exceed 6 characters.
Cheers!
73 de Jarek SP9HGN
?
|
Re: Modified BASE firmware - rev1
I'm afraid, that there is no way to know HW version. Let's check, is OEM FW operates different on different radios.
?
Could you flash your radio with this firmware ( /g/xiegu-x6100/message/7004) and check power (and ALC) with AM and FM without signal (mic gain to zero)? My values for 10W, external battery, zero mic gain: AM - 10W, ALC 9.3 FM - 10W, ALC 9.3
?
?
Also, I created rev1 with +10 dBm of output - could you test, how much output power and ALC value it will produce in FM and AM?
--
Georgy // R2RFE
|
Ordered cables and found that they work!
--
Mike NN3I
|
Re: R1CBU/R2RFE firmware's codename?
Agree on all points.
(and I've named a few commercial tech products in my day, including my favorite, a focused search engine we dubbed Quando. Not my idea, but I know a good name when I see one).
?
I like CanaryNest. Or just Canary.?
Nest has some other connotations, but the Canary is a birdie.
?
Onward!
David
|
Re: R1CBU/R2RFE firmware's codename?
Huh. A fan of a beloved ¡°product¡± thought it would be great if it had a name. Like someone who really loves their car might give it a name. He respectfully asks the ¡°parents¡± if they have something in mind.
?
Oleg defers the idea to Georgy, who makes a fun quip about variable names and then comes up with a jokey name. He even solicits others to join in on the fun. So the current developer of the software has explicitly asked people to play with him.
?
This playfulness is one of the longstanding traditions of computers and tech in general. So much software is named with in-jokes, fandom references, puns, or whimsical nonsense. I think it¡¯s something wonderful about geek culture. We like to play. We giddily share the delights we find in our hobbies.
Career businesspeople have serious meetings developing strategies for cornering market segments. Cutthroat competition can make people at the top of a big company millions, and drive other, often small, companies out of business. Their goal is to make money and it¡¯s serious work.
?
Open-source developers write non-commercial software because they love it. They work a crazy number of hours on their ¡°product,¡± almost always without any expectation of pay or profit. They come up with tools for themself, then excitedly share it with others. They make for the joy of making and share for the joy of friendship. The names of their creations often reflect this. Users often have such a love of a tool they embrace a whimsical name, making up logos, t-shirts, and making new tools with fun derivative names.
I had previously thought of it as ¡°Oleg¡¯s firmware,¡± but now that it has dual-custody, I agree the name has gotten unwieldy. It¡¯s not an ¡°invented problem.¡± The idea of a descriptive or fun name is great and timely. I¡¯m glad that Georgy, the keeper of the flame, is the kind of playful nerd that respects this tradition, and also the tradition of involving the community.
?
Absolutely no one has mentioned ¡°litigation or legislation or decree¡± except for the one odd comment above. What they have talked about is further enhancing the project by giving it its own name. Think about all the new x6100 owners being told ¡°Oh, you need to try out the CanaryNest firmware.¡± Isn¡¯t that more tempting (and easier to remember¡± for someone already intimidated by all the Ham radio jargon than R1CBU/R2RFE?
?
I thought about it a bit, and I actually like the name CanaryNest. But I bet I would chuckle at all sorts of other fun ideas.
|
Re: R1CBU/R2RFE firmware's codename?
I'm fine with whatever, but if you've used my as of late, i had changed the boot logo to this:
?
?
If it is going to be renamed, why not something simple since it¡¯s open source. Like ¡°OpenX6100¡± or similar.
|
Re: R1CBU/R2RFE firmware's codename?
This strikes me as an entirely-invented ¡°problem¡± that really just stirs controversy more than solving anything. I¡¯m seeing hundreds of posts here with no problems talking about this until now.
?
Let¡¯s please just leave it this way: ¡°R1CBU/R2RFE firmware¡± or ¡°R2RFE/R1CBU firmware¡± or ¡°alternative firmware¡± or whatever else someone wants to call it. Nobody has had trouble knowing exactly what is being discussed so far, so let¡¯s just let people decide as they type ¡ª as we have been doing without incident or problem or trouble until this thread. No litigation or legislation or decree is required.
?
Thanks,
73, Randy K7RAN
|
Re: R1CBU/R2RFE firmware's codename?
I don't mind to use some codename. Function/variables naming is a hardest thing in a development)
Any suggestion for a new codename?
I'll start - this radio has so many birdies - it might be called CanaryNest
--
Georgy // R2RFE
|
Re: R1CBU/R2RFE firmware's codename?
On Tue, Apr 22, 2025 at 01:29 PM, Jarek SP9HGN wrote:
Hence my question - do the esteemed Authors plan to give their project some kind of "codename"?
I am currently fully occupied with my TRX "Brass" project, so this question is entirely for Georgy. I am very glad that he "picked up the baton" and is developing this project. Although I still hope that he will eventually join our "Brass" team (;
?
73!
|
Re: Modified BASE firmware - rev1
Yes, I remember this thread in which you were trying to analyse what's causing this FT8 app to run at low power on some units... That would be perfect if we could somehow find what is this potential HW difference causing this issue across our units.
Regarding AM and FM, power meter shows ~300mW at 10W (when unaffected BASE is producing full 10W).
|
Re: Modified BASE firmware - rev1
Thanks. Something like this was with FT8 app (my radio requires lower signal to achieve target tx power). And I don't know - where to look as the HW version within running firmware...
Could you also check AM and FM output power (without a signal)?
--
Georgy // R2RFE
|
R1CBU/R2RFE firmware's codename?
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
|
Re: Modified BASE firmware - rev1
This morning I spent a bit of time playing with the Georgy's latest modified version of the base firmware (r1) and observed issues with the power output readings. The power meter on the radio¡¯s display, when set to output the full 10W, shows a maximum of only 3¨C4W.
I didn¡¯t have time to check what the actual power output into a dummy load is.
The issue only affects the r1 firmware version, both for the original GUI and the R1CBU/R2RFE GUI.
It would be great if someone else could verify this as well.
Perhaps this is a hardware-level issue related to differences between revisions of our radios?
|
Dave
David Billstrom
Mr Wintle W1NTL
wicknix
Randy K7RAN