Wireless access is everywhere and has become an essential convenience that customers expect businesses to provide. Wireless connections can become unreliable and suffer in high density use areas like trains, buses, cafes and stadiums. Users can face slow bandwidth, dropped connections and interruption when streaming video.
To improve wireless reliability, quality, and performance in high density areas, AOIFES has created a software solution called “Cognitive Hotspot Technology (CHT)” that runs on Gateworks Single Board Computers. CHT software is intelligent and designed to efficiently handle a large number of concurrent connections. Wireless access points with CHT software installed throughout a train or building can communicate with each other in real time allowing them to make intelligent decisions based on the current load and demand by the users. CHT increases throughput performance by over 400% thereby increasing the capacity of both number of simultaneous clients and the bandwidth availability for high QoS applications such as video streaming.
CHT on Gateworks SBCs provides the following advantages:
Provides Advanced Load Balancing
Increases network capacity and reliability
Increases network speed and performance
Reduces RF emissions, interference, and electricity consumption
Reduces the number of needed Wireless Access Points
To learn more about CHT and Wireless Access Points using Gateworks SBCs:
Nearly 7 million drones will be shipped by 2020 according to FAA estimates. UAVs require communication to a ground station over a wireless link providing information such as HD video and telemetry data.
Gateworks has Single Board Computers that are Drone & UAV Ready such as the Ventana GW5510 shown below:
HDMI Input for video cameras
High Power Mini-PCIe Slot for wireless radio
Communication busses for telemetry data
Industrial Temperature Ratings from -40 to +85C
Made in the USA
GStreamer Software Framework for video transmission
For videos and more about Gateworks SBCs for Drones and UAVS, visit the link below:
Android is growing fast in embedded applications. The Gateworks Android Development kit is a great starting point for customers that need to get going quickly with both the hardware and software.
To aid in Android software development, Gateworks has developed an example Android application showcasing the interaction of the software with the Gateworks Android hardware. The application features support for the user GPIO, LEDs and more. An easy to use Android library is also provided which can be utilized for any custom application development.
Gateworks has documented Android Software on the following wiki pages:
OS Development – This wiki page covers items dealing with the lower level operating system. This includes items on the serial console command line such as init scripts, ADB, partitions, command line networking, LED control, GPIO control and other hardware integration.
App Development – This wiki page details the building of an Android App (APK file) independent of building the entire Android OS. Topics covered include setting up the Android Studio IDE, writing sample code for a Hello World App, as well as using an external Gateworks code library for accessing low level items through the app such as GPIOs, LEDs and more.
Gateworks Android Library – This is a library that allows easy integration to low level system items such as LEDs, GPIO, PWM and voltage and temperature.
Gateworks Android Demo App
Gateworks has used the information above to create a Gateworks Demo App that is publicly available on GitHub here. The app features a user friendly front end for controlling some hardware features on the board utilizing the GateworksUtil library. Screenshots of the app can be seen below:
Figure 1. (Above) LED control of the trigger and the on / off state. GPIO as input or output and state.
Figure 2. (Above) Hardware system statistics
Figure 3. (Above) PWM enable, period and duty cycle.
Gateworks recently featured a blog in which 8 video cameras were connected to a Gateworks Ventana SBC and then displayed on a HDMI monitor. This is useful for localized applications. For remote applications there is another solution.
Remote applications require streaming the multiple video streams over the network (Ethernet or WiFi). For bandwidth efficiency, all camera inputs can be joined together into a single frame and then transmitted across the network.
To join all the streams into a single frame, a software element of GStreamer called a compositor is used. Older versions of the compositor relied on the CPU and caused choppy video. Gateworks recently started using gstreamer-imx which contains a hardware accelerated compositor which is far superior. With this compositor, each stream can be positioned on the frame and then linked to a RTSP stream in the H.264 format.
An example is shown with two Gateworks Ventana SBCs that are on the same network.
Start the following pipeline on the SBC with the cameras connected:
Everyone desires computers that boot very fast! The software that is shipped by default on Gateworks boards is tuned to be very ‘developer friendly’ for getting started in the development cycle. Common questions like: ‘How can I make my software boot quicker?’ are asked frequently and Gateworks has devoted time into documenting various methods of increasing boot speed or boot speed perception (see http://trac.gateworks.com/wiki/boot_speed). Gateworks has additionally improved boot speeds by implementing U-Boot’s Falcon mode in the Ventana bootloader. Gateworks Ventana is the first IMX6 based board in mainline U-Boot to get this support.
What is U-Boot Falcon mode? Falcon mode is named after the Peregin Falcon, the fastest member of the animal kingdom. U-Boot Falcon mode speeds up boot time by bypassing the bootloader completely which can save 3 to 10 seconds depending on the system configuration.
Continuing with the technical details, Falcon mode is a feature of the Secondary Program Loader (SPL) which is built from the same U-Boot source that builds U-Boot proper. The job of the SPL is to configure the memory controller and load the next stage – which is typically the full-blown, feature-rich U-Boot bootloader, which in turn is responsible for loading the OS. The U-Boot bootloader can easily add 3 to 10 seconds to the boot-up of a system depending on its configuration, the boot medium (Flash vs micro-SD for example) and the filesystem on that boot medium. To bypass the loading of U-Boot, the Ventana SPL now supports reading an OS kernel and boot parameters (or ‘args’) directly from NAND flash blocks or raw micro-SD sectors (sans filesystems). This typically takes 1 to 2 seconds, depending on the size of your OS kernel and results in being able to have a fancy graphical splash-screen show up within the first couple of seconds of power. What the OS does next is very dependent on the application and OS configuration. If several seconds are shaved off in getting to the OS with Falcon mode then the system boot time has been sped up in some cases significantly.
Keep in mind that using Falcon mode is something that should be done at the end of the development cycle as the U-Boot bootloader features that are bypassed can come in very handy during development.