Search results

@Frank, @Paul: Thanks for the input, lowering the priority of the control timer worked for me. my mistake was to set a low number and not a high like 192... @joe_prince: if you look at my code example in the first post you see that your method is exactly what can cause trouble. When not using...

When reading PWM i got "phantom" signals if using a timer for some calculations in the same project. I setup few lines of code so that the problem could be reproduced: #define RCPIN_IN 20 // input pin for RC receiver signal #define DEADBAND 10 // tolerance for the RC...

Still the same problem. problem also appears if opening the "Tools" menu in the arduino IDE. must be some kind of delay when checking installed com ports. but there's no lag when opening the serial monitor with old teensyduino version. i think you could reproduce the problem by installing the...

Just tested this new feature which is very useful to me but encountered a problem: opening the serial monitor is very slow, the lag after click is 3 seconds. it seems that it's searching or probing all serial ports available not only the one used to communicate with teensy. if i remove a...

Thanks Paul, first checked the values for UART_C1, UART_S2, UART_C3, UART_C4 without success then i followed instruction in the above link and was finally able to read data If needed: 0x8F is the correct setting to enable 9 Databits, Odd Parity and 2 Stopbits

Thank you very much, spent a couple of hours before you're code fixed my problem

Thanks Paul, was first confused because the device i try to communicate with is using 9 databits, 2 stopbits and odd parity. so one more question: could 0x89 used as initializer for 9O2 serial mode? Looking at HardwareSerial.h i think this should be correct... #define SERIAL_9N2 0x88 // bit0...

Title says it all: is there any experience/possibility to use this baudrates? Thanks in Advance, Andy

Can teensy readout it's own Vin somehow (without a voltage divider/ADC)? It is possible for some AVR chips as far as i know...

It works :D By setting the I2C IRQ Priority the code works without issues. NVIC_SET_PRIORITY(IRQ_I2C0,0); It doesn't matter if you change the NVIC Priority before or after the start of the intervall timer but i think set the priority before is more safe. I have no success setting the...

Thanks for your answer! I will double check this, maybe as was just a bit confused because of to less coffee and to much debugging ;) Timing is rather critical because the code collects samples to run a FFT on it. Allready tried your suggestion before but (without further optimization) results...

Hi guys, i'm facing problems using the i2c_t3 code from within an IntervallTimer callback (need that for sampling). The following part of code causes the application to hang: i2c_t3.cpp: uint8_t i2c_t3::finish_(struct i2cStruct* i2c, uint32_t timeout) { deltaT = elapsedMicros(); int i =0...

Nunchuck on teensy 3.1 Spend an hour getting the nunchuck to work with teensy 3.1 :p, here's what i found out: - no pullups required on 3.1 - set the cpu speed down to 48MHz to get any data related to the gyro - NUNCHUK_TWI_DELAY_MICROSEC is set to 5 Hope its helpful.