Multi-Mainframe with VXI-MXI-2 on VxWorks problem

I have two VXI Mainframes and use two VXI-MXI-2 boards connected. My OS is VxWorks 5.5 running in VXIpc874B. After running resman, it must show borads in two mainframes. but it usually show boards in first mainframe. I try to run resman several times. Sometimes,  the boards of second mainframe apear again. When the boards of second mainframe disapear, the second VXI-MAI-2 disapear too.
How do I configure my system?

MyController(VXIpc874) is in Mainframe 1 and LA is 0
        1st VXI-MXI-2 in Mainframe 1      2ed VXI-MXI-2 in Mainframe 2
LA      1                                                128
S2     Off                                              Off                                        50 Terminal for External Trigger Input
S3     Out                                             Out                                       SMB CLK10 Direction
S4     Off                                               Off                                        20 Terminal for SMB CLK10
S5     Inverted                                       Inverted                                SMB CLK10 Output Polarity
S7    Drive CLK10 out MXIbus             Receive CLK10 from MXIbus
S8     No                                              No                                        VXI-MXI to left
S9     No                                              No                                        VXI-MXI to right
W2    Auto                                           Auto
W3    From onboard oscillator            From MXIbus
U35 - 1   Yes                                       Yes                                       Terminal MXIbus
U35 - 2   Yes                                       Yes                                       Automatic MXIbus Terminal
U35 - 3    No                                        No                                        Change Factory Configuration
U35 - 4    No                                       No                                         Restore Factory Configuration
I referance these configure from the VXI-MXI-2 User Manual. I am not sure if lost some setting.
Another question. Is any sequence to power on the mainframe? Does first mainframe need to power on first or second one? Or never mind this.
Thanks if anyone can check my problem.

