Search results

Will the Arduino IDE as we know it continue to be developed? It's already difficult for me to run two Teensy 4.1s with their respective EVE 4 displays at the same time in IDE 2. Do I now have to learn a different environment?

I forgot to mention something important. Try the example included in the library called sprites. This will help us determine if there are any fine-tuning needs to be done on the timing table. If you see any distortion in the image, take a photo so we can try to interpret the possible source of...

I'm glad to see that the library works even on hardware I've never been able to test before. The timing table is in the link to the datasheet you attached. This is the content of constructor 43, the two parameters that are somewhat different are: Thfp and Tvfp, for the Newhaven TFT of 4.3"...

That 4.3" 4D Systems FT813 TFT is very good. Congratulations. The timing table is on page 25 of the link you provided. It seems to me that the GDSTx values are compatible with those of your TFT. However, there may be two parameters that need fine-tuning, as long as you see any kind of artifact...

So selection 3 worked correctly for you at 1280 pixels? There's no problem with the automatic selection; support for 4 is still native. Extended mode 3 applies only to the 12.1" TFT. I decided to use SizeEVE as the parameter to select the normal or extended mode. Now, in GDSTx, everything is...

Indeed, the value is natively 4 in GDSTx. My question is whether this setting to 3 has a real effect on your screen, allowing you to use the full 1280 pixels of width, meaning you can draw any element without color shifts or artifacts. I believe reducing the resolution from 16 to 8 is simply a...

