PXI 4130 Power SMU Output

Hi, I am trying to get my head around how the PXI 4130 works. I have a solenoid valve that I am trying to actuate with the utility channel of the 4130. It says that the utility channel can source 6V and 1A. The solenoid valve requires 6V, but the coil in the valve says it is a 12 Watt rated coil. Since amps = watt/voltage, the solenoid valve should draw 2A (12/6). But does that mean that the 4130 will not let out 2A and will only let out 1A? If I am supplying 6V will it not automatically just output 2A by the law V = IR??

Your understanding is correct.  The 6V Utility Channel (Channel 0) can only output 1A maximum on the PXI-4130 SMU.
If your load tries to draw more than the current limit (user programmable up to 1A on Channel 0), then the SMU output will go into "current compliance" which forces the SMU into constant current mode instead of constant voltage mode - as a result, your voltage will drop accordingly until V=IR.  This behavior is often used to protect the device under test connected to the SMU.  ...I might start by testing out the solenoid and seeing if it will actuate at only 1A, but the best solution would be to use an output capable of 2A like Channel 1 on the PXI-4130. 
Also, please take note that heavily inductive loads can occasionally cause issues with the control loops on power supplies on SMUs:
http://zone.ni.com/reference/en-XX/help/370736F-01/ni_dc_power_supplies_help/4130_source_stability/
NI has recently developed some cool technology on newer SMUs that helps manage control loops under reactive loads:
http://www.ni.com/white-paper/13093/en/
For both points above, I might recommend to monitor what happens to the 4130 output as you actuate the solenoid the first time - either using the on-board voltage and current measurements of the 4130 (can read at up to 3kHz) or with an external scope on the voltage.

