On Thu, 4 Jun 2009, Phil - w2lie wrote:
I would need to keep my RF -> INET Functions as well as my National WX Service beacons sent over I-NET to the RF world. I assume that is an easy config..
Depends. Xastir has the concept of INET ports and RF ports. It doesn't gate RF->RF or INET->INET, but can do RF<->INET for some things. Occasionally the classification of a port might surprise you so that gating might not be as expected.
Would I need the CRON to run it ever X minutes to beacon, or once you run the xastir_udp_client does that set it to beacon using the setup defined in Xastir?
Depends on whether Xastir is "adopting" the objects as it's own. If you send it from the callsign-SSID that Xastir is running as, then you send it once and Xastir takes over. If you're not, then you need to do the timing and keep sending it. In any case, make sure you test everything out and get it working as expected. Don't assume it's working correctly without and end-to-end test.
If that is the case, how would you tell Xastir to delete the object when it is no longer needed???
Probably by manually killing the object in Xastir, at least if Xastir has adopted the object. If it hasn't, issue "killed" objects for 5 or 10 transmit periods, then cease transmitting the object. -- Curt, WE7U. archer at eskimo dot com http://www.eskimo.com/~archer Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system!" _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
