Bad PFID when connecting to SHARC over RS-232

We have noticed an unknown packet ID being sent from Audio Weaver Server upon connecting to a SHARC target over RS-232 on one specific PC. The first packet contains a PFID of 87 (0x57) which is not defined in the Server Command Syntax document. We do not see this packet when connecting to the target over SPI (Aardvark) from this PC, nor when connecting over RS-232 to the target using a different PC.

Is there a file where the connection script is stored in the Audio Weaver folder structure that we can edit? I checked the .ini file for AWE server, but I didn’t see anything resembling a list of connection commands.

Here's a summary of the commands sent from both PCs over RS-232:

(It looks as if the 87 packet is just a fluke sent at the beginning of the correct command list.)

PC 1 with unknown PFID at start

----------------

TX: len 3 PFID 57 = unknown

TX: 0001C200

TX: 0002C257 (crc)

RX: len 3 PFID 0

RX: FFFFFFD9 = correct bad packet response

RX: FFFCFFD9 (crc)

----------------

TX: len 2 PFID 1F = PFID_GetSizeofInt

TX: 0002001F (crc)

RX: len 3 PFID 0

RX: 00000001

RX: 00030001 (crc)

----------------

TX: len 2 PFID 1F

TX: 0002001F (crc)

RX: len 3 PFID 0

RX: 00000001

RX: 00030001 (crc)

...

...

PC 2 with no bad PFID:

----------------

TX: len 2 PFID 1F = PFID_GetSizeofInt

TX: 0002001F (crc)

RX: len 3 PFID 0

RX: 00000001      = size is 1

RX: 00030001 (crc)

----------------

TX: len 2 PFID 1F

TX: 0002001F (crc)

RX: len 3 PFID 0

RX: 00000001

RX: 00030001 (crc)

----------------

TX: len 2 PFID 1F

TX: 0002001F (crc)

RX: len 3 PFID 0

RX: 00000001

RX: 00030001 (crc)

...

...