Omron HVC-P Vars Not Updating On Shell-E

Yes - for the Omron HVC-P / HVC-P2 plugin, the variable names are not the ones you guessed in your sample, and they’re also case-sensitive.

For face detection on the original Omron HVC-P skill, the common ARC variables are:

• $Omron_face_Count
• $Omron_face_CoordX
• $Omron_face_CoordY
• $Omron_face_Reliability
• $Omron_face_inclination_angle
• $Omron_face_leftright_direction
• $Omron_face_verticle_angle

And for a face-specific result:

• $Omron_age
• $Omron_gender
• $Omron_expression
• $Omron_gaze_LeftRight
• $Omron_gaze_UpDown
• $Omron_Recognized_Name
• $Omron_recognition_score

So for a basic "face exists" check, use:

• Face exists: $Omron_face_Count > 0
• Face X: $Omron_face_CoordX
• Face Y: $Omron_face_CoordY

Important note about the plugin behavior

The HVC-P plugin does not create variables named like:

• $Omron_Face_X
• $Omron_Face_Y
• $Omron_Face_Exists

Those names are why you’re not seeing anything in Variable Watcher.

Minimal working example

Also, since you’re using Shell-e + IoTiny, I’d strongly recommend using JavaScript in the Script skill instead of EZ-Script. ARC’s JavaScript is better for this kind of control loop.

Here’s a simple example that:

1. Triggers Omron detection
2. Waits a short moment
3. Reads the face variables
4. Moves two servos on d0 and d1

var faceCount = getVar("$Omron_face_Count", 0);

if (faceCount > 0) {
  var faceX = getVar("$Omron_face_CoordX", 50);
  var faceY = getVar("$Omron_face_CoordY", 50);

  // Map from 0-100 face coordinates to servo corrections
  var pan = 90 - ((faceX - 50) * 0.8);
  var tilt = 90 + ((faceY - 50) * 0.8);

  if (pan < 1) pan = 1;
  if (pan > 180) pan = 180;
  if (tilt < 1) tilt = 1;
  if (tilt > 180) tilt = 180;

  Servo.setPosition(d0, pan);
  Servo.setPosition(d1, tilt);

  print("Face detected: X=" + faceX + ", Y=" + faceY);
} else {
  print("No face detected");
}

If you want to trigger detection first

If the plugin expects a command before the variables update, do this:

controlCommand("Omron HVC-P", "Omron_Detect_All");
sleep(200);

var faceCount = getVar("$Omron_face_Count", 0);
var faceX = getVar("$Omron_face_CoordX", 50);
var faceY = getVar("$Omron_face_CoordY", 50);

print("Count=" + faceCount + " X=" + faceX + " Y=" + faceY);

A couple of likely issues in your setup

1) Wrong variable names

This is the biggest one. Use the exact names above.

2) Not enough time after Omron_Detect_All

Sleep(200) may be too short depending on the camera response time. Try 300-500 ms.

3) Your COM link is fine, but the camera may not have returned data yet

The plugin can show "connected" even if the detection cycle isn’t producing results yet.

4) Don’t poll too fast

Calling detect every 300-500 ms is reasonable. Faster can overwhelm the camera/plugin and make results unreliable.

Recommended loop timing

Try this as a starting point:

while (true) {
  controlCommand("Omron HVC-P", "Omron_Detect_All");
  sleep(400);

  var faceCount = getVar("$Omron_face_Count", 0);
  var faceX = getVar("$Omron_face_CoordX", 50);
  var faceY = getVar("$Omron_face_CoordY", 50);

  if (faceCount > 0) {
    var pan = 90 - ((faceX - 50) * 0.8);
    var tilt = 90 + ((faceY - 50) * 0.8);

    Servo.setPosition(d0, pan);
    Servo.setPosition(d1, tilt);
  }

  sleep(100);
}

One thing I’d verify in the HVC-P skill

Open the skill’s kebab menu / configure menu and confirm:

• the port is correct
• baud is set correctly
• the Python folder is set
• the album folder is set if you’re using recognition
• the skill is actually configured for the detection modes you want

Useful reference

The Omron second-camera plugin notes and variable list are here:

• https://synthiam.com/Support/Skills/Camera/Omron-HVC-P2-second-camera?id=16204

And the Script robot skill docs:

• https://synthiam.com/Support/Skills/Scripting/Script?id=16089

If you want, I can help you rewrite your current routine into a clean ARC JavaScript face-tracking script for the Shell-e that runs on the IoTiny and avoids overrunning the camera.