redhawksdr

问题 I have the latest version of Redhawk and CentOS, and I have run into a few problems right off the bat. Initially I couldn't see the Chalkboard and Sandbox, but that issue was resolved by commenting out (#) one of two lines in the eclipse.ini file: -Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB -Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton I found this fix from here. It was noted that while there were no obvious errors that arose, there may be some unforeseen problems. The issue I

问题 I am attempting to install REDHAWK v1.8.2 on a fresh install of CentOS 6.4 32 bit, but I am unable to get omniNames and omniEvents to start. sudo /sbin/service omniEvents stop Stopping CORBA event service: omniEvents sudo /sbin/service omniNames stop Stopping omniNames [ OK ] sudo /sbin/service omniNames start Starting omniNames [ OK ] sudo /sbin/service omniEvents start Starting CORBA event service on port 11169: omniEvents: [25848]: Warning - failed to resolve initial reference 'NameService

问题 I am trying to run a second node on a different processor, either an ARM or a second x86_64. I have a DomMgr running on one x86_64 and attempting to start a node on either another x86_64 or arm using nodeBooter. The DevMgr starts and registers with the DomMgr but when it starts the GPP device it "Requesting IDM CHANNEL IDM CHANNEL IDM_CHANNEL" and then immediately "terminate called after throwing an instance of 'CORBA::OBJECT_NOT_EXIST'". The DomMgr printed out to the console that "Domain

问题 I'm using REDHAWK 2.0.4 on CentOS 7 I'm trying to follow the tutorial here: https://www.youtube.com/watch?v=SttCsAIQtSA At 11:14 they add a device dependency to the xml file: <usesdevicedependencies> <usesdevice id="device_connection"> <propertyref refid="DCE:cdc5ee18-7ceb-4ae6-bf4c-31f983179b4d" value="chirp"/> </usesdevice> <usesdevicedependencies> And this <connectinterface id="device_connection_1"> <usesport> <usesidentifier>dataFloat_out</usesidentifier> <deviceusedbyapplication

问题 Using: Redhawk 1.9 / CentOS 6.4 (32 bit) / C++ implementation Creating a new FRONTEND::TUNER device Using default setting on code generation. Following port required for FRONTEND Digital Tuner and regenerate the code. <ports> <provides repid="IDL:FRONTEND/DigitalTuner:1.0" providesname="DigitalTuner"/> <provides repid="IDL:FRONTEND/RFInfo:1.0" providesname="RFInfo"/> </ports> After generating code make updates to port_impl.h and port_impl.cpp to get around the problem as defined in: error:

问题 I am working with a REDHAWK 1.9, Linux GPP, and a ARM GPP. I have a waveform that includes components across multiple GPPs. In this waveform, I have the same component (with same name) running on the Linux GPP and the ARM GPP. I have 2 different directories for this component on the host PC (Linux - running Domain Manager). I have one that is compiled on Linux (X86) and one compiled on ARM. The problem I have occurs when I create the Waveform with the IDE. Using the IDE it only sees one

问题 I've installed REDHAWK 2.0.0 from rpms on CentOS 6.7, run shell scripts as required, configured omniORB as required, updated SDRROOT permissions as required, and run cleanomni from a terminal command line, but cannot get REDHAWK_DEV to launch in the REDHAWK IDE. Right-clicking on Target SDR > Launch Domain... brings up the "Launch Domain Manager" dialog box with: red 'x" over the label 'Domain Manager'; default Device Manager visible and selectable; and "OK" button greyed out. Attempting to

问题 RedHawk installs JARs for eclipse plugins from redhawk-yum-1.10.2-5-el6-x86_64.tar.gz. In RedHawk 1.9 it only installed 4 JARs for IDL parsing and editing, but in RedHawk 1.10 it installs these 4 but also 2 from Eclipse Corba Package. gov.redhawk.eclipsecorba.idl_7.1.0.201501292343.jar gov.redhawk.eclipsecorba.idl.source_7.1.0.201501292343.jar gov.redhawk.eclipsecorba.idl.edit_4.1.0.201501292343.jar gov.redhawk.eclipsecorba.idl.edit.source_4.1.0.201501292343.jar net.sf.eclipsecorba.idl_0.7.0

问题 I am trying the Waveform example from chapter 5 of the documentation, but I do not see any output from the Siggen port or from the hard limit port. I set the frequency down to 50 MHz and connected the out port of the siggen to the in port of the hardlimit. I am trying to run it from a local domain manager, and it appears to start correctly. But, when I select Plot Port Data I just get an empty plot. On the Domain Manager console I see this right after starting the waveform: INFO

问题 I am using RedHawk v2.1.0 . Does anyone know how to prove that RedHawk-SDR confirms to the SCA(Ver.2.2) specification? Is there the evidence conforming to the SCA specification, or is there a verification/certification tool in RedHawk-IDE? Alternatively, if You have proved that RedHawk-SDR is compliant with the SCA specification, please tell me how to do the method. THank Youssef-san for document https://github.com/RedhawkSDR/redhawk/releases/download/2.0.0/SCASpecification-REDHAWK-2.0.0.pdf