-
Notifications
You must be signed in to change notification settings - Fork 143
added english documentation #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
|
Ukrit Pongsathaporn seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
| @@ -0,0 +1,382 @@ | |||
| # LINE Things Development Board | |||
| The LINE Things development board is powered by [Nordic Semiconductor's nRF52832] (https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832), in which the specific module used is the [Raytac MDBT42Q] (http: // www.raytac.com/product/ins.php?index_id=31). This development board is for experimenting with LINE Things. It actually consists of two boards, the first being the core or the CPU board, and the other is the peripheral board or the daughterboard. After verifying the functionality of a concept through the daughterboard, the core can be removed to be placed into a breadboard for custom board designs and prototyping. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please delete space between link title and URL.
| The LINE Things development board is powered by [Nordic Semiconductor's nRF52832] (https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832), in which the specific module used is the [Raytac MDBT42Q] (http: // www.raytac.com/product/ins.php?index_id=31). This development board is for experimenting with LINE Things. It actually consists of two boards, the first being the core or the CPU board, and the other is the peripheral board or the daughterboard. After verifying the functionality of a concept through the daughterboard, the core can be removed to be placed into a breadboard for custom board designs and prototyping. | |
| [Nordic Semiconductor's nRF52832](https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832) |
| | Maximum continuous current consumption (when using motor) | 2.6A | | ||
|
|
||
| ## Peripherals on the daughter board | ||
| **NOTE 5V systems and 3.3V systems cannnot be directly connected to one another.** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are 3.3V and 5V devices on the board.
On board battery can only supply 3.3V. So, can not work 5 V device.for example, motors.
When use external or USB power, 5V and 3.3V are provided and all devices can be used.
|
|
||
| ### Buzzer | ||
| A piezoelectric buzzer is included. To make the buzzer sound, you will need to provide an AC signal from the microcontroller. Setting the pin to HIGH will not cause the buzzer to make a sound. Normally on a regular Arduino, you would be able to use the tone() function to create such signals, however the timer in the nRF52832 is incompatible with this library. Therefore, you will need to generate the signal yourself through timers, interrupts, etc. In the sample provided, we take advantage of FreeRTOS's timer to generate a 1KHz interrupt to toggle the pin state which creates a 500Hz signal to make the buzzer sound. If you want to change the pitch of the buzzer, you will need to play around with the timers. | ||
| You can use the tone () function to produce any sound with regular Arduino, but you can not use this with the nRF52832 Arduino environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not need
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpulabs This sentence is from
通常のArduinoであればtone()関数で任意の音を出すことが可能ですが、nRF52832のArduino環境ではこれを使うことができません。
Is this unnecessary?
hktechn0
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check details later
| @@ -0,0 +1,382 @@ | |||
| # LINE Things Development Board | |||
| The LINE Things development board is powered by [Nordic Semiconductor's nRF52832] (https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832), in which the specific module used is the [Raytac MDBT42Q] (http: // www.raytac.com/product/ins.php?index_id=31). This development board is for experimenting with LINE Things. It actually consists of two boards, the first being the core or the CPU board, and the other is the peripheral board or the daughterboard. After verifying the functionality of a concept through the daughterboard, the core can be removed to be placed into a breadboard for custom board designs and prototyping. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The LINE Things development board is powered by [Nordic Semiconductor's nRF52832] (https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832), in which the specific module used is the [Raytac MDBT42Q] (http: // www.raytac.com/product/ins.php?index_id=31). This development board is for experimenting with LINE Things. It actually consists of two boards, the first being the core or the CPU board, and the other is the peripheral board or the daughterboard. After verifying the functionality of a concept through the daughterboard, the core can be removed to be placed into a breadboard for custom board designs and prototyping. | |
| The LINE Things development board is powered by [Nordic Semiconductor's nRF52832](https://www.nordicsemi.com/Products/Low-power-short-range-wireless/nRF52832), in which the specific module used is the [Raytac MDBT42Q](http://www.raytac.com/product/ins.php?index_id=31). This development board is for experimenting with LINE Things. It actually consists of two boards, the first being the core or the CPU board, and the other is the peripheral board or the daughterboard. After verifying the functionality of a concept through the daughterboard, the core can be removed to be placed into a breadboard for custom board designs and prototyping. |
| [Documentation on Github Pages] (https://line.github.io/line-things-dev-board/) | ||
|
|
||
| -README.md | ||
| -[Quick Start] (#quick-start) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| -[Quick Start] (#quick-start) | |
| -[Quick Start](#quick-start) |
|
|
||
| -README.md | ||
| -[Quick Start] (#quick-start) | ||
| -[How to use] (#How to use) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| -[How to use] (#How to use) | |
| -[How to use](#How to use) |
| -README.md | ||
| -[Quick Start] (#quick-start) | ||
| -[How to use] (#How to use) | ||
| -[Precautions] (#Precautions) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| -[Precautions] (#Precautions) | |
| -[Precautions](#Precautions) |
| -[Quick Start] (#quick-start) | ||
| -[How to use] (#How to use) | ||
| -[Precautions] (#Precautions) | ||
| -[Hardware Specification] (#Hardware Specification) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| -[Hardware Specification] (#Hardware Specification) | |
| -[Hardware Specification](#Hardware Specification) |
| ### CPU core | ||
| [cpuboard] (https://user-images.githubusercontent.com/135050/58088657-1bcf7080-7bfe-11e9-89f4-5e6bbde1a363.jpg) | ||
|
|
||
| The [Raytac MDBT42Q] (http://www.raytac.com/product/ins.php?index_id=31) module is the main processor of this development board. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| The [Raytac MDBT42Q] (http://www.raytac.com/product/ins.php?index_id=31) module is the main processor of this development board. | |
| The [Raytac MDBT42Q](http://www.raytac.com/product/ins.php?index_id=31) module is the main processor of this development board. |
| You can also develop everything from scratch using Nordic's nRF5 SDK. Both configurations of the board are supported; CPU core as a standalone as well as paired with the daughter board as a complete development board of LINE Things. | ||
|
|
||
| #### Pin assignment | ||
| [cpuboard_pinassign] (https://user-images.githubusercontent.com/135050/58088655-1a9e4380-7bfe-11e9-90d4-530f84e56242.png) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| [cpuboard_pinassign] (https://user-images.githubusercontent.com/135050/58088655-1a9e4380-7bfe-11e9-90d4-530f84e56242.png) | |
| [cpuboard_pinassign](https://user-images.githubusercontent.com/135050/58088655-1a9e4380-7bfe-11e9-90d4-530f84e56242.png) |
| The CPU core is fully functional as a standalone board, requiring only power to be supplied to it. The Reset pin is internally pulled up and can be left unconnected if unused. | ||
|
|
||
| ## Usage Notes | ||
| ### CPU board |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ### CPU board | |
| ### CPU core |
| * When using the CPU core as a standalone, ensure the antenna sits as far away from the breadboard as possible (preferably the edge of the breadboard) to avoid any interference. Additionally, any GND wiring and planes as well as any RF signals near the attena can cause interference. | ||
| * For a reliable connection and communication, make sure to keep the antenna as exposed as possible. Avoid metallic enclosures as it can block BLE signals. Plastic enclosures are highly advised. | ||
|
|
||
| ### Motherboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| ### Motherboard | |
| ### Daughter board |
|
|
||
| ### Buzzer | ||
| A piezoelectric buzzer is included. To make the buzzer sound, you will need to provide an AC signal from the microcontroller. Setting the pin to HIGH will not cause the buzzer to make a sound. Normally on a regular Arduino, you would be able to use the tone() function to create such signals, however the timer in the nRF52832 is incompatible with this library. Therefore, you will need to generate the signal yourself through timers, interrupts, etc. In the sample provided, we take advantage of FreeRTOS's timer to generate a 1KHz interrupt to toggle the pin state which creates a 500Hz signal to make the buzzer sound. If you want to change the pitch of the buzzer, you will need to play around with the timers. | ||
| You can use the tone () function to produce any sound with regular Arduino, but you can not use this with the nRF52832 Arduino environment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cpulabs This sentence is from
通常のArduinoであればtone()関数で任意の音を出すことが可能ですが、nRF52832のArduino環境ではこれを使うことができません。
Is this unnecessary?
| ## I've set a new UUID but the advertised UUID remains unchanged | ||
| The default sample firmware stores the UUID in Flash memory. In order to make changes to the UUID, the UUID changes must be applied after the device boots up the firmware and override the preloaded UUID value. | ||
|
|
||
| See [Reverting Service UUID to Stock](#service-uuid-reset) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| See [Reverting Service UUID to Stock](#service-uuid-reset) | |
| See [Return the Service UUID to its initial state](../README.md#return-the-service-uuid-to-its-initial-state) |
No description provided.