pyzenbo.modules.error_code module¶
-
pyzenbo.modules.error_code.NO_ERROR= 0¶ no error
-
pyzenbo.modules.error_code.UNKNOWN_COMMAND= 1¶ unknown command
-
pyzenbo.modules.error_code.COMMAND_NOT_IN_QUEUE= 2¶ command not in waiting queue
-
pyzenbo.modules.error_code.COMMAND_OVERRIDE= 3¶ command is overridden
-
pyzenbo.modules.error_code.WAITING_QUEUE_IS_FULL= 4¶ waiting queue is full
-
pyzenbo.modules.error_code.USER_CANCELED= 5¶ user canceled
-
pyzenbo.modules.error_code.PROCESS_KILLED= 6¶ process killed
-
pyzenbo.modules.error_code.PERMISSION_DENIED= 7¶ permission denied
-
pyzenbo.modules.error_code.SERVICE_FAILED= 8¶ service failed
-
pyzenbo.modules.error_code.FOLLOW_WRONG_USER= 9¶ robot followed the wrong person
-
pyzenbo.modules.error_code.UNKNOWN_ERROR= 10¶ unknown error
-
pyzenbo.modules.error_code.MAP_NOT_EXIST= 11¶ map does not exist
-
pyzenbo.modules.error_code.MULTITASK_QUEUE_IS_FULL= 12¶ multi-task queue is full
-
pyzenbo.modules.error_code.NOT_MULTITASK_COMMAND= 13¶ is not a multi-task command
-
pyzenbo.modules.error_code.ADJUST_SPEED_FAILED= 15¶ adjust motion speed failed
-
pyzenbo.modules.error_code.CANCEL_FAILED= 16¶ cancel failed
-
pyzenbo.modules.error_code.QUEUE_IS_EMPTY= 17¶ queue is empty
-
pyzenbo.modules.error_code.QUEUE_IS_NOT_EMPTY= 18¶ queue isn’t empty
-
pyzenbo.modules.error_code.CHARGING= 19¶ robot is charging
-
pyzenbo.modules.error_code.ERROR_FACE_UNKNOWN= -1¶ unknown face
-
pyzenbo.modules.error_code.ERROR_FACE_DETECT_FAIL= -2¶ face detect failed
-
pyzenbo.modules.error_code.ERROR_RECOGNITION_STATUS_FAILED= -3¶ face recognition failed
-
pyzenbo.modules.error_code.ERROR_FACE_TOO_SIDE= -4¶ face is sideways
-
pyzenbo.modules.error_code.ERROR_FACE_TOO_DARK= -5¶ face is too dark
-
pyzenbo.modules.error_code.ERROR_FACE_UNDER_RECOGNITION= -6¶ face under recognition
-
pyzenbo.modules.error_code.ERROR_FACE_INTERNAL_IDERROR= -7¶ face ID error
-
pyzenbo.modules.error_code.ERROR_FACE_NO_ONE_APPEAR= -8¶ no one appeared
-
pyzenbo.modules.error_code.ERROR_FACE_TOO_FAR= -9¶ face too far
-
pyzenbo.modules.error_code.ERROR_FACE_TOO_CLOSE= -10¶ face is too close
-
pyzenbo.modules.error_code.ERROR_FACE_TOO_LEFT= -11¶ face is too left
-
pyzenbo.modules.error_code.ERROR_FACE_TOO_RIGHT= -12¶ face is too right
-
pyzenbo.modules.error_code.ERROR_FACE_ALREADY_ENROLL= -13¶ face already enrolled
-
pyzenbo.modules.error_code.ERROR_UNDER_LONG_PROCESS_TIME= -14¶ under long process time
-
pyzenbo.modules.error_code.FAIL_TIME_OUT= -16¶ fail timeout
-
pyzenbo.modules.error_code.ERROR_FACE_IS_AMBIGUOUS= -21¶ face is ambiguous
-
pyzenbo.modules.error_code.GOTO_NO_SDCARD_PERMISSION= 67502080¶ need to grant read/write SD Card permission
-
pyzenbo.modules.error_code.GOTO_NO_CANDRAWOVERLAYS_PERMISSION= 67502081¶ need to grant can draw overlays permission
-
pyzenbo.modules.error_code.GOTO_MAP_NOT_EXIST= 67502082¶ could not find target slam map
-
pyzenbo.modules.error_code.GOTO_QUERY_LOCATION_FAIL_NO_LABEL= 67502083¶ queried labeling location do not exist
-
pyzenbo.modules.error_code.GOTO_INVALID_ADDRESS= 67502084¶ invalid address which out of map size or occupy point
-
pyzenbo.modules.error_code.GOTO_LOCALIZATION_ONERROR= 67502085¶ localization query fail
-
pyzenbo.modules.error_code.GOTO_NO_FREE_POINT_FROM_START= 67502086¶ could not find any free point from start
-
pyzenbo.modules.error_code.GOTO_USER_CANCELED_LOCALIZE_GUIDE= 67502087¶ user cancel to help localization
-
pyzenbo.modules.error_code.GOTO_USER_REQUEST_MOVING_GUIDE= 67502088¶ user want to move zenbo to help to localize
-
pyzenbo.modules.error_code.GOTO_USER_CANCEL_MOVING_TASK= 67502089¶ user cancel moving task, need to send notification to zenbo mobile application
-
pyzenbo.modules.error_code.GOTO_FAIL_TIME_OUT= 67502090¶ avoid obstacle fail timeout, including user cancel moving task or wait user ds command timeout
-
pyzenbo.modules.error_code.GOTO_UNEXPECTED_ERROR= 67502091¶ undefined error including ds initial fail, motion initial fail, go to time out … etc
-
pyzenbo.modules.error_code.GOTO_STUCK_CANCEL= 67502092¶ zenbo got stuck, and user cancel task
-
pyzenbo.modules.error_code.GOTO_GUIDE_TIMEOUT_OR_CANCEL= 67502093¶ guide time out or user cancel task
-
pyzenbo.modules.error_code.GOTO_STUCK_TIMEOUT= 67502094¶ zenbo got stuck and timeout
-
pyzenbo.modules.error_code.GOTO_QUERY_LOCATION_FAIL_NO_FREE_POINT= 67502095¶ queried labeling location have no free point to go
-
pyzenbo.modules.error_code.GOTO_ZMC_CAMERA_OFF= 67502096¶ zmc mode, camera disable
-
pyzenbo.modules.error_code.COMPASS_SERVICE_BIND_FAIL= 67764225¶ bind compass service fail
-
pyzenbo.modules.error_code.COMPASS_SENSOR_NO_CONTACT= 67764226¶ the values returned by this sensor cannot be trusted because the sensor had no contact with what it was measuring.
-
pyzenbo.modules.error_code.EXP_INIT_FINISH= -46¶ expression initial successfully
-
pyzenbo.modules.error_code.EXP_NOT_INIT_FINISH= -47¶ expression do not initial successfully
-
pyzenbo.modules.error_code.EXP_SEND_ERROR_ARGUMENT= -48¶ send error argument to expression
-
pyzenbo.modules.error_code.EXP_TTS_IS_PLAYING= -49¶ can’t resume when TTS is playing
-
pyzenbo.modules.error_code.EXP_FACE_PREEMPTED= -50¶ face don’t play finish when new face command have preempted
-
pyzenbo.modules.error_code.EXP_NEED_RESTART= -51¶ expression need restart when TTS or face service occur error
-
pyzenbo.modules.error_code.EXP_TTS_STOPPED= -52¶ TTS has stopped when playing
-
pyzenbo.modules.error_code.EXP_PREVIOUS_PAUSE_TTS_ABANDONED= -53¶ previous pause TTS sentence has abandoned cause by new one TTS to be paused
-
pyzenbo.modules.error_code.EXP_TTS_PAUSED= -54¶ TTS has paused when playing
-
pyzenbo.modules.error_code.EXP_TTS_RESUME= -55¶ TTS has resumed
-
pyzenbo.modules.error_code.EXP_FACIAL_SYSTEM_CHANGE= -56¶ request facial system change but not finish
-
pyzenbo.modules.error_code.EXP_WRITE_DATABASE_FAILED= -57¶ request to put property to setting database but occurs error
-
pyzenbo.modules.error_code.EXP_QUEUE_RESET= -58¶ TTS and face queue is resetting
-
pyzenbo.modules.error_code.COORDINATOR_COMMAND_NOT_IN_QUEUE= 131328¶ command isn’t in coordinator queue
-
pyzenbo.modules.error_code.COORDINATOR_PERMISSION_DENIED= 131584¶ no permission to execute this command
-
pyzenbo.modules.error_code.COORDINATOR_QUEUE_EMPTY= 131840¶ coordinator queue is empty
-
pyzenbo.modules.error_code.COORDINATOR_QUEUE_NOT_EMPTY= 132096¶ coordinator queue isn’t empty
-
pyzenbo.modules.error_code.COORDINATOR_UNKNOWN_COMMAND= 132352¶ it’s an unknown command
-
pyzenbo.modules.error_code.COORDINATOR_QUEUE_FULL= 132608¶ coordinator queue is full
-
pyzenbo.modules.error_code.COORDINATOR_READY_TO_CHARGE= 132864¶ robot needs to charge first
-
pyzenbo.modules.error_code.COORDINATOR_DESTROYED= 133120¶ coordinator destroyed
-
pyzenbo.modules.error_code.COORDINATOR_APP_CANCELED= 133376¶ command is canceled by application
-
pyzenbo.modules.error_code.COORDINATOR_COMMAND_PREEMPTED= 133632¶ command is preempted
-
pyzenbo.modules.error_code.COORDINATOR_CANCEL_FAILED= 133888¶ command cancel failed
-
pyzenbo.modules.error_code.COORDINATOR_PRIORITY_TOO_LOW= 134144¶ a high-priority application is running, coordinator will reject commands from other package
-
pyzenbo.modules.error_code.COORDINATOR_CAMERA_RECORD_NOT_ALLOW= 134400¶ not allow that application use motion command with permission camera or record
-
pyzenbo.modules.error_code.COORDINATOR_USB_CONNECTED= 134656¶ not allow that application use motion command with USB connected
-
pyzenbo.modules.error_code.COMMON_UNKNOWN_ERROR= 196864¶ it’s an unknown error
-
pyzenbo.modules.error_code.COMMON_SERVICE_FAILED= 197120¶ start service failed
-
pyzenbo.modules.error_code.COMMON_API_VERSION_TOO_OLD= 197121¶ RobotAPI version too old, please update to newest version
-
pyzenbo.modules.error_code.COMMON_IN_SLEEP_MODE= 197122¶ In sleep mode, reject command
-
pyzenbo.modules.error_code.COMMON_NOT_SUPPORTED_COMMAND= 197123¶ robot not suppord this command
-
pyzenbo.modules.error_code.COMMON_PROCESS_KILLED= 197376¶ process has been killed
-
pyzenbo.modules.error_code.COMMON_CHARGING= 197632¶ robot is charging now
-
pyzenbo.modules.error_code.COMMON_CHARGING_AC= 197633¶ robot is charging with AC-type now
-
pyzenbo.modules.error_code.COMMON_CHARGING_DOCKING= 197634¶ robot is charging with Docking-type now
-
pyzenbo.modules.error_code.COMMON_MOVING_TO_DOCKING_STATION= 197635¶ robot is moving to docking station for charging, can’t execute any command
-
pyzenbo.modules.error_code.COMMON_MAP_IS_BUILDING= 197636¶ Can’t get map because map is building
-
pyzenbo.modules.error_code.COMMON_OUT_OF_BATTERY= 197888¶ robot is out of battery, can’t execute any command
-
pyzenbo.modules.error_code.COMMON_SCREEN_OFF= 197889¶ robot is off in screen, can’t execute any command
-
pyzenbo.modules.error_code.COMMON_MOVING_AWAY_DOCKING_STATION= 197890¶ robot is moving away docking station to execute motion task, can’t execute any command
-
pyzenbo.modules.error_code.COMMON_MOVING_AWAY_DOCKING_STATION_TIMEOUT_FAILED= 197891¶ robot get failed when go away docking station because obstacle in front of docking station
-
pyzenbo.modules.error_code.COMMON_ZMC_CAMERA_OFF= 197892¶ camera disable by ZMC
-
pyzenbo.modules.error_code.COMMON_ZMC_MOVING_OFF= 197893¶ moving disable by ZMC
-
pyzenbo.modules.error_code.COMMON_FILE_NOT_FOUND= 197894¶ File isn’t found
-
pyzenbo.modules.error_code.COMMON_NETWORK_REQUEST_ERROR= 197895¶ network request error
-
pyzenbo.modules.error_code.COMMON_JSON_PARSE_ERROR= 197896¶ json parse error
-
pyzenbo.modules.error_code.COMMON_SOCKET_FAIL= 262400¶ TCP/IP socket connection fail
-
pyzenbo.modules.error_code.MOTION_FAIL_SEND_CMD_DATA= 33554433¶ fail to send command
-
pyzenbo.modules.error_code.MOTION_BLOCK_COMMAND= 33554434¶ block command
-
pyzenbo.modules.error_code.MOTION_FAIL_OVER_FLOW= 33554435¶ command over flow
-
pyzenbo.modules.error_code.MOTION_FAIL_SEND_CMD_SIZE= 33554438¶ command data size is not correct
-
pyzenbo.modules.error_code.MOTION_FAIL_OPEN_FILE= 33554443¶ fail to open the trajectory file
-
pyzenbo.modules.error_code.MOTION_FAIL_TIMEOUT= 33554448¶ base status timeout
-
pyzenbo.modules.error_code.MOTION_FAIL_OBSTACLE= 33554449¶ fail obstacle
-
pyzenbo.modules.error_code.MOTION_FAIL_REACH= 33554450¶ fail reach
-
pyzenbo.modules.error_code.MOTION_RESET_END_POINT= 33554451¶ go from A to B reset end point
-
pyzenbo.modules.error_code.MOTION_RESET_START_POINT= 33554452¶ go from A to B start end point
-
pyzenbo.modules.error_code.MOTION_FAIL_LOAD_MAP= 33554453¶ fail to load the map
-
pyzenbo.modules.error_code.MOTION_END_POINT_OUT_OF_MAP= 33554454¶ end point is out of map
-
pyzenbo.modules.error_code.MOTION_START_POINT_OUT_OF_MAP= 33554455¶ start point is out of map
-
pyzenbo.modules.error_code.MOTION_NO_ROUTE= 33554456¶ there is no route in path planning
-
pyzenbo.modules.error_code.MOTION_NO_SLAM_MAP= 33554457¶ no slam map
-
pyzenbo.modules.error_code.MOTION_CHECK_DOOR_LABEL= 33554458¶ check door label
-
pyzenbo.modules.error_code.MOTION_NO_ROUTE_A= 33554459¶ no route a
-
pyzenbo.modules.error_code.MOTION_NO_ROUTE_B= 33554460¶ no route b
-
pyzenbo.modules.error_code.MOTION_NO_SECTION_PATH= 33554461¶ no section path
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_B60= 33554542¶ B60 detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_R70= 33554543¶ R70 detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_R45= 33554544¶ R45 detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_L70= 33554545¶ L70 detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_L45= 33554546¶ L45 detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_LR70= 33554547¶ both L70 and R70 detect cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_LIFTED= 33554548¶ Robot has left the ground
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_RECOVER_FAIL= 33554549¶ drop recover fail
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_LR45= 33554550¶ both R45 and L45 detect cliff
-
pyzenbo.modules.error_code.MOTION_EXCEED_VEL_BOUND= 33554468¶ speed level exceed velocity bound
-
pyzenbo.modules.error_code.MOTION_OUT_WORK_SPACE= 33554473¶ out work space
-
pyzenbo.modules.error_code.MOTION_AVOIDANCE_STOP= 33554478¶ robot faces with obstacles
-
pyzenbo.modules.error_code.MOTION_ANTI_DROP= 33554479¶ any drop IR is triggered
-
pyzenbo.modules.error_code.MOTION_FAIL_SET_ODOMETRY= 33554483¶ fail set odometry
-
pyzenbo.modules.error_code.MOTION_FAIL_OUT_OF_BOUNDS= 33554488¶ speed level out of bounds
-
pyzenbo.modules.error_code.MOTION_FAIL_OUT_OF_TEMPO_BOUND= 33554493¶ exceed the bound of tempo
-
pyzenbo.modules.error_code.MOTION_SPECIFIC_ACTION_OUT_OF_DEFINITION= 33554494¶ specific action ID is out of definition
-
pyzenbo.modules.error_code.MOTION_FAIL_DOCKING_THREE_TIMES= 33554582¶ docking process retry time is over limit
-
pyzenbo.modules.error_code.MOTION_FAIL_DOCKING_TIMEOUT= 33554583¶ go back docking timeout
-
pyzenbo.modules.error_code.MOTION_FAIL_DOCKING_ERROR= 33554584¶ docking error timeout state
-
pyzenbo.modules.error_code.MOTION_FAIL_DOCKING_ABORT= 33554585¶ docking abort state
-
pyzenbo.modules.error_code.MOTION_FAIL_DOCKING_TERMINATE= 33554586¶ docking process terminated
-
pyzenbo.modules.error_code.MOTION_FAIL_FOLLOW_USER_OBSTACLE= 33554633¶ it’s a warning hint instead of a fail case for coordinator’s post application
-
pyzenbo.modules.error_code.MOTION_REMOTE_EXCEPTION= 33555332¶ remote exception
-
pyzenbo.modules.error_code.MOTION_FAIL_BATTERY_PLUGGED_AC= 33555337¶ fail battery plugged AC
-
pyzenbo.modules.error_code.MOTION_OVER_TEMPERATURE_NECK_YAW= 33554933¶ neck yaw motor over temperature
-
pyzenbo.modules.error_code.MOTION_OVER_TEMPERATURE_NECK_PITCH= 33554934¶ neck pitch motor over temperature
-
pyzenbo.modules.error_code.MOTION_OVER_TEMPERATURE_WHEEL_L= 33554936¶ left wheel motor over temperature
-
pyzenbo.modules.error_code.MOTION_OVER_TEMPERATURE_WHEEL_R= 33554940¶ right wheel motor over temperature
-
pyzenbo.modules.error_code.MOTION_OVER_TEMPERATURE_ALL= 33554947¶ all motor over temperature
-
pyzenbo.modules.error_code.MOTION_OVER_CURRENT_NECK_YAW= 33554953¶ neck yaw motor over current
-
pyzenbo.modules.error_code.MOTION_OVER_CURRENT_NECK_PITCH= 33554954¶ neck yaw motor over current
-
pyzenbo.modules.error_code.MOTION_OVER_CURRENT_WHEEL_L= 33554956¶ left wheel motor over current
-
pyzenbo.modules.error_code.MOTION_OVER_CURRENT_WHEEL_R= 33554960¶ right wheel motor over current
-
pyzenbo.modules.error_code.MOTION_OVER_CURRENT_ALL= 33554967¶ all motor over current
-
pyzenbo.modules.error_code.MOTION_OVER_LOAD_NECK_YAW= 33554973¶ neck yaw motor over load
-
pyzenbo.modules.error_code.MOTION_OVER_LOAD_NECK_PITCH= 33554974¶ neck pitch motor over load
-
pyzenbo.modules.error_code.MOTION_OVER_LOAD_WHEEL_L= 33554976¶ left wheel motor over load
-
pyzenbo.modules.error_code.MOTION_OVER_LOAD_WHEEL_R= 33554980¶ right wheel motor over load
-
pyzenbo.modules.error_code.MOTION_OVER_LOAD_ALL= 33554987¶ all motor over load
-
pyzenbo.modules.error_code.MOTION_TRAPPING= 33554513¶ robot faces with trapping situation
-
pyzenbo.modules.error_code.MOTION_BUMPING= 33554514¶ robot faces with bumping situation
-
pyzenbo.modules.error_code.MOTION_NOTHING= 33554515¶ nothing
-
pyzenbo.modules.error_code.MOTION_BUMPING_RECOVER_FAIL= 33554516¶ fail to recover from bumping situation. (B60 drop while recover from bumping)
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_FR= 33554552¶ FR detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_FL= 33554553¶ FL detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_FC= 33554554¶ FC detects cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_FRC= 33554555¶ both FR and FC detect cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_FLC= 33554556¶ both FL and FC detect cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_FRL= 33554557¶ both FR and FL detect cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_DROP_IR_FRLC= 33554558¶ both FR, FL and FC detect cliff
-
pyzenbo.modules.error_code.MOTION_FAIL_CTRL_BASE_VEL_SAFETY= 33554833¶ robot faces with not safety situation during ctrlBaseVel
-
pyzenbo.modules.error_code.MOTION_FAIL_TRACK_LINE_TIME_OUT= 33554733¶ follow line timeout (Can’t detect line over 3 sec)
-
pyzenbo.modules.error_code.MOTION_FAIL_LINE_DIFFERENCE= 33554734¶ the difference between line and floor is too small
-
pyzenbo.modules.error_code.MOTION_FAIL_NOT_CALIBRATION= 33554735¶ user not calibration before execute line following
-
pyzenbo.modules.error_code.MOTION_FAIL_SENSOR_NON_UPDATE= 33554736¶ color sensor non update
-
pyzenbo.modules.error_code.MOTION_PARAMETER_IS_NOT_APPLIED= 33554688¶ some parameters are not applied
-
pyzenbo.modules.error_code.RETURN_BASE_NO_SPECIFIC_CHARGING_STATION= 67764224¶ no specific charging station
-
pyzenbo.modules.error_code.COLOR_IDENTIFICATION_TIMEOUT= 67829760¶ identify color timeout (Can’t detect color result over 3 sec)
-
pyzenbo.modules.error_code.LINE_FOLLOWER_INVALID_ARGUMENT= 67830016¶ set invalid argument to track line
-
pyzenbo.modules.error_code.LINE_FOLLOWER_DUPLICATE_ARGUMENT= 67830017¶ set duplicate argument to track line
-
pyzenbo.modules.error_code.LINE_FOLLOWER_TRACK_LINE_TIME_OUT= 67830018¶ follow line timeout (Can’t detect line over 3 sec)
-
pyzenbo.modules.error_code.LINE_FOLLOWER_INVALID_COLOR_TYPE= 67830019¶ set invalid color type
-
pyzenbo.modules.error_code.LINE_FOLLOWER_INVALID_BEHAVIOR= 67830020¶ set invalid behavior
-
pyzenbo.modules.error_code.LINE_FOLLOWER_TOO_MANY_COLOR_ARRAY= 67830021¶ set up too many color array on line
-
pyzenbo.modules.error_code.VISION_R200_OPEN_FAILED= 83951617¶ R200 open failed
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_UNKNOWN_ERROR= 84017153¶ unknown error
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_INVALID_STATUS= 84017154¶ localization start without initialization first
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_MAP_FAILED= 84017155¶ loading map failed
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_NO_SPECIFIED_MAP_DIR= 84017156¶ no specified map directory
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_PERMISSION_DENIED= 84017157¶ no camera/storage permission
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_CANCELED= 84017158¶ localization is canceled by caller
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_RESULT_UNRELIABLE= 84017159¶ localization result is unreliable
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_OCCUPIED_POINT= 84017160¶ localization result is occupied
-
pyzenbo.modules.error_code.VISION_LOCALIZATION_DOING_MIGRATION= 84017161¶ localization is unavailable since migration is running
-
pyzenbo.modules.error_code.VISION_PROXY_RESOURCE_OCCUPIED= 84082689¶ vision resource is occupied by system plugin
-
pyzenbo.modules.error_code.VISION_PROXY_COMMAND_INTERRUPTED= 84082690¶ the vision command is interrupted by others
-
pyzenbo.modules.error_code.VISION_PROXY_RESOURCE_BLOCKED= 84082691¶ vision resource is blocked
-
pyzenbo.modules.error_code.VISION_ENROLL_RESULT_UNKNOWN_USER= 84148481¶ user cannot be recognized as faces already enroll in Database
-
pyzenbo.modules.error_code.VISION_ENROLL_RESULT_FACE_IS_AMBIGUOUS= 84148482¶ the face in current image is ambiguous
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_BEGIN_FACE_FEATURE_EXTRACTION= 84148737¶ begin face feature extraction
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_ENROLL_IMAGE_COLLECT_SUCCESS= 84148738¶ enroll image collect success
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_IMAGE_LOW_QUALITY= 84148739¶ person have blur face and fail to recognize
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_NOT_DETECTED= 84148740¶ not detected any face
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_PITCH_TOO_LARGE= 84148741¶ face pitch angle is too large
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_POSE_TOO_EXTREME= 84148742¶ user is looking somewhere else but not look into zenbo
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_RECOGNITION_SCORE_LOW_RETRYING= 84148743¶ vision service is retrying to recognize face because of low score
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_TOO_CLOSE= 84148744¶ face is too close
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_TOO_FAR= 84148745¶ face is too far
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FACE_YAW_TOO_LARGE= 84148746¶ face yaw angle is too large
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_FINISH_FACE_ENROLL= 84148747¶ face enroll is finished
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_PAUSE_ENROLL_SUCCESS= 84148748¶ pause enroll command is succeed
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_PERSON_NOT_DETECTED= 84148749¶ no any person is detected
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_RECOGNITION_OFF= 84148750¶ framework not specify turn on recognition during person detection
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_REPORT_DEFINE_POSES= 84148751¶ report all the predefined enroll posture
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_RESUME_ENROLL_SUCCESS= 84148752¶ resume enroll command is succeed
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_SKIP_POSTURE_ENROLL_SUCCESS= 84148753¶ skip enroll command is succeed
-
pyzenbo.modules.error_code.VISION_ENROLL_STATUS_WAIT_SNAPSHOT_ENROLL_IMAGE= 84148754¶ service is waiting R200 snapshot taken
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_ABORT_ENROLL_FAIL= 84148993¶ abort enroll fail
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_DUPLICATE_ENROLL_REQUEST= 84148994¶ duplicate enroll request
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_FACE_ALREADY_ENROLL= 84148995¶ new enroll face is already enroll
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_FACE_TOO_DARK= 84148996¶ face in image is too dark
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_PAUSE_ENROLL_FAIL= 84148997¶ pause enroll command is failed
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_RECOGNITION_STATUS_FAILED= 84148998¶ fail to do recognition even when face detection success
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_REGISTRATION_STATUS_FAIL= 84148999¶ current registration fail internally
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_RESUME_ENROLL_FAIL= 84149000¶ resume enroll command is failed
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_SKIP_POSTURE_ENROLL_FAIL= 84149001¶ skip enroll command is failed
-
pyzenbo.modules.error_code.VISION_ENROLL_WARNING_TOO_SIMILAR_FACE_FOR_NEW_USER= 84149002¶ new enroll person is similar to existing user but different
-
pyzenbo.modules.error_code.VISION_ENROLL_ID_ALREADY_EXIST= 84149003¶ id already exist
-
pyzenbo.modules.error_code.VISION_ENROLL_ID_IS_EMPTY= 84149004¶ id can’t be empty
-
pyzenbo.modules.error_code.VISION_ENROLL_PICTURE_INVALID= 84149005¶ too many invalid pictures
-
pyzenbo.modules.error_code.VISION_ENROLL_FOLDER_NOT_EXIST= 84149006¶ photo enroll folder not exist
-
pyzenbo.modules.error_code.WHEEL_LIGHT_EPERM= 100663297¶ wheel light locked, access denied
-
pyzenbo.modules.error_code.WHEEL_LIGHT_ENOENT= 100663298¶ no such file or directory
-
pyzenbo.modules.error_code.WHEEL_LIGHT_ENXIO= 100663302¶ no such device or address
-
pyzenbo.modules.error_code.WHEEL_LIGHT_EACCES= 100663309¶ permissions denied
-
pyzenbo.modules.error_code.WHEEL_LIGHT_ENODEV= 100663315¶ no such device
-
pyzenbo.modules.error_code.WHEEL_LIGHT_EINVAL= 100663318¶ invalid argument
-
pyzenbo.modules.error_code.WHEEL_LIGHT_I2C_TIMEOUT= 100663406¶ i2c timeout
-
pyzenbo.modules.error_code.WHEEL_LIGHT_EREMOTEIO= 100663417¶ remote I/O error
-
pyzenbo.modules.error_code.WHEEL_LIGHT_LOCKED_BY_IRREVERSIBLE_ABNORMALITY= 100663552¶ wheel light locked by irreversible abnormality
-
pyzenbo.modules.error_code.WHEEL_LIGHT_LOCKED_BY_RECOVERABLE_ABNORMALITY= 100663553¶ wheel light locked by recoverable abnormality
-
pyzenbo.modules.error_code.WHEEL_LIGHT_LOCKED_BY_BATTERY_STATUS= 100663554¶ wheel light locked by battery status
-
pyzenbo.modules.error_code.VOICE_ENROLL_HTTP_SERVICE_START_CODE= 117440513¶ http service start code
-
pyzenbo.modules.error_code.VOICE_ENROLL_HTTP_SERVICE_END_CODE= 117440514¶ http service end code
-
pyzenbo.modules.error_code.VOICE_ENROLL_SDK_REQUEST_START_CODE= 117440768¶ sdk request start code
-
pyzenbo.modules.error_code.VOICE_ENROLL_SDK_REQUEST_END_CODE= 117440769¶ sdk request end code
-
pyzenbo.modules.error_code.VOICE_ENROLL_SDK_REQUEST_LOGIN_HANDLE_ILLEGAL= 117440770¶ sdk request login handle illegal
-
pyzenbo.modules.error_code.VOICE_ENROLL_SDK_REQUEST_CONNECT_TO_SERVICE_FAIL= 117440771¶ sdk request connect to service fail
-
pyzenbo.modules.error_code.VOICE_ENROLL_SDK_REQUEST_RESPONSE_JSON_PRASE_FAIL= 117440772¶ sdk request response json prase fail
-
pyzenbo.modules.error_code.VOICE_ENROLL_SDK_REQUEST_ERROR_FILE_AS_OPEN_FAIL= 117440773¶ sdk request error file as open fail
-
pyzenbo.modules.error_code.VOICE_ENROLL_SDK_REQUEST_SDK_UNREGISTER_URL= 117440774¶ sdk request sdk unregister url
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_INTERNAL_ERROR= 117441024¶ logic service internal error
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_SIGNATURE_VERIFY_FAIL= 117441025¶ login service signature verify fail
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_ERROR_INPUT_PARAM= 117441026¶ login service error input param
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_INVALID_SIGNATURE= 117441027¶ login service invalid signature
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_APPID_NOEXIST= 117441028¶ login service appid no exist
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_REFRESH_PACKET_FAILURE= 117441029¶ login service refresh packet failure
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_PACKET_ID_CAN_NOT_BE_EMPTY= 117441030¶ login service packet id can not be empty
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_CLIENTNAME_CAN_NOT_BE_EMPTY= 117441031¶ login service clientname can not be empty
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_CREATE_CLIENT_FAILURE= 117441032¶ login service create client failure
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_REFRESH_CLIENT_FAILURE= 117441033¶ login service refresh client failure
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_SQL_ERROR= 117441034¶ login service sql error
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_TOKEN_REFRESH_FAIL= 117441035¶ login service token refresh fail
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_CREATING_PATH_SYSTEM_ERROR= 117441036¶ login service creating path system error
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_SAVE_FILE_FAILURE= 117441037¶ login serivce save file failure
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_REGISTRATION_FAILURE= 117441038¶ login service registration failure
-
pyzenbo.modules.error_code.VOICE_ENROLL_LOGIC_SERVICE_VERIFICATION_FAILURE= 117441039¶ login service verification failure
-
pyzenbo.modules.error_code.VOICE_ENROLL_SERVICE_CLIENT_CREATE_ERROR= 117441040¶ service client create error
-
pyzenbo.modules.error_code.VOICE_ENROLL_SENTENCE_NO_MATCH= 117441280¶ sentence no match
-
pyzenbo.modules.error_code.VOICE_ENROLL_SOUND_LEVEL_TOO_LOW= 117441281¶ sound level too low
-
pyzenbo.modules.error_code.VOICE_ENROLL_ENVIRONMENT_TOO_NOISY= 117441282¶ environment too noisy
-
pyzenbo.modules.error_code.VOICE_ENROLL_ENROLL_TIMEOUT= 117441283¶ enroll timeout
-
pyzenbo.modules.error_code.VOICE_ENROLL_FORCESTOP= 117441284¶ enroll force stop
-
pyzenbo.modules.error_code.VOICE_ENROLL_INIT_NOT_READY= 117441285¶ Enroll service initialization has not been completed. Please try again later.
-
pyzenbo.modules.error_code.VOICE_ENROLL_WIFI_DISCONNECT= 117441286¶ wifi disconnect
-
pyzenbo.modules.error_code.PLUGIN_FAIL_FOLLOW_USER_NOT_FOUND= 67436544¶ plugin followUser stopped because of not found
-
pyzenbo.modules.error_code.PLUGIN_FAIL_FOLLOW_USER_OBSTACLE= 67436545¶ plugin followUser stopped because of meeting obstacle
-
pyzenbo.modules.error_code.PLUGIN_FAIL_FOLLOW_USER_LOST= 67436546¶ plugin followUser stopped because of lost
-
pyzenbo.modules.error_code.code_to_description(code)¶ Get error code description.
- Parameters
code – error code number
- Returns
error code description