Unstable PXI/SCXI system

I’m using a SCXI 1100 with a SCXI 1300 module to read the output of 6 instruments and a test signal. These are used in conjunction with a PXI-6040E module and is housed in a PXI-1011 chassis. The majority of the instruments are 4-20ma and a 120ohm resistor is used across each 1300 input. The test signal is 0.3v taken from a battery-operated supply. When used with my CVI application, all signals seem to periodically dip to low value (0.2V) and then back again, although they are constant when read with a DVM. It doesn’t happen to all signals at the same time but often 2 consecutive channels will drop together. There are 3 other SCXI 1100/1300 modules in the system, with 32 voltage inputs connected to each. These seem to functioning correc
tly. Any ideas? Thanks

Hello Chris_hsl �
It seems like you are having incorrect software readings for these channels.
You may have a settling problem caused by either filters or high gains. First, check to see if you have enabled filtering. If you use a 4 Hz or 10 kHz filter on the SCXI-1100, you must scan channels at a slower rate. Because the filter circuitry is located after the amplifier, you must give the amplifier time to settle before switching to the next channel.
If you are not using the filter, check the amplifier gains you are using on the SCXI-1100 module and the DAQ board. Using a very high gain on your SCXI-1100 module and on some DAQ boards also has the effect of increasing your settling time. Decreasing your scan rate (increasing the delay between channels) should sol
ve this problem.
If these suggestions do not solve your problem, please reply to this post and I will look for a different solution to your dilemma. Have a great day!
Becky B.
Applications Engineer
National Instruments
Becky Linton
National Instruments
Field Engineer
Office: 734-464-2463
Cell: 248-709-2822
Email: [email protected]

Similar Messages

Windows "Blue screen of Death" when booting computer attached to LabVIEW PXI realtime system

Good Morning (at least in the western hemisphere)!
I'm having a problem on two test systems where intermittently, at least on one machine, I get a Windows "Blue Screen of Death" error message when booting the machine connected to a PXI RT system. I reloaded the RT systems software yesterday (LV RT 7.1.1, NI-VISA 3.3.1) and am having this problem on two different setups, two laptops, two PXI chassis. Our short term work around has been to boot with the network cable removed at one end or the other, but these are the baseline models for a larger test system in the design/construction stage that will not be used by knowledgeable engineers but by (probably more knowledgeable!) technicians. Any ideas would be a help
Thanks again,
Putnam
Certified LabVIEW Developer
Senior Test Engineer
Currently using LV 6.1-LabVIEW 2012, RT8.5
LabVIEW Champion

Blue screens are almost always caused by drivers and not by applications, so chances are there's a problem on the driver level. The crash log file will be instrumental to diagnosing this problem.
Turn on the crash event logging as described in this Microsoft KB:
http://support.microsoft.com/kb/314084/EN-US/
...and then post the details from the crash found in the Windows Event Viewer here. That will help us narrow the problem down.
--Paul Mandeltort
Automotive and Industrial Communications Product Marketing

Computing Requirements in Multiple PXI Chassis System

I have acquired a two PXI Chassis system, each with their own embedded controller (PXIe-8108 and PXIe-8130). I would like to control all instruments (simultaneously) in both chassis from a central location (either a laptop or one of the embedded controllers). What is the best configuration for this and will using one controller have enough power to drive two fully populated PXIe-1065 chassis?
(I am aware of the different configurations for control (MXI, etc.) and am more concerned with instrument performance, data buffers become full quickly etc., in using one PC controller)
THANKS!

Hi JMU_ISAT,
The PXIe-1065 chassis uses a four link configuration where there is an x4 link going to slots 7, one to slot 8, another to slots 9-14. There are also an x1 link converted to PXI that goes to slots 2-7 and another x1 link converted to PXI that goes to slots 11-13 and 15-18. Each x4 link gives 1 GB/s of bandwidth and each x1 link converted to PXI will provide 125 MB/s of bandwidth. These bandwidths are theoretical maximums where overhead and chip design reduces the bandwidth somewhat.
The PXI-8130 has four x4 links with the four link configuration so it will be able to get the full chassis bandwidth. The PXIe-8108 has four x1 links which will limit the bandwidth to 250 MB/s for slot 7, slot 8, and slot 9-14.
To synchronize the measurements across both chassis you will need a timing and synchronization module such as the PXIe-6672 in the timing slot of each chassis. This will allow you to route the clock of one timing module to the other and then use that clock to override the backplane reference clock of each chassis. Now each module can use the 10 MHz reference clock to synchronize to each other.
In order to control both chassis from one controller, you can run windows on one controller and LabVIEW RealTime on the other controller allowing you to distribute code from the windows controller to the LabVIEW RealTime controller. The other method would be to run a MXI connection from one chassis to the other to daisy chain the chassis. Since the most you can get out of a single slot of the PXIe-1065 is an x4 link, this would limit the total bandwidth of the daisy chained chassis to 1 GB/s theoretical maximum.
I hope this information is helpful!
Andy K.
Applications Engineer
National Instruments

How can I realize redundant PXI based system?

Hello,
I have to impliment a redundant PXI based system for my application. The System should have 64 channel DIO, 16 channel ADC, 8 channel RS232(redundant), 8 channel DAC.
Overall the system must have redundancy at power supply level, Processor level, communication level, and also at software level.
Can anybody please help me in configuring such a system on PXI or any other NI products? Dual redundant ethernet ports, and redundant processor based systems highly preffered. The system realization model figures will help me more. If any further technical information is required in this regard also I will provide. Please help me in this regard.
Thanks and regards,
A.D.M.Rao

Hello Mr. Brooks,
Thank you for your last reply. I have gone through the following link as you refered.
http://forums.ni.com/ni/board/message?board.id=170&message.id=37638&requireLogin=False
We are interested to impliment the heart beat system. So, please send me how to impliment this system using my earlier inputs to you. I request you to help me in configuring our system for redundancy.
Please send me the detailed information in this regard.
Looking forward for your reply.
With regards,
A.D.M.Rao

Shoud i use them together to connnect to SCXI system?

if i choose SCXI-1520,SCXI-1540,SCXI-1102 as the signal modules,can i choose PCI-6023 as the DAQ device? and should i use R6868 Ribbon cable and CB-68LP I/O connect block together for connecting the SCXI system and the DAQ device? or do i have other more considerable choice?

Yes the 6023E can control an SCXI System. To connect the DAQ board to the SCXI modules you will need a chassis such as the SCXI 1000. You will want an SCXI 1349 cable adapter and I would recommend a SH6868 shield cable if you are measuring low voltage signals so you will have less noise introduced in the cable. When connecting signals to the modules the best solution is to use the corresponding SCXI terminal blocks that mount directly to the SCXI modules.

PXI-SCXI in Linux running LV 8.0.1 consuming all available memory

Hi, we have the following environment here:
Software
- Mandriva 2006 PowerPack
- LabView 8.0 with update 8.0.1 for Linux
- DAQmx 8.0
- DAQmx base 2.0
Hardware
CHASSIS PXI-1011: PXI-8176, 512Mb RAM, 6052e, SCXI-1129 (we are using 7 of them), BORNES SCXI 1129: 1335, matrix topology 8x32
LV program
Two analogic acquisition tasks created and cleared in a non-simultaneous way (one for rotation measurements, and the other for vibration measurements), and a switching task, in a total of 54 sensors.
Here goes the history:
After struggling (togheter with some NI folks) to configure this environment in Linux, now we have a different problem: In a matter of days our application eats all the available memory (swap and RAM) and freezes the PXI-SCXI.
We have already checked:
- (phisical) memories
- all start-clear/stop threads (including different combinations of stop AND clear and only clear)
- isolated our algorithm;
- isolated all local variables and arrays (no global variables);
- isolated all database related code.
In the end, after having only the acquisition tasks running, the LV process still eating aproximatelly 1Mb of RAM per minute, if we use a 1minute window for complete switch-loop and acquisition-loop.
We would like to know if there is some known workaround or upgrade that we are supposed to do to solve this problem.
Thanks in advance for all contributions,
Message Edited by ratem on 08-09-2007 05:34 PM

