Difference between revisions of "Change API legacy"
From ElphelWiki
| (2 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Elphel cameras have two different APIs. The | + | {{Manual legacy_pages}} |
| + | |||
| + | Elphel cameras have two different APIs. The [[ccam.cgi]] API and the old [[Video API]] which is a superset of the [[AxisAPI]]. By default (after flashing), Elphel cameras (at least the 333 model) work in the [[ccam.cgi]] API mode, which means that all attempts to acces the images using the [[Video API]] will come back with a <tt>500 Server Error</tt>. | ||
To check wich API is currently active for your camera, use the "chapi.cgi" CGI script: | To check wich API is currently active for your camera, use the "chapi.cgi" CGI script: | ||
Latest revision as of 23:55, 13 August 2008
This is a legacy page. The information bellow is not compatible with Elphel 393 or 353/363 series cameras.
Elphel cameras have two different APIs. The ccam.cgi API and the old Video API which is a superset of the AxisAPI. By default (after flashing), Elphel cameras (at least the 333 model) work in the ccam.cgi API mode, which means that all attempts to acces the images using the Video API will come back with a 500 Server Error.
To check wich API is currently active for your camera, use the "chapi.cgi" CGI script:
http://192.168.0.9/cgi-bin/admin/chapi.cgi?action=status
This will return and XML document such as:
<camera> <api>0</api> </camera>
meaning:
To change the API, use the action=setup&api=X parameters, e.g.:
http://192.168.0.9/cgi-bin/admin/chapi.cgi?action=setup&api=1
which will change the API even over reboots and return the changed configuration:
<camera> <api>1</api> </camera>
