PXI-1052 not detecting SCXI chassis

Full disclosure:  I've submitted a support request on this too, but knowing that it may take some time to go through I thought I'd ping the discussion boards for any ideas people here might have as well.
I have a PXI-1052 PXI/SCXI combo chassis with a PXI-6289 card serving as the SCXI controller. Up to this point, the chassis has been controlled by a PXI-8105 embedded controller running WinXP. We are changing this. The PXI-8105 controller is being removed and instead we will use an MXI card (PXI-8360) to allow us to control the chassis via an external computer running Win7 32-bit.
With the chassis on and connected, using the Win7 computer I can see the PXI slots and the cards in them are correctly identified by model number. However, I cannot see the SCXI portion of the chassis, and when I try to manually add an SCXI chassis I am told that there is no DAQ device installed to serve as the SCXI controller. In addition, the PXI-GPIB card which is also installed is acting a little strangely. It allows me to scan for instruments, and it sees all of my GPIB instruments OK, but I don’t see a GPIB bus defined separately under Devices and Interfaces the way I did on the old controller—the instruments just show up listed under the PXI card.
I have read the Knowledgebase article on auto-detecting SCXI instruments, but it doesn’t seem to offer anything helpful. Everything works fine if I put the old controller back in and use it again, so this isn’t an issue of a bad card/chassis or the wrong card or a blown fuse or SCXI power not being on/set correctly or the DAQ being in the wrong slot. (The ONLY hardware difference is the controller being replaced by MXI; everything else is exactly the same.) All NI software on the Win7 machine is installed and up-to-date, and I even reinstalled everything just to make sure I hadn’t gotten a bad install. It seems to me like it must be either a driver or a configuration issue, but I’ve combed through the Windows Device Manager and the settings for all cards involved and can’t find any differences.
Screen shots attached.  Any ideas?
Solved!
Go to Solution.
Attachments:
Win7.png ‏109 KB
winXP.PNG ‏73 KB

Hello Sara_J,
I'm going to post to the forums with my suggestions from my email so that if we find the answer it will be available to the community as well.
As long as the 6289 is showing up incorrectly you're not going to be able to use the SCXI side of the chassis. The problem looks like your 6289 is not being associated as a DAQmx device. The alias it has in MAX is showing it as a generic VISA device. You'll have to manually associate the 6289 in device driver. Normally it would show up under Data Acquisition Devices with the NI logo in Device Manager. Since its not showing up correctly it may be located elsewhere, most likely under a PCI Standard PCI-to-PCI bridge (this is how the MXI card looks in Device Manger). 
Once you find it, right click and select Update Driver Software...>>Browse my computer for driver software>>Let me pick from a list of device drivers on my computer. You should then be able to pick the appropriate driver from the list. 
If this does not fix the issue then I believe there may be a corruption in your installation of DAQmx. You can download the newest version (9.9) here: http://www.ni.com/download/ni-daqmx-9.9/4707/en/ . 
Jonathan L.
Applications Engineer
National Instruments

