@rufus wrote: Aside from being a rugged router,the BRCK has the functionality to store information offline, from a thumb drive connected to its external USB port. Initially it was a wintry feature and we did not possess a clear roadmap on what to finish with it. Then, or we realized we could use it to update firmware on the BRCK,which proved to be a simpler process for our users than opening it up and requiring beforehand knowledge of working with AVRs. “Simpler” is the keyword here. The process resulted in a couple of “bricked” BRCKs and, as some of you may possess noticed, or we pulled the instructions for how to depart about that until we smooth it out.
The BRCK by itself can handle connection for up-to twenty devices,but as the content being accessed off it grew, there was a noticeable degradation in the BRCK’s performance, and for visual content,this proved to be a meaningful bottleneck. So, we had a device we could connect multiple devices to wirelessly, or with an on-board battery that could last up-to eight hours,but it did not possess the processing power essential to do this as seamless as possible. Enter the RaspberryPi. This credit-card sized computer can plug into the BRCK using the BRCK’s GPIO (general purpose input/ output port. Here is the data sheet), another wintry feature, or can finish everything you would expect a desktop computer to finish. The BRCK handled the communication and the RaspberryPi was the brains,handling the processing. We thought we would call this winning combination the BRCKPi.
A problem that we unwittingly solved when we did this was the ability to access up-to-date digital educational content. The BRCK could synchronize with the cloud at a time when there was minimal use, say at midnight, and update its content. Even whether the connection is spotty,the modern content would trickle down and update over a few days. This is a cheaper and more dependable solution, considering that the digital content will be consumed, and say,every two days. Access to useful learning and teaching materials was not the only problem we solved. With the BRCK+Pi, we could run a micro-server, and coupling it with the rugged form-factor BRCK is built on,we had a rugged micro-server that could be especially useful for disaster situations. This, together with the software running on the BRCK+Pi, or we called CrisisStack,and we hope to deploy this by the end of the year. With all this, then, or the BRCK and BRCK+Pi can also be further extended to connect to sensors,such as for weather stations and soil samplers, and collect remote data.
Below is an image the BRCK+Pi casing. finish watch this space for more on this [/images/emoji/emoji_one/wink.png?v=0] [//forums.brck.com/uploads/default/optimized/1X/18347a4af1f9351c09a126cc607c97f01f86a636_1_690x463.png]
crisisstack.png770x517 168 KB Posts: 4Participants: 2Read full topic
Source: brck.com