Search results

Well. Getting out the meter really did help me sort this out. It's now solved. I was not jumpering tracks across the two sections of hot and ground on my long breadboard. Gah! And yes, as maitou said, no external resistors are needed for this board, it turns out.

If only. Don't have one at hand. One thing I can say for sure is that the I2C pressure sensor board works because I tested it on another generic arduino. Will post a picture tomorrow when I am at work. Thanks.

Nice catch. I just tried that but it doesn't seem to change anything. Its always been the case that, with the Adafruit library, the code would claim to "see" the board, but couldn't retrieve any data. Same as now, when I changed to using the Wire2 in the begin line. Output: MPRLS Simple...

Thanks Manitou. Yes, I "even bothered" the lib examples. As stated clearly in my first post. I was not clear about using the wire2 constructor, I didn't see it documented clearly what I should do.

https://www.adafruit.com/product/3965 So I went and bought a pressure sensor board from Adafruit thinking that it would run fine on the Teensy 3.6 over I2C. So far, I am so wrong... Adafruit has their own dead simple library which base off of the Wire.h library but I know that's not going to...

Theoretically, couldn't you also enable the FTM1 and FTM2 after setting a different default timer and renaming the TeensyDelay to another name twice, to have a total of 16 timers for teensy 3.2? It might be nice to have an instantiation init call on the class that allows one to choose the...

Life==SAVED! Thank you! I think you might need to change your addChannel to addDelayChannel in your examples Readme.md file, btw. Could someone tell me what the functional difference is between Paul's timers and these? Is there a difference? I noticed that the teensy 3.2 has only 2 FTM...

Sure. I get that. But it makes sense to me to have a little more documentation at hand and maybe even a little function that simplifies the understanding of context for the various parameters. An example fragment of code even with some words that explains what is being achieved?

Ugh. Yes. Looks like page 2197 gets into the meat of all the gazillion settings you can theoretically use to adjust capacitance sensitivity: http://www.nxp.com/assets/documents/data/en/reference-manuals/K66P144M180SF5RMV2.pdf But it's not much that I can actually use in short order. I was...

Ok, it happened again. 20:31:44.651: Teensy Loader 1.35, begin program 20:31:44.753: Listening for remote control on port 3149 20:31:44.754: initialized, showing main window 20:31:44.896: remote connection opened 20:31:44.897: remote cmd: "comment: Teensyduino 1.35 - MACOSX...

Got the serial port working. Will definitely send more complete diagnostics, next time this happens.

I think I might have just blown the opportunity to grab this data as I upgraded both the teensyduino and arduino software to 1.35 and 1.8.1. I can confirm that there IS a .hex file with permissions that seem appropriate (owned by me). TBC. Can't even get the teensy to be seen by the Mac at...

