Sorry - the list of usable pins was supposed to read "0, 1, 6, 7, 13, 14, 18, 19, 23, 26". These are also the only pins clickable in the Console's GPIO Tool, along with pins 8 and 9, which while clickable they resort to Direction: Output and - respectively - Value: 1 and Value 0. Are schematics for these modules available anywhere for the community? These would help immensely!
Thanks for the reply. The device must indeed have been running some processor-intensive stuff, though I don't know what! I have not yet figured out how to run anything yet, and the device was well past boot-up. Since the thing only acted weird that one time, I'll consider it a fluke.
Apologies for the delay, we're still a fairly small team so depending on support ticket volume or spikes in requests, we can be swamped at times. Rest assured, if it's in the queue, we will get to it asap.
@Pavils-Jurjans I apologize for causing the embarrassment. Unfortunately wifisaint doesn't have any logs right now. However it does output dmesg when it encounters errors. Can you describe what you were doing?
Our new wifi setup tool will be released soon, and hopefully it will eliminate all of these issues.
I have only used motion on the raspberry pi, but it's function is to take a photo or short video when motion is detected. It is a much simpler algorithm than opencv. You can actually use opencv to detect objects and faces. I haven't used it yet, but now have a book on the project and intend to try to get it to recognize members of my family.
I was able to get the omega to stream video pretty easily (there are other threads). It was a pain to get the streaming library compiled on the pi.
@Boken-Lin Thanks - had already found this. I think some of my issues to date have been to do with my mistakes in building kernel code using the OenWRT cross compilation - I think I had some settings wrong. Am in the process of trying again with git://git.openwrt.org/15.05/openwrt.git - will let you know how things go.