ESP32-PaxCounter/src/if482.cpp

105 lines
3.1 KiB
C++
Raw Normal View History

2019-01-28 21:47:44 +01:00
/* NOTE:
The IF482 Generator needs an high precise 1 Hz clock signal which cannot be
acquired in suitable precision on the ESP32 SoC itself. Additional clocking
hardware is required, ususally the clock signal is generated by external RTC or
2019-01-29 09:04:31 +01:00
GPS which can generate a precise time pulse signal (+/- 2ppm).
In this example code we use a Maxim DS3231 RTC chip, and configure the chips's
interrupt output pin as clock. The clock signal triggers an interrupt on the
ESP32, which controls the realtime output of IF482 telegram. This is why code in
2019-01-28 21:47:44 +01:00
IF482.cpp depends on code in RTCTIME.cpp.
*/
2019-01-28 21:47:44 +01:00
///////////////////////////////////////////////////////////////////////////////
/*
2019-01-26 12:32:58 +01:00
IF482 Generator to control clocks with IF482 telegram input (e.g. BÜRK BU190)
2021-05-09 00:02:41 +02:00
2019-01-29 09:04:31 +01:00
2019-01-26 12:32:58 +01:00
Example IF482 telegram: "OAL160806F170400"
IF482 Specification:
2019-01-26 12:32:58 +01:00
http://www.mobatime.com/fileadmin/user_upload/downloads/TE-112023.pdf
The IF 482 telegram is a time telegram, which sends the time and date
information as ASCII characters through the serial interface RS 232 or RS 422.
Communication parameters:
Baud rate: 9600 Bit/s
Data bits 7
Parity: even
Stop bit: 1
Jitter: < 50ms
Interface : RS232 or RS422
Synchronization: Telegram ends at the beginning of the second
specified in the telegram
Cycle: 1 second
Format of ASCII telegram string:
Byte Meaning ASCII Hex
1 Start of telegram O 4F
2 Monitoring* A 41
3 Time-Season** W/S/U/L 57 or 53
4 Year tens 0 .. 9 30 .. 39
5 Year unit 0 .. 9 30 .. 39
6 Month tens 0 or 1 30 or 31
7 Month unit 0 .. 9 30 .. 39
8 Day tens 0 .. 3 30 .. 33
9 Day unit 0 .. 9 30 .. 39
10 Day of week*** 1 .. 7 31 .. 37
11 Hours tens 0 .. 2 30 .. 32
12 Hours unit 0 .. 9 30 .. 39
13 Minutes tens 0 .. 5 30 .. 35
14 Minutes unit 0 .. 9 30 .. 39
15 Seconds tens 0 .. 5 30 .. 35
16 Seconds unit 0 .. 9 30 .. 39
17 End of telegram CR 0D
*) Monitoring:
With a correctly received time in the sender unit, the ASCII character 'A' is
issued. If 'M' is issued, this indicates that the sender was unable to receive
any time signal for over 12 hours (time is accepted with A and M).
**) Season:
W: Standard time,
S: Season time,
U: UTC time (not supported by all systems),
L: Local Time
***) Day of week:
2019-03-06 22:56:51 +01:00
not evaluated by model BU-190, use "F" instead for this model
*/
2019-01-28 21:47:44 +01:00
///////////////////////////////////////////////////////////////////////////////
#ifdef HAS_IF482
#include "if482.h"
// Local logging tag
2019-02-27 00:52:27 +01:00
static const char TAG[] = __FILE__;
2022-01-16 19:43:06 +01:00
String IF482_Frame(time_t t) {
2019-02-02 09:15:31 +01:00
2019-03-06 22:56:51 +01:00
char mon, out[IF482_FRAME_SIZE + 1];
2022-01-23 21:12:28 +01:00
if (sntp_get_sync_status() == SNTP_SYNC_STATUS_IN_PROGRESS)
mon = 'M'; // time had been set but sync not completed
else
mon = 'A'; // time has been set and was recently synced
// generate IF482 telegram
// snprintf(out, sizeof(out), "O%cL%s\r", mon, myTZ.dateTime(t, UTC_TIME,
// "ymdwHis").c_str());
2021-05-09 00:02:41 +02:00
2022-01-23 21:12:28 +01:00
// ESP_LOGD(TAG, "[%s] IF482 date/time: %s", ctime(time(NULL), out);
2019-02-23 23:39:45 +01:00
return out;
}
#endif // HAS_IF482