NativeProcess and cmd loop

Hello,
cmd loop doesn't work correctly
file = file.resolvePath("C:\\Windows\\System32\\cmd.exe");
nativeProcessStartupInfo.executable = file;
process.addEventListener(ProgressEvent.STANDARD_OUTPUT_DATA, onOutputData);
process.addEventListener(ProgressEvent.STANDARD_ERROR_DATA, onError);
process.addEventListener(NativeProcessExitEvent.EXIT, exitHandler);
process.start(nativeProcessStartupInfo);
process.standardInput.writeUTFBytes('for /f "TOKENS=1" %%i in (\'"wmic Process where (Name="cmd.exe") GET processid | findstr [0-9]"\') do call :concat %%i' + "\n");
process.standardInput.writeUTFBytes('goto :fin' + "\n");
process.standardInput.writeUTFBytes(':concat' + "\n");
process.standardInput.writeUTFBytes('set str=%str%,%1' + "\n");
process.standardInput.writeUTFBytes('goto :eof' + "\n");
process.standardInput.writeUTFBytes(':fin' + "\n");
process.standardInput.writeUTFBytes('@echo pid%str%' + "\n");
public function onOutputData(event:ProgressEvent):void
var stdOut:IDataInput = process.standardOutput;
var data:String = stdOut.readUTFBytes(process.standardOutput.bytesAvailable);
are.appendText(data+"\n");
the cmd echo returns "pid%str%,%1"
Thanks