Hi Ratem,
Memory leaks is a little difficult to debug. I can see you have already done some procedures to isolate the problem. The tests indicate that the acquisition code is consuming the memory. It is possible if you are leaving some tasks open (in memory). All tasks opened must be closed to deallocate the reserved memory.
There are others possibilities to the memory problem. The linux itself can be the problem. Are you sure the memory leaks are only observed when the LV program runs? If it's the case, I will suggest you to do a simple vi, a while loop with a timing function. Does this simple program show the same behavior?
Best Regards,
Alisson Kokot
NI BRAZIL

Logic Pro 9 is unstable on my system and just keeps getting worse. Any ideas?

Hello all, so, I've had a Mac Pro, Quad-Core 2.93 GHz Intel Xeon, 16 GB RAM, Mac Pro running Snow Leopard for about 3 years now. I use Logic Pro 9 (Academic Version) and it is really, really unstable. It seems to go through periods of getting worse, but lately it's been unbearable. I am a professional and I find it hard to believe that this software is allowed to have the word "Pro" in the name if it's this unstable for everyone. But, it seems that only some people have the issues I have. Off the top of my head, a few of the main issues are: CPU spiking like crazy (when the Activity Monitor says very little usage by Logic), I know some of the workarounds like making more auxes and splitting up the load, but this is ridiculous. I shouldn't have to work around a professional piece of software just to use it. Sometimes the CPU spikes with one instrument or one audio channel and nothing going on. It's really messed up.Then there's the memory errors when Logic is only using 1GB or RAM, IF THAT. I don't understand this at all, it also can happen in a fully loaded session or with barely anything going on. Then there are the random crashes that make no sense. There's also the part where it does not agree with many LEGIT-OWNED plugins, like Refx Nexus, XFER Nerve, most of the UAD plugins and many more. There's literally a TON more bugs, but these are the big and obvious ones that ruin my workflow. I have not been able to find a real fix for this, from deleting the preferences to reinstalling. I really don't understand it and Logic seems to work much better for other people I know. It also runs much smoother on my really crappy, old laptop. There's nothing wrong with the Mac Pro (other than it's probably self destructing like we all know Apple products do, but this has been a problem since the day I purchased it), it passes all tests and runs perfectly with any other software - from audio/video editing (Cubase, Ableton, Pro Tools, Final Cut, etc. all run like a dream) to video games. So, I really am fed up with this because I've been using Logic for so long that I really don't want to switch to a new DAW. That would slow down my workflow even more than Logic's crashes already do. Someone please help me, if you can.
Here's my latest crash report:
Process:
Logic Pro [844]
Path:
/Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier:
com.apple.logic.pro
Version:
9.1.8 (1700.67)
Build Info:
Logic-17006700~1
Code Type:
X86 (Native)
Parent Process: launchd [144]
Date/Time:
2012-12-21 13:10:49.982 -0800
OS Version:
Mac OS X 10.6.8 (10K549)
Report Version: 6
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 8
Application Specific Information:
abort() called
Thread 0: Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   com.apple.CoreFoundation
0x9a9622df __CFRunLoopRun + 2079
3   com.apple.CoreFoundation
0x9a9613c4 CFRunLoopRunSpecific + 452
4   com.apple.CoreFoundation
0x9a9611f1 CFRunLoopRunInMode + 97
5   com.apple.HIToolbox
0x959cae04 RunCurrentEventLoopInMode + 392
6   com.apple.HIToolbox
0x959cabb9 ReceiveNextEventCommon + 354
7   com.apple.HIToolbox
0x959caa3e BlockUntilNextEventMatchingListInMode + 81
8   com.apple.AppKit
0x950f9595 _DPSNextEvent + 847
9   com.apple.AppKit
0x950f8dd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
10 com.apple.AppKit
0x950bb1f3 -[NSApplication run] + 821
11 com.apple.prokit
0x00fd4446 NSProApplicationMain + 326
12 com.apple.logic.pro
0x0002bad5 DummyConnection::DummyConnection() + 193
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0   libSystem.B.dylib
0x94c50382 kevent + 10
1   libSystem.B.dylib
0x94c50a9c _dispatch_mgr_invoke + 215
2   libSystem.B.dylib
0x94c4ff59 _dispatch_queue_invoke + 163
3   libSystem.B.dylib
0x94c4fcfe _dispatch_worker_thread2 + 240
4   libSystem.B.dylib
0x94c4f781 _pthread_wqthread + 390
5   libSystem.B.dylib
0x94c4f5c6 start_wqthread + 30
Thread 2:
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   com.apple.CoreFoundation
0x9a9622df __CFRunLoopRun + 2079
3   com.apple.CoreFoundation
0x9a9613c4 CFRunLoopRunSpecific + 452
4   com.apple.CoreFoundation
0x9a9611f1 CFRunLoopRunInMode + 97
5   com.apple.Foundation
0x94e20224 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 329
6   com.apple.Foundation
0x94de74c4 -[NSThread main] + 45
7   com.apple.Foundation
0x94de7474 __NSThread__main__ + 1499
8   libSystem.B.dylib
0x94c57259 _pthread_start + 345
9   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 3: com.apple.CFSocket.private
0   libSystem.B.dylib
0x94c48ac6 select$DARWIN_EXTSN + 10
1   com.apple.CoreFoundation
0x9a9a1c53 __CFSocketManager + 1091
2   libSystem.B.dylib
0x94c57259 _pthread_start + 345
3   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 4:
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   com.apple.CoreFoundation
0x9a9622df __CFRunLoopRun + 2079
3   com.apple.CoreFoundation
0x9a9613c4 CFRunLoopRunSpecific + 452
4   com.apple.CoreFoundation
0x9a967304 CFRunLoopRun + 84
5   com.apple.DVCPROHDMuxer
0x1c78b98f AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 317
6   libSystem.B.dylib
0x94c57259 _pthread_start + 345
7   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 5:
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   ....audio_hijack_server.hermes
0x02ea39b2 ah_serv_loop + 132
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 6:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   com.apple.music.apps.MAFiles
0x02a53838 ResolveFile + 54808
4   com.apple.music.apps.MAFiles
0x02a53901 ResolveFile + 55009
5   libSystem.B.dylib
0x94c57259 _pthread_start + 345
6   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 7:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   com.apple.music.apps.MAFiles
0x02a53838 ResolveFile + 54808
4   com.apple.music.apps.MAFiles
0x02a53901 ResolveFile + 55009
5   libSystem.B.dylib
0x94c57259 _pthread_start + 345
6   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 8 Crashed:
0   libSystem.B.dylib
0x94c970ee __semwait_signal_nocancel + 10
1   libSystem.B.dylib
0x94c96fd2 nanosleep$NOCANCEL$UNIX2003 + 166
2   libSystem.B.dylib
0x94d11fb2 usleep$NOCANCEL$UNIX2003 + 61
3   libSystem.B.dylib
0x94d33685 __abort + 136
4   libSystem.B.dylib
0x94d336f5 abort_report_np + 0
5   com.apple.logic.pro
0x003e6729 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3842985
6   libSystem.B.dylib
0x94c9005b _sigtramp + 43
7   ???
0x0000000b 0 + 11
Thread 9:
0   libSystem.B.dylib
0x94c29c0e mach_wait_until + 10
1   ...ple.CoreServices.CarbonCore
0x9409d7f0 MPDelayUntil + 43
2   ...ple.CoreServices.CarbonCore
0x940ad226 Delay + 107
3   ...opellerheads.rewire.library
0x50d0e654 RWIsReWireMixerAppRunningImp + 30420
4   ...opellerheads.rewire.library
0x50d1d228 RWIsReWireMixerAppRunningImp + 90792
5   libSystem.B.dylib
0x94c57259 _pthread_start + 345
6   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 10:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2   com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3   com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 11:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2   com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3   com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 12:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2   com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3   com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 13:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2   com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3   com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 14:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2   com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3   com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 15:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2   com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3   com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 16:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2   com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3   com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 17:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b09f7c MD::CallProcessThread1(void*) + 108
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 18:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b09cfc MD::CallProcessThread2(void*) + 124
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 19:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b09a6c MD::CallProcessThread3(void*) + 124
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 20:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b097dc MD::CallProcessThread4(void*) + 124
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 21:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b0954c MD::CallProcessThread5(void*) + 124
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 22:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b092bc MD::CallProcessThread6(void*) + 124
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 23:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b0902c MD::CallProcessThread7(void*) + 124
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 24:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b07bac MD::CallProcessThread15(void*) + 124
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 25:
0   libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1   libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2   libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3   ...le.music.apps.MAAudioEngine
0x02b273a9 MDFileIOThread_IsBusy + 3593
4   libSystem.B.dylib
0x94c57259 _pthread_start + 345
5   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 26:
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   com.apple.audio.midi.CoreMIDI
0x0139a0c1 XServerMachPort::ReceiveMessage(int&, void*, int&) + 155
3   com.apple.audio.midi.CoreMIDI
0x013b897a MIDIProcess::RunMIDIInThread() + 150
4   com.apple.audio.midi.CoreMIDI
0x0139b2d9 XThread::RunHelper(void*) + 17
5   com.apple.audio.midi.CoreMIDI
0x0139aca6 CAPThread::Entry(CAPThread*) + 96
6   libSystem.B.dylib
0x94c57259 _pthread_start + 345
7   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 27:
0   libSystem.B.dylib
0x94c29b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x94c576e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x94c865a8 pthread_cond_timedwait_relative_np + 47
3   ...ple.CoreServices.CarbonCore
0x94019b90 TSWaitOnConditionTimedRelative + 242
4   ...ple.CoreServices.CarbonCore
0x940198ce TSWaitOnSemaphoreCommon + 511
5   ...ple.CoreServices.CarbonCore
0x9403db8b TimerThread + 97
6   libSystem.B.dylib
0x94c57259 _pthread_start + 345
7   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 28:
0   libSystem.B.dylib
0x94c48ac6 select$DARWIN_EXTSN + 10
1   com.apple.logic.pro
0x0096fc07 void UnitTest::CheckEqual<ScTypeSetter::tVerticalAlignment, ScTypeSetter::tVerticalAlignment>(UnitTest::TestResults&, ScTypeSetter::tVerticalAlignment, ScTypeSetter::tVerticalAlignment, UnitTest::TestDetails const&) + 375367
2   com.apple.logic.pro
0x005b1d84 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5724676
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 29:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   ...ery 3.MusicDevice.component
0x5c4876be BEngine::SetEngineParThreadProc() + 62
2   ...ery 3.MusicDevice.component
0x5cdc2d68 NI::GP::Thread::execute(void*) + 72
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 30:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   ...ery 3.MusicDevice.component
0x5c4d8336 BStreamingEngine::run() + 230
2   ...ery 3.MusicDevice.component
0x5cdc2d68 NI::GP::Thread::execute(void*) + 72
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 31:
0   libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1   ...ery 3.MusicDevice.component
0x5c82c1ea BBackgroundLoader::run() + 74
2   ...ery 3.MusicDevice.component
0x5cdc2d68 NI::GP::Thread::execute(void*) + 72
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 32:
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   ...tope.audioplugins.AU.Trash2
0x667bd57a catch_exception_raise + 250
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 33:
0   libSystem.B.dylib
0x94c29b5a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib
0x94c576e1 _pthread_cond_wait + 1066
2   libSystem.B.dylib
0x94c865a8 pthread_cond_timedwait_relative_np + 47
3   ...ple.CoreServices.CarbonCore
0x94019b90 TSWaitOnConditionTimedRelative + 242
4   ...ple.CoreServices.CarbonCore
0x940198ce TSWaitOnSemaphoreCommon + 511
5   ...ickTimeComponents.component
0x920ee8b5 ReadSchedulerThreadEntryPoint + 4698
6   libSystem.B.dylib
0x94c57259 _pthread_start + 345
7   libSystem.B.dylib
0x94c570de thread_start + 34
Thread 34:
0   libSystem.B.dylib
0x94c4f412 __workq_kernreturn + 10
1   libSystem.B.dylib
0x94c4f9a8 _pthread_wqthread + 941
2   libSystem.B.dylib
0x94c4f5c6 start_wqthread + 30
Thread 8 crashed with X86 Thread State (32-bit):
eax: 0x0000003c ebx: 0x94c96f39 ecx: 0xb052211c edx: 0x94c970ee
edi: 0x00000000 esi: 0xb0522178 ebp: 0xb0522158 esp: 0xb052211c
   ss: 0x0000001f efl: 0x00000247 eip: 0x94c970ee   cs: 0x00000007
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
cr2: 0x62e4d000
Binary Images:
0x1000 -   0xbeafff com.apple.logic.pro 9.1.8 (1700.67) <94981650-518B-2288-F07D-F28F27103100> /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
0xe8f000 -   0xeadfef com.apple.XSKey 1.0.0 (52) <71B94F53-15DB-9012-91F2-211F7C2CD790> /Library/Frameworks/XSKey.framework/Versions/A/XSKey
0xebc000 -   0xeeffe7 com.apple.music.apps.MAAudioUnitSupport 9.1.8 (233.53) <E8A99468-7726-CCFE-8D26-DDBC9D5E1AC3> /Applications/Logic Pro.app/Contents/Frameworks/MAAudioUnitSupport.framework/Versions/A/MAAudioUnit Support
0xefc000 -   0xf2dff3 com.apple.musicaudiodataservices 1.1 (251.4) <0265F317-13AB-6CF1-A171-7D5853442E75> /Applications/Logic Pro.app/Contents/Frameworks/MAAssetSharing.framework/Versions/A/MAAssetSharing
0xf3c000 -   0xf9aff3 com.apple.music.apps.MALoopManagement 9.1.8 (219.66) <0075F2D0-7A48-A362-2D49-4FECA5E9DF8E> /Applications/Logic Pro.app/Contents/Frameworks/MALoopManagement.framework/Versions/A/MALoopManagem ent
0xfb0000 - 0x11e8fff com.apple.prokit 7.0 (1331) <B3DAD7D3-5D87-CBA6-D4C7-74E96928BA77> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x12f0000 - 0x136afff com.apple.music.apps.MACore 9.1.8 (477.58) <8025A098-49AF-AFF3-4B8E-4C30C06123FF> /Applications/Logic Pro.app/Contents/Frameworks/MACore.framework/Versions/A/MACore
0x138a000 - 0x13d6ffb com.apple.audio.midi.CoreMIDI 1.7.1 (42) <FB4D4B64-6ABB-679E-3AA8-21DE9062B4C1> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x13fb000 - 0x1451ff7 com.apple.music.apps.MAHarmony 9.1.8 (199.72) <448DD823-9EF9-8F88-FFF1-2C7EBD9647B1> /Applications/Logic Pro.app/Contents/Frameworks/MAHarmony.framework/Versions/A/MAHarmony
0x1468000 - 0x1882feb com.apple.music.apps.MAPlugInGUI 9.1.8 (424.79) <9EBA5689-ECE1-E66B-6A0D-DE3F9C7867E4> /Applications/Logic Pro.app/Contents/Frameworks/MAPlugInGUI.framework/Versions/A/MAPlugInGUI
0x1aa0000 - 0x1b82feb com.apple.music.apps.OMF 9.1.8 (109.7) <65E724BA-01DB-68E1-9661-E9B96DA76300> /Applications/Logic Pro.app/Contents/Frameworks/OMF.framework/Versions/A/OMF
0x1b96000 - 0x21e7fe3 com.apple.music.apps.MADSP 9.1.8 (588.98) <93C7306D-07A8-DED0-C59B-B333A475E6DB> /Applications/Logic Pro.app/Contents/Frameworks/MADSP.framework/Versions/A/MADSP
0x28cc000 - 0x28edff7 com.apple.music.apps.LogicFileBrowser 9.1.8 (1700.67) <DB122163-0F15-2E23-16AE-3DCAE41D1870> /Applications/Logic Pro.app/Contents/Frameworks/LogicFileBrowser.framework/Versions/A/LogicFileBrow ser
0x28f6000 - 0x296fff7 com.apple.music.apps.LogicLoopBrowser 9.1.8 (1700.67) <AFAED0FE-A81D-8204-3633-B6DEF6455B8A> /Applications/Logic Pro.app/Contents/Frameworks/LogicLoopBrowser.framework/Versions/A/LogicLoopBrow ser
0x2983000 - 0x29a4ff7 com.apple.music.apps.MAApogeeSupport 9.1.8 (313.26) <B23133C5-90D1-4B22-7421-375F9374C9EA> /Applications/Logic Pro.app/Contents/Frameworks/MAApogeeSupport.framework/Versions/A/MAApogeeSuppor t
0x29a9000 - 0x29aeff7 com.apple.music.apps.MAResources 9.1.8 (212.66) <EEB8FFEB-61A3-69E2-D6AC-AB5C7B8337E2> /Applications/Logic Pro.app/Contents/Frameworks/MAResources.framework/Versions/A/MAResources
0x29b2000 - 0x29dbfe3 com.apple.audio.CoreAudioKit 1.6.1 (1.6.1) <7FFBD485-5251-776A-CC44-4470DD84112B> /System/Library/Frameworks/CoreAudioKit.framework/Versions/A/CoreAudioKit
0x29ec000 - 0x29fcff7 com.apple.AERegistration 1.2 (401) <09312188-9C9E-E1A8-0F53-B8F34AA7F76A> /Applications/Logic Pro.app/Contents/Frameworks/AERegistration.framework/Versions/A/AERegistration
0x2a10000 - 0x2a1cff3 com.apple.music.apps.MAUnitTest 9.1.8 (97.27) <1B77FF0E-ABF2-ABC4-5D7E-638D56A24C69> /Applications/Logic Pro.app/Contents/Frameworks/MAUnitTest.framework/Versions/A/MAUnitTest
0x2a24000 - 0x2adafff com.apple.music.apps.MAFiles 9.1.8 (144.87) <23D65681-872A-1E6B-91E5-B93643CCB375> /Applications/Logic Pro.app/Contents/Frameworks/MAFiles.framework/Versions/A/MAFiles
0x2af3000 - 0x2b6bfe3 com.apple.music.apps.MAAudioEngine 9.1.8 (158.42) <6ADDBB03-0D41-4473-AFC3-385EFA574B87> /Applications/Logic Pro.app/Contents/Frameworks/MAAudioEngine.framework/Versions/A/MAAudioEngine
0x2bd2000 - 0x2bddff7 com.apple.music.apps.MAToolKit 9.1.8 (359.28) <FEEF1A62-CB87-8FD2-F724-0BB660D63146> /Applications/Logic Pro.app/Contents/Frameworks/MAToolKit.framework/Versions/A/MAToolKit
0x2be1000 - 0x2bf5ff7 com.apple.music.apps.MAVideo 9.1.8 (12.70) <FAFE71CD-0FC8-69F4-6FEE-9E873D9F5DD5> /Applications/Logic Pro.app/Contents/Frameworks/MAVideo.framework/Versions/A/MAVideo
0x2c08000 - 0x2cbdfe7 libcrypto.0.9.7.dylib 0.9.7 (compatibility 0.9.7) <AACC86C0-86B4-B1A7-003F-2A0AF68973A2> /usr/lib/libcrypto.0.9.7.dylib
0x2d03000 - 0x2d9fffc com.apple.MobileMe 9 (1.01) <EBADB981-9ED6-82B0-810F-F1CB05CB5A17> /Applications/Logic Pro.app/Contents/Frameworks/MobileMe.framework/Versions/A/MobileMe
0x2e59000 - 0x2e8eff7 com.apple.prokit.SnowLeopardPanels 7.0 (1331) <BB481932-46DC-8FB1-97CB-67C484A6CBF2> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/SnowLeo pardPanels.bundle/Contents/MacOS/SnowLeopardPanels
0x2e9f000 - 0x2eabff7 +com.rogueamoeba.audio_hijack_server.hermes 2.2.5 (2.2.5) <CD6C7A74-BA03-F3A7-0D1E-460E6A043024> /usr/local/hermes/modules/Instant Hijack Server.hermesmodule/Contents/MacOS/Instant Hijack Server
0x3f9a000 - 0x3f9eff3 com.apple.audio.AudioIPCPlugIn 1.1.6 (1.1.6) <E9CB576C-283B-1DB2-0C69-E7C914BD7922> /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugI n.bundle/Contents/MacOS/AudioIPCPlugIn
0x3fa3000 - 0x3fa9ff7 com.apple.audio.AppleHDAHALPlugIn 2.0.5 (2.0.5f14) <38E3C1A4-84E4-C105-B55F-8FC4C154036D> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bun dle/Contents/MacOS/AppleHDAHALPlugIn
0x3fae000 - 0x3fccfff +de.access-music.virus_ti.util.hal ??? (2.1.0) <DBC06F6E-0D35-0700-D515-CD0BAC2B6002> /Library/Audio/Plug-Ins/HAL/de.access-music.virus_ti.plugin/Contents/MacOS/de.a ccess-music.virus_ti
0x1b0b3000 - 0x1b0ddff7 +com.grame.JackRouter JackRouter (0.9.5) <13AB2581-FFAF-AC76-FB8F-D1C8779C94AF> /Library/Audio/Plug-Ins/HAL/JackRouter.plugin/Contents/MacOS/JackRouter
0x1c4a2000 - 0x1c4cbfff +Jackmp ??? (???) <0B8EB3A5-FD59-2D99-839C-2D4A9A59AA94> /Library/Frameworks/Jackmp.framework/Versions/A/Jackmp
0x1c700000 - 0x1c755fe2 com.apple.DVCPROHDAudio 1.3.2 (1.3.2) <2E0A9883-4EA5-706F-78F6-4C1F105A4D30> /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio
0x1c774000 - 0x1c7d9fe0 com.apple.DVCPROHDMuxer 1.3.2 (1.3.2) <483DD62C-46C4-36AA-6A1C-2DEA6F062863> /Library/QuickTime/DVCPROHDMuxer.component/Contents/MacOS/DVCPROHDMuxer
0x4577c000 - 0x45782ff7 +com.prosofteng.soundbunny.plugin 1.0.2 (898) <26781624-AE2F-3FCB-A11A-FC51C889E7A8> /Library/Audio/Plug-Ins/HAL/SoundBunny.plugin/Contents/MacOS/SoundBunny
0x457af000 - 0x457b7ff7 com.apple.proapps.mrcheckpro 1.4 (397) <25DBA6AA-139D-EFAC-1BF8-5D29A3DFA497> /Applications/Logic Pro.app/Contents/Resources/MRCheckPro.bundle/Contents/MacOS/MRCheckPro
0x457f2000 - 0x457f4ff3 com.apple.music.apps.anvil.resources 9.1.8 (280.4) <AFA90574-C724-880F-9C99-52E064F5B3E8> /Applications/Logic Pro.app/Contents/PlugIns/anvil.res/Contents/MacOS/anvil
0x457f8000 - 0x457faff3 com.apple.music.apps.common.resources 9.1.8 (280.4) <579C1A3C-3636-9A69-185E-819DC01E1083> /Applications/Logic Pro.app/Contents/PlugIns/common.res/Contents/MacOS/common
0x460e9000 - 0x460eafef com.apple.music.apps.midi.device.plugin.FaderPort 9.0.0 (173) <00C2D825-856B-A371-4684-6FCD1FDECC21> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/FaderPort.bundle/Contents/MacOS/FaderPort
0x46161000 - 0x46163ff3 com.apple.music.apps.ebp.resources 9.1.8 (280.4) <95A85BC0-7D35-B965-2026-1A44E96DC653> /Applications/Logic Pro.app/Contents/PlugIns/ebp.res/Contents/MacOS/ebp
0x46e3b000 - 0x46fb4ff7 GLEngine ??? (???) <76C922AA-A4A7-2835-537B-17F316AD95F6> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x46fe6000 - 0x473f9fef com.apple.ATIRadeonX2000GLDriver 1.6.36 (6.3.6) <257CAA1D-6573-2932-E344-E96F6C9CDA84> /System/Library/Extensions/ATIRadeonX2000GLDriver.bundle/Contents/MacOS/ATIRade onX2000GLDriver
0x4742b000 - 0x4744ffe7 GLRendererFloat ??? (???) <F19DDBE8-1DF6-6618-F554-0E81ED85CE67> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GL RendererFloat
0x47705000 - 0x47708fe7 com.apple.MIDIDevicePlugIn.Axiom Pro 1.0.1 (70) <B8D61742-3ADC-1EDB-4D0B-344E0CD0D33A> /Library/Application Support/MIDI Device Plug-ins/Axiom Pro.bundle/Contents/MacOS/Axiom Pro
0x47840000 - 0x47842ff3 com.apple.music.apps.efx.resources 9.1.8 (280.4) <FB5BBFF8-DF5E-32BC-4F4C-C5A2DA3FB1A6> /Applications/Logic Pro.app/Contents/PlugIns/efx.res/Contents/MacOS/efx
0x47846000 - 0x47848ff3 com.apple.music.apps.egt.resources 9.1.8 (280.4) <11B09E42-9FC4-A372-8738-057CAB888671> /Applications/Logic Pro.app/Contents/PlugIns/egt.res/Contents/MacOS/egt
0x4784c000 - 0x4784eff3 com.apple.music.apps.emx.resources 9.1.8 (280.4) <A3C65CFE-2BBF-DB8C-D4C8-5950284E44CF> /Applications/Logic Pro.app/Contents/PlugIns/emx.res/Contents/MacOS/emx
0x47852000 - 0x47854ff3 com.apple.music.apps.es1.resources 9.1.8 (280.4) <DB1CD8D6-2C8F-32EE-266B-A28C00B2DFB7> /Applications/Logic Pro.app/Contents/PlugIns/es1.res/Contents/MacOS/es1
0x47858000 - 0x4785aff3 com.apple.music.apps.es2.resources 9.1.8 (280.4) <7E91D13E-87CF-0B50-14A7-9B7A1E3D345C> /Applications/Logic Pro.app/Contents/PlugIns/es2.res/Contents/MacOS/es2
0x4785e000 - 0x47860ff3 com.apple.music.apps.esp.resources 9.1.8 (280.4) <C5284B25-3250-2201-D4EE-523FE37B9E6B> /Applications/Logic Pro.app/Contents/PlugIns/esp.res/Contents/MacOS/esp
0x47864000 - 0x47866ff3 com.apple.music.apps.evb3.resources 9.1.8 (280.4) <068F656F-6CA6-37E9-96F5-1F8E10546A43> /Applications/Logic Pro.app/Contents/PlugIns/evb3.res/Contents/MacOS/evb3
0x4786a000 - 0x4786cff3 com.apple.music.apps.evd6.resources 9.1.8 (280.4) <B15F044D-60BB-FD36-6A49-685C7DCA7FB4> /Applications/Logic Pro.app/Contents/PlugIns/evd6.res/Contents/MacOS/evd6
0x47870000 - 0x47872ff3 com.apple.music.apps.evoc.resources 9.1.8 (280.4) <E361301A-56EF-FF6C-67E5-AC3D9F15E190> /Applications/Logic Pro.app/Contents/PlugIns/evoc.res/Contents/MacOS/evoc
0x47876000 - 0x47878ff3 com.apple.music.apps.evp88.resources 9.1.8 (280.4) <6E1152B4-E9F3-3F6E-7246-A10456888210> /Applications/Logic Pro.app/Contents/PlugIns/evp88.res/Contents/MacOS/evp88
0x4787c000 - 0x4787eff3 com.apple.music.apps.exs24.resources 9.1.8 (280.4) <DC363BF8-D15A-6049-F148-7804EADF7539> /Applications/Logic Pro.app/Contents/PlugIns/exs24.res/Contents/MacOS/exs24
0x47882000 - 0x47884ff3 com.apple.music.apps.guitaramp.resources 9.1.8 (280.4) <27F67C33-C9BA-D9CE-DC89-A33A7F674F2C> /Applications/Logic Pro.app/Contents/PlugIns/guitaramp.res/Contents/MacOS/guitaramp
0x47888000 - 0x4788aff3 com.apple.music.apps.guitarcontrols.resources 9.1.8 (280.4) <DAD1836E-F4DD-EB95-2F48-A8AF8552D087> /Applications/Logic Pro.app/Contents/PlugIns/guitarcontrols.res/Contents/MacOS/guitarcontrols
0x4788e000 - 0x47890ff3 com.apple.music.apps.mutapdel.resources 9.1.8 (280.4) <555A65F0-E35D-0F5F-76EC-7C83D06C68AB> /Applications/Logic Pro.app/Contents/PlugIns/mutapdel.res/Contents/MacOS/mutapdel
0x47894000 - 0x47896ff3 com.apple.music.apps.pedalboard.resources 9.1.8 (280.4) <9923C7F7-E681-EE64-06CE-A0C8AABF7E65> /Applications/Logic Pro.app/Contents/PlugIns/pedalboard.res/Contents/MacOS/pedalboard
0x4789a000 - 0x4789cff3 com.apple.music.apps.revolver.resources 9.1.8 (280.4) <9AE36A7E-5D8F-681C-ABFD-4BCFE5048FF4> /Applications/Logic Pro.app/Contents/PlugIns/revolver.res/Contents/MacOS/revolver
0x478a0000 - 0x478a2ff3 com.apple.music.apps.sphere.resources 9.1.8 (280.4) <FF758F38-414E-5BFD-97CF-778DF8F52EAE> /Applications/Logic Pro.app/Contents/PlugIns/sphere.res/Contents/MacOS/sphere
0x478f1000 - 0x478f6ffb +com.WavesAudio.WavesReWireDevice.8.0.0 8.0.0 (8.0.0.10) <DBA04305-F027-23DF-A1EC-4D112843C03F> /Library/Application Support/Propellerhead Software/ReWire/WavesReWireDevice.bundle/Contents/MacOS/WavesReWireDevice
0x48ff8000 - 0x48ffaff3 com.apple.music.apps.midi.device.plugin.GiO 9.1.8 (198.73) <E2634721-B8D4-03CE-43B5-7C64EED8BFD3> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/GiO.bundle/Contents/MacOS/GiO
0x50ce5000 - 0x50d6cffb +se.propellerheads.rewire.library 1.8.1 build 124 (1.8.1) <79A1E240-4153-9288-475D-697D84C94343> /Library/Application Support/Propellerhead Software/ReWire/ReWire.bundle/Contents/MacOS/ReWire
0x50d7a000 - 0x5122dff7 +com.ableton.live-engine 8.2 (8.2) <DCF40AE3-0F7F-41FC-2B5E-EA8673EFBE99> /Applications/Live 8.2 OS X/Live.app/Contents/Resources/Ableton Live Engine.bundle/Contents/MacOS/Ableton Live Engine
0x5193c000 - 0x51947ff7 com.apple.DVCPROHDVideoOutput 1.3.2 (1.3.2) <8D8A75CC-6204-1187-04CC-B3323E76DCF9> /Library/QuickTime/DVCPROHDVideoOutput.component/Contents/MacOS/DVCPROHDVideoOu tput
0x519c9000 - 0x51d33fef +se.propellerheads.reason.engine 5.0 (5.0) <D7415C86-0873-62CC-358B-B205326D790D> /Applications/Reason/Reason.app/Contents/PlugIns/Reason Engine.plugin/Contents/MacOS/Reason Engine
0x51ffc000 - 0x5205bfe1 +se.propellerheads.rewire.library 1.7 (1.7) /Users/brandonscrushy/Library/Application Support/Propellerhead Software/ReWire/ReWire.bundle/Contents/MacOS/ReWire
0x5207a000 - 0x52095ff7 com.apple.OpenTransport 10.6.0 (10.6.0) <ECA6FEC6-5ECD-51BA-162F-CFC43899196A> /System/Library/PrivateFrameworks/OpenTransport.framework/OpenTransport
0x52328000 - 0x52369fe3 com.apple.audio.SoundManager.Components 3.9.4 (3.9.4) <AD66647C-03A9-EBAF-6FFC-E5A631F4D6BE> /System/Library/Components/SoundManagerComponents.component/Contents/MacOS/Soun dManagerComponents
0x52370000 - 0x523acfe3 com.apple.QuickTimeFireWireDV.component 7.6.6 (1791) <50D03C98-3DF6-BF7E-6440-7E3AB5A78CBE> /System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/MacOS/QuickTim eFireWireDV
0x523b8000 - 0x52475fe2 com.apple.DesktopVideoOut 1.2.7 (1.2.7) <7959538F-2A96-F2BB-EEC3-0718A326C152> /Library/QuickTime/DesktopVideoOut.component/Contents/MacOS/DesktopVideoOut
0x52494000 - 0x5249eff7 com.apple.IOFWDVComponents 1.9.9 (1.9.9) <5B4E7BD7-EF5A-2F5C-DF8E-3D4A7B59F779> /System/Library/Components/IOFWDVComponents.component/Contents/MacOS/IOFWDVComp onents
0x524e8000 - 0x524eafe3 com.apple.music.apps.midi.device.plugin.CS-32 9.1.8 (198.73) <EA9B28F8-4962-8224-D724-7ECA99692774> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/CS-32.bundle/Contents/MacOS/CS-32
0x524f2000 - 0x524f5feb com.apple.music.apps.midi.device.plugin.FW-1884 9.1.8 (198.73) <9A51CFA4-711B-1164-6874-80FBF4411A3B> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/FW-1884.bundle/Contents/MacOS/FW-1884
0x52700000 - 0x52704ffb com.apple.music.apps.midi.device.plugin.HUI 9.1.8 (198.73) <838E7E91-15F9-779A-9F34-18003221C5CE> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/HUI.bundle/Contents/MacOS/HUI
0x52710000 - 0x52711fff com.apple.music.apps.midi.device.plugin.iControl 9.1.8 (198.73) <F67DC4BC-6556-6AB6-F5CA-C07F087EF639> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/iControl.bundle/Contents/MacOS/iControl
0x52717000 - 0x5271eff3 com.apple.music.apps.midi.device.plugin.Logic-Control 9.1.8 (198.73) <04DC4A0E-2FE2-BE3F-5F5C-686FB712D8F5> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/Logic Control.bundle/Contents/MacOS/Logic Control
0x5273b000 - 0x5273cfff com.apple.music.apps.midi.device.plugin.MCS3 9.1.8 (198.73) <FB25C00A-5481-F18F-21DB-53D28ADCC168> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/MCS3.bundle/Contents/MacOS/MCS3
0x52741000 - 0x52743ff7 com.apple.music.apps.midi.device.plugin.microKONTROL 9.1.8 (198.73) <48E33623-5220-448C-E0D5-6F53B79EC815> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/microKONTROL.bundle/Contents/MacOS/microKONTROL
0x5274a000 - 0x5274aff3 com.apple.music.apps.midi.device.plugin.Recording-Light 9.1.8 (198.73) <62130915-EEC9-7EE1-AFB9-737A32AA09AC> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/Recording Light.bundle/Contents/MacOS/Recording Light
0x5274f000 - 0x52752fff com.apple.music.apps.midi.device.plugin.TouchOSC 9.1.8 (198.73) <09337083-973D-480B-C17F-8F68AE3F2FA2> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/TouchOSC.bundle/Contents/MacOS/TouchOSC
0x5275b000 - 0x5275dff3 com.apple.music.apps.midi.device.plugin.TranzPort 9.1.8 (198.73) <26E0C91B-097C-E77A-5E34-6BD85A8BA365> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/TranzPort.bundle/Contents/MacOS/TranzPort
0x52762000 - 0x52764fe7 com.apple.music.apps.midi.device.plugin.US-2400 9.1.8 (198.73) <8D056088-15A4-9FE5-4DDD-14CA2AC746A4> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/US-2400.bundle/Contents/MacOS/US-2400
0x5276d000 - 0x5276effb com.apple.music.apps.midi.device.plugin.US-428 9.1.8 (198.73) <A9C8442B-C474-977F-B61C-4C35DF494201> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/US-428.bundle/Contents/MacOS/US-428
0x527ef000 - 0x527f0ff7 com.apple.textencoding.unicode 2.3 (2.3) <78A61FD5-70EE-19EA-48D4-3481C640B70D> /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
0x5332a000 - 0x5332affd +jp.Canon.DPPCMPlugIn ??? (1.0) /Library/Contextual Menu Items/dppCMPlugIn.plugin/Contents/MacOS/dppCMPlugIn
0x5b18a000 - 0x5b18aff7 libmx.A.dylib 315.0.0 (compatibility 1.0.0) <01401BF8-3FC7-19CF-ACCE-0F292BFD2F25> /usr/lib/libmx.A.dylib
0x5b3c9000 - 0x5b3cafff +com.symantec.NAVCMPlugIn 11.1 (102) /Library/Contextual Menu Items/NAVCMPlugIn.plugin/Contents/MacOS/NAVCMPlugIn
0x5b5ec000 - 0x5b606fff +AdobeBIB ??? (???) /Library/Contextual Menu Items/ADFSMenu.plugin/Contents/Frameworks/AdobeBIB.framework/Versions/A/AdobeBI B
0x5b611000 - 0x5b617ff7 +com.symantec.avscan.framework 1.0.2 (6) /Library/PrivateFrameworks/SymAVScan.framework/Versions/A/SymAVScan
0x5bab6000 - 0x5bac7fe7 com.apple.FCP Uncompressed 422.component 1.6.1 (1.6.1) <62C290FB-2735-60C4-CE88-7ECB0DE6EDB3> /Library/QuickTime/FCP Uncompressed 422.component/Contents/MacOS/FCP Uncompressed 422
0x5bb49000 - 0x5bb64fef com.apple.AppleIntermediateCodec 1.3.2 (153) <D42634C1-8BDA-31ED-5216-13CB19BA7D1B> /Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS/AppleInterme diateCodec
0x5bb6a000 - 0x5bb83fe7 com.apple.applepixletvideo 1.2.29 (1.2d29) <52810348-A138-D148-92E4-9E1D73EA18A0> /System/Library/QuickTime/ApplePixletVideo.component/Contents/MacOS/ApplePixlet Video
0x5bc19000 - 0x5bc2cfe3 com.apple.IMXCodec 1.4 (155) <B7A1514F-1A2B-EC3E-719D-B8BB25016A05> /Library/QuickTime/IMXCodec.component/Contents/MacOS/IMXCodec
0x5c2c3000 - 0x5d52bfe3 +Battery 3.MusicDevice.component 3.2.3. (R637) (3.2.3. (R637), Copyright © 2011 Native Instruments) <8263B199-AABD-2CA2-6BAB-1111FF6B9828> /Library/Audio/Plug-Ins/Components/Battery 3.component/Contents/MacOS/Battery 3
0x5dbd8000 - 0x5dc0cfff +se.propellerheads.rex.library 1.7.0 (1.7.0) <7180964B-2D1C-03CC-E266-51DE3EFBAFA6> /Library/Application Support/Native Instruments/Helper/REX Shared Library.bundle/Contents/MacOS/REX Shared Library
0x5dcab000 - 0x5e04fff7 +de.native-instruments.kconvert.macho.bundle 3.0.0.7 (3.0.0.7) <92504456-EF51-82A6-ABBE-0FA019B40B23> /Library/Application Support/Native Instruments/Battery 3/bconvert.bundle/Contents/MacOS/kconvert
0x5fb4f000 - 0x5fb86fe7 com.apple.DVCPROHDCodec 1.5 (237) <5BA42205-5AEE-73BB-A7DE-5417EF028D5B> /Library/QuickTime/DVCPROHDCodec.component/Contents/MacOS/DVCPROHDCodec
0x5fba7000 - 0x5fbc3ffb +com.symantec.sharedsettings.framework 1.3 (6) /Library/PrivateFrameworks/SymSharedSettings.framework/Versions/A/SymSharedSett ings
0x601d3000 - 0x6028afef +com.xfer.LFOTool 1.0 (1.0) <AD242775-C1D9-3F6E-AACF-598117B69C22> /Library/Audio/Plug-Ins/Components/LFOTool.component/Contents/MacOS/LFOTool
0x60e27000 - 0x61236fc3 +com.reFX.Nexus 2.4.2 (2.4.2) <CB29856E-0602-3904-A599-26FDDB615A26> /Library/Audio/Plug-Ins/Components/Nexus.component/Contents/MacOS/Nexus
0x61334000 - 0x613b0ff3 +com.eLicenser.POSAccess-DLL ??? (1.4.0.9) <9FEB2066-B500-305F-8C6C-182F3BD62666> /Library/Application Support/eLicenser/pos/Synsoacc.bundle/Contents/MacOS/Synsoacc
0x633b7000 - 0x633dbfe3 +com.symantec.symbase 2.3 (15) <2FD986B4-9D7B-8800-0DDA-0872E4FD997F> /Library/PrivateFrameworks/SymBase.framework/Versions/B/SymBase
0x63f57000 - 0x64662fef +com.cytomic.theglue 1.0.15 (1.0.15) <3858820B-835B-6FDA-2E5D-EBE4241EF912> /Users/brandonscrushy/Library/Audio/Plug-Ins/Components/The Glue.component/Contents/MacOS/The Glue
0x64f33000 - 0x64f59ff7 +com.TailoredNoise.AU.SausageFattener 1.0 (1.0) <38AD3492-C3F8-3ED5-A625-95CCD38116E4> /Library/Audio/Plug-Ins/Components/SausageFattener.component/Contents/MacOS/Sau sageFattener
0x66000000 - 0x66199ff7 +com.wallanderinstruments.VST.SausageFattener ??? (2.32) <40C8BC6E-05FD-F722-A700-596499F82A71> /Library/Application Support/SausageFattener/Resource/SausageFattener.dat/Contents/MacOS/SausageFatt ener
0x66770000 - 0x667ebffb +com.izotope.audioplugins.AU.Trash2 2.0.0 (2.0.0b257) <ECBCABDA-2457-3058-A580-E2744D200565> /Library/Audio/Plug-Ins/Components/iZTrash2AUHook.component/Contents/MacOS/Plug inHooksAU
0x67a84000 - 0x684baffb +com.izotope.audioplugins.Trash2 2.0.0 (2.0.0b257) <88BA73FD-A36F-3344-8EAC-90E6C6D88DDE> /Library/Audio/Plug-Ins/Components/iZTrash2AUHook.component/Contents/Resources/ iZTrash2.bundle/Contents/MacOS/iZTrash2
0x6f9ce000 - 0x6fa0afc7 +com.adobe.vcmenu ??? (4.0.0.344) /Library/Contextual Menu Items/ADFSMenu.plugin/Contents/MacOS/ADFSMenu
0x6fa64000 - 0x6fa7cfe3 +com.symantec.internetSecurity.framework 1.3.2 (5) <0FF940EF-4FA3-C001-A7D1-976FE2351F54> /Library/PrivateFrameworks/SymInternetSecurity.framework/Versions/A/SymInternet Security
0x6fd40000 - 0x6fef6feb +com.fabfilter.Timeless.AU.2 2.13 (2.13) <141A5C98-C087-1463-2921-B7B695C0D35D> /Library/Audio/Plug-Ins/Components/FabFilter Timeless 2.component/Contents/MacOS/FabFilter Timeless 2
0x7083e000 - 0x7087efec +com.audiodamage.audiounit.DubStation_15 1.5.1 (1.5.1) <D2D31F5F-7C6E-2D59-A7B8-9753F0BD4D84> /Library/Audio/Plug-Ins/Components/DubStation_15.component/Contents/MacOS/DubSt ation_15
0x71232000 - 0x713dffeb +com.soundtoys.audiounit.EchoBoy 4.0.2 (4.0.2) <15B3A8F0-5DA7-8996-19B3-4B1D0CE6EC7D> /Library/Audio/Plug-Ins/Components/Echoboy.component/Contents/MacOS/EchoBoy
0x73c41000 - 0x74c2efe7 +com.voxengo.audio-plugins.audiounit.SPAN 2.4.1 (2.4.1) <B60A5232-CEEB-DF40-270E-5CEDCCD45704> /Library/Audio/Plug-Ins/Components/SPAN.component/Contents/MacOS/SPAN
0x76af0000 - 0x76b1cfe2 +com.symantec.daemon.framework 1.2.2 (7) <18F8E556-EA30-D193-69CB-4B0A60A5E821> /Library/PrivateFrameworks/SymDaemon.framework/Versions/A/SymDaemon
0x76d0f000 - 0x76d7cfe7 com.apple.AppleProResCodec 2.0 (224) <B7A79FF2-9C32-5554-A3C3-BE91F9B89419> /Library/QuickTime/AppleProResCodec.component/Contents/MacOS/AppleProResCodec
0x76dc9000 - 0x76e43fef com.apple.AppleVAH264HW.component 2.0 (1.0) <9F28FEE8-C61E-C474-4C4A-B4932DF28794> /System/Library/QuickTime/AppleVAH264HW.component/Contents/MacOS/AppleVAH264HW
0x76f06000 - 0x76fb5fe3 com.apple.AppleHDVCodec 1.6 (229) <C45D37E1-3CE0-1FBE-17DE-91D5B65FD940> /Library/QuickTime/AppleHDVCodec.component/Contents/MacOS/AppleHDVCodec
0x7f01a000 - 0x7f547ff7 +com.RPCX.SubBoomBass.component 1.1.0 (1.1.0) <62D227BF-1409-A527-ABEA-A4EF7B134BCD> /Library/Audio/Plug-Ins/Components/SubBoomBass.component/Conte

