Pxi ethernet streaming

hi
i want to know if anyone has experimented with streaming using ethernet on a PXI(e) platform? i want to stream from a 100 Msps PXI digitizer to a non-pxi PC?
what are the issues at hand...?
currently my system is windows XP, ethernet gigabit on a host controller... i have also looked at PXI 8234..although for vision applications...could it be used...although i will have to get it..donot have it right now...
can anyone explain to me as well, how the data is routed from host digitizer such as 5122 - PXIe bus-controller-ethernet...etc
it would be a great help
thanx

Hey Dannn,
Streaming data via ethernet is realatively straightforward.  On your non-PXI chassis, are you running Labview there? The starting point is to check out the data server-client example that is available with the Labview distribution.  If you are looking for high performance, Simple TCP-IP Messaging (STM) API that has been developed by NI.  This API abstracts some of the basic tasks that you will always be doing but not to the point of Shared Variables (which seem to have a lot of issues).
I can't think of any gotchas that you have to look out for.
Hope this helps.
Matt
Matt Richardson
Certified LabVIEW Developer
MSR Consulting, LLC

Similar Messages

  • PXIe 8262 streaming performance with HDD 8264 on a PXIe 1062Q chassis

    Hello,
    I have a PXIe 1062Q chassis, running Win XP, with one 8262 connected to an HD8264 and two PXIe 6537 installed, all the three board being on the express slots (3, 4 and 5). Running the benchmark application for testing the streaming speed (Win32FileIO) I get something like 100 MB/s with data chunks of about 4 MB, and around 140 MB/s with chunk of 64 M. How can improve these results toward the theoretical limit off 600 MB/s? Is there any software/driver trick to be applied?
    And, in case, which is the best way to exploit the 8262 from C++ written code (using the NI libraries)? Is there anything similar to the Win32FileIO library? I tried using the RAID system from a c++ test program, and the performance seems very poor, while I would need, if not the 600 MB/s rate, at least something around 200 MB/s of continuous streaming.
    Thanks in advance,
    Piero.
    Solved!
    Go to Solution.

    Hi Neil,
    I actually have a 8130 controller, and in fact that was not the problem: I found the problem being the file-caching performed by Windows file system. If you use standard fstream calls from C source code you cannot bypass it, but by using Windows native call (CreateFile(...), WriteFile(...) APIs) and setting the flag for no data caching or buffering inside the call, I managed to get the full bandwith of 600 MBytes/s.
    Anyway thanks for the quick reply!
    Piero
    I'm guessing you have a controller that only
    supports x1 PCI Express.  The PXIe-8130 is our highest-bandwidth
    controller, with four x4 links going to the chassis.  In the case of
    the 1062, each of slots 3, 4 and 5 get a dedicated link from the
    controller.  x1 links max out at about 200 MB/s and x4 links max out at
    800 MB/s.
    So your first step is to use an embedded
    controller or use MXI Express x4 instead of x1 back to a host
    computer.  While the PXIe-8130 is the best for high-bandwidth data
    transfers, the PXIe-8106 should also be sufficient for your needs.
    If
    you want to stream data to disk from a PXIe-6537, it is already built
    into DAQmx.  You simply specify a file name, and the data goes to
    disk.  If you want to stream *from* disk, you'll have to do that on
    your own.  Here is a C/CVI example for streaming digitizers to disk
    using a C API and the Windows File I/O functions.
    Neil
    Principal Engineer
    National Instruments

  • PXI ethernet activation requires initializing motion control?

    On a PXI with multiple 7344 motion control cards and an ethernet LAN connection, ethernet does not become active (e.g., flickering LED on the PXI controller connector) until the 7344 card is initialized. Shouldn't ethernet become active as part of booting up?

    The behavior is no longer reproducible, although several combinations of booting and plugging in the Ethernet cable were explored. LAN access is now available promptly upon booting or connecting the cable, as expected. A residual explanation might be that Win2K on the PXI 8175 controller did not fully respond when DHCP on the local router/firewall changed the PXI's IP address, due to changes in the network configuration. In this case, initializing the 7344 cards is taken as an event that caused the OS to complete LAN activation. Many other events with other hardware might have had the same effect.

  • How many PXI Ethernet Cards supported in LabVIEW RT?

    How many ethernet ports does LabVIEW RT support.  If I put in several cards (such as PXI-8231, PXI-8232, or PXIe-8234) into a PXI chassis, then would I be able to configure and use them all?

    Hello kmcdevitt,
    It should be fine to have as many ethernet cards as you need in the PXI chassis. There's a global limit depending on the number of interrupt lines available on the motherboard (or PXI chassis), but it's up to around 16, depending on the controller. You would set them up using the Advanced Ethernet Settings section in MAX, as explained in this LabVIEW Real-Time Module Help article. I posted the 2011 help but this works for a few versions back, what version of LabVIEW RT are you using? Hope this helps!
    Regards,
    Deborah Y.
    LabVIEW Real-Time Product Marketing Manager
    Certified LabVIEW Architect
    National Instruments

  • Looking for NDIS2 driver for PXI ethernet controller.

    I need to find a DOS level network driver (NDIS2) for the PXI815xb Ethernet controller. This driver does not appear to be on the driver disk or hard drive of the PXI chassis.

    The file is attached below. Just unzip it to a floppy disk. You will need to modify the settings for your particular network.
    Trey Hamilton
    Applications Engineer
    National Instruments
    http://www.ni.com/support
    Attachments:
    dosenet.zip ‏671 KB

  • Gigabit ehternet card in real time PXI chassis

    I was reading document # DZ52103_US about general real-time
    information. This document states that plug in ethernet, serial, and
    GPIB cards are not supported for real-time I/O operations. I want to
    use a plug in PXI gigabit ethernet card to transfer data from my real
    time PXI chassis to a host laptop computer. Can this be done?

    Currently, the only PXI ethernet controllers supported in LabVIEW Real-Time are the PXI-8211 and the PXI-8212. These are not Gigabit cards. This information is documented in the following link and will be updated as ethernet device support in LabVIEW Real-Time changes.
    If you have any further questions, please post a reply.
    Regards,
    Kristi H
    Applications Engineer
    National Instruments

  • How to stream DAQ from sub VI to a chart on its parrent VI?

    Hello,
    I have a working solution for my DAQ application that acuires data from 72 DSA PXI channels, streams it on disk (TDMS) with 1 kS/s and streams it on network eith 200 S/s. It works perfect on an obsolete P4 desktop. Attached is the DAQ sub VI that uses queues to sustain all operations. DAQ can last for longer periods so I'd like to also stream to a chart on the main panel (Main_VI). However this is not possible if the DAQ-SubVI is kept in a separate VI. I can stream data to a chart if everything is within a same VI - just wire the de-queued data to a chart inside the consumer (lower) loop.
    I prefer to keep the DAQ in a separate VI and I'd like to ask if somebody knows how to achieve that. I tried to pass de-queued data chunks form the consumer loop to a chart in the Main-VI via a "single process" shared variable but DAQ_SubVI acquires and nothing comes to the chart (I have placed the chart and its sourcing shared variable inside a while loop).
    Can this be done, and how?
    Thanks in advance,
    Attachments:
    DAQ_SubVI.jpg ‏181 KB
    Main_VI.jpg ‏33 KB

    Scott,
    I was away for few days. Thank you for helping me out again. I have done what you say (move the consumer loop to the main VI) and it works but I seem to have a kind of race condition. Namely, After the trigger is applied to the Sub VI, it waits for the STOP of DAQ and than the acquisiton is "played" on the Main VI's chart. In 20 attempts only once I got simultaneous DAQ and chart. What must I do so the consumer loop starts before the Sub_VI? Or is something else my problem?
    Thanks in advance,
    Attachments:
    Main_VI.jpg ‏70 KB
    Sub_VI.jpg ‏137 KB

  • ATV2 Jailbreak Streaming Issue

    Hi,
    Any help is appreciated!
    I have an ATV2 with Firecore added and I connect via ethernet to my Cisco E3000 router. Next to the router is my WHS box.
    I have a ticket open with Firecore but thought I'd ask here for help as well.
    I have 300 plus movies in a folder called AppleTV on the WHS machine. AppleTV is setup to login to the SMB share with its own user ID and password (it has a profile on the WHS).
    For a long time, this worked fine and I was able to stream wirelessly originally. Each movie file is between 700mb - 4gb generally depending upon source from DVD or Blu Ray and all are ripped using Handbrake set for AppleTV2. All play on my Imac just fine.
    The issue is that originally wireless, and now Ethernet streaming does the same thing. I get 30-60 minutes in and get playback error while streaming. I've tried verifying packet sizes, redoing the movie files to smaller folders by genre and nothing has worked. Not all files do this but more and more as time goes on.
    If I pull the file from WHS to my Imac, they play fine still.
    The WHS is a Dual core with 4gb ram and 9TB storage. Works fantastic otherwise.
    Thoughts? Suggestions?
    I even purchased a WDLive box to try and it seems to have the same issue..well almost. It never fails but the sound and picture get out of sync and the picture fast forwards to catch up.
    Time to upgrade the router?

    Anyone have any ideas?

  • N6030A Connection with LabView

    Hi,
    I am working with N6030A connected to Laptop through MXI Express.
    I read http://forums.ni.com/ni/board/message?board.id=270&message.id=3106&requireLogin=False
    and it doesn't solve my problem, everything in IVI-drivers section on Measurement and Automatic Explorer seems to be alright
    I have a code in mathlab, which can strangely communicate with the N6030A. Moreover, the N6030A Control Utility can detect the N6030A address.
    However, I cannot even connect to this device with LabView.
    When I use a AGN6030A driver (AGN6030A Initialize with Option) on Labview and connect it with an IVI resource name, there is only "ASRL3::INST" address available, which I don't really know what kind of device it is. Anyway, the connection using this resource name doesn't work either.
    I have also tried to copy the resource name that is showed on my N6030 Control Utility, and it doesn't work.
    Can you guys help me.
    Thank you

    Hi,
    Which instrument driver did you download? Which hardware bus are you using (GPIB, PXI, ethernet, etc)? I assume your instrument is PXI based; is this correct?
    The resource name "ASRL3::INSTR" corresponds to your serial port in your computer. If you are connecting to your N6030A using this serial port, ASRL3::INSTR is the correct resource to choose.
    From searching the instrument driver network, it looks like this is the only instrument driver available. It does not look like it is an IVI driver, but instead a software utility that you can use to communicate with the instrument. How do you access this instrument through Matlab? Through a DLL? Through VISA?
    Regards
    Krista S.
    Applications Engineering
    National Instruments

  • Streaming using ethernet

    Hello
    i looking for a suggestion a practical one. i want to stream data using ethernet cable from controller pxie 8130 ethernet slot,i have connected the controller to my PC using an ethernet cable(like form pxi 5142 digitizer onbord memory to controller 8130 memory and then from controller  memory to my PC).
    1-Can i make an application for acqusition on my PC labview, then using this can i acquire the data direct form controller
        memory to PC memory.
    2- Or  i have to store my data first form digitizer to controller Hardisk and then from controller hardisk to pc  i can move
         it using some other application like clint/server since it then would be a file to transfer.
    3- what can be the bottleneck's if the memory of PC,controller,digitzer is 256Mb each.
     Regards 

    Hello COMSIS, 
    Let's brake this down into small parts here and step through the data as it goes from signalall the way back to host computer. I'll assume that you are sampling on one channel at the full rate.  Since we can sample at 100 MS/s and each sample is streamed back as 2 Bytes of data, we would be streaming at 200 MB/s whichshould work with your chassis (should be a 250 MB/s limit as per PCIe spec's).  So, your card will not be a bottle neck.
    Once you bring the data back into LabVIEW, you will more than likely have to use a producer/consumer architecture.  Your producer loop will put your data into a queue that will be read out in your consumer queue.  In the consumer queue you will want to use TCP comunication to stream your data back to your non PXI computer.  This DevZone outlines how you would do it in an embedded application, but you can also use it with a Windows based PXI system.
    Here my knowledge of LabVIEW memory allocation and TCP communication speeds is a little lacking, so we might not be able to keep up with the data rates and so you may need to go with your other idea of storing it to a disk and then FTP'ing it back to your host computer.  To get the best answers, I would post the second half of your question on a LabVIEW board and just include a link back to this thread.  Once you post there, post back on this thread with a link to the LabVIEW post so that anyone who comes onto this post later can get the complete answer.
    Message Edited by ColeTrain on 01-27-2010 05:52 PM
    ColeR
    Field Engineer

  • Choosing the Right Network Protocol for CRIO 9024 to PXI over Ethernet

    We are in the design phase of setting up a CRIO 9024 Embedded Controller to send data captured to a PXIe-8105 Controller over ethernet. The data will be be 2D arrays of double precision. This data will need to be sent to the pxi at the end of each test step. Each step will have different number of channels and sample rates.
    For example,  Test Step 1 will have 5 channels of Analog inputs that will be sampled at 100,000 KHz for 1 second. This data will be coming from the CRIO FPGA. The data will get post processed by the CRIO 9024 and analyzed for pass or fail metrics. Then, the CRIO controller will send the 2D Array of Data (500,000 data points 5 X 100,000) and the results of all the metrics (a 1D array) to the PXI.
    The connection to the PXI will be using Ethernet.
    Keep in mind that the PXI will also have to send the CRIO some values to tell the CRIO when to start the test and when the test sequence is complete.
    I was thinking TCP/IP would work best because of the 2 way communication needed. But then I was looking at Network Streaming or even using Shared Variables.
    If anyone has any ideas or suggestions please please post them.
    Spark
    CLAD
    Test Engineer
    Solved!
    Go to Solution.

    Hi,
    You could use either.  Whichever you are more comfortable with really.  The STM method will have slightly less overhead over my XML style of tagging the data but it will be very little given the data size.  Probably go with STM as it just has most of the work done for you.
    In terms of data size the way you should normally transfer data like this is to flatten to string.  If you convert to a string of human readable numbers you will either lose precision, increase size or both.  Given that, the string after being flattened will be the same size as the original array anyway so quick calculation based on your previous post 500,000 doubles (8 bytes) is 4 miB (3.8MB)
    Cheers, 
    James Mc
    ========
    CLA and cRIO Fanatic
    wiresmithtech.com/blog

  • Choosing a PXIe controller for streaming 200 MBps

    Warning:  This is a long post with several questions.  My appologies in advance.
    I am a physics professor at a small liberal-arts college, and will be replacing a very old multi-channel analyzer for doing basic gamma-ray spectroscopy.  I would like to get a complete PXI system for maximum flexability.  Hopefully this configuration could be used for a lot of other experiments such as pulsed NMR.  But the most demanding role of the equipment would be gamma-ray spectroscopy, so I'll focus on that.
    For this, I will need to be measuring either the maximum height of an electrical pulse, or (more often) the integrated voltage of the pulse.  Pulses are typically 500 ns wide (at half maximum), and between roughly 2-200 mV without a preamp and up to 10V after the preamp.  With the PXI-5122 I don't think I'll need a preamp (better timing information and simpler pedagogy).  A 100 MHz sampling rate would give me at least 50 samples over the main portion of the peak, and about 300 samples over the entire range of integration.  This should be plenty if not a bit of overkill.
    My main questions are related to finding a long-term solution, and keeping up with the high data rate.  I'm mostly convinced that I want the NI PXIe-5122 digitizer board, and the cheapest (8-slot) PXIe chassis.  But I don't know what controller to use, or software environment (LabView / LabWindows / homebrew C++).  This system will likely run about $15,000, which is more than my department's yearly budget.  I have special funds to accomplish this now, but I want to minimize any future expenses in maintenance and updates.
    The pulses to be measured arrive at random intervals, so performance will be best when I can still measure the heights or areas of pulses arriving in short succession.  Obviously if two pulses overlap, I have to get clever and probably ignore them both.  But I want to minimize dead time - the time after one pulse arrives that I become receptive to the next one.  Dead times of less than 2 or 3 microseconds would be nice.
    I can imagine two general approaches.  One is to trigger on a pulse and have about a 3 us (or longer) readout window.  There could be a little bit of pileup inspection to tell if I happen to be seeing the beginning of a second pulse after the one responsible for the trigger.  Then I probably have to wait for some kind of re-arming time of the digitizer before it's ready to trigger on another pulse.  Hopefully this time is short, 1 or 2 us.  Is it?  I don't see this in the spec sheet unless it's equivalent to minimum holdoff (2 us).  For experiments with low rates of pulses, this seems like the easiest approach.
    The other possibility is to stream data to the host computer, and somehow process the data as it rolls in.  For high rate experiments, this would be a better mode of operation if the computer can keep up.  For several minutes of continuous data collection, I cannot rely on buffering the entire sample in memory.  I could stream to a RAID, but it's too expensive and I want to get feedback in real time as pulses are collected.
    With this in mind, what would you recommend for a controller?  The three choices that seem most reasonable to me are getting an embedded controller running Windows (or Linux?), an embedded controller running Labview real-time OS, or a fast interface card like the PCIe8371 and a powerful desktop PC.  If all options are workable, which one would give me the lowest cost of upgrades over the next decade or so?  I like the idea of a real-time embedded controller because I believe any run-of-the-mill desktop PC (whatever IT gives us) could connect and run the user interface including data display and higher-level analysis.  Is that correct?  But I am unsure of the life-span of an embedded controller, and am a little wary of the increased cost and need for periodic updates.  How are real-time OS upgrades handled?  Are they necessary?  Real-time sounds nice and all that, but in reality I do not need to process the data stream in a real-time environment.  It's just the computer and the digitizer board (not a control system), and both should buffer data very nicely.  Is there a raw performance difference between the two OSes available for embedded controllers?
    As for live processing of the streaming data, is this even possible?  I'm not thinking very precisely about this (would really have to just try and find out), but it seems like it could possibly work on a a 2 GHz dual-core system.  It would have to handle 200 MBps, but the data processing is extremely simple.  For example one thread could mark the beginnings and ends of pulses, and do simple pile-up inspection.  Another thread could integrate the pulses (no curve fitting or interpolation necessary, just simple addition) and store results in a table or list.  Naievely, I'd have not quite 20 clock cycles per sample.  It would be tight.  Maybe just getting the data into the CPU cache is prohibitively slow.  I'm not really even knowledgeable enough to make a reasonable guess.  If it were possible, I would imagine that I would need to code it in LabWindows CVI and not LabView.  That's not a big problem, but does anyone else have a good read on this?  I have experience with C/C++, and some with LabView, but not LabWindows (yet).
    What are my options if this system doesn't work out?  The return policy is somewhat unfriendly, as 30 days may pass quickly as I struggle with the system while teaching full time.  I'll have some student help and eventually a few long days over the summer.  An alternative system could be built around XIA's Pixie-4 digitizer, which should mostly just work out of the box.  I prefer somewhat the NI PXI-5122 solution because it's cheaper, better performance, has much more flexability, and suffers less from vendor lock-in.  XIA's software is proprietary and very costly.  If support ends or XIA gets bought out, I could be left with yet another legacy system.  Bad.
    The Pixie-4 does the peak detection and integration in hardware (FPGAs I think) so computing requirements are minimal.  But again I prefer the flexibility of the NI digitizers.  I would, however, be very interested if data from something as fast as the 5122 could be streamed into an FPGA-based DSP module.  I haven't been able to find such a module yet.  Any suggestions?
    Otherwise, am I on the right track in general on this kind of system, or badly mistaken about some issue?  Just want some reassurance before taking the plunge.

    drnikitin,
    The reason you did not find the spec for the rearm time for
    the 5133 is because the USB-5133 is not capable of multi-record acquisition.  The rearm time is a spec for the reference
    trigger, and that trigger is used when fetching the next record.  So every time you want to do another fetch
    you will have to stop and restart your task. 
    To grab a lot of data increase your minimum record size.  Keep in mind that you have 4MB of on board
    memory per channel. 
    Since you will only be able to fetch 1 record at a time,
    there really isn’t a way to use streaming. 
    When you call fetch, it will transfer the amount of data you specify to
    PC memory through the USB port (up to 12 MB/s for USB 2.0 – Idealy).
    Topher C,
    We do have a Digitizer that has onboard signal processing
    (OSP), which would be quicker than performing post processing.  It is
    the NI 5142
    and can perform the following signal
    processing functions.  It is
    essentially a 5122 but with built in OSP. 
    It may be a little out of your price range, but it may be worth a
    look. 
    For more
    information on streaming take a look at these two links (if you havn’t
    already). 
    High-Speed
    Data Streaming: Programming and Benchmarks
    Streaming Options for PXI
    Express
    When dealing with different LabVIEW versions
    it is important to note that previous versions will be compatible with new
    versions; such as going from 8.0 to 8.5. 
    Keep in mind that if you go too far back then LabVIEW may complain, but
    you still may be able to run your VI.  If
    you have a newer version going to an older version then we do have options in
    LabVIEW to save your VI for older versions. 
    It’s usually just 1 version back, but in LabVIEW 8.5 you can save for
    LabVIEW 8.2 and 8.0.
    ESD,
    Here is the link
    I was referring to earlier about DMA transfers.  DMA is actually done every time you call a
    fetch or read function in LabVIEW or CVI (through NI-SCOPE). 
    Topher C and ESD,
    LabVIEW is a combination of a compiled
    language and an interpreted language. 
    Whenever you make a change to the block diagram LabVIEW compiles
    itself.  This way when you hit run, it is
    ready to execute.  During execution LabVIEW
    uses the run-time engine to reference shared libraries (such as dll’s).  Take a look at this DevZone article about
    how LabVIEW compiles it’s block diagram (user code). 
    I hope all of this information helps!
    Ryan N
    National Instruments
    Application Engineer
    ni.com/support

  • We have an airport extreme wifi in house, but also want to set up a hardwired ethernet connection for gaming and streaming of netflix.  The computer only sees one or the other not both at same time.

    We have a new iMac 2.9ghz and are running an airport extreme set up in house with several express entenders.  The problem is that our son is streaming netflix and doing on line gaming and hogging all the band width.  Time Warner tech suggested a hard wired ethernet connection to computer base sattion next to computer so that it can have direct conenction to internet.  After much fishing of wire the connection worked great, but the wifi connection for the house is gone.  I unplugged the ethernet connection and everything is fine.  I read the articles about adjusting network preferences, but the issue seems to be in the extreme not in the computer.  the connection goes from cable modem to extreme, from extreme to house and to hard wired conenction to other computer.  Do we need a splitter before the extreme?

    No. Something else is going on.
    Your son may be hogging all the bandwidth but your wireless network should never simply disappear. Moreover, if your son isn't doing anything the available bandwidth for other devices should remain unaffected.
    I suspect that something is miswired, and from what you describe I suspect that link is between the Extreme and the "other computer".
    The way to accomplish what you propose is
    Modem > Ethernet cable to Extreme's WAN port
    Extreme's LAN ports > wired Ethernet devices.
    There should be nothing but an Ethernet cable linking an Extreme LAN port and any other wired device. If you run out of available LAN ports on the Extreme, you need to by an "Ethernet switch" - they are not expensive, but don't call it a "splitter" or you will only confuse yourself. The switch would be connected to one of the Extreme's LAN ports, and you would connect additional devices to it. You can also use one of your Expresses for that purpose, assuming it is the current generation model with two Ethernet ports.

  • IMac (on Ethernet) Can No Longer Stream to Airport Express (on WiFi)

    After years of reliable service, all of a sudden I cannot stream music from iTunes on my iMac, via my Airport Express, to my stereo system.
    First, a bit about my configuration:
       * iMac connected via Ethernet to a wireless router (D-Link DIR-655).
       * iMac Airport (WiFi) is turned off.
       * D-Link sets up a wireless network, and Airport Express joins the network.
       * Airport Express does not set up its own network, it's simply a client of the existing D-Link wireless network.
       * iTunes "sees" the Airport Express, and can stream audio via AirPlay.
       * iPad also joins the wireless network, and also can stream to the Airport Express via AirPlay.
       * iMac running 10.6.8, with all software updates applied.
       * Airport Express running latest firmware (7.6.1).
    Well, that was a few days ago, when "it just worked". But for some unknown reason iTunes could no longer "see" the Airport Express.
    So I took my Airport Express to the Apple Store and they did a Factory Reset, but it did not solve the problem. I figured my rather old Airport Express was failing, so today I bought a new one. The symptoms have changed a bit, but even after spending an hour on the phone with AppleCare, it doesn't work properly.
    Now, the only way the iMac can stream to the Airport Express is if the iMac also joins the wireless network. In fact, now with Airport turned OFF on the iMac, the Airport Utility cannot see the Airport Express. But here's another weird thing: when I use the IP address of the Airport Express, the Airport Utility CAN connect with and manage the Airport Express, even with Airport turned OFF on the iMac!
    I should also mention, the iPad has no issues whatsoever connecting to the D-Link's wireless network and streaming music to the Airport Express.
    This all seems like something might have changed on the D-Link wireless router. But for the life of me, I cannot figure out what setting(s) on the router might allow the iMac - over Ethernet - to stream audio to the Airport Express.
    Another thing. When I have Airport turned on on the iMac, it can "see" and stream to the Airport Express, but the music has very frequent drop-outs. Could this be related to the fact that the iMac has two IP addresses (one on Ethernet, one on WiFi)?
    My goal is to get things "back to normal", where I can turn off Airport on the iMac, and all LAN and WAN traffic from the iMac goes over Ethernet. I have a few questions (for now :-)
       * Since my iMac has two connections to my LAN using two IP addresses (Ethernet & WiFi), is that likely to cause any issues?
       * When two computers join the same wireless LAN, can they effectively talk directly to one another, or does the wireless router need to be involved every time one computer sends a TCP or UDP packet to the other?
       * Do routers (or the DIR-655 in particular) tend to have any firewalls or policies that control connections on the LAN between Ethernet and WiFi clients?
       * Since AirPlay uses TCP port 3689 and UDP port 5353, would the DIR-655 need any special configuration to "open these ports" so an Ethernet client can connect with a WiFi client?
    So, any help would be most appreciated!
    Thanks!
    Jim

    I am having a very similar issue.  I use my Airport Express (AX) to stream music from the computers on my network to my stereo via Airplay.  I have AX set up to wirelessly join my existing wireless network, which uses a D-Link DIR-655 router hooked to a Time Warner cable modem.  I can succesfully connect all of my wireless devices via Airplay, through iTunes to my AX, including two laptops and an iPhone.  However, my primary desktop PC, which does not have a wireless card is linked directly via ethernet cable to my D-Link router, and it is not able to see my AX.  Similar to your case, I can see the Airport Express from my PC through my Airport Utility by directly typing in the IP address.  Note that the  AX set-up option to allow Ethernet clients is checked.  I also noticed that my laptops will stop detecting AX if I directly connect them to my D-Link router via Ethernet and turn off their wireless cards.  They will resume detecting AX when I turn their wireless connections back on.  I have tried every conceivable setting of my D-Link router to no avail. 

  • PXIe acquiring and disk streaming speed

    Good evening,
    I need to acquire and stream to disk the status of N.8 digital lines at 100 MHz clock, idest 100MBytes/sec data rate, in continuously mode (without data loss) for five minutes.
    I've thought to a PXIe configuration with:
    PXIe 6544 High speed DIO,
    PXIe 1071 Chassis,
    PXIe Controller with solid state H.D. option.
    Is that configuration enough?
    Thanks.
    Natalino Roberto

    Hello Roberto,
    According to NI PXIe-6544 specifications, you should be able to achieve typical data streaming rates 400 MB/s for acquisition and 400 MB/s for generation. So, you shouldn't face with any issue from this side.
    Does your application provide an host interface communicating with embedded application? If doing so, you may need to design your application according real time guidelines.
    Let me know if you need help or additional assistance.
    Have a nice day.
    Matteo C. - Test Engineer

Maybe you are looking for