andry/EMS-ESP32
1
0
Fork 0
mirror of https://github.com/emsesp/EMS-ESP32.git synced 2025-12-06 15:59:52 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
gl3nni3
2019-03-07 21:04:57 +01:00
committed by GitHub
parent ab1a941b81
commit 4a2c324e4a
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -21,7 +21,7 @@ There are 3 parts to this project, first the design of the circuit, secondly the
- [EMS Polling](#ems-polling) - [EMS Polling](#ems-polling)
- [EMS Broadcasting](#ems-broadcasting) - [EMS Broadcasting](#ems-broadcasting)
- [EMS Reading and Writing](#ems-reading-and-writing) - [EMS Reading and Writing](#ems-reading-and-writing)
- [EMS](#ems-plus) - [EMS Plus](#ems-plus)
- [EMS Plus byte layout](#ems-plus-byte-layout) - [EMS Plus byte layout](#ems-plus-byte-layout)
- [The ESP8266 Source Code](#the-esp8266-source-code) - [The ESP8266 Source Code](#the-esp8266-source-code)
- [Special EMS Types](#special-ems-types) - [Special EMS Types](#special-ems-types)
@@ -149,14 +149,6 @@ A package can be a single byte (see Polling below) or a string of 6 or more byte
``[src] [dest] [type] [offset] [data] [crc] <BRK>`` ``[src] [dest] [type] [offset] [data] [crc] <BRK>``
The first 4 bytes is referenced as the *header* in this document. The first 4 bytes is referenced as the *header* in this document.
## Ems Plus
In this chapter we will report our findings on the ems plus.
### EMS Plus byte layout
| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| - | - | - | - | - | - | - | - |
| 18 | 00 | FF | 03 | 01 | A5 | 28 | 46|
|transmitter| receiver | ems plus mark | temperature set point marker | offset | ? | value | cnc
### EMS IDs ### EMS IDs
Each device has a unique ID. Each device has a unique ID.
@@ -206,6 +198,14 @@ Following a write request, the `[dest]` doesn't have the 8th bit set and after t
Every telegram sent is echo'd back to Rx, along the same Bus used for all Rx/Tx transmissions. Every telegram sent is echo'd back to Rx, along the same Bus used for all Rx/Tx transmissions.
## Ems Plus
In this chapter we will report our findings on the ems plus.
### EMS Plus byte layout
| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| - | - | - | - | - | - | - | - |
| 18 | 00 | FF | 03 | 01 | A5 | 28 | 46|
|transmitter| receiver | ems plus mark | temperature set point marker | offset | ? | value | cnc
## The ESP8266 Source Code ## The ESP8266 Source Code
`emsuart.cpp` handles the low level UART read and write logic to the bus. You shouldn't need to touch this. All receive commands from the EMS bus are handled asynchronously using a circular buffer via an interrupt. A separate function processes the buffer and extracts the telegrams. `emsuart.cpp` handles the low level UART read and write logic to the bus. You shouldn't need to touch this. All receive commands from the EMS bus are handled asynchronously using a circular buffer via an interrupt. A separate function processes the buffer and extracts the telegrams.