Search results

What do you guys do, when you need to carry a shield cable (say for serial cable) between an unshielded connector? Do you take the shield, convert it to a pin, and continue the shield from the pin? Or ground the shield from both ends, and leave it open at connector?

How do you do that with zener diodes? If the input volts are over 3.3V, it will clip to the power rail. Schottky diodes forward bias at about 0.2 V

Bump, wondering if this is acceptable protection circuit? Reading the data sheet, VCC + 0.3V seems okay.

Teensy 3.2 and 3.6 Yes it's just for on/off switches. I do believe I have a few on/off sensors that float at 5v. But I wanted to make sure down the road that it can handle 12v floating if the sensors change. Ah that may of answered my own question. If I have a pull up resistor attached to...

One project I'm going to use BAT54S to protect the digital inputs. Question on the pull-up voltage. Any reason to use 3.3V, 5V or 12V? I have 3.3V currently on the pull-up, and if I put 5V (or 12V) on the input, the output to Teensy is 3.587V (I'm assuming the chip can handle 3.3V +/- 0.3V)...

AH I just came across this. Perfect for my idea. When flying, the ATC can be very busy and loud over the headset. This will allow me to record 9seconds live, and be able to click a button for playback if I missed any communication.

When Teensy 3.6 is set to (180MHz or 168MHz) and FastLED is on software SPI, I have to drop the FastLed datarate down to 4Mhz. If the Teensy is set to lower MHz, then the FastLed datarate doesn't need to be set. When on hardware SPI, everything works at any speed. I'm not sure it's a bug, I...

Okay. I will on Monday night, just away till then.

Teensyduino is 1.41 and FastLed is 3.1.8 Ethernet works great, so I removed it from the equation. It has to do with clock speeds. Hardware SPI works at any speeds, but when you force it to use software, it doesn't like Teensy @ 168MHz & 180MHz. To work at those speeds, I had to slow down the...

I'm having troubles with FastLed using bit bang. The lights go haywire on software SPI flag. #define FASTLED_FORCE_SOFTWARE_SPI //Ethernet gets the hardware pins #define FASTLED_INTERNAL //Removes compiler pragma msgs #include <FastLED.h> I designed my board with the LEDs...

Yup stupid me, I should of done this simple test a year ago to see how much data was being passed. Turns out, found a bug in DeviceX with their code overloading the serial bus. #include <Metro.h> Metro Serial1_TMR = Metro(1000); long counter; void setup() { while (!Serial &&...

Oh Sorry, I didn't explain this well enough. The devices (Teensy and DeviceX) are standalone and talk to each other via serial cable on serial1. DeviceX just pumps out data on the serial cable while the Teensy reads and processes the sensor data. If I start the Teensy first, then DeviceX...

Oh yeah, I have a good processing sub routine to handle the start & end flags, checksum and stuffed bytes. But I dumbed down the sketch to just read anything on the serial bus for this example to keep things simple. It's hard to tell if there was any 'breaks' between the packets, I'm guessing...

It has to do with the timing. At 19200, the bus was too over loaded and couldn't "re-connect" a starting packet (I'm guessing). Up'd it to 38400 and it seems to catch every time I unplug and replug in the cable.

Yes underside is cut. No power from the computer. I'm trying a different teensy and a different serial device as we speak.

I'm using Vin for both the teensy and the other serial1 connection, with a power supply. The serial1 device continually pumps out data, doesn't need/wait for any feedback. I've confirmed with scope that the data is always present on the teensy pin, even when teensy isn't picking up the data...

This mainly happens while the teensy is already running it's code. I do think it's a timing issue, as if I need to plug in the cable while the device is inbetween sending data packets.

I have a weird issue that I can't seem to fix or debug very well. Have a device that pumps data out their serial bus into teensy 3.6. When I first boot up the power or send new code, the serial data get's picked up by teensy. If I unplug the serial cable and re-plug in, teensy stops picking up...

Here's my final draft in Eagle. Let me know what you guys think. Schematic only, going to start on board design. 16 - digital out (-) 12 - digital in (-) 14 - analog out pwm 8 - analog in (5v) 2 - serial bus 2 - power inputs 1 - spi out 1 - can bus 1 - wifi

The schematic (little blurry until you click on it) has 5V listed as Vcc. The datasheet for PS2501L shows roughly 1.2volts for LED. (5V - 1.2V) / 10ma = ~ 390ohms. I went with the next size up with 430ohms. Was wondering more on the MCU side of things. I generally put in 1K without really...

I found a 4ch PS2501L-4-E3-A that should work. https://www.digikey.ca/product-detail/en/cel/PS2501L-4-E3-A/PS2501L-4-E3-ACT-ND/3646233 On the MIDI example, they don't have a resister in-series, would the 1K i have be enough for protection? Guessing any diode should generally work here?

Figure I'll use software debouncing rather then hardware. Simplify build time. Sticking with external pull-up as wire length could be anywhere from 5-10ft. Digital Input

I see the OctoWS2811 uses 74HCT245 (bus transceiver), but I also looked at the 74HCT541 (buffer) instead. I don't really see much difference between them, other then a nano second here and there in specs.

I didn't want to get too serious, but I also didn't want a direct pin tied to MCU. Still need to take care when installing / playing around with the board. Mostly just for projects in my everyday life, sometimes I'll only use a few pins, or maybe all of them in another project. I think I'm safe...

I'm designing a generic board to use in my cars (or other projects) that the inputs/outputs of the Teensy will be protected. Just want to make sure I haven't over looked things, or have the resisters on the correct side. Teensy 3.6 ESP8266 Wifi, CAN, and RS232 Power Have two power sources...

I'm designing a little car computer and wanting to over-do the input circuits. Looking at other posts, I'm trying to find out how to come up with the right resistor values. It will be for simple external switches (gnd on end of switch), but just in case something shorts, power touches it, etc...

Thank you. I did not know that with analog but makes a lot of sense the way you worded it. Thank you again for your schematic.

Would you still put a current limiting resistor between the op-amp and teensy ?

Frank, yes you understand me correct. Your solution is nice and simple. I had to first change from a String to char array to speed things up. Around 200bytes, both our functions are only a few micros() apart.

Yes, my example was typed on the fly as well. Was not a full sketch. I wanted to take the actual hex value array (0x35, 0x01), save it in a char string. (3501 aka 0x33, 0x35, 0x30, 0x31). I've created a full sketch now to test things out. Created a function that loops through each byte and...

I'm going bald over this. I know it's right there, but I've searched and played around for hours. I have .... uint8_t hexData[6]; data[0] = 0x5B; data[1] = 0x01; data[2] = 0xFF; data[3] = 0x00; data[4] = 0x0F; How do I get it to ? char[] charData = "5B01FF00F" I've tried adding ..... and...

I'm starting a project that has 2 serial devices connected to Teensy 3.2. I'm looking to see if I'm on the right track on setting everything up. This will expand to another serial uart and a CAN device, along with SPI port. Serial 1 - Host Format - HEX RX - Gets load of information in hex with...