Search results

The second problem noted here is slightly less severe than it seemed to me. The single-color values are integers, but with a unit size of 4. That is, the integer division to compute dr/dg/db will cause bad gradients, but only in relatively extreme cases, like the narrow-gradient wide-rectangle...

I tried 99luftballons with DC & CS connected per the #defines (10 & 9) and then swapped. My board doesn't have the touch controller connected. so that's not the issue. When I upload 99luftballons (with either cabling), it claims inability to read the board's registers, trying with various SPI...

The library manager thinks that the available version is 1.1.1. Is that your latest? Using that one, the compiler looks at demosauce and says loading library from c:\Users\rrf\Documents\Arduino\libraries\bb_scd41: invalid library: no header files found FQBN: teensy:avr:teensy41 Using board...

I updated Teensyduino, and I deleted any ILI9341_t3 files still in Documents. (Why does the IDE Library Manager put them there?) ILI9341_t3.graphicstest now compiles, loading library from c:\Users\rrf\Documents\Arduino\libraries\bb_scd41: invalid library: no header files found FQBN...

Thanks for your continuing help. I gave the full diagnostic output for ILI9341_t3.graphicstest in post #1. I hadn't thought of putting the compiler into verbose mode. When I do that with ILI9341_t3.graphicstest, I get loading library from c:\Users\rrf\Documents\Arduino\libraries\bb_scd41...

Thanks for your effort. Inasmuch as I just installed the ILI9341_t3 package fresh via the IDE, I don't understand why your results are different from mine, unless my copy of the compiler is corrupted. If no one else has any useful suggestions, I'll try reinstalling the IDE. Thanks for the...

I searched my C: drive and removed all non-Adafruit files named ILI9341*.*, and I then reloaded the ILI9341_t3, ILI9341_t3n, and ILI9341_T4 libraries by using the library manager in the Teensyduino IDE. The resulting folders were all in Documents/Arduino/libraries. ILI9341.graphicstest still...

No, 4.1 is selected.

For what it's worth, the graphicstest sketch in the AdaFruit_ILI9341 package works fine, except for having a default screen size smaller than that of my device.

I am trying to connect an ILI9341 display unit to a Teensy 4.1, running the Teenyduino IDE (2.3.6) under Windows 10.. The IDE is running normally with other sketches. When I try to run the graphicstext example from the ILI9341_t3 library, the compiler says In file included from...

There are two problems with the fillRectHGradient and fillRectVGradient routines, one trivial and one deeper. In the fillRectHGradient routine, each h in the line dr=(r2-r1)/h; dg=(g2-g1)/h; db=(b2-b1)/h; should be w. The fillRectHGradient routine was probably written by copying the...

The area looks clean to me, even under magnification. I have blown the whole unit with compressed air anyway. If there is another freeze, I'll probably be able to revive this Teensy again, but is there any sort of informative probing that I might do before resuscitation?

After several days of continuous operation, not connected to USB, in an application described elsewhere , a Teensy 4.1 (S/N 1532053) abruptly froze, with its USB-proximate LED flashing in groups of 4. Power-cycling didn't help, but when I reconnected the Teensy to the Teensyduino IDE, I was able...

The first time (7+ days) I probably did try holding the Program Button, as you suggested, and the recovery can be attributed to that. I should have mentioned this. The second time (52 days), alas, I definitely did try the Program Button method, without success.

Thanks for the idea, but I never use millis().

I started this thread to report that a Teensy 4.1, not connected via USB, had frozen after over a week of continuous operation. Rebooting had no effect, and it could not be restarted until the app was reloaded from the Teensyduino IDE. The thread got sidetracked into a discussion of Windows...

I was caught off guard by Paul's page drawing attention to my old home monitoring project. The project is in the middle of some fairly broad redesign, and I am trying to avoid getting sucked into a 2.0 syndrome. I was not planning to say anything new about it here until the redesign was...

This system has evolved quite a bit since that writeup was produced. Now that you've drawn attention to it, I feel obligated to update the description. Among other things, some components use (and all components will use) Teensy 4.1s instead of 3.5s.

I have considered moving to Windows 10, but each time I have come across another way in which it is intrusive and Web-dependent, so I have put it off. I'll look at it again. But: The trigger for this thread was USB- and Windows-independent. I have a Teensy 4.1 that went into a deep frozen...

