Robot Not a Dev? Pre-order Now
Not a Dev?

Not sound when testing audio assets


#1

I just started testing assets, pulled audio list, set volume to max (100) and then hit “Play Clip”, there is no sound coming out from Misty. Console status = success. I am using API explorer. Images from assets do work but Misty has a 10 - 15 second response delay. Any suggestions before I decide to check for loose cables?

Best

William (“Devil’s advocate”)


#2

Hi @levesongower!

Sorry for the trouble! This may seem strange, but can you do a GetDeviceInformation call, then post the results of that?

https://docs.mistyrobotics.com/apis/api-reference/rest/#getdeviceinformation

You can also get the info via the API Explorer.


#3
  1. {batteryLevel: {…}, currentProfileName: “ASUS”, hardwareInfo: {…}, ipAddress: “192.168.1.38”, networkConnectivity: “InternetAccess”, …}

  2. batteryLevel: {batteryChargePercent: 0, currentVoltage: 11.883}

  3. currentProfileName: “ASUS”

  4. hardwareInfo: {mcBoard: “BoardId: 2490421-540488760, Hardware:2.0, Firmware:255.255.2.1”}

  5. ipAddress: “192.168.1.38”

  6. networkConnectivity: “InternetAccess”

  7. outputCapabilities: (12) [“User1”, “User2”, “Locomotion”, “LocomotionTrack”, “Illumination”, “ResetImu”, “/Robot/Display”, “/Robot/ChangeBusMode/”, “Halt”, “/Robot/AudioPlayback/speaker”, “Actuator_HeadPitch”, “MessageStream”]

  8. robotId: “00:00:00:00:00:00-00:00:00:00:00:00-00:00:00:00:00:00-00:00:00:00:00:00”

  9. robotVersion: “1.1.9.0”

  10. sensorCapabilities: (14) ["/Sensors/RTC/ConnectionStatusMessage", “/Sensors/OccipitalSlam”, “/Sensors/RTC/BatteryCharge”, “CV_4k”, “DriveEncoders”, “TOF_Right”, “TOF_Center”, “TOF_Left”, “TOF_Back”, “Hallucinated_OnlyOne”, “/Sensors/StringSensor”, “Actuator_HeadPitch”, “/Sensors/HardwareDetails/RtcBoard”, “/Sensors/HardwareDetails/McBoard”]

  11. sensoryServiceAppVersion: “1.1.283”

  12. serialNumber: “20180723_MR_1201”

  13. windowsOSVersion: “Windows.IoT - 10.0.17134.1”

  14. proto: Object


#4

I’m going to Slack you. It will be easier to support you that way, if that’s okay. If not, let me know, and we’ll work through things here…


#5

okidoki, thank you :slight_smile:


#6

Cool. I’m in the MistyCommunity slack in the #technical_support channel.


#7

Just to close this out a bit – this is an issue from a partial software update happening, which can cause a version mismatch in Misty’s software. The “no sound” symptom is one of the indicators. If this happens to you, please do let us know!