Downstreams allow us to communicate with peripherals from the controller. The example downstream is on the mercury EP1501 itself. It is important to note that only some controllers have a downstream device on-board and thus can be connected directly to a reader or several (depending on the controller).
Downstreams are fairly easy to add. Basically, all you need to do is assign a common name, Provide the active port’s driver number, and the panel address.
For more information on Downstreams and the methods used please look at Downstreaminfo.
Example in C#
var downstream = await client.AddDownstreamToController(controller,
new Ep1501OnBoardInfo
{
CommonName = "OnBoard Interface", //name for the downstream
DriverNumber = port.DriverNumber, //port from the driver number we got above
PanelAddress = 0
});
Example in CURL
curl -X POST \
https://keepapi.feenicshosting.com/api/f/INSTANCE.KEY/controllers/CONTROLLER.KEY/downstream \
-H 'Authorization: Bearer TOKEN_GOES_HERE' \
-H 'Content-Type: application/json' \
-d '{
"$type":"Feenics.Keep.WebApi.Model.Ep1501OnBoardInfo, Feenics.Keep.WebApi.Model",
"DriverNumber":0,
"PanelAddress":0,
"SioNumber":0,
"TargetBaudRate":0,
"Version":null,
"Status":null,
"Key":null,
"CommonName":"OnBoard Interface",
"InFolderHref":null,
"InFolderKey":null,"Links":[],
"ObjectLinks":null,
"Metadata":null,
"Notes":null,
"Tags":null,
"Monikers":null,
"Href":null
}'