开云体育

First - I have a new x6100 with latest firmware installed. I have NOT yet used the R1CBU firmware, I’m monitoring these threads to see what’s going on. DHCP does NOT work in stock firmware.

What do you mean you can see the x6100 but it doesn't have an IP Address?? Does that mean you can find the MAC address but the IP address is blank? Have you ever successfully connected the X6100 to

Make sure you choose a valid IP range. When i first got my x6100 it spit out a weird random IP that wasn’t even close to my other devices on my network. I ran arp -a in terminal on my desktop to

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

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

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

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

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

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

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

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

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 (

Ordered cables and found that they work! -- Mike NN3I

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

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

I'm fine with whatever, but if you've used my color modified firmware ( https://github.com/wicknix/x6100_gui/releases ) as of late, i had changed the boot logo to this: If it is going to be renamed,

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

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

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

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