On 17/8/24 5:25 am, Peter Laws via groups.io wrote:
I'm helping with the local D-STAR Gateway and expect to install the
"g2_link" link once the dev folks get some ALMA 9 things straightened
out. That will give our users use of the full range of "reflectors"
including, presumably, yours?
I did some ground work to get g2_link installed on a repeater, but it's
still on the todo list their end.?? I have no idea what "ALMA 9" or "IOP
prefix" is, haven't seen either of those terms used in this context before.
I wonder if I could encourage devs of non-DPlus schemes to use the IOP
prefix on "reflectors" that bridge between modes? Just to call out
the fact that they are a bridge from whatever to whatever.
Read above - "IOP prefix?"
At least until every radio supports M17 natively.
I do have an older Pi-Star-based hotspot and the version of Pi-Star it
supports (vendor is gone so no new firmware support) *will* do M17 but
it doesn't transcode so I can't listen on my D-STAR radios. AFAIK.
At this stage, there's no end user solution for transcoding between
D-STAR and M17.? Other than needing an AMBE chip for handling the D-STAR
side audio, this should be a relatively straightforward gateway, because
the addressing schemes are so similar (callsign based).? In fact, I
suspect you could design such a gateway so that you use a D-STAR radio
just like you would a native M17 radio, except needing the RPT1 and RPT2
settings configured.? Just needs someone interested in developing such a
gateway.? Starting with a MMDVM based system (M17Gateway would likely
not need modification) and adding the gateway/transcoding components
could be one approach.? Plug in a ThumbDV or similar to get the D-STAR
audio working.
So in theory it could be done, just needs developers to make it happen.
--
73 de Tony VK3JED/VK3IRL
Peter Laws