Acquisition parallel to 25 MHz with a PXI-7854R

Hello

For an application, I need to acquire a bus parallel to 25 MHz with a 7854R.

I search for information on the forum and I am a little lost. I have seen that we can create derivatives clock on my FPGA.

I can create a clock of 100 MHz and use it in a SCTL to check if a rising edge appears on my clock line and acquire the line data (24 rows of data), but I do not understand what means the limit of 40 MHz for EID.

At what rate data are updated if I used a SCTL clocked at 100 MHz to read a digital input?

Do you know if it the best way, or if it is possible to acquire my bus with this material?

Thanks in advance for your answer

The clock of the FPGA is of 40 MHz.  This is the maximum rate of the input/output of the FPGA (digital i/o).  What you could do is use a method node on the clock line to "wait on a side on the rise", read the data and send the data to a FIFO or DMA.  Put this inside a loop, and you should be good to go.

Tags: NI Software

Similar Questions

  • The precision of a PXI-6602 improve with a PXI-6608 2 driving 10 MHz slot PXI backplane?

    Improve the accuracy of a PXI-6602 module in slot 3 of my PXI chassis if I use the clock of a PXI-6608 OCXO in slot 2 to drive the background clock of 10 MHz of my PXI chassis basket?  If so, how is it improved?  660 x operating instructions shows the bottom basket of 10 MHz clock led the Phase Lock Loop of the 6602, but I don't know how that affects the overall accuracy.

    This will help you.  I think you need to set the reference of your meter to use the PXI 10 MHz clock and the clock of the 6608 of export to the PXI 10 MHz clock.  I managed to get orders of magnitude better measurement of the frequency by doing this (on a signal of very narrow limits).

  • Test Panel does not work with the PXI-6541/6542/6551 in PXI-1002

    Ripping my hair out trying to get the Test Panel can work with system as described below:

    1002-PXI chassis with controller PXI-8176.  In the three places available (from left to right) PXI-6551, PXI-6542 and PXI-6541.  They come in NIMAX, they self test, reset and to calibrate.  But when I try to open a Test Panel, I get an error as follows:

    nidmfpan.exe - Application error

    The application failed to initialize properly (0xc0000142). Click OK to close the application.

    I uninstalled, re-installed, modified and repaired everything NIDAQMX (15.0.1) 15.0 HSDIO, NI-VISA (15.0.1), etc.

    Original symptom is that when I pressed the button on the test Panel, nothing would happen.  Then, the next symptom is that MAX has said MFC90.dll (not found) and MSVCP90.dll (not found) and MSVCR90. DLL (not found).

    I can not find help topics or the forum messages that cover this.  Very annoying.

    Hi fully,

    Sorry to hear that!  Nidmfpan.exe is the process that opens MAX test panels and MFC90.dll is a Windows wrapper.  Combinations of driver reinstall or copy other MFC90.dll files in System32 are unlikely to solve the problem.

    You are on XP?  Try to navigate to C:\Windows\System32 and rename the nidmfpan.exe.manifest to nidmfpan.exe.manifest.back and after close/reopen MAX file and try to open a test Panel.  Is it effective?

    Note that the file you want to rename is nidmfpan.exe.manifest and NOT nidmfpan.exe.

    If not immediately successful, close and reopen the MAX and try the test panels a few times more.  If after several attempts it still does not work and the correct manifest file has been changed, it can point to a deeper problem of Windows that requires a reformatting of the OS.

    Really that's hope!

    P.S. you might get more visibility to a problem as it is in the sections "PXI" or "Digital i/o.  VXI and VME are not widely used these days, so this section of the forums is probably not too much traffic.

  • OR DC Soft Front Panel, minorbug, small bug with the PXI-4110

    Hello

    The NI DC Soft Front Panel V14.0, with the PXI-4110, scrolling to negative tension, works as expected to-10V, but then returns to 0. If we change from - 1V procedure, it goes...-8-9,-10, -1, -2... instead of-8-9,-10, -11, -12...

    Everything about her, a simple thing that I miss is a switch for all three voltages.

    (Also, IMO, it would be logical for negative tensions with the arrow pointing down, not more).

    My 2 c

    Hello Janaf,

    I completely agree with two of your statements, I tabled a report of corrective measures that you can monitor in the next versions of DCPower to see if this is fixed with the FPS. CAR number: 512257

    I've added notes that only manual insertion of numbers - less than 10 works and that it was not logical to use arrow increment or upward arrow to reduce the output voltage.

  • Acquire more than 2047 samples with the PXI-4461 instaled in SMU-1073

    Hi all, I would ask you for help with the buffer limit.

    I intend to buy digitizer PXI-4461 and he instal in SMU-1073 chassis, namely control via MXI Express of Labview installed on a separate computer.

    What I need:

    -to acquire data of a single channel of AI, but at least a sequence of 20 kS by a acquire task, in some situations until 200kS by a task to acquire.

    The question:

    - I can gain more than 2047 samples in a single sequence, like 200kS, with the PXI-4461 installed in SMU-1073?

    Internal buffer of the PXI-4461 is reserved to 2047 samples. So I'm not sure if Labview can download remotely via MXI Express the data in the buffer of the PXI-4461 via MXI Express fast enough without any affection of the sampling program.

    -in the case, this PXI-4461 with SMU-1073 isn't the right combination, what chassis and a controller can do?

    Thanks much for the reply

    Jan

    It will work for you.

    The on-board buffer 2047-sample is used only as a backup if the flow of data to the PC host (via MXI Express in this case) is not fast enough... that it will be (explained below).  DAQmx transfers data from the buffer of the device to the host PC as fast as he can and, in ideal conditions, should not save the buffer 2047 much at all.

    Let's just say you get 110 MB/s (randomly from a MXI data sheet) flow on your MXI connection.  The 4461 has 2 analog inputs, which will be at 24 bits, we just round 32-bit in case it transfers the data in this way.

    4 bytes/sample (32 bit) x 200,000 s/s x 2 (channels) = 1.6 MB/s, which is well below the 110 MB/s, which will make the MXI link.

    clear as mud?

    Germano-

  • Pulse modulated CW with the PXI-5650 and PXI-6653

    Hello

    I'm trying to generate a signal CW of pulse modulated with the PXI-5650 as source RF and the PXI-6653 as the modulation signal. Basically, I'm trying to generate a simple radar waveform. It seems that it would be possible to use the synchronization Module (6653) to transform the RF output on / off on the signal generator (5650), but I do not know how to route the signals from one to another using LabView.

    Has anyone tried this or something like this before? Can anyone please offer some advice?

    Thank you!

    -John

    Hi John,.

    Reading your post, it seems you want to use your calendar and map of synchronization to the RF output power, in other words, on Off Keying. OOK modulation is a feature built into the 5650. For more information, you can navigate through the NI RF Signal generators Help for devices-RF signal generators > NOR -> NOR 5650/5651/5652 overview-> Modes of Modulation and simply click on the Modulation Modes.

    An example of this is found in the example Finder OR by navigating to the help-> find the examples in LabVIEW and then navigate in the Finder to example NOR material input and output-> Modular Instruments-> NI - RFSG-> signals-> RFSG 565 x Digital Modulation.vi.

    Kind regards

    Jason L.

  • Card mother H-IG41uATX HP works @ 1066 Mhz with single 2GB 1333 Mhz RAM

    Hello

    My card mother H-IG41uATX HP works @ 1066 Mhz with single 2GB 1333 Mhz RAM (Apacer PC-10600) @ 7-7-7-20.

    BIOS is Version 6.08, 07/07/2011.

    BIOS it detected as PC-8500. CPUZ shows like PC-10700 work clocked at 533 Mhz (= 1066 MHz DDR).

    The processor is Intel Pentium Core 2 Duo E 8400 3.06 GHz with FSB 1333 MHz.

    WIndows 7 operating system

    1. Why does is not able 1333 Mhz motherboard @ full speed?

    2 working memory @ 1066 MHz @ 7-7-7-20 VS memory work @ 1333 MHz @ 9-9-9-24, which is better?

    Khelifi

    Sure... While theoretically fastest speed of memory should be faster, there is little or no difference in the overall performance of the memory. The memory CASE latency generally increases the rated speed increases. Latency means basically 'backwardness' and this latency to counterbalance the gain by increasing the speed. Still, you would never notice a difference between the two.

    If you have any other questions, feel free to ask.

    Please click the White Star of KUDOS to show your appreciation

  • Synchronization of multiple unit with the PXI-1044-6250 M-6143S

    Hi all

    I have a problem with several device synchronize with my PXI system: when starting a measurement, the devices do not start at the same time despite using a trigger to start. The delay in the start time varies randomly between 150 nanoseconds and about 80 milliseconds.

    My PXI system consists of the following:

    • Controller PXI-8108
    • Chassis PXI-1044
    • 6 * Series S PXI-6143 (Slots 2-7)
    • 1 * Series PXI - 6250 M (8 slots)

    The software in use is LabVIEW 8.2.1, NOR-DAQmx 8.9 and MAX 4.5.  "The trigger line routing" is set to "Dynamic" for all 8 lines.

    I created 3 tasks in the attached VI: task 1 ('Drehimpulsgeber' = encoder, 1 channel, rate: 1.25MS / s), task 2 ("Heißfilme 1-8" = hot-film probe No. 1-8, 8-channel, 250 ksps through rate / s) and task 3 ("Heißfilme 9-16" = hot-film probe No. 9-16, 8 channels, rates by way of 250 ksps / s). 3 tasks are expected to start at the same time acquire the analog voltage by pressing the button "Start". "." As the trigger for the beginning, I use a digital pulse created on/PXI1/PXI_Trig0.

    After reading samples, the first timestamp recorded for each task is retrieved, displayed and the delay time is calculated (see boxes 'Start time' and 'Time Delay' on the front panel).

    How can I optimize to synchronize the start of all three devices without getting this random delay?

    Thank you in advance.

    Kind regards

    Matze

    Hi MatzeK,

    Here's another one. Could you please try this too and send me information on success?

    TomBaum

  • What is the acquisition card OR 1426 compatible with a line/Linear array scanner?

    What is the acquisition card OR 1426 compatible with a line/Linear array scanner?

    I'm currently doing a feasibility study of the project that uses the NI 1426 and a linear Array Scanner acquisition card, and I would like to know if they are compatible with each other.

    Thanks in advance

    Martin

    Hi sandeepchinni,

    I agree with gunnesjr that we need more information about what you mean by Linear Array Scanner.  As he said if it is a scan line or an area then yes it will most likely compatible.  A small correction to what he says.  You need not buy NI Vision if all you need to do is to acquire images.  The framegrabber will be delivered with the software that is needed to work.  If you need to do any image processing then you need NI Vision.  The following knowledge base lists what is installed with the driver for the card.  Live that are installed with OR-IMAQ Vision Acquisition Software?

  • Is it possible to route signals of relaxation between two chassis PXI-1002 with the PXI-8335?

    Hello

    as the subject says, I am interested in the delivery of a signal to trigger between two chassis PXI-1002. At present, these two chassis are connected by a MXI - 3 system using maps PXI-8335. The software is Labview 2010 sp1 and 380 NIScope drivers.

    We want to keep (a PXI-5122 by chassis) scanners supply separated due to the requirements of our measure! The chassis are connected via cable to fiber optic. This explains why I can not just use the shutter release in Star, or connect via 'Trigger' or 'clk' cards (the inputs / outputs to the front of the cards).

    I found a few examples, but they seem to all be designed for use with a chassis only, I'll call later to the examples that inspired me to this point. Each guide explaining the synchronization of several chassis systems seems to use another material or VI is not accesible to me. This makes me wonder if my hardware has the capacibilities I need.

    The first picture shows approximately where I started from (sorry I can't post VI, confidential...):

    Only the middle part is interesting. Two sessions are initialized and manipulated parallel, trigger too. This has led to delays in the signals and should now be fixed. This apart from the VI works fine.

    Goal is to trigger only on one channel but both devices! If possible, the device will trigger must be chooseable.

    I started to rebuild the VI using the "EX Synchronization.vi 5xxx niScope' seeming spontaneity. The result is shown in the following image:

    I tried different RTSI lines, but had no positive results. only the main channel has triggered.

    After this first approach, I looked in the "niScope EX .vi multi-Device configured Acquisition (TClk)" and other examples of TClk which seem to work for similar problems. The VI of reconstruction can be seen in the following images:

    (Sorry, I had to use two photos..)

    In this case, I didn't have no choice for trigger lines, it would automatically set the VI TClk. I tried to trigger on both devices, though. This second approach seemed promising to me, but it was an error:

    "niTClk Synchronize.vi:1".

    Index (starting at zero) of the session: 1

    The error reported by the pilot of the instrument:

    No registered trigger could be found between the
    devices on the route.

    If you have a PXI chassis, the chassis correctly identify in
    MAX and make sure that it has been configured correctly. If you use PCI
    devices, make sure they are connected with a RTSI cable and that the cable RTSI
    is saved to the MAX. Otherwise, make sure that there is an available trigger line
    the trigger bus shared between devices.

    Source device: PXI1Slot4

    Target unit: PXI2Slot4

    Status code:-89125niTClk Synchronize.vi:1

    Index (starting at zero) of the session: 1

    The error reported by the pilot of the instrument:

    No registered trigger could be found between the
    devices on the route.

    If you have a PXI chassis, the chassis correctly identify in
    MAX and make sure that it has been configured correctly. If you use PCI
    devices, make sure they are connected with a RTSI cable and that the cable RTSI
    is saved to the MAX. Otherwise, make sure that there is an available trigger line
    the trigger bus shared between devices.

    Source device: PXI1Slot4

    Target unit: PXI2Slot4

    "Status code:-89125"

    This error came back even after I've identified this drug as possible to the MAX, as shown in the screenshot:

    In some of the textbooks, they showed how to get the MAX trigger lines, but as you can see, there is only booking options in my MAX. Whatever I do, I can't find options to define how to get my trigger signals...

    In principle, it is possible to trigger instruments in different chassis, which is indicated in this Guide and others... the question that remains is can it be done with my set of components?

    I understand that the use of multichassis compromised the integrity of the lines very adjusted as trigger in Star etc., so the configuration should be taken into account in some way, that my approach does not, I knew... But there must be a way to do this? And to start: to get just any signal from one device to the other trigger!

    For any advice on this issue, I would be very thanfull!

    Concerning

    Max1744

    Hi Max,.

    Thanks for the detailed post and explanations of your application and requirements. You're right using TClk, because this is the optimal method to synchronize the 5122 digitizers. The original VI you worked with is unique for some of the legacy scanners and does not directly work with scanners based on the most recent CMS (for example the 5122). The good news is that you can synchronize these cards to separate chassis, but it will use the calendar 66xx and synchronization (T & S) cards in the chassis of the master and the slave, as indicated in the guide that you have accessed. These are needed because a common reference clock must be shared between them as well as a couple of tripping. MXI itself can not handle export triggers and clocks, so there is no way to do this without physically wiring between the chassis with cards T & S. Unfortunately, regardless of what specific method, you use for synchronization, it will take a material extra beyond what you currently have.

    As one of your needs looks like it is necessary to retain wiring between the chassis directly, you may need to consider to synchronize using 1588 or GPS protocols. 1588 Protocol is a system for synchronization on the network while GPS course use antennas and locks for a common wireless signal. Although these synchronization methods may allow you to keep your chassis isolated, they will also require some manual configuration because you would be able to use the TClk synchronization and so the level of synchronization you can get between the cards may not be as good that can physically wire signals between the chassis using T & S cards.

    Hope this helps,

  • Why is relativeInitalX value not taking into account the triggering delay? using scope OR with the PXI-5124

    Hi all

    play with a digitizer PXI-5124 in a case of PXI1042Q with a PXI8110 controller that runs labview 2012 (latest updates) with the latest version of the driver NIScope.

    I put in place an acquisition of off-delay (by assigning the triggering delay, for example 20us) which works very well (I can tell by the signal I get delay control works correctly), but the data returned in the info wfm cluster (using the 2D version of niScope I16 Fetch) does not have this delay.

    Description of the relativeInitialX within this cluster indicator indicates "is the time in seconds between the trigger and the first sample in the acquired waveform" but its never to return something around 1E-9 independent of trigger delay. Surely the relative initial x should reflect the triggering delay?

    I'm doing something wrong?

    Thanks for your help!

    So, I made a screenshot of the image in the section "Trigger Delay" link I sent you.

    Meaning of the symbol:

    T0 = original moment of relaxation

    T1 = time to trigger used in the acquired record (t1 = t0 + TriggerDelay)

    T2 = time of first sample in the record of the acquis.

    RX = relativeInitialX = t1 - t2

    Response to previous reviews

    «I understand what you're saying - so basically, if I want to know the delay of my trigger for the first sample in the record, I just add my delay time value to the relativeInitialX.»

    • Close, the delay of the original trigger (t0), for the first sample in the record (t2), would actually be TriggerDelay-relativeInitialX

    «.. . Nowhere does graphically describe where is the relative value of initialX real. »

    • Right, relativeInitialX is not a timestamp, so it is not a place on the timeline, it is the difference between two timestamps (t1 and t2 above), where the relativeInitialX name.

     

    "The trigger"record"is the straight line in the Middle, so expect relative to - 1/2 initialX record length?

    • Almost correct, because the reference trigger is relativeInitialX to the position of 50%, will be the time in seconds for 1/2 the record length. (i.e. If the registration has been long relativeInitialX, 2s = 1 s).  RelativeInitialX will always be the delta time between the trigger (t1) and the first sample returned in the record (t2).

    • For example using the picture above: If t0 is 10 sec, Trigger Delay = 3 sec, SampleRate = 1 kHz, = 1000 record size.  This means that t1 = 13 s.  Our record is long of 1s (1000 points to 1 DC between each = 1 s), if t2 = 12.5 sec.  If away from all these moments are absolute time, as the timestamps.  So relativeInitialX = t1 - t2 is 13-12, 5 = 0.5 sec.

    • As a side note, the reference position should not be 50%, you can configure to between 0-100%.

    Time not yet discussed record attributes

    I don't want to make you more confused, but there is another useful attribute in the waveform info that we've not yet discussed and its AbsoluteInitialX.  Starting from the NOR-SCOPE help file:"absoluteInitialX is the timestamp of the first sample of recoveries in seconds..." "So, using the above image, absoluteInitialX = t2.

    I hope this helps.  If a part is still not clear, let me know.

    -Nathan

  • Trip trying to rearm with the pxi-5122 times

    Hi all!
    This is my first discussion in this forum so I'm not sure this is the right place to post, because I'm using LabView, but maybe it's a hardware problem.

    Then... I have a problem to calculate the tripping time rearm to pxi 5122.
    Compared to data sheets, I read that it should be about 3 us with the CDT to the large or 12 US if on.
    But I need a precise measurement of the time out after each record measured so I decided to find it by myself...
    With the help of an acquisition program that I have previous written in LabView, I started only acquisitions of 10000 records and each record is composed of 128 samples; as signal I've used waves square with different frequencies, 10 volts peak-to-peak (my trigger was set on the first channel of 5122 with 1 volt in value of edge).

    First acquisition: wave of 50 kHz. Theoretically, I s 0,2 need to capture 10000 records without losing all the square wave signals. Choose a time of acquisition for a single record of 15.3 us, I found that the time required is 0.199998 , very similar to the one expected.
    Then by choosing a time of acquisition for a single record of 15.4 us, I found approximately 0.4 s.
    I can guess that this latter one each tops of two waves will lost so I held twice the capture of 10000 records time.

    Because the wave is 20 us I calculated a timeout of 20-15, 3 = 4.7 us.
    It wasn't like the 3 described us for the 5122 but I was not impressed and I went with my essay.

    Second wave: 20 kHz. I need 0.5 s to capture 10000 records without losing the square wave signals.
    What I found was that in this case, choose us an acquisition time for one record of 39.6 required 0.5 s to capture all vertices, then with 39.7 us I held about 1 second, once again, twice by the time.
    The previous example, I calculated the dead time: 50-39, 6 is 10.4 us.

    Very strange... idle time I'm supposed to be the trigger for rearmament (and thus fixed) did not differ in 2 cases.
    Tried with other wavelengths, the values are always different.

    This also the frequency of the square wave of fixing and changing the number of samples per record.
    For example, with 128 samples per files as I told before, I needed a measurement time of 15.3 US to collect all the consecutive summits, while 64 samples I need 12.8 us and so forth.

    So it seems to be a dependency between the dead after a record time (the trigger reset? now I'm not sure if I can call it that) and the sampling frequency of the pxi 5122.
    But I don't know why, the acquisition of data behave in this way.

    Is this good? Rearm time should be set, shouldn't it?

    I know it took some time to read my problem but I tried to be more precise, I could.
    Thank you in advance.

    Giacomo

    Yes that's correct.  However, I do not think that its acceptable rate of the nearest synchronization that is chosen.  I really think he goes to rate lowest according to acceptable timetable.  So, if a synchronization rate is 2 and another is 5, and you want a 4.9uS rate, the synchronization will be 2, while 5 is the closest.  (Or maybe it's the other way around)  That's why you see the double period during the change of rates by just a fraction.

  • Acquisition of CVI HSDIO (NI6541) with external flash

    I use NI6541 for interfacing with a Component Manager (I know... too much... but it is available).  I would use 4-bit trigger output and 12 bits as gain entry.  And an external signal as a trigger/pause of entry.  The Manager of signals to acquire ~ once every 100ms.  On this event, I want to read/fetch the 12 bits and about 100 ms later write the 4 bits.  I can't find the code example that is very close.  I know that I have no doubt that you want to run the clock acquire max 50 MHz and pause/relaxation allows to acquire the minimum (2?) samples.  And I would use the trigger/break signal to trigger an event as CVICALLBACK; or a means of BLOCKING DO NOT read the acquisition pending... I have other tasks to do.  Can you give me give me advice?

    Hey bjasper,

    Without a fast PC, you would probably look at dynamic acquisition. You mentioned that each signal could happen without the other or a combination of both. This means that the only time where you do not want to trigger is when all channels are void? You can watch using niHSDIO_ConfigurePatternMatchRefTrigger. One of these entries is "trigger when. If we set this parameter to NIHSDIO_VAL_PATTERN_DOES_NOT_MATCH (37), the program can be set to trigger when the lines go high. In this way, if channel 3 is going high, the model no longer fits 0 so it triggers. If all of them go up at the same time, the model does not and it triggers.

  • Satellite A100: Parallel Port to USB with Vista printing error

    I have a new laptop Toshiba A100 with Windows Vista installed. I can't make my printer A3 HP works via USB with a USB/parallel cable.

    Vista recognizes the connection and says driver installed. Try to print, and it just says: "error" Vista will not let me load the driver supplied with the connecting cable. Anyone got a solution for this?

    Hello

    Are you sure that the driver that came with the connection cable was designed for Windows Vista?
    I assume that the driver is compatible with early versions of Windows like XP.

  • Satellite M70: Memory 533 MHz with 667 Mhz compatibality?

    Hello
    I bought the new Satellite M70 (PSM70) 1.7 Ghz (400FSB) with the construction of memory DDR2 PC2 512 MB 533 MHz, if I DDR2 1 G 667 Mhz added to it? the Mhz will be a problem? and why the standard memory 533 Mhz and 400 Mhz processor speed?

    Kind regards

    Hello

    In my view, you must use the Toshiba recommended of the memory modules.
    AFAIK you can use DDR2 modules like these:

    DDR2 -400/533 256 MB (PA3389U - 1 M 25)
    512 MB DDR2-400/533 (PA3412U - 1 M 51)
    1 GB OF DDR2 400/533 (PA3411U-1M1G)

    To my knowledge, the device supports:
    Intel Celeron M up to 1.7 GHZ 0.09u CPU, 1 M L2, at 400 MHz FSB
    Intel Pentium M CPU up to 2.26 GHZ 0.09u, 2 M L2, 533 MHz FSB

    Therefore, it is possible to use 400 and 533 MHz memory speed.
    You can also use the modules of Kingston. The performance is optimal.

Maybe you are looking for

  • Internal error in safari on download (navigation finder via safari)

    Hello I have a problem with Safari. Whenever I try to send, or upload a file, or just browse the finder (see imageView imageView imagehttps://www.google.co.uk/url?sa=i & rct = j & q = & esrc = s & source = image & cd = & cad = AJLN uact = 8 & ved = 0

  • Samsung tab 3

    I have a tab 3 the Samsung Galaxy, Android tablet.  My kids gave it to me so I can work in my bed and must make the dangerous descent to my computer room in the basement, in my old age.  I have a printer HP Deskjet 2543 downstairs.  My eldest son put

  • HP pavilion g6_2260us

    Hi guys,. I have a few drivers not installed on my laptop.   I'm on OS Win7 (32 bit) on my laptop.   Missing drivers are: 1. PCI device; 2 SM controller; and 3. USB controller. Grateful for your help. Kind regards Shawn

  • Compaq Presario V3745TU: Upgrade the hardware of Compaq Presario V3745TU

    Hello My Macbook Pro have hardware problem and I had sent to Apple. It would take time to repair. Luckly I have an old computer for temp use. I had to format the drive and reinstall the OS, but it works still slow. So, I want to update my old compute

  • How to clean this gui

    Hi all I am working on a template, that someone has already done. I would like to know how to make clusters to look like the one on the left side. Any tips? Thank you.