Search results

Please remove me from this forum board and with it all projects we contributed. Leave no trace behind!

Wow! 11,000 views. If you listen to those who probably flunked basic math 101 in school, this view count turns out to be only 250 views! On the other hand, just maybe, there is a keen interest for a different Teensy PCB form factor which allows full access of ALL GPIO. :cool:

A train wreck in which there is a definite low cost solution provided by HWGUY? Your cut and paste left off "A bit of humor ..." and is directed to "topper" who does his best to hi-jack any topic for his own entertainment. You can read Paul's mind?

WOW! With a topic on this board, with over 10,000 views, PJRC should re-think their marketing strategies for future products! First, don't release a product without bread board capabilities. Remember the dweeb who offset the Arduino headers so the board could not be bread boarded? Second...

@HWGuy Fully bread board compatible - no end pins. Inexpensive hardware solution. Easily accessible VIN with jumper. Great solution for all GPIO pins. A job well done...

The word "Teensy" means small. Now days, ARM chips have a very large count GPIO pins. Most 64 pin ARM chips could have counts of greater than 50 GPIO. To be useful, the GPIO should be "easily accessible" so users can utilize all the GPIO for complex applications. The word "Teensy" really...

Back on topic ... @iwanders - what is the estimated cost of this extension?

You must be new to this board. Please do your homework before speaking! In fact, several of our non-commercial projects are even showcased on the PJRC projects!!!!:confused:

Remembering way back, we had to shame PJRC in doing any type of work for low power. We always said "Apple computer chose the ARM chip for low power - why doesn't PJRC have low power for their Teensy ARM chip?" :rolleyes:

One library was the "low power library" and it was not done by PJRC. Most of the work was done by the fine gentleman from State College, Pa - Duff.

There are two of us? I wager that there are many more due to the number of views on this topic! Totally amazing! :D

We are extremely flattered but the answer is NO.

Release the hardware and wait for others to finish the software? Wow ... sounds like uncompensated forum members are helping a commercial enterprise make $$$$ money on their FREE software help/contributions BUT don't ask for a 48 pin ARM Stamp! :rolleyes:

Not my finances but what my customers are willing to pay.

Good, I hope the software is finished at the same time as the hardware. We waited 1.5 - 2 years for the Teensy 3.1 software libraries to be in decent shape so we could finish our projects.

No can do - due to the high price of the Mini54 in which PJRC has total control.

Anyone who has purchased a product from PJRC is a customer of PJRC. The last time I have checked PJRC is a commercial enterprise. Most commercial enterprises will go out of business if they don't listen to their customer's needs/wishes. To settle this topic, once and for all, take an informal...

Some people must have flunked basic math 101 and can't count pass the 1 digit.:) These same people cannot be trusted to do any type of marketing study for electronic products.:rolleyes: To do a un-bias study, there should be a separate thread for each forum user to vote and show his/hers...

https://forum.pjrc.com/threads/24633-Any-Chance-of-a-Teensy-3-1?highlight=Teensy-LC LargeDuino and if Paul could produce a 48 pin Teensy 3.1 maybe it could be called Teensy 3.1 LE (limited edition) The cost for a user to produce such a special ARM stamp would not be cost effective unless it...

This topic is a conundrum ... the definition of conundrum is a situation where there is no clear right answer or no good solution. The Teensy name was built on microcontroller(s) which are small and tiny. ARM chips are very small in footprint but carry a large number of GPIO. You can't have...

Now if someone could come up with a solution for the Teensy 3.1 and NOT talk about the future Teensy 3.x++ !!!! BTW ... there is a dead link for the Teensy 3.x++ on this forum board. It died last November. The 3.x++ is just vaporware until released and if it was released tomorrow, it would...

I don't care if you bury the GPIO in 4 layers or 6 layers, you will probably still need a larger Teensy footprint in any case when you re-surface the GPIO on the top layers. :cool:

With close to 2000 views on this topic, there is a great chance that, just maybe, there is a keen market interest for a Teensy 3.x 48 pin ARM stamp or clone. :) BTW ... For now, Talldog's Tindie 48 pin expanded GPIO solution works just fine. :cool:

Clean is not easy when you step on many entrenched users.

