Member Since: February 24, 2007

Country: United States

  • ok I haven’t submitted code in github but there is always a first time. Currently my computer where the code resides is down. So once it is up I will submit some.

  • ok now I think I understand the problem. the Teensy3.1 int type are 4 bytes so I changed the int and unsigned int to int16_t and uint16_t. I have made the changes and testing further. I can share once I am done testing, let me know.

  • Well I will keep looking since I know one problem is the double type is different in the Teensy 3.1 than on the Uno etc. which really is equivalent to float for Uno’s etc. I will run your code on Teensy with the debug print statements turned on. It may be in the calibration routines.

  • I purchased one of these recently and they work fine. I hooked it up and used with Arduino UNO and everything seemed reasonable using the SFE_BMP180 library. but when I tried the same code on a Teensy 3.1 I get completely out of range values for all the parameters read. Yet I can use a library for the BMP85 by and get good results. trying to figure what could be different. between the Teensy and the UNO that give such drastically different results using your code library any thoughts?

  • I download the software for this and played with it in demo mode. I also did the same with the Salea Logic system. Prefer the logic interface on the Salea and the MSO19 logic levels are limited to 3.3volts and below so if using a PIC at higher voltages would be a problem.

No public wish lists :(