microsoft / pxt-adafruit

Microsoft MakeCode editor for Adafruit Circuit Playground Express

MakeCode for Adafruit Circuit Playground Express

This repo contains the editor hosted at https://makecode.adafruit.com .

• (optional) install Visual Studio Code

Local server setup

This setup gives you a local version of the editor and the ability to load packages from your machine. This is the setup to develop new packages.

Setup

• install Node.js 8+
• clone https://github.com/Microsoft/pxt-adafruit to pxt-adafruit folder
• go to pxt-adafruit and run

npm install

Don't forget to periodically git pull and npm install to get the latest changes.

Launching the server

This command launches a local web server. Note that this web server is meant for development purposes only. It was not designed or secured to be run on a web server.

npm run serve

Creating and editing a package

• go to /projects under the pxt-adafruit folder
• clone your package repo, say pxt-helloworld
• launch the server with npm run serve from the pxt-adafruit folder using npm serve
• create a new project
• go to project settings and click on Edit settings as text
• add an entry in the dependency section that points to your project

    "dependencies": {
        "circuit-playground": "*",
        "helloworld": "file:../pxt-helloworld"
    },

• click on the Blocks icon to reload the blocks.

Once this project is setup, simply reload the editor after making changes on disk.

Local Dev setup

This setup is needed if you plan to make changes in PXT itself. In most cases, it's a bit of an overkill if you are building a package for the Adafruit editor.

• install Node.js 8+
• install the PXT command line

npm install -g pxt

In a common folder,

• clone https://github.com/Microsoft/pxt to pxt folder
• clone https://github.com/Microsoft/pxt-common-packages to pxt-common-packages folder
• clone https://github.com/Microsoft/pxt-adafruit to pxt-adafruit folder
• go to pxt and run

npm install
npm run build

• go to pxt-common-packages and run

npm install
npm link ../pxt

• go to pxt-adafruit and run

npm install
npm link ../pxt
npm link ../pxt-common-packages

to run the local server

From root github folder,

cd pxt-adafruit
pxt serve

to build and deploy a single package via command line

cd libs/core
pxt deploy

License

MIT

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.

Trademarks

MICROSOFT, the Microsoft Logo, and MAKECODE are registered trademarks of Microsoft Corporation. They can only be used for the purposes described in and in accordance with Microsoft’s Trademark and Brand guidelines published at https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/general.aspx. If the use is not covered in Microsoft’s published guidelines or you are not sure, please consult your legal counsel or MakeCode team ([email protected]).

pxt-adafruit's Issues

Highlight simulator buttons/pins used in programs

Similar to how we add controls depending on the APIs that are hit (light sensor, temp, etc.), we should also be highlighting the pins and buttons that are referenced in the code. Or greying out the others.

On Button Click

Hey guys, can we default this block to show the Left button instead of Pin? Left/Right buttons are super important to be discoverable. I'm almost thinking we should have separate blocks for Pins vs. Buttons vs. Switch... even though I know they act the same, it would be easier for students.

Missing categories and colorization in monaco

For some reason the input APIs don't show up in the Monaco toolbox. Syntax coloring doesn't seem to work on them either.

Show values being output on pins

Pins should get a gradient and indicate what value is being written to them

fixed instance blocks are not sorted properly

Under input, button events should be on top (weight = 99)

Show Fahrenheit temp in simulator

Simulator only allows you to pick temperature in Celsius

reduce memory pressure of neopixel layer

The current neopixel implementation allocates of lot of objects and intermediate arrays.

• remove the use of HSV in interpolate
• review all uses of HSV and remove allocation
• move hsvtoRgb into simple function logic

Fix twitter card info

Getting started tutorial: crashes when you have more than 7 unique blocks

If the getting started tutorial samples include 7 unique blocks, the tutorial tries to display categories and crashes with a "cannot read style of null" error

Speed up Animations

Can we speed up the built-in animations - Rainbow Cycle, and Comet?

error message when uf2 file is downloaded

• use nolocalhost=1 to trigger download mode.
• click download

NeoPixelColors lost when JS -> Blocks translations

Try converting

let initialValue = 0
control.forever(() => {
    if (initialValue != pins.D3.digitalRead()) {
        light.pixels.showColor(NeoPixelColors.Blue)
    }
})
initialValue = pins.D3.digitalRead()
light.pixels.showColor(NeoPixelColors.Red)

PXT editor should detect outdated firmware and auto-upgrade

The editor could lookup the tag in github, compare to the version number exposed by the board and upgrade as needed.

Deployment over HID fails on windows

Attempt to flash the device leads to this error. Running bootloader 0.1.11

HF2: Connected; msgSize 320B; flash 256kB; bootloader mode
HF2: Board-ID: SAMD21G18A-CPlay-v0
HF2: recv error: could not read from HID device
HIDERR Timeout
HF2: error cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}; reconnecting attempt #1
HF2: error cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}; reconnecting attempt #2
HF2: error cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}; reconnecting attempt #3
HF2: error cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}; reconnecting attempt #4
HF2: error cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}; reconnecting attempt #5
HIDERR cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
HIDERR cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
HIDERR cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
HIDERR cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
HIDERR cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
HIDERR cannot open device with path \\?\hid#vid_239a&pid_8019&mi_03#7&33dca5b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

Edge Browser Error on Save As

Michal, you're too fast! :-)
Repro: On Edge, hit Download, Save As, Select CPLAYBOOT, Save
Browser throws this error:

Singleton animations with parameters only respsect parameters on first call

If you show the "Color Wipe" animation with one color and then try to show it with another, it will still show the first color. Here is a program to illustrate what I mean:

Whichever button is pressed first determines the color of the animation forever.

Default brightness on neopixels is blinding

When you use the on-board neopixels in a program, they default to full brightness unless you explicitly set a lower value. The full brightness is way too bright (you can't look directly at it). I think that on our scale of 0-255, we should default to something more like 10 and that might even still be too bright if the board is held closer than arm's length. Anyone with a circuit playground want to weigh in on a good value?

Getting started is broken

Infinite hang on Edge when you click on getting started.

accelerometer hard crashes device

Repro:

control.forever(() => {
    neopixel.builtin.showBarGraph(
        input.acceleration(Dimension.X),
        255
    )
})

fix avatar svg

still using microbit logo

Show Bar Graph default values

are 0 - 255. In micro:bit they're 0 - 0. We should probably be consistent...

Update pin mappings for Rev G

Current Pin mappings are out of date; A8-A11 around the edge have been replaced with A0-A3

bug in rotation simulator function

The following leveling code doesn't work in the simulator:

let roll = 0
let pitch = 0
control.forever(() => {
    pitch = input.rotation(Rotation.Pitch)
    roll = input.rotation(Rotation.Roll)
    if (Math.abs(pitch) < 10 && Math.abs(roll) < 10) {
        light.pixels.showColor(light.colors(NeoPixelColors.Blue))
    } else {
        light.pixels.showColor(light.colors(NeoPixelColors.Red))
    }
})

light.builtin needs to be renamed

The singleton should be renamed now that the namespace is more general. "pixels" ?

legal links not visible on tiny embed view

white on white...

Update reference documentation

There are some microbit references in our documentation (see input.onGesture) and we need reference documentation for all of the API changes we are making. This is mostly a placeholder issue until we have all the APIs finalized.

send a "clear" buffer to neopixels before starting pxt compiled code

We should be able to send a clear buffer to the neopixel before running user code.

support for reset button inside of simulator

Since the reset button is visible, i tend to try to click it rather than to the toolbox icon.

z-index issue with the board in sandbox

unreadable code due to colors

Neopixels aren't cleared on reset

If you are showing something on the neopixels and reset (or go into the bootloader), the last thing being displayed on the neopixels will continue to show (i.e. they don't get turned off)

Docs decompilation adds unnecessary onstart

The following md in docs adds an unnecessary onstart:

let roll = 0
let pitch = 0
control.forever(() => {
    pitch = input.rotation(Rotation.Pitch)
    roll = input.rotation(Rotation.Roll)
    if (Math.abs(pitch) < 10 && Math.abs(roll) < 10) {
        light.pixels.showColor(light.colors(NeoPixelColors.Blue))
    } else {
        light.pixels.showColor(light.colors(NeoPixelColors.Red))
    }
});

converts to:

see http://localhost:3232/reference/input/rotation

Monaco toolbox fails to load

Display neopixel index as tooltip on simulator

Sparkle

Built-in animation Sparkle doesn't seem to be working in the Sim...

When HID deployment fails, generate and drop UF2 file.

With the program hard faulting, the HID code is busted and fails to upload. We need to bail out and tell the user to drop .uf2 file in the device.

TODO

Let's a list of TODOs in a single place rather with tons of issues.

Apis

• capacitive buttons events / pressed apis
• finalize pin mapping in board definition
• generate API docs

Art

• logo svg based
• avatar image (svg)
• loader image (svg)
• review category colors

Docs

• getting started
• generate api docs (once finalized)
• add 'Beta' somewhere on the page or in the domain name

neopixels should be grey when value is 0.

Currently has a glow when rgb value is 0.

simulation of analog pins need to account for "secret" pins

This script crashes the simulator

control.forever(() => {
    pins.A0.analogWrite(1023)
})

Add some better APIs for the slide switch

Right now its all wrapped up with the button APIs. We can leave those, but it is not obvious how you achieve "when switch turned on" and "when switch turned off". The "Up" and "Down" terminology is confusing.

scrollbars invisible

CP simulator SVG needs to be updated to latest rev

We're still using a rather old SVG based - all labels are outdated.

hw crash on new program

Crashes quickly after running

control.forever(() => {
    photon.forward(1)
})

PWM pins not displayed in Analog pin method drop down

A8-A11 not showing up in analogWritePin in blocks because they are a subclass of analog pin. The methods are defined in TS so it seems that it is a blockly load issue.

external neopixels not working

Repo:
[-] connect a 60-neopixel strip to ground, power and pin A8 on CP (note, we have "D" pins in our editor instead of "A")
[-] build and deploy this program

Nothing happens.

"no-default-lib.d.ts(1,1): error TS9043: The hex file is not available, please connect to internet and try again."

Need to fix that one.

Update adafruit category colors

Yellow fails the contrast check at http://leaverou.github.io/contrast-ratio.
We should refrain from yellow as it doesnt contrast well with white.

Look into updating some of the other colors.

IE11 - simulator crashes on 'fill'

fix servoSetPulse signature in PXT

nameId argument should be removed.

Add shake button in the simulator

It's hard to shake using just the mouse.