Search results

I've been searching for years for a suitable display option for my Teensy-based project. The display requirements are a daylight-readable 7"-ish touchscreen with a decent refresh rate. I have been scouring the available options for a good while and haven't found anything I like that can be used...

wwatson, do you have any experience with this device in outdoor lighting conditions? This type of display would fit my bill for an integrated instrumentation system in an automotive application, but the 100 cd/m2 the datasheet calls out has me concerned about readability.

Looks like it's getting cast to a float anyway. I don't see a reason I can't just alter Tone.cpp to accept a float?

Hello, I am trying to output a square wave using tone(). The frequency is being returned as a float and I would prefer to output the square wave with the decimals intact, for example 12.34 Hz instead of rounding it off, but it appears the function was written to have an integer passed into it...

Hi guys, About to start on a large project and I could use a couple suggestions. The prototype will be built as a series of daughterboards linked to a single motherboard containing essentially only the MCU. Essentially everything else will be handled on daughterboards. The daughterboards will...

That's funny, when I first read that paragraph in the reference article, I thought "I bet 'processor' clock really means 'F_BUS' clock." Thanks for confirming. I guess I find it a little odd that the recommended frequency limit is so low (1KHz) in the reference article, but I guess I just need...

Hello, I am potentially going to be measuring a square-wave signal (.5 to 5KHz) with a Teensy 3.6 and possibly later a Teensy 4. The low end of this range is a major control input for my project, as such I would prefer to use FreqMeasure to have the best resolution possible below 1KHz. The...

I'm using several of these types of character LCDs in various pieces of gadgetry: https://www.adafruit.com/product/198 I like them because they are inexpensive, easy, and a useful size. The one issue I have is the slow effective update rate. I've found that attempting to draw to them faster...

Reviewing the 1050 datasheet, it says: Am I correct in interpreting this to mean the 1050's ADC is technically 12-bit, but only 10/11 are useful like the 3.6 is technically 16-bit, but only 13-bits are useful?

Roger that, thanks for the quick response.

Hello all, I am attempting to measure 3 pulse signals. I had this project going on a Due but moved it to a 3.2. My circuitry is configured for internal pullups, and just now, altering the source code to move it over to the Teensy, (implementing FreqMeasureMulti) I cannot find any information on...

Custom full-authority ECU for use in the motorsport sector. Modular avionics-level sensor package, datalogging, engine protection, etc.

Any update? I'd love to get some of these.

At this point I don't have the experience to lend any useful suggestions on specific pins to include or exclude. Unless several variants optimized for specific roles could be developed (T4-audio, T4-comm board, T4-digital/analog IO, and I know this is as unrealistic as it would be awesome), I...

Replies in red.

Your community support is remarkable and appreciated, and I am definitely looking forward to the new Teensy(s). Are you far enough along yet to have an idea whether or not the T3.6 form factor can be retained?

The only thing I can add, which may or may not be helpful, is I wouldn't assume the meter can properly detect square wave frequency. I have a Fluke meter that I use at work, one night while trying to diagnose an intermittently failing cab blower motor in a Freightliner (this model used...

Yes, it should.

I'm a moderator on another forum, you can view the IP address of each individual post, as well as each that a given user has logged in with and the one they registered the account with. I use IP addresses almost daily to bust people for a wide array of forum-specific rule violations, as well as...

I can't provide the level of detail you're looking for, but I remember when I left the AVR boards that F() does nothing, at least on the Due and Teensy 3.6. I did some cursory searching and it seemed that the ARM processors place strings in PROGMEM by default, so F() is redundant and does...

https://www.pjrc.com/teensy/td_pulse.html Does this satisfy your needs?

You can do RPi in Bare Metal, but I found the community support is a fraction of what's available with Arduino-derived systems, and the RPI platform didn't seem like a very good fit for a complex embedded project like the automotive ECU I'm working on.

Forgot to mention, now can't edit my last post: Blue waveform is the signal generator output (simulating the signal from the drive). Red waveform is voltage at the pin on the Arduino configured as input/pullup. I did some further testing and settled on a 10k current-limiting resistor in the...

