Search results

I’ve noticed this happen to some of my boards as well. We have them soldered to a few dozen carrier boards and for us it seems to be related to the quality of the USB connection. For whatever reason, the CLI is more sensitive than other interfaces to the kinds of USB issues that don’t even show...

I’ve been using these spring loaded pins underneath those pads for a couple years now and they work great: https://www.digikey.ca/short/0ftt7j54

I install pogo pins underneath the USB device test points to access the device end on a carrier board. I believe there should be a drawing somewhere that dimensions their location and mapping on the board.

This is more likely to be related to the MTU (maximum transfer unit) set on your network switch or receiving computer. I think there may also be some MTU set in either NativeEthernet.h or FNET.h that may also prevent you from getting packets larger than ~1400bytes. I would very much like to be...

In your example of getting analogRead() = 769, and the Teensy 4.0 being a 3.3V device, it would follow that the converted voltage is 2.48V (3.3/1024*769). Teensy4.0 is working fine and linearly, and yes please do not expose any signal pin to more than 3.3V.

I usually run teensy_reboot.exe from the Teensyduino binaries to trigger a restart and automatic code upload. Doesn't work unless the serial port is closed though!

I use the XBees a bit but only between two modules. Even then it's been very tricky to get them to operate quickly because the default settings seem to be optimized around minimizing packet loss, not to maximize throughput or to lower latency. For example, I use two set up as endpoints (no...

Can you post an example sketch that demonstrates the limits you're hitting? Maybe it can be optimized with a couple tweaks. Please also include the defines you changed in SdFat. The speed is limited partly due to the fact that the SD cards cannot draw full power or communicate at full speed with...

Does this mean it would be highly preferably to use this method instead of micros() or an elapsedMicros() object? Therefore can the elapsedMicros() class be rewritten to be faster for short period reads?

That sounds efficient for SPI! That probably makes the difference for flicker. Maybe I should give it a second try if there's a nice super-bright display I could find for it.

I would recommend starting with the Gameduino code for trying the displays that include FT810, FT812, and FT815. I first tried the RiverDi 7" display using the GD3 code that was modified to work with Teensy3.2. Then as I changed to use the not supported Matrix Orbital Display , I ended up...

Gorgeous mechanics! I love the leg hinge solution. What material are you using it? You're spot on about the difficulty of using 'dumb' motors, closed-loop is a fundamental feature for systems with so many DOFs. If you had an internal physics engine servo telemetry would let you do velocity...

How good is the RA8875? Last time I tried to use it I couldn't get it to stop flickering! Could be my fault. I've been using the 7.0" 800x480 EVE displays that run on the FTDI FT813 chip using SPI (also compatible with QSPI but I don't know how to configure that with Teensy4). It's quite hard...

Thank you all for the wealth of information. I was going to ask these questions today if it weren't for this thread. I just moved all my projects to the T4.0 from the T3.6, and am now learning how to optimize for the new MCU. Would the opinion of a novice be helpful? I hope so... I have two...

I'd recommend CrazyFlie by BitCraze/. In this field you can get bogged down really quickly... Starting from a known good solution with many examples of the exact goals you're trying to achieve will do well. Your worst case scenario by starting from a product designed around your needs if that...

Datalogging is a problem I've been trying to brute-force for half a year now. My solution (that I hope to release in a couple more months of testing) runs on top of the SdFs library for the purpose of low-latency high-frequency binary logging. I'm currently able to (somewhat reliably) maintain...

Further Improvement To Slave Handling Hey all, The improvements are fantastic! In my use case I want to be able to have multiple "types" of slaves that can hot-swap and identify using a universal handshake packet. To make it easy to program each type individually I am writing a wrapper class...

Improvement to slave handling Hi Tonton81, For my uses with multiple slaves, the amount of them fluctuates throughout operation. In an ideal system, I can use the same handler to parse the data of each slave, but without knowing which slave the handler got data from, it's quite difficult. To...

Hi tonton81, You were right that a wire was missing, but the ground wire is the green one in my setup. I was missing the CS line, now added between 15 on 3.6, and 2 on 3.1. Now everything is working great! Sorry about the rookie error! I'm hoping to use this to talk to multiple slaves, I will...

Hi All, I've been reading throughout development of this library and decided it's time to try it myself. Unfortunately, I'm having trouble getting the master and slave to communicate. I used the wiring as described here, running the TVmaster and TVslave examples with no modifications from the...

Thank you very much for the Xbox support! I tested it out today and got it to work without much issue. The only thing I had to change was to add another PID as my Xbox One controller seemed to have a different one: //*****************************************************************************...