RTSI implemention between FPGA and PXI controller

I have a need to be able to send and receive data from a r-series modules. I note these have an RTSI bus (PXI form). I am looking to implement this bus so I can pass results to a PXI controller and send new settings (info for PWM), can someone point me at an article as I have been looking for a while now to no avail.
Many thanks
Please remember to accept any solutions and give kudos, Thanks
LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7

To pass data from an FPGA depending on the data type it is common to use a FIFO as R series cards tend to gather data faster than most devices can handle so the buffer is used so data isnt lost. If you could post some example code I would be happy to point you in the right direction.
Matthew Trott
Applications Engineer
National Instruments UK
www.ni.com/ask

Similar Messages

Communication between : AP and WLAN controller

Hi,
The communication between AP and WLAN Controller is ( Data and Control ) UDP.
Source port 1024 and destination port 12222 and 12223. Actually which device listen to which port or both should listen as control and data can be generated from both the devices.
How does the user ( wireless client) traffic is switched - if user traffic is a TCP traffic. It will be sent to WLANC and then WLANC forwards it to respective VLAN or default gateway ( depending upon the destination in the packet ).
Please explain / share the experience.
any link on cisco.com
Thanka in advance
Subodh

"the LWAPP Control and Data messages are encapsulated in UDP packets that are carried over the IP network. The only requirement is established IP connectivity between the access points and the WLC. The LWAPP tunnel uses the access point's IP address and the WLC's AP Manager interface IP address as endpoints. The AP Manager interface is explained in further detail in the
implementation section. On the access point side, both LWAPP Control and Data messages use an ephemeral port that is derived from a hash of the access point MAC address as the UDP port. On the WLC side, LWAPP Data messages always use UDP port 12222. On the WLC side, LWAPP Control messages always use UDP port 12223.
The mechanics and sequencing of Layer 3 LWAPP are similar to Layer 2 LWAPP except that the packets are carried in UDP packets instead of being encapsulated in Ethernet frames."
Taken from "Cisco 440X Series Wireless LAN Controllers Deployment Guide"

What are the differences between CompactRIO and PXI-RT?

Hi. We want to perform distributed data acquisition, specifically with (let's say) eigth IEPE accelerometers, wich are about (let's say) 80 meters away from the host PC. We think a good solution is to acquire locally (with PXI-RT or cRIO), maybe do some temporary storage, and then transmit the acquired data through ethernet to the host. This way, we can mantain a desktop PC on a safe place to perform centralized data processing and storage and avoid long accelerometer cable runs, subject to signal degradation.
As I mentioned, we thought on a basic PXI-RT system or a cRIO system, since little or no processing and storage is needed, while providing signal conditioning to the accelerometers. We thought about the next configurations:
1. PXI-RT: PXI-1002 chassis, PXI-8145 RT controller, PXI-4472 8 channel DSA. Total: $ 6585
2. cRIO: cRIO-9101 chassis, cRIO-9002 real-time controller, 2x cRIO-9233 4ch IEPE AI. Total: $ 5260
Prices are relatively close and none is absolutely cheaper than the other if we add accesories, change the number of channels or other characteristics.
We are new to PXI-RT and cRIO, so I would like to know what could be the main effective differences for my application and what do you think would be the best solution.
Thank you,
Daniel R.
Universidad de Concepcion

Hi Daniel,
I agree with John's comments on the difference between PXI-RT and cRIO. To add to this discussion, Compact RIO is an FPGA platform. So you can compile a VI and download it onto the cRIO's FPGA. The cRIO also has an RT portion, meaning that you can have a VI running on the FPGA and a VI running on the RT part and they can communicate with each other. I would recommend cRIO only if you need to take advantage of its FPGA functionality, which gives you extremely fast program execution with amazing loop cycle times. The ruggedness is also a plus. However, programming for LabVIEW FPGA is a bit different than programming for LabVIEW (or LV RT). FPGA programming is very low level and will require additional development time. This is why the direct comparison between PXI-RT and cRIO brings up more than just the price as a differentiator.
If you are looking for a compact platform like cRIO, I would recommend Compact FieldPoint. In ruggedness, it is quite close to the cRIO platform. Development-wise, its exactly like programming for the PXI-RT. This means that basically, any regular LabVIEW VI can be downloaded and run on it. So as you can see, its not a lateral step between PXI/Fieldpoing RT and cRIO. I would recommend that you read more about these platforms before proceeding. If you call us at NI, we can also help you decide a suitable platform for you.
cRIO: http://www.ni.com/compactrio/
FPGA: http://www.ni.com/fpga/
RT: http://www.ni.com/realtime/
Hope this information is helpful.
Anu Saha
Academic Product Marketing Engineer
National Instruments

