PLLefebvre
New member
Hello, I am new to teensy and actually to arduino framework as well. Our previous projects are based on the microchip ecosystem mainly on PIC24 and dsPICs.
We would like to switch to the open source world for our next project. We have selected the Teensy 4.1 for our next project's proof of concept and so far it is going very well.
For this next project we need much more processing power to implement a set of complex equations for a measurement application. We dont have a large team and the schedule for this project is very tight. So instead of developping the microcontroller HW interface we are seriously considering to use the Teensy 4.1 right away within our PCB.
The product that we develop will operate in the field for several years in a controlled temperature room (10+). It will need to be reliable 24hour/day, 365 days/year. Any operation failure of the product could cost a lot for our customer. So far our demo board is reliable. The beta FW keeps the internal MCU temperature below 50 degre celsius. So the microcontroller will not be overwhelmed with our application. The system that we develop will need to pass a certification including EMC emission and immunity tests.
It will be a very low volume production of say 20 to 30 modules per year. We would like to select a platform that will stay around for several years (dev board and IDE). The big concern is availability of the module for the next 10 years as well as the firmware development platform (IDE). We are using platformIO so far with teensyduino and the onboard booltloader to develop the firmware. The product that we develop will need to be supported for FW updates (say one release per year) and we will need to build PCB with the Teensy for a minimum of 10 years from now (there is already a long term agreement for the service that we offer).
I would like to have your recommendations if this approach (using Teensy 4.1 in a commercial product) is viable on:
The legal side (There will also be some legal dpt questions to make sure it is ok to sell products with Teensy board embbeded. Is it?);
For the reliability 10+ years 24/7;
The platformIO with VSC IDE for firmware development and support;
The very long term support that we need to adress for this product (10+ years).
Should we go with the open source or should we continue with Microchip and switch to their M7 microcontrollers platform?
Thanks for reading this full BIG Question
We would like to switch to the open source world for our next project. We have selected the Teensy 4.1 for our next project's proof of concept and so far it is going very well.
For this next project we need much more processing power to implement a set of complex equations for a measurement application. We dont have a large team and the schedule for this project is very tight. So instead of developping the microcontroller HW interface we are seriously considering to use the Teensy 4.1 right away within our PCB.
The product that we develop will operate in the field for several years in a controlled temperature room (10+). It will need to be reliable 24hour/day, 365 days/year. Any operation failure of the product could cost a lot for our customer. So far our demo board is reliable. The beta FW keeps the internal MCU temperature below 50 degre celsius. So the microcontroller will not be overwhelmed with our application. The system that we develop will need to pass a certification including EMC emission and immunity tests.
It will be a very low volume production of say 20 to 30 modules per year. We would like to select a platform that will stay around for several years (dev board and IDE). The big concern is availability of the module for the next 10 years as well as the firmware development platform (IDE). We are using platformIO so far with teensyduino and the onboard booltloader to develop the firmware. The product that we develop will need to be supported for FW updates (say one release per year) and we will need to build PCB with the Teensy for a minimum of 10 years from now (there is already a long term agreement for the service that we offer).
I would like to have your recommendations if this approach (using Teensy 4.1 in a commercial product) is viable on:
The legal side (There will also be some legal dpt questions to make sure it is ok to sell products with Teensy board embbeded. Is it?);
For the reliability 10+ years 24/7;
The platformIO with VSC IDE for firmware development and support;
The very long term support that we need to adress for this product (10+ years).
Should we go with the open source or should we continue with Microchip and switch to their M7 microcontrollers platform?
Thanks for reading this full BIG Question