Detecting C Series Module Fault through I/O Variable Node

Hello LabVIEW Users.
My name is Eisuke Ono, An Application Engineer at NI Japan.
One of our customer is requesting a function.
The function is to retrieve information of module fault from C Series I/O variable Node (Scan Interface).
I know that we can get the information of module fault through FPGA I/O node, but not through Scan Inteface mode.
The customer's application is embedded condition monitoring system. It runs 24/7.
So it is very convenient if he get information of module fault C Series I/O variable Node Error Output.
I agree his opinion.
What do you think?
Bestr regards.
Eisuke Ono

RT
FPGA
The goal is to detect Module Fault (Other than Communication Error) through IOV or FPGA node.
If it is already implemented, I would delete this thread.
Best!

Similar Messages

Can I detect if a module is present in CRIO FPGA?

I have a cRIO-9073 controller chassis with 8 NI 9237 modules. I plan to use FPGA reads - not the scan engine. Can I detect whether a module is present or not within my FPGA VI? If not, is there a way to do this within the RT Host VI? (This is my first cRIO project so I'm still a bit green). I can foresee my client needing to replace a module sometime in the future and still needing to operate the system with the remaining modules - so the system must be robust and adaptible to fault conditions.
- Thanks in advance
- Tore
Solved!
Go to Solution.

I switched to the Find Hardware VI and it doesn't error, but what I need is network devices. I have expansion chassis on the network that I need to confirm are connected. The Find Hardware VI only lists off local devices. I asked about the error over at this topic here:
https://forums.ni.com/t5/LabVIEW/LV-RT-System-Config-Find-Systems-vi-Error-quot-2147220620-quot/m-p/...
Thanks,
James
LabVIEW Professional 2014

Can I create a task that includes 2 C series modules?

I am trying to create a single task that includes 2 NI-9425 C series modules but when I wire the physical channel constant "Mod3/port0, Mod4/port0" into the DAQmx Create Virtual Channel.vi I receive error -200086 which states physical channel range syntax in the input string is invalid because multiple devices were listed in the string. It is my understanding from LabView help that multidevice tasks are allowed. Also according to this KB article http://digital.ni.com/public.nsf/allkb/CF85114C6025C84C862571C000722DDA multi-device tasks are supported for S Series devices, C Series, and DSA devices, and according to this KB article http://digital.ni.com/public.nsf/websearch/78E44565FD87E7D686257108007F94F8?OpenDocument I have formatted my physical channel constant correctly.
Can someone please explain why I am getting this error when all indications are that this should be a simple thing to do?
My C series modules are in slots 3 and 4 in a cDAQ-9188 chassis, I am currently running LabView 8.5.1, with Windows XP
Thank you,
Eric
Solved!
Go to Solution.

Hi Eric,
I'm afraid that you can't configure hardware timing with the NI 9425 in CompactDAQ. The NI 9425 data sheet explains: "The NI 9425 is a static digital module, so you can use it to perform software-timed or static operations only when installed in an NI CompactDAQ chassis."
For AI, AO, and counters, daisy chaining multiple calls to DAQmx Create Channel is equivalent to specifying a list of physical channels, but for DIO it's different. A single DIO virtual channel can contain multiple physical channels (lines). It would be completely reasonable to assume that specifying a list of lines with "one channel for all lines" would cause DAQmx to put all of the lines in a single virtual channel, but due to how it's implemented in the DAQmx framework, this is not possible when the lines are on multiple devices. It would also be reasonable to assume that if DAQmx couldn't put all of the lines in a single virtual channel, then it would create one virtual channel per device, but that's also not how it's implemented--it returns the error that you received.
Instead, here are two approaches to putting all 64 lines in one task. Either one should work.
Approach A: Create a single task, containing two virtual channels (MyChan0 and MyChan1). MyChan0 contains cDAQ1Mod3/port0/line0:31 and MyChan1 contains cDAQ1Mod4/port0/line0:31. The Digital 2D Bool NChan 1Samp read VI returns a 2x32 array of Booleans. To flatten this into a 1D 64-element array, you need to use Reshape Array or some other method.
The DAQmx Task >> Channels property is there to show that there are two virtual channels named MyChan0 and MyChan1. Also, I used a for-loop to show that you don't have to hardcode multiple calls to DAQmx Create Channel. The "one channel for all lines" constant is redundant because that is the default.
Approach B: Create a single task, containing 64 virtual channels (MyChan0 through MyChan63). This uses the "one channel for each line" constant, which is not the default. MyChan0 contains cDAQ1Mod3/port0/line0, MyChan1 contains cDAQ1Mod3/port0/line1, etc. The Digital 1D Bool NChan 1Samp read VI returns a 1D 64-element array of Booleans. If you used the Digital 2D Bool NChan 1Samp VI instead, you would get a 64x1 array because there are 64 virtual channels containing 1 line each.
Brad
Brad Keryan
NI R&D

Third party system call function module/BAPI through RFC to update Z table

Dear Friends,
We have a third party system which directly inserts a Z table in SAP through its programming, which is an auditing issue.
We want the third party system should call function module/BAPI through RFC so that the Z table gets updated.
waiting for inputs..
Thanks,
Kumar

if third party system is capable of making Remote Function call, then writing a Function module & making it remote enable is not difficult task in ABAP.
You may have to prepare specifications first to decide if third party system is going to Read, insert, update, delete records from Zee table.

Why do I keep getting error -65581 when trying to use a cRIO 9024 and c series modules

I am simply trying to send out a digital high on DIO0 of a 9401 c series module and I get the following error every time.
Error -65581 occurred at Shared Variable in Send True Value Out.vi
Possible reason(s):
CompactRIO: (Hex 0xFFFEFFD3) The FPGA personality currently running on the CompactRIO chassis does not support the RIO Scan Interface in this slot.
This error or warning occurred while writing the following Shared Variable:
\\NRL-CMG-cRIO\NI 9401-1\DIO0
\\170.126.209.52\NI 9401-1\DIO0
Any help would be greatly appreciated.
Nate
Solved!
Go to Solution.

NMAYO,
In your project view can you right click on the chassis in the cRIO and make sure that it is set for Scan Mode and not FPGA mode? Also, In the measurement and automation explorer you can check the cRIO and verify that it has Scan Engine Support installed on it. The tutorial below shows how to reformat a cRIO and install software on it, the later steps on software will allow you to check your cRIO.
Reformatting a CompactRIO Real-Time Embedded Controller
Ben Sisney
FlexRIO V&V Engineer
National Instruments

Which c-series modules are compatible with Scan Mode?

OK, so I just wasted 4 hours.
I started a new Project with a need to use a 9220 analogue input card on a cRIO 9030, but immediately became stuck when I was unable to add the module using the right click Add New C-Series Module wizard to the 9030 chassis.
My first (and only) assumption was that this was a new card and I needed the latest Device Drivers. So I installed those.
When that failed I upgraded my LV2014 to LV2014 SP1, and also upgraded the Real-Time and FPGA modules too.
4 hours later, when that failed, I realised that maybe this isn't a card compatible with Scan Mode so began searching ni.com for information. I've searched a whole raft of terms and I just cannot find information on which modules are supported by Scan Mode (which is presumably nearly all of them). I know it exists somewhere because I one referred to it when I had an RS485 module that was only compatible in FPGA mode, about four years ago.
So:
1. Is there an easy way to determine if a C-Series module is compatible with Scan Mode? I still don't know!
2. Can we please have Scan Mode compatibility shown in the Add C-Seris Module Wizard. When attempting to add a module to a cRIO chassis, the wizard can hint to us that a particular module is not compatible. By not showing the 9220 in the drop down list I was led to believe the module was not a known device (and hence I attempted to upgrade my drivers). It would be better if the module was listed but disabled and not selectable, with some informational text to explain why. It's a fair assumption that a module will be compatible, so we don't expect it to not be listed when we attempt to add it. In fact, the possibility that some modules aren't compatible can evade your consciousness temporarily and make you do stupid things (like upgrade your installation!).
3. Can we please have Scan Mode compatability information put on each module's description page. That would have made this whole process much quicker.
Thoric (CLA, CLED, CTD and LabVIEW Champion)

Well, I definitely agree that finding info about RSI module support is not as easy as it should be. Since I know where to look, I will refer you to this document, which I found linked from this page.
That's the best document I know of on the topic.
Cheers!
TJ G

CompactRIO, CVI, and C series modules

Being used to LabVIEW, not sure how to interface to the C-series modules on my cRIO using CVI. The project I'm on needs to use CVI, and I have no idea how to interface to my cards -- e.g. writing to my DIO card or reading from an AI channel, etc.
In LV, it was easy and each I/O channel was simply a variable I could drop over to my block diagram and either read to write from/to. Any pointers in the right direction for this? I have the CVI real-time module and I know C, but never messed with CVI much.. I've searched and searched, but maybe I'm not searching right or something :/
How can I read from my NI-9221 card on, say, channel 0 and get a double back representing the voltage that's on that line?? That's the kind of stuff I'm looking for... in CVI?
Thanks.

Hi there,
LabWindows/CVi actually cannot be used to program cRIO. CVI uses Pharlap, while cRIO uses VxWorks. See CVI + RT FAQ and here's another more in-depth document regarding CVI in Real-Time.
Best,
Ryan C.
Applications Engineer
National Instruments

How do I detect a NI9862 module under FPGA

Hello,
I am trying to add NI9862 module under the FPGA target of NI9144 chassis. But I am unable to do so. Please see the attached image.
I read some of the earlier posts on the forum and I understand that some of these CAN modules need to be added in Offline mode, which is what I am trying to do. However, the list of C series modules doesn't have NI9862.
Help appreciated.
Thanks,
Rohan
Attachments:
2011sp1 ni9862 ni9144.png ‏343 KB

Hello Rohan,
I see the CAN module 9862 listed here as being incompatible in scan mode with the 9144 chassis. Is this the documentation you were referring to?
Andy C.
Applications Engineering
National Instruments

Change a c-series module

I have created a labview project and am using a RT Controller cRIO-9024 with cRIO-9118 Chassis. I assigned the NI9474 to 5 of the slots and the NI9425 to the remaining 3 slots. I now need to change the NI9474 to a NI9478. When I try to add a new C-Series module nothing happens? I have even tried removing the NI9474 from the project and I still can't add a new C-Series module. Can someone tell me what I am doing wrong? Thanks
Solved!
Go to Solution.

Do you only have 1 of each module in your chassis? If so, why have you added the modules to multiple slots? I don't think it will let you add a module if all 8 slots have had modules allocated to them - you will probably need to remove the NI9474 and then add the NI9478. If you rename the module/signals, it shouldn't affect your FPGA code.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

C-Series Module NI 9871, 4-Port, RS485/422 Serial Interface

I have a question regarding the C-Series Module NI 9871, 4-Port, RS485/422 Serial Interface.
I need to find out how it recovers the data from the link. I need to compare it with 8b/10b encoding.
Does anyone know what UARTs are used or how the data is recovered.
Thanks
John Lee

Hi John,
I have had a look into this and I cannot find any specific information on the Transciever or UART. However I have come across an example using the 9871 with processing on a cRIO FPGA.
To find this example open up Labview » go to Help » Find Examples » Search for 9871 and open up NI-987x Serial Loopback.lvproj.
Hopefully this should give you a good start. Once your serial data is passed onto the FPGA you can then decode the 8b/10b within the FPGA code.
Best Regards,
Ben B.
Applications Engineer
National Instruments UK & Ireland
"I've looked into the reset button, the science is impossible!"

A much more efficient way to add C Series modules manually

Scenario
Suppose that we want to start coding my Real-Time application, but the hardware hasn't arrived yet.
We can't Discover the chassis + modules, so we need to add modules manually.
Current editor
To add N modules, we need to launch this dialog N times:
Right-click on Chassis in the Project Explorer
Hover over "New"
Click "C Series Modules…"
Click "New target or device"
Click "C Series Module"
Click "OK"
Wait for LabVIEW to fetch module list (wait ~1 second)
Select Type (2 clicks)
Select Location (2 clicks)
Click "OK"
Go to #1 to add a new module
How tedious!
Proposed Editor
Wouldn't it be nice if we could set up all the modules in 1 dialog?
Features
Table auto-fills itself with modules already in the project
Number of rows is determined by the chassis model. No need to select Location
Ability to leave rows/slots empty
Editable Name field (with default name) appears upon selecting Type
Description appears upon selecting Type
Feel the difference
Adding N modules (using default names) requires...
Current dialog: 10N clicks, N hovers, waiting N seconds
Proposed dialog*: (6+2N) clicks, 1 hover, waiting 1 second
So, adding 8 modules requires...
Current dialog: 80 clicks, 8 hovers, waiting 8 seconds
Proposed dialog*: 22 clicks, 1 hover, waiting 1 second
*Assuming that steps 1-7 and 10 need to be performed once

Oh, and if this is implemented, please make sure that users can comfortably fit all text on their screen!

10Gig Copper SFP for Nexus F Series module (N7K-F248XP-25E)

Does Cisco have 10Gig Copper SFP which can be supported on Nexus platform in the F Series module (N7K-F248XP-25E)

Leo,
Thank you for the answer, you mentioned 10Gig Copper module in your reply (Part# N7K-F248XT-25E) but I already have Fiber Module (Part# N7K-F248XP-25E), I just need 2 10Gig copper ports for my storage and cant afford to buy a whole new Copper module. My question was if there is any 10Gig Copper SFP supported on F Series Fiber Module (Part# N7K-F248XP-25E), (not a twinax/DAC cable since my distance is longer and Twinax wont work)

Slot Detection of PXI Modules, More details

I read the knowledge base titled: Slot Detection of PXI Modules but have a few questions about it. How often to I have to do this? When I insert or remove a board from the PXI chassis? When I insert or remove an additional chassis in daisy chain? With Multiple chassis in Daisy chain. How do I know which device number is which card? ie if I have 2 of the same model of cards both in slot 5 but in different chassis. If I remove a card, am I guarranted that other cards device numbers will not change?

John,
The Knowledge Base (KB) "Slot Detection of PXI Modules" says that the PXI Initialization File (PXISYS.INI) file must be saved in the systems directory in order for the system to be able to identify the slot where a board is located. This is because every slot in a PCI Bus (a PXI system uses a PCI bus) has a PCI Device Number and PCI Bus Number associated with it. The PXISYS.INI file describes the architecture of the chassis and the controller, and has the appropiate PCI Device Number and PCI Bus Number for every slot. There is a unique PXISYS.INI file for every combination of PXI chassis and PXI controller.
How often to I have to do this? When I insert or remove a board from the PXI chassis?
Currently you do not need to edit the PXISYS.INI file. You can download the PXISYS.INI file from our website and use it as it is (see link in the KB you were reading). So you only need to save once the appropiate PXISYS.INI file to the Windows Systems directory, regardless of whether you change the PXI board in your system.
When I insert or remove an additional chassis in daisy chain? With Multiple chassis in Daisy chain?
If you are daysi-chaining chassis, keep in mind that the current PXI Standard DOES NOT support daysi-chaining. However, in previous PXI configurations, I have successfully edited a PXISYS.INI file so I can do Slot Identification in daysi-chained chassis (not in star configuration, though). The steps I followed are in the text file attach to this e-mail.
How do I know which device number is which card? ie if I have 2 of the same model of cards both in slot 5 but in different chassis. If I remove a card, am I guarranted that other cards device numbers will not change?
Finally, if you are using NI DAQ boards, NI-DAQ driver will assign a Device Number to the boards that correspond to the Slot Number, and the Slot Number is described in the PXISYS.INI file that you edited following the instructions in the text file attached below.
If your boards do not use the NI-DAQ driver, but support NI-VISA, you can use the PXI VISA Instrument Descriptor to find out the Slot they are installed in. See the KB "Programmatic Slot ID" linked below for more information. It has an Example Program linked to it too:
KnowledgeBase 2MDFG2WD - Programmatic PXI Slot Detection
Let me know if I can be of further assistance,
Claudia Lorente
Applications Engineer
National Instruments
http://www.ni.com/
Attachments:
PXISYS_for_Daysi_Chain.txt ‏4 KB

Exception fault: ReferenceError: Error #1065: Variable ::_fileSystemType is not defined. - ?

Hi! I'm stuck with debugging our AIR Application since it does crash very hard. After days of tracking down at least one point where the app crashes on AIR 3.5, 3.7 and AIR 3.8 beta (you see - I tried...).
AIR 3.5 finally reports this console output:
ScrollerTouch.onTargetMouseDown()-F true // A
ScrollerTouch.onTargetMouseDown()-I // B
targetV [object ScrollPane] // C
CRASH! // D
Exception fault: ReferenceError: Error #1065: Variable ::_fileSystemType is not defined.
          at global/trace()[int:49]
          at de.superclass.control::ScrollerTouch/onTargetMouseDown()[/path/to/.../ScrollerTouch.as:381]
          at de.superclass.control::ScrollerTouch/onTargetMouseDown()
The code snipped:
trace("ScrollerTouch.onTargetMouseDown()-F", _scrollHorizontal ); // A
switch ( _scrollPolicyVertical )
case ScrollPolicy.ON:
trace("ScrollerTouch.onTargetMouseDown()-G");
_scrollVertical = true;
                                        break;
case ScrollPolicy.OFF:
trace("ScrollerTouch.onTargetMouseDown()-H");
_scrollVertical = false;
                                        break;
case ScrollPolicy.AUTO:
trace("ScrollerTouch.onTargetMouseDown()-I"); // B
default:
                                                  trace( "targetV", targetV ); // C
                                                  try
                                                            trace( "targetV.height", targetV.height );
                                                  catch( e: Error )
                                                            trace( "CRASH!" ); // D
                                                  _scrollVertical = Boolean( targetV.height < targetV.contentHeight ); // line 381
trace( "targetV.xxx" );
                                                  trace( "targetV.contentHeight", targetV.contentHeight );
return;
So accessing targetV.height somehow crashes very hard (app quits) but I have no clue at all. Actually, this code worked for a long time...
So please, what is ::_fileSystemType ?

I changed the code again but the app keeps crashing. This is what XCode-Console says:
Jul 4 21:25:48 iRad-3 ReportCrash[1206] <Notice>: Formulating crash report for process APP_NAME[1191]
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: BKSendGSEvent ERROR sending event type 3001: (ipc/send) invalid destination port (0x10000003)
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: BKSendGSEvent ERROR sending event type 3001: (ipc/send) invalid destination port (0x10000003)
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: BKSendGSEvent ERROR sending event type 3001: (ipc/send) invalid destination port (0x10000003)
Jul 4 21:25:48 iRad-3 ReportCrash[1206] <Error>: libMobileGestalt copySystemVersionDictionaryValue: Could not lookup ReleaseType from system version dictionary
Jul 4 21:25:48 iRad-3 com.apple.launchd[1] (UIKitApplication:APP_NAME_SPACE[0x469][1191]) <Warning>: (UIKitApplication:APP_NAME_SPACE[0x469]) Job appears to have crashed: Segmentation fault: 11
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: Application 'UIKitApplication:APP_NAME_SPACE[0x469]' exited abnormally with signal 11: Segmentation fault: 11
Jul 4 21:25:48 iRad-3 ReportCrash[1206] <Notice>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/APP_NAME_2013-07-04-212547_iRad-3.plist using uid: 0 gid: 0, synthetic_euid: 501 egid: 0
Jul 4 21:25:55 iRad-3 kernel[0] <Debug>: launchd[1207] Builtin profile: container (sandbox)
Jul 4 21:25:55 iRad-3 kernel[0] <Debug>: launchd[1207] Container: /private/var/mobile/Applications/CDA04278-5D34-4609-BE71-D66FB16794C1 (sandbox)
Jul 4 21:25:56 iRad-3 kernel[0] <Debug>: launchd[1208] Builtin profile: PasteBoard (sandbox)
Jul 4 21:25:56 iRad-3 backboardd[26] <Warning>: CoreAnimation: updates deferred for too long
Jul 4 21:25:56 iRad-3 backboardd[26] <Warning>: CoreAnimation: timed out fence 2685b
And here's the Crash Log:
Jul 4 21:25:48 iRad-3 ReportCrash[1206] <Notice>: Formulating crash report for process APP_NAME[1191]
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: BKSendGSEvent ERROR sending event type 3001: (ipc/send) invalid destination port (0x10000003)
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: BKSendGSEvent ERROR sending event type 3001: (ipc/send) invalid destination port (0x10000003)
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: BKSendGSEvent ERROR sending event type 3001: (ipc/send) invalid destination port (0x10000003)
Jul 4 21:25:48 iRad-3 ReportCrash[1206] <Error>: libMobileGestalt copySystemVersionDictionaryValue: Could not lookup ReleaseType from system version dictionary
Jul 4 21:25:48 iRad-3 com.apple.launchd[1] (UIKitApplication:APP_NAME_SPACE[0x469][1191]) <Warning>: (UIKitApplication:APP_NAME_SPACE[0x469]) Job appears to have crashed: Segmentation fault: 11
Jul 4 21:25:48 iRad-3 backboardd[26] <Warning>: Application 'UIKitApplication:APP_NAME_SPACE[0x469]' exited abnormally with signal 11: Segmentation fault: 11
Jul 4 21:25:48 iRad-3 ReportCrash[1206] <Notice>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/APP_NAME_2013-07-04-212547_iRad-3.plist using uid: 0 gid: 0, synthetic_euid: 501 egid: 0
Jul 4 21:25:55 iRad-3 kernel[0] <Debug>: launchd[1207] Builtin profile: container (sandbox)
Jul 4 21:25:55 iRad-3 kernel[0] <Debug>: launchd[1207] Container: /private/var/mobile/Applications/CDA04278-5D34-4609-BE71-D66FB16794C1 (sandbox)
Jul 4 21:25:56 iRad-3 kernel[0] <Debug>: launchd[1208] Builtin profile: PasteBoard (sandbox)
Jul 4 21:25:56 iRad-3 backboardd[26] <Warning>: CoreAnimation: updates deferred for too long
Jul 4 21:25:56 iRad-3 backboardd[26] <Warning>: CoreAnimation: timed out fence 2685b
And here's the Crash Log:
Incident Identifier: 17615510-16A5-43B9-B8A5-2ED2C5A2EEBA
CrashReporter Key:   3f85661334bfff23c2d4128bc63674d30647c15b
Hardware Model:      iPad3,3
Process:         APP_NAME [1191]
Path:            /var/mobile/Applications/CDA04278-5D34-4609-BE71-D66FB16794C1/APP_NAME.app/APP_NAME
Identifier:      APP_NAME
Version:         ??? (???)
Code Type:       ARM (Native)
Parent Process: launchd [1]
Date/Time:       2013-07-04 21:25:47.935 +0200
OS Version:      iOS 6.1.3 (10B329)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x4095e008
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0   APP_NAME        0x008c71c8 0x1000 + 9200072
1   APP_NAME        0x005284ac 0x1000 + 5403820
2   APP_NAME        0x007b5edc 0x1000 + 8081116
3   APP_NAME        0x00002928 0x1000 + 6440
4   APP_NAME        0x0045f128 0x1000 + 4579624
5   APP_NAME        0x0045f5f8 0x1000 + 4580856
6   APP_NAME        0x0045eeb4 0x1000 + 4578996
7   APP_NAME        0x0045eab4 0x1000 + 4577972
8   APP_NAME        0x003d98d8 0x1000 + 4032728
9   APP_NAME        0x003c59c0 0x1000 + 3951040
10 APP_NAME        0x00443d24 0x1000 + 4468004
11 APP_NAME        0x009d5448 0x1000 + 10306632
12 APP_NAME        0x009d509c 0x1000 + 10305692
13 APP_NAME        0x009d4ad0 0x1000 + 10304208
14 APP_NAME        0x009d6618 0x1000 + 10311192
15 APP_NAME        0x00cf4d40 0x1000 + 13581632
16 APP_NAME        0x00a5f418 0x1000 + 10871832
17 APP_NAME        0x008d810c 0x1000 + 9269516
18 APP_NAME        0x009b45ac 0x1000 + 10171820
19 APP_NAME        0x009b5140 0x1000 + 10174784
20 UIKit                         0x347ff51e -[UIWindow _sendTouchesForEvent:] + 314
21 UIKit                         0x347ec7fc -[UIApplication sendEvent:] + 376
22 UIKit                         0x347ec116 _UIApplicationHandleEvent + 6150
23 GraphicsServices              0x364e05a0 _PurpleEventCallback + 588
24 GraphicsServices              0x364e01ce PurpleEventCallback + 30
25 CoreFoundation                0x329b9170 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 32
26 CoreFoundation                0x329b9112 __CFRunLoopDoSource1 + 134
27 CoreFoundation                0x329b7f94 __CFRunLoopRun + 1380
28 CoreFoundation                0x3292aeb8 CFRunLoopRunSpecific + 352
29 CoreFoundation                0x3292ad44 CFRunLoopRunInMode + 100
30 GraphicsServices              0x364df2e6 GSEventRunModal + 70
31 UIKit                         0x348402fc UIApplicationMain + 1116
32 APP_NAME        0x008f5c0c 0x1000 + 9391116
33 APP_NAME        0x00d2b0e0 0x1000 + 13803744
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0   libsystem_kernel.dylib        0x3ad76648 kevent64 + 24
1   libdispatch.dylib             0x3aca6974 _dispatch_mgr_invoke + 792
2   libdispatch.dylib             0x3aca6654 _dispatch_mgr_thread$VARIANT$mp + 32
Thread 2 name: WebThread
Thread 2:
0   libsystem_kernel.dylib        0x3ad75eb4 mach_msg_trap + 20
1   libsystem_kernel.dylib        0x3ad76048 mach_msg + 36
2   CoreFoundation                0x329b9040 __CFRunLoopServiceMachPort + 124
3   CoreFoundation                0x329b7d9e __CFRunLoopRun + 878
4   CoreFoundation                0x3292aeb8 CFRunLoopRunSpecific + 352
5   CoreFoundation                0x3292ad44 CFRunLoopRunInMode + 100
6   WebCore                       0x3891a500 RunWebThread(void*) + 440
7   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
8   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 3:
0   libsystem_kernel.dylib        0x3ad75eb4 mach_msg_trap + 20
1   libsystem_kernel.dylib        0x3ad76048 mach_msg + 36
2   APP_NAME        0x00480b04 0x1000 + 4717316
3   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
4   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 4:
0   libsystem_kernel.dylib        0x3ad8608c __psynch_cvwait + 24
1   libsystem_c.dylib             0x3acd7d2a _pthread_cond_wait + 642
2   libsystem_c.dylib             0x3ace1f14 pthread_cond_wait + 36
3   APP_NAME        0x00a33ad4 0x1000 + 10693332
4   APP_NAME        0x0097d9e0 0x1000 + 9947616
5   APP_NAME        0x00a33938 0x1000 + 10692920
6   APP_NAME        0x00a3398c 0x1000 + 10693004
7   APP_NAME        0x00a336b8 0x1000 + 10692280
8   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
9   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 5:
0   libsystem_kernel.dylib        0x3ad8608c __psynch_cvwait + 24
1   libsystem_c.dylib             0x3acd7d2a _pthread_cond_wait + 642
2   libsystem_c.dylib             0x3ace1f14 pthread_cond_wait + 36
3   APP_NAME        0x00a33ad4 0x1000 + 10693332
4   APP_NAME        0x0097d9e0 0x1000 + 9947616
5   APP_NAME        0x00a33938 0x1000 + 10692920
6   APP_NAME        0x00a3398c 0x1000 + 10693004
7   APP_NAME        0x00a336b8 0x1000 + 10692280
8   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
9   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 6:
0   libsystem_kernel.dylib        0x3ad866a4 __semwait_signal + 24
1   libsystem_c.dylib             0x3ace43ce nanosleep + 138
2   APP_NAME        0x00a33724 0x1000 + 10692388
3   APP_NAME        0x00913638 0x1000 + 9512504
4   APP_NAME        0x009135d8 0x1000 + 9512408
5   APP_NAME        0x00a33938 0x1000 + 10692920
6   APP_NAME        0x00a3398c 0x1000 + 10693004
7   APP_NAME        0x00a336b8 0x1000 + 10692280
8   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
9   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 7:
0   libsystem_kernel.dylib        0x3ad8608c __psynch_cvwait + 24
1   libsystem_c.dylib             0x3acd7d2a _pthread_cond_wait + 642
2   libsystem_c.dylib             0x3acd7aa0 pthread_cond_timedwait + 40
3   APP_NAME        0x00a33b54 0x1000 + 10693460
4   APP_NAME        0x000a7254 0x1000 + 680532
5   APP_NAME        0x00a33938 0x1000 + 10692920
6   APP_NAME        0x00a3398c 0x1000 + 10693004
7   APP_NAME        0x00a336b8 0x1000 + 10692280
8   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
9   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 8:
0   libsystem_kernel.dylib        0x3ad866a4 __semwait_signal + 24
1   libsystem_c.dylib             0x3ace43ce nanosleep + 138
2   APP_NAME        0x00a33724 0x1000 + 10692388
3   APP_NAME        0x008caff0 0x1000 + 9215984
4   APP_NAME        0x008cae08 0x1000 + 9215496
5   APP_NAME        0x00a33938 0x1000 + 10692920
6   APP_NAME        0x00a3398c 0x1000 + 10693004
7   APP_NAME        0x00a336b8 0x1000 + 10692280
8   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
9   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 9 name: com.apple.NSURLConnectionLoader
Thread 9:
0   libsystem_kernel.dylib        0x3ad75eb4 mach_msg_trap + 20
1   libsystem_kernel.dylib        0x3ad76048 mach_msg + 36
2   CoreFoundation                0x329b9040 __CFRunLoopServiceMachPort + 124
3   CoreFoundation                0x329b7d9e __CFRunLoopRun + 878
4   CoreFoundation                0x3292aeb8 CFRunLoopRunSpecific + 352
5   CoreFoundation                0x3292ad44 CFRunLoopRunInMode + 100
6   Foundation                    0x332773d0 +[NSURLConnection(Loader) _resourceLoadLoop:] + 304
7   Foundation                    0x332fae80 __NSThread__main__ + 968
8   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
9   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 10 name: com.apple.CFSocket.private
Thread 10:
0   libsystem_kernel.dylib        0x3ad86594 __select + 20
1   CoreFoundation                0x329bd1f2 __CFSocketManager + 674
2   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
3   libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 11:
0   libsystem_kernel.dylib        0x3ad86d98 __workq_kernreturn + 8
1   libsystem_c.dylib             0x3acd4cf6 _pthread_workq_return + 14
2   libsystem_c.dylib             0x3acd4a12 _pthread_wqthread + 362
3   libsystem_c.dylib             0x3acd48a0 start_wqthread + 4
Thread 12:
0   libsystem_kernel.dylib        0x3ad8608c __psynch_cvwait + 24
1   libsystem_c.dylib             0x3acd7d68 _pthread_cond_wait + 704
2   libsystem_c.dylib             0x3aceb080 pthread_cond_timedwait_relative_np + 12
3   APP_NAME        0x00a7e558 0x1000 + 10999128
4   APP_NAME        0x00a7e200 0x1000 + 10998272
5   APP_NAME        0x00a7e0f8 0x1000 + 10998008
6   APP_NAME        0x00a33938 0x1000 + 10692920
7   APP_NAME        0x00a3398c 0x1000 + 10693004
8   APP_NAME        0x00a336b8 0x1000 + 10692280
9   libsystem_c.dylib             0x3acdf30e _pthread_start + 306
10 libsystem_c.dylib             0x3acdf1d4 thread_start + 4
Thread 13:
0   libsystem_kernel.dylib        0x3ad86d98 __workq_kernreturn + 8
1   libsystem_c.dylib             0x3acd4cf6 _pthread_workq_return + 14
2   libsystem_c.dylib             0x3acd4a12 _pthread_wqthread + 362
3   libsystem_c.dylib             0x3acd48a0 start_wqthread + 4
Thread 0 crashed with ARM Thread State (32-bit):
    r0: 0x4095e000    r1: 0x2fdfdf58      r2: 0x0052844c      r3: 0x2fdfdf1c
    r4: 0x00000221    r5: 0x084d8060      r6: 0x2fdfdf14      r7: 0x2fdfdf88
    r8: 0x2fdfdf20    r9: 0x000003fe     r10: 0x4095e000     r11: 0x00000000
    ip: 0x000002fc    sp: 0x2fdfdf10      lr: 0x005284b0      pc: 0x008c71c8
cpsr: 0x20000010
This immediately occurs when I touch and move a little on a specific display object which listens to Mouse-Events DOWN, MOVE to drag it's contents. I think it has something to do with the event system or so. But I'm absolutely blind I guess.
What could I do?

Drill Through to BW - Variable - Range

Has anyone created a drill through to BW which can pass a range value for a dimension by using the configuration? Was able to create drill through which can pass single value for a dimension, but not with range value.
Example: Would like to pass 2011.Jan to 2011.Mar for the period dimension range. Technical name in BW for the period range variable shows one value and not separate values for Period From and period To.

Hi,
I am trying DT to ECC funcationality in BPC 7.5 NW version. I am trying to TD from a P&L report based on hierarchies.
I would like to know how people are using drill-through on parent level nodes within their BPC hierarchies.
I hear that there is something called which is a hierarchical view of their objects/metadata in ECC. How is it related to BPC drill through?
In my example, the DT is from a P&L report that consists of Functoinal Area & P_Account (with a mix of hier nodes and base members) and Company Code in Colum (in summarized columns like N. America, Europe, etc). The current View migth have profiit center hier nodes that comprise of multiple base member profit centers.
We would like to to drill thorugh from a cell that is an intersection of FuncArea-Account parent node and Comoamy Code parent node (N. America) to an ECC profict center transaction - K5EZ (Profit center line item).
Any help/guidance with some documentation if possible is appreciated.
Thanks in advance.
Regards
Raj

Detecting C Series Module Fault through I/O Variable Node

Similar Messages

Maybe you are looking for