Fpga: Communicating between fpga and third party program running on pc

I am using a C-Rio to control a planar robotic joystick. The goal is to use the joystick as a force feedback controller for a computer game running on a pc.
My program as is for now runs a program on the fpga to read the encoder values and run the pwm for the motors. An RT program reads those values and performs the control as well as it calculates the fwd and inverse kinematics of the robot.
What I would like to do now is to pass the x-y values of the joystick on a third program (computer game) that runs on a PC.Currently the game runs on LabVIEW but I would the system to be combatible with other programs written in different programming languages. I have been told that the best way of doing this is to setup a server. Is this the only/best way of doing this?
I would like to know what is the best way to communicate between a program running on a pc and a program running on the fpga for this type of application. What is the best way to pass along information from fpga to third party app running on pc and vice versa?
I am sorry if this has been asked before but I couldn't find a relevant thread. Thank you for reading this!
Ares

If you need every command to make it, then you should use TCP. I would recommend taking a look at the STM library that is floating around somewhere on the LabVIEW Tools Network.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Data Transfer methods between FPGA and RT

I have 10 values that I combined into a cluster that I want to send to the RT controller. The problem is if I just the read/write FPGA, I only get 1/10th of the data. I am assuming that it is the time taking to transfer from FPGA to RT. So I looked into DMA FIFO. When I use this, I do capture the data, but I notice jumps/shifts in the data. It's almost like the buffer fills up, and then dumps it at the last sec. To reduce this, I went from 10 values from the cluster to 2, and there were not shifts/jumps. The problem is I need all 10 values. So I'm wondering if I need to increase my DMA FIFO or if there is another meathod I need to use like Shared Varibles?
Thanks,
guilio

The one thing I still don't understand is what you mean by this "jump" in your data. Can you be a bit more specific about this? What I mean by jump. The elements coming from the FIFO in the RT controller will display on my array visual aid normally. Then you will see the data jump. Here is an example. I am bringing out 3 elements, X Y Z into an array. I'll read lets say 9 elements at a time. So my array, after I transform it into a 2D array for saving will look like this. [x y z;x y z;x y z]. At some points in time, the array will jump and look like this. [x y z;z x y ;z x y]. Then it will go back to how I expect it to look [z x y;x y z;x y z]. Right now, I am reading ~3000 elements. The elements remaining depends on what else is going on. If the visual aids are deleted, then elements remaining will never max out and thus, I won't get jumps. If I put visual aids in, then I get jumps because elements remaining maxes out. This leads me to believe that the FIFO is filling up and since it can't release all the information fast enough, then it just dumps it and fill it up again. The weird thing about it, It doesn't happen in a pattern (every 3000 elements). I tried putting them in seperate loops, it still slows things down. I tried queing/dequeing, still slows it down. I need to be able to read all elements fo all 3 DMA transfers at once. Maybe it will help us locate the problem. Otherwise, your DMA FIFO looks OK. Can you verify the number of times your data is written to the FIFO from the FPGA? When I put a clock in to measure loops speed, it was showing 8-9us. I can't have this no more than 10us or I will missed data. I would like to see a definite count of this. Then on the RT side, what does the "Elements Remaining" output look like? As before, elements remaining depends on what else is going on. If I just have the DMA FIFO's, then I can adjust the read elements number so all three don't max out, but as soon as I put something else in, it will max out. Since this is a FIFO we should be able to keep very close track of elements in and out.
Let me know if you need more info. I know about the FXP point transfer, unfotunately, not all my FXP elements are the same data type.
Thanks,
guilio

Difference in client tables between WLC and AP controller d0