HI,
if your to internal table satisfy the bellow requirements
To use this following should be true
1)      Both tables should be sorted with the same key ( in the above case field1 and field2 )
2)      The mapping between primary to secondary tables should be
a.       one to many ( for one record in primary there are multiple records in secondary )
b.      one to one (for one record in primary there is only one in secondary )
Please note that other than the above 2 other 2 scenarios (many to many & many to one) will not work with the above logic and make sure you donu2019t use in such case.
3)      The secondary table should not contain a record which does not map to the primary table ( this will not happen if the secondary is fetched using for all entries from primary )
4)      Please make sure you do not delete any record from primary before using the logic which will make the point 3 false 
5)      If you were to use a 'AND' in where statement of the inner loop you should use or in the inner loop if condition in the above logic. 
then you can use the
Loop AT i_primary into wa_primary.
Loop AT i_secondary into wa_secondary from lv_index.
If ( wa_primary-field1 NE wa_secondary-field1 ) or
( wa_primary-field2 NE wa_secondary-field2 ).
Lv_index = sy-tabix.
Endif.
u201C your code comes here u201C
Endloop.
Endloop.
which is very fast i have check it in most of the reports gave performance issues
you can check the link for detail
[http://nafran.blogspot.com/2009/09/when-and-where-we-can-use-parallel.html|http://nafran.blogspot.com/2009/09/when-and-where-we-can-use-parallel.html]
[ http://nafran.blogspot.com/2009/05/best-way-to-code-nested-loops-sap.html|http://nafran.blogspot.com/2009/05/best-way-to-code-nested-loops-sap.html]

Similar Messages

  • Random iPhone crashes and reboot loop after iOS 7 upgrade

    Hi all
    Since I upgraded my iPhone to iOS 7, I suffer from random crashes/resets, where my iPhone reboots and enters a reboot loop (Apple logo, black screen, reboot, Apple logo, black screen, reboot, etc) that I can only exit by restoring the device (resetting doesn't help).
    Some more information
    a) The device: iPhone 4, 32 GB, has never been jailbroken, and has never shown any similar issues before.
    b) The crashes/reboots: I haven't been able yet to find a pattern when and why they happen. I had reboots when searching for an app, when pluging in the wall charger, when entering the access code, and even when doing nothing at all (iPhone in my pocket). The only constant is the reboot loop after the crash.
    c) What I tried so far: I restored the device several times, using normal restore (with the iTunes logo) and DFU mode (black screen). After that, I recovered from a recent backup (takes some hours), and everything is ok again - for some hours, until the next crash and reboot loop. I also set up the device as a new phone, and there it seems stable, so I exclude a hardware issue. I tried quite a few of the advices that I found when googling for reboot loops: reset all settings (this led to an another immediate crash and reboot loop), disable app background refresh, etc.
    I've been using this device for my daily business. With the current instability (and the couple of hours it takes to bring it back to life again), it became more or less useless. I wish I could downgrade again (I know that I can't). My assumption is that either iOS 7, or some incompatible app or some corrupt setting is causing this situation. But I don't know how to proceed to isolate and eliminate the issue. I really would like to avoid setting up everything from scratch again.
    Any advice is greatly appreciated!

    All,
    First of all, sorry for my half-finished post above. While typing, I was interrupted, and by reflex I hit CMD-S. Unfortunately, the stupid interface of Apple's support website interpreted that as a submit command. I tried to complete my text with the update function, but when finally hitting the submit button, I got an error message, and all my updated text was gone... No way to bring it back, and also no way to delete the half-baked posting. Quite frustrating.
    Now, to complete what I started above:
    In my case, the problem definitely had something to do with the springboard process (an iOS system 'app' that manages the iOS homescreens) and the watchdog process (another iOS system 'app' that monitors certain things on your phone and that can initiate a restart when it thinks the phone is frozen). In the folder '/Users/<your account>/Library/Logs/CrashReporter/MobileDevice/<your phone>' I could see what caused my crashes; they were all 'stack+SpringBoard' and the reason in these crash log files was 'Watchdog timeout'.
    The following two forum posts helped me:
    https://discussions.apple.com/thread/1676330?start=30&tstart=0
    https://discussions.apple.com/message/20794982#20794982
    I'm quite sure that my issues had to do with the 'application map' that is mentioned in the above posts. So far, Ive been thinking that it was just too large (as in the case of Andi1996 [second link above]), but jmbladen's observation seems not to support this. So, the absolute number might not the source of the problem, but I still assume that something went wrong with my application map during the upgrade from iOS6 to iOS7. I remember having stability problems before, as soon as all my 10 home screens were full of apps and newly downloaded apps would generate additional pages (only visible via iTunes). Considering that there are some fundamental changes to how we can organize apps within folders in iOS 7, it can well be that the springboard process just wasn't able to cope with my application map correctly within the 120 seconds before the watchdog process restarts the phone. My massive cleanup action must have fixed this somehow.
    @jmbladen: I'm only using iCloud for the 'find my phone' functionality, so all the backup & recovery was done via iTunes from my local harddisk. And there was no temporal pattern for my crashes before. You might suffer from the same symptoms, but probably not because of the same cause.
    My advice for anyone affected by random crashes and a reboot loop is to check out the directory with the CrashReporter logs mentioned above to find out what app or process causes the crash. If it's the springboard and watchdog problem, then you should try to clean up your home screens (from iTunes). Maybe the absolute number of apps is not that important, but make sure that you reduce the number of screens. And then sync and backup before you start using the phone again. In my case it helped.
    Hope this helps someone else too.
    P.S. Once you know the right keywords to search for, you find forum postings back to 2008 / iOS 2 describing exactly the same problem. This reboot loop is a very nasty issue, and it is hard to understand that Apple still hasn't been able to address this, or at least provide some better help on how to get out of it again.

  • Constant Program Crashes and Random/Loop Restarts

    Since the Mountain Lion update, my computer has been restarting randomly and occasionally loops during restarts.  I have to force it to shut down and then give it a few seconds and then allow it to start--and again, it may result in loop restarts.  Everything boots fine in safe mode and once I get it to start normally, everything usually is okay...at least for a while.  Also, more programs have been crashing than normal.  Here is a copy/paste of one of the more recent ones.
    Can someone PLEASE help me?
    Process:    
    java [337]
    Path:       
    /usr/bin/java
    Identifier: 
    com.apple.javajdk16.cmd
    Version:    
    1.0 (1.0)
    Code Type:  
    X86-64 (Native)
    Parent Process:  ??? [1]
    User ID:    
    501
    Date/Time:  
    2012-10-15 21:56:59.643 -0400
    OS Version: 
    Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Interval Since Last Report:     
    114400 sec
    Crashes Since Last Report:      
    32
    Per-App Interval Since Last Report:  8540 sec
    Per-App Crashes Since Last Report:   2
    Anonymous UUID:                 
    8DE55E1B-94E3-E817-34DE-B7465084C894
    Crashed Thread:  9  Java: VM Thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000408e290e8
    VM Regions Near 0x408e290e8:
    CG backing stores 
    00000001c7079000-00000001c7223000 [ 1704K] rw-/rw- SM=SHM 
    -->
    Java              
    000000077ae00000-000000078ae00000 [256.0M] rw-/rwx SM=PRV 
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   com.apple.CoreFoundation 
    0x00000001016b6803 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation 
    0x00000001016bbee6 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation 
    0x00000001016bb6b2 CFRunLoopRunSpecific + 290
    5   com.apple.HIToolbox      
    0x00000001061030a4 RunCurrentEventLoopInMode + 209
    6   com.apple.HIToolbox      
    0x0000000106102e42 ReceiveNextEventCommon + 356
    7   com.apple.HIToolbox      
    0x0000000106102cd3 BlockUntilNextEventMatchingListInMode + 62
    8   com.apple.AppKit         
    0x00000001047b8613 _DPSNextEvent + 685
    9   com.apple.AppKit         
    0x00000001047b7ed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
    10  libawt.jnilib            
    0x0000000113c7cfe3 -[NSApplicationAWT nextEventMatchingMask:untilDate:inMode:dequeue:] + 124
    11  com.apple.AppKit         
    0x00000001047af283 -[NSApplication run] + 517
    12  libawt.jnilib            
    0x0000000113c7b694 +[AWTStarter startAWT:] + 1495
    13  libawt.jnilib            
    0x0000000113c7b00e -[CPerformer perform] + 93
    14  com.apple.Foundation     
    0x0000000101a61677 __NSThreadPerformPerform + 225
    15  com.apple.CoreFoundation 
    0x0000000101699101 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
    16  com.apple.CoreFoundation 
    0x0000000101698a25 __CFRunLoopDoSources0 + 245
    17  com.apple.CoreFoundation 
    0x00000001016bbdc5 __CFRunLoopRun + 789
    18  com.apple.CoreFoundation 
    0x00000001016bb6b2 CFRunLoopRunSpecific + 290
    19  java                     
    0x000000010165f843 0x10165b000 + 18499
    20  java                     
    0x000000010165f29a 0x10165b000 + 17050
    21  java                     
    0x000000010165ca98 0x10165b000 + 6808
    Thread 1:
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de660e 0x103dd3000 + 79374
    7   libclient64.dylib        
    0x0000000103e8d1dc 0x103dd3000 + 762332
    8   libclient64.dylib        
    0x0000000103e8cd3f 0x103dd3000 + 761151
    9   java                     
    0x000000010165e286 0x10165b000 + 12934
    10  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    11  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 2:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib   
    0x0000000102417d16 kevent + 10
    1   libdispatch.dylib        
    0x0000000102206dea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib        
    0x00000001022069ee _dispatch_mgr_thread + 54
    Thread 3:: Java: Exception Handler Thread
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libsystem_kernel.dylib   
    0x000000010241550c mach_msg_server + 552
    3   libclient64.dylib        
    0x0000000103de73c9 0x103dd3000 + 82889
    4   libclient64.dylib        
    0x0000000103de738b 0x103dd3000 + 82827
    5   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    6   libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    7   libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 4:: Java: Gang worker#0 (Parallel GC Threads)
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de668f 0x103dd3000 + 79503
    7   libclient64.dylib        
    0x0000000104249cbe 0x103dd3000 + 4680894
    8   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    9   libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    10  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 5:: Java: Gang worker#1 (Parallel GC Threads)
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de668f 0x103dd3000 + 79503
    7   libclient64.dylib        
    0x0000000104249cbe 0x103dd3000 + 4680894
    8   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    9   libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    10  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 6:: Java: Gang worker#2 (Parallel GC Threads)
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de668f 0x103dd3000 + 79503
    7   libclient64.dylib        
    0x0000000104249cbe 0x103dd3000 + 4680894
    8   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    9   libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    10  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 7:: Java: Gang worker#3 (Parallel GC Threads)
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de668f 0x103dd3000 + 79503
    7   libclient64.dylib        
    0x0000000104249cbe 0x103dd3000 + 4680894
    8   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    9   libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    10  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 8:: Java: Concurrent Mark-Sweep GC Thread
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e92541 0x103dd3000 + 783681
    3   libclient64.dylib        
    0x0000000103ea7d96 0x103dd3000 + 871830
    4   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    5   libclient64.dylib        
    0x0000000103de668f 0x103dd3000 + 79503
    6   libclient64.dylib        
    0x00000001040d4773 0x103dd3000 + 3151731
    7   libclient64.dylib        
    0x00000001040d4a11 0x103dd3000 + 3152401
    8   libclient64.dylib        
    0x00000001040d4601 0x103dd3000 + 3151361
    9   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    10  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    11  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 9 Crashed:: Java: VM Thread
    0   libclient64.dylib        
    0x000000010421b5e6 0x103dd3000 + 4490726
    1   libclient64.dylib        
    0x00000001040dd106 0x103dd3000 + 3186950
    2   libclient64.dylib        
    0x000000010410c828 0x103dd3000 + 3381288
    3   libclient64.dylib        
    0x00000001041faefc 0x103dd3000 + 4357884
    4   libclient64.dylib        
    0x0000000103faa5d0 0x103dd3000 + 1930704
    5   libclient64.dylib        
    0x000000010420d389 0x103dd3000 + 4432777
    6   libclient64.dylib        
    0x000000010420d5c4 0x103dd3000 + 4433348
    7   libclient64.dylib        
    0x00000001041fc1aa 0x103dd3000 + 4362666
    8   libclient64.dylib        
    0x000000010410e739 0x103dd3000 + 3389241
    9   libclient64.dylib        
    0x00000001040af37f 0x103dd3000 + 2999167
    10  libclient64.dylib        
    0x0000000104247b10 0x103dd3000 + 4672272
    11  libclient64.dylib        
    0x0000000103f6bb25 0x103dd3000 + 1674021
    12  libclient64.dylib        
    0x0000000103f6ba39 0x103dd3000 + 1673785
    13  libclient64.dylib        
    0x0000000103e68f15 0x103dd3000 + 614165
    14  libclient64.dylib        
    0x0000000103e68b0b 0x103dd3000 + 613131
    15  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    16  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    17  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 10:: Java: Reference Handler
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103ea8183 0x103dd3000 + 872835
    5   libclient64.dylib        
    0x0000000103ea7ed4 0x103dd3000 + 872148
    6   libclient64.dylib        
    0x0000000103e76488 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib      
    0x00000001044d3b0b JVM_MonitorWait + 59
    8   ???                      
    0x0000000109fa3eee 0 + 4462362350
    9   ???                      
    0x0000000109f9885a 0 + 4462315610
    10  ???                      
    0x0000000109f9885a 0 + 4462315610
    11  ???                      
    0x0000000109f93438 0 + 4462294072
    12  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    13  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    14  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    15  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    16  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    17  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    18  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    19  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    20  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 11:: Java: Finalizer
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103ea8183 0x103dd3000 + 872835
    5   libclient64.dylib        
    0x0000000103ea7ed4 0x103dd3000 + 872148
    6   libclient64.dylib        
    0x0000000103e76488 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib      
    0x00000001044d3b0b JVM_MonitorWait + 59
    8   ???                      
    0x0000000109fa3eee 0 + 4462362350
    9   ???                      
    0x0000000109f9885a 0 + 4462315610
    10  ???                      
    0x0000000109f989b3 0 + 4462315955
    11  ???                      
    0x0000000109f989b3 0 + 4462315955
    12  ???                      
    0x0000000109f93438 0 + 4462294072
    13  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    14  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    15  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    16  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    17  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    18  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    19  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    20  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    21  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 12:: Java: Surrogate Locker Thread (Concurrent GC)
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de65f6 0x103dd3000 + 79350
    7   libclient64.dylib        
    0x00000001040bc5cd 0x103dd3000 + 3053005
    8   libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    9   libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    10  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    11  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    12  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 13:: Java: Signal Dispatcher
    0   libsystem_kernel.dylib   
    0x00000001024156c2 semaphore_wait_trap + 10
    1   libclient64.dylib        
    0x0000000103e8641b 0x103dd3000 + 734235
    2   libclient64.dylib        
    0x0000000103e85eea 0x103dd3000 + 732906
    3   libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    4   libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    5   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    6   libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    7   libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 14:: Java: C2 CompilerThread0
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de65f6 0x103dd3000 + 79350
    7   libclient64.dylib        
    0x0000000103e8c409 0x103dd3000 + 758793
    8   libclient64.dylib        
    0x0000000103e87267 0x103dd3000 + 737895
    9   libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    10  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    11  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    12  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    13  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 15:: Java: C2 CompilerThread1
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de65f6 0x103dd3000 + 79350
    7   libclient64.dylib        
    0x0000000103e8c409 0x103dd3000 + 758793
    8   libclient64.dylib        
    0x0000000103e87267 0x103dd3000 + 737895
    9   libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    10  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    11  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    12  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    13  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 16:: Java: Low Memory Detector
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de668f 0x103dd3000 + 79503
    7   libclient64.dylib        
    0x0000000103e89bfe 0x103dd3000 + 748542
    8   libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    9   libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    10  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    11  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    12  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 17:: Java: VM Periodic Task Thread
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e92541 0x103dd3000 + 783681
    3   libclient64.dylib        
    0x0000000103ea7d96 0x103dd3000 + 871830
    4   libclient64.dylib        
    0x0000000103e8b7d2 0x103dd3000 + 755666
    5   libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    6   libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    7   libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 18:: Java: AWT-Shutdown
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103ea8183 0x103dd3000 + 872835
    5   libclient64.dylib        
    0x0000000103ea7ed4 0x103dd3000 + 872148
    6   libclient64.dylib        
    0x0000000103e76488 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib      
    0x00000001044d3b0b JVM_MonitorWait + 59
    8   ???                      
    0x0000000109fa3eee 0 + 4462362350
    9   ???                      
    0x0000000109f9885a 0 + 4462315610
    10  ???                      
    0x0000000109f9885a 0 + 4462315610
    11  ???                      
    0x0000000109f98d34 0 + 4462316852
    12  ???                      
    0x0000000109f93438 0 + 4462294072
    13  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    14  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    15  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    16  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    17  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    18  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    19  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    20  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    21  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 19:: Java: Java2D Disposer
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103ea8183 0x103dd3000 + 872835
    5   libclient64.dylib        
    0x0000000103ea7ed4 0x103dd3000 + 872148
    6   libclient64.dylib        
    0x0000000103e76488 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib      
    0x00000001044d3b0b JVM_MonitorWait + 59
    8   ???                      
    0x0000000109fa3eee 0 + 4462362350
    9   ???                      
    0x0000000109f9885a 0 + 4462315610
    10  ???                      
    0x0000000109f989b3 0 + 4462315955
    11  ???                      
    0x0000000109f989b3 0 + 4462315955
    12  ???                      
    0x0000000109f98d34 0 + 4462316852
    13  ???                      
    0x0000000109f93438 0 + 4462294072
    14  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    15  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    16  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    17  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    18  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    19  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    20  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    21  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    22  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 20:: Java: AWT-EventQueue-0
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103e92369 0x103dd3000 + 783209
    6   libclient64.dylib        
    0x0000000103de65f6 0x103dd3000 + 79350
    7   libclient64.dylib        
    0x0000000103f6b5c8 0x103dd3000 + 1672648
    8   libclient64.dylib        
    0x00000001040af035 0x103dd3000 + 2998325
    9   libclient64.dylib        
    0x0000000103e5ae43 0x103dd3000 + 556611
    10  libclient64.dylib        
    0x0000000103e5acc4 0x103dd3000 + 556228
    11  libclient64.dylib        
    0x0000000103e60356 0x103dd3000 + 578390
    12  libclient64.dylib        
    0x0000000103fae427 0x103dd3000 + 1946663
    13  ???                      
    0x0000000109ff05c9 0 + 4462675401
    Thread 21:: Java: SwingWorker-pool-1-thread-1
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x00000001041f4351 0x103dd3000 + 4330321
    4   libclient64.dylib        
    0x0000000104236368 0x103dd3000 + 4600680
    5   ???                      
    0x0000000109fa3eee 0 + 4462362350
    6   ???                      
    0x0000000109f9885a 0 + 4462315610
    7   ???                      
    0x0000000109f9885a 0 + 4462315610
    8   ???                      
    0x0000000109f98d34 0 + 4462316852
    9   ???                      
    0x0000000109f98e8d 0 + 4462317197
    10  ???                      
    0x0000000109f989b3 0 + 4462315955
    11  ???                      
    0x0000000109f98d34 0 + 4462316852
    12  ???                      
    0x0000000109f93438 0 + 4462294072
    13  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    14  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    15  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    16  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    17  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    18  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    19  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    20  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    21  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 22:: Java: TimerQueue
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103ea8183 0x103dd3000 + 872835
    5   libclient64.dylib        
    0x0000000103ea7ed4 0x103dd3000 + 872148
    6   libclient64.dylib        
    0x0000000103e76488 JVM_MonitorWait + 154
    7   libjvmlinkage.dylib      
    0x00000001044d3b0b JVM_MonitorWait + 59
    8   ???                      
    0x0000000109fa3eee 0 + 4462362350
    9   ???                      
    0x0000000109f9885a 0 + 4462315610
    10  ???                      
    0x0000000109f98d34 0 + 4462316852
    11  ???                      
    0x0000000109f93438 0 + 4462294072
    12  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    13  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    14  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    15  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    16  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    17  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    18  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    19  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    20  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 23:: Java: SwingWorker-pool-1-thread-2
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x00000001041f4351 0x103dd3000 + 4330321
    4   libclient64.dylib        
    0x0000000104236368 0x103dd3000 + 4600680
    5   ???                      
    0x0000000109fa3eee 0 + 4462362350
    6   ???                      
    0x0000000109f9885a 0 + 4462315610
    7   ???                      
    0x0000000109f9885a 0 + 4462315610
    8   ???                      
    0x0000000109f98d34 0 + 4462316852
    9   ???                      
    0x0000000109f98e8d 0 + 4462317197
    10  ???                      
    0x0000000109f989b3 0 + 4462315955
    11  ???                      
    0x0000000109f98d34 0 + 4462316852
    12  ???                      
    0x0000000109f93438 0 + 4462294072
    13  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    14  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    15  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    16  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    17  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    18  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    19  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    20  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    21  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 24:: Java: SwingWorker-pool-1-thread-3
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x00000001041f4351 0x103dd3000 + 4330321
    4   libclient64.dylib        
    0x0000000104236368 0x103dd3000 + 4600680
    5   ???                      
    0x0000000109fa3eee 0 + 4462362350
    6   ???                      
    0x0000000109f9885a 0 + 4462315610
    7   ???                      
    0x0000000109f9885a 0 + 4462315610
    8   ???                      
    0x0000000109f98d34 0 + 4462316852
    9   ???                      
    0x0000000109f98e8d 0 + 4462317197
    10  ???                      
    0x0000000109f989b3 0 + 4462315955
    11  ???                      
    0x0000000109f98d34 0 + 4462316852
    12  ???                      
    0x0000000109f93438 0 + 4462294072
    13  libclient64.dylib        
    0x0000000103e69f8e 0x103dd3000 + 618382
    14  libclient64.dylib        
    0x0000000103e76018 0x103dd3000 + 667672
    15  libclient64.dylib        
    0x0000000103e75f0e 0x103dd3000 + 667406
    16  libclient64.dylib        
    0x0000000103e75eae 0x103dd3000 + 667310
    17  libclient64.dylib        
    0x0000000103e75d50 0x103dd3000 + 666960
    18  libclient64.dylib        
    0x0000000103e75b65 0x103dd3000 + 666469
    19  libclient64.dylib        
    0x0000000103de64fa 0x103dd3000 + 79098
    20  libsystem_c.dylib        
    0x00000001022a3742 _pthread_start + 327
    21  libsystem_c.dylib        
    0x0000000102290181 thread_start + 13
    Thread 25:: Java: Image Animator 3
    0   libsystem_kernel.dylib   
    0x0000000102415686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x0000000102414c42 mach_msg + 70
    2   libclient64.dylib        
    0x0000000103e924af 0x103dd3000 + 783535
    3   libclient64.dylib        
    0x0000000103de6a80 0x103dd3000 + 80512
    4   libclient64.dylib        
    0x0000000103e9245a 0x103dd3000 + 783450
    5   libclient64.dylib        
    0x0000000103de59c5 0x103dd3000 + 76229
    6   libclient64.dylib        
    0x0000000103de5907 0x103dd3000 + 76039
    7   libclient64.dylib        
    0x0000000103f7c9b7 0x103dd3000 + 1743287
    8   libclient64.dylib        
    0x0000000103e452a8 0x103dd3000 + 467624
    9   libclient64.dylib        
    0x0000000103fdbb00 0x103dd3000 + 2132736
    10  libclient64.dylib        
    0x0000000103f89c26 JVM_Sleep + 191
    11  libjvmlinkage.dylib      
    0x00000001044d465e JVM_Sleep + 62
    12  ???                      
    0x0000000109fa3eee 0 + 4462362350
    13  ???                      
    0x0000000109f9885a 0 + 4462315610
    14  ???                      
    0x0000000109f98a82 0 + 4462316162
    15  ???                      

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac. 
    These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing. 
    Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. 
    Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then either copy or drag it. The headings “Step 1” and so on are not part of the commands. 
    Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply. 
    Launch the Terminal application in any of the following ways: 
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.) 
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. 
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid. 
    When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign. 
    Step 1 
    Copy or drag — do not type — the line below into the Terminal window, then press return:
    kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' 
    Post the lines of output (if any) that appear below what you just entered (the text, please, not a screenshot.) You can omit the final line ending in “$”. 
    Step 2 
    Repeat with this line:
    sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|edu\.mit|org\.(amavis|apache|cups|isc|ntp|postfix|x)/{print $3}' 
    This time, you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning. 
    Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step. 
    Step 3
    launchctl list | sed 1d | awk '!/0x|com\.apple|edu\.mit|org\.(x|openbsd)/{print $3}' 
    Step 4
    ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null  
    Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting. 
    Step 5
    osascript -e 'tell application "System Events" to get name of every login item' 2> /dev/null 
    Remember, steps 1-5 are all drag-and-drop or copy-and-paste, whichever you prefer — no typing, except your password. Also remember to post the output. 
    You can then quit Terminal.

  • 7344 servo motion switching between open and closed loop operation

    I have a custom end-of-line test system presently using a 4-axis 7344 servo controller to perform various functional tests on small, brushed DC motors. The system is programmed in C/C++ and uses flex motion functions to control the motor during testing. Motors are coupled to external encoder feedback and third party PWM drives running in closed-loop torque mode from an analog command signal. The system uses all four motion axis channels on the 7344 board to independently and asynchronously test up to four production motors at a time.
    In closed-loop mode, the system runs without issue, satisfying the battery of testing protocols executed by this system. I now have a request to add additional test functionality to the system. This testing must be run in open loop mode. Specifically, I need to use my +/- 10v analog output command to my torque drive to send different DAC output levels to the connected motor.drive while monitoring response.
    I do not believe the flex motion library or 7344 controller includes functions to easily switch between open and closed loop mode without sending a new drive configuration. I am also under the impression that I cannot reconfigure one (or more) servo controller axis channels without disabling the entire drive. As my system runs each axis channel in an asynchronous manner, any requirement to shutdown all drives each time I change modes is an unworkable solution.
    I am open to all ideas that will allow asynchronous operation of my 4 motor testing stations. If the only solution is to add a second 7344 controller and mechanical relays to switch the drive and motor wiring between two separately configured servo channels, so be it. I just want to explore any available avenue before I place a price tag on this new system requirement.
    Bob

    Jochen,
    Thank you for the quick response. The 7344 board does an excellent job running my manufacturing motor assemblies through a custom end-of-line tester in closed loop mode. A portion of the performance history and test result couples the motor through a mechanical load and external shaft. The shaft is in contact with a linear encoder that closes my servo loop.
    My new manufacturing requirement is to also sample/document how the small DC motor behaves in open loop operation. Your solution is exactly what I need to perform the additional functional tests on the product I am manufacturing. I see no reason why this cannot work. I was originally concerned that I would need to reinitialize the 7344 board after changing axis configuration. Initialization is a global event and impacts all four channels on the 7344 board.
    Using flex_config_axis() to change axis configuration on a single channel without disturbing other potentially running axis channels will solve my concern. It will be several weeks before I can return to the manufacturing facility where the 7344-based testing machine is located. I will update this thread once I verify a successful result.
    Bob

  • How to add cursor and for loop

    PROCEDURE "TEST" is
    bala number;
    ins1 number;
    ins2 number;
    BEGIN
    select sum(bal) into bala from (select sum(acp.acp_totbal) bal,acp_instruid from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and c_srm_prncplinsid=acp_instruid
    and acp_acntnum!='SG030001'
    group by acp_instruid
    union
    select sum(acp.acp_totbal) bal,acp_instruid from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and acp_acntnum!='SG030001'
    and acp_instruid=c_srm_prntinsid
    group by acp_instruid)view1;
    dbms_output.put_line(bala);
    select acp_instruid into ins1 from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and c_srm_prncplinsid=acp_instruid
    and acp_acntnum='SG030001';
    dbms_output.put_line('principal'||ins1);
    select acp_instruid into ins2 from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and acp_acntnum='SG030001'
    and acp_instruid=c_srm_prntinsid;
    dbms_output.put_line('parent'||ins2);
    update cs_acpos_bkp
    set acp_totbal=-bala
    where acp_instruid=ins2
    and acp_acntnum='SG030001';
    END;
    i have written this code,i need to use cursor and for loops to get more than one rows and update also.
    if there are more than 1 rows in cs_strmap_t,then the procedure throws an error stating that it cannot take 2 rows.
    Edited by: 850836 on Apr 7, 2011 11:43 PM

    PROCEDURE "TEST" is
    bala number;
    ins1 number;
    ins2 number;
    CURSOR cur_1 IS
    select sum(bal) bala from (select sum(acp.acp_totbal) bal,acp_instruid from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and c_srm_prncplinsid=acp_instruid
    and acp_acntnum='SG030001'
    group by acp_instruid
    union
    select sum(acp.acp_totbal) bal,acp_instruid from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and acp_acntnum='SG030001'
    and acp_instruid=c_srm_prntinsid
    group by acp_instruid)view1;
    BEGIN
    select acp_instruid into ins1 from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and c_srm_prncplinsid=acp_instruid
    and acp_acntnum='SG030001';
    dbms_output.put_line('principal'||ins1);
    select acp_instruid into ins2 from cs_strmap_t map,cs_instru_strips strip,cs_acpos_bkp acp
    where c_int_instruid=c_srm_prncplinsid
    and acp_acntnum='SG030001'
    and acp_instruid=c_srm_prntinsid;
    dbms_output.put_line('parent'||ins2);
    for var_for in cur_1
    loop
    update cs_acpos_bkp
    set acp_totbal=var_for.bala
    where acp_instruid=ins2
    and acp_acntnum='SG030001'
    and abs(acp_totbal)>abs(bala);
    dbms_output.put_line(bala);
    end loop;
    END;
    i wrote the following procedure,but the balance is not getting updated.
    Getting this errors when there are more than 1 row in cs_strmap_t table
    ORA-01422: exact fetch returns more than requested number of rows
    ORA-06512: line 22
    ORA-06512: at line 2

  • MIDI Banks and Apple Loops Trustworthy Downloads?

    I am currently attempting to locate and download MIDI banks and Apple Loops that I can use in the future, but I'm looking for a trustworthy site (a one stop shop if you will) to do this.  If we only have Garageband installed, and not Pro Logic or any other programs, then is Garageband the only program to open up and play around with our MIDI banks or Apple Loops just for fun?  I mean, is there another way we can open our loops simply to play around with and be able to pick out sounds we like, then perhaps save different sounds we like for future reference?  I'm confused on how to actually open the loops and MIDI banks, so I need someone to tell me precisely how to do this if we just want to begin exploring.  Thanks!

    You can open Apple Loops in the Quicktime Player. Many sample producers offer their libraries in Apple Loops format as well as the more traditional standard WAV nowadays, so you should have no trouble finding plenty of resources.
    Quicktime Player will also play GM MIDI files.

  • Itunes wont let me download anything for my ipod touch.  everytime i try to it keeps looping thru to verify my account, so i do and then try to download and it loops me right back thru again to verify my account.  HELP ME PLEASE :(

    everytime i try to it keeps looping thru to verify my account, so i do and then try to download and it loops me right back thru again to verify my account.  HELP ME PLEASE

    Contact iTunes.  Select the appropriate topic of:
    Apple - Support - iTunes

  • How to code a parallel 'for loop' and 'while loop' where the while loop cannot terminate until the for loop has finished?? (queues also present)

    I've attached a sample VI that I just cannot figure out how to get working the way that I want.  I've labeled the some sections with black-on-yellow text boxes for clarity during the description that follows in the next few sentences.  Here's what I want:
    1) overall -- i'm intend for this to be a subVI that will do data acquisition and write the data to a file.  I want it to use a producer/consumer approach.  The producer construct is the 'parallel for loop' that runs an exact number of times depending on user input (which will come from the mainVI that is not included).  For now I've wired a 1-D array w/ 2 elements as a test case.  During the producer loop, the data is acquired and put into a queue to be delt with in the consumer loop (for now, i just add a random number to the queue).
    2) the consumer construct is the 'parallel while loop'.  It will dequeue elements and write them to a file.  I want this to keep running continuously and parallel until two conditions are met.
          i. the for loop has finished execution
          ii. the queue is empty.
       when the conditions are met, the while loop will exit, close the queue, and the subVI will finish. (and return stuff to mainVI that i can deal with on my own)
    Here's the problems.
    1)  in the "parallel for loop" I have a flat sequence structure.. I haven't had time to incorporate some data dependency into these two sequential sections, but basically, I just care that the "inner while loop" condition is met before the data is collected and queued.  I think I can do this on my own, but if you have suggestions, I'm interested.
    2)  I can easily get the outer for and while loops to run sequentially, but I want them to run in parallel.  My reasoning for this is that that I anticipate the two tasks taking very different amounts of time. .. basically, I want the while loop to just keep polling the queue to get everything out of it (or I suppose I could somehow use notifiers - suggestions welcome)...  the thing is, this loop will probably run faster than the for loop, so just checking to see that the queue is empty will not work... I need to meet the additional condition that nothing else will be placed in the queue - and this condition is met when the for loop is complete. basically, I just can't figure out how to do this.
    3) for now, I've placed a simple stop button in the 'parallel while loop', but I must be missing something fundamental here, because the stop button is totally unresponsive.  i.e. - when I press it, it stays depressed, and nothing happens.
    suggestions are totally welcome!
    thanks,
    -Z
    Attachments:
    daq01v1.vi ‏59 KB

    I'd actually like to add a little more, since I thought about it a bit and I'm still not quite certain I understand the sequence of events...
    altenbach wrote:
    zskillz wrote:
    So i read a bit more about the 'dequeue element' function, and as I understand it, since there is no timeout wired to the dequeue element function, it will wait forever, thus the race condition I suggested above can never happen!
    Yes, you got it!
    As I've thought about it a bit more, there's a few things that surprise me... first, the reason the 'dequeue element while loop' errors is not because there's nothing in the queue, it's becaues the queue has been released and it's trying to access that released queue...   However the problem I have is this --- Even though there's no timeout wired to the dequeue element, I still would think that the while loop that contains it would continue to run at whatever pace it wanted -- and as i said before.. most of the time, it would find that there is nothing to dequeue, but once in a while, something is there.  however, it seems that this loop only runs when something has been enqueued.  the reason I say this is illustrated in the next code sample MODv2 that's attached below.  I've added a stop button to the "queue size while loop" so the program runs until that is pressed.  I've also added a simple conditional in the "dequeue while loop"  that generates a random number if it a button is pressed... but this button is totally non-responsive... which means to me that the "dequeue while loop" isn't actually continuously running, but only when an element is added to the queue.  this still seems almost like the 'dequeue while loop" waits for a notifier from the queue telling it to run.  can you explain this to me? because it is different from what I expect to be happening.
    rasputin wrote:
    I tried to open your VIs but it doesn't work. LV
    is launched, the dialog box (new, open, configure...) opens and then...
    nothing. Not even an error message. I guess it isn't a problem of LV
    version or a dialog box would appear saying this. Could you, please,
    send a image of the code?
    Thanks,
    Hi Rasputin, I'm using LV8.  I assume that was your problem, but who knows.  I've attached a pic of of altenbach's solution since it's what I needed.
    thanks
    -Z
    Message Edited by zskillz on 10-20-2006 11:49 AM
    Attachments:
    daq01v1MODv2.vi ‏63 KB
    daq01v1MODpic.JPG ‏116 KB

  • How to use Fuzzy Logic Controller for transfer function in labview control and simulation loop?

    I am facing problem with fuzzy PD logic controller for transfer function in control and simulation loop.
    Plz Help me in this regard...................
    i have attache snapshot of my program
    Attachments:
    fuzzy in simulation loop.JPG ‏52 KB

    Hi Sankhadip,
    Sorry for the late response. I was looking at your code and
    I noticed that the graph scale does not start from zero. That might be the
    reason why you don't see the transient in the simulation. To change the scales
    simply double click on the lower limit and set it to zero. If this is not the
    expected results, can you please post the expected results, so we can see what are the
    differences between the results . Also, you might be using different
    solvers, and that gives different results as well.    
    Thanks and have a great day.
    Esmail Hamdan | Applications Engineering | National
    Instruments

  • Master and Slave Loops

    I'm having problems with my Master and slave loop combination.  I would like to be able to start and stop acquiring data from individual thermocouples. Please help.
    Message Edited by nicholas03 on 04-13-2008 03:22 PM
    Attachments:
    eight thermo.JPG ‏106 KB

    Dear Nicholas,
    My first advise would be to check the examples on master-slave patterns, and run them step by step, looking at what the data does...
    In a master-slave system, you use the queue to pass data from the master to the slave.   You're not passing data in the queue... in stead, you're passing data using local variables, which you should NOT do...  
    In the top loops, you should attach the temp array to the enqueue element.   In the bottom loop, you should remove the temp local, and instead get your data from the dequeue vi.
    Also, you have to create a queue with the proper variable.   You can create a queue from any variable type, but it has to know beforehand, and the init vi.  
    Assuming you want to queue the temp array, you're basic structure should look like this:
    It does help if you add your own code, so we can easier edit it for you...  Otherwise we need to use photoshop on your design...
    Message Edited by Anthony de Vries on 04-14-2008 11:30 AM
    Attachments:
    master-slave1.JPG ‏24 KB

  • Cmd-+ and cmd-x not working

    Hi,
    I can't get ANY commands working that consist of a + or - sign.
    I have tried to reassign cmd-+ and cmd-- to zoom in and out but the commands doesn't work in the editor.
    When going into the command preferences I can clearly see that cmd-+ and cmd-- gets correctly detected when pressing them.
    Any advice would be kindly appreciated.
    /K

    You are puzzled by an operating system problem.
    I guess that you will get more accurate answers in the forum dedicated to this one.
    https://discussions.apple.com/community/mac_os/mac_os_x_v10.6_snow_leopard
    As far as I remember, the shortcut to insert a newline in a table's cell isn't
    alt + down_arrow but alt + return
    Oops, I read too fast and confound newline and new line.
    I applied the combo updater 10.6.8 and every shortcuts behave flawlessly.
    Yvan KOENIG (VALLAURIS, France) lundi 11 juillet 2011 15:50:12
    iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8
    Please : Search for questions similar to your own before submitting them to the community
    To be the AW6 successor, iWork MUST integrate a TRUE DB, not a list organizer !

  • What are:  LiveType Media 1 & 2 - And Apple Loops?

    Hello Hello
    I just bought and installed the 'FCE HD Version 3.5' Upgrade - looks nice
    Apple bundled with it, 'LiveType Media 1 & 2' - And 'Apple Loops'.
    Before I install these programs, can you guys give me a brief description of what these programs do you for?
    Why do I ask?
    Well, I already have Sound Studio 2.2.4, and iLife 6. I just didn't want to install these new programs until I can find out if they're really worth it?
    I guess the 'Apple Loops' will add some addtional sound effects to my Garage Band Sound Effects Library?
    Thank you my friends
    Mike

    Hi Tom
    Thanx so much for replying to my questions
    Yes I see what happened - I 'UNCHECKED' those applications when I installed FCE HD, because I wanted to ask you guys about it's usefulness first. So I'd have to go back and re-insert the install disc to install them. But that's ok..
    Tom - could you please tell me a little more about what 'Sond Track' offers?
    I mean, can you do the same things that you can do in Garage Band?
    EQ, Effects, Presets etc... ?
    And are there any cool sound effects on that Apple LOOP Disc? Like the ones that Garage Band gives you?
    Thanx Tom
    Mike

  • Best way to capture data every 5 ms (milli-seconds) in the .vi diagram when using "Time between Points, and Small Loop Delay tools" ?

    - Using LabView version 6.1, is there anyway to change the "Time Between Points" indicator of (HH.MM.SS) to only (mm.ss), or to perhaps only (.ss) ?
    - Need to set the data sampling rate to capture every 5 milliseconds, but the defaults is always to 20 or greater; even when the "Small Loop Delay" variable is adjusted down. 
    Thank you in advance.

    I have no idea what "Time between Points, and Small Loop Delay tools" is. If this is some code you downloaded, you should provide a linke to it. And, if you want to acquire analog data every 5 milliseconds from a DAQ board, that is possible with just about every DAQ board and is not related to the version of LabVIEW. You simply have to set the sample rate of the DAQ board to 200 samples/sec. If it's digital data, then there will be a problem getting consistent 5 msec data.

  • Interrupt process and Debug loop

    Hi,
    What is the difference between Interrupt process and Debug Loop in the process chain if both are used to delay the a process
    Thanks
    krish

    hi,
    Interrupt is a process type which is used in the process chains to trigger the chain after completion of specific steps in another process chains or to pass the process chain up to specified certain time is reached based on the requirement.
    Debug loop can be used to debug a process chain,you will have to specify here the gap between one event been triggered and the next subsequent process also you have to Enter a wait time
    regards
    laksh

  • Garageband Instruments and Apple Loops 1.0 update keeps repeating

    I have OSX Yosemite 10.10.2 and Garageband 10.0.3. The auto update for Instruments and Apple Loops 1.0 appears and runs as an available update on a daily basis despite the fact that it has previously updated Garageband. Help please.

    Paul,
    I think what is happening is, that the update you are trying to install is meant for the new Mavericks compatable version of GarageBand - GarageBand 10.0. When the download finishes, it cannot be installed properly, because GarageBand 10.0 is not present. With GB 10 installed, these instruments download with no problem on my mac.
    GB 10.0 is free on Mavericks - so, honestly, download and install GB 10.0 in addition to your current version. Let it download and install additional instruments and loops, launch it once to let it rebuild the loop index, then ignore it. The application does not need much space, and perhaps you may want to use occasionally the automatic drummer or the Arpeggiator. Before downloading GB10.0, make a backup copy of GB '09, just in case the installer should try to overwrite it.
    After GB 10 installed the additional instruments, search for all places with installed loops in the system library and rebuild your loop index.
    Rebuilding the Loop Index in GarageBand
    http://support.apple.com/kb/HT1045