Similar Messages

  • Pxi 4130 current range error

    Hi, 
    I'm trying to configure PXI - 4130, with labview.
    DC Volt and range set to 1.5V - no error.
    Current limit and range set to 200uA, 2mA and 20mA - getting the following error.
    The error tells that i'm not setting the right range - which is not true. Also, Property: Current Limit Corresponding Value:  100.0e-3 . In fact this is 2mA itself in the VI. 
    Tried with the VI in llb as well as NI DC Power property node.
    Confused !! Please help.
    Property Node (arg 2) in PXI_4130_SMU.vi <ERR>
    Invalid value for parameter or property.
    Conflicting Properties: Current Limit Range, Current Limit
    Property: Current Limit Range
    Requested Value:  2.0e-3
    Possible Values:  200.0e-6,  2.0e-3,  20.0e-3,  200.0e-3,  2.000000
    Property: Current Limit
    Corresponding Value:  100.0e-3
    Specified Range Minimum:  40.0e-6
    Specified Range Maximum:  2.0e-3
    Channel Name: 1
    Status Code: -225152
    Thanks
    Manu
    Solved!
    Go to Solution.

    Hi Manu,
    What version of the DC Power driver are you working with? Are you explicitly setting both the Current Limit and the Current Limit Range in your VI? If you open up the Example Finder (Help>>Find Examples) you can locate the DC Power Examples (Hardware Input and Output>>Modular Instruments>>NI-DCPOWER) and I would recommend that you open up and try running the example titled "NI-DCPower Source DC Voltage.vi". This example will configure the SMU to source a DC voltage for the configured current limit and current limit range. If properly configured, this VI should run without errors and can be used as guide for writing your VI. 
    Steve B

  • PXI Chassis Power LED Flashing Red: What to do?

    My NI PXI-1042 keeps blinking red the Power LED. I know it means the voltage is out of the specs. What to do?

    FilipeTaveiros wrote:
    But it is not continuously red.. It is blinking red.. Thanks for your help. Anyone? 
    This is copied right out of the manual: 
    The chassis power switch has an integrated LED. This LED indicates one
    of three different conditions:
    • If the power switch LED is steady green (not flashing), the chassis is
    powered on and operating normally.
    • If the power switch LED is flashing green, the air-intake temperature
    has exceeded the chassis operating range.
    • If the power switch LED is flashing red, the power supply outputs are
    not within voltage regulation requirements.
    You either have a power supply problem, or you are loading it down with too many modules.  Try running it empty and see what the light does. 
    Using LabVIEW: 7.1.1, 8.5.1 & 2013

  • Renew authorization on a Power BI output isn't working

    We have received reports that clicking renew authorization on a Power BI output doesn't renew the Power BI authorization.
    Engineering team is working on resolving this issue but in the meanwhile you can delete and add an identical Power BI output to work-around it.

    We have received reports that clicking renew authorization on a Power BI output doesn't renew the Power BI authorization.
    Engineering team is working on resolving this issue but in the meanwhile you can delete and add an identical Power BI output to work-around it.

  • SIngle reference for PXI 6509 Input and Output

    Hi ,
    I am using 96 channel PXI 6509 as a DIO, In this 96 channels i need to assign 1st port for input, 2nd port for output  and 4th and 5th for input so on. its is not a big deal using labview but labview creates seperate reference( Task in) for input and ouput.
    I need to have a single reference for both input and output ( like we have in NI DCpower for SMU)
    Can any one suggest me how i can achive this?
    Thanks and best regards,

    I would accomplish this with an Action Engine that handles all of your tasks.  Alternatively, make a class that handles all of the tasks.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • My PXI-4132 has stopped outputting voltage

    I have an NI PXIe-1073 chassis with an NI PXI-4132 card installed.
    I had the system turned off over the weekend & started it up to do some linearity measurements on an ADC  yesterday. As usual, I was going to do a quick check of my setup by using the NI DC-power soft front panel to output some dc voltages & check that the data converter was giving ball park correct codes before I started a vi to sweep the input voltage & collect real data.
    I started MAX(measurement & automation explorer) & it told me that my card passed self test. Then I ran the test panel & tried to force 4V at the DUT, but my scope showed 75mV.
    I removed all the cabling & measured again at the front connector. All the lights on the front were green & the scope was set to 1MΩ input termination, but again I got no voltage on any pin of the 4132. I was expecting it to come out on “HI”.  Then I checked “Sense HI” & then all of the pins, but no voltage. The scope ground is connected through a banana lead to the chassis ground on the front of the card. I measured my HP 1.8V power supply & got 1.8V on the scope.
    I rebooted the chassis & the pc 3 times each , with the same result. What  might I be doing wrong? Is there a vi I could run to reset everyting? I have reset the card with MAX.
    I have had this unit for 3 years & I don't think it has ever done this before.

    Hello Bob,
    You can try to self-calibrate your device (In MAX, right click the device and select Self-Calibrate). If there is something wrong with the hardware then the calibration is going to fail. Please document the result if there is any error. Please remember to disconnect all the cabling previous to the calibration.
    What is the value read in the front panel for voltage and current after you enable the output? Are you working with the Local or Sense measurement mode? Please connect your oscilloscope to terminals C and F (refer to picture 7 on the link below) and configure the test panel to Local Sense, what is the value read on your oscilloscope?
    http://www.ni.com/pdf/manuals/375128b.pdf
    Regards,
    MCOTO

  • UMI-7774 - Setting default Power up outputs?

    Hi,
    I'm using a UMI7774, PXI7350, NI Motion 7.4.0.3002, and LV 8.2 I have a 24 V power supply connected to Viso on the UMI. When the PXI computer boots the general purpose digital output lines (table 3-9 in the UMI manual) on the 25-pin D-sub go to 24V and stay there until the board is initialized. Is there a way to set the default power up state to 0V?
    Thanks,
    Richard

    Hi Richard,
    Here is a knowledgebase document regarding how to change the
    power up state
    KB 2HA8B9YJ: How Do I Change the
    Default Power Up State of the DIO Lines on the NI 733x, 734x, and 7...Based on the setup configuration you have described, there
    is currently no direct method for accessing the DPull pin. One work-around
    would be to create your own custom cable in order to ground this pin.   Here is
    another document regarding how to do this:
    KB 47FARV4M: Creating custom cables
    for NI Motion controllers (733x, 734x, 735x) I
    hope this helps.  Please let us know if
    you would like further clarification or assistance regarding this issue.  
    Best
    regards,
    Vu

  • No firewire after turning of mains power - SMU reset needed to fix

    Everytime I turn the mains power off on my 20" G5 imac when I reboot I've lost all my firewire connections. If I do a SMU reset they both come back.
    It's a new logic board having been replaced on Apple Care for the overheating and fan problems.
    Unfortunately my Apple care has now run out.
    I've so far:
    1. Replaced the Logic Board battery,
    2. Wiped the drive and reinstalled the OS,
    3. Zapped the PRAM
    4. Reset the NVRAM
    5. Reset-all the Open Firmware
    6. Swapped the Ram out
    I know a lot of people have had similar problems, but none of the fixes work.
    Any ideas on what might be causing this problem?
    Thanks.

    Hi airsine,
    The "standard" fix for firewire problems is actually to remove all power to both the computer and the connected FW devices, disconnect the FW devices, wait 15 minutes (sometimes far less is all that is needed) and then fire it all up again. The FW ports have a self resetting fuse that can be reset using the above process. The SMU reset process can "mimic" this process, because it also involves removing power to the computer, though the SMU in theory itself should have no real effect on your FW ports.
    I find myself wondering whether the problem is actually occurring not when you turn your system off at the mains, but when you turn it on again. Usually FW problems of this kind turn out to be related to either a problematic device, or combination of devices, dragging too much power, or a bad cable.
    Have you tried adding the devices one by one, to see if the problem is related to any particular one of them? You might also want to try using a powered FW hub, as this can overcome problems associated with too much load on the FW port when devices are "daisy chained". What do you actually have connected?
    Cheers
    Rod

  • Pxi 8360 power led flashes red

    I have a PXI 8360 MXI Express board mounted in a PXI 1050 chassis. I am seeing the power LED occasionally flash red and I lose communication with the computer. The power LED will return to solid green status after a few minutes but I am not able to do much with NI DAQ to test the system since it has failed self test. The suspicion here is the power supply may be bad but how do we check that.
    The system with the computer has worked well over the past several years and we are concerned about possible damage from a power fluctuation that happened here around Christmas time.

    Hi Xavier,
    The red flashing light is on the PXI 8360. I have not seen any flashing lights on the chassis.
    The modules present in the system are
    PXI 8360  MXI Express
    PXI 4071  7 1/2 digit flex DMM
    PXI 4110  Programmable DC power supply
    PXI 4110
    PXI 4110
    PXI 8252  1394 Host Adapter
    TB 2627  multiplexer terminal block
    PXI 6289  M series multifunction DAQ
    SCXI 1306
    SCXI 1303
    SCXI 1303
    SCXI 1300
    So far all testing has been done with all modules installed. Another person has tried reseating all modules to see if that would fix the problem but it does not.
    The system will work fine for a few hours and then the blinking LED will begin and somewhere near that time the communications fail with the computer. The light will blink for a few minutes and then will return to solid green. Once the error has occurred it seems that the only way to re establish proper operation is to shut down the whole system, PXI chassis and computer, and restart. I saw one time where the power LED on the 8360 went from flashing red to solid green when the computer was turned off.
    The computer is  a Dell Precision 690 with PCIe 8361.
    I will be opening up the chassis hopefully in the next day or two to check fuses and voltages where I can.
    Bill

  • PXIe-1062Q Power switch will not turn of chassis

    I have a PXIe-1062Q PXI Chassis that I can turn on with the front mounted power switch, but it won't turn off again.  Is there something wrong with it, or am I missing something in the way that it's set up?
    Solved!
    Go to Solution.

    Never mind.  Figured it out.  I need to press the power button for several seconds and then it turns off.

  • PXIe-1075 Power switch will not turn off chassis

    Hi,
    I think I am having trouble turning my PXIe-1075 chassis off with the front mounted power switch. When I press the power switch, the green LED will ficker and the PWR LED on my PXIe-8360 MXI card will flicker from green to red and then back to green. I have a PXI-1042 chassis as well that seems to turn off properly. The switch on my PXI-1042 chassis has two positions, but the switch on my PXIe-1075 only seems to have one position. I am in a spot where I will need to power off my chassis to move it occasionally. Does it sound like my PXIe-1075 chassis has an issue? Am I missing something? I also tried holding the power switch. This will cause all the installed modules active light to turn off, but the PWR light on the switch and the PWR light on the MIX card will stay the same.

    Hello,
    The 1075 has two modes for shutdown.  You can select between the modes with the 'inhibit' switch on the back of the chassis.  When this switch is in the default position, the chassis will power down when you shut down the controller in the chassis (I'm not sure if it will automatically power down with the MXI connection when you shutdown the PC- I do not believe it will).  When the switch is in the manual position, the chassis does not shut down with the controller and you must use the Inhibit signal on pin 5 of the Remote Inhibit and Voltage Monitoring connector.  I believe your chassis is in 'Manual' mode.  More information on this is available in the manual on page 2-12:
    http://www.ni.com/pdf/manuals/372537b.pdf
    I do not think that the power button on the front can be used to power off the chassis.
    Jon F.
    Applications Engineer
    National Instruments

  • PXI-1033 power up causes PC to boot up

     I have a PXI-1033 chassis connected to a Windows 7 PC via MXI-Express cable. Both the PC and PXI chassis are off. When I push the power button on the PXI chassis, the PC turns on. I cannot figure out the cause of this. Thanks.

    habsfan,
    This is expected behavior.  The PXI-1033 attempts to wake the host PC when it's turned on as a convenience so you can power up the whole system with a single switch.  The mechanism it uses is the PCIe WAKE# signal.
    Is it a problem for you, or are you just suprised by it?  I don't think there's a way to disable it on the PXI-1033, but there may be other ways.  Many systems have an option to enable or disable waking the system from PCIe cards, so you could look through the BIOS options of your PC.  Or, if you power on the chassis 4-5 seconds before connecting the MXI cable it shouldn't wake the PC.
    - Robert

  • PXI-5421, C++, Creating output signal, DAQmxWriteAnalogF64 fails

    I want to create a simple sine wave output on a PXI-5421 card. I have looked at the sample projects for DAQmx, and based an application on them.
    The application falls over at the call to DAQmxWriteAnalogF64 using the following parameters:
    lReturn = DAQmxWriteAnalogF64(
    m_hTask,
    1000,
    0,
    10.0,
    DAQmx_Val_GroupByChannel,
    data,
    &lWritten,
    NULL
    What am I doing wrong?
    Below is the output of the application, and the code.
    ***** START OF OUTPUT *****
    DAQmxResetDevice -> SUCCESS
    DAQmxCreateTask -> SUCCESS
    DAQmxCreateAOVoltageChan -> SUCCESS
    DAQmxCfgSampClkTiming -> SUCCESS
    Samples per channel written: 0
    Source terminal to be routed could not be found on the device.
    Make sure the terminal name is valid for the specified device. Refer to Measurement & Automation Explorer for valid terminal names.
    Device: PXI1Slot3
    Property: DAQmx_SampClk_Src
    Source Terminal:
    Task Name: _unnamedTask<0>
    Status Code: -200040
    DAQmxWriteAnalogF64 -> -200040
    ***** END OF OUTPUT *****
    ***** START OF APPLICATION *****
    void Startup( void )
    // get amplitude
    double dblAmplitude = 5; // 5 volts
    // generate wave data
    float64 data[1000];
    for( int i=0; i<1000; i++ )
    data[i] = dblAmplitude * sin( (double)i * 2.0 * PI/1000.0 );
    // device, channel and terminal names
    char szDeviceName[128];
    strcpy(szDeviceName,"PXI1Slot3"); // PXI1Slot3
    char szChannel[128];
    sprintf(szChannel,"%s/ao0",szChannelName); // PXI1Slot3/ao0
    char szTerminal[128];
    strcpy(szTerminal,"Onboard Clock"); // Onboard Clock
    // reset device
    long lReturn = DAQmxResetDevice(szDeviceName);
    _AddToLog("DAQmxResetDevice",lReturn);
    // create task
    lReturn = DAQmxCreateTask("",&m_hTask);
    _AddToLog("DAQmxCreateTask",lReturn);
    // if that worked...
    if(lReturn==0)
    // create output voltage channel
    lReturn = DAQmxCreateAOVoltageChan(
    m_hTask,
    szChannel,
    -1 * dblAmplitude,
    dblAmplitude,
    DAQmx_Val_Volts,
    NULL
    _AddToLog("DAQmxCreateAOVoltageChan",lReturn);
    // if that worked...
    if(lReturn==0)
    // define sampling
    lReturn = DAQmxCfgSampClkTiming(
    m_hTask,
    szTerminal,
    10*1000,
    DAQmx_Val_Rising,
    DAQmx_Val_ContSamps,
    1000
    _AddToLog("DAQmxCfgSampClkTiming",lReturn);
    // if that worked...
    if(lReturn==0)
    // write to buffer
    long lWritten = 0;
    lReturn = DAQmxWriteAnalogF64(
    m_hTask,
    1000,
    0,
    10.0,
    DAQmx_Val_GroupByChannel,
    data,
    &lWritten,
    NULL
    CString strLine;
    strLine.Format("Samples per channel written: %d",lWritten);
    _AddToLog(strLine);
    _AddToLog("DAQmxWriteAnalogF64",lReturn);
    // if that worked...
    if(lReturn==0)
    // start task
    lReturn = DAQmxStartTask(m_hTask);
    _AddToLog("DAQmxStartTask",lReturn);
    else
    // clean up
    _CleanUp();
    void _CleanUp( void )
    // stop task
    long lReturn = DAQmxStopTask(m_hTask);
    _AddToLog("DAQmxStopTask",lReturn);
    // clear task
    lReturn = DAQmxClearTask(m_hTask);
    _AddToLog("DAQmxClearTask",lReturn);
    ***** END OF APPLICATION *****

    Broccoli wrote:
    I want to create a simple sine wave output on a PXI-5421 card. I have looked at the sample projects for DAQmx, and based an application on them.
    The application falls over at the call to DAQmxWriteAnalogF64 using the following parameters:
    lReturn = DAQmxWriteAnalogF64(
    m_hTask,
    1000,
    0,
    10.0,
    DAQmx_Val_GroupByChannel,
    data,
    &lWritten,
    NULL
    What am I doing wrong?
    Below is the output of the application, and the code.
    ***** START OF OUTPUT *****
    DAQmxResetDevice -> SUCCESS
    DAQmxCreateTask -> SUCCESS
    DAQmxCreateAOVoltageChan -> SUCCESS
    DAQmxCfgSampClkTiming -> SUCCESS
    Samples per channel written: 0
    Source terminal to be routed could not be found on the device.
    Make sure the terminal name is valid for the specified device. Refer to Measurement & Automation Explorer for valid terminal names.
    Device: PXI1Slot3
    Property: DAQmx_SampClk_Src
    Source Terminal:
    Task Name: _unnamedTask<0>
    Status Code: -200040
    DAQmxWriteAnalogF64 -> -200040
    ***** END OF OUTPUT *****
    ***** START OF APPLICATION *****
    void Startup( void )
    // get amplitude
    double dblAmplitude = 5; // 5 volts
    // generate wave data
    float64 data[1000];
    for( int i=0; i<1000; i++ )
    data[i] = dblAmplitude * sin( (double)i * 2.0 * PI/1000.0 );
    // device, channel and terminal names
    char szDeviceName[128];
    strcpy(szDeviceName,"PXI1Slot3"); // PXI1Slot3
    char szChannel[128];
    sprintf(szChannel,"%s/ao0",szChannelName); // PXI1Slot3/ao0
    char szTerminal[128];
    strcpy(szTerminal,"Onboard Clock"); // Onboard Clock
    // reset device
    long lReturn = DAQmxResetDevice(szDeviceName);
    _AddToLog("DAQmxResetDevice",lReturn);
    // create task
    lReturn = DAQmxCreateTask("",&m_hTask);
    _AddToLog("DAQmxCreateTask",lReturn);
    // if that worked...
    if(lReturn==0)
    // create output voltage channel
    lReturn = DAQmxCreateAOVoltageChan(
    m_hTask,
    szChannel,
    -1 * dblAmplitude,
    dblAmplitude,
    DAQmx_Val_Volts,
    NULL
    _AddToLog("DAQmxCreateAOVoltageChan",lReturn);
    // if that worked...
    if(lReturn==0)
    // define sampling
    lReturn = DAQmxCfgSampClkTiming(
    m_hTask,
    szTerminal,
    10*1000,
    DAQmx_Val_Rising,
    DAQmx_Val_ContSamps,
    1000
    _AddToLog("DAQmxCfgSampClkTiming",lReturn);
    // if that worked...
    if(lReturn==0)
    // write to buffer
    long lWritten = 0;
    lReturn = DAQmxWriteAnalogF64(
    m_hTask,
    1000,
    0,
    10.0,
    DAQmx_Val_GroupByChannel,
    data,
    &lWritten,
    NULL
    CString strLine;
    strLine.Format("Samples per channel written: %d",lWritten);
    _AddToLog(strLine);
    _AddToLog("DAQmxWriteAnalogF64",lReturn);
    // if that worked...
    if(lReturn==0)
    // start task
    lReturn = DAQmxStartTask(m_hTask);
    _AddToLog("DAQmxStartTask",lReturn);
    else
    // clean up
    _CleanUp();
    void _CleanUp( void )
    // stop task
    long lReturn = DAQmxStopTask(m_hTask);
    _AddToLog("DAQmxStopTask",lReturn);
    // clear task
    lReturn = DAQmxClearTask(m_hTask);
    _AddToLog("DAQmxClearTask",lReturn);
    ***** END OF APPLICATION *****
    Hello Broccoli,
    NI-DAQmx is not a supported API for the NI-5421 AWG. For all NI Signal Generators, please use the NI-FGEN API, which shipped with your instrument. You may also download NI-FGEN (2.2.1 as of today) from
    http://digital.ni.com/softlib.nsf/954feaeea92d90918625674b00658b83/8b1f32b4b8f7148586256efd006075a9?OpenDocument
    You should find helpful C examples bundled with NI-FGEN that will make using the NI-5421's full capabilities very easy.
    Marcos Kirsch
    Signal Generators Software Engineer
    Marcos Kirsch
    Principal Software Engineer
    Core Modular Instruments Software
    National Instruments

  • PXIe 1073 Power On Start

    Hello.,
    I have a PXIe 1073   system
    I want to start it automatically when there the Mains  Power is connected.
    any clues !!

    Dear aparab,
    as far as I understand your inquiry, you'd like to boot a pxi controller without pressing the on-switch. The PXI chassis has three different methods on how to power on: Wake-On-LAN, an inbuilt switch and a BIOS setting. Details you can find in the following article.
    Remote Power of a PXI Chassis
    http://digital.ni.com/public.nsf/allkb/FF5AB8BB6A1157DB8625756D00502D55
    with regards
    AndGar

  • PXIe-1075 power on failure

    I have one NI PXIe-1075 chasis. It was working fine last week. But today when I power on it, it failed.
    There is the 'tick tick tick' sound coming from the behind the chasis.
    Can anyone help on this ? could the power supply on the chasis broken ?

    kmcdevitt wrote:
    Any chance that enabling a total of 8 hyperthreaded cores in LabVIEW RT on a PXE diskless booted PXIe-8133 caused it to use draw too much power on the the PXIe-1075?
    Hah!  You guys are always ready with a joke, I like that.  Seriously, though, you're right that enabling hyperthreading does indeed draw more power than when it's not enabled, simply because all areas of the core have to be powered in hyperthreaded mode (even those that normally are in standby most of the time).  However, hyperthreading is a normal and fully tested use-case when running Windows on an RT controller - all NI PXI(e) embedded controllers (that support hyperthreading) can run Windows in full hyperthreaded mode.  Therefore, running LabVIEW RT in hyperthreaded mode via the PXE option or through turning the RT controller into a PC Desktop RT system should not have any detrimental effect on the power supply or power availability. However, if your supply was on its last leg, maybe enabling hyperthreading helped it kick its last bucket?  
    -Danny

Maybe you are looking for

  • Is the MacBook Air as powerful as the MacBook Pro?

    I need a pretty powerful computer and it has to be apple because I need itunes for my job and I can only rely on itunes on a mac, but it has to run some pretty powerful software, so can an air handle it as well as a MBP with retina?

  • Enhancement on F.13 to clear line items automatically

    hello friends, i am not able to clear line items with F.13 transaction for special G/L Account..i am inputing the values with the Transactions F-48 and F-43....we can view the details in Tr.code-FBL1N. Can any one help me...plzzz vamshi

  • When is the siri voices pack become available

    Okay this might seem a bit trivial when you compare it to yet another awsome invention from apple. But why do we not have a choice of voices on SIRI, after all this is to replace the need to use manual imput, so can you imagine having to listen to a

  • Getting error System.Web.Services.Protocols.SoapException: Server did not r

    I am trying to acces my web service using this code Call call = new Call (); SOAPMappingRegistry soap = new SOAPMappingRegistry(); call.setTargetObjectURI ("http://tempuri.org/"); call.setMethodName ("EarnNValue"); Vector params = new Vector (); para

  • Authorization error in DTR

    Hi, We have installed and configured NWDI SP 17 using template config tool and DI template. I have created CMSADM user and assigned the groups JDI.Administrators and JDI.Developers to it.  I can login to the DEVINF (CBS, CMS), but not DTR. I am getti