Hello gang,
Anyone know whether its normal to have an APs' d0/d1 controller output show clients that don't appear on the WLC's "sh client <AP>" output?
Here's an example - 10 clients visible from a "sh client " on the controller, but 15 clients visible on AP4s "sh controller d0" debug.
Granted the User Idle Timeout has been bumped up to 7200 seconds, but shouldn't the AP's d0/1 client table get updated if/when a client roams to another AP nonetheless? Wouldn't this otherwise cause confusion? Is the Split-MAC Split-brained?
Thanks for your input,
--Bruce Johnson
(mcores2wlc1) >show client ap 802.11b mell9s1ap4
MAC Address AP Id Status WLAN Id Authenticated
00:40:9d:31:b0:79 130 Associated 6 Yes
00:40:9d:34:1f:04 130 Associated 6 Yes
00:40:9d:33:ee:04 130 Associated 6 Yes
00:40:9d:2b:d1:6a 130 Associated 6 Yes
00:40:9d:31:23:a3 130 Associated 6 Yes
00:40:9d:33:e9:28 130 Associated 6 Yes
00:40:9d:31:27:a5 130 Associated 6 Yes
00:40:9d:33:eb:4b 130 Associated 6 Yes
00:40:9d:31:22:1d 130 Associated 6 Yes
00:40:9d:33:ee:cb 130 Associated 6 Yes
(mcores2wlc1) >debug ap command "sh cont d0" mell9s1ap4
(mcores2wlc1) >Thu Feb 26 18:54:10 2009: mell9s1ap4:
Thu Feb 26 18:54:10 2009: mell9s1ap4: ---Clients AID VLAN Status Age Tx Mode Enc Key Rate
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.eaec 198 6 0000 0800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d30.efd1 197 6 0000 0800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.bc74 195 6 0000 2800001FF 7165/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.27a5 193 6 0000 0800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.eecb 192 6 0000 2800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.221d 190 6 0000 0800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.eb4b 186 6 0000 0800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0016.6faf.9d64 185 3 0000 0C00000FF 7186/7200 0-0 0191 200 0-10 10FC0000 06C
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.e928 177 6 0000 2800001FF 5818/7200 0-0 10111 200 0-10 10000000 016
=>Thu Feb 26 18:54:10 2009: mell9s1ap4: 0016.6faf.9db8 176 3 0000 0C00000FF 7140/7200 0-0 0191 200 0-10 10FC0000 06C
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.23a3 174 6 0000 2800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d2b.d16a 165 6 0000 1800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d33.ee04 163 6 0000 0800000FF 7194/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d34.1f04 151 6 0000 1800000FF 7195/7200 0-0 10111 200 0-10 10000000 016
Thu Feb 26 18:54:10 2009: mell9s1ap4: 0040.9d31.b079 147 6 0000 2800000FF 7194/7200 0-0 10111 200 0-10 10000000 016

hi Leo,
I tested this out, but i guess its not working as i thought it would work. I configured the backup primary controller IP and name in the global configuration of the Wireless tab of the WLC and left the AP high availability blank with no settings. I joined the AP to the WLC and show capwap client ha output on the AP shows the backup primary controller name. but if i shut down the primary controller, the AP does not join the back, it just tries to get WLC ip by renewing DHCP forever and stuck in that...   below are the outputs.. any idea why its like this ? I thot if there is no HA configured at the AP level, the global config on the controller level should take effect ?
LWAP3-1042#sh cap cli ha
fastHeartbeatTmr(sec)   7 (enabled)
primaryDiscoverTmr(sec) 30
primaryBackupWlcIp      0xA0A700A
primaryBackupWlcName    WLC2-4402-50
secondaryBackupWlcIp    0x0
secondaryBackupWlcName
DHCP renew try count    0
Fwd traffic stats get   0
Fast Heartbeat sent     0
Discovery attempt      0
Backup WLC array:
LWAP3-1042#
*Apr 30 20:36:21.324: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
*Apr 30 20:36:31.829: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.114.49, mask 255.255.255.0, hostname LWAP3-1042
*Apr 30 20:37:17.832: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
*Apr 30 20:37:28.337: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.114.50, mask 255.255.255.0, hostname LWAP3-1042
*Apr 30 20:38:14.338: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
Not in Bound state.
*Apr 30 20:38:24.842: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.114.51, mask 255.255.255.0, hostname LWAP3-1042
regards
Joe

Difference between custom controller and component controller

Hi All,
I am a beginner in CRM SAP .
Please can anyone tell me whats the difference between custom controller and component controller with some scenario.
I am totally baffled.
Thanks in advance.
Regards
Shilpi

Hi Shilpi,
The main difference between custom and component controller is the role which they play during data transfer.
a) Custom controller is used for data transfer across two views within a component. For that you need to bind view context nodes to custom controller either through wizard or manually by adding the code in CTXT class create_contextnode method:
initial setting for depandant model node
    coll_wrapper =
      BTADMINH->get_collection_wrapper( ).
    TRY.
        entity ?= coll_wrapper->get_current( ).
      CATCH cx_sy_move_cast_error.
    ENDTRY.
    IF entity IS BOUND.
      BTOpportH->on_new_focus(
                   focus_bo = entity ).
    ENDIF.