Similar Messages

  • Can't see boards in a VXI chassis connected via VXI-MXI-2 cards using a GPIB-USB adapter

    I'm working on a system that has two VXI enclosures, and the two are bridged via VXI-MXI-2 boards in each of them.  The first one has a GPIB-VXI board in slot 0, and I have a Winodows XP computer connected to that with a GPIB-USB-HS adapter.  The problem is that I cannot see any of the boards in the second chassis over GPIB in the Measurement & Automation Explorer.  As far as I can tell, everything is configured correctly; the VXI-MXI-2 board in the first chassis is in the last slot and has a logical address of 126, and the VXI-MXI-2 board in the second chassis is in slot 0 and has a logical address of 127.  To make things even more confusing, if I put a VXI PC in slot 0 of the first chassis, it seems to see everything without any problems.  Do you have any idea why this might be happening?  I'm pretty new to working with these systems, so I might be missing something obvious.  Thanks in advance.

    Nevermind that -- I just discovered that you can't bridge two VXI chassis with VXI-MXI-2 boards if you're using a GPIB-VXI board as the controller.  So, I'll just have to find another way to accomplish what I need to do.

  • VXI-MXI-2 missing in resource manager

    Hello,
    I have a VXI-MXI-2 and I configure the A16 write posting to enable. After that i can not work with VXI-MXI-2.
    When resman run, it found a instrument at address 1 but got a Generic I/O error on VXI D16 peek.
    I try to set all jump status to default and set the U35 Restore Factory Configuration to Yes. it is the same.
    How do i fix this problem?

    My Friend.
                I understood your frustration totally. I got the same problem. There is not much you can do about it. Probably you won’t like my solution either. It is very painful experiences. Are you ready? Here is the solution.
                            Reinstall all of your software.
                            Yes, Reinstall it. The whole thing, LabVIEW, Drivers, and etc. But you must uninstall first.
                            If it does not work, change the computer.
                            The system should run and found the device. It may takes you a couple of days to do it. But it should work.
                            I ran into this issue a few times. Every time I end it up uninstall and reinstall every thing. And it runs without any problems.

  • Should VXI-MXI-2 work with an old Colorado Data Systems 73A-021 Mainframe (card rack)

    I am attempting to use an old CDS 73A-021 Mainframe with a VXI-MXI-2 card.  The host is Windows XP with a PCI-MXI-2.  Resman runs fine, but when I look at the configuration in MAX the frame and the VXI-MXI-2 does not show up.  (See attached image).  I have tried removing all other cards from the VXI Rack, but no effect.
    On systems that do work I see a frame as the child of the MXI-2 bus 0 and the VXI-MXI-2 card as slot 0 child of the frame.  As shown in the attachment I thnk Max is only seeing the PC card and the cable.  If I run resman when the vxi cage is turned off, I see the same results.
    Attachments:
    vxi-mxi-2.pdf ‏85 KB

    Hi JeffERobertson,
    To eliminate the chassis as the potential culprit I would check a working module in the questionable system.  You've said your CDS 73A-021 doesn't work in another system so the module itself could also just be broken.  Another thing to consider would be the slots that you are using.  It would also be worthwhile to try multiple slots.  Post back if you have any more questions.
    Regards,
    Dustin D

  • NI MAX 4.1.0.3001 looses trigger mapping settings for my VXI / MXI2 multi mainframe configurat​ion

    I have NI VXI 3.3.1 and NI VISA 4.0 installed on the system and I am attempting to use a MXI 2 multi mainframe configuration.
    NI MAX sees all the hardware correctly but when I set the MXI-2 Signal Mappings for the TTL Triggers then re-run resman these settings are not retained.  This worked flawlessly in VISA 2.6 (my prior version).
    Specfic config information..
    frame 1 -
    slot 0 MXI2 LA1
    slot 2 1432A LA 66
    Frame 2
    Slot 0 MXI2 LA 129
    Slot 2 1432 LA 133
    NI-VXI version 3.3.1 installed.
    Thank you for any help you can provide!
    Message Edited by Rikh-VXI on 06-12-2008 03:43 PM

    Nicholas_K,
    I understand how to map the trig lines in MAX, and was able to successfully configure these mappings.  The issue is that once configured, I re-run resman and the mappings are then lost, returned to "NONE".  I'm not sure but it appears to be a bug.
    Thank you,
    Rikh

  • Bus Error when accessing A24 space on a VME device with VXI-VISA and VME-MXI-2

    I am trying to access A248 register space on a VME card, but I get a bus error using viIn8 and viOut8 with VXI-VISA on a VXI controller running Win2k across a VXI-MXI-2 <-> VME-MXI-2 link.
    I found the following entry on your site, but I do not if or how it applies to my situation:
    I Cannot Access A24 Space on a VME Bus with a VME-MXI and an AT-MXI-1 on a Windows NT System.
    Product Group: VXI Software
    Product Name: NI-VXI for AT-MXI for Windows NT
    Version/Revision: 1.0
    Problem: With a VME device, bus errors were received when trying to do a VXIin or VXIout to the address in A24 space. The device was successfully edited within the non-VXI device editor portion of VXIedit. Resma
    n acknowledges that the device has a base address of x0000 and has requested 4 MBytes of space in A24 space, but the bus errors were still received.
    Solution: Use VXIedit to insert x4700 into registers A, C, E and 10 of the the VME-MXI. This allows the entire range of VME address spaces (A16, A24 and A32) to be mapped to the MXI bus. You can then access A24 Space.
    Related Links:
    Fixed Version:
    Report Date: 08/01/96
    Last Updated: 07/19/2002
    Document ID: 0O076NGJ

    Hi bnemmers,
    Thank you for contacting National Instruments. First, let me address the KnowledgeBase that you referenced. That KnowledgeBase applies to the VXI-MXI, not the VXI-MXI-2. A similar solution may help, but I will explain that solution last.
    You said that you could not access A24 space on you instrument. Do you have problems accessing A24 space on this particular instrument or on all of your instruments? If you can not access A24 space at all, then there could be a problem with your MXI-2 controller or with its configuration.
    If it is a single instrument that is causing problems, then I suspect there is a problem either with that particular instrument or with the configuration of that particular instrument. If possible, I suggest you test another working instrument in this system. I also suggest you test this instrument in another system that you know is working.
    You mentioned that you are using a VME instrument. If this is the case, then I want to make sure that you have the VME instrument properly configured in Measurement and Automation Explorer. When you add a VME instrument using the "Create new VME Device" option in Measurement and Automation Explorer, you must make sure to add A24 space as a resource in order to communicate in A24 space. When you add this resource, make sure that you select an appropriate range.
    As I mentioned above, it is possible that the MXI-2 interface is not configured properly. It is possible that A24 access is not configured properly and that your device is never even seeing a request to read or write a register. There is a register on the MXI-2 that controls A24 access. This register is called VWR2, Extender A24 Window, and is located at 0xE of the MXI-2's A24/A32 address space. You can read this register using viIn16. If you are using A24 space, then bit 14 should be set to 1 to enable A24 address mapping. Bits 10-8 control the size of the A24 window that is mapped, and bits 7-0 control the base of the A24 window. To make sure that A24 space is enabled and mapped, try writing 0x7800 to this register using viOut16. Assuming that you have opened a VISA session to your VXI-MXI-2 or VME-MXI-2, you would use viOut16(visa session, A24, 0xE, 0x7800). Some of this is explained in the VME-MXI-2 User Manual available at http://digital.ni.com/manuals.nsf/webAdvsearch/68409BFF568BB6118625665F005A0A41?OpenDocument&vid=niwc&node=132100_US.
    I hope this helps. If you are still encountering problems, I suggest you call and talk to an Applications Engineer. Please generate a phone support request at http://www.ni.com/ask. When you do that, you will be given a Service Request Number and a phone number to call. When you call that phone number, you will be routed directly to an Applications Engineer.
    Regards,
    David Shatila
    Applications Engineer
    National Instruments

  • VXI-MXI-2

    I have multi test stations with a PC runing Windows XP, each configured with an NI PCI-MXI-2 Card. Each station has two VXI Chassis, each with it's own Slot-0 controller, daisy-chained to run off the same VXI System, which the system identifies as VXI0.
    When I build a new station, I ghost a Hard Drive from an existing station and use that in the new station. The ghosted drive works fine on the station from which it was created. On a new station with a ghosted drive when I open up MAX, I see two VXI systems listed...VXI0 and VXI1. VXI0 is listed but not recognized (i.e. I can't talk to it). VXI1 appears to be recognized by MAX, but not by NI-VISA. (I can't open up a VISA session from either MAX or VIC).
    I can delete VXI0 and rename VXI1 to VXI0, but VISA still can't talk to it. Also, Resman reports still think the hardware resides on VXI1.
    I get similar problems with NI-GPIB cards. In this case, I believe each PCI GPIB card has it's unique Serial Number encoded in it's ID, so when I move drives from one station to another, I'm able to successfully delete GPIB0 and rename and then used GPIB1 to GPIB0 and all works fine. It appears the same approach does not work on my PCI MXI card.
    Is there something else I need to do to re-identify the newly found VXI1 to VXI0? I have multiple files that expect all my instruments to be located on VXI0.
    Solved!
    Go to Solution.

    Hello TomMcG,
    I believe the issue you are seeing with ghosting a hard drive and moving it to a new station is that it is carrying over the Measurement & Automation Explorer (MAX) configuration with the VXI0 configuration, and the current configuration of the chassis plugged in does not match the previous one from thus it creates a new resource name called VXI1. I would like you to delete VXI1and VXI0 from Measurement & Automation Explorer, and then uninstall the VXI driver for the VXI-MXI 2 from the Device Manager.  This will dissociate the driver from the hardware and not allow you to detect this hardware in MAX. Then when your restart your machine the association will be reinstated and (since there is no VXI0 in MAX) be titles VXI0 in MAX. You can access the device manager via Start>> (Right Click on) Computer and select manage. Then navigate to Device Manager underneath Computer Management>>Systems Tools>>Device Manager. Check to make sure the VXI Bus/devices is there, then right click on the MXI 2 module and click uninstall.  You will have to restart your computer in order for the connection and software to be reinstated. Hopefully this will allow the VXI to re-identify the newly found VXI1 as VXI0. Also when you attempt to use Visa Interactive Control (VIC) does it throw you an error?  
    Regards,
    Izzy O.
    Applications Engineer
    National Instruments 

  • Can not install VXI-MXI-2 driver under Windows XP

    I have a new IBM IntelliStation M Pro PC with Windows XP Pro (but only Service Pack 1) that is having a hard time getting the VXI-MXI-2 PCI driver installed. It reports: "There was a problem installing this hardware: PCI-MXI-2 This device cannot start. (Code 10)".
    Taking a look at some issues raised on the "Troubleshooting PCI-GPIB, PCI-DAQ, PCI-MXI-2, PCI-IMAQ Installation Problems" page, I have dealt with the following:
    1) "PCI Bus Mastering" - originally this was turned off for both PCI slots.  I have turned both slots on, but no change.
    2) PCI slots - I have tried the card in both PCI slots in this machine.
    3) "More that one PCI bridge (very rare)" - my system reports two other PCI bridges: one for the SCSI interface to my hard drive and another for use of the 1394 port. Could this be the issue and what would be needed to fix it?
    Thanks!

    NI-VXI 3.3.1 installs an older version of NI-VISA (2.6, I believe)
    which sometimes has problems with newer systems and results in this
    "Code 10."  Installing the latest version of NI-VISA (currently
    3.5) should fix the problem.
    Robert Mortensen
    Software Engineer
    National Instruments

  • VXI-MXI-2 is not detected in VIC / VISA panel

    Hello,
    I have a VXI work station (VXI-MXI-2)  with Windows XP (PCI-MXI-2). I had installed the nivxi 3.1.1.
    The VXI-MXI-2 card is not detected / showing in the VIC panel. Only the PCI-MXI-2 is detected as VXI0 (PCI-MXI-2).
    No error occoured while running the Resman. It was completed successfully.
    Regards,
    Perumal.V

    My Friend.
                I understood your frustration totally. I got the same problem. There is not much you can do about it. Probably you won’t like my solution either. It is very painful experiences. Are you ready? Here is the solution.
                            Reinstall all of your software.
                            Yes, Reinstall it. The whole thing, LabVIEW, Drivers, and etc. But you must uninstall first.
                            If it does not work, change the computer.
                            The system should run and found the device. It may takes you a couple of days to do it. But it should work.
                            I ran into this issue a few times. Every time I end it up uninstall and reinstall every thing. And it runs without any problems.

  • Install VXI/MXI pn RedHat 5

    I'm trying to install the VXI/MXI drivers on a Red Hat ENterprise Linux 5 box but I'm getting the following errors when I try to compile the driver.
    make -C /lib/modules/2.6.18-371.3.1.el5PAE/build SUBDIRS=/usr/local/nivxi/src KBUILD_VERBOSE=0 modules
    make[1]: Entering directory `/usr/src/kernels/2.6.18-371.3.1.el5-PAE-i686'
      CC [M]  /usr/local/nivxi/src/vxi.o
    In file included from /usr/local/nivxi/src/vxi.c:13:
    /usr/local/nivxi/src/mutex.h:59:42: error: macro "mutex_acquire" requires 4 arguments, but only 1 given
    In file included from /usr/local/nivxi/src/vxi.c:13:
    /usr/local/nivxi/src/mutex.h:59: warning: ‘regparm’ attribute only applies to function types
    /usr/local/nivxi/src/mutex.h:59: warning: ‘cdecl’ attribute only applies to function types
    /usr/local/nivxi/src/mutex.h:61:42: error: macro "mutex_release" requires 3 arguments, but only 1 given
    /usr/local/nivxi/src/mutex.h:61: warning: ‘regparm’ attribute only applies to function types
    /usr/local/nivxi/src/mutex.h:61: warning: ‘cdecl’ attribute only applies to function types
    /usr/local/nivxi/src/vxi.c:128:31: error: macro "mutex_acquire" requires 4 arguments, but only 1 given
    /usr/local/nivxi/src/vxi.c:133:31: error: macro "mutex_release" requires 3 arguments, but only 1 given
    /usr/local/nivxi/src/vxi.c:146:31: error: macro "mutex_acquire" requires 4 arguments, but only 1 given
    /usr/local/nivxi/src/vxi.c:158:31: error: macro "mutex_release" requires 3 arguments, but only 1 given
    make[2]: *** [/usr/local/nivxi/src/vxi.o] Error 1
    make[1]: *** [_module_/usr/local/nivxi/src] Error 2
    make[1]: Leaving directory `/usr/src/kernels/2.6.18-371.3.1.el5-PAE-i686'
    make: *** [default] Error 2
    Any ideas?

    Hi Saldon,
    Thank you for the clarification. So, it looks like Linux kernel version 2.6 is indeed supported by the NI-VXI 2.1.0 driver, but the driver Readme also mentions that the driver has only been tested on Red Hat Enterprise Linux 4. This information is available in the NI-VXI 2.1.0 Readme and the KnowledgeBase article linked below. 
    NI KnowledgeBase Article: Which Linux Kernels Do The Different Versions of NI-VXI for Linux Support?
    Also, I spoke with the R&D Product Engineers for these products and they confirmed this information as well. I believe that there is currently work being done to develop a new NI-VXI version that supports Red Hat Enterprise Linux 6, but there is no date available for the release at this time. I hope this information helps.
    Regards,
    Mike Watts
    Product Marketing - Modular Instruments

  • VI_ERROR_IO while viMOVE operation on VXI-MXI-2

    Hello. We have troubles with our old PCI-MXI-2 & VXI-MXI-2 cards. OS WinXP SP3,  NI-VXI 3.6,  VISA 4.6.2
    Any viMOVEOUT command, issued in A24 adress space, returns VI_ERROR_IO status. I read old posts on this forum and tried to turn off DMA mode for MXI-2. It helps to remove error status but all operations became very slow, inadmissible slow. I'd also tried to switch off SYNC MXI (in regedit set UseSyncMXI=0), but it doesnt solve problem with error status.
    Could you ask me how to solve this problem, while not slowing down perfomance?
    Thank you for attention.

    ABV-
    I found one other documented issue related to yours, and the solution was posted as a potential solution, but is not guaranteed to work.  It involves adjusting registry keys (which it looks like you are familiar with).  Caution should be taken when adjusting registry keys.  Again, this is just a step to try that helped one other customer out, so I thought I would offer it to you as a potential solution.
    Some MITE-based systems have experienced problems with the MITE chip reaching the maximum number of retries on the PCI bus. To help prevent this problem from occuring, a delay was added before the MITE chip would perform a retry on the PCI bus. The amount of time that the MITE waits is determined by the DmaCpuRequestDelay value that is entered in the Registry. The default value for this setting is 2.
    In this instance, it was this value that was causing the slowdown in the transfer rate. By changing the DmaCpuRequestDelay to 0, the transfer was increased to an acceptable level. However, caution should be taken when changing this value. If this value is changed, there is a slight possibility that bus errors might be received during large data transfers, due to the maximum retry limit being reached on the MITE chip.
    If this happens, there are two options:
    You can raise the DmaCpuRequestDelay up to 1 or back to 2
    You can disable DMA on the MITE chip by changing the DisableMiteDma value to 1.
    To change the DmaCpuRequestDelay, use the Registry Editor via Start » Run and type regedit. Navigate to the following section of the registry for WIN32: HKEY_LOCAL_MACHINE/Software/National Instruments/NI-VXI
         I hope this helps.  Have great day!
    Gary P.
    Applications Engineer
    National Instruments
    Visit ni.com/gettingstarted for step-by-step help in setting up your system.

  • VXI-MXI-2 loses register values during normal operation. Causing Bus Errors.

    The Setup:
    I have a system with two VXI chassis and a MXI2 bus running
    between them.  Each VXI chassis has a
    VXI-MXI-2 card in slot zero.  The first
    chassis has VXI cards and the second chassis has VME cards.  I set registers 0xA, 0xC, 0xE, and 0x10 to
    0x6100 on the first chassis’s VXI-MXI-2 card and 0x6180 on the second chassis’s
    VXI-MXI-2 card. 
    The Problem:
    This configuration runs smoothly 99% of the time.  Every so often we get a hiccup and lose the
    values in the 0xA, 0xC, 0xE, and 0x10 registers on the VXI-MXI-2 card in the
    second chassis.  The registers on that
    card are set to their default values of 0x1800. 
    This causes a problem, because we are unable to access the VME cards in
    the second chassis until the register’s values are reset properly.  We have verified with a bus analyzer that our
    software is not writing zeros across the VXI/MXI bus to those register.  It appears as though the second VXI-MXI-2
    card is seeing a hard reset.  The first
    chassis is definitely not experiencing a hard reset.
    Attempted fixes that have not worked:
    1) We put back the register values back into place whenever
    we detect that the MXI2 registers have been reset.  We poll the registers at 1Hz.  While this fix is semi-adequate, there are
    times that we access the registers in the second chassis more frequent than
    1Hz.
    2) We have tried swapping out our second VXI-MXI-2 card with
    a new card, but the problem persists.
    3) We have also swapped out the second VXI chassis with a
    new chassis, and that did not work.
    My questions:
    What could be causing this problem?  Has anyone else seen this problem?  What would cause the values in the VXI-MXI-2
    card to reset to zeros besides a hard reset? 
     Any suggestions?
    Thanks for your input,
    Mike Arthur

    Hi Mike,
    We currently have a support request open on this issue, and we are working on it.
    Thank you!
    Regards,
    Ebele O.
    National Instruments

  • Routing VXI-MXI-2 Trigger to backplane

    I'm currently working with a VXI-MXI-2 and a AIM/AXI429 boards. My aim
    is to drive a trigger on backplane TTL line 0 from my VXI board to the
    AIM board.
    I found the SrcTrig function that could do what I want, but it doesn't work.
    Do I have to do some special programming before calling this this function for this signal to reach the backplane ?
    Thanks for your answers.

    Hi,
    You will find some details about the SrcTrig function in the following document in the "NI-VXI Solutions to VXIbus Triggering" part :
    http://zone.ni.com/devzone/conceptd.nsf/webmain/4544aa9f5fe65b998625688600612b44?OpenDocument#3
    You will find some program examples which could help you.
    Regards,
    Marc L.
    NIF

  • Multi threadin with VC++

    Multi threadin with VC++
    I have some problems with multi threading using the provider OraOLEDB.
    When I try to execute a CreateCommand for a CCommand<CManualAccessor> in a secondary thread I have a failure inside OraOLEDB.dll.
    There is no problem if I use the provider MSDAORA.
    I found a property for the OLE DB provider named DBPROP_DSOTHREADMODEL and must be DBPROPVAL_RT_FREETHREAD,
    is the provider OraOLEDB FREETHREAD?
    Thanks for helping me.

    Do I have this right?
    You want to start a Java application from the commandline, and this application creates multiple threads.
    Each thread executes methods from the ProcessBuilder or Runtime classes, which opens a terminal (cmd) window, starts an external (non-Java) .exe program. The exe writes to the cmd window.
    If that's correct, then you need to learn how to create a threaded program, and to use Either the ProcessBuilder or Runtime class.
    Here's a how-to on creating threaded (concurrent) Java programs
    http://java.sun.com/docs/books/tutorial/essential/concurrency/index.html
    and here's an article on correct use of the Runtime class
    http://www.javaworld.com/javaworld/jw-12-2000/jw-1229-traps.html

  • Multi mapping with out BPM

    HI ALL ,
           I am trying to do multi mapping with out using BPM .I will get message from the sender and i need to send that to two different target system. I have defined the mapping in the IR . In ID i  have created the configuration scenario and i have created the receiver determination .In receiver determination i have selected "EXTENDED" and when i select input help for mapping name it says "NO Object found". What else should i do get the mapping program here .
    Regards,
    Tarun.

    Bhavesh,
    I'm sorry but if he needs 2 different receivers, then it's not the case of using Enhanced Interface Determination.
    sapuser,
    if you scenario is asynchronous, then it's easily implemented.
    But it won't be achieved with multimapping.
    You'll have 2 receivers in receiver determination (normal RD, not enhanced). For each of those, you'll have to create a separate simple mapping (that will generate the message expected at each receiver system) and refer that mapping in the interface determination of each receiver.
    For example, you have input_message containing data1 and data 2. You'll have 2 simple mappings (not a multimapping), 1 generating output_message_1 containing data1 and the other generating output_message_2 containing data2. Then refer those mappings in the proper interface determinations.
    Regards,
    Henrique.

