Again, the debug log window will show why the ezb was disconnected. Simply press the button to view the Debug Log Window and view the log to see why the EZB has been disconnected.

OK DJ, I got the following in the debug window.  Looks like the firmware is not sending the data...  not sure why.

DJ, I think I found the issue it looks to be in the firmware I will continue my testing.

I haven’t checked, but does the wifi and i2c of the esp32 work at the same time? I know some of the pins are used by the wifi features.

I looked and it seems i2c should be fine. Just make sure you’re not using pins that the wifi is using.

so I’m guessing the issue is going to be with the data not being sent from the firmware. The command 0x00 is sent to the esp32, but there’s no response it appears.

DJ,  I have some more questions based on things I am seeing that I have not been able to fix.  Please see the following pictures:

The issue is the values in the Variable Watcher skill.  I see the six vars for my skill: AngleZ, AngleY, AngleZ, servoYvalue, servoPvalue, servoRvalue.

The servoYvalue, servoPvalue, servoRvalue values are reporting in the watcher skill correctly, but the AngleZ, AngleY, AngleZ do not if any of these values are negative values the Watcher shows them as values like 65514, 65528 not the correct value of -9 or -21 shown in the last picture.

You can also see I converted the float ypr values to float like you said.  Not sure if I did it correctly but the value in the serial monitor in the last pictures shows the float and the converted values and they seem to be where they should be.

      AngleZ=int(round(ypr[0]));
      AngleY=int(round(ypr[1]));
      AngleX=int(round(ypr[2]));

The other thing I don't understand is why in the MPU skill window the values are not being displayed in the textbox control

void readValues()
    {
        try
        {

            var response = EZBManager.EZBs[0].SendCommandData(12, 0x00);

            UInt16 AngleZ = BitConverter.ToUInt16(response, 0);
            UInt16 AngleY = BitConverter.ToUInt16(response, 2);
            UInt16 AngleX = BitConverter.ToUInt16(response, 4);
            UInt16 servoRvalue = BitConverter.ToUInt16(response, 6);
            UInt16 servoPvalue = BitConverter.ToUInt16(response, 8);
            UInt16 servoYvalue = BitConverter.ToUInt16(response, 10);

            ARC.Scripting.VariableManager.SetVariable("$AngleZ", AngleZ);
            ARC.Scripting.VariableManager.SetVariable("$AngleY", AngleY);
            ARC.Scripting.VariableManager.SetVariable("$AngleX", AngleX);
            ARC.Scripting.VariableManager.SetVariable("$servoRvalue", servoRvalue);
            ARC.Scripting.VariableManager.SetVariable("$servoPvalue", servoPvalue);
            ARC.Scripting.VariableManager.SetVariable("$servoYvalue", servoYvalue);

            if (Invokers.GetCheckedValue(cbDebug))
                Invokers.SetAppendText(textBox1, true, "AngleZ: {0}, AngleY: {1}, AngelX: {3}, Yaw: {4}, Pitch: {5}, Roll: {6}", AngleZ, AngleY, AngleX, servoYvalue, servoPvalue, servoRvalue);
            }
               catch (Exception ex)
            {
               Invokers.SetAppendText(textBox1, true, ex.ToString());
        }

    }

Oh you’re getting close! Seems like they’re only a few minor things you’ll need to sort out. Good work!

such as you’re converting a signed int to an unsigned int. And a few other stuff. But you’re so close.

Thanks but I could use a little help DJ.  Can you provide a sample of how I need to convert the Angel Var's so they report correctly the watcher, and also tell me how I can get the values to show up in the textbox