Pancenter...
Yes... but I have come across some setups that came with a native SL (and even one Lion!) installation.. that somehow had a corrupted or older Prokit installed for some unknown reason... and given it's a quick fix to try.. I thought I'd mention it..
I frankly don't think it is entirely a Prokit issue itself, but it wouldn't do any harm to try and install v7 just in case it is part of the problem...
+1 on the UAD stuff....
Also, at the time it crashed... according to the logs...the OP was running Ableton Live at the same time, presumably rewired with Logic... so add all that together with UAD plugins... and that's quite a load on the system...
Finally in thread 32 there is a weird exception msg relating to the Trash2 plugin.. that I haven't seen before...
Thread 32:
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   ...tope.audioplugins.AU.Trash2
0x667bd57a catch_exception_raise + 250
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
That might be nothing... but as i said, I haven't seen that one before and given what else is going on.. it might be involved too... or nothing to do with that at all!

SLD configuration for DXI / PXI technical systems

Hello,
we have a problem when transporting XI configuration objects from XI dev to XI prod. The transport objects arrive in XI prod, but the name of the business system (for the SAP backend system) is not converted from dev business system (T01CLNT010) to prod business system (P01CLNT01) although the transport target for T01CLNT010 business system was set correctly (we are using business system groups Dev and Prod). And the "related integration server" for T01CLNT010 was also set correctly to DXICLNT010.
But then I noticed that the technical system for the DXI (XI Dev) is configured as follows:
TMS Domain ("DOMAIN_PXI") and TMS Transport Group Name GROUP_PXI ("GROUP_PXI") have the same values as PXI. Is that correct ?? We are using file transport, not CMS.
Another strange effect is that when I set the group in business system DXICLNT010 to Dev, that is also applied to business system PXICLNT010 ! Which is of course not what I want.
I assume I have to associate DXICLNT010 to Dev and PXICLNT010 to Prod, same as for T01CLNT010 / P01CLNT010. Correct ? Or does the group in the XI business systems not matter ?
Can anyone post an example of a working SLD configuration with two XI system dev and prod ? What values do I have to use in the XI technical and business systems, so that the transport will work ?
CSY

