Skip to content
/ XiaomiCyberDog-k91 Public

小米集团 XIaomi 铁蛋 CyberDog 仿生四足机器人 Bionic quadruped robot

23 stars 10 forks Branches Tags Activity
Star
Notifications You must be signed in to change notification settings

MAVProxyUser/XiaomiCyberDog-k91

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

57 Commits
README.md
README.md
 
 
cyberdog_app.apk
cyberdog_app.apk
 
 
hot_query_robotcontroller.txt
hot_query_robotcontroller.txt
 
 

Repository files navigation

XiaomiCyberDog-k91

小米集团 XIaomi 铁蛋 CyberDog 仿生四足机器人 Bionic quadruped robot

Looking for Quadruped friends? Join "The Dog Pound animal control for Stray robot dogs" slack group:
https://join.slack.com/t/robotdogs/shared_invite/zt-1fvixx89u-7T79~VxmDYdFSIoTnSagFQ

The smart robot dog has become a reality. With the new device by Xiaomi, everyone can have such an electronic pet.
https://xiaomi-mi.com/appliances/yi-home-camera-3/
https://www.mi.com/shop/buy/detail?product_id=14815

Archived Xiaomi CyberDog GitLab Project

https://partner-gitlab.mioffice.cn/groups/cyberdog/-/archived

Clone all the repos with the following commands

git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_tina_sdk.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_drivers_gd_bin.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_locomotion_bin.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_cyberdog.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_kernel.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_vision.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_assistant.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_automation.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_repos.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_lcm_type.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/athena_drivers_st.git
git clone https://partner-gitlab.mioffice.cn/cyberdog/build_extra.git

Active GitHub Project

https://github.com/MiRoboticsLab/cyberdog_ros2
https://github.com/MiRoboticsLab/cyberdog_motor_sdk
https://github.com/MiRoboticsLab/cyberdog_tegra_kernel
https://github.com/MiRoboticsLab/cyberdog_ros2/wiki

English Wiki

https://github.com/MiRoboticsLab/cyberdog_ros2/blob/main/README_EN.md
https://github.com/MiRoboticsLab/cyberdog_ros2/wiki/铁蛋ROS-2软件架构-%7C-ROS-2-Software-Architecture-of-CyberDog#english

Discussion

Telegram group in Announcements: https://telegram.me/cyberdog_mi

OTA updates

https://github.com/MiRoboticsLab/cyberdog_ros2/discussions
MiRoboticsLab/cyberdog_ros2#133

CyberDog Engineering Exploration Edition forum

https://www.xiaomi.cn/board/27817860

Xiaomi Phone Home

You can occasionally see the athena_audio process in the SYN_SENT state connecting to 47.241.92.41 on https port.

This appears to be connection to access.speech.ai.xiaomi.com

mi@lubuntu:/opt/ros2/cyberdog/data$ cat audio_debug.toml 
title = "audio_debug_config"
config_audio_force_enable = 0
config_audio_dump_raw = 0
config_audio_dump_asr = 0
config_audio_silence = 0
config_audio_testtoken = 0
testtoken_access = <snip>
testtoken_refresh = <snip>
testtoken_deviceid = <snip>

The token further supports this

$ cat token.json  | jq
{
  "censored_DO-TOKEN-V1_access.speech.ai.xiaomi.com-WIFI-mioffice-5g": 
"{\"dns\":[\"47.241.176.221:80\",\"47.241.176.221:443\"],\"expire_at\":1660787428}",
  "censored_DO-TOKEN-V1_aes_key_info": "{\"aes_key\":\"xxxxxx\"}",
  "censored_DO-TOKEN-V1_rsa_key_info": "{\"key_id\":\"xxxxx\",\"public_key\":\"-----BEGIN PUBLIC KEY-----\\ncensored
PUBLIC KEY-----\\n\",\"expire_at\":1672815028000}",
  "censored_DO-TOKEN-V1_token_info": 
"{\"access_token\":\"default\",\"expire_at\":1662774605,\"refresh_at\":1661753376,\"refresh_token\":\"default\"}",
  "censored_DO-TOKEN-V1_updated_at": "1660182605",
  "auto_ping_interval": null,
  "cloud_control_link_wss": "false",
  "cloud_control_version": "72",
  "next_cloud_control_interval": "120",
  "next_cloud_control_time": "1660186210",
  "next_hijack_detect_at": "1660441565",
  "wss_expire_at": null
}

This API is used to phone home for the Siri like audio "Home Assistant" functionality
https://developers.xiaoai.mi.com/documents/Home?type=/api/doc/render_markdown/SkillAccess/skill/fulu/PrivacyInfo

The SDK in play is: https://cdn.cnbj2m.fds.api.mi-img.com/cyberdog-package/packages/xiaoai_sdk_1.0.0.8.2.tar.xz

