Inline C Node on Blackfin Beta 2.0

I am using the Labview Embedded for Blackfin beta 2.0
I am trying to run the example for 7.1 where the processor uses an Inline C Node to detect its IP address.  Everytime I put down the node, the error message tells me that inline C is not supported for the current target.  The target is the BF537 EZ-Lite kit.  I thought the inline C node was supported?

To add an Inline C Node to a VI, the VI must be opened in the context of an embedded target. Move your VI under a Blackfin target in the LabVIEW Project, then open it.
Michael P
National Instruments

Similar Messages

  • How can I know the latency in a sub VI or routine (inline c node) in blackfin module?

    Hi, I want to control a transceiver using a BF-537. The two principal taks are programming the transceiver and send/receive data from transceiver. These operation are development with sub-VIs, little routine in C using inline c node, etc. However, I need to know the lantency of each sub-VI or code writing in C; I need to know how much time use these elemnt to finished your function.
    If anybody know How Can I to measure the lantecy, I will be grateful...!
    regards
    The Caribbean

    Hello,
    The easiest way to benchmark how long operations take on the Blackfin is to insert timing code in a sequence structure to directly measure the timing with the Tick Count function.  Bear in mind, of course, that adding this code will itself affect your timing somewhat.  Take a look at the example below to see what I mean - you could just repeat this for each operation you wanted to measure.
    Message Edited by MattP on 07-31-2007 10:50 AM
    Message Edited by MattP on 07-31-2007 10:50 AM
    Cheers,
    Matt Pollock
    National Instruments
    Attachments:
    benchmark.jpg ‏16 KB

  • Cisco ISE inline posture node Posture assessment query

    Hi all,
    i read the user guide for the ISE 1.1 and in the Inline posture section, I picked up the following text which concerned me if I understand it right...
    "In a deployment, such as outlined in the example, when more endpoints connect to the wireless network
    they are likely to fall into one of the identity groups that already have authenticated and authorized users
    connected to the network.
    For instance, there may be an employee, executive, and guest that have been granted access through the
    outlined steps. This situation means that the respective restrictive or full-access profiles for those ID
    groups have already been installed on the Inline Posture node. The subsequent endpoint authentication
    and authorization uses the existing installed profiles on the Inline Posture node, unless the original
    profiles have been modified at the Cisco ISE policy configuration. In the latter case, the modified profile
    with ACL is downloaded and installed on the Inline Posture node, replacing the previous version."
    Does this mean that if a corporate user VPNs in and successfully passes posture and gets a dACL applied to the session allowing full access, will the next user completely skip posture assessment and granted full access to the network if they are a member of the same AD group?
    I am planning on using the iPEP for posturing VPN clients and using AD groups to determine the correct dACL to apply to a particular VPN session.
    Thanks!
    Mario

    I'm not too familiar with the actual operations of the Inline Posture node, but it seems to me that the only things that are more or less "cached" are the authentication and authorization profiles that have been previously matched. So, even if they're "cached" and a endpoint matches and authorizes based on those policies, it would match on the policy that provides a pre-posture state. So, a PRE-POSTURE ACL would be pushed and an URL redirect would also occur to the NAC agent download portal (if the endpoint doesn't have it already).
    After posture is assessed, a change of authorization would occur and reauthorize that endpoint's session.
    So, in short, even if the profiles are cached, they only deliver pre-posture profiles. After posture assessment, the endpoint is goes through reauth via CoA.
    If you have access to the partner education connection, I suggest checking out the VoE deep dive series for ISE. There's a posture presentation that would probably help you out.
    https://communities.cisco.com/docs/DOC-30977
    HTH,
    Ryan

  • Inline C node QEI lm3s8962

    I'm trying to get the QEI modules to work on the LM3S8962 board and I understand that there is no LabVIEW VIs for it. I'm trying to use inline C to get everything working but I keep running into an unexpected interrupt when I look at Keil. I have enabled the QEI module and enabled the QEI Interrupt, but I still get stuck in an infinite loop. Has anybody gotten this to work or has some knowledge on the subject. I'm pretty new to LabVIEW and QEI so I apologize in advance.
    Thanks for any help.

    Hi,
    I have never used the QEI module but I can recommend a process to create a driver for LabVIEW embedded for ARM:
    First try with a simple c program, for this:
    Go to this folder: C:\Keil\ARM\Boards\Luminary\ek-lm3s8962\ 
    Copy and paste the LCD_Blinky folder and rename it to LCD_QEI for example.
    Open the Blinky project in the LCD_QEI folder.   Now try to do a small driver for QEI in this project.
    For example create two files QEI.c and QEI.h with two functions: QEI_init, QEI_ReadPos .
    Add these two functions in the main program and display the QEI position in the onboard display.  
    When the QEI driver works fine on a simple Keil µVision project, you can add the driver in LabVIEW.
    Please let me know when you are at this point.
    Best regards
    Yann C.
    France

  • ISE Inline Node

    I have an ISE Inline Node that I successfully added to my admin ISE node.  After I added the inline node, I wasn't able to configure it until later.  When I went back to edit the configuration, the admin node says it is not able to communicate with the inline node.  Below is the exact error:
    Could not establish secure connection with Inline Posture node. Please be sure that certificates are configured correctly for mutual authentication between this node and the Inline Posture node.
    The certificates haven't changed since I initially added the node.  Also I am not able to open an SSL session to the trusted IP of the inline node.  I am not sure if this is normal or not.

    Yes I caught this during the upgrade, so my nodes were already deregistered. Since I was planning on rebuilding my setup I went ahead and reset the configuration (or you can issue the pep switchoutof-pep command - http://www.cisco.com/en/US/docs/security/ise/1.1/cli_ref_guide/ise_cli_app_a.html#wp2150747) in order to rollback the configuration to standalone and make the certificate change.
    Just for you reference here is the link that will help you nail down the cert requirements (Step 3) -
    http://www.cisco.com/en/US/docs/security/ise/1.1.1/release_notes/ise111_rn.html#wp248769
    This should do the trick for you!
    Tarik Admani
    *Please rate helpful posts*

  • Blackfin Performance Profiling

    Hello,
    I'm acquiring 32 bits signals in which only 18 bits are used.   As the acquisition rate is around 4.5 MHz and last a few seconds, I must compress my data.  Therefore I wrote a simple VI that takes an array of 4 32 bits data (where only 4*18 bits are usefull)  and convert it into an array of 9 U8 of data.  The conversion takes 0.4 us on my computer (Quad Xeon) but more than 60 us on the Blackin which make no sense.  I'm using the BF548 evaluation kit running at 600 MHz where 60 us equals almost 36000 operations...
    I'm using the TickCount (ms) over multiple calls the conversion VI to know get my execution time. 
    Is there any known issue with the TickCount (ms) function?   Is the evaluation kit expected to run slower for any reason?  I've attached the LabVIEW project to this message.
    Regards,
    Patrick Lessnick 
    Attachments:
    bitstuffing.zip ‏33 KB

    Patrick,
    From my discussions with R&D we are not experiencing a bug.  Its a unique challenge to streamline performance with LabVIEW for Blackfin since there are so many additional caveats we don't usually have to worry about in LabVIEW for Windows. 
     If performance is the chief concern, here are my recommendations.
    Use a shift register.
    Don't use a subVI. The code will be larger on the diagram, but it will be faster and smaller on the chip.
    Don't use build array in the low level part. Instead, Initialize an array outside of the loop and index into it.
    Turn on optimization. For example, turning on Disable parallel execution should have a significant effect.
    If all else fails and our generated code just isn't fast enough (which I doubt), there is still the Inline C Node that he can use for doing something like this.
    Given these recommendations please let me know if you have any additional questions or concerns.
    -Mark
    Mark
    LabVIEW R&D

  • Blackfin Timer Access

    Hello All
        I am currently evaluating the Blackfin BF537 EZ-Kit w/LabView Embedded. I would like to use this unit for an application that requires measuring the time between triggers. What I would like to do is create an interrupt driven application that would raise an interrupt when a trigger occurs on the timer's input terminal. The interrupt handler would then read out, and reset the timer. The 32 bit counters on the blackfin would be ideal, but I cannot find a reference or an example to illustrate how to access and configure the counter/timers to perform this function. Would I have to use a code window to work with the timers, or is there a VI that already does this? In the Blackfin>Device>Common palette, there are VI's that would seem to be able to create a connection to the timers, but they require a device reference? What are the device references for the BF537?
    Thank you for any help you can provice
    Sean Sexton

    Hi Sean,
    You might want to take the link and copy it into Start>>Run. It
    should work if you have VDSP++ 4.5 installed in the default location.
    There are several ways to import external C code into LabVIEW. The one
    I recommend is the Inline C Node. This node is located on the
    Structures palette. You can type C code directly into it, just like you
    type text into the Formula Node or the Mathscript Node.
    You could also use the Inline C Node to call a function that is defined
    in an external C file. If you do this, you should also right-click on
    the node and Add a header file that prototypes the function. You could
    then add an external C file to your build specification that implements
    this function.
    You can add inputs and outputs to the Inline C Node. That is the recommended way to pass data to/from LabVIEW and C.
    Michael P
    National Instruments

  • Logical and Physical Standby on same Node

    Is it possible to have a logical and physical standby database for a primary database on the same node (i.e. primary on NodeA, logical and physical database of primary on NodeB)?
    Will there be any conflicts with data guard broker with this configuration or any problems I may encounter?

    From a technical point of view this is possible. Your standby node should be powerful enough to handle 2 instances. For even higher availability 3 dedicated nodes would be better. When Node B is down, both physical and logical standby are also down.
    Werner

  • Cisco ISE - line posture node and switch connection.

    I am studying how Cisco ISE - Inline Posture Node working under the Bridge Mode. I learned that I need to configure the vlan mapping between the untrusted and trusted interfaces of IPN device ( http://www.cisco.com/en/US/docs/security/ise/1.1/user_guide/ise_ipep_deploy.html - Figure 10-6).
    Does that mean I can setup a 802.1Q trunk link between the switch port and trusted/untrusted interface on IPN? Is there any vlan mapping entry limitation? Thanks.

    Please review the below link which might also be  helpful:
    http://www.cisco.com/en/US/products/ps11640/products_configuration_example09186a0080bea904.shtml

  • ISE | Inline VPN deployment Issue

    Hi,
    I have ASA which I use for internet access and VPN gateway. I am trying to deploy ISE inline VPN node, but i found that the users traffic (from inside to internet) denied by the Inline node (users return traffic from untrusted port to trusted is blocked).... It is only permitted if i add the real IP subnet , i need to access , in the filter tab.
    This is not practical because i can not exclude all internet addresses.
    My questions are:
    1) Is Inline VPN designed to be used only with dedicated VPN GWs?
    2)Is there any workaround for this?
    Thanks for any support.

    The ASA code you need is 9.2.1 or later.  This allows the ASA to perform CoA, thus negating the need for the Inline Posture Node.
    In which mode is the IPN working?  Bridged or Routed?
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

  • Forcing a JTree to only accept one type of node?

    So I have a JTree and I want to make sure that all of its nodes are of the same, specific type (that type being a custom extension of DefaultMutableTreeNode).
    The way to do this that initially crosses my mind is to extend JTree and override the add method and constructor to only accept nodes of this type (and just throw an exception if given a node if a different type). Then I realized that if someone connected up a bunch of some other kind of node but rooted it with the custom node, the custom JTree would accept it. Then I thought I'd probably have to override my node's add method so that you can't add nodes of other types to it either. This seems like a lot of work that I'd like to avoid if possible.
    Does anyone see a more straightforward way of doing this?

    Don't subclass JTree. Subclass DefaultTreeModel to only accept your kind of node, or probably better still, just write your own TreeModel. Making the modifications to TreeNode seems odd to me.

  • ISE inline posture limitation.

    Hi all,
    Can any one help me in configuration of ISE in inline posture mode. and What are the limitation of this mode.

    The following are known limitations for Inline Posture in Cisco ISE, Release 1.0.
    • Inline Posture is not supported in a virtual environment, such as VMware.
    • Backup and restore is not available for Inline Posture nodes in Cisco ISE, Release 1.0.
    • The Simple Network Management Protocol (SNMP) Agent is not supported by Inline Posture.
    • The Cisco Discovery Protocol (CDP) is not supported by Inline Posture.
    For more information over configuration and others you can see the attached PDF    

  • Ise inline Posture

    ..

    Understanding the Role of Inline Posture
    An Inline Posture node is a gatekeeper that enforces access policies and handles change of authorization (CoA) requests. An Inline Posture node is positioned behind the network access devices on your network that are unable to accommodate CoA, such as wireless LAN controllers (WLC) and virtual private network (VPN) devices.
    After the initial authentication of a client (using EAP/802.1x and RADIUS), the client must still go through posture assessment. The posture assessment process determines whether the client should be restricted, denied, or allowed full access to the network. When a client accesses the network through a WLC or VPN device, Inline Posture is responsible for the policy enforcement and CoA that these devices are unable to accommodate.
    Inline Posture Policy Enforcement
    Inline Posture uses RADIUS proxy and URL redirect capabilities in the control plane to manage data plane traffic for endpoints. As a RADIUS proxy, Inline Posture is able to tap into RADIUS sessions between network access devices (NADs) and RADIUS servers. NADs can open full gate to client traffic. However, Inline Posture opens only enough to allow limited traffic from clients. The restricted bandwidth allows clients the ability to have an agent provisioned, have posture assessed, and have remediation done. This restriction is accomplished by downloading and installing DACLs that are tailored for specific client flow.
    Upon full compliance, a CoA is sent to the Inline Posture node by the Policy Service ISE node, and full gate is opened by the Inline Posture node for the compliant client endpoint. The RADIUS proxy downloads the full-access DACL, installs it, and associates the client IP address to it. The installed DACL can be common for a number of user groups, so that duplicate downloads are not necessary as long as the DACL content does not change at the Cisco ISE servers.
    The Inline Posture policy enforcement flow illustrated in the figure above follows these steps:
    1. The endpoint initiates a .1X connection to the wireless network.
    2. The WLC, which is a NAD, sends a RADIUS Access-Request message to the RADIUS server (usually the Policy Service ISE node).
    3. Inline Posture node, acting as a RADIUS proxy, relays the Access-Request message to the RADIUS server.
    4. After authenticating the user, the RADIUS server sends a RADIUS Access-Accept message back to the Inline Posture node.
    There can be a number of RADIUS transactions between the Endpoint, WLC, Inline Posture node, and the Cisco ISE RADIUS server before the Access-Accept message is sent. The process described in this example has been simplified for the sake of brevity.
    5. The Inline Posture node passes the Access-Accept message to the WLC, which in turn authorizes the endpoint access, in accordance with the profile that accompanied the message.
    6. The proxied Access-Accept message triggers Inline Posture to send an Authorization-Only request to the Policy Service ISE node, to retrieve the profile for the session.
    7. The Policy Service ISE node returns an Access-Accept message, along with the necessary Inline Posture profile.
    8. If the access control list (ACL) that is defined in the profile is not already available on the Inline Posture node, Inline Posture downloads it from the Policy Service ISE node using a RADIUS request (to the Cisco ISE RADIUS server).
    9. The Cisco ISE RADIUS server sends the complete ACL in response. It is then installed in the Inline Posture data plane so that endpoint traffic passes through it.
    There may be a number of transactions before the complete ACL is downloaded, especially if the ACL is too large for one transaction.
    10. As the endpoint traffic arrives at the WLC, the WLC sends out a RADIUS Accounting-Start message for the session to the Inline Posture node.
    The actual data traffic from the endpoint may arrive at the Inline Posture untrusted side before the Accounting-Start message is received by the Inline Posture node. Upon receiving the RADIUS Accounting-Start message, the Inline Posture node learns the IP address of the endpoint involved in the session and associates the endpoint with the ACL (downloaded and installed earlier in the session). The initial profile for this client endpoint could be restrictive, to posture the client before being given full access.
    11. Assuming the restrictive ACL allows only access to Cisco ISE servers, the endpoint is only allowed actions such as agent downloading and posture assessment over the data plane.
    12. If the client endpoint is posture compliant (as part of the restricted communication with Cisco ISE services earlier), the Policy Service ISE node initiates a RADIUS Change of Authorization (CoA) with the new profile. Hence, a new ACL is applied at the Inline Posture node for the session. The new ACL is installed immediately and applied to the endpoint traffic.
    13. The endpoint is then capable of full access to the enterprise network, as a result of the new profile that was applied to Inline Posture.
    A RADIUS stop message for a given session that is issued from the WLC, resets the corresponding endpoint access at the Inline Posture node.
    Best regards,
    Mantej Mangat

  • Inline c

    I am trying to make a wireless sensor with arm microcontroller which support labview arm module. but arm module seems to be controlled by labview timing loop. It is not sufficient speed to meet 10000 samples per second. so i want to use inline c function to speed up data aquisition speed but very complicate. if someone has same experience of this problem, please answer me or tell me any examples.

    Hi,
    What kind of help are you looking for? Using an inline C node is exactly like writing C code. We provide this functionality so that you can program features on the board that we havent built support for.You can also try contacting your local NI support. They should be a able to help you create examples.
    Thank you,
    Jaidev  
    National Instruments
    LabVIEW Embedded Product Support Engineer

  • Debugging Node Manager

    Where does the node manager keep its log files? I am trying to start a managed server
    on a remote machine - but it fails. I cannot find anything in any of the log files
    that helps me work out what the problem is. (I have it running as a service - I guess
    I could run it from the console - but this wont help me in a production environment)
    Are there different log levels with the Node Manager (or, better still, some way
    to turn debugging/verbose on)?
    (I have looked in D:\bea\weblogic700\common\nodemanager\* for the log files - there
    are log files but nothing useful in them (no error messages - nothing))
    Cheers,
    Nick

    Yes.
    Try "java weblogic.nodemanager.NodeManager help"
    This will print nodemanager's help usage.
    I understand that you want to run NM as an NT service.
    But are you able to start managed servers from admin console?
    This may help to troubleshoot the problem.
    Kumar
    Nick Minutello wrote:
    Cheers. Thanks.
    Are all the debug options for Weblogic documented somewhere?
    -Nick
    prasen <[email protected]> wrote:
    Most common problem in NodeMgr is SSLHandShake failure. Here is a list
    of command which
    I use:
    -Dweblogic.nodemanager.debugLevel=90
    -Dssl.debug=true
    -Dweblogic.StdoutDebugEnabled=true
    -Dweblogic.nodemanager.javaHome=c:\jdk1.3.1_02
    -Dweblogic.security.SSL.trustedCAKeyStore=C:\weblogicdev\src_131sj\server\lib\cacerts
    Nick Minutello wrote:
    Where does the node manager keep its log files? I am trying to start amanaged server
    on a remote machine - but it fails. I cannot find anything in any of thelog files
    that helps me work out what the problem is. (I have it running as a service- I guess
    I could run it from the console - but this wont help me in a productionenvironment)
    Are there different log levels with the Node Manager (or, better still,some way
    to turn debugging/verbose on)?
    (I have looked in D:\bea\weblogic700\common\nodemanager\* for the logfiles - there
    are log files but nothing useful in them (no error messages - nothing))
    Cheers,
    Nick

Maybe you are looking for