Akurate Kontrol pre-amplifier - RS232 ASCII Interface Specification and Commands - Version 1.2
1.3: Identifier Considerations
The full transmission format uses four fields as shown.
#Source_ID# &Group_ID& @Destination_ID@ $Message$
Where fields are omitted the results are defined in the following notes.
........... .......... ................ $Message$ refer to note 1
........... .......... @Destination_ID@ $Message$ refer to note 2
........... &Group_ID& ................ $Message$ refer to note 3
........... &Group_ID& @Destination_ID@ $Message$ refer to note 4
#Source_ID# .......... ................ $Message$ refer to note 5
#Source_ID# .......... @Destination_ID@ $Message$ refer to note 6
#Source_ID# &Group_ID& ................ $Message$ refer to note 7
#Source_ID# &Group_ID& @Destination_ID@ $Message$ refer to note 8
- A product recognising the command will issue an initial response and try to perform the
task.
- A successful or unsuccessful final response will be issued subsequently.
- Products not recognising the command will remain silent.
- If no product recognises the command then there will be no reply.
- If more than one product recognises the command then there may be a comms clash on
the replies.
- The destination product is responsible for all replies.
- Invalid commands will generate an error response.
- The replying product will transfer the destination to the source field on a reply.
- All products not matching the destination must remain silent and not attempt to handle the
command.
- If two products have the same id, then a comms clash may occur.
- All products within the group should attempt the task.
- Products out with the group should ignore the task.
- There are no replies from any boxes.
- All products within the group should attempt the task.
- Products out with the group should ignore the task.
- Only the product, which matches the destination identity, should reply.
- Invalid commands will generate an error response.
- If there are more than two products in the group with the same destination identity then a
comms clash may occur.
- The destination identity becomes the source identity in any reply traffic.
- As for note 1, with the source identity becoming the destination identity in any replies.
- As for note 2, with the source identity becoming the destination identity in any replies.
- As for note 3. There are no replies.
- As for note 4, with the source identity becoming the destination identity in any replies.