There's obviously something wrong in the SLD configuration for the exchange infrastructure systems. The error you're describing (one system pointing to another) usually occurs when one system is generated through homogeneous system copy of another system (was that your case?). I've seen that behaviour once and they corrected it by manually deleting the exchange infrastructure systems from SLD and creating them again from scratch.
Anyway, I highly recommend you to get an expert NW Basis consultant to realize a check in it before you proceed any further.
Aside of that, you're correct in your assumptions.
Your config in SLD should be like:
DEV_GROUP:
- DXI
- T01
PRD_GROUP:
- PXI
- P01
It's always 1 XI BS per group.
Also, if you use separate SLDs for XI Dev and XI Prd, you have to make sure that this configuration is reflected in both SLDs. So, if you make it one SLD instance, you must generate a delta export zip file from the SLD where you did the configuration and import this zip file in the other SLD instance.
If you use a central SLD, then it's not necessary.
Regards,
Henrique.

PXI-1006 system crahes-Blue Screen

Problem: System Crash - Blue Screen - PXI 1006
I am using NI IPX-1006. Environment: Win NT 4.0 with CVI 5.5.
Problems
1. Everytime the system crashes the .Prj file is lost from the project folder.
2. This time nipalk.sys and nibffrk.dll got corrupted (no entry point found). I replaced those from other system. The corrution message do not come anymore, but as soon as I try to run my test program, it crahses again ....
Blue Screen Message: "KMODE_EXCEPTION-NOT-HNADLED ...Adress FD337FAC has base address at FD327000-NYPALK.SYS ..."
Does anyone has any solutions/ update!
Thank YOU.

