I have a StickC Plus with a working program on it, but i lost the source file.
Is there a way to read a blockly/python script from a Core device?

1. I assume the python source code is on the Core Device and being run through a MicroPython interpreter.
   Is that correct, or is the Soruce being compiled down to something else before it is downloaded to the Core?

2. Assuming 1. is correct, is there a way to read back the python script?
   (appart from reading it back directly from the flash chip with a programmer and extracting from there)

I miss some descriptions and/or a schematic, to understand details of JoyC:

1. Which pins from the StickC are used by the JoyC, which are available for other purposes?
   (I guess only 2 pins are used for SDA/SCL, so one should be available)

2. Also, i wonder what the Battery on JoyC does. Does it power the stick, or does it only drive the JoyC?

3. What is the switch doing?
   I can see that the led's are turned on and off, but does it also have other effects?

@m5stack could you provide Examples for the Servo?
I am mainly interested in having it in an Arduino example, but also for UiFlow.
Something that shows how the angle and pulse commands (angle is self explaining, but pulse less so).
Maybe this could be added to the existing examples?
In the Docs, i don't see much about the Claw, except the register description.

@zano

Thank you very much for reply , is there any instructions or tutorial how to compile the icon.c image array into the file and compile time , i would be thankfull .
Best Regards .
A workaround is to just copy the contents of icon.c into the main script where the include-line was.
So, overwriting the include-line with the contents of the file that was meant to be included.

I thought it would be enough to have icon.c in the same folder as the main script, but it was not fould that way for me.
Pasting into the main File is not the intended way to do it, so can anyone tell how includes are meant to work here?
I am pretty sure the path of the main script is normally working for include commands...

The two Sticks on the Board lock in place if you throttle the stick to the limit, and only jump back to zero if you help them.
Can this lock-feature be disabled somehow? Because for me, it's a Bug right now.
The obvious solution is to add some kind of mechanical stop, eg. elevate the existing led-cover, so the stick can't reach the lock position.
I need to get some spacers and longer screws for that.
But i wonder if there's another way, which i am overlooking. Something simple like removing/turning a screw/knob or so...
The shop- and doc- page don't mention the locking-feature at all, is it actually a bug, and not a feature?

I try to compile the code from https://github.com/m5stack/M5StickC-Plus/blob/master/examples/KIT/JoyC_%26_RoverC/Master/Master.ino
under Arduino: 1.8.19 (Windows 10), Board: "M5Stick-C-Plus, Default, 1500000, None"
But i get an error:

RoverC:88:23: error: 'I2C_ERROR_NO_BEGIN' was not declared in this scope

 uint8_t IIC_ReState = I2C_ERROR_NO_BEGIN;

                       ^~~~~~~~~~~~~~~~~~

C:\Users\toro\Documents\Arduino\RoverC\RoverC.ino:88:23: note: suggested alternative: 'ESP_ERR_NO_MEM'

 uint8_t IIC_ReState = I2C_ERROR_NO_BEGIN;

                       ^~~~~~~~~~~~~~~~~~

                       ESP_ERR_NO_MEM

The answer is in the error, following the suggestion fixes the error.

Now, besides that it works i have no idea if the replacement is correct logically. The Const-Names suggest yes, but there might be more to it...
If the replacement is universally ok, should a github pull request be made?

EDIT:
There is an error/warning thrown that i had overlooked.
So, just doing the replacement seems like not enough...

RoverC.ino.cpp:1:
...\AppData\Local\Arduino15\packages\m5stack\hardware\esp32\2.0.2/
tools/sdk/esp32/include/esp_common/include/esp_err.h:31:37: 
warning: unsigned conversion from 'int' to 'uint8_t' {aka 'unsigned char'} changes value from '257' to '1' [-Woverflow]
 #define ESP_ERR_NO_MEM              0x101   /*!< Out of memory */
                                     ^~~~~
...\Arduino\RoverC\RoverC.ino:88:23: note: in expansion of macro 'ESP_ERR_NO_MEM'
 uint8_t IIC_ReState = ESP_ERR_NO_MEM;
                       ^~~~~~~~~~~~~~

When I got the Rover, only one wheel did turn with the slow moving example.
After I sprayed some contact clean into the gears, and let them run full speed for a while, they started to move.
But one wheel is still struggling.
Is this a known issue?
Any ideas to resolve it?

What's the purpose of- and valid values for- the set-pulse commands?

The docs only tell about motor speed taking values -127 to +127