Create Project Need help?
  • PROJECT STATUS
  • CREATION PERIOD
  • BADGE
Latest comments
Tapetenhobel
Tapetenhobel 2 hours ago
Moin Karl-Heinz, danke fuer den patch, mein NTP funktioniert damit 1a: ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== *adsb .PPS. 1 u 66 64 67 4.220 -3.637 4.774 192.168.178.241 .PPS. 1 u 1 64 167 27.755 -1083.7 728.989 Matthias  
mini-NTP server with GPS
Mathias Clauszen
Mathias Clauszen 5 hours ago
@Karl-Heinz Lohner Danke für das debuggen und die Fehlerkorrekur. Ich denke das in den nächtsen zwei Tagen dann auch die Software mit den änderungen als Zip bereit steht und das Git Repository angepasst ist.  Mit freundlichen Grüßen Mathias
mini-NTP server with GPS
Karl-Heinz Lohner
Karl-Heinz Lohner 9 hours ago
Hallo, nach ein parr Änderungen funktionert  der mini-ESP32-NTP. UBuntu und Windows 7 akzepieren den NTP Server. Der diff mit meinen Änderungen. ------------------------------------- --- ntp_server.cpp.orig    2019-10-22 12:36:38.722558078 +0200 +++ ntp_server.cpp    2019-10-22 15:06:01.305285383 +0200 @@ -86,7 +86,7 @@          if(udp.listen(port)) {          started=true; -        udp.onPacket([](AsyncUDPPacket packet) { +        udp.onPacket([](AsyncUDPPacket& packet) {             uint32_t processing_start = 0;             ntp_packet_t ntp_req;              @@ -111,8 +111,8 @@            ntp_req.refTm_s = ntohl(ntp_req.refTm_s );                  ntp_req.refTm_f = ntohl(ntp_req.refTm_f  );                  -          ntp_req.origTm_s = ntohl( ntp_req.origTm_s );       -          ntp_req.origTm_f = ntohl( ntp_req.origTm_f );       +          ntp_req.origTm_s = ntohl( ntp_req.txTm_s );       +          ntp_req.origTm_f = ntohl( ntp_req.txTm_f );                              ntp_req.rxTm_s = ntohl( ntp_req.rxTm_s );         @@ -136,7 +136,8 @@            ntp_req.rxTm_s= processing_start;            ntp_req.rxTm_f= 0;            /* UNIX Start is 1.1.1970 and GPS Start is 1.1.1900 */ -          ntp_req.refTm_s=  ntp_req.refTm_s +  NTP_TIMESTAMP_DELTA; // We need to add 70 Years + //         ntp_req.refTm_s=  ntp_req.refTm_s +  NTP_TIMESTAMP_DELTA; // We need to add 70 Years +          ntp_req.refTm_s = processing_start;            ntp_req.refTm_f = 0;                        ntp_req.txTm_s = fnc_read_utc()+NTP_TIMESTAMP_DELTA; ---------------------------------- Karl-Heinz
mini-NTP server with GPS
dan ocho
dan ocho 15 hours ago
How do I program this base and propeller?
High-end propeller clock [120732]
Karl-Heinz Lohner
Karl-Heinz Lohner 1 day ago
Hallo, mit meiner Entwicklungsumgebung: 180622_1_1-11.zip Arduino IDE 1.8.10 Arduino-esp32 1.0.4 crashed det ESP32 während "packet.write" mit einer assertion: Switch to PPS Update RTC Timestamp is 1571554227 Timestamp is 1571554227 assertion "pbuf_free: p->ref > 0" failed: file "/Users/ficeto/Desktop/ESP32/ESP32/esp-idf-public/components/lwip/lwip/src/core/pbuf.c", line 765, function: pbuf_free abort() was called at PC 0x400ed617 on core 1 Backtrace: 0x4008d008:0x3ffcf630 0x4008d239:0x3ffcf650 0x400ed617:0x3ffcf670 0x4010f0ab:0x3ffcf6a0 0x400df8d7:0x3ffcf6c0 0x400df927:0x3ffcf750 0x40088f81:0x3ffcf780 Rebooting... ets Jun  8 2016 00:22:57 Dies kann durch die Änderung: udp.onPacket([](AsyncUDPPacket packet) { in udp.onPacket([](AsyncUDPPacket& packet) { behoben werden. Leider akzeptiert der ntpdate meines 18.04.3 LTS (Bionic Beaver) den ESP32-NTP nicht als NTP Source: ntpdate[4691]: no server suitable for synchronization found Hier ein Auszug vom tcpdump: Ubintu: *.130, NTP: *.199 14:26:41.437389 IP (tos 0x0, ttl 64, id 49538, offset 0, flags [DF], proto UDP (17), length 76)     192.168.2.130.123 > 192.168.2.199.123: [bad udp cksum 0x86e3 -> 0x2604!] NTPv4, length 48         Client, Leap indicator: clock unsynchronized (192), Stratum 0 (unspecified), poll 3 (8s), precision -6         Root Delay: 1.000000, Root dispersion: 1.000000, Reference-ID: (unspec)           Reference Timestamp:  0.000000000           Originator Timestamp: 0.000000000           Receive Timestamp:    0.000000000           Transmit Timestamp:   3780649601.437255331 (2019/10/21 14:26:41)             Originator - Receive Timestamp:  0.000000000             Originator - Transmit Timestamp: 3780649601.437255331 (2019/10/21 14:26:41) 14:26:41.498058 IP (tos 0x0, ttl 255, id 94, offset 0, flags [none], proto UDP (17), length 76)     192.168.2.199.123 > 192.168.2.130.123: [udp sum ok] NTPv4, length 48         Server, Leap indicator:  (0), Stratum 1 (primary reference), poll 3 (8s), precision 0         Root Delay: 0.000015, Root dispersion: 0.000015, Reference-ID: PPS^@           Reference Timestamp:  2208988800.000000000 (1970/01/01 01:00:00)           Originator Timestamp: 0.000000000           Receive Timestamp:    3780649602.000000000 (2019/10/21 14:26:42)           Transmit Timestamp:   3780649602.000000000 (2019/10/21 14:26:42)             Originator - Receive Timestamp:  3780649602.000000000 (2019/10/21 14:26:42)             Originator - Transmit Timestamp: 3780649602.000000000 (2019/10/21 14:26:42) Sind Reference Timestamp, Originator Timestamp und Originator - Receive Timestamp, Originator - Transmit Timestamp wirklich OK? Die BAD Checksum vom Ubuntu scheint nicht zu stören. Da meine FB als NTP Server akzeptiert wird. Karl-Heinz  
mini-NTP server with GPS