Search results

Nicely done. I appreciate the detail you show. I was just talking about this with a friend of mine. Do you have video or other pictures of the RGB action?

+1. I, perhaps obviously, support this addition!

I don't think so, only because the code here doesn't include the low-frequency handling: https://github.com/PaulStoffregen/cores/blob/master/teensy3/pins_teensy.c

maybe if U Think about it First then ppl will b moar willing to help. Give it a try and post what you come up with after reading the documentation available for elapsedMillis

Any through hole is obviously the same front/back. There are additional surface pads on the back that offer additional signals. There are a few ways to connect to them. The easiest way seems to be to buy a circuit board as have been designed and posted here by a couple people, which you can...

Seems to me that a Teensy is a great way for you to further your goals. The programming language is the same as Arduino, with a few additions. That is because Paul, the creator of Teensy, has built an extension to the Arduino environment to allow it to be used to program Teensy. That extension...

Is this just for greater headroom before the damage-threshold voltage is reached?

Ground shields at one end to avoid ground loops. Are your two systems intentionally isolated including the grounds? If designed that way then I suppose that may work but otherwise they would commonly share a ground. No pun intended.

Wrap each motor lead through a ferrite a few times. Put a power filter on the input to the motor power supply. Shield your signal cables and ground the shield at one end.

Why differential input mode?

When I built a large machine tool using brushless motors (grad school) we used ferries on the motor leads to reduce radiated noise. They were quite effective. I imagine, though, that ferrites on the signal wires may also help by suppressing the induced noise. One would think that they should be...

Since you want zero-cross detection, couldn't you use a comparator circuit for that and then have that provide the sync signal for PWM? Or something like this: http://www.atmel.com/images/doc2508.pdf Or this, which is closer to what I was imagining...

Why not just use theremingenieur's code, which will accommodate the frequency range.

I can confirm that this works as desired, thank you so much. Am I correct that, based on section 36.3.3 of the Reference Manual (pp. 780-81), each FTM may select a different clock and/or prescale? But each channel within a given FTM shares that clock and prescale selection (based on 36.3.6)...

This is fantastic, thank you. I need to spend some time with the reference manual to understand your code and what else may be impacted by changing the clock source for the FTM. No doubt it may mean that I should have chosen certain pins for the outputs of interest. (My board uses pins 23 and 32...

I'm curious about lower limits for PWM output too. Is there a practical limit where it makes more sense to switch to using a software-based implementation of PWM? For my application, I will be modulating a solenoid water valve, so the fastest PWM cycle I will want is ~1 Hz. I'm interested both...

It does seem suspicious that the buffer is 64 bytes. Why not try increasing it and see what happens?

Thank you that helps my understanding considerably. Is there any reason to use the PNP instead of a p-channel MOSFET?

What an awesome sensor. Do you have a data sheet for it?

Thanks. Do I not need a series resistor between the Teensy and the NPN?

Thank you Paul. I really appreciate your help (and great products). I had thought that reducing R3 may be in order, just wanted to stay well clear of the 20V max voltage differential. I will go with your recommendation.

Isn't the output enable of the 74AHCT125 an inverse input, so that the outputs are enabled with the OE_ input is LOW?

So maybe someone is willing to comment on this schematic? (Adapted from post 11 of this thread.) It uses an NPN transistor to drive the P-channel MOSFET. Since the car operates at ~14.4V, the resistor dividers would mean the gate is about 7V when the transistor conducts, if the K line were at...

I'm using Teensy 3.1 in an automotive interface that includes a connection to the OBD2 k-line. That specification requires a terminating 510 Ohm pull-up resistor from the k-line to +12V. If there is an external device connected to the bus, it will have a terminating resistor; when there is no...

Why not just compile for Arduino Micro?

This just got me. Is there any reason to redefine the pin to turn the output off? I was using digitalWrite(pin,LOW), which didn't work so I tried analogWrite(pin,0), which did. That seems fine but I just want to make sure there's no reason to do something different.

I always recommend Teensy over Arduino. I have found it to be so much better from a capability perspective and I think Paul's software contributions would be impossible to overstate. They are magnificent.

Does the switch ground the input?

You have it correct. That's why I recommended that relay module. For just getting things connected, it's completely awesome. And it has all the right features like current-limiting resistors and optoisolation. I have a few of their modules. They also make modules with solid-state relays, if that...

Your option 1 sounds right to me. I'm pretty sure that's how I did it, although it was a while ago and I may have been using an Arduino board (5V). Is your 5V supply running the Teensy? In that case they are sharing a ground anyway. Just send 5V to relay_JD-VCC, 3.3V to relay_VCC, GND to...

Honestly, you might be better off getting started by using something like this, which you can connect directly to the digital output pins.

Isn't the TIP120 a Darlington pair? Seems like you'd want a MOSFET for high-speed use. But you said you need 1ms and that the TIP120 is 20 us, so aren't you fine?

Don't you have to define count as a volatile int?