Some of the FAQs about using RAPIDSEA for developing embedded firmware and products quickly
- What is RAPIDSEA and what is its use?
- How can I program with RAPIDSEA?
- I am an experienced programmer. Why will I need RAPIDSEA?
- Why is the data-driven approach followed?
- What target platforms do RAPIDSEA support?
- Can it be ported to any other platform?
- I am not a fan of IDEs. I like to program by hand. Does RAPIDSEA support such interface?
- What are the features supported in RAPIDSEA?
- Can I add my own modules inside?
- I have a display interface in my application. Does RAPIDSEA support GUI?
- How to buy RAPIDSEA?
RAPIDSEA is an acronym for Rapid Deployment Suite for Embedded Applications. It is a combination of software modules and programming interface designed for reducing time to market for embedded applications.
The Flint IDE provides an easy way to program the applications. The steps to be followed typically are
- Define the Input data objects and its properties
- Define the Output data objects and its properties
- Select the Modules that uses these data objects
- Set the hardware functionality being used
- Configure the lower level driver modules according to the hardware functionality
- Add the higher application modules that act on the driver modules
- Code the logic to convert the input data to output data
For example, to develop an application that needs to read temperature over SNMP with a sensor connected to one of the AIN channels of eStorm-C1, steps to be followed are
- Define a data object named 'raw_temperature_value' as integer
- Define a data object named 'actual_temperature_value' as integer
- In the Module selection screen, identify the pin to be connected to the sensor and configure it as ADC.
- Drag and Drop the 'ADC Converter' module to that position
- Drag and Drop the 'ADC Bridge' and map the 'raw_temperature_value' data object
- Connect the Ethernet Module to the Ethernet pins and in turn drag and drop the TCP/IP module.
- In TCP/IP module properties, configure the properties suitably and enable the SNMP option.
- In the Data Configuration View, map the 'actual_temperature_value' to the SNMP MIB object.
- Finally edit the change handler for 'raw_temperature_value' and multiply the scaling factor to get the actual temperature value and store it in the output data object.
- Save the project and the Hex file will be generated in the configured path. Load the same in eStorm-C1 and now it is ready!
Thus the application can be developed and deployed in minutes. The video demo of this example can be found in RAPIDSEA Demo.
There is no doubt any application can be developed with or without RAPIDSEA. But the difference is the development time and effort involved. With RAPIDSEA all the software modules necessary are already available as a package. The functionality is already tested completely by us and is proven. So there is no need to reinvent the wheel!
Since any system, especially embedded, acts on an input data, process it and outputs it in some way, we used this model to program the application. Further the user can even write code in procedural model.
Currently eStorm-C1 is supported. And since the port is primarily for LPC1769, it can be used for any LPC176x platform.
Yes, the overall design is modular with well defined interfaces. It can be ported for any other platforms
IDE is only one way of programming. Users can configure and program the application directly with 'C' language coding. The API's are clearly documented.
RAPIDSEA supports most of the features needed for running an application for any type of industry. Some of them includes TCP/IP stack with HTTP server, SNMP support etc, GSM/GPRS stack, GPS receiver, USB stacks etc.
The flexible architecture of RAPIDSEA allows easy addition and customization of modules.
Yes, RAPIDSEA supports integration with Embien's Sparklet library. In fact, Flint IDE can be used to program both RAPIDSEA and Sparklet. So with Sparklet and RAPIDSEA, a graphical application can be designed very fast.
Contact us in our email address email@example.com