Search results

I do that all the time putting on QFN parts. After using the heat gun to melt the solder paste, I'll flood the pins with sticky flux and run a very fine tipped soldering iron along the pins and the solder cleans up perfectly. I use Amtech SynTECH solder paste, it's supposed to have a shelf life...

I'm using a OSH Teensy 3.1, Arduino 1.0.6 and Teensyduino 1.2 This page: http://pjrc.com/teensy/td_pulse.html Contains the sentence: The value is between 0 to 255, where the higher the value, the more time the signal remains high. The value is referred to in percentage terms as "duty cycle"...

Well , Paul told you how to do it so my question is moot, but it's not that hard to bit bang serial at reasonable baud rates. Ira

You're right, the difference is on clearance tab of the DRC dialog. Osh has same signal spacing set to 6 and Itead has it set to 0. It's more a setting for you, as that will not effect Osh's ability to make a PCB for you. That check is is more about design standards and either he neglected to...

What baud rate?

I think the issue is the layers you have selected, turn some layers and I'd guess most of those errors will go away. The likely problems are 29-30 and 39-43. Those are not Osh Park errors. I put holes in the pads under QFNs and Osh builds them with no problems. Ira

You seem to install the libraries in Program Files. Users should not touch files in that folder and if they do, too bad. If they want to modify a library it should be copied or moved to their Arduino folder in My Documents or where ever they choose. I believe the only proper Windows like...

No idea if you consider this a bug, but if you install it over an older version where you checked, include all libraries, and don't check include all libraries, I don't think it updates or uninstalls the unselected libraries. Problem being all the old versions of the libraries are still there. Ira

A teensy can not drive a fan directly, but it can drive a FET or transistor that can drive the fan. Ira

Though it might seem intimidating, if you can get CAN to work, it's sort of perfect for something like this.

Would watchdog make more sense like this? I really dislike delay() and it's pretty easy on a Teensy3 to set up a millisecond clock so you know when it's time to kick the dog. I've set it so it resets the watchdog every 3 milliseconds. You need to make it at least 2 as even set to 2 it can be...

I just installed 1.6 and then Teensyduino 1.20 Release Candidate #3. It seems to work fine but during the Teensyduino install I said to install all libraries and now my builds are much slower as if it's trying to link them all in. Is there someplace I can say I don't want that?

.6ma might not be enough to see the LED in a bright room. Did you possibly mean 6ma?

I would also suggest that learning the 2 really simple equations will help you a lot. That's all that LED site does but it certainly gave you a misleading answer. Leading you to believe that a 1 ohm resistor will do anything in series with a LED is a serious mistake. Ohms law, E = IR, says...

And if you're doing more than a couple I'm a big fan of the ULN2003 and it's siblings. Ira

Unless I misunderstand completely, you can't reasonably use a resistor to limit current on a LED requiring 3.3V if you are driving it from the output of a Teensy Any resistor small enough in value to allow reasonable brightness won't have any real effect in limiting current. If you really want...

Unless the program gets a whole lot bigger than it is now, not much point in making it a const. Also with the generation in code, it's trivial to test to see if 500 can become something larger enough to significantly improve the output. Also, I think you only need 1/2 of the entries as 0-250-0...

Since amplitude only seems to have 500 possible values and a Tiny 3. has lots of memory, you could generate them in setup and put them in an array, then amplitude = (((sineFactor*sinf(phase))+(cosineFactor*cosf(phase)))*2000.0)+2050.0; analogWrite(A14, (int)amplitude); would become...

OK, now that I have it all working for me is there interest in versions of Timer1 and maybe timer3 that work at much lower frequencies? If so would you like my modified version. Also, is there a reason you choose center aligned PWM? Ira

So I went back and tried to find the smallest piece of code that would cause the problem. It took a while but I figured it out and it's attached at the end of this message. I eventually figured out that the center PWM has some limits with very slow PWM speed. Under something near 370 hz, the...

So it's a bit later and I managed to make it work by making the following change to Timer1.h. //FTM1_SC = FTM_SC_CLKS(1) | FTM_SC_CPWMS | clockSelectBits | (sc & FTM_SC_TOIE); FTM1_SC = FTM_SC_CLKS(1) | clockSelectBits | (sc & FTM_SC_TOIE); Something with center aligned PWM it seems for as...

Using the Fan Speed example that comes with the Timer1 library everything works perfect except I can not figure out why I can't set a PWM percent higher than 55 or 56. 0-54% work perfect and then around 55 or 56 the actual percent (checked via oscilloscope) goes to zero. I've tried to follow the...