Skip to content

Commit 5f94d08

Browse files
committed
Updated README.md and TravisCI config
1 parent e6fb724 commit 5f94d08

File tree

2 files changed

+4
-5
lines changed

2 files changed

+4
-5
lines changed

.travis.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ script:
1818
- arduino --verify --board arduino:avr:uno $PWD/examples/AcquireGPSPosition/AcquireGPSPosition.ino
1919
- arduino --verify --board arduino:avr:uno $PWD/examples/GeneralInformation/GeneralInformation.ino
2020
- arduino --verify --board arduino:avr:uno $PWD/examples/HttpPost/HttpPost.ino
21+
- arduino --verify --board arduino:avr:uno $PWD/examples/Tester/Tester.ino
2122
notifications:
2223
email:
2324
on_success: change

README.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,17 +16,15 @@ really easy, and avoid successive prints or string concatenation.
1616
* Reading of the device states (battery, gps, network)
1717

1818
## Why another library ?
19-
Their is a number of libraries out there which support this modem ([Adafruit's FONA](https://github.com/adafruit/Adafruit_FONA), [TinyGSM](https://github.com/vshymanskyy/TinyGSM) for instance), so why build another one ? None fit the needs I had for a project. FONA is more a giant example for testing commands individually and I was getting unreliable results with it. TinyGSM seems great but what it gains in chips support it lacks in fine grained control
20-
over each modules, which I needed.
19+
Their is a number of libraries out there which support this modem ([Adafruit's FONA](https://github.com/adafruit/Adafruit_FONA), [TinyGSM](https://github.com/vshymanskyy/TinyGSM) for instance), so why build another one ? None fit the needs I had for a project. FONA is more a giant example for testing commands individually and I was getting unreliable results with it. TinyGSM seems great but what it gains in chips support it lacks in fine grained control over each modules, which I needed.
2120

22-
This library is then greatly inspired by FONA, which served as the reference implementation, but mostly only support the features I needed for my project and has been
23-
tested thoroughly and successfully in that configuration. It also tries to reduce the final HEX size as this was a real problem for the project it was built (currently using 30660 bytes out of 30720).
21+
This library is then greatly inspired by FONA, which served as the reference implementation, but mostly only support the features I needed for my project and has been tested thoroughly and successfully in that configuration. It also tries to reduce the final HEX size as this was a real problem for the project it was built for.
2422

2523
It does *not* have the pretention to become the new SIM808 standard library, but can be useful to others as a source of inspiration or documentation to understand how AT commands works.
2624

2725
## Debugging
2826
If you need to debug the communication with the SIM808 module, you can either define `_DEBUG` to `1`, or directly change `_SIM808_DEBUG` to `1` in [SIMComAT.h](/src/SIMComAT.h).
29-
> Be aware that it will greatly increase the final hex size as debug strings are stored in flash.
27+
> Be aware that it will increase the final hex size as debug strings are stored in flash.
3028
3129
## Usage
3230
No default instance is created when the library is included. It's up to you to create one with the appropriate parameters.

0 commit comments

Comments
 (0)