3.2.4 Multi Card Support

If several cards are connected to the service, One of two scenarios will apply to each card specific command:

1. The target card is specified with the command: The command will run on this card only.
2. No target card is specified with the command: The command will apply to all cards (if possible)

api.Acquisition.Start();

Having multiple cards connected also means that each card must have its own configuration. The cards are distinguished by their ConnectionId which maps each connected card to a card configuration. To enable card switching the ConnectionId is the IP used to connect to the card or the SuggestedIp if the card is connected by serial number.

A card configuration can be changed in several ways.

• Do nothing: The service loads the PDA configuration file on startup.

• Configure the card in the PDA UI, then start the service. The service will load the PDA configuration file on startup. Currently the PDA UI supports only one device, so only one device can be configured in this manner.

• Instruct the service to use another existing configuration file by running the SetPdaConfig with a PathFieldNumber containing a path to the new configuration file. C# user can directly call SetPdaConfig with a path as argument.

• Load a configuration file from path with LoadPdaConfig or with the C# wrapper using the overloaded LoadPdaConfig , adapt its content and apply the PDA configuration with SetPdaConfig or the C# overloads of SetPdaConfig .

• Get the current service configurations with GetPdaConfig or on C# conveniently with GetPdaConfig , adapt them and update the service configuration as above.

The SavePdaConfig method can be used to save a configuration to a custom path. It can then be manually adapted or loaded into the service from path.