Thanks.
In my last code posting you will see I had that line commented out. That is because, as I replied to J , it did not make any difference to the output. (It is true that LED does get brighter). I was probably erroneously basing my expectations of what these functions really to on UNO implementations which is quite different hardware. That is why I generally try to avoid these dumb-me-down libraries doing stuff analogWrite to a gpio pin !
Uncommenting this line I'm still getting erratic input data, but with a brighter LED.
Can you suggest a suitable current limitting resistance and/or potential divider values to reduce the risk of input damage connecting to a 5V IMU?
Where is the 470R resistor on 4.0 if I want to lift it off?
Thanks.
In my last code posting you will see I had that line commented out. That is because, as I replied to J , it did not make any difference to the output. (It is true that LED does get brighter). I was probably erroneously basing my expectations of what these functions really to on UNO implementations which is quite different hardware. That is why I generally try to avoid these dumb-me-down libraries doing stuff analogWrite to a gpio pin !
Code:
pinMode(LED_PIN, OUTPUT);
Uncommenting this line I'm still getting erratic input data, but with a brighter LED.
Code:
IO pin test.
pin10 = 0
pin10 = 1
pin10 = 1
pin10 = 1
pin10 = 1
pin10 = 1
pin10 = 1
pin10 = 1
pin10 = 0
pin10 = 1
pin10 = 0
pin10 = 0
pin10 = 0
pin10 = 0
pin10 = 0
Can you suggest a suitable current limitting resistance and/or potential divider values to reduce the risk of input damage connecting to a 5V IMU?
Where is the 470R resistor on 4.0 if I want to lift it off?
Thanks.
Last edited: