I'm setting up a TNC-X with my IC-2730 for APRS operation and running into path configuration problems. Currently using WIDE1-1,WIDE2-1 as recommended but my packets seem to be getting dropped after first hop. Serial interface is at 9600 baud, 8N1 - confirmed working with terminal. Beacon text shows correct lat/long in degrees/minutes/decimal format. Has anyone experienced similar issues with path routing on newer TNCs? The digipeater about 15 miles out acknowledges receipt but packets don't propagate beyond that point.

Smart digipeaters filter duplicates based on WIDEn-N paths but may not handle older RELAY paths properly. Check if your local digi supports the newer algorithms - some older KPC-3+ units need firmware updates to handle current path standards correctly.

The first WIDEn-N digi should insert its callsign before forwarding to show packet origin. If you're not seeing that callsign substitution in your raw packets, the digipeater may not be APRS-aware. Try WIDE2-1 instead - you rarely need more than single hop and it reduces network congestion.

Had this exact issue with my TNC-X last month. Verify your terminal program settings match the TNC - most use 9600 baud, no stop bit, 8 data bits, 1 parity. Also check UNPROTO setting should be APN382 for TNC-X units. My problem was incorrect SSID format in the path string.