Hi Paul. I have been getting the infamous "this should never happen" error message. I have gotten this error on prior versions of arduino/teensyduino as well. Related to this, my arduino/usb port connection to the teensy has always seemed to be super sketch (as in, I have had all matter of...

I was simply responding to the non-helpful comment that this information was available on the card, not whether the information is "discoverable". Yes, I understand that it's impossible to fit all the complex information about timers on the card, and I have no issues with that. Very much...

Where's the information about PIT and FTM timers? Nowhere.

No, it isn't.

I did try the button a number of times. It didn't seem to change anything. I was always able to upload the code without the button, no problem. I was hoping pushing the button would make it behave differently in terms of running the code (which I now understand to mean seeing the device on...

BTW. The bluetooth device was never selected on the arduino IDE. Bluetooth and the arduino devices showed as available but neither were selected after a new insert in this case. Seems like sometimes it autoselects correctly, sometimes not. Though it would consisently autoselect for one...

One extra little question though... Why is it that the code would upload fine to the teensy (checked the teensyduino logs) and yet the port isn't selected in the arduino ide? I can appreciate that they are two separate processes and so, therefore... But I wonder if the teensyduino code is...

Ok. We have a winner. Paul. I still don't understand why it would behave differently with two different teensy's as it did but when I manually reselected the port, the teensy that would never work came back to life even with the while(). Good thought defragster. Now that I am a little...

The while(!Serial) was commented out because it is what seemed to cause the teensy to fail (well, one of the teensy's anyway). It was uncommented in the scenario I first described. This "while" line is already put before the LED_BUILTIN lines and is placed right after the Serial.begin(9600)...

// Play tones in 4 different coils const int speak1Pin = 9; // Teensy3 has Speaker on pwm digital pin 9 const int speak2Pin = 10; const int speak3Pin = 3; const int speak4Pin = 4; const int speak1Dir = 11; const int speak2Dir = 12; const int speak3Dir = 7; const int speak4Dir = 8; //const int...

// Play random tones in 4 different coils const int speak1Pin = 9; // Teensy3 has Speaker on pwm digital pin 9 const int speak2Pin = 10; const int speak3Pin = 3; const int speak4Pin = 4; const int speak1Dir = 11; const int speak2Dir = 12; const int speak3Dir = 7; const int speak4Dir = 8...

No includes. I tried to find the code tags in the form but they seemed to be missing, so I thought manually putting on <code> would work. Apparently not.

Fair point, Paul. Rebooting my computer is one idea but does it explain why both teensy wont run the code on a usb power source other than my computer? Maybe. Yes, it compiles on both teensy's but I don't think the compile phase is hardware depended, so that should't matter. No other...

In both cases my serial monitor is closed, btw.

Ok, thanks for the improved code advice, but it still doesn't explain why one Teensy consistently works while the other Teensy consistently will not.

...yes, and...

So I have two Teensy 3.2 MCU's and both seem to fail differently due to the following code fragment: void setup(){ randomSeed(analogRead(0)); // pinMode(GSR,INPUT); analogWriteResolution(8); Serial.begin(9600); while (!Serial); pinMode(LED_BUILTIN, OUTPUT); pinMode(speak1Pin...

This is AWESOME Maxbot! Glad to see this.

Thanks for the clarification.

Hi Folks, I understand, from various postings and conversations, that Teensy 3.6 has 4 independent timer "blocks" that would allow for one to use 4 different values for analogWriteFrequency (as stated in the PWM section https://www.pjrc.com/teensy/td_pulse.html) , but it still doesn't clarify...

Fair enough. I can say that I feel more information about Timers and PWM should be provided somewhere more central (perhaps as one of the example sketches). I spent more thrash time than I feel I should have puzzling over and eventually figuring out why I couldn't have different PWM values in...

Thanks tni for that bit of c++ wizardry. I'll store that in my brain somewhere and hope it stays. Paul. Yes, I know there's only 4 timers, I just wanted to pinch on code space. Also, it seems that there are 4 possible physical FTM channels amongst the pins for the 3.6 teensy (which isn't...

It sure would be great to have which pins (channels) work with which timers documented on that card.

Thanks tni. I'll try this if what your suggesting is true. It's annoying to have to write separate functions for each different pin, when I am only doing the same thing over and over. So I need to address this as a kind of array like you have it? Speak4Timer.begin([]{Speak(pin);}, 700); I...

void Speak(int pin){ if (count1%2) analogWrite(pin,0); else analogWrite(pin,255); //set the PWM to the just-read sample, this will average out because of the speaker’s inertia to a position count1++; // increment sample } Speak4Timer.begin(Speak, 700); Compiler gives me hell about not...

Yes. I eventually settled on the 1.6.11 and it, mostly, is working well. Thanks! The one problem I am having (and I don't think it's a Teensyduino problem) is that everytime I restart the Arduino app, my mac seems to think that it's a first time install.

Still has the old 3.4 and 3.5 board name tab labels.

I can see getting more into multichannel ADC to DAC stuff via the timers, so again, more channels is better. More independent channels is better better better!

Thanks Kurt. This mostly answers my questions. I'm guessing that the table 3.4 is meant to be 3.5 and 3.5 is meant to be for the 3.6 teensy?? I did look at one excel sheet early on but I couldn't see any timer info. It looks like you are one of the people that is more focused on the timer...

Sorry if this question has been answered (somewhere in this really hard to search mass). Wondering about the number of independent timer blocks and which pins will be assigned to which timer, etc? Looking for information similar too:

*nod* Thanks. I have a bad habit of answering my own questions after I post to these forums...

OK. I figured out how to get this running without the pgmspace libraries. (Sub pgm-read-byte for just an int cast). Still confused about how much available space i should expect though...

I now get errors about overflowing flash by some 114196 bytes which I am puzzled by. If I just do a Unix ls-alh on the files I have the header files only use up 2M of space. Aren't I supposed to have 32m of space? I see conversations about not using the pgmspace commands at all with the newer...

Thank you. Im not super fluent on the ins and out of these data types. That solved the warnings.

BTW. I think I the Arduino IDE has some kind of problem with the scroll window in the error/warning section getting overfull. In my case, I have a bunch of "Warning: narrowing conversion of '123' from int to const signed char inside { }". This likely comes from the way my data is declared in...

Thanks for the advice. I have been reticent to go to a beta given that the supposidly stable IDE doesn't even work very well. As it happens, my code does now compile but something seems to be eating up my CPU even when idle with this 1.6.9 Arduino IDE.

ARgh. So now arduino basically hangs and often never finishes compiling now that I have "upgraded" my IDE to 1.6.9 and added teensyduino 1.29. Great.... I do get lots of warnings about narrowing my int to unsigned chars but I always got those warnings and stuff worked. Arduino now compiles...

ARgh. So now arduino basically hangs and often never finishes compiling now that I have "upgraded" my IDE to 1.6.9 and added teensyduino 1.29. Great.... I do get lots of warnings about narrowing my int to unsigned chars but I always got those warnings and stuff worked. Arduino now compiles...