Maybe you are looking for

  • The AdfFacesFilter has not been installed ???

    When i let my program on idle for a little while it sometimes gives this error First what is the ADFFacesFilter??? Second do i really have to install this for proper execution? and when in production will this be recreated by the way i am using jdev

  • Software could not be verfied

    I have just downloaded Lion from the apple store having previously paid and installed it on  another macbook.  However, when I try to install I get a message telling me that the software can not be verified because it has been corrupted or tampered w

  • Disable Vertex Tax Jurisdiction Code Validation & RFC Call

    We want to disable calling vertex for tax jurisdiction code in some cases based on sales org & division.  For a small business unit we are using SAP ECC 5.0 SD module to create customers & sales orders.  These orders are placed via a external non-SAP

  • Hard crash of LR3 when printing

    I suspect I know the answer but I'm posting anyways. LR3 - clean new database Trying to print to a HP616 (5x7 printer) Works like a dream under LR2 and still does LR3 will crash and burn every single time it spools off the printer. My suspect other t

  • Variants missing error in RSTRANSP

    Hi All, I want to transport eight screen variants of the program 'RSUSR070' to another system. SAP&_AUTH SAP&_BENU SAP&_CHANGE SAP&_MINI SAP&_PROFIL SAP&_STANDARD SAP&_TRANSAKT SAP&_VALUES I ran RSTRANSP but it could not find any variants and threw t