I seen it on one of the video. I created an issue about it -?
Thank you so much Georgy
I can confirm that the Wi-Fi worked first time and updated the internal clock perfectly. ? Can I just make one observation?
When you go to ¡®Settings¡¯ and try and set the ¡®Day¡¯ with the ¡®Wrong¡¯ knob (ie the volume / RF knob) you get some strange coding digits in the display where the date should be !! ? I know that I am the idiot, but I thought I would own up to this as I do it soooo many times !! ? 73 ? Brian ¨C GW4DVB ? ? ? ? Hi.
Actual release available on the on GitHub. Significant changes - WiFi, FTx incremental decoding and support of CQ modifiers (SOTA, POTA, etc).
This version based on updated linux image and using external FTx library - so it (possible) might have some bugs.
Remember to copy files from DATA partition before flashing to save all parameters, logs, messages, etc. After flashing and first boot - copy these files back to DATA.
73. Georgy // R2RFE
|
Thank you so much Georgy
I can confirm that the Wi-Fi worked first time and updated the internal clock perfectly. ? Can I just make one observation?
When you go to ¡®Settings¡¯ and try and set the ¡®Day¡¯ with the ¡®Wrong¡¯ knob (ie the volume / RF knob) you get some strange coding digits in the display where the date should be !! ? I know that I am the idiot, but I thought I would own up to this as I do it soooo many times !! ? 73 ? Brian ¨C GW4DVB ? ? ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of ??????? ???????
Sent: 22 October 2024 15:34
To: [email protected]
Subject: [xiegu-x6100] R1CBU firmware 0.26.0 #development #firmware #r1cbu #R1CBU-Firmware? Hi.
Actual release available on the on GitHub. Significant changes - WiFi, FTx incremental decoding and support of CQ modifiers (SOTA, POTA, etc).
This version based on updated linux image and using external FTx library - so it (possible) might have some bugs.
Remember to copy files from DATA partition before flashing to save all parameters, logs, messages, etc. After flashing and first boot - copy these files back to DATA.
73. Georgy // R2RFE
|
Hi.
Actual release available on the on GitHub. Significant changes - WiFi, FTx incremental decoding and support of CQ modifiers (SOTA, POTA, etc).
This version based on updated linux image and using external FTx library - so it (possible) might have some bugs.
Remember to copy files from DATA partition before flashing to save all parameters, logs, messages, etc. After flashing and first boot - copy these files back to DATA.
73. Georgy // R2RFE
|
Re: R1CBU FT8 Time Sync..
Latest version seems to get the GPS working however the time still does not sync with the FT8 signal for me. ? I have to switch off and back on again to get it to work fairly often. ?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]> On Behalf Of ??????? ???????
Sent: 21 October 2024 19:58
To: [email protected]
Subject: Re: [xiegu-x6100] R1CBU FT8 Time Sync..? Thanks for sharing this information. I? didn't check the time synchronization with GPS, but checked that the application (last version) supports the hot plug of the GPS dongle. Georgy. ? I did a tutorial a while back for Oleg's 0.19 firmware to get the GPS to sync the internal time to the GPS. it is in Message: Basically, the linux operating system compares the current system time with the received GPS time. If the times are too different, linux will not update the system time when a new GPS time is received. I presume this is so linux will not change the time at all to the GPS time if it seems the GPS time is too far out of sync. There is a minor change that can be made to the NTP time syncing software parameters that will force the system time to be synced with the GPS time, no matter how far off the GPS time is. Here is a copy of the tutorial I posted for Oleg's 0.19 version. Hopefully, it will also work for George's firmware: I had the GPS working with the X6100 with Version 0.18, months back. I just installed Version 0.19, and it works with both of my GPS Dongles. Here are some hints and requirements on getting the GPS to sync the time in Oleg's software: 1) First, the GPS must be plugged into the X6100 before powering it up. I believe Oleg indicated this is so the software can detect that there is a GPS installed during power up, so it can configure the Linux system to handle GPS signals. So, first install the GPS Dongle in the Host USB port with power off. 2) Next, check that the X6100 is properly receiving the GPS signals from the GPS Dongle. Turn on power, and wait for the display to show the spectrum, indicating the X6100 is powered up and operating normally. Press the APP button. Select the? GPS button. On the screen, you will see several fields for the GPS. There are two important ones, "Fix" and "Date, time." If there is no data in the Date/Time field, the GPS is not receiving even one satellite, or the GPS hasn't warmed up yet, or the software is not receiving the time/location message from the GPS. If the Date/Time field has today's UTC (Zulu) date and the UTC time looks about correct, the GPS and the software are probably working correctly. 3) Next, the Fix field can have one of three values, "None," "2D" and "3D." With a good UTC time, None probably indicates that the GPS has not received enough satellites yet to do even an approximate location. When the Fix field indicates None, the software time will not update the System Time to the GPS UTC time. The Fix field must show 2D or 3D to allow the GPS time to update the system time. There are several reasons the Fix field may indicate None. The most common are that either the GPS is still initializing, or that it can't see enough satellites. So, first move the GPS/X6100 to a place where it has a good view of the sky. Then, wait for the GPS to indicate a GPS Fix of 2D or 3D. It may take a while for the GPS to initialize, so give it several minutes, and depending on the GPS, it may take the same time to initialize every time you turn on power, though it is usually a lot faster after the first time. 4) Once the GPS app indicates a good UTC time and a Fix of 2D or 3D, the software sends the UTC time from the GPS to the Linux system. The Linux system will compare the GPS time against its own internal system time. If the times are "close," within several hundred seconds or so, it will initialize the system time to the GPS time, then start tracking the GPS time, so the system time is always "synced" with the GPS time. So generally, you should see the system time in the upper right of the screen sync a few seconds after the Fix shows 2D/3D. And, the GPS time should track within one displayed second of system time until you turn off the system. 5) Finally, Linux has one "gotcha" for the time syncing. Linux is set up so that a bad GPS time doesn't set the system time to the wrong value, if the system and GPS times are way off. So finally, if the system time doesn't sync with the GPS time, check that the system time is close to the GPS time. First, still on the GPS App screen, write down the UTC Date and Time. Then, press the APP button, then the APP 1:2 button to get to the APP 2:2 screen. Then press the Settings button. Change the Day, Month, Year and Hour, Min fields to the GPS UTC values you wrote down (you don't have to update the Sec field, as the times will be close enough). Linux will then try to sync the system time to the GPS time, usually within a few seconds. If they don't sync, try turning off the power and then turn it on again. Wait for the GPS to get a 2D or 3D fix If the times don't sync, manually update the System time to agree with the GPS time If this doesn't work, you will probably need to ask for help from Oleg. One final thing: A while back, when Oleg first installed the GPS function, I couldn't get my GPS to sync the system time. Oleg and I had a discussion about this on this Forum. That's when I/we found out about the times not syncing if the times are too far apart (see above). I dug into Linux and found a parameter I could change in a Linux configuration file that would allow Linux to force an initial sync of the times once the Fix is 2D/3D, no matter how far apart the times are. I just tried patching the configuration file and the patch still seems to be working. However, I don't know enough Linux to know if there are any side effects to this change. I hope some of the above (long) descriptions/instructions are helpful to someone else. ? I¡¯m having trouble syncing my X6100 when trying the FT8 / FT4 mode. Ive tried a couple of GPS modules but they won¡¯t lock either.. Also can someone please provide a link to the latest firmware release ?
|
Re: R1CBU FT8 Time Sync..
Thanks for sharing this information. I? didn't check the time synchronization with GPS, but checked that the application (last version) supports the hot plug of the GPS dongle.
Georgy.
Brian,
I did a tutorial a while back for Oleg's 0.19 firmware to get the GPS to sync the internal time to the GPS. it is in Message:
Basically, the linux operating system compares the current system time with the received GPS time. If the times are too different, linux will not update the system time when a new GPS time is received. I presume this is so linux will not change the time at all to the GPS time if it seems the GPS time is too far out of sync.
There is a minor change that can be made to the NTP time syncing software parameters that will force the system time to be synced with the GPS time, no matter how far off the GPS time is.
Here is a copy of the tutorial I posted for Oleg's 0.19 version. Hopefully, it will also work for George's firmware:
I had the GPS working with the X6100 with Version 0.18, months
back. I just installed Version 0.19, and it works with both of my GPS
Dongles. Here are some hints and requirements on getting the GPS to sync
the time in Oleg's software:
1) First, the GPS
must be plugged into the X6100 before powering it up. I believe Oleg
indicated this is so the software can detect that there is a GPS
installed during power up, so it can configure the Linux system to
handle GPS signals. So, first install the GPS Dongle in the Host USB
port with power off.
2) Next, check that the
X6100 is properly receiving the GPS signals from the GPS Dongle. Turn on
power, and wait for the display to show the spectrum, indicating the
X6100 is powered up and operating normally. Press the APP button. Select
the? GPS button. On the screen, you will see several fields for the
GPS. There are two important ones, "Fix" and "Date, time." If there is
no data in the Date/Time field, the GPS is not receiving even one
satellite, or the GPS hasn't warmed up yet, or the software is not
receiving the time/location message from the GPS. If the Date/Time field
has today's UTC (Zulu) date and the UTC time looks about correct, the
GPS and the software are probably working correctly.
3)
Next, the Fix field can have one of three values, "None," "2D" and
"3D." With a good UTC time, None probably indicates that the GPS has not
received enough satellites yet to do even an approximate location. When
the Fix field indicates None, the software time will not update the
System Time to the GPS UTC time. The Fix field must show 2D or 3D to
allow the GPS time to update the system time. There are several reasons
the Fix field may indicate None. The most common are that either the GPS
is still initializing, or that it can't see enough satellites. So,
first move the GPS/X6100 to a place where it has a good view of the sky.
Then, wait for the GPS to indicate a GPS Fix of 2D or 3D. It may take a
while for the GPS to initialize, so give it several minutes, and
depending on the GPS, it may take the same time to initialize every time
you turn on power, though it is usually a lot faster after the first
time.
4) Once the GPS app indicates a good UTC
time and a Fix of 2D or 3D, the software sends the UTC time from the GPS
to the Linux system. The Linux system will compare the GPS time against
its own internal system time. If the times are "close," within several
hundred seconds or so, it will initialize the system time to the GPS
time, then start tracking the GPS time, so the system time is always
"synced" with the GPS time. So generally, you should see the system time
in the upper right of the screen sync a few seconds after the Fix shows
2D/3D. And, the GPS time should track within one displayed second of
system time until you turn off the system.
5)
Finally, Linux has one "gotcha" for the time syncing. Linux is set up so
that a bad GPS time doesn't set the system time to the wrong value, if
the system and GPS times are way off. So finally, if the system time
doesn't sync with the GPS time, check that the system time is close to
the GPS time. First, still on the GPS App screen, write down the UTC
Date and Time. Then, press the APP button, then the APP 1:2 button to
get to the APP 2:2 screen. Then press the Settings button. Change the
Day, Month, Year and Hour, Min fields to the GPS UTC values you wrote
down (you don't have to update the Sec field, as the times will be close
enough). Linux will then try to sync the system time to the GPS time,
usually within a few seconds. If they don't sync, try turning off the
power and then turn it on again.
So, to summarize:
Turn off power
Plug in the GPS Dongle
Turn on power
Go to the GPS App
Wait for the GPS to get a 2D or 3D fix
If the times don't sync, manually update the System time to agree with the GPS time
If this doesn't work, you will probably need to ask for help from Oleg.
One
final thing: A while back, when Oleg first installed the GPS function, I
couldn't get my GPS to sync the system time. Oleg and I had a
discussion about this on this Forum. That's when I/we found out about
the times not syncing if the times are too far apart (see above). I dug
into Linux and found a parameter I could change in a Linux configuration
file that would allow Linux to force an initial sync of the times once
the Fix is 2D/3D, no matter how far apart the times are. I just tried
patching the configuration file and the patch still seems to be working.
However, I don't know enough Linux to know if there are any side
effects to this change.
I hope some of the above (long) descriptions/instructions are helpful to someone else.
Jerry K6ANI
I¡¯m having trouble syncing my X6100 when trying the FT8 / FT4 mode.
?
Ive tried a couple of GPS modules but they won¡¯t lock either..
?
Any ideas ?
?
Also can someone please provide a link to the latest firmware release ?
|
Re: R1CBU FT8 Time Sync..
Brian,
I did a tutorial a while back for Oleg's 0.19 firmware to get the GPS to sync the internal time to the GPS. it is in Message:
Basically, the linux operating system compares the current system time with the received GPS time. If the times are too different, linux will not update the system time when a new GPS time is received. I presume this is so linux will not change the time at all to the GPS time if it seems the GPS time is too far out of sync.
There is a minor change that can be made to the NTP time syncing software parameters that will force the system time to be synced with the GPS time, no matter how far off the GPS time is.
Here is a copy of the tutorial I posted for Oleg's 0.19 version. Hopefully, it will also work for George's firmware:
I had the GPS working with the X6100 with Version 0.18, months
back. I just installed Version 0.19, and it works with both of my GPS
Dongles. Here are some hints and requirements on getting the GPS to sync
the time in Oleg's software:
1) First, the GPS
must be plugged into the X6100 before powering it up. I believe Oleg
indicated this is so the software can detect that there is a GPS
installed during power up, so it can configure the Linux system to
handle GPS signals. So, first install the GPS Dongle in the Host USB
port with power off.
2) Next, check that the
X6100 is properly receiving the GPS signals from the GPS Dongle. Turn on
power, and wait for the display to show the spectrum, indicating the
X6100 is powered up and operating normally. Press the APP button. Select
the? GPS button. On the screen, you will see several fields for the
GPS. There are two important ones, "Fix" and "Date, time." If there is
no data in the Date/Time field, the GPS is not receiving even one
satellite, or the GPS hasn't warmed up yet, or the software is not
receiving the time/location message from the GPS. If the Date/Time field
has today's UTC (Zulu) date and the UTC time looks about correct, the
GPS and the software are probably working correctly.
3)
Next, the Fix field can have one of three values, "None," "2D" and
"3D." With a good UTC time, None probably indicates that the GPS has not
received enough satellites yet to do even an approximate location. When
the Fix field indicates None, the software time will not update the
System Time to the GPS UTC time. The Fix field must show 2D or 3D to
allow the GPS time to update the system time. There are several reasons
the Fix field may indicate None. The most common are that either the GPS
is still initializing, or that it can't see enough satellites. So,
first move the GPS/X6100 to a place where it has a good view of the sky.
Then, wait for the GPS to indicate a GPS Fix of 2D or 3D. It may take a
while for the GPS to initialize, so give it several minutes, and
depending on the GPS, it may take the same time to initialize every time
you turn on power, though it is usually a lot faster after the first
time.
4) Once the GPS app indicates a good UTC
time and a Fix of 2D or 3D, the software sends the UTC time from the GPS
to the Linux system. The Linux system will compare the GPS time against
its own internal system time. If the times are "close," within several
hundred seconds or so, it will initialize the system time to the GPS
time, then start tracking the GPS time, so the system time is always
"synced" with the GPS time. So generally, you should see the system time
in the upper right of the screen sync a few seconds after the Fix shows
2D/3D. And, the GPS time should track within one displayed second of
system time until you turn off the system.
5)
Finally, Linux has one "gotcha" for the time syncing. Linux is set up so
that a bad GPS time doesn't set the system time to the wrong value, if
the system and GPS times are way off. So finally, if the system time
doesn't sync with the GPS time, check that the system time is close to
the GPS time. First, still on the GPS App screen, write down the UTC
Date and Time. Then, press the APP button, then the APP 1:2 button to
get to the APP 2:2 screen. Then press the Settings button. Change the
Day, Month, Year and Hour, Min fields to the GPS UTC values you wrote
down (you don't have to update the Sec field, as the times will be close
enough). Linux will then try to sync the system time to the GPS time,
usually within a few seconds. If they don't sync, try turning off the
power and then turn it on again.
So, to summarize:
Turn off power
Plug in the GPS Dongle
Turn on power
Go to the GPS App
Wait for the GPS to get a 2D or 3D fix
If the times don't sync, manually update the System time to agree with the GPS time
If this doesn't work, you will probably need to ask for help from Oleg.
One
final thing: A while back, when Oleg first installed the GPS function, I
couldn't get my GPS to sync the system time. Oleg and I had a
discussion about this on this Forum. That's when I/we found out about
the times not syncing if the times are too far apart (see above). I dug
into Linux and found a parameter I could change in a Linux configuration
file that would allow Linux to force an initial sync of the times once
the Fix is 2D/3D, no matter how far apart the times are. I just tried
patching the configuration file and the patch still seems to be working.
However, I don't know enough Linux to know if there are any side
effects to this change.
I hope some of the above (long) descriptions/instructions are helpful to someone else.
Jerry K6ANI
I¡¯m having trouble syncing my X6100 when trying the FT8 / FT4 mode.
?
Ive tried a couple of GPS modules but they won¡¯t lock either..
?
Any ideas ?
?
Also can someone please provide a link to the latest firmware release ?
|
Re: R1CBU FT8 Time Sync..
Now it's almost impossible to setup correct time for FT8, if you don't have a usb Ethernet adaptor or GPS dongle. This button was created to adjust local time to nearest 15s/7.5s time slot start. This button will be removed in the next release.
I make sure I plug in my GPS into the host port before booting.? A good GPS unit will lock and then all is well.? I still don't understand if the "Time Sync" button is working at this time and what it is for.
?
|
Re: R1CBU FT8 Time Sync..
I make sure I plug in my GPS into the host port before booting.? A good GPS unit will lock and then all is well.? I still don't understand if the "Time Sync" button is working at this time and what it is for.
?
|
I have an issue () about this and almost fixed it. Will be published in the next release.
?
73! Georgy // R2RFE
|
Re: R1CBU FT8 Time Sync..
All releases available on the github -
?
I'm working on the next release with WiFi support - you will be able to sync time using NTP after connecting to WiFi (your home network, or using phone Access Point).
?
73! Georgy // R2RFE
|
I¡¯m having trouble syncing my X6100 when trying the FT8 / FT4 mode.
?
Ive tried a couple of GPS modules but they won¡¯t lock either..
?
Any ideas ?
?
Also can someone please provide a link to the latest firmware release ?
|
Hello Franco,
?
Thanks for confirming what I was seeing and confirmed by several on a FB group.? It's not a showstopper and if it could be implemented, I think it would make this a perfect app within R1CBU based firmware.? I'm not a programmer, but I know enough to be dangerous, and I thought some sort of filter could be implemented but as you say, there are different variations that need to be accounted for.??
|
I just took a quick look at Georgy's code, and I see that he already has a 'TODO' item about POTA:
?
Since on FT8 people call 'CQ POTA' , 'CQ SOTA', 'CQ IOTA', and I have even seen 'CQ VOTA', I thought of a couple of better approaches than just checking if the second word in the CQ message is two characters long:
?
A: check if the CQ message is comprised of four words instead of three - in that case the second word is an extra field, like 'DX' or 'POTA', or similar qualifier.
B. check if the second word contains a digit or not; if it contains a digit it is very likely a call sign, otherwise it is some extra field
?
The latter approach could be easily implemented by changing the next line (line 1404) with a call to a new function 'hasdigit':
if (!hasdigit(call_de)) {
where the function 'hasdigit()' would be:
static bool hasdigit(const char * str) {
const char *p = str;
while (*p++) {
if (isdigit(*p))
return true;
}
return false;
}
?
I haven't tried to build the code with these changes, but I thought I would throw a couple of ideas.
?
Franco
?
|
Has anyone had any luck using the internal FT8 Applicaiton in R1CBU based firmware with POTA stations?? From the picture attached, it seems like the software is calling "POTA" instead of the station when the station has added POTA preceding the call sign as you can see at the top of the screen.? You can see at the bottom of the screen what it appears to be calling.? Any thoughts or feedback?? Overall I love the R1CBU based version.? It's worked very well otherwise.? I can sit in my car with a mag-mount and make contacts either via SSB or FT8.
?
|
Re: No/low receive on X6100
Did you figure this out? Mine all of a sudden stopped receiving?
|
Anybody uses Pactor with SCS Modem and the Xiegu X6100? Helmar 73 from dl1kvc
|
Re: R1CBU - Cancelling an app once started?
I'm away from the radio right now (of course!) but I think the
window was displaying and the menu bar reflected the button that
had been pressed.
The mystery to me was that that window survived a reboot, too!
I'll have to see if I can reproduce it. (I've been afraid that I
could, so I haven't tried!)
--
Paul -- AI7JR
|
Re: R1CBU - Cancelling an app once started?
Hmm. I checked on my radio - any left button (except DFL) closes RTTY window.
Also - there is no persistent option to load some application on the start.
Does GEN and other left buttons works as expected?
73. Georgy // R2RFE
|
R1CBU - Cancelling an app once started?
I've been exploring R1CBU V 25 on my x6100. Nice! But I've run into a problem--
?
I press the APP button and choose RTTY. Bar at the bottom changes to RTTY options, but none are exit! So, even if I press the GEN button the RTTY window continues to be displayed.
?
I think the same thing happens with FT8, don't recall for sure.
?
Shutdown and reboot, continues to show the RTTY window. :-(
?
What am I doing wrong?
?
73, Paul -- AI7JR
|
Re: Hearing aids and radio
Thanks for the replies. I can always use my older hearing aids and the adapter I have for them while playing radio. I will contact the folks at the VA and see if they have a discount on the TV adapter, or I can always go fishing on ebay for a used one.
73, Gale Smith KD9OCL
|
GW4DVB
Bill KM6TAU
Paul - AI7JR