Search results

Still works great, thanks!

Still not yet? Thanks, Mark

Are there any Snooze power consumption measurements for the Teensy LC? (Haven't found any.) Since the LC features the MKL26Z64VFT4 supposedly a "ultra-low-power MCU" this should be interesting. Thanks for all info. -Markk

Thanks everybody for the feedback. Can you share your pad reduction parameters or are they a trade secret :-) ? Thanks, _Markk

Hi duff this is quite fascinating. Looking forward to the scope pics. Many thanks! Just to be clear, from my perspective it's most important to fix idle() aka wait(). Personally I can live with some transition jitter in REDUCED_CPU_BLOCK and sleep() because I use those with low frequency...

Thanks veng1 That's exactly what I thought. So on the second revision I pressed down quite hard. No change. I ordered with Seeed and its a 0.12mm stencil, so ~4.7 mil. As I said I pressed down quite hard but it still looks way too thick: Perhaps it would help to reduce the cream layer...

Ah, I completely misunderstood! Now that I reread after a good night of sleep it was obvious. Apologies. Thanks for the tip about pressure because I obviously got it wrong, thinking I had not enough pressure for the stencil to really touch down on the BCP fully and therefore not scraping off...

Thanks for the answer but this is about using a DIY reflow oven with a solder paste stencil. I would never finish my design with hand soldering ;-) I hope I'll soon find time to start document the project. It's a Teensy 3.1 custom build + MCU controlled MPPT solar charger + weather station...

Homemade reflow oven + QFN? Hi I know it's probably a bit OT to ask about this here but has anybody any experience with "homemade reflow oven" + QFN? I've successfully made a custom build Teensy 3.1 with various chips down to 0.5mm pitch and 0603 parts. But all pins were visible/outside so...

Just a guess: could it be that Audio is enabling the DAC? According to the data sheet it consumes between 150 and 700uA. Snooze does not handle the DAC. The SIM_SCGC6_DAC0 control bit is commented out in kinetis.h which probably has a good reason. At your own risk you could probably switch...

Oh I see. Nothing "automagical" there. Thanks. Just for clarification (more to myself): idle() aka wait() during either normal run mode or VLPR does not go through that code. So it's still valid to say: the systick interrupt should be left enabled and millis() remains accurate. :-)...

Good to know, thank you. Will wrap my head around it ;-) _Markk

Hi duff again thanks for the quick answers. I think you misunderstood my test results. Idle does NOT "mess up the Idle + millis" inside REDUCE_CPU_BLOCK if (and only if) you leave the systick interrupt enabled. It works! Although the reference manual states that systick is tied to FCLK (and...

Systick should remain enabled! Hi duff I think the cpu has built-in support for maintaining a stable systick clock. I studied the reference manual which I don't really understand. There is this LPO output always at 1kHz (except in VLLS0) driven by the PMC clock (see page 144). But I don't see...

How to release() a channel temporarily Hi Paul thanks for this great lib! Any particular reason, why release() is not public? If I understand the code correctly it already handles everything fine for repeated begin() and release() pairs; with channel == 16 signaling the "released" state...

Hi duff thanks for the fast reply. I should clarify first: this is not about the absolute power values. I'm quite confident that your lib provides the correct savings (I'm looking at the "minus" from normal run mode). My post is more about the capabilities and performances (most specifically...

Hi first a big thank-you to duff for the formidable Snooze lib! I'm playing around with continuous ADC+DMA in low power modes and/or with lowered CPU frequencies. Here are some insights and issues for comment. First I tried a ADC setup in normal run mode with different CPU frequencies. The...

I had to sacrifice a third DMA channel to reliably get rid of the lag. This will probably complicate DMA channel usage for other purposes down the road (there are only 4 triggered DMA channels in Teensy 3.1). I guess I will have to release and reacquire channels when switching between different...

Went to the scope Just went to the scope. Doubled the caps to be sure. This is the typical scope output (dark blue is comparator output against the 2.2nF cap, bright blue is the Schmitt-triggered AND-gate's output) As you can see the comparator indeed (sometimes) changes his mind twice but...

Here's a schematic: -Markk

Hi Paul thanks for the elaborate feedback. In my case it's a bit more complicated to add hysteresis. It's an integrator reset circuit. When the integrator hits bottom or ceiling it is supposed to self-reset, i.e. discharge the integrator capacitor. This works very well. At the same time I...

Thanks for the info. What I found out in the meantime: the Teensy 3.x has the passive filter not enabled on the input pins by default. If I got it right, one would set/clear the filter like this: // switch passive filter on *portConfigRegister(pin) |= PORT_PCR_PFE; // switch passive...

Hi I'm using attachInterrupt() on pins. It works most of the time. However some pulses are lost. Because the phenomenon is associated with a related signal "acceleration" in the analog part of my circuit, I suspect the pulse width might be the issue. The signal is still strong and well...

Success! Just wanted to report that it works like a charm. Thanks to Xenoamor again!

Serial Number of Teensy 3.1 Maybe add this right after the MAC entry: 128-bit unique identification (ID) number per chip https://forum.pjrc.com/threads/25522-Serial-Number-of-Teensy-3-1?p=72175&viewfull=1#post72175 For custom builds this is the [only?] way to get a unique number, I believe...

That's one reason I'm currently favoring the "half SPI.h + half native as the ILI9341_t3 lib does" approach "Using an #ifdef fest" to "get both, portability and speed, using a simplified ILI9341_t3 lib pattern one way". The demo by Paul is really impressive! Also, only a template class is...

Yes, I think I understand SPI Transactions reasonably well and I know it's just an incremental consensus solution, not wanting to break the Arduino "way of life". It is clear that many problems can't be solved adequately with the SPI Transactions' still simplistic approach. One would need...

Hi I'm trying to find the right way to write a "model citizen" SPI device library, maybe even a reusable base class for such devices. Looking at diverse libraries I'm now a bit confused. These are my findings: For portability you would have to go with SPI.h Strangely there is no separate...

Very nice! The K20 datasheet is really cryptic... I really believed only timers [and IO modules] can actually trigger them... Thank you guys. -Markk

Hi It's amazing how simple solutions have generally become with DMAChannel. Great work and thank you! Still I'm stuck here: I tried to find out if a digital pin input (edge) can trigger a DMA transfer (random pulses from outside, not periodic). NOTE: I know I can trigger DMA from the...

Would be very nice to have in Teensyduino Something like that would be very nice to have in Teensyduino! _Markk

Confirmation: it works! Just wanted to add one more confirmation that the Constantin Eagle lib worked very well for my custom build. Will post more about my project, once I got the time. Thanx again, Constantin! _Markk

That's exactly what I tried, but stupid me forgot to select the Teensy 3.1 board in the Arduino IDE. I usually work with Visual Micro for Arduino inside Visual Studio (where the spoofing worked anyway). Note the additional typedef I use in the spoofing Wire.h #ifndef _WIRE_SPOOF_I2C_T3_...

Thank you very much for this explanation and verification! Based on your inspiration I tried the following but I failed FAILED: 1) Create a Wire directory in <sketchbook>/libraries: 2 ) Create a Wire.h file in it with the following contents: #ifndef _WIRE_SPOOF_I2C_T3_ #define...

