Mindboards

Hi, Finally I found the solution. It was mainly a problem in the timer configuration. Now the driver is independant from any timer. There's still a lot of things to do to make the driver clean, but I hope we will publish a release soon, with other drivers in ada/ravenscar. Thanks for your advices (a...

Hi In fact my question on pull up/down was stupid because at every moment in the initialization procedure you control the clock (you set it manually to 0 or 1). So there is never any floating value, and no need for pull up/down... I'll try your trick with the scope maybe tomorrow. Thank you very muc...

I couldn't have access to a scope with memory so I couldn't see what I sending. But as usual I could see I was sending things (I have up and down levels on clock and data lines, so I suppose I'm talking to the sensor ;) ). In the standard firmware It seems that the clock line is pull-up whereas the ...

When you send the mode data are you also toggling the clock line? You also need to keep the clock and data lines stable for a short period. The easiest way to debug this would probably be to attach a scope to the cable between the NXT and the sensor and run either the standard firmware or leJOS the...

Hello, I'm currently trying to write a low level driver in Ada for the lego RGB color sensor 2.0. I saw the communication protocol in Lejos (and in the open source firmware) code and I wrote the corresponding code of the initialization sequence in Ada. As far as I understood the initialization proce...