In case this helps anyone else, here are my results with the LTV-816 opto using a 20k (.5mA) current-limiting resistor right off the simulated drive output: 325Hz is the motor current with no load. 750Hz represents full motor load of 4 amps. This configuration will work up to about 1.5kHz...

Awesome, thanks for the input. Most of my confusion was from a preconception the optoisolator was more of a switching element, but the CTR makes a lot more sense if ICE scales somewhat with LED current. I wish that datasheet was more clear on that component's CTR but I'll do some more research...

Hey guys, I'm attempting to read a pulse signal from a Hitachi variable-frequency drive. The drive's reference guide states this output is a 0-10v square wave, with a limit of 2mA. This circuit must ground back to the drive. I was initially planning to use a voltage divider to drop the signal...

Interesting. I will be well below whatever the Due's memory limit is (don't recall and I'm not going to look it up right now. 512kb?). My curiosity has been piqued enough to benchmark the hardware as mentioned previously. I found this other thread that talks about similar testing. I figured I...

Okay, cool, just wanted to make sure there wasn't some little syntax nuance messing up my declarations.

Those are all declared as unsigned. Are you saying "unsigned int" does not equate to uint32_t?

I don't understand. Everything millis() is used with is an unsigned long. The only standard "int" in there is the pin declaration and there are no signed "long" variables at all.

Changing to explicits is the plan, though as I mentioned "int" and "long" are both 32-bit types on this microcontroller. Regardless, none of the ints in that example will be more than a 4-digit number. Which brings me back to the first point regarding whether or not a 16-bit type is actually...

This specific project is using a Due, but that looks like a good idea for the T3.6/T4 projects, which will need to read pulse signals as well.

A uint64_t would hold 18,446,744,073,709,551,615 micros, or 584,942.4 years. A 36-bit value would be plenty as I don't expect more than 12 hours of uptime at a go, but of course no such thing exists. The superiority of explicit datatypes seemed like a no-brainer from that small amount of...

I've been reviewing datatype standards for a couple projects I'm working on, and have a couple points I could use guidance on. The current project is actually based on a Due but this is more for general programming knowledge and will also pertain to the T3.6 I'm using in another project until...

Interested to hear your thoughts on the Stone screen and using it. Might just be the perfect solution for my similar project as well, but a bit more than I'm interested in spending without some real-world feedback.

As protoshields are available for Mega/Due, I would be interested in those.

I did not, thank you. Incorporating that into the final install may allow me to delete a port expander or two.

Hopefully this isn't too dead... I'm liking the T3.6 and want to use it for all the projects I have planned (at least until T4 blows it out of the water). The only trouble I'm having with it is there's not a lot of great "ProtoShield" type options available for it which makes anything past...

I don't know exactly what your project is, but it sounds like a simple voltage divider is all you need: https://www.allaboutcircuits.com/tools/voltage-divider-calculator/ If necessary, I build my level-shifting into the voltage divider for analog inputs. I also like to protect those inputs by...

You can overclock F_BUS by changing a config setting in (I think) one of the core libraries. I found that my project doesn't have the PWM freq/resolution requirements I thought it might, so I haven't messed with it.

Any updates? Really looking forward to implementing v9 on several projects. Thanks.

This subject also came up in the Teensy 4 thread. As someone who's a rookie electronics hobbyist and fresh onto the Teensy bandwagon, something that I would have (still would, really) found very helpful is updating of the Teensyduino database. Many sections are incomplete, or only cover older...

The NXP marketing blurb said FreeRTOS on it, I'm guessing that means native support.

Interested in what you come up with, I have not made it to the display point in my project yet but it will require a RA8875. I was planning on modifying the library to isolate the RA8875 to its own SPI bus to avoid the tri-state issue, but I need it to communicate with the SD card as well.

Bring on the megahertz. More power, more better.

Understood. Thanks.

Sounds like he's got some time on that, though personally I'm hoping for easier implementation of a real RTOS on the T4.

Are you at liberty to elaborate on this point a little? Perhaps even just a comment on whether it's primarily less capabilities with the ADCs or PWM. Thanks.

Bump for update, I am interested in this.

I would also like to know how this is coming along.