Is your feature request related to a problem? Please describe.
Need LED support.

Describe the solution you'd like
Set LED write block.

Describe alternatives you've considered
Rewrite LED support library.

Additional context
See KK extension.

Is your feature request related to a problem? Please describe.
Students get really confused between 180 / 360 motors.

Describe the solution you'd like
Distinction between 180/360 degrees servo motors:

• 180 degree motors should allow angle change.
• 360 degree motors should allow only states MOVE_FORWARD/STOP/MOVE_BACKWARD.

Describe alternatives you've considered
N/A.

Additional context
Different vendors for the 360 motors may have different implementations for the motors.

Describe the bug
LEDs do not work when firmware upgraded from Windows 10 machines, but the same firmware does work when uploaded from macOS machines.

To Reproduce
Upload from Windows 10 machines.

Expected behavior
Uniform behaviour.

Screenshots
N/A.

Desktop (please complete the following information):

• OS: Windows
• Version 10

Additional context
Suspected to be firmware-related.

this is a wrapper of the srevo angle but has the pin already in. The user selects servo1 and it points to pin 11 and servo2 goes to pin 10

I am not sure if it's my installation but right now it shows "read analog A(0)" . This should be replaced by Read Sensor ( ) , allowing to select from 1 to 4

-nice to have-

It would be interesting to explore why the capacitive sensing doesn't work: https://github.com/PaulStoffregen/CapacitiveSensor/blob/master/CapacitiveSensor.h

if it works, we could add a block that says "touch"

Either "DIGITAL" block with 2 options (sensor1/2/3/4) and OUT/IN, or 8 blocks that say digitalRead digitalWrite with the right pin number (13, 12, 5, 6)

Is your feature request related to a problem? Please describe.
Some students are not familiar with en-US locale and would like zh_CN locale.

Describe the solution you'd like
Add block locale translations.

Describe alternatives you've considered
N/A.

Additional context
N/A.

initial code should just address pin3 for the buzzer.

conflict with IRreceive, something to consider when we start using remote control. Code should have something like:

void playTone(int tone, int duration) {
for (long i = 0; i < duration * 1000L; i += tone * 2) {
digitalWrite(speakerPin, HIGH);
delayMicroseconds(tone);
digitalWrite(speakerPin, LOW);
delayMicroseconds(tone);
}
}

I found today "knob" was not working. It's possible it was that particular board. Could we double check?

returns distance in cm