clinker8
Senior Member

It is possible to power a Teensy 4.1 from "6V" sort of. As mentioned above, it depends which batteries you use, (their chemistry, or more to the point, their output voltage.) You shouldn't exceed 5.5V I believe. ...

Please be advised that getting the full 16 bits of performance from the ADC is not easy. Follow the manufacturer's guidelines (to the letter) to get all 16 bits worth, especially with filtering supplies and recommended...

I think SPI should be able to do this. However, I ended up just implementing a parallel interface for all 16 bits. This is possible with a Teensy 4.1, but not a Teensy 4.0. With a Teensy 4.0, you can do a...

Scales are easy. I was surprised at how well it seemed to work. A scale is merely a linear quadrature encoder. Just count pulses and multiply the count by your calibration factor. Oh, and check for double counts and...

Yes, I am using int64 counters for my electronic lead screw in my lathe. @luni was gracious (and talented enough) to modify his encoder library. I can report it is working well on two different lathes. I am also...

matplotlib was acting up. Here are the two pictures, first the time domain. The time domain figure is partially cut off. The signal is 2.499000V plus what you see on the Y-axis. Midpoint is roughly 2.4990 +...

@MarkT, Probably so. Sound cards aren't bad - if you have one. They are also limited to audio rates. Eventually hope to measure impulses coming from a PIN diode, due to scattered low energy X-rays. Unfortunately the...

Just as a fyi, FFTW consists of 53 folders and about 3500 files. I probably don't need 75% of them, but it's not just a couple of files. I'll keep on looking into it, but it doesn't seem trivial.

FFTW is pretty easy to build on many OS's. I built it in 2009 for the Cell processor, which ran Yellow Dog Linux. I don't know how to do a build for a Teensy. Definitely not plug and play, as compared to a standard...

Even the latest CMSIS is limited to 4K FFT's. I wonder why that is? Can't a Teensy/M7 do a bigger one? Is it some sort of register limit? There's lots of RAM. Or is it a matter of keeping the library size under...

Err, made a few mistakes. Dumb indexing problem at the end - printing out. Should be 8*i + j, not i+j. Also forgot to scale the FFT. That matters, at least if you are comparing noise floors. Still limited to 4K...

Sort of have something running, but the results don't look correct just yet. I cannot get the "more modern way" to work. This is the sequence that I use. Not the whole program. I'd post it, but it contains code from...

Where I get tripped up are the defines, or the specific names that are used to get the larger FFT's I don't know what they are called. Will make an attempt at it... A lot of the examples are very specific and there's...

Realize this is a merry go round sort of thing - https://arm-software.github.io/CMSIS-DSP/latest/group__ComplexFFT.html shows the version of cmsis-dsp is now 1.14.3. At least 1.14.3 shows f64 functions. I think I...

Realize this is an older thread, but the topic is the same. Where can I actually find the transform functions in the current Teensy CMSIS? What size FFT's are available in f32 for T4x? Is it possible to increase...

Seem to have gotten something to work. Final code is: #include <Audio.h> #include <Wire.h> #include <SPI.h> #include <SD.h> #include <SerialFlash.h> // GUItool: begin automatically generated code...

I have run EncoderTool up to 400 KHz. I think beyond that you should look into the HW encoders in the post above. I was able to use 64 bit counters for EncoderTool which meant I didn't need to deal with roll...

Does your library ILI9341_t3n allow (ie. not overwrite a user supplied setting) a SPI CLOCK setting of 60MHz? I just want to do a test. No point of dragging out the oscilloscope if I know the setting is not observed. ...

Thanks for the actual numbers. Appreciate that.

Probably none that are spec'd that fast in my possession at the moment. Best I can do is try to drive an ILI9341 faster and see what happens. I have one installed on a PCB I can try.

Thanks for that. This is a helpful table. The question somewhat remains - how fast can it really go? I'd think the actual I/O drivers on the outputs wouldn't be able to drive 120MHz without heroics. Don't think...

@KurtE, thanks for the tables. How are the QSPI memories supported ? Or the SD card on the T4.1? Some specialized driver? If I wanted a QSPI ADC, yeah, I'd have to search for one. Probably not many to choose...

I have tested the IDE2 generated hex file on my lathe. Seems to work fine, for which I am very grateful. Now I have to synchronize all my platforms - but that is not an EncoderTool topic.

