API reference: https://www.qoitech.com/help/tcpserver/#arc_is_connected
I am trying to use our python code (used to automate measurements using an Otii Arc device) to control an Otii Ace device, basically to perform the same measurements using higher supply voltages. I am using Otii windows software 3.1.0 in combination with Otii ace pro (FW 3.0.4)
Where I get stuck, while performing the same sequence of commands as with ace, is that the device seems not connected and the ‘project_start_recording’ command times out. (snippet of log below). I am using the command set prefixed with arc because the TCP interface does not seem to support ace prefixed counterparts. Or at least I could not find an Ace specific command set online.
What I do notice is that in the new version 3 windows software you first have to “Add” a device before you can access all the other controls. Does the TCP API support something similar that I am forgetting to call before recording? How can I connect my Ace box with the TCP API and my python code?
Log snippet:
arc_set_main {‘type’: ‘response’, ‘cmd’: ‘arc_set_main’, ‘data’: {}}
otii_create_project {‘type’: ‘response’, ‘cmd’: ‘otii_create_project’, ‘data’: {‘project_id’: 1}}
otii_get_active_project {‘type’: ‘response’, ‘cmd’: ‘otii_get_active_project’, ‘data’: {‘project_id’: 1}}
arc_is_connected {‘type’: ‘error’, ‘errorcode’: ‘Device not connected’, ‘cmd’: ‘arc_is_connected’, ‘data’: {}}
arc_enable_channel {‘type’: ‘error’, ‘errorcode’: ‘Device not connected’, ‘cmd’: ‘arc_enable_channel’, ‘data’: {}}
arc_enable_channel {‘type’: ‘error’, ‘errorcode’: ‘Device not connected’, ‘cmd’: ‘arc_enable_channel’, ‘data’: {}}
project_start_recording {‘type’: ‘error’, ‘errorcode’: ‘Command timeout’, ‘cmd’: ‘project_start_recording’, ‘data’: {}}
project_stop_recording {‘type’: ‘error’, ‘errorcode’: ‘Unknown error’, ‘cmd’: ‘project_stop_recording’, ‘data’: “Cannot access ‘a’ before initialization”}