None of I2C function use the internal timer, but they need time to execute. I should be able to build the board today.
Out of curiosity... did you also tried to test it with ISIS?
|
None of I2C function use the internal timer, but they need time to execute. I should be able to build the board today.
Out of curiosity... did you also tried to test it with ISIS?
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
|
I have no licence of ISIS. If I had I would be happy
Well, I have now the clock working(it means running the way it has to do) and it looks like the settings of the menu is now a software-thing what I have to debug and modificate. My old version did work but to make it timerinterrupt I had to change the code. So, I think I have make some mistakes at that part of the job. It looks like it runs the menu for one time and don't wait for inputs.
For this part thanks for all your help!
It is a option to use also a interrupt for the inputbuttons...
|
Well, its workingfinally!
The only thing is that the display dos not change when a button is pushed-in. so, when you hold your hand on a button so it will count crom 1,2,3,4 and release it by five, you see the 1 untill you release the button.
I have to finish that part..
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks