uArm Creator Studio is a Visual Programming Language for robot arms, with a heavy emphasis on computer vision and usability for both low experience and high experience programmers. It's written entirely in Python, and supports python scripting within the application.
It was erroring out during camera setup. Didn't dig too much, but looks like some checks were missing before initialization. I was able to work around the issue by using opencv 3.1 to set up the camera first, then launch again with opencv3.2.
Good thing is that opencv3.2 has fix for the tracking issue, so it does not error out at calibration.
Robot ERROR: Tried setting uArm when it was already set!
GUI Opening Devices Window
OpenCV: out device of bound (0-0): 1
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 2
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 3
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 4
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 5
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 6
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 7
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 8
OpenCV: camera failed to properly initialize!
OpenCV: out device of bound (0-0): 9
OpenCV: camera failed to properly initialize!
2016-12-23 21:10:52.581 python[7393:10326436] An instance 0x107bec070 of class AVCaptureDALDevice was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:
<NSKeyValueObservationInfo 0x10dc83370> (
<NSKeyValueObservance 0x1080c4bc0: Observer: 0x10c4d7470, Key path: open, Options: <New: NO, Old: NO, Prior: NO> Context: 0x7fff776e53c0, Property: 0x1080c3fb0>
)
It was erroring out during camera setup. Didn't dig too much, but looks like some checks were missing before initialization. I was able to work around the issue by using opencv 3.1 to set up the camera first, then launch again with opencv3.2.
Good thing is that opencv3.2 has fix for the tracking issue, so it does not error out at calibration.
opencv: