Search results

Maybe something like this..? http://www.instructables.com/id/how-to-defuse-an-LED/

Found something quite interesting. Not very useful for this but still

This got me thinking about how delete[] knows the size of the array. Turns out there's a good discussion on it over here The two methods commonly done by compilers are: over-allocation associative array I try to use new[] as little as possible personally. I like to know exactly how much memory...

If the array is fixed you want to define it statically. Then keep track of how much it actually contains seperately int myArray[MAXSIZE] int numOfDataPoints = 0; // Add data point to array myArray[numOfDataPoints++] = newVal; // Remove end data point from array numOfDataPoints -= 1;

Pictures of the board would be a good start. Is this part of a keyboard? What is this 'assembly' part I can't find a reference to it If the device is an I2C slave things will be more tricky if you do want to reverse engineer the I2C protocol

Have a look at using wavelet transforms for reducing noise. I've had good results with this in the past Right leg drive systems can help to increase the CMRR

Hmmm, perhaps just rewrite the init and ledon commands from scratch. The datasheet seems pretty clear

Replace all instances of word with uint16_t

Yep, either that or modify the source code

Pin 8 is the ICP1 (Input Capture Pin 1). As there is only one of these you can not switch the pin Unfortunately this is also the RX pin which is probably needed for your TFT LCD. Can you post the part number of your LCD? You maybe able to drive it with just the TX pin (Pin 9)

This looks really dodgy See this for why. The Teensy is almost certainly 32bits for a word and in this case it should be 16bits

You can always use a zener diode to protect from overvoltage

Did you try my example code? You can't transfer more than one byte at a time. You can do multi-reading of bytes sure but you still have to have an acknowledgement between bytes. See Page 36

See the following explanation: Actually reading #31 I see this may not be true. The device does support multi-reading as described in Page 36. This does state however: Because of this we must use: Wire.requestFrom(address, quantity, TRUE) //address, quantity, stop

You can't typecast a signed 8 bit value to a signed 16 bit value. Well you can but 0xFF(-1) will become 0x00FF(127). Assuming Char is signed in this case which may not be true If you're after a signed 16 bit value from a register you probably want the following: int16_t...

Shouldn't it be: out3 = out1 | (out2 << 8);

Oh wow, thanks for the pointer to that library. His explanation of Kalman Filters are really rather good This should give you a serious hand in understanding it. I wish I found this sooner when I was doing sensor fusion!

... I'm really struggling to see what you're doing here. Don't you just assign a function to a special area in the linker. Then in the linker you mark that area as OVERLAY? Such as in: http://codingrelic.geekhold.com/2011/01/overlays-not-yet-extinct.html

Looks like a very cool project, congratulations on the 100A discharge! The kalman filter for the propsheild is (I imagine) deeply tied into the use of Quaternions and you'll find most of the code is working with that. This is because the filter needs to operate in 3D with that extra 1D to...

... woops, yes you are quite right! I was thinking of data plotting for some reason More than possible if your ADC interrupt is triggering fast enough, try the double buffered version Yeah you don't see unions discussed so much in education these days. It's non-portable sure but I never find...

Isolate the CLK with a GND line. MOSI and MISO can go together as they probably won't be transmitting at the same time. SS can go wherever unless it toggles a lot which it normally doesn't. Ground all unused cables at both ends

If you wish to use SPI for this either reduce it's speed or use shielded CAT5 cables. I'd recommend doing both At 3 feet you probably want to start considering a different communication protocol I2C I'd consider to suffer from the same issues. It is by default slower though

Surely with a board this size you should increase the pin count right? Multiple PCI-e slots in parallel would be good with tristate buffers Actually I take that back, I see what you're going for here. I'd be very interested to know how you've done those solderless push connects As a crazy idea...

Ouch, looks like a painful task. Just use this: https://www.cirrus.com/en/pubs/proDatasheet/CS8416_F3.pdf Or https://www.cirrus.com/en/pubs/proDatasheet/WM8804_v4.5.pdf

Beep boop http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/17302.html Also you'll want to read this for the linker: ftp://ftp.gnu.org/old-gnu/Manuals/ld-2.9.1/html_node/ld_22.html

I believe the Teensy LC did. Why don't you just use a voltage divider to bring your battery down to 1.2v?

