I suspected this would be a problem and held off purchasing the radio. I know it’s just a matter of updating the keps but I’m glad I didn’t buy it before seeing your video. Liked and subscribed!
I have also been using this feature. I am a beta tester for Anytone. I have reported it back to the test team that the predictions are slightly out .My iss predictions are either missing or about 17 minutes out of sync. I have my UTC set correct. We are waiting for proper instructions and information where the kep files are coming from .regards Chris. 2E0UKH
@digitalanaloguehamradio Roger that. I really dug into the x86 program files and found the abc. Text file that has the keps. I even copied and pasted the keps from nasa. Bare. Still didn't work...
@@w8cptCptDon I did some digging into it myself, the CPS pulls the keps from Celestrak directly every time you upload them to the radio. I checked what's actually being sent to the radio and it turns out the ISS keps are completely wrong. But they *are* a match for SWISSCUBE. My guess is that the CPS just searches for "ISS" which obviously also matches to SWISSCUBE
I improved it somewhat by using the GPS check in the time and date setting. But it’s still not good on ISS although other satellites are good like so50
@@digitalanaloguehamradio right i have a live video where I worked S0-50 after doing the same. It worked great! So I really hope they fix this keps update issue!
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
I suspected this would be a problem and held off purchasing the radio. I know it’s just a matter of updating the keps but I’m glad I didn’t buy it before seeing your video. Liked and subscribed!
I have also been using this feature. I am a beta tester for Anytone. I have reported it back to the test team that the predictions are slightly out .My iss predictions are either missing or about 17 minutes out of sync. I have my UTC set correct. We are waiting for proper instructions and information where the kep files are coming from .regards Chris. 2E0UKH
@digitalanaloguehamradio i like to get the keps from www.amsat.org/amsat/ftp/keps/current/nasabare.txt
@digitalanaloguehamradio Roger that. I really dug into the x86 program files and found the abc. Text file that has the keps. I even copied and pasted the keps from nasa. Bare. Still didn't work...
@@w8cptCptDon I did some digging into it myself, the CPS pulls the keps from Celestrak directly every time you upload them to the radio. I checked what's actually being sent to the radio and it turns out the ISS keps are completely wrong. But they *are* a match for SWISSCUBE. My guess is that the CPS just searches for "ISS" which obviously also matches to SWISSCUBE
I improved it somewhat by using the GPS check in the time and date setting. But it’s still not good on ISS although other satellites are good like so50
@@digitalanaloguehamradio right i have a live video where I worked S0-50 after doing the same. It worked great! So I really hope they fix this keps update issue!
In the CPS 3.04 software, under Tool, there is an option called Satellite Data Writing. I clicked that and my radio seems to be correct.
@@8fstnf i clicked that too and its still wrong
Thanks for the video. I just did my first comparison with ISS Detector and mine are way off as well. At least it wasn't a for-fee update.
Notice also the spelling of “predicting.” I know that this is a Chinese product, but that error looks more like a typo that was never caught.
Firmware 3.04d is out; supposed to fix the sat prediction.
@@johnclark2849 I'm testing it as we type this lol
Keps are not static. They need to be regularly updated for accuracy.
@ag1382 yes i know this. The firmware has issues the next firmware update will fix it