b)Component controller is used for data transfer across two views in two different components. For this, we need to define the component usage first and then bind the context nodes in the method-WD_USAGE_INITIALIZE of the Component Controller impl class.
    WHEN 'ComponentUsageName'.
      iv_usage->bind_context_node(
                  iv_controller_type = cl_bsp_wd_controller=>co_type_custom
                  iv_target_node_name = 'ContextNodeName' "#EC NOTEXT
                  iv_node_2_bind      = 'ContextNodeName' ). "#EC NOTEXT
Hope this clears some of your doubts!
Thanks and Regards,
Rohit
P.S-This is valid for CRM 2007.Raghu is also right because Interaction Center is made up of different different components combined together.You have put your question in wrong forum.

What is the difference between Custom controller and context controller?

Hi Gurus,
What is the difference between Custom and context controller?
In which occasion we should prefer to use Custom Controller?
Thanks in Advance,
Dharani

You mean difference between custom controller and component controller???
if yes...
its been discussed many times.... just go through these threads, you will be clear
custom controller vs component controller
Component Controller and Custom comtroller
[ why we need Custom controllers in Model Applications |why we need Custom controllers in Model Applications;
[CONTROLLER AND CONTEXT|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/944ea9e5-0601-0010-65b3-b49a56eb6385]
Pradeep
Edited by: pradeep bondla on Jul 22, 2008 12:42 PM

Best Practice - Outer Join between Fact and Dim table

Hi Gurus,
Need some advice on the below scenario
I have an OOTB subject area and we have around 50-60 reports based on it. The related subject area Fact and Dim1 table are having inner join.
Now I have a scenario for one report where outer join has to be implemented between Fact and Dim1. Here I am against changing the OOTB subject area join as the outer join will impact the performance of other 50-60 reports.
Can anyone provide any inputs on what is the best way to handle this scenario?
Thanks

Ok. I tried this:
Driving table : Fact, Left outer join -- didnt work.
Driving table: Dimension D left outer join -- didnt work either
In either the case, I see physical query as D left outer Join on Fact F. and omitting the rows.
And then I tried this -
Driving table: Fact, RIght outer join.
Now, this is giving me error:
Sybase][ODBC Driver]Internal Error. [nQSError: 16001] ODBC error state: 00000 code: 30128 message: [Sybase][ODBC Driver]Data overflow. Increase specified column size or buffer size. [nQSError: 16011] ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement. (HY000)
I checked all columns, everything matched with database table type and size.
I am pulling Fact.account number, Dimension.account name, Fact.Measures. I am seeing this error each time I pull Fact.Account number.

Single Sign On between BPM and Siebel

Hi,
How are you? has somebody involved in a proyect where SSO was implemented between BPM and Siebel? is there an Oracle Standard way of achieving this?
thanx in Advanced and Kind Regards!
Gerardo J

Hi Harsh,
I heard about SPNego a mechanism you use for making single Sign On Using Kerberos Authentication with Web clients...
check this link.. It may give you some inputs...
http://help.sap.com/saphelp_nw04/helpdata/en/43/4bd58c6c5e5f34e10000000a1553f6/content.htm
Thanks,
Sudhakar.

Difference between interface view and interface controller

Hi,
What is the difference between interface controller and interface view?
When we will use interface controller and when we will use interface view?
How do we create an interface view?
How do we attach this interface view to a view in another component
Regards
MQ

Hi
Interface View Controllers
A) Implement event handlers which are called when ..
-starting (start-up plugs) Web Dypro applications
-a component is reached via navigation (inbound plugs)
B) Allow fireing outbound plugs (navigation)
C) Allow firing exit plug
D) Have no own context, public methods or events
Interface Controller of a Component
The interface controller of a Web Dynpro component contains all context nodes, events and methods of the component controller to which you assigned the Interface addition in the Controller Editor. These parts can be displayed in the interface controller view, although you cannot edit them here.
Interface Controller of a Component Interface
A Web Dynpro component interface can be created independently and defined so that it can be implemented later in any components (see working with Web Dynpro Component Interfaces in the Programming Manual of this documentation). That is why in this case you can define the context nodes, methods and events you require in the interface controller view. The relevant implementation then takes place in the component controller of the implementing component.
Check this links and work on it.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#13 [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#12 [original link is broken]
Interface view and interface controller
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f727d100-0801-0010-4cbd-b0ad5c161945
Difference between custom controller and interface component
Thanks and Regards,
Tulasi Palnati

Swapping hard drives between PXI-8115 and PXI-8105 won't boot up

