FAQs

The answer is both yes and no, and it depends upon what part of the system you are discussing.  The current terminal utilizes an Iridium Short Burst Data (SBD) service as its communications link.  This is a limited length format designed for short messaging applications.

Continue reading...
Tags: |  

The short answer is yes.  The intention is to eventually work with partners to develop a number of terminal designs or implementations.  Admittedly, the current design came about from a very specific requirement and need.   Of course we expect different working environments will have the need for either add-on modules or entirely redesigned terminals.  Currently, however, there are not plans to expand implementations or terminal designs.  Any future developments will depend largely upon the success of the pilot, as well as articulated needs of various user grou

Continue reading...
Tags: |  

The first version of the Chattle Beetle is designed to operate in standby for 36 hours off of internal gel cell batteries.  Therefore, as a standard package, it is assumed that the unit will plug into some existing power source during normal operations.  However, it is understood that some remote locations may not have power, or the current wind/solar/generator power source may be maxed out.  Therefore, partners at the University of Guam have been exploring options for a solar add-on module where necessary.

Continue reading...
Tags: |  

The short answer is yes.  RANET is developing a donor pool to cover messaging costs associated with the primary purpose of the Beetle, which is alert and notification.

Continue reading...
Tags: |  

The specific permissions of who will be able to message which terminals will be worked out further in the first pilot deployment.  In fact the primary purpose of the deployment is to ensure that while the terminal perform well technically, that they can also fit well within existing warning chains and authorities.

Continue reading...
Tags: |  

The short answer is yes, however, the program will not then cover messaging fees or provide other backend system support.  In the current system cost and functionality model, the terminals, messaging gateway, and then desktop management software are all tighly woven.  Nonetheless, RANET is about the mission of communication, and if we can help others develop systems, we will do so.  As the Chatty Beetle system matures, specifications for all the components will be made available on this website.  Where security is a concern, certain aspects, descriptions,

Continue reading...
Tags: |  

There is no cost associated with using the backend messaging system or desktop client, but it use will be limited to regional and national warning authorities, as well as national and local emergency management officials.  Operation of the client will require a modest but reliable internet connection, which the regional and national facilities are expected to provide, along with a standard desktop computer. 

Continue reading...
Tags: |  

Despite its name being somewhat whimsical the RANET Chatty Beetle is designed to a address a serious topic of hazard alert and notification to rural and remote areas.  The original name was the 'RANET Global Messenger', which just seemed to lack all creativity.  In searching for a name descriptive of the alert terminal, the notion of a beetle came to mind.  Beetles are found throughout the globe, and (not being entomologists ourselves) impart a sense of ruggedness and task specialization.  Simply, we though the alert terminal, housed in a protective case and concentratin

Continue reading...
Tags: |