Episode Response Amp API Overview
Design Points
-
TCP connections are used to control the amplifier with a third party device
-
Authorization is required for each TCP connection
-
Control data is sent as a C/C++ style string, i.e. NULL-terminated string
-
The string is encoded with UTF-8, formatted in JSON
Connection Scenario
The amplifier's TCP server is listening for a third party TCP client.
Note: -__.Port 8080 can be configured dynamically.
The TCP connection can support up to 10 simultaneous connections.
Status Code
All the amplifier's data is displayed as an integer in the JSON field. Use the table below determine the integer’s meaning.
Integer |
Meaning |
---|---|
200 |
Success |
300 |
Repeat operation |
400 |
User or password error |
401 |
Illegal request |
402 |
Log in first |
403 |
The default password is being used and needs to be updated |
405 |
User is signed out |
406 |
Too many incorrect password attempts and the user is locked out |
407 |
Re-enter the password |
408 |
Password has been set successfully |
500 |
An unknown error has occurred on the server |
600 |
The import file does not exist |
601 |
MD5 values do not match |
602 |
File type mismatch |
700 |
The amplifier is in standby mode |
701 |
The amplifier is in Voltage Trigger mode |
702 |
The machine is in Audio mode |
800 |
Successful update |
801 |
Failed update |