Thank you for solving the problem. It now compiles, but I have not tested this on a live platform yet. I will try it tomorrow. Sorry to have touched a nerve. I was very anxious about fixing this, and experiencing...

@luni, Issues registered on github. Don't know what else to do. I realize you are busy, but would appreciate your help here. Thanks. Trying to set up a gitlab repo with full instructions on how to build, but...

All my warnings, like iso C++, unused variables are fixed and all of ILI9341_t3n issues are resolved. Thanks to all for your help. Only thing left generating issues are EncoderTool and TeensyTimerTool. The new...

Well that got rid of the rest of the warnings from this library. Thanks for your help!

Hmm. Ok. It seems in fillRect, the arguments are int16_t x, int16_t y, int16_t w, int16_t h, whereas w and h in getTextBounds are uint16_t. Guess I have to roll with it. Doesn't feel consistent, but that's me.

Odd, I haven't even been using Teensy that long... I only started 1 May 2022. I downloaded a zip file. Maybe the zip file was old? Been a lot of confusion lately. So how does one use this? Minimal example? ...

I'd appreciate if you could get to it. Visited your repos and saw nothing obviously new.

Thank you so much for your patient explanation. It helps. All that I do with the char arrays is pass them to a function which displays the array. At no time do I change the contents of the char array. Makes sense...

Paul, as you might surmise by now, I'm a terrible programmer, with a bare grasp of C. My calling code is always using the same way of doing it, as shown in the very first post. Sometimes I need to pass a two element...

The warning vanishes from that line, but a new warning comes when doing the displayRoundedTextBox function. Is that because I have char *text1 in the argument list? Should it then be const char *text1 ? I use this...

Sometimes there are multiple choices :) Like when I want to pass "in" or "mm" to the function.

Afraid that doesn't help much. Now the warning is: /home/bruce/Arduino/ELS_IDE2/touchdisplay.ino:198:69: warning: invalid conversion from 'const char**' to 'char**' 198 | const char * buttonText = {"Clear...

Thanks, appreciate it. Can wait, have plenty of other stuff to do!

All that's left is compatibility between EncoderTool 3.1.0 and TeensyTimerTool 1.2.0 on Teensy 0.58.3 running on Arduino 2.0.3. These are @luni s libraries. I will work on cleaning up some of my warnings. Got to...

Did you try to say that I should uninstall Paul's and install mjs513's version, and it might work? Because, I didn't really quite understand you. Edit: This helped a lot. It cleaned out all the t3/t3n errors

Yes I am. Are the incompatible now? They used to work great together under 1.8.19. I changed to 0.58.3, with EncoderTool at 3.1.0 and TeensyTimerTool at 1.2.0 and I am getting all sorts of errors In file included...

Fortunately, I have a complete working IDE 1.8.19 running on two different RPI4's. (32bit and 64bit) All my source code is on a private git server. I am not totally lost. It's more of a setback. Still, I'd like to...

Fixed the TeensyTimerTool errors by reverting to V1.0.0. It seems TTT>1.0.0 relies on Teensyduino 1.58beta or better. This is not shipped with IDE2.0.3. EncoderTool errors fixed by updating to latest by cloning @luni...

It seems it is a lot more than that. I have dozens of errors in IDE2, whereas I had none in IDE 1.8.19. As I shipped a unit, I am alarmed at this, as I have a customer to support. At the moment, I am in a pickle,...

I just cloned EncoderTool. I'm getting a bunch of errors. In file included from /home/bruce/Arduino/libraries/EncoderTool/src/config.h:26:0, from...

@luni I'm working with IDE2 now. This seemed to have broken a few things. I installed EncoderTool 3.0.6. Encoder_tpl<int64_t> SpindleEnc; doesn't work. The Compilation error is: "Encoder_tpl" does not name a...

Thanks. Transition is almost complete. Got to figure out why EncoderTool isn't working. @luni made some changes to allow 64 bit counters.

Hmm, is that font bundled with ILI9341_t3 ? It looks like it. In IDE 1, it found the font. IDE 2 can't.

I didn't say trivial, but a makefile is easy. Yes, I had to buld FreeCAD from source because their app image didn't work. I just ran make. Done - well it took awhile. But at least it ran! The app image seems to...

Just found that. Thanks. Have 1.57.2 installed. Will give this a go.

Well, I think it won't screw things up, too bad. I ran the app image, but it knows nothing about Teensy under boards. My OS is Pop!OS 22.04, which is an Ubuntu derivative. Do I need to supply a url for Teensy...