This commit is contained in:
Lexzach 2022-07-04 18:07:36 -04:00
commit 116e71bf8f
14 changed files with 1281 additions and 0 deletions

2
.gitattributes vendored Normal file
View File

@ -0,0 +1,2 @@
# Auto detect text files and perform LF normalization
* text=auto

5
facp/.gitignore vendored Normal file
View File

@ -0,0 +1,5 @@
.pio
.vscode/.browse.c_cpp.db*
.vscode/c_cpp_properties.json
.vscode/launch.json
.vscode/ipch

10
facp/.vscode/extensions.json vendored Normal file
View File

@ -0,0 +1,10 @@
{
// See http://go.microsoft.com/fwlink/?LinkId=827846
// for the documentation about the extensions.json format
"recommendations": [
"platformio.platformio-ide"
],
"unwantedRecommendations": [
"ms-vscode.cpptools-extension-pack"
]
}

5
facp/.vscode/settings.json vendored Normal file
View File

@ -0,0 +1,5 @@
{
"files.associations": {
"*.tcc": "cpp"
}
}

39
facp/include/README Normal file
View File

@ -0,0 +1,39 @@
This directory is intended for project header files.
A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.
```src/main.c
#include "header.h"
int main (void)
{
...
}
```
Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.
In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.
Read more about using header files in official GCC documentation:
* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes
https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html

46
facp/lib/README Normal file
View File

@ -0,0 +1,46 @@
This directory is intended for project specific (private) libraries.
PlatformIO will compile them to static libraries and link into executable file.
The source code of each library should be placed in a an own separate directory
("lib/your_library_name/[here are source files]").
For example, see a structure of the following two libraries `Foo` and `Bar`:
|--lib
| |
| |--Bar
| | |--docs
| | |--examples
| | |--src
| | |- Bar.c
| | |- Bar.h
| | |- library.json (optional, custom build options, etc) https://docs.platformio.org/page/librarymanager/config.html
| |
| |--Foo
| | |- Foo.c
| | |- Foo.h
| |
| |- README --> THIS FILE
|
|- platformio.ini
|--src
|- main.c
and a contents of `src/main.c`:
```
#include <Foo.h>
#include <Bar.h>
int main (void)
{
...
}
```
PlatformIO Library Dependency Finder will find automatically dependent
libraries scanning project source files.
More information about PlatformIO Library Dependency Finder
- https://docs.platformio.org/page/librarymanager/ldf.html

17
facp/platformio.ini Normal file
View File

@ -0,0 +1,17 @@
; PlatformIO Project Configuration File
;
; Build options: build flags, source filter
; Upload options: custom upload port, speed and extra flags
; Library options: dependencies, extra library storages
; Advanced options: extra scripting
;
; Please visit documentation for the other options and examples
; https://docs.platformio.org/page/projectconf.html
[env:esp32doit-devkit-v1]
platform = espressif32
board = esp32doit-devkit-v1
framework = arduino
monitor_speed = 115200
lib_deps =
marcoschwartz/LiquidCrystal_I2C@^1.1.4

BIN
facp/src/allcharacters.jpg Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 582 KiB

BIN
facp/src/ascii.jpg Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 533 KiB

16
facp/src/eeprom.txt Normal file
View File

@ -0,0 +1,16 @@
Address allocation:
1-6 | "Lexzach" - verify that eeprom is the FACP config eeprom
7 | 0-5 - coding selection
8 | 0-1 - is a key required
9 | 0-1 - is there verification
10 | 1-255 - how long to do verification (value * 0.1 = actual verification time in seconds)
11-71 | 65-90, 45-57, 32, 39 - System name
72 | 0-4094 - EOL resistor lenience
73 | 0-1 - enable EOL resistor
74 | 0-1 - pre-alarm enabled
75 | 1-10 - first-stage time
76 | 0-1 - smoke detector pre-alarm
77 | 1-5 - smoke detector timeout
78 | 0-1 - panel homescreen
79 | 0-1 - audible silence
80 | 0-40 - lcd timeout

BIN
facp/src/eol.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

1083
facp/src/main.cpp Normal file

File diff suppressed because it is too large Load Diff

47
facp/src/menus.txt Normal file
View File

@ -0,0 +1,47 @@
[testing]
- walk test
- silent walk test
- strobe test
- automatic system test
[settings]
- [fire alarm settings]
- - [coding]
- - - Temporal 3 = 0
- - - Marchtime = 1
- - - 4-4 = 2
- - - Continuious = 3
- - - California = 4
- - - Marchtime (slower) = 5
- - enable/disable verification
- - [verification time]
- - - 0.1-25.5 seconds
- - [pre-alarm]
- - - enable/disable pre-alarm
- - - [first-stage]
- - - - [first-stage time]
- - - - - 1-10 minutes
- - - [second-stage]
- - - [smoke detector pre-alarm]
- - - - enable/disable smoke detector pre-alarm
- - - - [smoke detector timeout]
- - - - - 1-20 minutes
- - enable/disable audible silence
- [panel settings]
- - [panel name]
- - - enter panel name
- - [panel security]
- - - None
- - - Keyswitch (pin 33)
- - - Passcode (future)
- - [homescreen]
- - - panel name
- - - [stats for nerds]
- - - - zone input voltages
- - - -
- - [lcd timeout]
- - - 30 sec, 1 min, 5 min, 30 min, off
[advanced settings]
- [resistor lenience]
- - 0-200
- enable/disable EOL resistors

11
facp/test/README Normal file
View File

@ -0,0 +1,11 @@
This directory is intended for PlatformIO Unit Testing and project tests.
Unit Testing is a software testing method by which individual units of
source code, sets of one or more MCU program modules together with associated
control data, usage procedures, and operating procedures, are tested to
determine whether they are fit for use. Unit testing finds problems early
in the development cycle.
More information about PlatformIO Unit Testing:
- https://docs.platformio.org/page/plus/unit-testing.html