I hereby claim:
- I am amcjen on github.
- I am amcjen (https://keybase.io/amcjen) on keybase.
- I have a public key ASBgceVqmZYML5YKhvUM9YfnF867u95mxCoNMzpQ1qsEPgo
To claim this, I am signing this object:
// ------------------------------------------------------------- | |
// CANtest for Teensy 3.6 dual CAN bus | |
// by Collin Kidder, Based on CANTest by Pawelsky (based on CANtest by teachop) | |
// | |
// Both buses are left at default 250k speed and the second bus sends frames to the first | |
// to do this properly you should have the two buses linked together. This sketch | |
// also assumes that you need to set enable pins active. Comment out if not using | |
// enable pins or set them to your correct pins. | |
// | |
// This sketch tests both buses as well as interrupt driven Rx and Tx. There are only |
static const uart_conf_t uart_config[] = { | |
{ /* Virtual COM Port */ | |
.dev = &SERCOM4->USART, | |
.rx_pin = GPIO_PIN(PB,14), | |
.tx_pin = GPIO_PIN(PB,15), | |
.mux = GPIO_MUX_D, | |
.rx_pad = UART_PAD_RX_2, | |
.tx_pad = UART_PAD_TX_3, | |
.flags = UART_FLAG_NONE, | |
.gclk_src = GCLK_PCHCTRL_GEN_GCLK0 |
#include <Bounce.h> // Bounce library makes button change detection easy | |
const int channel = 1; | |
Bounce button1 = Bounce(1, 5); // 5 = 5 ms debounce time | |
Bounce button2 = Bounce(2, 5); // which is appropriate for good | |
// quality mechanical pushbuttons | |
void setup() { | |
pinMode(1, INPUT_PULLUP); | |
pinMode(2, INPUT_PULLUP); | |
} |
#include <Bounce.h> // Bounce library makes button change detection easy | |
const int channel = 1; | |
Bounce button1 = Bounce(1, 5); // 5 = 5 ms debounce time | |
Bounce button2 = Bounce(2, 5); // which is appropriate for good | |
Bounce button3 = Bounce(3, 5); // quality mechanical pushbuttons | |
void setup() { | |
pinMode(1, INPUT_PULLUP); | |
pinMode(2, INPUT_PULLUP); | |
pinMode(3, INPUT_PULLUP); |
I hereby claim:
To claim this, I am signing this object:
PUSHBUTTON INTERFACE | |
The LTC3101 includes a pushbutton interface that allows a single momentary pushbutton to control the sequenced power-up and power-down of all output rails in coordina- tion with an external microprocessor. In addition, three independent enable pins allow an unused DC/DC converter to be independently disabled and also provide the means to manually implement an alternate power-up sequence. | |
The LTC3101 can be enabled by either forcing PWRON high or by forcing PWRKEY low. In either case, the DC/DC converters (if enabled by their respective enable pin) will power up in the internally fixed default sequence: buck converter 1, buck converter 2, and finally the buck- boost converter. In the typical application, the power-on sequence is initiated when the PWRKEY is driven low by an external momentary pushbutton. Once the microproces- sor is powered up it must assert PWRON high before the pushbutton is released, thereby forcing the LTC3101 to | |
remain enabled. Power-down is usually accomplished by |
to install node: | |
- run: `curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.31.0/install.sh | bash` | |
- Follow instructions |
Verifying that +ethomjen is my blockchain ID. https://onename.com/ethomjen |
Antonio A. Rucci, Chief Security Officer, Ghost Systems, LLC | |
Friday, April 10 at 12:00pm to 1:00pm DMSC, 102 Davidson Mathematics Science Center (Parking can be found in the Brian Whalen Parking complex for $7.00 from the dispenser on the 5th floor). | |
Interoperability Dependencies in the Internet of Things (IoT) | |
Abstract: As business capabilities continue to develop and evolve, our dependencies on technology continue to scale while diminishing our ability to operate in its absence. Security is often an afterthought or oversight in technology design and development, resulting in complex redesign post-process. As we embrace the "Internet of Things" (IoT), we must also embrace the interoperability dependencies of adjacent, independent technologies, policies and laws, which will drive the IoT into the foreseeable future. During this talk, Don Ritzman, Chief Executive Officer; and Antonio A. Rucci, Chief Security Officer, Ghost Systems, LLC, Reno, NV, will address high level strategy and technologies whic |