¿ªÔÆÌåÓýThe APRS-IS will be fine (it's pretty bullet proof), but my experience is that there could be some subtle problems, specifically with messaging.? You can send a message, but who can see it and who receives the reply?? It might have been a quirk with how I set things up (this was with YAAC on a Raspberry Pi), but after noticing the issue I ran through the combinations of source and sink (RF, IS, various SSIDs, etc) until my head began to hurt.? Most worked, but some did not.? Since there is overlap, what roles should Direwolf play, and what for the attached client (YAAC in this case)?? I never got to the bottom of it.?The Pi is the one in my car, rarely used on APRS since my mobile rig has only one VFO and it's usually parked on the local repeater.? So, not a high priority to fix, but I'd love to know how one should implement something like this, particularly the question of roles.? I was trying to make a communicate-with-everything box, both iGate and as a Digi, moving map display of local stations, messaging, etc.? I presume it still works as it did, but it's been a couple of years. Greg? KO6TH Craig T. Bailey, N1SFT wrote:
|