Similar Messages

  • PXIe-1073 not detected

    I'm trying to install a PXIe-1073 chassis on a new Dell system running Windows 7 x64.  I have the latest version of Labview, NI-DAQmx, etc.  The PCI express controller shows as properly installed in the Device Manager ("PCI standard PCI-to-PCI bridge").  The chassis and installed DAQ card are not detected in MAX.
    I am actually transferring this system from an older computer.  I recall having exactly the same problem before, and I'm fairly certain I solved it by installing the "MXI-Express BIOS Compatability Software".  There was never any way to actually identify the "PXI System" as anything other than "External PC" even when it was working properly.
    After installing the current version of the MXI-Express software, I rebooted and was able to load MAX briefly before Windows BSODed with an error involving "niraptrk.dll".  This proceeded to occur every time I tried to load Windows.  I was able to start in safe mode, but attempting to uninstall any NI software gave me an "error 1601".  I was finally able to load the last known good configuration and uninstall the software.
    When I checked MAX again, the chassis was still unrecognized, but there were multiple broken entries for the DAQ card installed in it, so I assume it was detected at some point.  It looks like the MXI-Express software worked, but it's obviously unusable if it causes the computer to BSOD every time Windows starts.  Why is the computer unable to recognize the chassis without it?  What else can I do to solve the problem?

    Hello Bob_mcbob,
    After looking over this issue, I think we have a problem with the Windows installer on your machine. I have found a KnowledgeBase about the Error 1601 stating that this is a Microsoft Windows installer error and that the installer will need to be reinstalled. The Knowledgebase explains how to do this.
    As for the BSOD, do you have any more information that it provided when this occurred like the address line, etc? Did you do something in MAX before it crashed?
    Since accessing MAX now gives you a BSOD, I think it would be best to uninstall/reinstall the drivers to fix the issue. What cards do you have in this system?
    Jim St
    National Instruments
    RF Product Support Engineer

  • NI PXI-1033 not detected if turned on after PC

    Hi,
    I noticed that MAX does not detect the presence of the NIPXI-1033 if it is turned on after the PC.
    There is a programmatic solution to resynchronize the device? My application using C # and C + +.
    thanks
    Roberto Guerzoni
    Solved!
    Go to Solution.

    Thank you Roberto
    It is normal what happens. Your PC has to see the device during the boot up. It is a BIOS matter. 
    Have a great weekend!
    Antonios

  • PXI cards not detected

    I'm using SignalExpress with a NI PXIe-1062Q chassis and the following cards:
    PXIe-8360
    PXI-4071 DMM
    PXIe-6556 waveform generator/analyser
    PXI-4110
    All cards are detected by NI MAX. However when I create a waveform in SignalExpress, it's unable to see my hardware. It can see the 4071.
    I'm following the correct startup procedure of booting the chassis first, then booting my PC.
    Any suggestions?

    Hello AidanFrost,
    The reason for this could probably be that you may not have the correct drivers installed. Which drivers do you have on you computer at the moment ?

  • PXIe-1073 sytem not detected

    I connected a PXIe-1073 system (PXIe-6363 and PXI-2567 connected) to the PC (running Windows 7) and the PC does not detect the chassis. It started happening when I recently upgraded to LabVIEW 2013 and NI-DAQmx 9.7.5.
    I also installed the MXI BIOS compatibility software Ver 1.4, changed the DIP switch1 to ON position on the MXI express card 8361 and rebooted the computer. That did not solve the problem.
    Then, I upgraded to PXI Platform services 3.2.3 and restarted the computer. I still don't see PXI system recognized in NI MAX. When the computer was restarted, the 8361's MXI card's switch 1 was still in ON position.
    Any ideas on how to fix this issue ?
    Thanks
    Jeet

    Hi Matt
    Sorry for delay in replying.
    After a lot of uninstallation/installation/repair of different driver versions, i have currently got the following software (see attached pic): NI-DAQmx 9.5.5, Ni PXI platform services 3.2.1.
    In the picture, you can  see that all my cards are detected in NI-DAQmx devices as Dev1, Dev2 etc.
    My PXIe-1073 is not detected or listed in MAX. I expect to see chassis controller detected and all the cards listed under the chassis controller as "PXI2slot2" device or "PXI2slot4" device etc.
    The attached pic shows NI-MAX and device manager snap shot.
    Please advise.
    Thanks
    Jeet
    Attachments:
    nimax dev man.jpg ‏316 KB

  • SCXI-1102/SCXI-1303 not detected in SCXI-1000 chassis

    I am using a setup with SCXI-1303 module in a SCXI-1102 within a SCXI-1000 chassis to take voltage and thermocouple measurements.
    Until recently, everything was working fine. but it now appears I am unable to communicate with the interface. I have tried two different computers and the hardware is not detected in MAX. The power light and fan on the SCXI-1000 still comes on, there just appears to be no acknowledgment of the connection to the computer.
    A few more specific error codes:
    * When I double-clicked the DAQ Assistant in the block diagram window and clicked "Test" on one of my inputs, I received the following error:
    "Error -88705:The specified device is not present or is not active in the system."
    * I have also gotten the error code "Error -89130: Device not available in NI-DAQmx" in the DAQ Assistant test panel
    * When closing the DAQ Assistant test panel, I see the error "Error -89130: Device not available for routing"
    * In MAX, if I try to "test" the chassis or module, I have seen errors either saying that the device is not detected, or that the device needs to be reset or is in the process of being reset, or that Traditional DAQ drivers need to be reset (I've tried these reset suggestions with no result)
    At this point I'm wondering if the board or the cable is shot. I unfortunately don't have another 68-pin cable to test at the moment.
    Thanks in advance...
    Solved!
    Go to Solution.

    mtd12 wrote:
    Thanks guys, I was able to resolve the problem. For anyone who might come across this,
    * I noticed in Windows Device Manager that two PCI devices were listed as not being installed properly.
    * After trying to update the drivers, I couldn't start the computer; got BSOD after BIOS load.
    * Some research prompted me to pull out the two PCI cards that I was not using, and I also moved my DAQ card to another slot to force a hardware reinstall.
    * Booted up, loaded the drivers automatically, and off I went.
    Doesn't explain why it didn't work in the other computer, but in the words of Spinal Tap, the authorities said it was better left unsolved at this point.
    You should move the DAQ board back and verify whether it still works. Perhaps one of the slots went bad.
    You didn't notice that you had two PCI devices that were not installed properly before?

  • PXI-8532 DNET card is not detected in MAX

    Hi all,
    I'm using NI PXI-1031(4 slot PXI chassis). I have the following cards in the respective slots
    Slot 1= PXI-8106 Controller
    Slot 2= PXI-6259 card(AI)
    Slot 3= PXI-6509 card(DI,DO)
    Slot 4= PXI-8532 Card(DNET)
    In MAX(Measurement & Automation Explorer), I was expecting all the above cards(PXI 6259, 6509 & 8532) to be detected under Devices and Interfaces. But only the AI and DIO cards are detected in MAX under Remote Systems>>PXI>>Devices and Interfaces.
    PXI-6259 (PXI1 Slot2)
    PXI-6509 (PXI1 Slot3)
    The device net card, PXI-8532 is not detected in MAX. Does MAX shows/detects the DNET card?
    In MAX, I selected Tools menu>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, I pressed OK. A message appears that no device is found.
    Can any one help me how to detect the DNET card in MAX and do the DNET port configuration?
    DNET driver version - 1.6.4
    Thanks,
    Raja
    Solved!
    Go to Solution.

    Dirk,
    Thanks for the reply. After updating the new driver, I am able to detect the DNET card PXI-8532 in MAX
    New driver - NI-Industrial Communications for DeviceNet 2.1
    But Im not able to configure the Device Net port. In MAX, I selected the menu option Tools>>NI-DNET>>RT Hardware Configurations. Then a window prompts for RT IP address. After entering the IP address, a message appears that no device interface is found.
    By default, the DNET0 port is configured for the card in MAX. So I tried to communicate from LabVIEW using DNET0 port.
    After installing Devicenet 2.1, an additional function palette has been added for DNET in LabVIEW.
    Old DNET function palette - Instrument IO>>DNET
    New DNET function palette - Industrial Communications
    My original application was written with old function palette VIs which corresponds to DNET 1.6.4 version. In the download link that you shared has a description about the driver compatibility. The description says still the DNET card PXI-8532 is compatible with NI-DNET 1.x LabVIEW VIs.
    With the old DNET VIs, I tried to establish communication with DNET interface port "DNET0". But it shows error while opening the interface.
    Error Code ="-1074388957" - The Interface is invalid or unknown.  Solution: Verify that the interface is assigned to a specific port within the Devices and Interfaces branch of the Measurement and Automation Explorer (MAX).
    With the new DNET VIs(DNET 2.1.0), Im able to open the DNET interface successfully. But my original application was written in Old DNET VIs (DNET 1.6.4).
    1. Do you know why the DNET 1.6.4 LabVIEW VIs are not working with PXI-8532 DNET card?
    2. Can you help me how to configure DNET port in MAX for PXI-8532 DNET card?
    Thanks,
    Raja
    LV 2009, Windows XP

  • Verify SCXI chassis: Configurat​ion specifies a SCXI -1600 module but nothing was detected

    Hello NI Engineer,
    I am using SCXI 1001 chassis with SCXI 1600 control module, SCXI 1520 signal conditioning module and SCXI 1314 connector block to acquire data from strain gage. Once I right clicked SCXI 1001 under device and Interfaces in MAX>> test>>I found a pop up window as “Verify SCXI chassis: Configuration specifies a SCXI -1600 module but nothing was detected”.
    This is what I did.  I connected wires from strain gage to SCXI 1314 connector block which is then connected to SCXI 1520, placed in chassis. I connected SCXI 1600 controller module to computer using a USB 2.0 cable. As soon as I switched on chassis, I found a pop up at task bar as “SCXI 1600 is detected”. I opened MAX and right clicked NI SCXI -1001 under devices and interfaces>> Properties>>selected the accessory under module tab and got “Configuration complete” message at top of pop  up window, But once I right clicked NI SCXI 1001 >> test >> I found an error as mentioned above. Also once I right clicked NI SCXI 1520, under NI SCXI 1001>> Configure TEDS>> I was not able to click scan for HW TEDS option (i.e. It’s not shown up). How to overcome these two errors? Please help me. I also attached screen shots with this. I am using windows XP.
    Thanks
    Dhaya.
    Attachments:
    Error pic 1.JPG ‏115 KB
    Error pic.JPG ‏97 KB

    Hi Dhaya,
    You seems in the correct direction to configure the SCXI hardware. There is nothing to test on the SCXI-1001 chassis instead you can test on the individual channels inside the SCXI. SCXI 1600 will auto detect the modules inside the SCXI Chassis and display it in MAX. The next step that you may need to do is to configure the Accessories (Connector Block) that is attached to the SCXI-1520 mentioned.
    Once you configure the connector block, you should be able to test SCXI-1520 channel.
    In regards to TEDS, Are you using SCXI-1314T connector block (http://sine.ni.com/nips/cds/view/p/lang/en/nid/137​35) which is for TEDS sensors?
    I hope that this helps
    - Meadow -
    LabVIEW 7.0 - 2011, Vision, RT, FPGA
    TestStand 3.0 - 4.5

  • NI Scope Sorf Front Panel will not detect NI PXI-5122

    Hello,
    I am trying to use NI Scope Soft Front Panel 2.7f0 to acquire simple waveforms;
    however it will not detect my NI PXI-5122. I have confirmed that the digitizer
    works under MAX 4.2.1 and can see waveforms under the test panel. I have
    installed NI Scope 3.3.1 on my machine and have updated the driver on the PXI
    to version 3.3.1. Any ideas on what is wrong?
    ~Buck

    It is unclear from your post whether or not the 5122 is on the same physical device as you are running the soft front panel (SFP).  The SFP only works on local devices.  It does not have the capability to attach to RT or remote systems (MAX does).  However, if you are running Windows on your PXI controller or are using MXI to control the chassis, there is another issue.
    This account is no longer active. Contact ShadesOfGray for current posts and information.

  • PXI-6602 is not detected by M&A

    Hello,
    I have a PXI-1033 (integrated MXIe card) chassis with a PXI-6602 module installed in it.
    Measurement & Automation Explorer shows only PXI System (Undifined), please see attached file (1.jpg). In the list "Identify as" I can not see NI-1033 controller. Before that I have installed software form "NI PXI Platform Service". When I choose NI-1033 controller from CD the message "could not import controller information" is appeared, when I choose any other controller, Measurement & Automation Explorer shows "chassis" which I can identify as PXI-1033. But there is no possibility to detect PXI-6602 card by Measurement & Automation Explorer.
    System information: Win XP, LabView 8.5.1,NIDAQ922f0 drivers are installed.
    So, the questions:
    1. Why there is no DAQmx branch in Measurement & Automation Explorer tree with PXI-6602 card? 
    2. How can I test my PXI-6602 card (it absolutely new, but...)?
    3. How it is possible to install correct controller for PXI-1033 chassis?
    Thank you.
    Attachments:
    1.jpg ‏141 KB

    Hello,
    the problem discussed in the previous message was fixed and here is the solution:
    After additional investigation it was found that the issue is with "This device cannot find enough free resources that it can use. If you want to use this device, you will need to disable one of the other devices on this system. (Code 12)". This topic was discussed (http://digital.ni.com/public.nsf/allkb/04C12CB4A5143ECC862572DC007B8DF6). But it did not help. I updated the BIOS in my Laptop (Dell Vostro 3300) from A05 to A09 version. But it did not help again.
    After that I found a "MSI-Express BIOS Compatibility Software". Installation this software fixed the problem.
    Hope this information will be helpful.

  • Can't configure a SCXI chassis (PXI-1010) with a PXI-8176 and a PXI-6052E.

    I have a PXI-1010 chassis with a PXI-8176 running Windows 2000. In the rightmost PXI slot, I have a PXI-6052E. The remaining PXI slots are either empty or have misc. modules in them. I have a SCXI-1520 in the leftmost SCXI slot.
    I am trying to get MAX to recognize my SCXI chassis with the SCXI-1520. When I try to add the SCXI chassis in MAX by right-clicking "Devices and Interfaces" or "NI-DAQmx", I leave the communication mode to communicate on the PXI backplane, choose SCXI slot zero, and find that the communication device field is greyed out where I want to choose the PXI-6052E. For some reason,the wizard used to add an SCXI chassis does not see my PXI-6052E pluged in to the leftmost sl
    ot. Strangely, MAX does see the PXI-6052E in the "Devices and Interfaces" tree. I verified that the 6052E is working correctly. I also verified that the pxisys.ini file is in the WINNT directory. What is the problem?

    I am first trying to install the SCXI chassis using the SCXI 1520 user manual. I put a PXI-6052E in the right-most PXI slot and the SCXI 1520 in a SCXI slot. On page 1-12 of the SCXI-1520 user manual, it instructs me to power up the chassis, right-click on MAX "devices and interfaces", choose the correct chassis, and click finish. The problem is, after I click finish, a window appears that forces me to choose a DAQ device. The SCXI chassis doesn't configure correctly because the wizard doesn't see the PXI-6052E.

  • MXI3 (NI PXI-8330) board not detected. Not powering up, no link light.

    MXI3 (NI PXI-8330) board not detected. Not powering up, no link light. Cable looks fine. Any ideas?

    PeteMan,
    I will need to know in more detail how your system is behaving to give you better tips, so please feel free to send me more information.
    For now, let me send you a couple of troubleshooting tips:
    Cable connection
    Make sure both ends of the copper cable are well connected to the PCI-MXI-3 and the PXI-MXI-3 boards. Be careful when disconnecting the copper connectors. you need to push down the plastic connector so it does not get damaged. Damaged connectors could result in bad MXI-3 links.
    If the connector has not been used properly, it could be broken (this rarely happens). Make sure you are not connecting the cable backwards.
    Power - Up order.
    It seems you are controlling your PXI chassis using a PCI-to-PXI extender (copper cable). Make sure you are powering up the PXI chassis BEFORE powering up the PC.
    PXI is built on top of the CompactPCI spec, so it uses the PCI high speed bus. The MXI-3 extender is really a PCI-to-PCI bridge toyour computer, so for your PC, all the slots in the PXI chassis look like more PCI slots. In other words, your computer suddenly has more PCI slots.
    It is very important to power up the PXI chassis first before powering up the computer, because at power up the PC enumerates all PCI slots. If the PXI chassis is OFF during boot up, the slots in the PXI chassis will never get enumerated and your PC will never see the board installed in the PXI chassis.
    Normal Power up LED sequence
    Each MXI-3 board has four LED light on its front panel: two green lights (POWER and LINK) and two orange lights (Tx and Rx). When you power up the PXI chassis you should see one green light and one orange light ON steadily (POWER and ). Then, when you power up the PC, both green lights shoudl be ON steadily and the orange lights shoudl flicker.
    If you do not see this behaviour at power up, most probably one of your boards its damage.
    If you have another MXI-3 extender kit, try to set up the system mixing the boards from the two kits to try isolate which board is the one that is damaged.
    Run the MXI-3 Optimization Software
    The MXI-3 Optimizaton Software makes sure that the link between the PC and the PXI chassis has been set up properly. It will show you an error otherwise.
    MXI-3 Software Version 1.15 for Windows 95/98/NT/2000/ME
    The PC powers up fine if the PXI chassis is OFF, but if I turn on the PXI chassis first and then try to power up my PC, my PC does not boot
    There are several things that could be causing this behaviour:
    It could be that your PC has an old BIOS that has issues detecting PCI-to-PCI bridges. You could try upgrading the BIOS.
    A part of the hardware could be damaged. If you have a main-stream computer (like a DELL or HP PC, for example), test your MXI-3 extender in it to make sure that the hardware is in good conditions. Main-stream computers tend to use new Motherboards with good BIOS.
    There are more tips in the following KnowledgeBase:
    KB 267FAS5P : MXI-3 Troubleshooting Guide
    Hope this helps,
    Claudia Lorente
    Applications Engineer
    National Instruments
    http://www.ni.com/ask

  • Pxi cards on 1000b cahssis not detected under windows 98

    my mxi-3 card is being detected on windows startup (mxi-3 optimization software is running correctly) but all other pxi cards on my 1000b pxi chassis are not detected.

    Anis,
    Well, I always prefer to try the simplest things first. In this case, that would be fully powering down the chassis and the computer. Then powering on the chassis first, and a few seconds later, powering on the computer. If this doesn't help, then you would probably want to try any or all of the following troubleshooting steps to try and isolate the problem:
    - Try removing all but the mxi-3 and one other card from chassis and then try booting up.
    - Try placing the pci mxi-3 card in a different slot in the computer.
    - Try uninstalling and reinstalling all the NI software on your computer. (better yet, format and reinstall).
    - Try the pci mxi-3 card in a different computer.
    - Try a different set of mxi-3 cards (if available)
    - Check
    device manager to see if there are any errors or warnings.
    So those are the things that I would try. If after all that you still have no luck connecting you may have a hardware problem and need to RMA (Return Materials Authorization) your hardware.
    Please post back with what you find.
    Regards,
    Jed R.
    Applications Engineer
    National Instruments

  • MXI-3 interface not detected?

    Hello to you all,
    I was using PXI/PCI 8335 with PXI 1000B chassis. Everytime I run the MXI-3 optimization it says MXI-interface not detected.
    I checked the LEDs.
    For PXI-8335, the PWR and RX were both solid on, one green and the other orange. For PCI-8335, the PWR and TX (nor sure it's TX or RX, just the one in the same row with PWR) were both solid on, one green and the other orange.
    No LINK light.
    The whole system was powered in proper sequence and the fibre optic cable was fine.
    So there seems to be something wrong with the cards.
    I was wondering is there any way to know particularly which one of PXI-8335 and PCI-8335 doesn't work well without replacing them one by one, since I don't have any extras?
    Like, does the LED tell other information except they are not linked?
    Thank you in advance.
    Yaqiong

    Yaqiong,
    In general you can't differentiate between a bad transmitter on one side or a bad receiver on the other, so it's often hard to tell which side is bad.
    In your case, it sounds like one side or the other has a broken transceiver.  Power and RX on both sides means the boards aren't communicating at all, meaning a transceiver is bad, or a cable is bad in both directions, or a cable is not plugged in or is plugged in backwards.  If you power it up without a cable you should get the same LED behavior -- PWR and RX, the two LEDs next to each other.
    If that's the case (same LEDs without a cable as with a cable), you should be able to tell which card is bad if you connect both ends of a half cable to one card (a loopback).  On a working card connecting RX to TX will "link" to itself according to the LEDs (at least it did for me on both the PCI and PXI card).  On a broken card you'll get something else.
    - Robert

  • Which is better, many PXI cards or fewer PXI cards with more SCXI cards?

    I have a pretty basic question.  Which is "better", using multiple PXI cards for analog inputs or a single PXI card and multiple SCXI cards?  For example, if I have say 100 channels to sample (all at the same rate), I could use 2 6225s at 80 ch each.  Or I could use 1 6220 and 4 SCXI 1100s (32 ch each).  What are the pros and cons with either approach?  Keep in mind sample rate probably isn't an issue (less than 1 kHz) but it is the same for all channels.
    Thanks.

    The pros/cons will depend on your application now and in the future.  I recommend contacting your local NI sales representative.  Synchronizing across a PXI system is easy to do via the backplane.  There are PXI/SCXI combo chassis available, you could use PXI multifunction DAQ cards and then SCC for signal conditioning for thermocouples for additional functionality later.  There are many possibilities that may be best discussed with your sales representative.
    Regards,
    h_baker
    National Instruments
    Applications Engineer
    Digital Multimeter Resources

Maybe you are looking for

  • What is the maximum file size allowed by Yosemite's Archive Utility?

    I've seen radically different answers to this question, ranging from ".zip files have a 4GB size limit" to "no limit other than the OS maximum file size". It's been very difficult to find current info on this. I have lots of large folders full of rec

  • HDMI cable required for importing?

    I'm using FCE4. iMac's don't have HDMI inputs. If I use a Canon HV20 and I shoot in HD does that mean that I cannot capture the footage at full quality using a firewire cable? Does it matter if I use firewire 400 or 800?

  • Can I use more than 1 camera with EOS utility simultaneously?

    I have to manage 5 canon cameras to make them shots simultaneously. Is it possible to do this? Thanks.

  • Need a good IDE

    can someone tell me a good IDE for developing servlets and Jsps,

  • MacBook Air and older iPods?

    My MacBook Air did not seem to take a liking to my original U2 Special Edition iPod when I grabbed it this morning, stuck a USB connector cable onto it and plugged into the Air, intending to use it as a disk drive and drag some tracks onto it to stic