My previous post was not about the pin that never gets in high level, dont worry about that, it’s probably a bad contact in some solder point. Once I get my multimeter back’ll test. I just posted the code because I thought I might be doing something wrong in algorithm to activate sensor. But if algorithm is correct, problem should be on board. Also I was not sure if the ticks system that I did would work.
The issue is that I can not understand why you guys refuse to give examples of source code. I see several threads of users asking questions that could be answered with a few lines of code, but instead you send the datasheet’s link.
After all, what’s the problem in put some code example in user guide? To make wixel most friendly you guys dont need to change anything in it. Just make a more friendly documentation. I’m not saying you guys have to explain the concepts involved. Microcontrollers are all kinda similar, use the same concepts, it is easy to find information about the concepts. But details of wixel programming is not easy to find and you guys do not make it easier for users.
For example, no one needs to explain me the concept of timer and interrupt, I know what it means and I also know the working principle. And I read a lot about it in datasheet (SDK documentation dont say a single word about timers and interrupts). All I needed now was to see some code example, few lines, that’s all. And I asked this a few times, including in the post where I put my code. But this seems to be a taboo subject here. Other users have asked same thing in other threads and all they got was a link to datasheet.
But i got your message:
And hell, maybe you’re right. Perhaps wixel is the wrong choice for this project. I’m not just trying to make a little robot. I am a professor in a college which has some computer courses but none related to electronics or mechatronics. My project is introduce robotics in college creating a little robot that has a very simple electronics, so that it could be easily replicated by students, but that can run relatively sophisticated programs and encourage students to program robot. As I enjoyed working with Wixel and had success with basic programming, I thought I could use wixel in this project. But if this is the posture of you guys, it will not work.
I was trying to avoid Arduino because it’s too easy download and install programs on it without knowing what is happening. Also I would have to provide wireless communication with another device, which would endearing and complicating the project. But now I have to rethink this issue, because students will not have where to seek information to make programs, and even crosses my mind to suggest that they study the datasheet.
When you have some time, take a look, is not done yet, but is in progress. Wixel is mentioned in introduction:
fperrotti.wikispaces.com/Projet … m%C3%B3vel