Generate PXI Trigger Signals with PXI-6115

Hello,
I have a question.
I have a PXI-6115 and some other card in my mainframe.
These other cards nee 10 Mhz pulses on line PXI-Star1 and 2.5 MHz on PXI_trg7.
So I thought to apply (somewhere on my PXI 6115 card) 10 MHz, divide the 10 MHz with a counter to 4 and route all this things to the backplane.
But I don't understand how to do this.
There are no good examples.
And as far as I know the PXI-6115 isn't yet supported by DAQ-MX.
Can anybody give me some good advises or tips, white paper or so to make me solve my problem ???
Thanks Ruediger

I don't have time to write any example snippets right now, but I'll try to provide you the general idea and hopefully you can take it from there.
First, it's not clear whether you want to generate the 10 MHz from the 6115 and send it to other devices in the system or accept the 10 MHz externally and route it to the rest of the system.  If you're bringing in the signal externally, I would simply using the DAQmx Connect Terminals VI to route the signal from a PFI line on the front connector of the board to one of the PXI trigger bus lines in the backplane.  Check out the routing table in MAX to see what routes are possible.  To perform this route, the driver will have to route through Counter 0 so you won't be able to use Counter 0 for anything else.
If you want to generate 10 MHz from the 6115, I would create a continuous pulse train task on Counter 0 using the CO Pulse Ticks version of the Create Channel VI with a value of 2 for both the high ticks and low ticks input.  However, to achieve 10 MHz clock on a PXI trigger line, you'll have to perform a couple of modifications that typically aren't done with counter tasks.  First, you'll need to use the DAQmx Export Signal Property Node to route the Counter Output Event to the desired PXI trigger line.  You can find this property by navigating the following menu hierarchy Events->Counter Output Event->Output Terminal.  By default, the driver routes this event to the Ctr0Output pin on the front connector of the board.  Using this property will override this behavior and route the output of the counter to a PXI trigger line instead.  Second, you will need to change the output behavior of the Counter Output Event from toggle to pulse.  This can be through the Events->Counter Output Event->Output Behavior property.  Normally, when generating pulse trains, the high ticks and low ticks parameters from the Create Channel VI determine the frequency and duty cycle of the pulse train.  When the high ticks count expires, the output of the counter toggles.  The low ticks value is then loaded into the counter, and the counter output toggles again when the low ticks value expires.  This process repeats to produce a pulse train of the desired frequency and duty cycle.  Since the counter uses a 20 MHz timebase and has a minimum low ticks and high ticks value of 2, you can only produce at maximum a 5 MHz pulse train using the toggle behavior.  However, by changing the output behavior from toggle to pulse, the counter output will issue a short pulse each time the high ticks and low ticks counts expire yielding a 10 MHz clock signal.
Now that you have the 10 MHz signal taken care of, you need to generate a 2.5 MHz signal from it.  My guess is that since you have a 6115, you already have plans for the AI engine so I'll describe a route that uses AO instead.  First, create an AO task to perform continous waveform generation.  Use the DAQmx Channel Property Node and set the Use Only Onboard Memory property to true.  Setting this to true will cause the driver to download the waveform once upon starting the task and replay the waveform from the onboard FIFO.  Since you're only using this task to generate a clock, you don't really care about the data and this will prevent unneccessary traffic across the PCI bus.  Next, use the DAQmx Timing Property Node to set the Sample Clock->Timebase->Source to the PXI Trigger line that you're generating the 10 MHz clock on, and set the Sample Clock->Timebase Divisor to 4 (10 MHz / 4 should give you a 2.5 MHz sample clock).  Last, use the DAQmx Export Signal Property Node to set the Clocks->Sample Clock->Output Terminal to the PXI Trigger Line you want to generate the 2.5 MHz signal on.
It requires some creative programming, but you should now have a 10 MHz and 2.5 MHz signal routed onto two different PXI Trigger lines.  I know this solution is a bit involved so if you have any further questions be sure to post back.

