I'm starting to work on switching my product from the T3.5 to the T4.1 for obvious reasons.
I've shipped almost 350 units with T3.5 but I am down to my last 20(ish) T3.5's on hand.
Here are the areas of concern I have with functionality that I'm using with the T3.5.
I'm trying to find and research all the differences with the T4.1 and head off any major gotchas.
I have read a lot of forum posts on the areas below but here are my thoughts.
Dev Environment: Currently using Arduino 1.8.8 & TeensyDuino 1.4.5: I plan on upgrading to the latest on both. Hopefully no breaking changes with my 8k+ lines of existing code?? I hate the way all the libraries get upgraded/changed with no easy way to lock them to a specific version without making my own copies of all them. Maybe there is a better way..
Lack of 5V tolerance: I am adding a few level shifters to my board to take care of this. No prob.
ADC/AREF: I have been using AREF pin with a TI precision 3.3V ref. (This possibly has always been overkill but it works)
T4.1 doesnt have AREF.
I'm trying to decide if switching to the T4.1's onboard 3.3V for my application is going to be fine and if the 12bit max(10bit practical) is going to be good enough. Application is reading a 10k precision String Pot for distance measurements. I will be testing this soon. I have thought about adding external ADC..
EEPROM: Code changes necessary? Looks like it may work exactly the same as is..
RTC: I currently use a Touchscreen to enter Date/Time so the user can set it.
Using this code with <TimeLib.h>
RawHID: I talk to T3.5 using rawHID from a C# App. I also flash FW using my custom app.I embed my .HEX file into app source code. Is this going to be possible with the T4.1 or are there breaking changes with the way they are flashed that would make this impossible? I did see reference to the same 4 magik bytes used for T4.0.
RA8875: It looks like there has been enough work done on the libraries to make this work with T4.1.
I'm not looking for exact answers for any of this as I know I didn't provide enough info in some cases. I'm just throwing this out there to get any helpful tips or areas that I may be overlooking here at the start of the changeover from T3.5 to T4.1.
I've shipped almost 350 units with T3.5 but I am down to my last 20(ish) T3.5's on hand.
Here are the areas of concern I have with functionality that I'm using with the T3.5.
I'm trying to find and research all the differences with the T4.1 and head off any major gotchas.
I have read a lot of forum posts on the areas below but here are my thoughts.
Dev Environment: Currently using Arduino 1.8.8 & TeensyDuino 1.4.5: I plan on upgrading to the latest on both. Hopefully no breaking changes with my 8k+ lines of existing code?? I hate the way all the libraries get upgraded/changed with no easy way to lock them to a specific version without making my own copies of all them. Maybe there is a better way..
Lack of 5V tolerance: I am adding a few level shifters to my board to take care of this. No prob.
ADC/AREF: I have been using AREF pin with a TI precision 3.3V ref. (This possibly has always been overkill but it works)
Code:
analogReference(EXTERNAL); analogReadRes(16); analogReadAveraging(32)
I'm trying to decide if switching to the T4.1's onboard 3.3V for my application is going to be fine and if the 12bit max(10bit practical) is going to be good enough. Application is reading a 10k precision String Pot for distance measurements. I will be testing this soon. I have thought about adding external ADC..
EEPROM: Code changes necessary? Looks like it may work exactly the same as is..
RTC: I currently use a Touchscreen to enter Date/Time so the user can set it.
Using this code with <TimeLib.h>
Code:
dateTimeSetting = makeTime(dateTimeElements);
Teensy3Clock.set(dateTimeSetting); setTime(dateTimeSetting);
RawHID: I talk to T3.5 using rawHID from a C# App. I also flash FW using my custom app.I embed my .HEX file into app source code. Is this going to be possible with the T4.1 or are there breaking changes with the way they are flashed that would make this impossible? I did see reference to the same 4 magik bytes used for T4.0.
RA8875: It looks like there has been enough work done on the libraries to make this work with T4.1.
I'm not looking for exact answers for any of this as I know I didn't provide enough info in some cases. I'm just throwing this out there to get any helpful tips or areas that I may be overlooking here at the start of the changeover from T3.5 to T4.1.