microsoft / microsoft/pxt-microbit

Provide virtual servo in simulator for block servo set pulsepin

Open
#4,063 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

apis Simulator
Dominant language
TypeScript
Stars
804
Forks
721
Avg merge
2d 9h
Merged PRs (30d)
2

Description

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Unlike for the block servo write pin, that shows a virtual servo in the simulator, there is no representation of a servo for the "servo set pulsepin (us) block.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Could a representation of a servo be added to the "servo set pulsepin (us) block, please.

Perhaps some lower (500us) and upper (2500us) bounds would also need applying.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

An alternative would be to provide a new block to show the "set" pulse value e.g. keep keep exisitng block unchanged and have new block say "servo write pulsepin".

Additional context
Add any other context or screenshots about the feature request here.

Showing a servo in the simualtor for this bloack would be useful for defining a custom range for various servos and also be more relavent to speed determination when using continuous servos.

Providing such a feature would make the the block much more useful to explore realtionship between native pulse width to angle.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names the servo set pulsepin (us) block and its simulator representation, but provides no files or tests. Start by locating that block's simulator implementation and comparing it with the servo write pin block. Done means the simulator shows a servo for this block and supports the requested pulse-width range behavior, including the proposed 500–2500us bounds if appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.