Wow, I thought the touchpad was going to give problems, it's good to know that it's valid for resolutions greater than 800x480 px. According to the EVE3/EVE4 chip programming guide, the workspace is defined by the VERTEX_FORMAT instruction, which can take the values 0, 1, 2, 3, and 4. (Page 24...

Apparently, the general parameters are correct. Perhaps it's a matter of fine-tuning some of the general timings; it's difficult to know which ones are correct at a distance. However, the datasheet should be your guide. I think this is the first approximation and the way to go. Don't change...

My mystake, sorry! Try this: #include <GDSTx.h> void setup() { GD.begin(); } void loop() { GD.ClearColorRGB(0x100020); GD.Clear(); GD.cmd_text(GD.w / 2, GD.h / 2, 31, OPT_CENTER, "Hello world"); GD.Begin(LINES); GD.ColorRGB(255,255,255); GD.SaveContext(); GD.VertexFormat(3)...

Try this sketch again #include <GDSTx.h> int MCUID; void setup() { GD.begin(); IDEMCU(); } void loop() { GD.ClearColorRGB(0x100020); GD.Clear(); GD.cmd_text(GD.w / 2, GD.h / 2, 31, OPT_CENTER, "Hello world"); GD.Begin(LINES); GD.ColorRGB(255,255,255); GD.SaveContext()...

This maximum resolution of the BT817 is very recent; Riverdi pushed the chip's capabilities to the limit. I see that the GDSTx library is responding well with the latest tweaks; it's just a matter of applying the correct TFT timing values in the startup section of GDSTx.ccp; the display...

Before reaching the 2001 counter, did you notice any artifacts? I've adjusted some parts of the library so that the BT817 chip's line pattern and color test can be used for the 12.1" display. Please download the GDSTx library from the Github repository again and upload the example. #include...

The displacement in x+, y-, and y+ is interesting. Please upload the sketch called "sprites" and again upload a photo with the result.

Great. Please, share a photo of the result so I can get an idea of the corrections. They should be minimal in both hoffset and voffset.

A while ago, I was configuring the library to connect a 10.1" EVE4 display. However, due to time and resource constraints, it wasn't possible to get the display for testing. Since you already have a 12.1" display, if you'd allow me, "you'll be my eyes for the experiment." The timing tables...

You've achieved an interesting optimization. To be able to see the behavior of an audio signal's FFT in real time on the serial monitor, using the corrections you've studied, what would the example look like? With the AudioAnalyzeFFT1024 class, I use these lines: AudioInputAnalog adc1...

Yep. Jejejeje translator errors!, I apologize for that

I have a couple of these modules, identical to the one you mentioned. I'll use one of them to control the PWM fans; it's being tested. The other has been running on a Teensy 4.1 board for over two years. It controls the PC's on/off switch, a servomotor that drives the PC's folding ventilation...

Audio input GND must be common to GND of the conditioning circuit and GND of the Teeny 4.1. The audio input to the teensy 4.1 is pin A2

MarkT, already on the topic and appealing to your experience in this type of projects, then what would be the correct way to take the audio signal from one of the 3.5 mm outputs of the PC motherboard, to process it on pin A2 of a teensy 4.1 board. Is the conditioning circuit we have talked...

I built the conditioner with SMD components, I didn't have a 2.2K resistor on hand, I had a 2.4K one, I don't think it affects the resulting signal too much. I used ceramic capacitors and a 3.5mm stereo adapter. Check the wiring again, a couple of times I didn't get a response, I took some time...

I just have the conditioner installed on the teeny 4.1. The audio signal comes from the PC, from a 3.5 mm output. In the screenshot you can see the result from the serial plotter of the Arduino IDE, 4 audio-files are played simultaneously with signals of 500 Hz, 1.25 Khz, 1.6 Khz and 2.0 Khz...

The first thing is to condition the audio signal so that information about its behavior is not lost. This circuit to condition the audio signal on pin A2 of your teensy is a good start. Try this code: #include <Audio.h> AudioInputAnalog adc1; // A2 pin teensy 4.1...

The relay is just a switch for the power supplied to the fan. This is the simplest example I can reduce the controller I built to: int PINRELEFan1 = 39;// Fan1 PWM int PWMControlFan1= 33;// Fan1 Rele int SALIDAPWMFan1 = 1; // RPM base = 759 RPM, Noctua NF-F12 industrialPPC- 3000 PWM...

The first step is to define how you are going to power the fan. For safety, it is convenient that you can turn it off or on at any time. To do this you can use a relay board, there are 2, 4, or 8, depending on what you want to connect. There are already relay boards that work with 3.3V...

Is there a difference between using a PWM pin with default frequency? analogWrite(fan_control_pin, 50); Serial.begin(9600); pinMode(2, INPUT_PULLUP); attachInterrupt(digitalPinToInterrupt(2), counter, RISING); // Yellow Wire And with modified frequency...

You can control the fan power with a relay. And with that you can control the on and off of the fan. You can isolate the PWM control pin of your MCU with a 1N4148 diode Implemented the control on a teensy 4.1 and a 5" 800x480 FT813 TFT

I have seen that the SD library that is installed with any version of teensyduino is improved with layers of the SDFat library. The GDSTx library for EVEx displays that I have worked on is based on the library for gameduino 23x, that library has layers of the original SD library of the Arduino...

A year after the strong adjustments, the fine adjustments begin. I think that the library has all the necessary updates to work without problems with teensy 4.1, some points had given me problems, but I think I have finally been able to overcome them. The library is 100% functional. The touch...

If you allow me, I would like to take another approach. Let's think that you are the one who is going to guide me in connecting the parts of the project. Disconnect everything and tell me step by step how I should connect the screen to the teensy. Starting from all the parts that we are going to...

By the way I use a USB 3 port on the PC. Now I am building the prototype of a fan controller that I will install on the PC to better regulate three pwm fans. I will use a 5" NHD FT813 screen

Something I haven't mentioned before and I apologize for that. Normally powering the teensy 4.1 via microUSB cable gave me problems a while ago. Not only did I see it on the T41, I saw it on an STM32F429 Disk-1 board and an Nucleo-STM32F767 board. When I tried to connect a 5" NHD FT813 screen...

Connect your teensy 3.6 to the PC with Windows 11. Press the reset button for about 15 seconds. You will see that the red LED will start flashing. It is a reset that deletes the recent program in memory and leaves it with the factory program

Did the library work with your 4.3" screen?

Share some photos to see if the settings work as they should, and to be able to adjust something else in case something goes wrong. For the Riverdi 5" BT817 display. I used this bracket:

The timing table on the 4.3" BT817 is different than the 5" BT817. I updated the GDSTx library with the table corresponding to the TFT that you have, it is in the datasheet. Since there are 14 parameters, of which 8 have a maximum, minimum and recommended value, I chose to assign the recommended...

Ok, apparently it must be something in the library. In the congif.h file, what configuration did you use? Did you modify any variables? For teensy 4.1, this is what the library has when it is downloaded from the repository: #ifdef TEENSYDUINO #define SizeEVE 74 // NHD...

Very good TFT you have achieved. Let's see if from a distance we can get it to work with that teensy 4.1. Please, the first thing is to upload some photos of your TFT-teensy arrangement, to see how you want to connect it. You must take great care of the flexible cable of that type of TFT. If...

So you can now see data on the serial monitor with the GD.begin() call?. Brilliant. Waiting for more information about your project PD: Just by using "SD" in the line "SdFs SD", wow, what a thing!

When fixes were implemented in the GDS Tx library, you mentioned that you were building a (taking your own words) "audio vectorscope for displaying oscilloscope art". Indeed there are some incompatibilities between the SD.h, Audio.h and SdFat.h libraries; which overlap with GDSTx.h. In my case...

In theory yes, you just have to consider that the advanced instructions for EVE 2/3/4 are not available, such as PlayVideo, or rotation only 0 and 1. The FT800/FT801 chips have a maximum pixel resolution of 480x272. In the config.h file, you must set: #define SizeEVE 0...

Great that it worked. Please share in the forum some pictures of your TFT working, for me it is feedback, since I can indirectly see how the library works in other variants of EVEx and it allows me to improve the library. A while ago I tried to get a screen like the one you have, but...

The library already includes all the instructions to access the teensy 4.1 SDIO reader. It is not necessary to define anything externally. Using GDSTx and the most recent SDFat library, the example to load an image from a microSD card installed in the teensy 4.1 is: #include <GDSTx.h> void...

I was putting together the PCB to connect to a Teensy 4.1, a 5" NHD FT813 screen, specifically this TFT: NHD-5.0-800480FT-CSXP-CTP, just arrived yesterday afternoon from Elgin, IL. After connecting a few things on the PCB... Example: SdInfo Remember, you must have the SdFat V2 library...

You are welcome. I see that you are using another of the variants, GDT4Xv134. I think there were two other experimental ones before GDSTx. Have you modified the time table of the TFT variants that the library has to adjust it to your FT812 screen?. I mean, have you modified any function in the...

It's been a while since I saw anyone use the GDTeensy4X library. It was a first experiment. For more than three years there have been improvements in the library. The most recent version is GDSTx. Starting from a base, you point out that when drawing primitives it works without problems...

In Mexico, to order a Mouser Teensy 4.1 I had to fill out a questionnaire before they would allow me to buy it. Sparfun has a section indicating the export restrictions to which some of its items are subject. Fortunately my teensy 4.1 is with me, helping me monitor the liquid cooling of my...

What does the "b side" of your project look like, where all the components come together?. I don't know, maybe a loose wire somewhere?

I am in the process of adding the R-pi Pico board that has two SPI ports to the GDSTx library for EVEx displays. On the Teensy 4.1 board it was enough to use the SDIO reader. I have been able to access the second SPI port with these lines in the SdInfo example: // SDCARD_SS_PIN is defined for...

You are right Paul, just as very fast and high-capacity microSD memories have emerged, it is also a fact that these small memories have practically disappeared and the ones we have left can no longer be used as before. My shield gameduino 3 that accompanied me so much, I had to put it in the...