Home Assistant voice commands

Uses Cuda Deep Neural Network cuDNN
https://developer.nvidia.com/cudnn
https://docs.nvidia.com/deeplearning/nemo/user-guide/docs/en/stable/asr/asr_language_modeling.html (ASR)
https://docs.nvidia.com/deeplearning/nemo/user-guide/docs/en/stable/asr/speech_classification/models.html (VAD)

https://docs.nvidia.com/deeplearning/nemo/user-guide/docs/en/stable/core/core.html
NeMo comes with many pretrained models for each of our collections: ASR, NLP, and TTS.

$ ls /opt/ros2/cyberdog/ai_conf/
dnn_vad_model  dnn_we_model  hot_query_robotcontroller.txt  k91.fst  model.bin  vad_config.json  xaudio_engine.conf  xaudio_vpm_ut

The audio_assistant source gives more clues about how things work.
https://partner-gitlab.mioffice.cn/cyberdog/athena_assistant/-/tree/devel/audio_assistant/src

./audio_assistant/src/ai_asr_native.cpp:#define    ASR_MODEL_BIN  "/opt/ros2/cyberdog/ai_conf/model.bin"
./audio_assistant/src/ai_keyword.cpp:#define VPM_CONFIG_FILE_PATH "/opt/ros2/cyberdog/ai_conf/xaudio_engine.conf"
./audio_assistant/src/ai_asr_native.cpp:  std::string name = "k91";

The VPM config file also gives some hints

mi@lubuntu:/opt/ros2/cyberdog/ai_conf$ cat xaudio_engine.conf
[engine opt]
version = K91_v1.0.0_8-20210810;
[wakeup opt]
model_path = /opt/ros2/cyberdog/ai_conf/wakeup_model.bin;
version = kws_tdtd_model_6.0-20210731;
[vad opt]
model_path = /opt/ros2/cyberdog/ai_conf/;
version = model-hires-0605-210709;
timeout_num = 600;
[dnn vad opt]
dnn_vad_model_path = /opt/ros2/cyberdog/ai_conf/dnn_vad_model;
dnn_we_model_path = /opt/ros2/cyberdog/ai_conf/dnn_we_model;

hot_query_robotcontroller.txt contains the gramatical structure for the recognized voice commands.

If you split each line in the file by ":" you can get an idea of the voice commands. They line up with what is in the manual

(^(旺财旺财|请|麻烦|给我)?(站)?起来(啊)?$|^(给我)?起立$)	旺财，旺财，站起来	robotControl	"resp"

^(请|旺财|麻烦|给我|表演一下)?趴下去(旺财)?$	旺财，旺财，趴下去	robotControl	"resp"

^(旺财|麻烦|给我)?(过来)?过来$	旺财，旺财，过来过来	robotControl	"resp"

^(旺财|麻烦|请|给我)?后退一步$	旺财，旺财，后退一步	robotControl	"resp"

^(旺财来|麻烦|请|给我|表扬一下)?原地转圈$	旺财，旺财，原地转圈	robotControl	"resp"

(^(旺财来|麻烦|给我|表演一下|请)?(握个手|击个掌)$|^击个掌吧击个掌$)	旺财，旺财，握个手/击个掌	robotControl	"resp"

^(旺财来|麻烦|请|给我|表演一下)?后空翻$	旺财，旺财，后空翻	robotControl	"resp"

^(旺财来)?(麻烦|请|给我|表演一下)?跳个舞(吧|呗)?$	旺财，旺财，跳个舞	robotControl	"resp"

The rough English translation is below:

(^(Wang Cai Wang Cai|Please|Trouble|Give me)?(Stand)?Get up(Ah)?$|^(Give me)?Stand up $) Prosperity, Prosperity, stand up robotControl "resp"

^(Please|prosperity|trouble|give me|perform)? Get down (prosperity)?$ Prosperity, prosperous, get down robotControl "resp"

^(Wangcai|Trouble|Give me)?(Come over)?Come over $ Wangcai,Wangcai, come here robotControl "resp"

^(Wangcai|trouble|please|give me)? One step back $ Wangcai, Wangcai, one step back robotControl "resp"

^(Wangcailai|trouble|please|give me|praise)? Circling in place $ Prosperity, prosperity, circling robotControl "resp"

(^(Prosperity Come|Trouble|Give me|Show me|Please)?(Shake a hand|Clap)$|^Clap, give a slap$) Prosperity, prosperity, shake hands/hit A palm robotControl "resp"

^(Wangcailai|trouble|please|give me|show it)? Backflip $ Prosperity, Prosperity, Backflip robotControl "resp"

^(Prosperity is coming)?(Trouble|please|show me|perform)? Dance (bar|chan)?$ Prosperity, prosperity, dance robotControl "resp"

"Wang Cai" is supposed to be "Iron Egg" which you can tell from the "CyberDog voice commands" section of the manual.

Wake word: "iron egg iron egg" instruction: "take a step back", "stand up", "get down", "dance", "shake hands", "turn around"

The "backflip" instruction seems to be disabled, even though shown in marketing.
https://www.youtube.com/watch?v=Jj95byxQCeU

This non CyberDog specific discussion on adding custom Xiaomi wakeup words has some overlap with the above info
https://bbs.hassbian.com/archiver/?tid-5649.html&page=1

STP file for accessory mounting

https://cdn.cnbj2m.fds.api.mi-img.com/cyberdog-package/packages/doc_materials/cyber_dog_body.stp

GRPC remote control

https://github.com/Karlsx/CyberDog_Ctrl

Wav files for dog sound effects

https://cdn.cnbj2m.fds.api.mi-img.com/cyberdog-package/packages/CyberDog_wavs.tar.xz

Bluetooth remote support

The CyberDog appears to use a custom Bluetooth T8S by RadioLink. It includes a cell phone holder as the main difference between the T8S(BT)
http://www.radiolink.com.cn/docc/index.html
http://radiolink.com.cn/doce/product-detail-167.html
The "FPV Monitor Holder" is also included
https://www.aliexpress.com/item/2255800731743329.html
https://www.amazon.com/ATA-HOBBY-Transmitter-Controller-Accessories/dp/B09Z5F798W
https://www.amazon.com/Radiolink-Controller-Receiver-Transmitter-Gamepad/dp/B07WR9Y1HG
If you buy your own, you'll need to center the throttle stick
https://www.youtube.com/watch?v=4_FrGGzbxiE

Usage

Open the App... go to settings, go to Remote Control Connection. 

action gait, send combination key from CH5 and CH7, when Key CH6 pressed
gait range: 1~4, 7~11, when ch6 pressed

https://github.com/MiRoboticsLab/cyberdog_ros2/blob/main/cyberdog_interaction/cyberdog_wireless/bluetooth/bluetooth/remote.py

-------------------------------------
Roller - Ch8 (height)
-------------------------------------
Left - Ch7  | Right - Ch5  | Mode
-------------------------------------
Center      | Center       | Trot
Center      | Down         | Slow Trot
Center      | Up           | Fly Trot
Down        | Center       | Kneel
Down        | Down         | Down
Down        | Up           | Recover 
Up          | Center       | Bound
Up          | Down         | Recover
Up          | Up           | Show Atti
--------------------------------------

Services on dog for control

The services are enabled by default:

/opt/ros2/cyberdog/lib/python3.6/site-packages/bluetooth/gattserver.py:enableAutoRemoteControl: bool = True  # for bluetooth remote control handle auto connect<br>

The following binaries support the remote control

mi@lubuntu:/opt$ grep btRemoteCommand . -r
Binary file ./ros2/cyberdog/lib/athena_cyberdog_app/app_server matches
Binary file ./ros2/cyberdog/lib/libapp_server_core.a matches
Binary file ./ros2/cyberdog/lib/python3.6/site-packages/bluetooth/__pycache__/remote.cpython-36.pyc matches

https://github.com/MiRoboticsLab/cyberdog_ros2/blob/011025c2ee43a144f32f42440b631019124a731b/cyberdog_interaction/cyberdog_wireless/bluetooth/bluetooth/remote.py https://github.com/MiRoboticsLab/cyberdog_ros2/blob/011025c2ee43a144f32f42440b631019124a731b/cyberdog_interaction/cyberdog_wireless/bluetooth/bluetooth/gattserver.py#L36

Launched by ROS2 gattserver

root@lubuntu:/home/mi# ps -ax | grep gat
 4628 ?        Ss     0:01 /usr/bin/python3 /opt/ros2/foxy/bin/ros2 run bluetooth gattserver
 5755 ?        Sl     0:07 /usr/bin/python3 /opt/ros2/cyberdog/lib/bluetooth/gattserver

When the service starts the following log entries are created.

2022-07-30 12:44:01,744 - gattserver.py[line:1006] - INFO: main: init
2022-07-31 06:39:29,957 - gattserver.py[line:253] - INFO: add service: <dbus._dbus.SystemBus (system) at 0x7f9dde60a0>
2022-07-31 06:39:29,958 - gattserver.py[line:263] - INFO: add_service: <bluetooth.gattserver.RobotService at /org/bluez/example/service0 at 0x7f9dde2c50>
2022-07-31 06:39:31,537 - gattserver.py[line:232] - INFO: get psn is:b'P21511906GR00152ZM\n'
2022-07-31 06:39:31,541 - gattserver.py[line:1046] - DEBUG: main: set bleStatus BLE_STATUS_NONE -> BLE_STATUS_ADV
2022-07-31 06:39:31,542 - gattserver.py[line:930] - INFO: RegADV: RegisterAdvertisement
2022-07-31 06:39:31,543 - gattserver.py[line:942] - INFO: RegATT: RegisterApplication
2022-07-31 06:39:31,543 - gattserver.py[line:258] - INFO: get_path: <bluetooth.gattserver.RobotApplication at / at 0x7f9dde2c88>
2022-07-31 06:39:31,548 - gattserver.py[line:1050] - DEBUG: main init and send audio cmd BOOT_COMPLETE
2022-07-31 06:39:31,564 - gattserver.py[line:1053] - DEBUG: RegADV: BT enable adv, set LED_BT_ADV
2022-07-31 06:39:31,607 - gattserver.py[line:760] - INFO: register_app_cb: GATT application registered!!!
2022-07-31 06:39:31,609 - gattserver.py[line:204] - INFO: GetAll
2022-07-31 06:39:31,609 - gattserver.py[line:207] - INFO: returning props
2022-07-31 06:39:31,618 - gattserver.py[line:771] - INFO: register_ad_cb: Advertisement registered!!!


2022-07-30 12:08:34,895 - remote.py[line:863] - INFO: startAutoConnect: get autoConThreadRunning is 0
2022-07-30 12:08:34,899 - remote.py[line:872] - INFO: startAutoConnect: waiting 10 seconds for start
2022-07-30 12:08:34,902 - gattserver.py[line:978] - DEBUG: disable ADV and ATT, led send LED_BT_ADV OFF
2022-07-30 12:08:44,897 - remote.py[line:914] - INFO: autoConnection: THREAD WAITING-> ENTER
2022-07-30 12:08:44,898 - remote.py[line:920] - WARNING: auto device is null
2022-07-30 12:08:44,898 - remote.py[line:1000] - DEBUG: autoConnection: autoConThreadRunning is 0 and quit

Android App

Download link: http://cdn.cnbj1.fds.api.mi-img.com/ota-packages/apk/cyberdog_app.apk

1|gtowifi:/ # ps -ef | grep athena                                                                                                                                                                   
u0_a131      20839   433 7 18:18:44 ?     00:00:02 com.xiaomi.athena_remocons

gtowifi:/ # logcat --pid 21131                                                                                                                                                                       
--------- beginning of main
07-30 18:20:09.481 21131 21131 E athena_remocon: Not starting debugger since process cannot load the jdwp agent.

The app leaves a GRPC port open for remote control

gtowifi:/data/user/0/com.xiaomi.athena_remocons # netstat -anp  | grep athen                                                                       
tcp        0      0 10.0.0.64:46038         10.0.0.65:1935          ESTABLISHED 21131/com.xiaomi.athena_remocons
tcp6       0      0 :::8980                 :::*                    LISTEN      21131/com.xiaomi.athena_remocons
tcp6       0      0 ::ffff:10.0.0.64:8980   ::ffff:10.0.0.65:44306  ESTABLISHED 21131/com.xiaomi.athena_remocons

Files left in /data/data/com.xiaomi.athena_remocons/files/mmkv/spUtils seemingly ties the current dog mode and settings to a Xiaomi account session /data/data/com.xiaomi.athena_remocons/files/mmkv/ seems to tie the serial to the dogs settings, including the "room map"

The app forces the end user to login before being able to control the dog. The needs to be neutered.
You are also forced to read the manual, privacy policy, legal statement, etc.

Passwords and systems

Tegra: pi / 123 root / 123

Tina: root / no pass

USB Download port

L4T provides a USB bridge on the Jetson inside the dog. You can use it for IP communications, or serial
https://forums.developer.nvidia.com/t/ip-address-192-168-55-1/184273/4

$ ls -al /dev/ttyACM0 
crw-rw-rw- 1 root dialout 166, 0 Aug 16 01:20 /dev/ttyACM0
$ screen /dev/ttyACM0 115200
[screen is terminating]
$ sudo ifconfig usb0 192.168.55.100
$ ping 192.168.55.1
PING 192.168.55.1 (192.168.55.1) 56(84) bytes of data.
64 bytes from 192.168.55.1: icmp_seq=1 ttl=64 time=0.350 ms
64 bytes from 192.168.55.1: icmp_seq=2 ttl=64 time=0.321 ms
^C
--- 192.168.55.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1019ms
rtt min/avg/max/mdev = 0.321/0.335/0.350/0.014 ms

Alternately if you plug a USB adapter into the extension port, you need to edit th e/etc/netplan/01-netcfg.yaml file to get DHCP

mi@lubuntu:/etc/netplan$ sudo pico 01-netcfg.yaml
network:
  version: 2
  renderer: networkd
  ethernets:
    eth1:
      dhcp4: true
      optional: true

mi@lubuntu:/etc/netplan$ sudo netplan try 
Do you want to keep these settings?


Press ENTER before the timeout to accept the new configuration


