I recently updated my Robomaster S1's firmware from 00.06.0300 to 00.06.0518, because the function for getting the chassis' relative position in Python always returned 0, and I thought updating would fix it.

The SDK hack that was installed stopped working, so I installed it again with instructions from this post: https://forum.dji.com/forum.php?mod=viewthread&tid=212767

Currently, I can run my Python script (that just connects to the robot and prints the version) once or twice, but a few seconds after running it the first time, the hack seems to stop working. Restarting the robot fixes it until I run the script again.


Running this example script (https://github.com/dji-sdk/RoboMaster-SDK/blob/master/examples/plaintext_sample_code/RoboMasterEP/connection/network/usb_connection.py) works for a maximum of 5 times if I run it in succession very quickly. Then it stops working.


Here's the output of running that script multiple times. I added ==== between every time I run the script for clarity:


Connection successful
send data to robot   : command
recv data from robot : b'ok;'
send data to robot   : version ?
recv data from robot : b'version 00.00.00.70;'
send data to robot   : quit
recv data from robot : b'ok;'

===================================================
Connection successful
send data to robot   : command
recv data from robot : b'ok;'
send data to robot   : version ?
recv data from robot : b'version 00.00.00.70;'
send data to robot   : quit
recv data from robot : b'ok;'
===================================================
Connection successful
send data to robot   : command
recv data from robot : b'ok;'
send data to robot   : version ?
recv data from robot : b'version 00.00.00.70;'
send data to robot   : quit
recv data from robot : b'ok;'
===================================================
Connection successful
send data to robot   : command
recv data from robot : b'ok;'
send data to robot   : version ?
recv data from robot : b'version 00.00.00.70;'
send data to robot   : quit
recv data from robot : b'quit sdk mode failed;'
===================================================
Connection successful
send data to robot   : command
recv data from robot : None
send data to robot   : version ?
recv data from robot : None
send data to robot   : quit
recv data from robot : None

===================================================

As you can see, the last time it just stops working and I need to restart my robot. All of this worked before the firmware update.

What is happening here? How can I fix this?

The SDK stopping to work due to a firmware update is expected. usually re-applying it should be enough to get it to work again but it is a hack and, as such, is not guaranteed to work. It is specially not guaranteed to work on a firmware I never tested it with.

BGA Posted at 4-10 15:59
The SDK stopping to work due to a firmware update is expected. usually re-applying it should be enough to get it to work again but it is a hack and, as such, is not guaranteed to work. It is specially not guaranteed to work on a firmware I never tested it with.

Is there anything I can do to help troubleshoot this issue? Any logs I could view using adb?

zjeffer Posted at 4-17 10:01
Is there anything I can do to help troubleshoot this issue? Any logs I could view using adb?

Unfortunately I am too busy to be able to help with this for the foreseeable future. Your best best is to try to figure it out yourself.

Hi there,

I grabbed the files with the fix for the Plaintext protocol from my EP Core model with latest firmware.
I also modified the hack to make it work on the S1.

If you are interested in, I can make it public on GitHub in the next days.

Greetings

Vinz1911 Posted at 6-20 12:50
Hi there,

I grabbed the files with the fix for the Plaintext protocol from my EP Core model with latest firmware.

Yes, please publish it. Thanks!

Here we go

DJI Forum S1 Hack

Vinz1911 Posted at 2022-6-21 06:20
Here we go

DJI Forum S1 Hack

need help...