I have a test system running Windows XP on PXI-8105. I've upgraded the entire test system for another project and need to upgrade my existing systems; the upgrade runs on Windows 7 and PXI-8115. I have new hard drives with Windows 7 and the new test software which were loaded/configured/tested on a PXI-8115, but I need to retrofit the PXI-8105 with them. This doesn't work. Windows begins to boot but fails and tries over and over again. In an effort to take the PXI-8105 off-line to troubleshoot, I replaced it with one of the PXI-8115 and the old (WinXP) drive. This didn't boot up, either.
Here's a summary of my situation:
An old system has PXI-8105 running WinXP
A new system has PXI -8115 running Win7
A hard drive (with Win7) from the PXI-8115 won't boot on the PXI-8105
A hard drive (with WinXP) from the PXI-8105 won't boot on the PXI-8115
What is different between the two PXI controllers that keeps me from swapping hard drives?
Jim
You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
Solved!
Go to Solution.

A couple thoughts:
1. Windows 7 probably works fine on a PXI-8105. Although NI never officially supported or shipped that configuration, I suspect that the default Windows 7 installation contains enough of the driver support needed to boot up.
2. In general, Windows is not very tolerant of swapping hard drives between completely different systems, especially with Windows XP and prior. Consider whether just installing fresh and copying over what you need is faster than trying to do this, but if you must, I would suspect that Windows 7 would be more tolerant of the swap.
3. As a debugging step, try pressing 'F8' during the boot process to launch the Windows boot menu and try safe mode or some of the other options. More information here.
4. If all else fails, Google is your friend here as there's nothing particularly specific about this being an NI product that you need to know when attempting this operation. Any information you find online about swapping hard drives between PCs should be relevant to your situation. Searching for 'swap hard drive to new computer windows 7' gave some useful hits on the first page. Beyond that, you can also look into using the 'sysprep' utility to try and clean the system and prepare for swapping to a new PC.

Remote startup and shutdown of of PXIe controller running Labview RT (WoL)

I would like to be able to remotely start up and shut down a PXIe-8133/PXIe-8130 controller remotely over the LAN.
I can see that the hardware specs for the PXIe-8133 supports wake on lan (WoL), but I'm not sure about the 8130 (although it seems to respond to the network when asleep).
I have seen the guide for configuring WoL under Windows, but I do not have Windows installed on these controllers, so how is WoL configured if I only have Labview RT 2011?
And the 2nd part of my question is whether Labview RT supports a way to programatically shut down the controller? I'd like the controller to shut down when the startup application terminates. I've found the RT Restart Target VI, but not one for shutting down.

Hey there.
Power management on a PXI controller isn't well supported (or supported at all, really). WoL is only supported via Windows, LabVIEW Real-Time does not support the WoL feature. Shutting the controller down is only supported in LabVIEW 2012 and newer via the power button on an express chassis; LabVIEW Real-Time cannot programmatically kill the power on the controller, but it can put itself into a safe state (i.e. shut down) when the power button tells it that, "it has 13 seconds to shut down or else."
Power Management is on our roadmap, and is being considered for future versions of LabVIEW Real-Time.
-Danny

Diff between Component controller,Custome controller and View controller

hi,
Can any body tell me the following details,
1.difference between the Component controller,Custome controller and View controller in WD-ABAP.?
2.what is Lead Selection?
Regards,
Ravi

Hi Ravi.
The component controller is visbile to all views in a component. So all context nodes and methods you create here can be accessed from all views in the component. This way you can share data between the views by mapping context nodes or thru method calls. You can also mark methods and nodes as interface so that they are acessable from other components that define component usages to this cmponent.
Custom controller is quiet similar to the component controller. You can define it if you want to group some views with a custom controller for a certain functionality.
If you want to access a custom controller in a view you have to define the usage first on the properties tab of the view.
A view controller is only visible in the view itself. So all methods or context nodes you define here are only accesable by the current view.
The lead selection is in most cases the current selected element in a context node. The lead selection is used by many UI elements to determine which element has to be shown (e.g drop down).
If you have a table with single selection the current selected table row is the lead selection element of the bound context node.
SO you can get the lead selection element easily in any mthod by calling context_node->get_element( ).
Hope this clears your questions.
Cheers,
Sascha

Difference between AP Operational Status and Registered Controller

When reviewing the AP Details page in Prime there are two fields I'm not sure what they mean specifically:
1) Operational Status - Registered
2) Registered Controller - Not Associated
Any clarity or document references would be greatly appreciated.

This is in CPI viewing the AP Details tab.
The only valid values for Operational Status are Registered/Not Registered.
The only valid values for Registered Controller are Associated/Not Associated
The IP address is not a valid input.
It is still unclear to me what the specific and fuctional differences and impacts are between Operational Status and
Registered Controller? How do the values of each impact the client device?
Thank You.

RTSI implemention between FPGA and PXI controller

Similar Messages

Maybe you are looking for