-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DGIdGateway] Show received DG-ID in Display of TRX #255
Comments
Do you know what Yaesu systems show when using DG-Id routing? I’d like to follow their lead rather than do something odd.
Sent from Yahoo Mail for iPhone
On Wednesday, March 10, 2021, 12:49, Kim - DG9VH <[email protected]> wrote:
Hi Jonathan,
for users of DGIdGateway it will be helpful to see the received DG-ID in the Display of the TRX. Maybe it is possible for you to add it simply to the transported Callsign-string like [42]DG9VH where 42 is the DG-ID the receiving audio stream is issued from or something like that?
Actually there is no possibility to identify where the received traffic is coming from so you have to take a look at the logfile to see it (or at a somehow existing dashboard).
I think it should be easy to add but I did not found the corresponding passage due my minor c++-capabilities :-(
73 de Kim
DG9VH
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi,
no, sorry, I have no Yaesu-System here to check this... maybe some others
could help with this info. We could ask in the mailing-list.
73 de Kim
|
Back again: Situation: our "friends" in YCS use following format for example: 62/DG9VH (but also not working rock-solid as reported) but they also implemented a hang-time that has higher control over the DG-ID as the transmitter... not suitable for DGIdGateway, because we love the possibility to switch "ad-hoc" to another group and reflector if wanted... Situation: Direct to Direct-QSO with two transceivers: So we are lost in concepting it by ourself... having it DG9VH@42 would make also sense in linguistic way, you can read it "DG9VH at 42" and know: hey, DG9VH is speaking at DG-ID 42... :-) On the net there is nothing documented by yaesu about display-screens in receiving situations... I found a youtube websession-video of over an hour talking about Wires-X and Fusion II, but also no info about "how do we signalize it on the displays"... Now I don't know what to do clever way... but I think displaying it like "DG9VH@42" would be intuitive for users to understand and if someone could bring some info that yaesu will do it in another way, it could be modified in that way... just a change request away, hi. Think about it :-) |
Hello Jonathan, Kim |
Hi Jonathan,
for users of DGIdGateway it will be helpful to see the received DG-ID in the Display of the TRX. Maybe it is possible for you to add it simply to the transported Callsign-string like [42]DG9VH where 42 is the DG-ID the receiving audio stream is issued from or something like that?
Actually there is no possibility to identify where the received traffic is coming from so you have to take a look at the logfile to see it (or at a somehow existing dashboard).
I think it should be easy to add but I did not found the corresponding passage due my minor c++-capabilities :-(
73 de Kim
DG9VH
The text was updated successfully, but these errors were encountered: