pxt-microbit 4.1.6 → 4.1.10

package/docs/device/usb/webusb.md

@@ -1,12 +1,11 @@
 # WebUSB
 
-[WebUSB](https://wicg.github.io/webusb/) is an emerging web standard that allows to access @boardname@ from web pages. 
-It allows for a **one-click download** without installing any additional app or software! It also allows to receive data from the @boardname@.
+[WebUSB](https://wicg.github.io/webusb/) is a recent and developing web standard that allows you to access @boardname@ directly from a web page. It allows for a **one-click download** without installing any additional app or software! It also lets you receive data into the web page from the @boardname@.
 
 ## Support
 
-* Chrome 79+ browser for Android, Chrome OS, Linux, macOS and Windows 10.
-* Microsoft Edge 79+ browser for Android, Chrome OS, Linux, macOS and Windows 10.
+* Chrome (version 79 and newer) browser for Android, Chrome OS, Linux, macOS and Windows 10.
+* Microsoft Edge (version 79  and newer) browser for Android, Chrome OS, Linux, macOS and Windows 10.
 
 ## Prepare your @boardname@
 
@@ -18,13 +17,36 @@ Make sure that your @boardname@ is running version **0249** or above of the firm
 
 Here are the steps on the supported browsers:
 
-* connect your @boardname@ to your computer with the microUSB cable
-* open a project
-* click the triple dot icon on the **Download** button and click **Pair device**
-* click on the **Pair device** button and select **BBC micro:bit CMSIS-DAP** or **DAPLink CMSIS-DAP** from the list.
+* Connect your @boardname@ to your computer with the Micro USB cable
+* Open a project
+* Click the triple dot icon on the **Download** button and then click **Connect device**.
+
+![Download button and menu](/static/mb/device/usb/download-button-menu.jpg)
+
+* In the connection message window, click **Next**.
+
+![Connect device dialog](/static/mb/device/usb/connect-usb.jpg)
+
+* Another message window will display telling you which device you should pair with. Click **Next** to go to the device list.
+
+![Device name dialog](/static/mb/device/usb/pair-dap.jpg)
+
+* Select **BBC micro:bit CMSIS-DAP** or **DAPLink CMSIS-DAP** from the list and click **Connect**.
+
+![Device list for WebUSB pairing](/static/mb/device/usb/pair-device.jpg)
 
 If you don't see any devices in the list and @boardname@ has the right firmware (**0249** or above), you can create a [support ticket](https://support.microbit.org/support/tickets/new) to notify the Micro:bit Foundation of the problem. Skip the rest of these steps.
 
+![Device list for WebUSB pairing](/static/mb/device/usb/no-pair.jpg)
+
+* When your @boardname@ is connected, you'll see the **Connected to micro:bit** message window. Click on **Done** and you're ready to go! 
+
+![Connected message window](/static/mb/device/usb/connected.jpg)
+
+* If the connection to your @boardname@ was unsuccessful, you'll see the **Connect failed** message. You can press **Try Again** to attempt the connection again or cancel the window and [troubleshoot](/device/usb/webusb/troubleshoot) your connection.
+
+![Connect failed message window](/static/mb/device/usb/connect-fail.jpg)
+
 ## Unpair your @boardname@ #unpair
 
 You will need to unpair your device from the editor to disable WebUSB.
@@ -33,7 +55,7 @@ You will need to unpair your device from the editor to disable WebUSB.
 * Uncheck each **BBC micro:bit CMSIS-DAP** or **DAPLink CMSIS-DAP** device
 * Reload the page
 
-![](/static/webusb/unpair.gif)
+![Unpairing from the browser](/static/webusb/unpair.gif)
 
 ## One-click Download
 

package/docs/device/usb/windows-chrome.md

@@ -1,32 +1,22 @@
-# Uploading from Chrome for Windows
-
-## ~ hint
-
-Starting with Chrome 65 on Windows 10, 
-you can use **WebUSB** to download with one-click.
-[Learn more about WebUSB...](/device/usb/webusb).
-
-## ~
+# Transferring from Chrome for Windows
 
 While you're writing and testing your programs, you'll mostly be [running them
 in the simulator](/device/simulator), but once you've finished your program you
 can **compile** it and run it on your micro:bit.
 
-The basic steps are:
+## Transfer using a WebUSB connection
 
-1. Connect your micro:bit to your computer via USB
-2. Click **Download** and download the `.hex` file
-3. Copy the `.hex` file from your computer onto the micro:bit drive
+With Chrome (version 79 and newer), you can transfer your program to the @boardname@ with a single click. If your browser supports WebUSB, you can use the **one-click download** feature to send your programs to the @boardname@. See the [WebUSB](/device/usb/webusb) page to learn how to pair your @boardname@ with a computer and transfer your programs with a single click.
 
-## Requirements
+## Downloading your program as file
 
-You need the following things to transfer and run a script on your micro:bit:
+The basic steps are:
 
-* A-Male to Micro USB cable to connect your computer to your micro:bit. This is
-    the same cable that is commonly used to connect a smart phone to a computer.
-* A PC running Windows 7 or later.
+1. Connect your @boardname@ to your computer with a USB cable (use an A-Male to Micro USB cable)
+2. Click **Download** and download the `.hex` file
+3. Copy the `.hex` file from your computer onto the micro:bit drive
 
-## Step 1: Connect your micro:bit to your computer
+### Step 1: Connect your micro:bit to your computer
 
 First, connect the micro:bit:
 
@@ -40,7 +30,7 @@ it appears as a new drive under Devices.
 
 ![](/static/mb/device/usb-windows-device.jpg)
 
-## Step 2 (optional): Configure Chrome to ask where to save the file
+### Step 2 (optional): Configure Chrome to ask where to save the file
 
 You only need to do this once.
 
@@ -49,7 +39,7 @@ You only need to do this once.
 3. Find the **Downloads** settings.
 4. Enable the setting **Ask where to save each file before downloading**.
 
-## Step 3: Download your program
+### Step 3: Download your program
 
 1. Open your project on @homeurl@
 2. Click **Download**
@@ -57,11 +47,11 @@ You only need to do this once.
     so save it into the `MICROBIT` drive.
     Otherwise, continue with one of the options in Step 4 below.
 
-## Step 4: Transfer the file to your micro:bit
+### Step 4: Transfer the file to your micro:bit
 
 If the file was saved onto your computer, you will need to transfer it to the micro:bit.
 
-## Manual transfer
+#### Manual transfer
 
 Your `.hex` file (created in Step 3 above) appears as a download at the bottom of the browser.
 Click on the arrow next to the name of the file and then click **Show in folder**.
@@ -74,7 +64,7 @@ Alternatively, right-click on the hex file, choose **Send to**, and then **MICRO
 
 ![](/static/mb/device/usb-windows-sendto.jpg)
 
-## Step 5: After transferring the file
+### Step 5: After transferring the file
 
 * The LED on the back of your micro:bit flashes during the transfer (which 
     should only take a few seconds).

package/docs/device/usb/windows-edge.md

@@ -1,26 +1,24 @@
-# Uploading from Microsoft Edge on Windows
+# Transferring from Microsoft Edge on Windows
 
-How to compile, transfer, and run a program on your micro:bit on **Microsoft Edge**.
+How to compile, transfer, and run a program on your micro:bit with **Microsoft Edge**.
 
 While you're writing and testing your programs, you'll mostly be [running them
 in the simulator](/device/simulator), but once you've finished your program you
 can **compile** it and run it on your micro:bit.
 
-The basic steps are:
+## Transfer using a WebUSB connection
 
-1. Connect your @boardname@ to your computer via USB
-2. Click **Download** to download the `.hex` file
-3. Click the **Save As** button in the bottom bar and save the `.hex` file into the MICROBIT drive
+With Microsoft Edge (version 79 and newer), you can transfer your program to the @boardname@ with a single click. If your browser supports WebUSB, you can use the **one-click download** feature to send your programs to the @boardname@. See the [WebUSB](/device/usb/webusb) page to learn how to pair your @boardname@ with a computer and transfer your programs with a single click.
 
-## Requirements
+## Downloading your program as file
 
-You need the following things to transfer and run a script on your micro:bit:
+The basic steps are:
 
-* A-Male to Micro USB cable to connect your computer to your micro:bit. This is
-    the same cable that is commonly used to connect a smart phone to a computer.
-* A PC running Windows 7 or later.
+1. Connect your @boardname@ to your computer with a USB cable (use an A-Male to Micro USB cable)
+2. Click **Download** to download the `.hex` file
+3. Click the **Save As** button in the bottom bar and save the `.hex` file into the MICROBIT drive
 
-## Step 1: Connect your micro:bit to your computer
+### Step 1: Connect your micro:bit to your computer
 
 First, connect the micro:bit:
 
@@ -34,7 +32,7 @@ it appears as a new drive under Devices.
 
 ![](/static/mb/device/usb-windows-device.jpg)
 
-## Step 2: Download your program
+### Step 2: Download your program
 
 1. Open your project on @homeurl@
 2. Click **Download**

package/docs/device/usb.md

@@ -1,10 +1,16 @@
-# Uploading programs to your @boardname@
+# Transferring programs to your @boardname@
 
-Most of the time you'll be writing and testing your programs in the [simulator](/device/simulator). Once you've finished your program though, you can **compile** it and run it on your @boardname@. Transferring your program to the @boardname@ is as simple as saving a file to a drive on your computer.
+Most of the time you'll be writing and testing your programs in the [simulator](/device/simulator). Once you've finished your program though, you can **compile** it and run it on your @boardname@. Transferring your program to the @boardname@ is as simple as clicking the **Download** button, or by saving a file to a drive on your computer.
 
-When you plug your @boardname@ into USB, a new drive is created with the **@drivename@** label. This is where you'll save your program.
+![micro:bit connected using USB](/static/mb/device/usb-thin.jpg)
 
-![](/static/mb/device/usb-thin.jpg)
+## Transfer using a WebUSB connection
+
+With some newer browsers, you can transfer your program to the @boardname@ with a single click. If your browser supports WebUSB, you can use the **one-click download** feature to send your programs to the @boardname@. See the [WebUSB](/device/usb/webusb) page to learn how to pair your @boardname@ with a computer and transfer your programs with a single click.
+
+## Downloading your program as file
+
+If your browser doesn't support WebUSB or you want to use your computer's file system to transfer your program instead, you can download it to the @boardname@ as a file. When you plug your @boardname@ into USB, a new drive is created with the **@drivename@** label. This is where you'll save your program.
 
 The basic steps are:
 

package/docs/device.md

@@ -1,16 +1,24 @@
 # Device
 
+### ~ hint
 
-## ~ hint
+#### Looking to buy a micro:bit?
 
-**Looking to buy a micro:bit?** See the [list of resellers](https://microbit.org/resellers).
+See the [list of resellers](https://microbit.org/resellers).
 
-## ~
+### ~
 
 All the bits and pieces that make up the BBC micro:bit
 
-![micro:bit board layout](/static/mb/device-0.png)
+![micro:bit board layout](/static/mb/device-v2.jpg)
 
+### ~ hint
+
+#### The current version of micro:bit is v2
+
+The version of @boardname@ is now currently at **v2**. See the what's new in MakeCode for programming the [@boardname@ v2](/device/v2).
+
+### ~
 
 ## LED Screen and Status LED
 
@@ -27,17 +35,21 @@ https://www.youtube.com/watch?v=qqBmvHD5bCw
 
 ## Buttons
 
-Buttons A and B are a form of input.  When you press a button, it completes an electrical circuit. 
+Buttons **A** and **B** are a form of input.  When you press a button, it completes an electrical circuit. 
 The micro:bit can detect either of its two buttons being pressed/released and be programmed 
 to act on these events.
 
-Button R on the back of the micro:bit is a system button. It has different uses. 
-When you have downloaded and run your code onto your micro:bit, press Button R to restart and run your program from the beginning.
+Button **R** on the back of the micro:bit is a system button. It has different uses. 
+When you have downloaded and run your code onto your micro:bit, press Button **R** to restart and run your program from the beginning.
 
 Find out how buttons provide input to the @boardname@ in this video:
 
 https://www.youtube.com/watch?v=t_Qujjd_38o
 
+## Touch
+
+Pins **0**, **1**, **2**, and the board **logo** can work as touch buttons when they are programmed for input.
+
 ## USB connection
 
 When you plug in your micro:bit via [USB](/device/usb), it should appear as  a ``MICROBIT`` drive. 
@@ -47,9 +59,9 @@ the micro:bit will appear as a ``MAINTENANCE`` drive instead of ``MICROBIT``. Th
 
 To continue programming your micro:bit YOU MUST unplug your USB and reconnect it. Check that the drive now shows as ``MICROBIT``.
 
-## ~ hint
+### ~ hint
 
-### Open the version file
+#### Open the version file
 
 Use with caution!
 If you click on the drive while it shows the ``MAINTENANCE`` label, 
@@ -57,7 +69,7 @@ you can see which version of firmware you have running on your micro:bit.
 Firmware on your micro:bit should be up-to-date already. 
 You can find the version of firmware in the 'version.txt' file on the micro:bit. See the @boardname@ **[firmware](https://microbit.org/guide/firmware/)** page for more about checking your board's firmware version.
 
-## ~
+### ~
 
 ## Compass
 
@@ -79,7 +91,11 @@ https://www.youtube.com/watch?v=byngcwjO51U
 ## Pins
 
 The [pins](/device/pins) can be a form of electrical input or output. 
-There are labels for the input/output pins ``P0``, ``P1``, ``P2``, which you can attach external sensors to such as thermometers or moisture detectors.
+There are labels for the input/output pins **0**, **1**, **2**, which you can attach external sensors to such as thermometers or moisture detectors.
+
+## Microphone
+
+Using the microphone, your programs can detect sounds that are present. You can check for loud or quiet sounds and find out what their sound level is.
 
 ## Light level
 
@@ -119,7 +135,7 @@ and [click here to read more about the error messages you might get](/device/err
 When your micro:bit is connected to your computer with the micro USB, it doesn’t need another power source.  
 When your micro:bit isn’t connected to your computer, tablet or mobile, you will need 2 x AAA 1.5 V batteries to power it.
 
-The pins labelled 3V and GND are the power supply pins. 
+The pins labelled **3V** and **GND** are the power supply pins. 
 You can attach an external device such as a motor to these and power it using the battery or USB.
 
 ## Serial Communication

package/docs/docs.md

@@ -21,7 +21,7 @@
 
 ## More questions?
 
-* [Frequently Asked Question](/faq)
+* [Frequently Asked Questions](/faq)
 * [Help Translate](/translate)
 * [Embedding project](/share)
 

package/docs/extensions.md

@@ -55,6 +55,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
     "name": "Wearables",
     "url": "/extensions#wearables",
     "cardType": "link"
+ }, {
+    "name": "Utilities",
+    "url": "/extensions#utilities",
+    "cardType": "link"
 }]
 ```
 
@@ -172,6 +176,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
 
 ```codecard
 [{
+ "name": "SGBotic Ultimate SR04",
+  "url":"/pkg/SGBotic/pxt-SGBotic-Ultimate-SR04-RGB",
+  "cardType": "package"
+}, {
  "name": "TCS3200 Color sensor",
   "url":"/pkg/joy-it/pxt-SEN-Color",
   "cardType": "package"
@@ -302,6 +310,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
 
 ```codecard
 [{
+  "name": "iClass IoT",
+  "url":"/pkg/KelieLeung/pxt-iClassIoT",
+  "cardType": "package"
+}, {
   "name": "Kittenbot Wifi",
   "url":"/pkg/KittenBot/pxt-kittenwifi",
   "cardType": "package"
@@ -344,6 +356,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
 
 ```codecard
 [{
+   "name": "HacKids hack:bit",
+   "url": "/pkg/HackidsEdu/pxt-hackbit",
+   "cardType": "package"
+}, {
    "name": "KittenBot Sugar",
    "url": "/pkg/KittenBot/pxt-sugar",
    "cardType": "package"
@@ -376,8 +392,12 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
   "url":"/pkg/elecfreaks/pxt-PlanetX",
   "cardType": "package"
 }, {
-  "name": "Inksmith Climate Action Kit",
-  "url":"/pkg/dugbraden/pxt-climate-action-kit",
+  "name": "Inksmith Climate Action Kit: Land",
+  "url":"/pkg/climate-action-kits/pxt-climate-action-kit-land",
+  "cardType": "package"
+}, {
+  "name": "Inksmith Climate Action Kit: Energy",
+  "url":"/pkg/climate-action-kits/pxt-climate-action-kit-land",
   "cardType": "package"
 }, {
   "name": "Grove inventor kit",
@@ -453,6 +473,18 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
 
 ```codecard
 [{
+  "name": "Kitronik :CREATE Simple Servo Control Board",
+  "url":"/pkg/KitronikLtd/pxt-kitronik-simple-servo",
+  "cardType": "package"
+}, {
+  "name": "Kittenbot miniLFR",
+  "url":"/pkg/KittenBot/pxt-minilfr",
+  "cardType": "package"
+}, {
+  "name": "Cytron ZOOM:BIT",
+  "url":"/pkg/CytronTechnologies/pxt-zoombit",
+  "cardType": "package"
+}, {
   "name": "Kid Spark Spark:bit",
   "url":"/pkg/KidSpark/pxt-sparkbit",
   "cardType": "package"
@@ -687,6 +719,10 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
 
 ```codecard
 [{
+  "name": "PT-BOT KidsBIT",
+  "url":"/pkg/iBuilds/pxt-PTKidsBIT-IoT",
+  "cardType": "package"
+}, {
   "name": "Kitronik Air Quality & Environmental Board",
   "url":"/pkg/KitronikLtd/pxt-kitronik-air-quality",
   "cardType": "package"
@@ -808,6 +844,34 @@ Check out [the accessories pages on microbit.org](https://microbit.org/buy/acces
 ## Utilities
 ```codecard
 [{
+  "name": "Soroban abacus",
+  "url":"/pkg/aorczyk/soroban",
+  "cardType": "package"
+}, {  
+  "name": "Lego PF recorder",
+  "url":"/pkg/aorczyk/pf-recorder",
+  "cardType": "package"
+}, {
+  "name": "Lego PF transmitter",
+  "url":"/pkg/aorczyk/lego-pf-transmitter",
+  "cardType": "package"
+}, {
+  "name": "Lego PF receiver",
+  "url":"/pkg/aorczyk/lego-pf-receiver",
+  "cardType": "package"
+}, {
+  "name": "Kodely dot",
+  "url":"/pkg/Kodely-io/dot",
+  "cardType": "package"
+}, {
+  "name": "Wait until...",
+  "url":"/pkg/TeacherPinky/Wait-Until-Blocks",
+  "cardType": "package"
+}, {
+  "name": "micro:bit power saving",
+  "url":"/pkg/microbit-foundation/pxt-microbit-v2-power",
+  "cardType": "package"
+}, {
   "name": "DS3231 Real Time Clock",
   "url":"/pkg/AlexandreFrolov/DS3231",
   "cardType": "package"

package/docs/projects/micro-coin.md

@@ -6,27 +6,31 @@ Have you heard about BitCoin and all those new Crypto currencies? Well micro:bit
 
 ## ~
 
+![micro:coin at CoinBank](/static/mb/projects/micro-coin/coinbank.png)
+
 ## How does a @boardname@ make coins?
 
 
-Each @boardname@ contains a **blockchain**, a sequence of **blocks**, that is public and can't be modified. Each block represents a **coin**. To mine new coins, the user shakes 
-the @boardname@ and, if they are in luck, their coin added to the chain as a new block! 
+Each @boardname@ contains a **blockchain**, a sequence of **blocks** (in this case, chunks of information not blocks of a program), that is public and can't be modified. Each block represents a **coin**. The process of making coins is called _mining_. To mine new coins, the user shakes 
+the @boardname@ and, if they are in luck, their coin is added to the chain as a new block! 
 Once the block is added, it is broadcasted to the other @boardname@ (the block chain is public and can't be modified so it's ok to share it). Other @boardname@s receive the block, validate the transaction and update their block chain as needed.
 
-Pressing ``A`` shows the number of block you added to the chain, that's your score.
-Pressing ``B`` shows you the length of the chain.
-
-Happy mining!
-
 ## Coins, blocks, chains
 
 A _blockchain_ is a list of _blocks_ that record transactions of a crypto-currency like BitCoin. A block might contain information like the time it was created (mined) and who mined it. The most important part of the block is it's _hash_. This is a special number made from the information in the last block of the block list combined with the hash number of previous block in the list. The new block contains information for the current transaction and this new hash number. The new block is added to the list of previous blocks. This list is then transmitted to the crypto currency network. It's really hard (like impossible) to tamper or forge a hash which allows the blockchain to be transmitted publicly.
 
+## Start mining
+
+Pressing ``A`` shows the number of blocks you added to the chain, that's your score.
+Pressing ``B`` shows you the length of the chain.
+
+Happy mining!
+
 ### ~ hint
 
 #### Secure your coins
 
-Build yourself a [@boardname@ wallet](/projects/wallet) to hold your coins!
+Keep your coins safe. Build yourself a [@boardname@ wallet](/projects/wallet) to hold your coins!
 
 ### ~
 

package/docs/projects/v2-morse-chat.md

@@ -256,10 +256,10 @@ Remember to turn your sound on!
 
 ---
 
-► Touch the gold logo at the top of your @boardname@ (it looks like a pig snout 🐽) on the simulator. You'll notice that a second @boardname@ appears.  
+► Touch the gold **micro:bit logo** at the top of your @boardname@ on the simulator. You'll notice that a second @boardname@ appears.  
 💡 If your screen is too small, you might not be able to see it.
 
-► Touch the 🐽 again to send messages to Sky 🐖  
+► Touch the logo again to send messages to Sky 🐖  
 **Press** to send a dot.  
 **Long press** (count to 3!) to send a dash.
 

package/docs/projects/v2-pet-hamster.md

@@ -146,7 +146,7 @@ Check out the simulator and make sure your speakers are on 🔊
 
 Play with Cyrus to see how they react 🐹  
 **Click on the SHAKE button** to shake Cyrus.  
-**Touch the gold logo at the top** (it looks like a piggy snout 🐽) to tickle Cyrus.
+**Touch the gold logo at the top** to tickle Cyrus.
 
 If you have a new @boardname@ (the one with the **shiny gold** logo at the top), download this code and try it out!
 

package/docs/reference/radio/received-packet.md

@@ -18,10 +18,18 @@ In addition to a [number](types/number), [string](/types/string), or name-value
 ## Returns
 
 * a [number](/types/number) that is the property selected in the **type** parameter:
->* ``signal strength``: the value ranges from `-128` to `-42` (`-128` means a weak signal and `-42` means a strong one.)
+>* ``signal strength``: the value ranges from `-128` up to `-28` (`-128` means a weak signal and `-28` means a strong one.)
 >* ``serial number``: the value is the serial number of the board sending the packet.
 >* ``time``: the value is the system time, in microseconds, of the sender at the time when the packet was sent.
 
+### ~ hint
+
+#### Signal strength and board version
+
+Measurement of the received signal strength is dependent on what version of @boardname@ you have. The @boardname@ boards prior to v2 can typically measure a signal strength up to `-42` dBm. Now, v2 boards will measure a signal strength up to `-28` dBm (typical).
+
+### ~
+
 ## Example
 
 This program uses the signal strength from received packets to graph the

package/docs/reference/radio/received-signal-strength.md

@@ -6,29 +6,35 @@ Find how strong the radio signal is.
 radio.receivedSignalStrength();
 ```
 
-## ~ hint
+### ~ hint
 
-**Deprecated**
+#### Deprecated
 
 This API has been deprecated! Use [received packet](/reference/radio/received-packet) instead.
 
-## ~
+### ~
 
-Find how strong the ``radio`` signal is, from `-128` to `-42`.
-(`-128` means a weak signal and `-42` means a strong one.)
+Find how strong the ``radio`` signal is, from `-128` to `-28`.
+(`-128` means a weak signal and `-28` means a strong one.)
 
 The @boardname@ finds the signal strength by checking how strong it was
 the last time it ran the
 [on received number](/reference/radio/on-received-number) function. That means
 it needs to run **receive number** first.
 
-
-
 ## Returns
 
-* a [number](/types/number) between `-128` and `-42` that means
+* a [number](/types/number) between `-128` and `-28` that means
 how strong the signal is.
 
+### ~ hint
+
+#### Signal strength and board version
+
+Measurement of the received signal strength is dependent on what version of @boardname@ you have. The @boardname@ boards prior to v2 can typically measure a signal strength up to `-42` dBm. Now, v2 boards will measure a signal strength up to `-28` dBm (typical).
+
+### ~
+
 ## Simulator
 
 This function only works on the @boardname@, not in browsers.
@@ -49,7 +55,8 @@ basic.forever(() => {
 
 ## See also
 
-[on received number](/reference/radio/on-received-number), [send number](/reference/radio/send-number), [on data received](/reference/radio/on-data-received)
+[on received number](/reference/radio/on-received-number), [send number](/reference/radio/send-number),
+[on data received](/reference/radio/on-data-received), [received packet](/reference/received-packet)
 
 ```package
 radio

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "pxt-microbit",
-    "version": "4.1.6",
+    "version": "4.1.10",
     "description": "micro:bit target for Microsoft MakeCode (PXT)",
     "keywords": [
         "JavaScript",
@@ -44,7 +44,7 @@
         "typescript": "4.2.3"
     },
     "dependencies": {
-        "pxt-common-packages": "9.2.7",
-        "pxt-core": "7.2.16"
+        "pxt-common-packages": "9.4.3",
+        "pxt-core": "7.4.12"
     }
 }

package/pxtarget.json

@@ -164,7 +164,7 @@
                 "codalTarget": {
                     "name": "codal-microbit-v2",
                     "url": "https://github.com/lancaster-university/codal-microbit-v2",
-                    "branch": "v0.2.32",
+                    "branch": "v0.2.34-RC1",
                     "type": "git"
                 },
                 "codalBinary": "MICROBIT",
@@ -522,6 +522,7 @@
             "ar",
             "bg",
             "cs",
+            "cy",
             "da",
             "de",
             "el",