Similar Messages

  • How to measure different signals with PXI-2501

    Hello everybody,
    i have a an understanding problem.
    I have a PXI-2501 switch and i want to measuere signals with the pxi-4071, so far so good.
    I did some voltage- measurements and everything worked fine. Then i disconnected the power source and measured the temperature with a PT1000 in four-wire-mode ... also worked fine.
    But i want to measure voltage and temperature, in the same VI, so i connected the voltage signal on CH0 and the PT1000 at CH5 (in four wire mode), and now i get problems. The temperature is fluctating. There are a few measurements that seems OK, and then i see some that are far away from the truth.
    The VI consists of a state machine, the measurements are done in different states, of course with the correct scan list for each measurement.
    Any suggestions? Am I doing something completely wrong?
    Thanks
    (and excuse for my english )

    Hi Roman,
    id I understand you right:
    The temperature measurement works fine, if the sensor is directly connected to the 4071, but if connected via the 2501 you see the big deviations?
    Have you measured the the resistance of the Switch-Matrix yet?
    kind regards 
    Heinz

  • CTR works with PXI 8196,PXIe 8102, fails with PXIe 8100 - why?

    My client has reported a problem.  
    For years he has used a PXI 8196 RT Controller with PXI 6602 Counter card and my software has given good results.  They have 20+ of these systems and they have worked well.
    Now they are moving to PXIe 810x controllers, for cost reasons.
    WIth a PXIe 8102, the same code also works perfectly, measuring total counts over a period, as well as instantaneous frequency.
    With a PXIe 8100 - the exact same code reports DIFFERENT answers. The reported frequency is always 1% HIGHER than actual (For example, a known 4500 Hz input is reported as 4500 Hz on 8102, but as 4545 Hz on 8100.
    This happens on any channel, and swapping just the controller will make the problem come and go.
    Here is the CONFIGURE code, where the channels are set up (again, this has worked for years).
    Here is the SAMPLE code:
    Basically the CONFIG code configures the thing to count edges.   I do this because they need an accurate count over a 20-minute period, in addition to instantaneous frequency readings.
    The AVG TIME is a user-settable number defining how long a period to average, when showing the "instantaneous" frequency.
    So, I create a buffer for N samples, corresponding to that period.
    At SAMPLE time, I read the counter.  I replace the oldest value in the buffer with the newest, then subtract the newest - oldest to get the total counts in the sample period.
    The PULSES PER COUNT item is a scaler, to account for a 60-tooth wheel, or something.
    So, this same code has worked perfectly for years, until I plug an 8100 code in.  Then the result changes by 1 %, and EXACTLY 1%?
    The CPU burden on the bad controller is 31%.
    Any ideas?
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

    Well, the controllers are not in my own hands.  I have an 8196 controller and on that, the CPU time is between 2 and 4%.
    But the 8100 and 8102 controllers are in my client's hands.
    I haven't gotten any hard timing numbers other than I saw the 31% figure reported on the video monitor.
    It's hard to believe that it would be EXACTLY 1% if it was CPU overburden.
    My software includes a calibration facility; here is a run from the good 8102:
    Here is a run from the 8100:
    This was with a reference digital freq generator.  You can see the one case where everything is within 0.1 Hz.
    the other case has everything EXACTLY 1% higher.  My only explanation is that the scan engine is running 1% slower.
    Steve Bird
    Culverson Software - Elegant software that is a pleasure to use.
    Culverson.com
    Blog for (mostly LabVIEW) programmers: Tips And Tricks

  • How to continously generate a voltage signal with dynamic amplitude.

    Hello all,
    I am looking for ideas and pointers (help in other words). I would like to generate a voltage signal (sine for example) on a AO of my NI cRIO-9263 (DAQmx). The signal should be:
    continuous (without jumps ie. smooth)
    dynamically able to be change the amplitude, frequency and sampling rate.
    interuptable so that the AO can be turned off.
    I have tried to use the DAQ Assistant but once it runs in continous mode, I have the impression that the waveform should not be changed. Is there maybe a way where I send repeatedly N samples of the waveform to the AO and gain more control over the signal that way. But if I do that how can I ensure that the signal is continous?
    Further more this output has to be generated in an event application ie. in the background.
    Your ideas and input is appreciated. Thanks, Bernie

    See if this example VI helps
    Ches this one too

  • Re-arming trigger time with pxi-5122

    Hi all!
    this is my first discussion in this forum so I'm not sure it's the right place to post it, because i'm using LabView but maybe it is an hardware problem.
    So... I have a problem to calculate the re-arm trigger time for the pxi 5122.
    From the data sheets I read that it should be about 3 us with the tdc off or 12 us if on.
    But I needed an accurate measure of the dead time following each record measured so i decided to find it by myself...
    Using an acquisition program I have previous written in LabView, I started single acquisitions of 10000 records and each record is composed of 128 samples; as signal I used square waves with different frequencies, of 10 volts peak-to-peak (my trigger was set on the first channel of 5122 with 1 volt of edge value).
    First acquisition: 50 kHz wave. Theoretically I need 0.2 s to capture 10000 records without loosing any signals from the square wave. Choosing an acquisition time for a single record of 15.3 us, I found that the time required was 0.199998 s, very similar to the expected one.
    Then choosing an acquisition time for a single record of 15.4 us, I found about 0.4 s.
    I can guess that in this second case one every two wave peaks goes lost so I required twice the time to capture 10000 records.
    Because a wave period is 20 us I have calculated a dead time of 20 - 15.3 = 4.7 us.
    It wasn't as the 3 us described for the 5122 but i wasn't impressed and i went on with my try.
    Second wave: 20 kHz. I need 0.5 s to capture 10000 records without loosing signals from the square waves.
    What i found was that in this case, choosing an acquisition time for a single record of 39.6 us I required 0,5 s to capture all the peaks, while with 39.7 us I required about 1 second, again twice the time.
    As the previous example I have calculated the dead time: 50 - 39.6 = 10.4 us.
    Very strange... the dead time I supposed being the rearming trigger (and so fixed) was different for the 2 cases.
    Trying with others waves lenghts, values were always different.
    This happen also fixing the frequency of the square wave and changing the number of samples per record.
    For example, with 128 samples per records as I said before I needed a measure time of about 15.3 us to collect all the consecutive peaks, while with 64 samples I needed 12,8 us and so on.
    So it seems to be a dependency between the dead time after a records ( the rearming trigger? now i'm not so sure if I can call so) and the sampling frequency of the pxi 5122.
    But I don't know why the DAQ behave in this way.
    Is it right? Rearm time should be fixed,shouldn't it?
    I know it required a bit of time to read my problem but i tried to be more accurate I could.
    Thank you in advance.
    Giacomo
    Solved!
    Go to Solution.

    Just as with full blown oscope, the cannot select a timing period between the scales shown on the front panel.  For example, the horizontal setting is labled 1us, 2us, 5us, etc.  You cannot select 2.5us.  Here is an excerpt from the PXI-5122 spec manual triggering section:
    Divide by
    n decimation available where 1<n<65,535
    For more information about Sample Clock and decimation, refer to the NI High-Speed Digitizers Help.
    What this means is that when you change from 15.3us to 15.4us, the scope changes timing ranges.  That is why it takes twice as long to acquire the samples.
    - tbob
    Inventor of the WORM Global

  • Aquisition of a voltage Signal with PXI 6713

    Hi.
    I want to make voltage aquisition with a PXI 6713 card. I take the Channels ai16 to ai33. The voltage at the clamp is 3.886VDC ( measured with a DMM ). When i measure the voltage and calculate it into a current ( see my applikation atteched ) the result is something between -10 and -24mA?!?!?
    Are the settinges in the DAQmx Express-VI "analog voltage aquire" wrong or could it be another Problem?
    My settings are:
    RSE
    voltage measuring from 0 to +8VDC
    N Samples
    I hope of yous Answer.
    Thanks
    Attachments:
    analog_voltage_aquisition.jpg ‏33 KB

    Is it a trick question??
    First of all, Looks like you mentioned the card wrong PXI 6713 is an AO card, without any AI channels
    Which card are you using??
    Are you connecting a 390 ohm Resistance on your connector block to convert current signal to Voltage equivalent?? ( Sounds like you are not )
    Are you measuring the Voltage correctly in the first place??
    if you are not, check if the signal is connected correctly for RSE mode
    Hope this Helps
    Regards
    Dev
    Message Edited by devchander on 07-28-2006 07:35 AM

  • Can't replace PXI onboard clock with PXI-6682 oscillator clock on PXI back plane

    I have installed a PXI-6682 timing module in slot 2 of a PXI-1031chassis with a PXI-8110 controller running Hypervisor and RT.  The 6682 is installed on the RT system under Hypervisor for GPS timing during measurements but I would like to put the TCXO on the PXI-1031 chassis backplane (replacing the PXI onboard clock).  When I try to run the "Route Clock.vi" that I found in the example finder, all I get are error messages indicating that a parameter for this operation is invalid.  The source terminal is "Oscillator" and the destination terminal is "PXI-Clk10_In".  How do I determine which parameter is invalid?  Any suggestions?  Thanks
    Solved!
    Go to Solution.

    Hi vugt,
    I tested this out and have what I believe to be your final answer.
    The short answer:  The PXI-6682 can be used with NI-Hypervisor on the Windows side, but not on the Real-Time side.
    The long answer:
    While the NI-Hypervisor Manager allow you to put the PXI-6682 on two different systems, it is still only one PXI card on the PCI bus, so really only one system can access it at a time.
    Therefore we need to assign both "devices" to either Windows or Real-Time.  For our purposes, let's assume we assign it to Real-Time.
    On an NI-Hypervisor system, each PCI interrupt line can only be assigned to one operating system.  Either it can be assigned to Windows, or it can be assigned to RT.
    Here is where the problem arises: The PXI-6682 needs to be located in a System Timing slot (generally slot 2).  However, this slot (at least in the 1000B chassis I tested in) is located on the same PCI interrupt line as the chipset.  Windows is required to have access to this PCI interrupt line, so devices used by Real-Time cannot be located on this interrupt line.
    This prevents us from being able to use the PXI-6682 in Real-Time.
    The NI-Hypervisor Manager will try to tell you to resolve this conflict by moving the PXI-6682 to slot 3, however, now the System Timing slot requirement is not met.
    This does not prevent the card from being used on the Windows side of an NI-Hypervisor system, or on a purely Real-Time system.
    Have a great day,
    Chris V
    Applications Engineer
    National Instruments

  • Generating frequency hopping signal

    I'm working with 5661 + 5671.
    I want to generate frequency hopping signal with 5671. The frequency band is 2400-2500MHz, and the hopping rate is one hop per frame (1.024ms) or 976 hop per second.
    I also need to be able to test the hopping signal with 5661 RFSA.
    Does it possible to run such hopping test with the 5661+5671?
    Thanks,
    Chen
    Solved!
    Go to Solution.

    HI
    I want to generate a hopping signal with PXI-5671 RFSG and want to analys with PXI-5660 RFSA. While seaching for the related posts i came across ur post, The frequency range in my case is between 200-300Mhz but i will use 200-220Mhz due to BW of 20Mhz...the hopping rate i wil use is very slow as compared to urs..i m trying to do this with 10-20 hops per second..
    I m new with the hardware i have used it to generate and analyz the signals but stil unable to generate the hopping signal with predefined hopping sequence and hopping rate...
    can you guide me that how to do this????or can u give me a copy of ur VI so that i can learn it from ur program and regenrate with my specs to chk weather it works or not...??
    I wil b realy thankful if u can help me in anyway....
    REGARDZ

  • Analog Trigger unavialable in PXIe-4353

    Hello,
    I'd be grateful for some help with my case. I'm building a VI for acquisition of multiple signals from thermocouples. My hardware is NI PXIe-1073 chassis with PXIe-4353 module to read the signals.
    The problem is that I want to use an Analog Edge trigger for the start of the measurement but it is unavialable to choose in the DAQ Assistant properties window (I have only None and Digital Edge to choose form). I also tried to do the same with DAQmx functions but I got the Error which says that I can only choose Digital Edge Trigger or None.
    The hardware (PXIe-4353) does seem to support Analog Triggering: http://zone.ni.com/reference/en-XX/help/370471W-01/cdaqmxsupp/pxie-4353/ or am I mistaken ?
    Also I want to note that I currently use hardware simulation and not the actual hardware - can this be the reason?
    My VI and SubVI are attached to this post. I'm new to Labview so I may have made some silly mistake. Please let me know then
    Attachments:
    poczatek.vi ‏124 KB
    poczatek.vi ‏124 KB
    DAqass.vi ‏70 KB

    Dear pancarlos,
    Unfortunately, the hardware does not support analog triggering, as stated in this thread. If that is necessary in your application, you might want to consider adding another PXI card to the system that does trigger on analog input, and use the trigger lines to start your PXIe-4353.
    Regards:
    Andrew Valko
    National Instruments Hungary

  • Driver install with PXI 8360 Error " This device cannot start - Code 10"

    While trying to instal PXI-6541 in PXI-1036 chassi with PXI 8360 controller[express-8360 on laptop side] , getting the error message "This device cannot start [Code 10]" Laptop is Lenovo T60 with latest BIOS
    Thanks
    Manu 
    Solved!
    Go to Solution.

    Hello Manu,
    I'm sorry to hear that you are having so many issues with getting your Expresscard 8360 working on your Lenovo. I recommend that we first look into Device Manager in more details. You mentioned that there were question marks (?) on certain devices. This usually means that there are devices on your PC that do not have any associated hardware drivers. For the Expresscard 8360, the drivers should be native to the Windows system, so I am unsure if those "?" do belong to this portion of the system. We can test this out by removing the expresscard 8360 and see if the "?" are still present. These "?" can be from the internals of the PC or modules that you've attached. If you've restored your operating system recently, it could be from the peripherals of your computer in which case you will need to find and install the chipset drivers. This can also be from the modules that you in your chassis, assuming that you haven't installed the necessary drivers for them, in which case you can find them on the Driver CD you have.
    The exclamation mark (!) in Device Manager usually signifies a problem with getting the hardware started/operational. From your earlier posts I believe that the "!" is related to the Error Code 10 that you are receiving. Assuming that the correct power sequence was performed, chassis then PC, this is representative of a BIOS compatibility issue. Essentially this is occuring because the BIOS of the motherboard is not correctly allocating the necessary resources to all the devices as it is supposed to. Since you already have the latest BIOS, I would recommend that you try using the MXI Express Compatibility Software, here ni.com/beta. This is something that National Instruments created in order to correct for the incorrect resource allocation of the PC. It is not a beta program, it is only on the site so that we can manage it more easily. I have seen Lenovo T60 laptops work with this software installed.
    Let me know if this helps
    Thanks
    Can W.
    PXI and VXI Platform PSE
    National Instruments

  • ADLINK PXIe-3985 Controller - NI PXIe-1062Q Chassis Compatibility

    Hello forum members!
    we recently purchased  a PXIe-3985 ADLINK PXIe Embedded controller to be installed in a NI PXIe-1062Q PXIe chassis. In our system is also present a NI PXIe-6672 Timing Module, installed in the chassis timing slot (4). Windows 7 installation, NI MAX toolsuite and NI PXIe-6672 Timing Module driver installation worked fine, but we discovered that the CPU is not able to recognize the TIMING SLOT. We cannot generate any PXI STAR signal with our NI PXIe-6672 Timing Module because it appears that the TIMING SLOT is recognized as normal peripheral slot. The PXI trigger lines and clocks are working well and usable, but not the PXI STAR signals.
    I also tried to install the PXIe Chassis in the NIMAX toolsuite as explained in the PXIPLATFORM _50-17049-100_200.pdf document from ADLINK.
    basically in the NIMAX device and interface tab I right click and try to add the pxie chassis.
    First it is not understandable how can I find the bus identifier root of the chassis. There is a PXI bus tree, but no evidence of the PXI bus related to the chassis.
    Furthermore even if I select one PXI bus, the NI PXIe-1062Q PXIe chassis is not listed and trying to load the corresponding .ini file from C://programs/nationl instruments/PXI/PXIe Chassis/ returns the error “Could not import Chassis information. Error Code 0xFFFB380E”
    is the ini file working at all for my PXIe chassis? is there another procedure that I must follow to have my  timing controller working or the chassis installed?
    We definitely need this capability to test our equipment and I would like to know if there are known incompatibility issues between these three devices:
    PXIe-3985 ADLINK PXIe Embedded controller
    NI PXIe-1062Q PXIe chassis
    NI PXIe-6672 Timing Module
    And in case if there is an update or workaround which solves the issue.
    The system has Win7 32bit installed.
    Many thanks to every answering user

    Hi emanuele83,
    which version of PXI Platform Service do you use?
    Can you please upgrade to a current version?
    Here is a download link:
    PXI Platform Services 14.1 - National Instruments
    http://www.ni.com/download/pxi-platform-services-14.1/5230/en/
    This may solve the issue.
    Best regards,
    Andi

  • Generating a flicker signal VI?

    Hello all,
    I'm currently creating a program which creates several tests concerning Power Quality with a Daqmx PXI-4461.
    First of all i would like to say that i have no problem generating or reading signals with the Daqmx.
    I'm currently at the point where I want to generate a flickering squarewave signal (flickering = small voltage dips over time) with the Daqmx, and was wondering if there was an example somewhere on the web that lets me insert the flickerfrequency and % decrease compared to the RMS value
    Like a good professor of mine always said, its better to edit an excisting example then to start from scratch!
    Regards,
    Dennis

    Hello Dennis
    I didn't directly find directly usable code, but I did find something else:
    https://decibel.ni.com/content/docs/DOC-12324
    http://sine.ni.com/cs/app/doc/p/id/cs-13888
    I think that especially the first document could help you a bit further.
    Another thing you could try is contacting the author of the case study to request if he can send you his code.
    Kind Regards,
    Thierry C - Applications Engineering Specialist Northern European Region - National Instruments
    CLD, CTA
    If someone helped you, let them know. Mark as solved and/or give a kudo.

  • Continuous square wave signal with time high pulses between 1 and 2 ms

    Hi,
    I need to generate a wave signal with time high pulses between 1 and 2 ms. I am trying to use the pwm on a digital output (Inhibit) but nothing happens.
    I am using a PCI7330 and UMI 7764.
    My labview version is 8.2.
    Does someone have an example how to generate it?
    Best regards

    Hi,
    I need to generate a wave signal with time high pulses between 1 and 2 ms. I am trying to use the pwm on a digital output (Inhibit) but nothing happens.
    I am using a PCI7330 and UMI 7764.
    My labview version is 8.2.
    Does someone have an example how to generate it?
    Best regards

  • PXI-2514 triggering with TTL signal

    Hello,
    I'm looking for help regarding opening and closing of the individual relay on PXI-2514 card through use of TTL signal.
    I'll appreciate any help.
    And, as this is my first post - hello everyone, I'm glad to be here

    Hello, and thank you for your reply.
    I'll try to describe it in detail.
    I have a PXI with two cards pxi-6115 and pxi-2514.
    Using pxi-6115 digital output I've generated a set of two impulses, and first one triggers pfi0 of pxi-6115 and through it aquisition of AI0.
    I wanted the signal on pfi0 of pxi-6115 to trigger pxi-2514 at the same time to close the relay (channels ch0 and dut0) and the second impulse (which does nothing to AI0 aquisition) to open the relay (disconnect ch0 and dut0). As I've mentioned this digital signal is connected to pfi0 of pxi-6115.
    I tried to route that signal to pxi-2514 ttl0, but with no luck.
    I attach png files with my test solutions.
    Best regards

  • Route front trigger of PXIe 2593 to backplane for use with PXIe 5251

    I have a PXIe 1062Q chassis with a number of PXIe 2593 Mux's which are connected to the two inputs channels of a PXIe 5251 Digitizer. What I want to do is to use the trigger on the front of the Mux to close the appropriate switches on the muz and to trigger the start of capture on the Digitizer, is there anyway to do this?
    If not is there another way to do what i want?

    Hi WayneR1,
    Thank you for your question!
    In order to route different signals (like triggers) on the PXIe backplane "DAQmx Connect Terminals"
    VI should be used:
    The source and destination terminals can be on different devices as long as a connecting public bus,
    such as RTSI or the PXI backplane, connects the devices.
    More detailed information can be found here: http://zone.ni.com/reference/en-XX/help/370469AA-01/lvdaqmx/mxconnectterminals/
    Please make sure that you disconnect those routes after running your code.
    Once routes has been connected, they will stay connected until you restart the PXIe controller
    or use "DAQmx Disconnect Terminals" VI:
    More information about "DAQmx Disconnect Terminals" VI: http://zone.ni.com/reference/en-XX/help/370469AA-01/lvdaqmx/mxdisconnectterminals/
    I hope that you will find this information useful!
    Kind Regards,
    Max
    Applications Engineer
    National Instruments

Maybe you are looking for

  • Startup error message on Satellite M30-107

    I get the following message when trying to boot up: Windows could not start because the following file is missing or corrupt \windows\system32\config\system You can attempt to repair this file by starting windows setup using the original setup CD-ROM

  • Reinstall the reporting services point

    We are running SCCM 2012 R2 and using SQL 2008 R2. I had to create a new reporting services database and reinstall the reporting services point. After the reinstall I am now finding the below errors in the srsrp.log log. Timed Out... SMS_SRS_REPORTIN

  • Grouping of Business Area

    Hi Gurus,       I want to do the grouping of business area.  Can i do the grouping by Maintain consolidation business area (SPRO Way). If not what is the procedure. Does it will affect the financial structure by Maintain consolidation business area o

  • 2nd HDD to replace optical drive - B560

    I have seen a thread here (http://forums.lenovo.com/t5/W-Series-ThinkPad-Laptops/2nd-hard-drive-in-a-W510/m-p/346539#M12570) of success replacing the optical drive with a 2nd HDD bay in a y560. I am wrong thinking there is not much difference betwee

  • Could somebody tell me how this program works....

    Hi, I am new in Java...I just bought a book and start to learn the java from that book. Here is one of the project exercise and seems that it is difficult for me to understand the flow of the program. class HelpClassDemo { public static void main(Str