![background image](http://html1.mh-extra.com/html/barco/s3-series/s3-series_user-manual_3891629516.webp)
B. Remote Control Protocol
•
method—a String with the name of the method to be invoked.
•
params—an Object or Array of values to be passed as parameters to the de
fi
ned method.
•
id—a value of any type used to match the response with the request to which it is replying.
The receiver of the request must reply with a valid response to all received requests. A response must contain the properties men-
tioned below.
•
result—the data returned by the invoked method.
If an error occurred while invoking the method, this value must be null.
•
error—a speci
fi
ed error code if there was an error invoking the method, otherwise null.
•
id—the id of the request to which it is responding.
For example:
{"params":{}, "method":"powerStatus", "id":"1234", "jsonrpc":"2.0"}
Image B-2
powerStatus API – example
Here,
powerStatus
is the JSON API to be sent.
JSON APIs
Here are some of the JSON APIs de
fi
ned for controlling the Event Master processor. If you have a master / slave Event Master
setup, JSON must be sent to the master unit. For all the requests, this section explains the parameter passed or used in the RPC
calls. If the params object is blank that means that API doesn’t require a parameter.
Requests are case sensitive.
allTrans
•
De
fi
nition
-
It executes the “allTrans” command.
•
Request:
-
params:
{}
- It doesn’t require any parameter.
•
Response:
-
response: null
-
success: (0=success, anything else is an error)
•
Example:
-
{"params":{}, "method":"allTrans", "id":"1234", "jsonrpc":"2.0"}
cut
•
De
fi
nition
-
It executes the “Cut” command.
•
Request:
-
params:
{}
- It doesn’t require any parameter.
•
Response:
-
response: null
-
success: (0=success, anything else is an error)
•
Example:
-
{"params":{}, "method":"cut", "id":"1234", "jsonrpc":"2.0"}
512
R5905948 EVENT MASTER DEVICES 17/07/2017
Summary of Contents for S3 series
Page 1: ...Event Master Devices User s Guide R5905948 05 17 07 2017 ...
Page 9: ...Table of contents Index 531 R5905948 EVENT MASTER DEVICES 17 07 2017 5 ...
Page 10: ...Table of contents 6 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 20: ...2 Safety 16 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 66: ...4 Hardware orientation 62 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 90: ...5 Front Panel Menu orientation 86 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 264: ...8 Updating firmware 260 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 268: ...9 General operation example Image 9 3 264 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 285: ...9 General operation example Image 9 25 R5905948 EVENT MASTER DEVICES 17 07 2017 281 ...
Page 288: ...9 General operation example 284 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 316: ...10 Controller orientation 312 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 326: ...11 Controller Configuration 322 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 352: ...12 Controller Operation 348 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 418: ...13 E2 Maintenance 414 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 488: ...16 EC 200 Maintenance 484 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 494: ...17 Environmental information 490 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 512: ...A Specifications 508 R5905948 EVENT MASTER DEVICES 17 07 2017 ...
Page 527: ...C Troubleshooting C TROUBLESHOOTING R5905948 EVENT MASTER DEVICES 17 07 2017 523 ...
Page 528: ...C Troubleshooting 524 R5905948 EVENT MASTER DEVICES 17 07 2017 ...