Changes will revert in 118 seconds
Configuration accepted.
mi@lubuntu:/etc/netplan$ ifconfig eth1
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.147  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::205:1bff:fec1:c8be  prefixlen 64  scopeid 0x20<link>
        ether 00:05:1b:c1:c8:be  txqueuelen 1000  (Ethernet)
        RX packets 93  bytes 5476 (5.4 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 87  bytes 9430 (9.4 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

LED control

import rclcomm
import rclpy

https://raw.githubusercontent.com/MiRoboticsLab/cyberdog_ros2/main/cyberdog_interaction/cyberdog_led/README.md

rclpy.init(args=None)
ledClient = rclcomm.LedClientAsync()

if ledClient.check_ready():
	if ledClient.get_last_always():
		ledClient.send_request(ledClient.LED_BT_ADV,ledClient.TYPE_FUNCTION,ledClient.COMMAND_OFF)  # clean adv 
led
	else:
	#	ledClient.send_request(ledClient.LED_WIFI_CONNECT_SUCCESS,ledClient.TYPE_FUNCTION, 1000000000)
		ledClient.send_request(25,ledClient.TYPE_ALARM, ledClient.COMMAND_ALWAYSON) # SkyBlue Breath == 25

Backdoor wifi connections

mi@lubuntu:/etc/init.d$ nmcli connection show
NAME                UUID                                  TYPE      DEVICE 
DataPipe            defae6a4-944f-45b4-8d19-1a364b4f70e8  wifi      wlan0  
eth0                ee15f340-6d55-47ed-b794-39c9d63586c7  ethernet  eth0   
l4tbr0              d91c2d61-76a2-4ef1-9514-cd2d9695bbde  bridge    l4tbr0 
1234                f3ad1b24-3707-4c1a-b347-8327164b9bd8  wifi      --     
Dog2                9b9423fe-ce84-40ae-9757-9ffd15824299  wifi      --     
Dreame-test         0acd8a29-8c8c-4b9e-81cd-2d53404bf7e2  wifi      --     
Dreame-test 1       2a28484c-8323-4719-a888-4c8dc7db2e54  wifi      --     
Dreame-test 2       650c03e9-aef0-48be-b7de-1b22b863b105  wifi      --     
Dreame-test 3       39d2f37b-a38d-4cd6-9b3a-0b9249a7cec9  wifi      --     
Dreame-test 4       42370f0a-8270-42d4-8c5c-c93b26d7dc2a  wifi      --     
Dreame-test 5       14cd5bf9-6416-4744-80b1-a89693feea90  wifi      --     
Redmi               e7161e00-13d9-44f5-975b-312b53f80eec  wifi      --     
Wired connection 1  86d27518-92c1-3b91-9a7e-3b3b3cd31351  ethernet  --     
ddog1               2e3920ce-b3d3-4589-8dee-a7f18d4b6f60  wifi      --     
dog4                4fece0fb-dc5c-416f-a4c7-cde54368164c  wifi      --     
mi@lubuntu:/etc/init.d$ sudo grep -r '^psk=' /etc/NetworkManager/system-connections/
/etc/NetworkManager/system-connections/Dreame-test 2:psk=12345678
/etc/NetworkManager/system-connections/Redmi:psk=peterwu123
/etc/NetworkManager/system-connections/dog4:psk=12345678
/etc/NetworkManager/system-connections/Dreame-test:psk=12345678
/etc/NetworkManager/system-connections/Dreame-test 1:psk=12345678
/etc/NetworkManager/system-connections/Dog2:psk=123456789
/etc/NetworkManager/system-connections/Dreame-test 4:psk=12345678
/etc/NetworkManager/system-connections/1234:psk=123456789
/etc/NetworkManager/system-connections/ddog1:psk=123456789
/etc/NetworkManager/system-connections/Dreame-test 3:psk=12345678
/etc/NetworkManager/system-connections/Dreame-test 5:psk=12345678

Remote ROS connectivity.

Install Debinan binary version of foxy https://docs.ros.org/en/rolling/Installation/Alternatives/Ubuntu-Install-Binary.html

$ sudo apt-get install libzmq3-dev
$ sudo apt install python3-colcon-common-extensions
$ sudo apt-get install ros-foxy-rmw-cyclonedds-cpp
$ source /opt/ros/foxy/setup.bash

The dog uses Cyclone DDS & ROS Domain 42

$ ps -ax | grep dds -i
23620 pts/2    Sl     0:01 /usr/bin/python3 /opt/ros2/foxy/bin/_ros2_daemon --rmw-implementation rmw_cyclonedds_cpp --ros-domain-id 42

Remote listener for ROS2

The dog must be on the same network as your remote PC. Install the APK on an android phone and use "Start To Connect" and if you do not see a "Nearby CyberDog", you need to use "Quick Connect" + sign and add a dog via "Bluetooth Connection". If you don't see a dog via bluetooth, touch his head for 3 seconds until it chimes, and try again.

The github wiki gives us more detail on the actual ROS connectivity via DDS
https://github.com/MiRoboticsLab/cyberdog_ros2/wiki/CyberDog-DDS本地及多播设置

modify the config as follows:

root@lubuntu:/home/mi# grep -E 'CYCLONEDDS_URI|ROS_LOCALHOST_ONLY' /etc -r

/etc/systemd/system/cyberdog_automation.service:#Environment="ROS_LOCALHOST_ONLY=1"
/etc/systemd/system/cyberdog_automation.service:#Environment="CYCLONEDDS_URI=file:///etc/systemd/system/cyclonedds.xml"
/etc/systemd/system/cyberdog_ros2.service:#Environment="ROS_LOCALHOST_ONLY=1"
/etc/systemd/system/cyberdog_ros2.service:#Environment="CYCLONEDDS_URI=file:///etc/systemd/system/cyclonedds.xml"
/etc/systemd/system/bluetooth_ros2.service:#Environment="ROS_LOCALHOST_ONLY=1"
/etc/systemd/system/bluetooth_ros2.service:#Environment="CYCLONEDDS_URI=file:///etc/systemd/system/cyclonedds.xml"
/etc/mi/mi_config:#export ROS_LOCALHOST_ONLY=1
/etc/mi/mi_config:export CYCLONEDDS_URI=file:///etc/systemd/system/cyclonedds.xml

root@lubuntu:/home/mi# grep -E 'NetworkInterfaceAddress|AllowMulticast' /etc/systemd/system/cyclonedds.xml
            <NetworkInterfaceAddress>wlan0</NetworkInterfaceAddress>
            <AllowMulticast>true</AllowMulticast>

Reboot after making the changes. Reboot your client PC if you have any connectivity failure. DDS can be finiky!

Rviz + remote control plugin

https://www.bilibili.com/video/BV1ML4y1b78d

$ mkdir ~/cyberdog_ws/src -p
$ cd ~/cyberdog_ws/src/
$ git clone https://github.com/linzhibo/Cyberdog_rviz2_plugin.git

Set dog namespace in ./Cyberdog_rviz2_plugin/src/mission_panel.cpp

$ cd ~/cyberdog_ws/src/
$ git clone https://github.com/MiRoboticsLab/cyberdog_ros2.git
$ cd ~/cyberdog_ws/
$ colcon build
$ source install/setup.sh

To talk to the dog remotely several conditions are necessary on the client PC

export ROS_DOMAIN_ID=42
export RMW_IMPLEMENTATION=rmw_cyclonedds_cpp

You'll know it works when you can enable the cam from the remote PC

kfinisterre@dev0:~$ ros2 service call /mi1036871/camera/enable std_srvs/SetBool "{data : True}"
waiting for service to become available...
requester: making request: std_srvs.srv.SetBool_Request(data=True)

response:
std_srvs.srv.SetBool_Response(success=False, message='Device is already ON.')

Next launch rviz

$ rviz2

To ensure this works at next login, add the following to ~/.bashrc

source /opt/ros/foxy/setup.bash
export RMW_IMPLEMENTATION=rmw_cyclonedds_cpp
export ROS_DOMAIN_ID=42
source ~/cyberdog_ws/src/install/setup.sh

It has been observed that after disconnection of DDS, sometimes the PC client is unable to re-connect until the dog is rebooted. Issues like this may be related: ros2/rmw_cyclonedds#74. It may be possible to use trace to debug this issue: https://cyclonedds.io/content/guides/tracefile.html

We can do this by adding the following to /etc/systemd/system/cyclonedds.xml between the tags

        <Tracing>
            <Verbosity>config</Verbosity>
            <OutputFile>cdds.log.${CYCLONEDDS_PID}</OutputFile>
        </Tracing>

Logs will be left in /home/mi

mi@lubuntu:~$ head  cdds.log.7860 
1663102587.967364 [42]       ros2: config: Domain/General/NetworkInterfaceAddress/#text: wlan0 {1}
1663102587.967482 [42]       ros2: config: Domain/General/MulticastRecvNetworkInterfaceAddresses/#text: preferred {}
1663102587.967509 [42]       ros2: config: Domain/General/ExternalNetworkAddress/#text: auto {}
1663102587.967528 [42]       ros2: config: Domain/General/ExternalNetworkMask/#text: 0.0.0.0 {}
1663102587.967549 [42]       ros2: config: Domain/General/AllowMulticast/#text: true {1}
1663102587.967597 [42]       ros2: config: Domain/General/PreferMulticast/#text: false {}
1663102587.967615 [42]       ros2: config: Domain/General/MulticastTimeToLive/#text: 32 {}
1663102587.967635 [42]       ros2: config: Domain/General/DontRoute/#text: false {}
1663102587.967653 [42]       ros2: config: Domain/General/Transport/#text: udp {}
1663102587.967703 [42]       ros2: config: Domain/General/EnableMulticastLoopback/#text: true {}

Hotspot Wifi

To enable:

mi@lubuntu:~$ sudo su 

root@lubuntu:/home/mi# nmcli dev wifi hotspot ifname wlan0 ssid test password "test1234"
Device 'wlan0' successfully activated with 'e2898ed9-cce4-4926-9bca-cf4fb32020e8'.

root@lubuntu:/home/mi# nmcli con show Hotspot | grep autoconnect
connection.autoconnect:                 no
...

root@lubuntu:/home/mi# nmcli con mod Hotspot connection.autoconnect yes
root@lubuntu:/home/mi# nmcli con show Hotspot | grep autoconnect
connection.autoconnect:                 yes
...

root@lubuntu:/home/mi# reboot

Your adapter will come up with the default network manager address. This address is hardcoded into network manager src/nm-device.c https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1098362

root@lubuntu:/home/mi# ifconfig wlan0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.42.0.1  netmask 255.255.255.0  broadcast 10.42.0.255
        inet6 fe80::2257:9eff:fe79:df4f  prefixlen 64  scopeid 0x20<link>
        ether 20:57:9e:79:df:4f  txqueuelen 1000  (Ethernet)
        RX packets 2779  bytes 14962490 (14.9 MB)
        RX errors 0  dropped 3  overruns 0  frame 0
        TX packets 2088  bytes 14971817 (14.9 MB)
        TX errors 0  dropped 1 overruns 0  carrier 0  collisions 0

You should be able to ping any client that connects at this point. You'll find any connected hosts in the leases file.

root@lubuntu:/home/mi# cat /var/lib/misc/dnsmasq.leases
1663085613 ea:2c:f8:2d:db:ce 10.42.0.12 * 01:ea:2c:f8:2d:db:ce

root@lubuntu:/home/mi# ping -c 3 10.42.0.12
PING 10.42.0.12 (10.42.0.12) 56(84) bytes of data.
64 bytes from 10.42.0.12: icmp_seq=1 ttl=64 time=7.27 ms
64 bytes from 10.42.0.12: icmp_seq=2 ttl=64 time=3.24 ms
64 bytes from 10.42.0.12: icmp_seq=3 ttl=64 time=4.34 ms

--- 10.42.0.12 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 3.247/4.956/7.273/1.699 ms

Next you must enable the app to work. You'll need to make a Bluetooth connection to tell the dog to connect to itself. On the "Quick Connect" screen, click the "+" sign. Choose the Dog SN to connect. Then choose the "Network connectin". In this case we'll literally tell the dog to connect to itself. Choose the "test" Access Point that is created with our Network Manager hotspot setup above.

To disable the hotspot:

mi@lubuntu:~$ sudo su 
root@lubuntu:/home/mi# nmcli connection delete Hotspot
Connection 'Hotspot' (e2898ed9-cce4-4926-9bca-cf4fb32020e8) successfully deleted.

Dreame involvement?

"At the end of 2017, Dreame joined the Xiaomi Ecological Chain, as the driving force and leading enterprise of smart household cleaning appliances."
https://global.dreametech.com/pages/brand-story

I noticed that there is realdime dreame mapping support that seems identical to the Xiaomi implementation on the dog
https://github.com/PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor

On the dog Linux you can see dreame refrences, the first is in the wifi backdoors. The second is in the ros packages

mi@lubuntu:~$ grep dreame /opt/ -ri
/opt/ros2/cyberdog/share/chassis_node/package.xml:  <maintainer email="yangbowei@dreame.tech">ybw</maintainer>
/opt/ros2/cyberdog/share/ov_msckf/package.xml:  <author email="yangsheng@dreame.tech">yangsheng</author>
/opt/ros2/cyberdog/share/interactive/package.xml:  <maintainer email="chenshaojie@dreame.tech">csj</maintainer>

You can see Dreame refrences on the Tina linux instance.

mi@lubuntu:~$ ssh root@192.168.55.233
Warning: Permanently added '192.168.55.233' (RSA) to the list of known hosts.


BusyBox v1.27.2 () built-in shell (ash)

 _____  _              __     _
|_   _||_| ___  _ _   |  |   |_| ___  _ _  _ _
  | |   _ |   ||   |  |  |__ | ||   || | ||_'_|
  | |  | || | || _ |  |_____||_||_|_||___||_,_|
  |_|  |_||_|_||_|_|  Tina is Based on OpenWrt!
 ------------------------------------------------
 Tina Linux (Neptune, 5C1C9C53)
 ------------------------------------------------
 请输入help指令,获取系统帮助
 ------------------------------------------------
 please enter the help command to get system help
 ------------------------------------------------
root@TinaLinux:~# cd /robot
root@TinaLinux:/robot#  strings manager | grep Dreame -i 
dreame_state
100 DREAME SERVER HELLO
root@TinaLinux:/robot# grep dreame . -ri
./manager:dreame_state
./manager:100 DREAME SERVER HELLO
./manager_config/sub-project/imu_online_calib/imu_online_calibrate:St23_Sp_counted_ptr_inplaceIN9DreameDog4User14MessageHandlerESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE
./manager_config/sub-project/imu_online_calib/imu_online_calibrate:NSt6thread11_State_implISt12_Bind_simpleIFSt7_Mem_fnIMN9DreameDog4User14MessageHandlerEFbvEEPS5_EEEE

Useful Repos

https://github.com/Karlsx/CyberDog_Ctrl - grpc control
https://github.com/Sunshengjin/ds4_for_cyberdog - PS4 specific joystick support
https://github.com/cyh1231wp/cyberdog-joystick - generic bluetooth joystick support
https://github.com/sraccah/CyberDog_42 - GRPC based control, and voice support
https://github.com/linzhibo/Cyberdog_utils - Centroid follower example
https://github.com/zbwu/cyberdog_misc - includes bits of the motion controller (locomotion wrapper)
https://github.com/zbwu/athena_motorcontrol
https://github.com/zbwu/athena_locomotion
https://github.com/zbwu/athena_adapter
https://github.com/zbwu/GD32_SPINE
https://github.com/PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor

Fixing rosdep

rosdep is broken

mi@lubuntu:~/cyberdog_ws$ rosdep
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 568, in _build_master
    ws.require(__requires__)
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 886, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 777, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.VersionConflict: (rosdep 0.22.1 (/home/mi/.local/lib/python3.6/site-packages), Requirement.parse('rosdep==0.20.0'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/rosdep", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 3242, in <module>
    @_call_aside
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 3226, in _call_aside
    f(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 3255, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 570, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 583, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/local/lib/python3.6/dist-packages/pkg_resources/__init__.py", line 772, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'rosdep==0.20.0' distribution was not found and is required by the application

You can fix it like this

mi@lubuntu:~/cyberdog_ws$ sudo update-alternatives --install /usr/bin/python python /usr/bin/python2.7 1
mi@lubuntu:~/cyberdog_ws$ sudo update-alternatives --install /usr/bin/python python /usr/bin/python3.6 2

mi@lubuntu:~/cyberdog_ws$ update-alternatives --list python
/usr/bin/python2.7
/usr/bin/python3.6


mi@lubuntu:~/cyberdog_ws$ sudo update-alternatives --config python
There are 2 choices for the alternative python (providing /usr/bin/python).

  Selection    Path                Priority   Status
------------------------------------------------------------
* 0            /usr/bin/python3.6   2         auto mode
  1            /usr/bin/python2.7   1         manual mode
  2            /usr/bin/python3.6   2         manual mode

Press <enter> to keep the current choice[*], or type selection number: 1

mi@lubuntu:~/cyberdog_ws$ sudo rosdep init
Wrote /etc/ros/rosdep/sources.list.d/20-default.list
Recommended: please run

	rosdep update

mi@lubuntu:~/cyberdog_ws$ sudo rosdep update
reading in sources list data from /etc/ros/rosdep/sources.list.d
Warning: running 'rosdep update' as root is not recommended.
  You should run 'sudo rosdep fix-permissions' and invoke 'rosdep update' again without sudo.
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml
Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index-v4.yaml
Skip end-of-life distro "ardent"
Skip end-of-life distro "bouncy"
Skip end-of-life distro "crystal"
Skip end-of-life distro "dashing"
Skip end-of-life distro "eloquent"
Add distro "foxy"
Add distro "galactic"
Skip end-of-life distro "groovy"
Add distro "humble"
Skip end-of-life distro "hydro"
Skip end-of-life distro "indigo"
Skip end-of-life distro "jade"
Skip end-of-life distro "kinetic"
Skip end-of-life distro "lunar"
Add distro "melodic"
Add distro "noetic"
Add distro "rolling"
updated cache in /home/mi/.ros/rosdep/sources.cache

You can see it works

mi@lubuntu:~/cyberdog_ws$ sudo rosdep fix-permissions
Recursively changing ownership of ros home directory '/home/mi/.ros' to 'mi:mi' (current user)...
Done.
mi@lubuntu:~/cyberdog_ws$  rosdep install -i --from-path src --rosdistro foxy -y
#All required rosdeps installed successfully

About

小米集团 XIaomi 铁蛋 CyberDog 仿生四足机器人 Bionic quadruped robot

Resources

Readme
Activity

Stars

23 stars

Watchers

4 watching

Forks

10 forks
Report repository

Releases

No releases published

Packages