Board:   [fsxNet] Test messages
Subject: Re: Testing
From:    J0hnny A1pha(21:4/158.1)
Date:    Thu Sep 10, 2026 12:21

--- Accession Said ---
Ac> JA> @AREA:FSX_TST
Ac>
Ac> Should this kludge have a space in it? Seems to have changed in the
Ac> clrghouz automated reply, like it was parsed wrong, is why I ask.
Ac>
--- Accession Done ---

Good catch, and thanks for the hex dump Deon, that made it easier to spot.

1. Confirmed, no space needed after colon per FTS-004
3. Double area problem will be fixed (ViSiON/3 was writing it twice, as bare
area (top) then as kludge down with PID/TID).

I'm in there now and i also made the inbound parser tolerant of the variant
you are seeing in the wild (space + leading SOH). That would have triggered a
BAD message flag on my end!

Making these corrections now and will put this out in a hotfix today and
re-test...

..jA
--- ViSiON/3 v0.9.0/Linux
 * Origin: Broken Bit Syndicate - ViSiON/3 HQ (21:4/158.1)
.