Neat project! I don't think I've seen PET film used as a sensor before. I started looking at trying to use a Magnetospeed sensor, but had difficulties seeing the signal on my o'scope while also getting a reading. I've always wanted to include air/barrel temperature as well as time of...
Are the pins using shared interrupts or is there an interrupt per pin? I assume I'd want to distribute things across as many interrupts as possible. Also, I totally forgot about the Teensy-LC, seems like that should work too?
I'm looking at building a project using a Teensy 3.1/3.2 with 4-12 Melexis MLX90614 IR temp sensors. The sensors support SMBus (I2C) as well as PWM output, but I'd like to use the PWM mode since it means I won't have to assign a unique slave ID for each sensor and means I can read the...
Wow, ok, yeah, looks like prices have come down a fair bit since last I looked around. Looks like the Ublox Neo-6M w/ ant is about $15USD on ebay. That makes things a lot more interesting!
Interesting. I'm currently working on an astronomy related Teensy 3.1 related project: https://github.com/synfinatic/teensy-dsc
Right now I just support reading two encoders and provide a counter readout to software like SkySafari, but I'm strongly considering implementing Taki's work in order...
Yeah, sadly, I'm not really setup for doing reflow work.
Yeah, it would probably be easier if the edge holes were cut in half to make it easy to surface mount. Then I easily could do plated holes under the various pads and just solder them directly from under the PCB. That wouldn't be too...
Actually, I just need to electrically make contact with the D+/D- pads on the Teensy to the custom PCB below. No need for strain relief or anything like that since the other USB connector will also be soldered to the PCB and I'll use traces to connect things up. I just can't figure out a...
Any suggestions for connecting the USB D+/D- pins to a PCB? I'd like to expose a USB port for my project, but would rather not use the one built in on the Teensy 3.1.
I've found some references to pogo pins, but I haven't found any which are short enough for mounting in the short space when...
LOL. You're right. He clearly says " but Teensy3 is not 5V tolerant. " And clearly my ability to understand the meaning of 3 letter words is lacking. :)
Thanks Michael!
So I was doing some searches & reading and came across this thread:
http://forum.pjrc.com/threads/24147-Encoder-library-missing-pulses
Now I realize it is for the Teensy 3.0, not 3.1 but there was talk that the 3.0 was "5V tolerant" just like the 3.1 is and that doesn't mean you should always...
As for the RasperryPi idea: It could be done and I'm plenty Linux experienced to make it work... it just makes things more complicated then I'd like for how complex this problem really is. For example, now I have two different configurations to manage- networking on the Pi and various other...
Yeah basically it's two TCP2UART's, a third port for a different protocol and ideally a fourth port running a HTTP server. Although I could make the 3rd port intelligent and automatically figure out if the client is speaking HTTP or some other protocol I guess. It just would be cleaner to run...
Did you find a good breakout board for it? So far the only two I've been able to find are:
https://oshpark.com/shared_projects/9vAB5zCG
and
http://www.inmojo.com/store/jeff-rowberg/item/wf121-wifi-breakout-board/
The first doesn't breakout a lot of the pins and the second requires the ground...
Wow, thanks for all the feedback so far everyone. I definitely wouldn't of come up with most of these on my own!
I want to read up on the Blugiga WF121 a bit more since that would be the cleanest I think. I was able to download the BGscript examples and docs and it seems really simple to do...
I'm hoping someone here might be able to give me a hint on a WiFi solution that I can integrate with a Teensy 3.1. Specifically, I'd like a WiFi module which has the following features:
1. Soft/Limited AP mode (just needs to allow 1 client to connect)
2. DHCP Server
3. Ability to...
So I'm working on a project utilizing a teensy 3.1 to read some encoders. First I hooked up some cheap rotary encoders and long story short, I found that the encoders shouldn't be powered (3.3V), but rather the central pin should be grounded. I didn't understand that so I started reading...
Version 1.19 in teensy3/avr/pgmspace.h:41
#define strncpy_P(a, b, n) strncmp((a), (b), (n))
would not be correct.
#define strncpy_P(a, b, n) strncpy((a), (b), (n))
Works better. :)
The library is here: http://arduinowifly.sourceforge.net/
I've got my own fork, on github so I'll be sure to send the original author the necessary changes.
So I'm trying to use the WiFlySerial library with my Teensy 3.1 and I'm having some problems with my program crashing or just behaving oddly. I've tracked it down to it's use of pgm_read_word(). The same problem happens with the "Arrays of strings" example code here...
Well I finally found my old Acer netbook running Windows 7... That recognizes the Teeny's and is able to program them. Of course, just using that slow thing makes me want to pull my hair out. Would love it if anyone had any suggestions on getting things to work under OSX again.
Well I'm guessing this must be an incompatibility/bad driver under 10.9.4 as I'm having the same problem on another Mac running the same OS version. Anyone know of a 3rd party driver I might try?
So I've used at least 4 Teensy 2.0 boards for various projects in the past always worked great. Didn't use them for a few months and now I try plugging in a new board to my Mac running OSX 10.9.4 and Blinky is running, but no new serial port is detected in the Arduino.app (1.0.5) and no new...