Hi Anna:
Primarily it crahses when I open the Measurement and Automation Explorer (as well as run when I run application which uses Digital IO-PXI-6527, GPIB, Relays PXI-2565..). It is NOT a new setup, but the problem is new. Initially it was related to "failure to find entry point to a dll >> nibffrk.dll". Then I copied the dll from another PXI-1006 chasis and replaced in this machine. But problem is still there!
Please note the environment is as follows: PXI-1006 chasis with PXI-6527, 2565, 6070, 4060, 5102; OS WinNT 4.0 - CVI 5.5-Measurement and Automation Explorer 2.0. In my application I am using NI-DAQ driver.
Should I reinstall the machine ?
Thank you very much.
Delowar

Can I use our PC with existing SCXI setup (conencted to a PC by PCI-MIO-16E4) and use one labview application to communicate with FP and SCXI systems at the same time?

We have an existing PC with SCXI setup. can i plug in a PCI-485/2 card connected to a FP-1001 network, and get both systems to be utilized in a single labview VI?

Yes, you can utilize both sets of resources (SCXI and FieldPoint) at the same time from the same VI.
If you were using the SCXI RS-485 interface, the SCXI and FieldPoint system would have to be on separate serial ports. Beyond that, there should be no real restrictions on accessing both of them.
Regards,
Aaron

Can I use a SCXI system with 1102Cs and 1120D AND control a GPIO on RTSI0?

I have a complex system with multiple DAQ cards and a SCXI chasis on a 6341.
I need to place a GPIO software controlled digital signal on RTSI0 (preferably).
Can I run the SCXI chassis AND use the 6341 card to control a TTL line on RTSI0? Getting to the HW is difficult, so I would like to know this before I set out. NI tech support has not been helpful getting this resolved.
Thanks

Hey Jed,
I just wanted to let you know that our support team is working on the issue, but if anyone else has other options we are welcome to any suggestions.
We should get back with you soon,
Regards
J Newk
Systems Engineer
National Instruments

PXI-8187 System state: Unconfigured

Bonjour,
j'ai un problème au boot avec mon controleur PXI-8187 dans un chassis PXI-1000B
message affiché:
Labview RT Boot Loader
(C) Copyright ....
Intel 8255x Ethernet found.
Initializing network ... done: IP address is 0.0.0.0
System state: Unconfigured
Merci pour votre reponse
Cordialement.

Bonjour,
Tout d'abord, il faut connecter votre contrôleur à un PC Host. Sur ce PC Host, il faut que LabVIEW RT (même version que sur votre contrôleur PXI) et MAX (Measurement and Automation eXplorer) y soient installés.
1/ Dans MAX, allez à la rubrique "Systèmes déportés" ainsi votre contrôleur doit apparaître sous cette arborescence.
2/ Une fois votre contrôleur sélectionné, dans la partie droite de MAX, pour configurer l'adresse IP de votre contrôleur, sélectionnez l'obtention d'une adresse IP en DHCP. Afin d'avoir les mêmes paramètres réseau que le PC Host.
3/ Cliquez sur le bouton "Appliquer"
4/ Redémarrez votre contrôleur.
Lors du redémarrage de celui-ci, l'adresse IP configurée précedemment dans MAX, doit apparaître sur l'écran de votre contrôleur.
Ensuite, pour l'utilisation de vos cartes PXI de votre chassis, vous devez installer les drivers correspondants à ces cartes en allant dans la partie "logiciels" de voter contrôleur puis en cliquant sur "Installer". Attention, il faut que les drivers soient installés sur le PC Host et soient plus récents que Novembre 2003.
De plus, voici une :note d'application en anglais reprenant ces différents points.
Salutations,
Isabelle
Ingénieur d'applications
National Instruments France

