Hi Toon, Good you got it running. I came across this lib too and am convinced the API could be better (but that might procdure less compact code).
And that delay could be documented in the sample you create ;) ;) Joep 2009/7/18 phalox <[email protected]>: > > Hy there! > > After an afternoon of research and trial and error, I finally got my > codelock to work with the keyboard version. > At first I had to 'cheat'. I don't have a 4*4 key matrix, but only a > 3*4. That wasn't so bad to do... but then: > > The documentation for this library is present, but is spread over a > lot of parts. IMO the information is present, but needs to be > collected on 1 website/document/... > > Why are the constants defined so strangely? > > I'd do it more like this: > const row1 = 0b0000_0001 -- match these constants to your > soldering skills > const row2 = 0b0000_0010 > const row3 = 0b0000_0100 > const row4 = 0b0000_1000 > const col1 = 0b0000_0001 > const col2 = 0b0000_0010 > const col3 = 0b0000_0100 > const col4 = 0b0000_1000 > > It says you have to match it to the layout you have (that's, in the > first place, somewhat strange for a library). > I wanted to keep the constants from the library, so I adjusted my > pinout from the key-matrix. > This made the hex values as result become illogical! > > In the docs, it might be useful to notice that a delay is necessary! > This, again, took me a while to figure out why my set-up was acting so > strange! I mean this more like a Hint, not as something obligatory! > > Keep in mind I'm a starter, this question may sounds really stupid to > you guys :-) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
