Hi Gordon, no it's not I'm afraid. Thanks for testing your side to confirm it's ok on the firmware.
The earlier post in the other thread was pre-obtaining the correct resistor. At that point I believed that my issue. (I thought i better leave that thread alone as it appeared to be unrelated to firmware since I installed several of the earlier binaries to test which I should have mentioned here. Same result as 1.69)
I'm baffled. I suppose I probably need to try a sensor from a different supplier but is there a chance the bluetooth module has anything to do with this? I've powered down the CC3000 to rule it out but obviously the bluetooth is soldered on so powered up all the time. I'm clutching at straws with that though.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Hi Gordon, no it's not I'm afraid. Thanks for testing your side to confirm it's ok on the firmware.
The earlier post in the other thread was pre-obtaining the correct resistor. At that point I believed that my issue. (I thought i better leave that thread alone as it appeared to be unrelated to firmware since I installed several of the earlier binaries to test which I should have mentioned here. Same result as 1.69)
I'm baffled. I suppose I probably need to try a sensor from a different supplier but is there a chance the bluetooth module has anything to do with this? I've powered down the CC3000 to rule it out but obviously the bluetooth is soldered on so powered up all the time. I'm clutching at straws with that though.