Skip to content

Commit ff777bc

Browse files
author
Catalin Ioana
authored
Merge pull request #175 from pycom/pymesh
Pymesh added licence file
2 parents 12edd44 + 2e41917 commit ff777bc

File tree

4 files changed

+3
-4
lines changed

4 files changed

+3
-4
lines changed

content/pymesh/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ A Mesh network acts like a net, this means that any node within the network can
1414

1515
Mesh networks essentially get rid of gateways, which decentralises the network's infrastructure. This then means that the network becomes flexible, so it can do many wonderful things – such as generate, change and fix itself. The success of the Mesh network is down to its parts, as any node within the network will automatically connect to the best radio-link available.
1616

17-
Pymesh solution works on all of our LoRa supporting development boards, the LoPy4 and FiPy as well as on our OEM modules, L01 and L04.
17+
Pymesh works on all of our LoRa supporting development boards, the LoPy4 and FiPy as well as on our OEM modules, L01 and L04.
1818

1919
_**Note: For obtaining the Pymesh firmware please follow the steps from [Pymesh LICENCE page](/pymesh/licence).**_
2020

content/pymesh/lib-ble-rpc.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ This returns the list of pairs that form a mesh connection, as shown bellow:
4444

4545
#### get_node_info(mac_id = ' ')
4646

47-
This returns the node data for a specified mac address, or own data id `mac_id` is not specified. Node data is dictionary with the following structure:
47+
This returns the node data for a specified mac address, or own data if `mac_id` is not specified. Node data is dictionary with the following structure:
4848
```
4949
{
5050
'ip': 4c00, # last 2bytes from the ip v6 RLOC16 address

content/pymesh/licence.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,8 @@ aliases:
77
## Licensing process
88

99
In order to receive access to the Pymesh firmware releases (for Lopy4, Fipy, L01 or L04), the next process should be followed:
10-
<!-- <a href="/gitbook/assets/specsheets/Pycom_002_Specsheets_LoPy4_v2.pdf" target="\_blank"> the Pymesh LICENCE PDF document </a> -->
1110

12-
1. Complete the Pymesh LICENCE PDF document(not yet available), sign it and send us by [this email](mailto:catalin@pycom.io?subject=[Pymesh_LICENCE]).
11+
1. Complete the <a href="/gitbook/assets/pymesh/Pymesh_Licence_Copyright_Notice.pdf" target="\_blank"> the Pymesh LICENCE PDF document</a>, sign it and send us by [this email](mailto:catalin@pycom.io?subject=[Pymesh_LICENCE]).
1312
1. You will receive by email an archive containing the images for all boards.
1413
1. Extract the corresponding image, for example Lopy4.tar.gz, and upload the firmware to your board, using the [Pycom Firmware Update Tool](https://pycom.io/downloads/), similar in the following image:
1514
<img src="/gitbook/assets/pymesh/pymesh_firmware_update.png" alt="Pymesh Firmware Update" width="500"/>
Binary file not shown.

0 commit comments

Comments
 (0)