The end of creative destruction ends here. :(

There is the "Free" DipTrace PCB program with 300 pins max. limitation. It automatically generates the necessary files for PCB production.

What you are seeing are several entrenched users that any extra GPIO is worthless to them. I see a major obstacle in ever producing a differential form factor Teensy and that is the high cost of the bootloader chip. :(

... then you might change the Teensy name to LONGduino. :)

In a sense, all ARM chips are compatible BUT how long did it take to port the software libraries, from the T3.0 to the "ARM compatible" Teensy-LC and T3.1? It was a great effort by many users/beta testers on this board to bring it to final fruition. (Along with Paul S.) Correct, we have the...

The problem is on the next "future" Teensy, Teensyduino users will have to wait for another 1.5 to 2 years for the software to be created and debugged. Right now, the Teensy 3.1 with resource heavy 256K flash, 64K Ram with loads of GPIO, would be the perfect candidate for a new GPIO pin/bus...

It is extremely hard for me to say this but I think I found a new religion in stevech's suggestion of a modular, stackable, bus for the Teensy 3.x. Maybe a 48 pin dip is not necessary but a square with "all" the GPIO properly engineered for a common stackable bus.

If the shoe fits ;) <-- a bit of humor - no offense. Why re-invent the wheel? :confused: ... There are many SeeedStudio four pin "Grove" boards and also many "Click" boards from MikroElektronika. All a user would need is a common interface board from the Teensy 3.x. :cool...

There you go ... if any user steps forward and produces a larger 48 + pin version of the Teensy 3.1, then I would be the first to purchase your design if the price was reasonable! :)

Only PJRC knows this answer but it's a shame to cost the end user lots of money to access the extra GPIO on the bottom of the Teensy 3.1. At the time, Paul S. was under the gun with Kickstarter to produce and ship a product on-time. I believe (IMHO) many users will "pay up" a few dollars for...

For $12 more, I can purchase a Teensy 3.1 breakout from Tindie which breaks out all the GPIO but adds layers of unnecessary connection points. (no offense talldog) Why not just redesign (PJRC), from scratch, a "clean" 48 pin Teensy ARM stamp and be done with it? I really don't believe it would...

Update ... Our GPS wall clocks have be running for months and the center "blue" status NeoPixel has never come on in either wall clock. This would indicate loss of GPS signal for more than 30 seconds. Having a loss of GPS signal, the wall clock would fall back to the Teensy-LC software clock...

Any (serial) examples using the stream class I could examine?

@Paul Does Teensy 3.x support the class stream?

Since we had a "Hydra smart power supply" laying around we used it for power isolation between the Lidar lite sensor, the CPU and the servo. Our "top secret" drone radar detector works fine. :cool: http://www.chrobotics.com/shop/hydra

How about a 3 pin switch jumper and a battery fuel/gas gauge? The fuel gauge is worth more! :cool:

That's just like saying "that a halogen bulb can be battery powered" It can be but the batteries won't last long! NeoPixels aka WS2812b are not known to conserve power but by reducing the color intensity from 255 down to 5 will allow the wall clock to be battery powered. Just get yourself a...

@duff I am very surprised your statement coming from the only state in the union that takes the first day of deer hunting season off as a holiday. You forgot crossbows and bows and arrows! They will also take down a drone. ;)

Slugs are good for 100 yards and probably would do the most destruction. :cool: There won't be that many "certified drones" flying for about 2 years until new laws are made by the government. In the meantime, its open season on any drone passing over my airspace!

Alternate use for the WS2812b/NeoPixel 360 degree GPS wall clock display ... Using my circular NeoPixel LED display with the 40 m Lidar Lite mounted on a servo I was able to detect low flying drones in the area. A 12 ga. shotgun should be able to take them down at 40 yards! :cool:

My approach, in using any microcontroller, is to see what it can do without spending years of developing software for it. For one person to port FreeRTOS and ChibOS and make everything work with all the commands and libraries would require a very knowledgeable source like Paul S. Energia MT...

Energia MT (Multi-Task) Multitasking is the ability to run multiple tasks or threads concurrently on a microcontroller. In Energia MT, multitasking is achieved by treating each tab as a separate task and letting TI-RTOS and Energia take care of the rest. Currently, Multitasking is supported on...

@onehorse Your Teensy charger is great! Since the new Teensy-LC Mo+ ARM stamp sleeps in uamps have you ever entertain the thought to also providing a battery monitor aka fuel guage in addition to your lipo charger? Link design ref...

For the hardcore hackers ...

For those who are entertaining the thought of ever constructing this 360 degree WS2812b/NeoPixel Teensy driven NeoPixel display, here are some pointers... You will probably need above average soldering/de-soldering and electronic troubleshooting skills to finish this project. There are close...

When both alternate green hour LED hand and red LED minutes hands are at the "same position", the clock is read a such ... Example 7:35 35 minutes after 7. (hand color = Green/Red/Green) ... with both hands on 12 ---> 12:00 reads green/red/green This clock was not designed to save power due to...