Thanks, fixed it - it wasn't properly limiting the string length and the
path was being overwritten.
The AX.25 protocol only has space for 6 characters and a 4-bit SSID, so
there's no way to make your long VE2/ call work. Best to just put that
in the comment.
> Being in software development myself, I try to avoid using the 'b'
> word as it makes people cranky, so I wanted to mention a small feature
> I discovered this weekend.
> Driving into Canada from New York, I thought I would be clever (always
> a mistake) and decided to send
> --CALL VE2/KC2JCJ
> to my Tracker2 from the Nuvi 350. I wasn't sure if it would work, but
> I thought I'd do it anyway as it might catch the attention of some
> APRS-loving Canadians and get them to send me a message.
> It didn't work, unfortunately, (CALL ended up being some horrible
> frankenstein of a string) and I had to re-enter my proper call with SSID.
> Anyway, I noticed that for the remainder of the trip, and for the
> whole ride back into the States, all the local digis were deaf to me.
> I thought perhaps it was just some bad weather, but come last night I
> figured something must have gone south.
> It looks like trying to set my CALL to the value above hosed up the
> PATH variable setting on the Tracker2. If I recall correctly, it got
> set to something like:
> Correcting the PATH fixed everything.
> While this is probably an edge case, I figured firing off an email to
> you might save someone a headache down the road.
> Cheers and 73