germaholdings.blogg.se - Anytone at d868uv error message

#ANYTONE AT D868UV ERROR MESSAGE HOW TO#
#ANYTONE AT D868UV ERROR MESSAGE UPDATE#
#ANYTONE AT D868UV ERROR MESSAGE UPGRADE#

I did not change the board between yesterday and today. Mode enabled and network status both show "DMR" with the green background. Under where it says "DMR Repeater" it is showing "not linked"/"not linked." This article is multi-page, to be browsed from one page to another or directly from the contents to the desired page. It is not today, but I was getting the same error message yesterday also. It should also be noted that the BTECH DMR-6X2 model, which is the equivalent of the AnyTone AT-D868UV, can also be modified under the same conditions. Interestingly, yesterday the word "internet" with a green background was showing. All of the them return the same error message.Įvery once in a while the green light for DMR on the Zumspot lights up, and the dashboard shows gateway activity. I've programmed several talkgroups starting with a few of the "parrot" TG's and then a few others. Specifically my dashboard shows CC1 and TS2 enabled. The color codes and time slots of the programmed channels also agree with what is showing on the dashboard. I have double checked that the transmit and receive frequencies on my radio are the same as the frequency that I put on the pi-star dashboard. When I transmit for more than a few seconds an error message comes up on the screen of my radio that says "repeater not found."

#ANYTONE AT D868UV ERROR MESSAGE HOW TO#

So it was really just a labor of love for a few hams who had a blast working out how to do the upgrade.I don't know if this is a problem with the Zumspot or the pi-star configuration.

#ANYTONE AT D868UV ERROR MESSAGE UPGRADE#

The funny part about that is the upgrade involves buying a special programming board and considerable time and effort, plus the risk of ruining your radio. This was one of the topics that would get you banned on that Facebook group, as the group owner would rather sell you a new radio.

#ANYTONE AT D868UV ERROR MESSAGE UPDATE#

The most popular issue is a lengthy collaboration among several hams who worked out a way to update the firmware on the D868UV to convert it to a D878UV. People found it and it took on a life of its own. So I made a repo and started adding issues for the things I'd noticed. There was an active Facebook group, but it is a weird place run by a radio dealer who would ban you for discussing anything he thought might interfere with his business. I am embarrassed to admit that my most popular GitHub repo is an issues-only tracker for something I didn't even create: a popular handheld ham radio, the AnyTone AT-D868UV/AT-D878UV.Īfter I bought my radio, I found a few firmware issues and looked for a way to communicate them to the manufacturer.

Advancing developer freedom: GitHub is fully available in Iran.

(I think this one is newest and I probably never tried it) (I think this is one of the original ones) One did have a webview that ran from a repo, but it was up to you to figure out how to keep it in sync with the comments/etc devs were putting in their copies of the issue tracker. * Most of them didn't have a non-repo way to track issues, for project managers and such. * The rest effectively ran in parallel to the git repo, pushing and pulling their data within it but requiring their own commands to do so, so it was totally possible to clone the repo and not get the issues.

* At least one of them kept their info in the repo in a dot-prefixed directory and auto added/committed the file as changes were made this meant a single issue could be in different statuses depending on which branch you were on and there was no overarching view. * Some of them make a mess of some part of git one of them put its info in separate git branches to ensure changes were always pushed/pulled even without a special push/pull command for the issue tracker. Most of them died out though, there were typically a few problems - this is what I remember offhand from experimenting with a whole bunch of them: Experimenting with distributed issue trackers in git was popular in the early 2010s, there were a whole bunch of different implementations people came up with for git.