Skip to content
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

Testing and finetuning #141

Closed
wants to merge 5 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
107 changes: 107 additions & 0 deletions docs/hardware/test_procedure.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,107 @@
## TEST PROCEDURE


Check failure on line 3 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Multiple consecutive blank lines

docs/hardware/test_procedure.md:3 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md012.md
### I- System startup

##### 1. Upload the code into the STM32

Check failure on line 6 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Heading levels should only increment by one level at a time

docs/hardware/test_procedure.md:6 MD001/heading-increment/header-increment Heading levels should only increment by one level at a time [Expected: h4; Actual: h5] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md001.md

Check failure on line 6 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Headings should be surrounded by blank lines

docs/hardware/test_procedure.md:6 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "##### 1. Upload the code into the STM32"] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md022.md
##### 2. Connection of different components

Check failure on line 7 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Headings should be surrounded by blank lines

docs/hardware/test_procedure.md:7 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "##### 2. Connection of different components"] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md022.md

Check failure on line 7 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Headings should be surrounded by blank lines

docs/hardware/test_procedure.md:7 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "##### 2. Connection of different components"] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md022.md
##### 3. System power

Check failure on line 8 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Headings should be surrounded by blank lines

docs/hardware/test_procedure.md:8 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "##### 3. System power"] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md022.md

Check failure on line 8 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Headings should be surrounded by blank lines

docs/hardware/test_procedure.md:8 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "##### 3. System power"] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md022.md
##### 4. Start-up

Check failure on line 9 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Headings should be surrounded by blank lines

docs/hardware/test_procedure.md:9 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "##### 4. Start-up"] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md022.md


Check failure on line 11 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Multiple consecutive blank lines

docs/hardware/test_procedure.md:11 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md012.md
### II- Configuration of the operating mode.

Check failure on line 12 in docs/hardware/test_procedure.md

View workflow job for this annotation

GitHub Actions / Run markdownlint

Headings should be surrounded by blank lines

docs/hardware/test_procedure.md:12 MD022/blanks-around-headings/blanks-around-headers Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### II- Configuration of the operating mode."] https://github.com/DavidAnson/markdownlint/blob/v0.31.1/doc/md022.md
##### 1. Enter setup mode
##### 2. Choose the different operating modes (STS, OpayGo Time-based? OpayGo Energy-based)


### III- Entry of token For each mode

#### A. When recharging for the first time
Test the entry of two types of tokens:

##### 1. STS Mode

a- a correct token => supposed to set credit (energy)

b- an incorrect token => supposed to do nothing

##### 2. OpayGo Time-based Mode

a- a correct token => supposed to set time

b- an incorrect token => supposed to do nothing

##### 3. OpayGo Energy-based Mode

a- a correct token => supposed to set credit (energy)

b- an incorrect token => supposed to do nothing


#### B. When the previous recharge is completed
Test the entry of three types of tokens:

##### 1. STS Mode

a- a correct token => supposed to set a new credit (energy)

b- an incorrect token => supposed to do nothing

c- a token already used => supposed to do nothing

##### 2. OpayGo Time-based Mode

a- a correct token => supposed to set a new time

b- an incorrect token => supposed to do nothing

c- a token already => supposed to do nothing

##### 3. OpayGo Energy-based Mode

a- a correct token => supposed to set a new credit (energy)

b- an incorrect token => supposed to do nothing

c- a token already => supposed to do nothing


#### C. When the previous recharge is still in progress
Test the entry of three types of tokens:

##### 1. STS Mode

a- a correct token => supposed to add credit (energy) to the current value

b- an incorrect token => supposed to do nothing

c- a token already used => supposed to do nothing

##### 2. OpayGo Time-based Mode

a- a correct token => supposed to add time to the current value

b- an incorrect token => supposed to do nothing

c- a token already => supposed to do nothing

##### 3. OpayGo Energy-based Mode

a- a correct token => supposed to add credit (energy) to the current value

b- an incorrect token => supposed to do nothing

c- a token already => supposed to do nothing


### IV- Perform a value reset for each mode (Restoration of factory settings)

##### 1. STS Mode
##### 2. OpayGo Time-based Mode
##### 3. OpayGo Energy-based Mode

### V- Changing the configuration password
##### 1. Enter setup mode using old password
##### 2. Replace the old password with the new one
##### 3. Test entering configuration mode using the old password => supposed to do nothing
##### 4. Test entering configuration mode using the new password => supposed to work!
4 changes: 2 additions & 2 deletions firmware/platformio.ini
Original file line number Diff line number Diff line change
Expand Up @@ -18,9 +18,9 @@ framework = arduino
platform = [email protected]
board = bluepill_f103c8_128k

upload_protocol = serial
upload_protocol = dfu
monitor_speed = 115200
#upload_port = COM4 # To upload the code uncomment this line and put the port corresponding to your module on you PC
upload_port = COM6 # To upload the code uncomment this line and put the port corresponding to your module on you PC

# Disable some warning flags for libraries
build_flags =
Expand Down