Maybe you are looking for

  • Problem during creation of dynamic Internal

    Hi All, I am trying to create a dynamic internal table. I went through many posts, but the problem i am facing is, I want an internal table as: Empno Ename Lgart1- Depending on the Wage types user enter on the selection screen. Lgart2 When i tried to

  • Replacing WS_DOWNLOAD with CL_GUI_FRONTEND_SERVICES= GUI_DOWNLOAD

    Hi Guys,    I'm currently changing the programs that uses the obsolete function WS_DOWNLOAD with CL_GUI_FRONTEND_SERVICES=>GUI_DOWNLOAD, and I just want to ask what are the valid FILETYPE for GUI_DOWNLOAD and how can I use a WK1, XLS and DAT filetype

  • Trouble w unit test code

    this code compiles fine, but my unit tests starting with the lines public static class AllTests extends TestCase { are failing with a null pointer exception. i was advised that '> The testCreateAccount is failing because you're using a local variable

  • Adding a ValueField to an existing Operating Concern?

    Gurus, I'm new to CO-PA. I need to add a new Value Field to an operating concern which is already live in CO-PA. Please let me know the impact of it on an operating concern and the existing reports if any. Create the new Value Field in KEA6 Add the n

  • What is the best version of Final Cut Studio

    I'm not a pro but not an amateur video maker so I want to upgrade from FCE 4. I focus on action sports. The question I have is whats the best version of FCS? Thanks!