I think this will not work, because the library .cpp files are compiled independently without any influence from the sketch.

Yes but it's not about my sketch, it's about the 3rd party library. For instance I use the Adafruit_INA219 lib and it's header Adafruit_INA219.h includes <Wire.h> (see the code there). So I would need to modify that header. --Markk

Thanks for the quick reply! >Yes, you may want to replace wire.h in these libraries with i2c_t3.h But if I change the 3rd party library I lose the update capability. If a new version is released I have to re-modify it. With many libs this becomes a nightmare. Also, if I want to distribute...

Spoofing <Wire.h> to <i2c_t3.h> Hi thank you for this great library! I have a project where I use many i2c devices. So libraries by other people are involved. These typically #include <Wire.h>. Am I correct that there is no way but to modify these libraries to switch them over to i2c_t3...

I need more frequent wakeups that every 200ms. :( Paul, can you please confirm that when I connect the MINI54TAN reset testpoint to ground, it will a) not allow anyone to (accidently) reprogram the Teensy b) draw almost no power c) not disturb the I2C lines (high-Z) I looked at the MINI54TAN...

Thanks a lot!

Sounds promising.. however attachments do not seem to work? -Markk

Thank you Constantin! I noticed your symbol has a different layout as compared to the schematic published by Paul here whereas kam42's is a match. Obviously I'd like to recreate Paul's schematic as close as possible in order to avoid mistakes. I can always rearrange Connections later...

Hi I added the Teensy 3.1 MK20DX256VLH7 to the library, also adding the DAC0 pin 18 DAC/A14 as per https://www.pjrc.com/teensy/schematic.html. Thank you kam42! Paul, perhaps you could update the mentioned link. Thank you very much! --Mark

Hi, the time_t is (by convention) simply the number of seconds, since January the first, 1970, UTC. As such you can calculate and compare these as you can with seconds. The Alarm library takes a time indication and a function name to be started at that time. So BeginHeatingMorning is actually...

Thank you, I will try to follow up on this suggestions. The "common mode choke" seems to be exactly the creature that I need. Nice tip. -Markk

I think I misused the term "ground loop". It was always RF and AC noise pickup that I was concerned about. Will have to learn much more about those terms, about ferrites, "chokes" etc. Thank you Jp3141 for the pointers!

Before I throw it over board I definitely need to learn more about it. Is it possible to get the part number or spec? Thank you very much .. for everything! Markk

Hello William thanks! I guess it's difficult to communicate. This is the "guidance" forum, so things are not yet all worked out and I can't show you finished schematics etc. Hen and egg. :confused: This is where my concerns come from...

Anyone? Please?

Hi thank you all for the great work! I'm trying to figure out the right way to use GND and AGND in a project. There is some info in another post, but I'm still unsure. I'm not formally schooled and new in electronics, so I read a book about PCB design. I learned about ground loops, when and...