git.scottworley.com Git - tattlekey/blob - client/config.c

   1 #include "config.h"
   2
   3 /* Wi-Fi credentials */
   4 const char config_wifi_ssid[] = "THEWIFISSID";
   5 const char config_wifi_pass[] = "THEWIFIPASSWORD";
   6
   7 /* Network address of the server to contact */
   8 const char config_tattle_server_ip_address[] = "192.168.10.10";
   9 const u16_t config_tattle_port = 29803; // 'tk'
  10
  11 /* For distinguishing reports from multiple tattlekey devices. */
  12 const u16_t config_this_tattler_identity = 1;
  13
  14 /* Which GPIO pin is the button connected to?
  15  * The button should span this pin and ground, connecting this pin to ground
  16  * when pressed.
  17  * https://projects.raspberrypi.org/en/projects/introduction-to-the-pico/10
  18  * recommends pins 18, 22, or 28. */
  19 const uint config_button_pin = 18;
  20
  21 /* Don't bother reporting each separate button press when it is pressed many
  22  * times in short succession.  (We also use this to de-bounce. :) */
  23 const u32_t config_minimum_seconds_between_button_presses = 1;
  24
  25 /* Send each report multiple times. */
  26 const uint config_resend_count = 5;
  27
  28 /* These control the size of the per-send-count press queues.
  29 When the button is pressed more than config_maximum_queue_size times
  30 within the resend interval, some presses will be reported fewer
  31 than config_resend_count times. This is usually fine because it's
  32 the old, longest-delayed, most-redundant reports that get dropped;
  33 fresh, timely reports of new button presses will not get anywhere near
  34 config_resend_count in a resend interval because the early resend internals
  35 are so short.  */
  36 const uint config_maximum_queue_size = 512;
  37
  38 /* This is paranoia about unanticipated delays.  Setting this to zero
  39 would probably be fine, but imposing a minimum queue size is an easy
  40 safety measure. */
  41 const uint config_minimum_queue_size = 32;