So the 4.x optimisations are mixed in with the old 3.2 stuff? Sigh.. I'm currently using teensy 1.59 & the 1.8.19 IDE for writing this stuff. I'd figured I was back far enough. Guess not.
I totally understand why you are not interested in...
Yes, I know. But in this case I have no say in the matter. Some are specced for int32_t and some are insisting on int64_t. I notice that the instruments that I'm using to display the values (marine applications) are using the int32_t versions of...
Like I said it was late and I was tired. Just because the function is declared in the .h file doesn't mean I don't need to actually write it in the .cpp file.
Thanks again for the help. What you were all telling me pointed me in the right...
What's going on. This is converting GPS data (read in as text string) to NMEA2000 data packet. (binary) They are looking for latitude/longitude in degrees. Then multiplied by 10^16 and stuffing the result into a signed 64 bit integer. Kinda'...
Well, the speed should be fine for this. I only need to calculate it twice per second. As for the 4.x teensy? I'm getting there. I only have about 1/2 dozen 3.2 teensy's left. Then I will be switching over.
P.S. Thanks for letting me know the...
Actually, I see that it's listed as 32 bit processor. Do I need to use double to get the precision? I have some picky math in my immediate future.
-jim lee
Wait, I tried switching it over to serial3, nothing. So I removed the added serial device all together. Nothing. I'm sorry to have bothered you guys. I obviously have something else going on here. Maybe I cooked one of the SPI pins messing about...
Thanks. But that isn't working either. I have pin 7 free and I can move move pin 8's wire to pin 6. This'll leave Serial3 free of anything. I think I'll try that for now.
-jim lee
That still seems to get in the way of the SPI port. (That likes to use pins 9 & 10 as chip select) Or maybe I'm doing it wrong?
Serial2.setRX(26);
Serial2.setTX(31);
Serial2.begin(9600);
-jim lee