I have a stable app running on a Teensy 4.1. After more than a week of uninterrupted operation (not connected to any USB port), the Teensy froze, and power cycling did not revive it. When I reconnected it to my computer (Windows 7/64) and tried to reload it from the Arduino IDE (2.1.1, CLI...

thanks for your interest Yes, I have pullups, and in fact it is all working after I made the correction shown in post #2. Thanks; that turns out to have been (as you noted) unrelated to my original problem, but I'm glad you spotted it.

I2C problem solved; I failed again to RTFM Here's what I missed: // MCP4725 test program ... void tMCP4725::Setup(uint8_t Addr) { _i2cAddr = Addr; // Wire4725.begin(Addr); // ********* this is what I had Wire4725.begin(); // ********* this is what it should be } //...

I am developing an app that will make limited use of a MCP4725 DAC. I have used the MCP4725 before, driving it with Teensy 3.5s. I can't get it to work with T4.1; there seems to be an interaction between the i2c apparatus and the Serial channel. This test program // MCP4725 test program //...

I'm sure that's true, but I see my project as one that could be extended as needed, possibly by contributions from people with specialized experience. For example, the board might have multiple sockets, so it could accept various Teensy form factors, with (of course) only one socket in use at a...

Thinking about it some more, the rig you describe and my fantasy board are directed at different tasks. PJRC doesn't knowingly sell Teensies that work except for one or two bad pins, so their rig is presumably optimized for rapid sell-or-trash decisions. In the field, I think most people...

Can you give a reference to that test jig?

The code described in the https://forum.pjrc.com/threads/55735...l=1#post324323 post covers only a small part (digitalRead) of the Teensy's functionality. If I told you "This Teensy seems to be working perfectly," you would assume that I had looked at more than digitalRead. Also, using the...

I have an app that connects Teensies to a variety of other hardware. A few days ago I blundered and connected an external opamp (LV321, rated up to 5.5V) to a Teensy 3.5's Vin (about 8.8V) instead of the intended 3V3. That destroyed the LV321, and it also did obscure damage to the Teensy...

Does anyone else have experience with the VC0706 cameras? I have a large T3.5 app in which AF_VC0706 is an instance of Adafruit_VC0706(&Serial2). AF_VC0706.begin() succeeds, but then { // motion detect WhatMeasured = wm2VC0706Motion...

Terrific, that solved it. I can stare at syntax things like this for hours and never see them. Thanks. Although that solved the problem, I still don't understand why the program was doing what it was doing. It was writing to D02, D03, D13 and (when it should have been writing to A14) to...

I hadn't known about analogWriteResolution, and it's probably a good idea to put in that call to complement the analogReadResolution call. On the other hand, it's unlikely to solve the problem I asked about. Something is changing the DAC output when no such change is programmed, and that...

As part of my modular datalogger project, I have been developing a depth monitor for my backyard pond. The sensor just lets the pond water (more of it when the water level is higher) be part of a voltage divider, where the voltage is supplied by a Teensy. There is a tiny bit more to this...

Ignore this thread for now. I think the problem is some sort of hardware instability. I may need help, but I'm not properly prepared to ask for it.

Following a suggestion in a thread that might be related, I turned verbose compiler output on. The last few lines of the output are [not legible as screen capture. The only libraries mentioned between Opening Teensy Loader and Sketch uses ... are SD, SdFat, and SPI, each in the likenamed...

I have an old application which now fails when it is recompiled and reloaded. On each "peripheral station" PCB of the application, a Teensy 3.5 is connected to a variety of hardware, notably including a TeensyView display. When the code is recompiled and reloaded, the Teensy can't find...

eInk Before adding an eInk display to your project, think about the intended refresh rate and number of lifetime refresh cycles. I designed an AdaFruit red/black eInk display into one of my projects, and I regret it. Over the course of a few thousand refresh cycles, black text became...

pictures I'm sorry; I hadn't been aware of that rule. Here are pictures (in use) of the base station and two peripheral stations. The design is always evolving, so the "TV room" peripheral board is of a slightly different (newer) design than the "office" peripheral board.

That's implementation-dependent. Two standard LZW routines should produce the same output, but one or both implementors might have diverged, thinking that the output was never going to be decoded by any decoder but the one he/she provided. For example, it's natural to put the code table at the...

It depends what you mean by "done line by line." Most of the output of an LZW compression is a string of 12-bit codes that capture the input, but there are also one or more 4096-entry tables that tell what the codes are. The early codes in the table just encode single ASCII characters, but...

The LZW method runs through the to-be-compressed data only once, generating the output as it goes. An implementation that appears to be file --> file is coded with the primitives initialize get next byte output next 12-bit code finalize That's it (not that each of those is altogether trivial)...

All of the good compression algorithms are adaptive, so compressing an all-zero file is not very informative. The best compression routines for linear files and still images look for progressively larger patterns in the data, and then encode these patterns in short, file-specific codes. The...

My unit had been running on a table that got occasional direct sunlight, but the display was -- does this make a difference? -- always faced away from the sun.

e-paper hardware questions (slightly off topic) This is not exactly on topic, but this thread seems to have collected some members with e-paper experience that I'd like to draw on. I have an Adafruit e-paper display that I have been driving from a Teensy 3.2. The Adafruit site first...

update This project has been variously updated. See https://www.fenichel.net/pages/Indoor_Activities/electronics/datalogger/datalogger.pdf

This expands on my previous answer about sampling rates. The key to tuning the system has been that all of the configuration information is on the uSD cards. The only numbers hardcoded into the sensor drivers are minimum read intervals and the like, taken from the sensors' datasheets. Every...

This varies from sensor to sensor, but rarely as often as once a second. Remember, these are measurements of what is happening in & around an ordinary house. Why measure the temperature of a room every second? Why measure the temperature of a pond more often than every hour? The...

Several other forum members have described dataloggers for high-bandwidth datastreams, often status data from moving vehicles. I have completed a project that flexibly collects data from two or three dozen low-bandwidth sensors placed around my house, taking VC0706 pictures; measuring...

Yes, of course. I knew it would turn out to have been a slip at that bonehead level, but I stared at the code without seeing it. Thanks. Using .h & .cpp files makes a lot of sense when there is non-trivial time to be saved by not recompiling modules until they've been changed. Using that...

addendum: the uSD card is 2GB, formatted FAT32 all of the example SD programs run without problem

I have been having difficulty with a datalogger-style project; all of the code for the failing component is in the attachment. This component receives messages from remote components via XBee transceivers, and then it (for now) just stores the incoming data The problem is all in the...