Desolder the bootloader chip.?

The Teensy 3.0 only has a 3.3v and 1.2v reference. Is this what you are using?

.. What simulator is this? Also the Teensy can only read 0->3.3V. You'll have to voltage divide

This is probably to limit the maximum current in case it's resistance drops to a low value I'm not surprised it floats though, I imagine it has some capacitance just looking at how it's constructed

Can you attach this to an oscilloscope and check the signals are actually noisy?

I use Kinetis Design Studio which is free and will allow you to develop and program any Kinetis device all from within one application. It certainly is not everyone's cup of tea though The hex file generated on compiling your code is effectively the raw machine code that your device will run...

I'm glad this has given you the speed upgrade you were looking for! It's always good to keep your time specific code at a high priority and to reduce it's processing time as much as possible It is very unlikely you are dropping packets due to the way the USB transmission works. Your samples are...

Just stick the same microcontroller on the board and bring out the JTAG pins. Then use a Segger J-Link to program the hex file in

Nordic Semiconductor do a range of SoC bluetooth devices. Have a look at the RFduino for example The ESP8266 is the same sort of thing but WiFi. It can also be programmed from the Arduino enviroment Both are very compact and are available in small boards if you don't wish to make your own Why...

Give this a try perhaps? /** * TeensyADC - High speed audio sampling with the teeny 3.2 ARM board This code samples the ADC on the teensy3.2 at * the highest stable rate possible and dumps that data out the USB port using a double buffer. The purpose of * this is for high speed...

You should always shield analogue signal wires. Also decouple the microphone VCC to GND at the device Buff0/1 should be volatile as your interrupt changes them If you want high speed I'd trigger a DMA to transfer the ADC0 output into a circular buffer and interrupt on complete. You could use...

I use the Segger J-link EDU to program the MK20 over JTAG. There are some serial bootloaders floating around that you can then use to program the device from the pc (or other device) from that stage forth If you give us some information on the project we can probably give you better advice

1) Yes that's correct, although don't forget to set the Teensy to use the 3.3V reference for the ADC. This is done with analogReference() 2) No idea. I believe the ones on the top are 5V tolerant and the ones on the bottom aren't 2.2?) Nope, you want to measure the voltage between the 'wiper'...

74LS241 All pins that output from the MKL02 to the MK20. All MKL02 input pins can be ignored. Check the SWD protocol for which pins are inputs/outputs Enable/disable the tristate buffer from a jumper The MK20 should have a pullup on the RESET line

The MKL02 is probably being parasitically powered. Paul hasn't programmed in a disable pin for the MKL02 so your only option is to insert a tri-state buffer chip (hint hint for the upcoming board Paul :rolleyes:) Are you trying to get a board you have large multiples of working? If not I'd just...

You need a pull up resistor on the RESET line else when the device is powered down the K20 has a floating RESET line. This could cause it to reset continuously or not even start Also just for the record if you're not using the internal ADC you don't have to use so many components around the...

This is impressive stuff! A little overkill, I've had these chips running on breakout boards but it's nice to see such an eye for detail

I can't see anything wrong with your code. Here's what I feel should work though: #include <Bounce.h> #define HWSERIAL Serial1 Bounce button2 = Bounce(2, 10); Bounce button3 = Bounce(3, 10); Bounce button4 = Bounce(4, 10); Bounce button5 = Bounce(5, 10); void setup() { pinMode(2...

Do you have any Teensy 3.x that works?

Can you post your latest version of your sender sourcecode?

Hey Ryan, use the code tags to wrap your code next time just to ease our eyes a little! Here's my envisioning of what you're trying to do. Where possible stick to good naming and indentation conventions #define HWSERIAL Serial1 //Teensy Requires you to use Serial1, Serial2, or Serial3 instaed...

Welcome to the forum Ryan, Everytime you call HWSERIAL.read() your program reads the oldest value recieved by HWSERIAL, returns it and then deletes it. This is the basic principle of FIFO (first in first out) So say you send 'a' If you do this on the recieve side: if (HWSERIAL.read() == 'b')...

Yep of course

U5 looks a little dodgy yeah. You have a lot of solder going on there so I'll assume you're using solder paste. You'll find it very hard to apply the right amount without a stencil What I find useful if I am using solder paste like that is to do exactly what you've done but go over all the...