osmars

Apache Redhawk User Manual

Apache Redhawk User Manual 6,4/10 3629votes
Apache Redhawk User Manual

Dec 19, 2011 - hai can anyone provide me redhawk apache userguide. It would be a great help. Apache Redhawk User Manual Apache Design Inc. RedHawk, RedHawk User Reference Manual, (2015), (Online) Available:apache-da. Castle Miner Z Usb Mods. com/.

REDHAWK Description REDHAWK is a software-defined radio (SDR) framework designed to support the development, deployment, and management of real-time software radio applications. To support the design and development of software applications, REDHAWK provides tools that allow development and testing of software modules called 'Components' and composition of Components into 'Waveform Applications' that can be seamlessly deployed on a single computer or multiple network-enabled computers. The REDHAWK integrated development environment (IDE) provides tools to support development of REDHAWK software. The development and deployment of REDHAWK Applications are aided by graphical editors and drag-and-drop Waveform construction. The IDE allows users to interact with and control multiple running REDHAWK instances and applications. Recent Announcements (December 2017) - Download the new Core Framework, IDE, and documentation from our page.

The effort in REDHAWK 2.1.2 focused on: Core REDHAWK Features and APIs • Shared address space Components: Significant enhancement of Component model and BULKIO to support high performance I/O. Preliminary developer documentation for the REDHAWK 2.1.1 Beta Release is available. This feature will be under extensive evaluation during the 2.1.x beta release series and is expected to provide the ground work for several new major enhancements to REDHAWK. • Implementing a new zero-copy IPC mechanism for BulkIO that uses shared memory to transfer data between two processes on the same host.

This is a follow-on enhancement to the shared address space Components feature. Preliminary developer documentation for the REDHAWK 2.1.0 beta release is available. • FrontEnd Interfaces (FEI) Property definition change: For Devices, the FRONTEND::tuner_allocation and FRONTEND::listener_allocation allocation properties are now writeonly instead of readwrite. Because the properties are now created as writeonly, they can no longer be queried. This change was made to prevent confusion with the actual state of the FrontEnd Device, which is reported by the FRONTEND::tuner_status property. Existing Core Asset FEI Devices have been updated with this change.

New FrontEnd Devices created with the IDE will automatically have this change. • Adding support for a new type of Property, utctime, extending the list that includes types such as short or string.

This timestamp Property is used in PropertyChangeEvents and can be queried from Components/Devices with the id QUERY_TIMESTAMP, which is useful when synchronizing the state of the system. Utctime can be used by Component/Device developers as an additional type of Property. • Adding functionality for capacity to be reserved for an entire host collocation on the SAD file. The reservation is a capacity floor for the Components in the host collocation, where the amount of capacity utilized by the aggregate set of Components is this reservation or actual, whichever is higher. This reservation is allocated against the target GPP running this Application, allowing the GPP to verify that the request can be satisfied, reducing the likelihood of over-subscription. • Adding support for DCD files to have a startorder attribute, which functions similarly to the SAD file's startorder. On startup, 'start' is automatically called on Devices and Services (when possible), and on shutdown, reverse-order 'stop' is called.

The IDE's tooling for DCD files has been updated to display and edit startorder. • Adding support for the DeviceManager to resolve run time environment settings when deploying Devices and Services that have soft package dependencies. • Resolving issue so that during Application release, calls to the Application object no longer result in misleading errors. • Adding functionality within the code generators so they create C++, Java, or Python constants for enumerated values defined in the PRF.

• Improving flexibility to ignore GPP threshold checks when determining if the GPP should go into a BUSY state. • Removing some obsolete options from the Core Framework and BulkIO configure scripts. • Resolving issue where processes with spaces in the names would cause the GPP to terminate.