PXI 8184 system boots up - shows nothing on screen

Hi All,
I recently found our NI PXI-8184 in our company and I wanted to test if we can use the device for our testing purposes.
The first time, I got to its BIOS. I saw the system date was resetted to 1988. I did make some changes on boot options, saved and exited bios. I was able to loging WindowsXP and run LabView.
After turning off the unit, unplug power cable. I removed the PXI-8184 to check on its battery. I found its bios battery voltage is 0 (technically no charge). I got a new battery (3V) and plugged into the system.
Once the power is turned on, there is nothing showing on screen, only black screen. The power LED is ON, LED lights for ethernet cable are ON (one is solid, one is blinking), the Drive LED is off (the hard drive is not even accessed). I checked the hard drive with my external encloser, it seems everything is ok. I can read files from hard drive from my laptop through an external encloser.
I suspect there is something wrong with BIOS. I did reset BIOS by moving jumper to a new location and setting it back to its original place.
The screen shows nothing on bootup, I think the bios is not even loaded.
Any help/inputs to help me to solve this problem would be helpful. Thanks for your replies and inputs.
PS: The Switch Configuration at the moment is Switch1 is ON position (Boot LabView RT) and other switches are in OFF positions

Yes. That was the only change. With the old battery (zero charge voltage), same behavior with black screen.
I am not sure whether or not the last bios save did have affect on bios firmware (may some corrected parts of firmware ? )
Thanks for your reply.

