thanks for response. I really love what your company is doing and I’m committed to going to other solutions once I make something usefull with current one.
I have executed both Python and C test examples. I haven’t checked Scratch, since it’s not for me. I started with Python, although I know C better, but checked C later as well. BTW. There is bug in C example for Touch sensor. I proposed the change, althogh I don’t know git well yet, so not sure about the result. PORT4 is not recognized, should be PORT_4.
Regardless the language, the result are values between 1014 and 1023. With C example it means reporting that button is constantly pressed.
Just background: I have RasPI 2, Advanced BrickPI and checking sensor either with power connected through RasPi or external 8AA pack connected to BrickPi. No difference. The sensors and motors I have are from educational EV3.
What is interesting, I found, that C and Python examples differs. For example LEDs works in Python (both examples), while not at all with C. I haven’t figured out the reason yet - not focused on that so far.
Gyro and Ultrasound sensors seem to work with C, so I can see more less proper values, although the results are not perfect. Maybe this is sensor fault reporting that way, being not enough accurate. I haven’t worked with Lego Mindstorms before so I cannot compare yet.
With Python examples the results are totally different and not usefull at all. No angle reading like 0, -1, -2, 0, 1, 2 on Gyro with C, but those 10xx mostly 1023.
So far noticed difference in readings through GetBits being different offsets, but I haven’t analyzed those functions yet to see that matters.
But Touch sensor is total failure, both C and Python.
I mostly test using one sensor connected at a time, although sometimes there is more connected more. No difference though.
Hope that will help to diagnoze.