aprsdroid
aprsdroid copied to clipboard
ge0rg
iGate support (TCP connection and Bluetooth TNC simultaneously?)
In the next release will it be possible to have a TCP connection and a Bluetooth TNC connection simultaneously? Allowing APRSdroid to be an iGate? I have been using APRSdroid while mobile on a HTC sensation with a bluetooth rs232 dongle connected to a Paccom Tiny2 MK2 TNC and its working great. As the majority of Scotland does not have iGate coverage I would like to beacon via TCP as well as on bluetooth.
It is something I have on my roadmap. However, as it is not trivial to implement all the gating options and simultaneous backend support, I am planning iGate support for APRSdroid 2.0. You will need to have some patience before it is done :)
I am eager for the iGate function too: I often travel with my friends, all of us have OT2m, GPS, radio. We know each other's place well from our GPS connected to OT2m. But if APRSdroid can support igate, we would be very happy to share our position to APRS-IS, so all of our other friends can enjoy our journey at their home.
Hey GE0RG, wanted to take a second to 1+ this feature request. There are many if us anxiously awaiting this feature. Thanks for your hard work, and we look forward to this and all of the other cool features I'm sure you will have baked into v2.0.
it would be so nice to have I-Gate support! really looking forward to having v2.0 soon.
Is there an ETA on this? I'm thinking of getting a lifetime subscription to APRS Pro, but I would totally wait if this is actually going to happen...
Looking at how many Raspberry PI + RTL-SDR igates there are around these days, thanks to the pymultimonaprs project, I have to say that when this iGate and/or digipeater feature gets implemented it will be a major breakthrough in APRS in general. This would be completely new chapter in the history of APRS as iGates will be in everybodys pocket...
Is this happening? This would be a killer feature. It would need to take audio from the radio.
Developer's welcome to help! We can always more contributors. :-)
Right now, I believe the main issue is that support to instantiate multiple backends and also allow them to be configured in preferences simultaneously. Beyond that, we then need to be able to route packets between them and have some kind of routing policy. Which packets received over the local radio get forwarded to RF? If it has RFONLY in it's Digipath, it shouldn't be forwarded. And, even more difficult is if it implements bidirectional iGating and might forward packets to RF seen on APRS-IS. That feature, if implemented, will be more involved and probably even farther down the road. And then, there's locally generated packets. Do those always get sent over both backends and how would the packets differ? I believe a different digipath is needed at a minimum. Also, I believe any packets forwarded in either direction will need some modification to their digipath to either insert a hop or flag a seen bit. I believe ge0rg has had a little more time to think about all the other issues I am missing here.
