Search results

To me, "Teensy-compatible" brings up the question: Which Teensy? There have been a bunch. And even then, it doesn't seem like Adafruit is making something compatible with any of them. And this probably goes without saying, but I'll say it anyway: They should market the device on its own merits...

I think what I saw was this: https://try.discourse.org/t/the-room-appreciation-topic/289 See the second post in that thread, from user codinghorror, which starts: "Au contraire, mon frère!" At the bottom of that post, it says "1 Reply" with a downward-pointing carrot, which you can expand to...

Something I noticed in the Discourse demo that I didn't like was the way it threads messages. It appears, at least, that when you reply to a post within a thread, your message shows up as a subthread (which is collapsed by default). That makes some logical sense, but in using vBulletin/XenForo...

All the other vBulletin forums that I visit have switched to XenForo, and it seems pretty good. As for PMs, I think they're good to have, especially for exchanging contact information that you don't want to expose to the world. Perhaps prevent new users from sending PMs until they have made...

Solved! I had completely neglected to solder two of the pins on the double-sided header to the Teensy! (I feel pretty dumb, right now!) Those pins were VIN and AGND. So that pretty much explains everything. The WebServer example now works completely! The TimeNTP example has some problem...

Update: the W5500 does in fact light up when powered on a breadboard. I had a grounding problem before. (I had the W5500 connected to the Teensy's AGND pin rather than the GND pin. Doh!) Unfortunately, that problem only affected that one test. The weird voltages in my previous post were...

So I checked the voltage between the ground and 3.3V pins on the W5500, while it was connected to the Teensy and the Teensy was powered by USB. It was only about 2.3V, which seems like a problem. I checked the Teensy's VIN pin, with the W5500 removed, and it's only 1.8V! When I plug the W5500...

This is a Teensy 3.2, with Teensyduino 1.47.

It’s this one: https://www.pjrc.com/store/wiz820_sd_adaptor.html It did have a live Ethernet cable attached, yet none of the LEDs lit up at all. I’ll check the voltages when I have a chance.

I can't get this W5500 ethernet module working with Teensy. I'm hoping I just setup something wrong. Can anyone spot a problem? I've tried it with the WebServer example and the TimeNTP example, and both can't find the adapter, nor do any of the LEDs on the W5500 light up. I've tried adding the...

It's a power supply that speaks PMBus. I bought it used, and expected it to follow the datasheet, but the manufacturer tells me it was customized and probably had those commands disabled in firmware. So I'm pretty sure at this point the delay I see on the bus has nothing to do with the lack of...

The begin statement is this: Wire.begin(I2C_MASTER, 0x01, I2C_PINS_18_19, I2C_PULLUP_EXT, 100000); I measured 5 us high and 5us low on SCL, when it's not delayed. That matches the clock speed I setup in the begin statement. I used 4.7k pullup resistors. The slave responds to some commands...

Sorry if this has been covered elsewhere in this thread. (I did search for it!) I'm seeing delays on the I2C bus between each part of a command. I'll explain with an example. First, the code snippet (from the master): Wire.beginTransmission(addr); Wire.write(cmd_byte)...

Ok, for the sake of testing, I installed the desktop environment and a VNC server, and was able to run the Arduino IDE that way. (That required hundreds of packages... which is why I was reluctant!) Anyway, the Arduino serial monitor had the same problem. But... That worked! (Correct link...

Minicom doesn't seem to work any better. So far, I've only able to get two lines of output before it stopped. Since then, I haven't been able to get any output at all, even after unplugging and replugging the USB cable. I don't think Arduino Serial Monitor is an option, as this is a headless...

I'm seeing a problem similar to this, though with Teensy LC, not 3.1. I'm using a Raspberry Pi 3B+ with Raspbian 9.8. The Teensy LC has been pre-programmed on a different computer, as I have not installed Teensyduino on the Pi. I have installed the udev rule. I do not have modemmanager. If I...

I did take a look at the yield() source code, but I didn't follow it all the down. There's a call to EventResponder::runFromYield(). Not really sure what that does, but it's probably nothing important for my project. Regarding buffer size, what buffer are you talking about? As you can see from...

After some more investigation, I found that changing "if (Serial.available()) {" to "while (Serial.available()) {" solved the problem! So this suggests that there is too much time between loop() calls to keep up with the USB stream. I was even able to reduce the delay in the sending code all the...

I'm using a Teensy 3.2 with Teensyduino 1.44. I have an application where I send data from a PC to the Teensy over the USB serial port, and I was noticing data corruption. I wrote this simple sketch to demonstrate the problem: void setup() { Serial.begin(1000000); } static int seq = 0...

UCS1903 seems to have slightly different timing from WS2811. I wonder if that could be causing problems for longer strips?

It looks like you might have DI2 attached to the positive side of your 24V power supply? That is probably way too much voltage for that pin. In the UCS1903 datasheet I attached above, it should either be floating or +6V. Not knowing the exact chip, I would suggest keeping it no higher than +5V...

Looking a little closer at the photo, I see the rightmost LED is different. It has 8 pins instead of 6. I'm betting that LED package has the controller built into it. I would try FastLED, set to UCS1903, attached to DI1, leaving DI2 floating. And if that doesn't work, attach DI2, and leave DI1...

Here's a UCS1903 datasheet that I found: http://www.bestlightingbuy.com/pdf/UCS1903%20datasheet.pdf According to that, there is an extra pin to select data speed. Connect to VDD for low speed, leave floating for high speed. Are there chips like that on the strip somewhere? I don't see any in...

Ok, will do. Yeah, I get that. But can we still have an option for this? Sometimes, that extra 250us is more than I want to give up, and as long as I have compatible pixels, I shouldn't have to. Would you entertain a pull request that adds a flag for this (keeping the default at 300us)?

I noticed some changes to the OctoWS2811 library that have had a negative impact on performance. The change with the most impact on performance was this one: https://github.com/PaulStoffregen/OctoWS2811/commit/09fcdedb8e7669bcd77fc348586ce706711530cd#diff-baf1e8544e6d4607249cff6356e85e46...

It's probably possible to do without it, if you want rework the bootloader code, but it wouldn't be a Teensy, anymore. And it would be much easier to brick with the bootloader on the main processor.

I'm curious, how much do you think it would raise the cost?

A Teensy LC with twice as much RAM and flash would be fantastic, if prices could be kept down. The price difference for these chips at Digikey is only 61 cents, in quantities of 500, so seems like it would make sense. If Teensy LC could be refreshed with only a slight increase in price, I think...

Yeah, I've used that for end caps, since it works great for attaching silicone to silicone. But I'm not sure it sticks well to anything else. Edit: Website says it "secures glass, metal, plastics, fabric, vinyl, weather stripping and vinyl tops", so I guess it will stick to some other stuff...

Perhaps an ifdef, or a maybe a whole separate example for LC? I think it's always good to have a working example, so users have something to try before they start writing their own code.

Awesome! Also, as Gibbedy pointed out above, BasicTest doesn't work on LC. (Gibbedy sent me a pull request, which I haven't gotten around to: https://github.com/baysinger/OctoWS2811/pull/1). Not sure if you want to update BasicTest or not.

I don't think there is anything 5V specific about this part. It's just an LED and an NPN phototransistor together in one package. The way that Arduino circuit works is the the 5.6K resistor is a pull up resistor, so the voltage going into the microcontroller is pulled up to 5V, unless the...

If they have a waterproof silicone sheath, very little will stick to it. If not, you have lots of options. I use clips like these: https://www.adafruit.com/products/1644 Those will work with or without the silicone sheath, though you'd want to get clips that were a couple of millimeters smaller...

It sure looks like OctoWS2811 supports 3.5 and 3.6, per the GitHub commits. (I'm taking ws2812s to be plural of ws2812, which speaks the same protocol as ws2812b and ws2811.)

The OctoWS2811 library always uses the whole port. It exploits the fact that copying a byte to one register will update all of the port's outputs at once. You can probably modify the library fairly easily to use a different port, if you want, though. The OctoWS2811 board just contains a simple...

Thanks for trying out my port. Glad you were able to get it working! I think Teensy LC should be able to handle a few hundred LEDs easily, as long as they are split up among multiple pins. (Using all eight channels equally is the most efficient use of RAM.) But of course that will depend of what...

No worries. I'm having fun trying to eek as much out of my Teensy LC as it will give!

Yeah, I'm a fan of simplicity! If you do want to try to get OctoWS2811 working on a different port, I can try to help you out. It doesn't look like it should be that hard. But I do not have a Teensy 3.x to test with.

This looks like the error: c:/program files (x86)/arduino/hardware/tools/arm/bin/../lib/gcc/arm-none-eabi/4.8.4/../../../../arm-none-eabi/bin/ld.exe: region `RAM' overflowed by 120 bytes I think that means your global variable allocation exceeds the available RAM. Teensy LC has only 8k of...

I'm the one who made the port of OctoWS2811 that Paul linked to above. If you tried it, could you tell me where it went wrong? Thanks!

Since you only want to drive one LED strip, FastLED might be a better solution for you than OctoWS2811, which is designed to drive eight. OctoWS2811 writes to port D, which is spread out among all eight of those pins. Simply commenting out those pinMode statements won't do anything, if you are...

I'd certainly be interested in any feedback anyone has! Here's my GitHub repo, which might make for easier viewing of the code: https://github.com/baysinger/OctoWS2811 Paul previously posted this: I'm curious what kind of test I can do to expose this issue? Since I didn't really do anything...

Here's my attempt at porting OctoWS2811 to Teensy LC. It does seem work, based on my minimal testing. I've tested with a 6-pixel strip of WS2812B chips and a 22-pixel strand of WS2811 chips. In both cases, I drove the pixels directly from the Teensy's GPIO pins (no buffer chip available to...