Scan order and empty channels for SCXI-1102

Hello-
Sorry for the cross-board re-post, but I really need to get this answered asap.
I have two SCXI-1102 cards in my chassis, all measurements will be routed to ch0 of the PXI-6229 that is also in the chassis. For design reasons, I prefer to use about 2/3 of each 1102, and thus leaving about 1/3 of each 1102 empty.
Should I populate the channels in any particular order? Eg should I start at ch0 or ch31, and which direction is the scan order? e.g. 1102a/ch0 -> 1102a/ch15 and then 1102b/ch0 -> 1102b/ch15 OR say 1102a/ch15 -> 1102/ch0 and then 1102b/ch15 -> 1102b/ch0
Does this matter AT ALL with a PXI/SCXI system? I know with many DAQ devices (E-series for example) you must scan in descending order (eg. 7,6,5...0) so it makes more sense to start populating the last channel first and then leave the lower-numbers empty.
thanks-
brad

Please see this post.
Regards,
Natasa

DAQmx Error 88709

I'm running TestStand in conjunction with LabVIEW on a PXI/SCXI system. I experience DAQmx Error 88709 only when running my TestStand sequence file the first time after all equipment has been powered down. For all subsequent executions of the TestStand sequence file, I don't experience the error (everything runs fine). I can reboot the controller and I don't get the error. I only get the error after a complete power-down (all PXI and SCXI equipment).
In my attachment, the VI that causes the error is Output_Drive.vi. In this VI, I'm acquiring data from two PXI-5114 Digitizers. When the error occurs, data from the first digitizer is displayed on the front panel graph, but before the data from the second digitizer is displayed, the error occurs. Data from the second digitizer is coming from a PXI-6711 Analog Out card.
In my attachment, Error Report.bmp shows the error report that I get.
Any ideas will be greatly appreciated.
Attachments:
DAQmx Error 88709.zip ‏225 KB

Hello,
Do you get this error if you just run the VI in LabVIEW and not in TestStand?
Best Regards,
Adam G
National Instruments
Applications Engineer

Unstable PXI/SCXI system

Similar Messages

Maybe you are looking for