RT and instrument communication over ethernet

We plant to use a Xantrex DC PS (interface info attached) and was wondering if we can use an ethernet hub in between the Host and the RT target and have all our stand-alone instruments connected to this hub. RT will communicate with these instruments over VISA. Hope nothing is wrong with this picture and it's doable.
Attachments:
Xantrex ethernet brochure.pdf ‏513 KB

Hi Pavan,
What exactly are you looking for? In other words, what do you think it could go wrong? The reason I am asking is that there might be several KBs or few, depending on what you are looking for. Now, NI-VISA shouldn't have any problem because it is a protocol that is used to communicate with instruments that are in a bus, like the GPIB bus or Ethernet bus, so I don't understand what could be the problem. If you have something in mind, let me know so we can discuss it.
Ricardo S.
National Instruments.

Similar Messages

  • Using DynDNS and Sharing disks over Ethernet WAN port

    I am having issues accessing the AirDisk from outside my LAN. So here are the steps that I have taken:
    In the AirPort Utility, I enable "Share disks over Ethernet WAN port".
    Created a DynDNS account at http://www.dyndns.com so my hostname points to my IP address.
    After reading a bunch of threads, mainly this one below, there are a few conflicting issues.
    http://discussions.apple.com/thread.jspa?messageID=4105319
    Someone mentioned you have to Setup Port Mapping to open up Personal File Sharing. But another said you don't have to set up Port Mapping. Well if you do, you're gonna run into a problem. This Apple article states you have to use a different port: http://docs.info.apple.com/article.html?artnum=305183
    Someone said Remote Access only works via AFP not via SMB. Is this true?
    Also do I have to enter my DynDNS hostname into the wide area bonour tab in the advanced tab?
    What am I doing wrong?
    Macbook   Mac OS X (10.4.8)   Airport Extreme N

    Are you aware of any DynDNS-like service that support Wide Area Bonjour?
    None at the moment. One might hope that Apple's .Mac service would make use of it, but I don't think Apple has announced anything about that possibility.
    Or as a practical matter is this a technology that only appears at the moment in private installations of OS X Server?
    I've found the version of dnsextd that ships in Mac OS X 10.4 (not just the server version) to be a bit flaky. One hopes it will work a lot better in Mac OS X 10.5.
    But since the AEBS doesn't support DynDNS update, as other routers do, it ends up requiring a server after all.
    Wouldn't it be nice if DynDNS and similar services allowed you to configure DNS resource records manually? That way, it wouldn't matter what your home gateway/fileserver was capable of doing— you could just edit your DNS zone accordingly.

  • Has anyone used Ethernet Gateway and LabVIEW, communicating with Ethernet/IP protocol ?

    I have a PLC system (Jokab Safety B20)  together with Ethernet Gateway (also Jokab Safety type E1).
    What I want to do is to communicate with this unit using LabVIEW Ethernet/IP.
    Read a couple of data and write a couple.
    Has anyone anything like this with LabVIEW and Ethernet/IP ?
    I'm completely new to using PLC's, but I have made a minimum PLC application, but can't get communication to work with LabVIEW (+ Ethernet/IP).

    i generally use an OPC server to talk to he PLC and then use Datasocket to talk to the OPC server tags.
    if that gaetway thing is an OPC server then you maybe abel to do data socket R/W via it.
    Otherwise the NI OPC server may support that widget and (at the rate I bill out) is a good deal in the eyes of most of my customers.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • LWAPP with AP and AC communicating over L3

    When the Access Point (AP) and Access Controller (AC) communicate over an IP network (using UDP):
    1- Is the MAC address of the AP's wireless clients known at some stage by the Access Controller?
    2- I do not have a clear picture about DHCP (for wireless clients) in case the DHCP server is not at the AP itself.
        - Is DHCP relayed onto LWAPP just as any other user data message?
        - I assume the AC can work as a DHCP relay. Correct?

    As per my understanding the above AP failover scenario you described applicable to "Local" mode APs. 
    In H-REAP, if WLC is not reachable it is going to "Standalone" mode without trying to fail-over to another controller. In that sense what you trying to achieve may not work.
    Anyway I have not tested this sort of scenario, you are in a best place to give it a try & see. If that works let us know.
    HTH
    Rasika
    *** Pls rate all useful responses ****

  • Airport extreme and HP printer over ethernet problem

    I'm new here, so forgive me if this topic has been done to death. I'm running airport extreme and have an HP photosmart 2600 connected to it via ethernet. My wife has no trouble printing with her Macbook Pro (Snow Leopard), but my daughter's older iMac only prints very intermittantly and mostly not at all.I've tried all the sharing options and reinstalling/updating the HP software, but no luck. The printer is at the other end of the house from the Airport, so connecting via usb is not an option. Any assistance much appreciated, thanks.

    Using Ethernet should give the best results, plus it allows the use of more than just the print function, which USB would not. Proof of that should be the fact that this older HP model (it works with OS 9!!!) works well with your recent Mac's Snow Leopard OS.
    If the iMac has OS X 10.5.8, the correct printer driver should have already been installed and no further update would have been needed. All that should have been needed was to open the Print & Fax panel of System Preferences and add the HP printer as the iMac's default printer.
    When the iMac was first unable to print using the HP, did you consider any chance that the iMac was too far from the Extreme, or that there might have been some interference involved? Did you power cycle starting with the modem? When power cycling is necessary, printers seem to throw off unexplainable errors (such as out of paper or ink, paper jam - when none of these is true).

  • Process Failure when communicating over MODBUS using LabVIEW 2011 and DSC

    I'm currently trying to read from a PLC's holding registers using MODBUS/TCP. I've confirmed that the PLC is updating the values and responding to MODBUS communication correctly using a third party program called Modbus Poll. However, when I try to poll the PLC using LabVIEW's shared variable engine, I am unable to read any values from the same addresses that I'm viewing with Modbus Poll.
    My setup simply consists of a PC connected directly to the PLC over Ethernet, with no router in between. I am using LabVIEW 2011 SP1 with the DSC module.
    I opened the NI Distributed Systems Manager to view the status of all shared variables in the Modbus library that I created and I've noticed that the CommFail bit is permanently set to "true". All other variables with a "read" access mode report "Process Failure". I've tried restarting the process as well as stopping and starting the local variable engine with no success. I've also restarted my computer several times to see if any services were failing, but this does not seem to have fixed the problem.
    I finally resorted to monitoring communications over the network card that I have the PLC plugged into via Ethernet using Wireshark and I've found that while Modbus Poll is communicating with the PLC, many MODBUS and TCP packets are sent and received. However, when solely using LabVIEW or the NI DSM to communicate with the PLC, there does not appear to be any communication over the network card.
    Something that may be worth noting is that I was able to communicate with the PLC and read values from it with the DSM on just one occasion, when I first figured out which addresses I should be reading from. It all stopped working shortly thereafter. Prior to this, "CommFail" was not usually set to "true" with my current configuration. Thinking that it was my firewall, I have since turned my firewall off, but this seems to have had no effect on the problem either.
    Any help on this matter would be appreciated.
    Solved!
    Go to Solution.

    Just a thought but I think the  register addresses used by LabVIEW are one off of the actual register #.  I was using a CRIO as a modbus IO Server and had to shift the register addresses by 1 to get things to work correctly (can;t recall if it was +1 or -1).  This is documented somewhere on ni.com but can;t seem to find it now.  But here is another  link that may help:
    http://zone.ni.com/reference/en-XX/help/371618E-01/lvmve/dsc_modbus_using/
    Dan

  • Problems communicating with LK4.5 and Quantum PLC over Modbus TCP/IP

    I am developing an application using LK4.5 communicating to Quantum PLC over Ethernet Modbus. The update is set at 1 sec. There is a periodic delay in getting an response from the PLC. On probing, i have found that the Modbus object update (checked with an led) blinks OK for about 20-30 seconds during which the valid frames are incrementing correctly. However, after that, for a short duration of about 10 secs, the update led stops, and the valid frame count increases quite rapidly. During this time, the date is not being read from the PLC. This process repeats quite regularly. This time during which it reads correctly, and when it gives a problem, remains quite constant for one PLC, though it varie
    s between PLC to PLC. There are 7 PLC's connected to the system. Please suggest any remedial action. Thanks.

    Further development has happened on the Modbus driver to resolve Ethernet issues. There is a Lookout 4.5.1 update on the FTP site to update Modbus driver and Report Object.
    ftp://ftp.ni.com/support/lookout/fixes/4.5.1

  • Ethernet communications over writing RIO on boot up

    I have CRio 9068 that writes all setpoints to a text file on board while the program is running. My HMI is Vartech touch screen computer running windows 7 embeded. When power is cycled to the system and it reboots both the controller and HMI I loose my setpoints that were in the text files as they are getting over written from the touchscreen. We are using network streams over ethernet for the communications between devices. Is there any sample codes that I can look at to better understand how to prevent this from happing? I have thought about using a first call wired to time delay off timer then allowing the string to write the new variables but I don't think this is the best solution.

    You'll want to Fetch the current values from your cRIO and store them on your HMI. You can see this pattern by creating the LabVIEW Real-Time Control on CompactRIO sample project, opening RT Main.vi on the cRIO and look at the case "Send Control Configuration to UI". Basically the messaging scheme you're talking about should be bydirectional. When your HMI connects to the cRIO it requests an update BEFORE it sends anything out, and waits for the cRIO to respond. 

  • Does Lookout have a driver for SLC 5/05 and 1500 over ethernet

    Does Lookout communicate with the AB SLC 5/05 over ethernet and the AB 1500 via the Net DNI over ethernet ?

    Several years ago (back in Lookout 3.8 days) there was ethernet for AB SLC-5/05, it was a choice on the pull down menu for the communications type. It works great.
    then in the days of Lookout 5.X, NI removed the ethernet for AB SLC-5/05. I believe the issue was that some users were having difficulty in understanding the I/O addressing, expecially when they would have an analog input/output card in the chassie. The issue is that RSLogix 'neatly' organizes this I/O table for us, however, NI can only get the I/O table in its 'raw' form. And this caused confusion for users not experienced with how the I/O table is truly layed out. A user can experiment with a bench/test system and see how the I/O is layed out and get a good understanding. But a another method is to write the analog input value to a "N" file address, and use that in Lookout (remember only the I/O is the issue) Also, you can have Lookout write to another "N" file address, and in the SLC, move that "N" address to the Analog Ouput.
    I still have a SLC file for Lookout that has the ethernet enabled (works with Lookout V5.x) but I bet Ryan can send you one if you need it.
    I have upgraded to Lookout V6.2 and making a driver object to talk to AB SLC-5/05 on ethernet works great. (I love native drivers, and hate using RSLinx OEM to do OPC (for out ControLogix5000 processors)
    If a person can work thru how I/O tables are truly layed out (one big matrix actually) go direct and dont' use OPC.
    Remember, this isn't a fault/limitation of Lookout or NI, it is how AB layes out their I/0 table, and how the addressing we see in RSLogix is actually not the true representation of the actual matrix. (and this matrix is all that is actually available, AB just makes it more 'readable' because you (or who ever setup the chassie configuration) told RSLogix what cards are in which slot, so RSLogix can minipulate the table to show it to you more 'pretty'.
    If NI would add a chassie configuration to the AB SLC driver, then this issue would not exist. But I don't think we want to do that.
    Hope this was helpful!
    Rich Anderson

  • Time Capsule and only 120 kB/sec over ethernet?

    Hi Community,
    I want to connect a Mac Mini (late 2009) and a Time Capsule (4th gen) over ethernet.
    Even if I connect them directly (with a cat 6 cable, 6ft = 2m in length) I have a maximum transfer speed of around 120 kBit/sec ~ this is roughly 1/100 th of which is possible over gigabit ethernet (if hdds would be really fast ;-) .
    The time capsule worked for about a year wirelessly and served my MacMini and my MacBook Air... but I have the cables and liked to gain some speed (and not have so much usage on my wifi).
    I made a factory reset and put the Time Capsule in a No-Wifi-No-Internet mode with "hard wired" IP -- so it should work like a simple wired NAS.
    Working with a switch (Netgear GS) I get the LED info, that the switch senses a gigabit-connection for the Mac Mini and the Time Capsule.
    BTW: My internet download speed ist roughly at 600 kBit/sec -- so the Mini could handle more, which means: the Problem lies within the Time Capsule.
    Can anyone help me? Is my TimeCapsule defective?

    WLAN is deactivated in the Time Capsule and the Mac Mini. My "test-object" is my saved Mountain-Lion-Image with 4,4 GB in size -- forget to mention: The Mini runs on Mountain Lion.
    I never tried the ethernet LAN connection before... so I don't know, if it would have worked with Snow-Leo or Lion. But as said before... downloading from the internet I can get 600 kB/s which is limited by my 6MBit DSL line.
    Unfortunately I don't have another gBit ethernet Mac to test the Time Capsule. The Air doesn't have a LAN plug-socket.
    I tried the three LAN ports and the WAN port of the Time Capsule -- all connect the Mini to the TC, but all give me the same transfer speed... of 120 kB/sec.
    Of course, the WLAN connection to the TC is much faster. Before the wires I used the 5 GHz band -- and could make a full system Backup over a night. Cabled I would have to spend around 80 days for that ;-)
    BTW: A PING-Test looks quite good...
    PING 192.168.2.2 (192.168.2.2): 56 data bytes
    64 bytes from 192.168.2.2: icmp_seq=0 ttl=255 time=0.194 ms
    64 bytes from 192.168.2.2: icmp_seq=1 ttl=255 time=0.236 ms
    64 bytes from 192.168.2.2: icmp_seq=2 ttl=255 time=0.172 ms
    64 bytes from 192.168.2.2: icmp_seq=3 ttl=255 time=0.229 ms
    64 bytes from 192.168.2.2: icmp_seq=4 ttl=255 time=0.232 ms
    64 bytes from 192.168.2.2: icmp_seq=5 ttl=255 time=0.226 ms
    64 bytes from 192.168.2.2: icmp_seq=6 ttl=255 time=0.230 ms
    64 bytes from 192.168.2.2: icmp_seq=7 ttl=255 time=0.227 ms
    64 bytes from 192.168.2.2: icmp_seq=8 ttl=255 time=0.268 ms
    64 bytes from 192.168.2.2: icmp_seq=9 ttl=255 time=0.227 ms
    ^C
    --- 192.168.2.2 ping statistics ---
    10 packets transmitted, 10 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 0.172/0.224/0.268/0.024 ms

  • Extending Wireless Network and Bridging Over Ethernet

    Have a TimeCapsule and Airport Basestation at home. Both are currently connected over wireless using the "Extend Wireless Network" feature.
    On each of the devices have several laptops, mac minis etc. connected over Ethernet (since wireless insufficient for our high speed data transfers etc.)... Trouble we are having is the speed/connection between both the TC and the AP, so considering to connect them both over Ethernet to improve.
    Question is once they are connected over Ethernet, what happens to the "Extend Wireless Network", how does the TC and AP know to either use the wireless or the Ethernet to connect with each other? Does one take precedence over the other?
    We want to keep them both on Ethernet and Wireless bridge ideally, so that at opposite ends the wireless network is extended for our iPhones and iPads and all devices connected on Ethernet benefit the speed boost over Ethernet, but just not sure how it will behave, and not sure how to test this scenario....
    So asking here instead
    Thanks!

    It sounds like you might want to configure your base stations into a "roaming network".

  • ATM over Ethernet and pseudowires

    Hello.
    Could somebody tell me if there is a Cisco Router that can work ATM over ethernet. This ATM circuits comming from an ethernet interface sholuld be transported as pseudowires through an IP/MPLS Backbone. Routers 12000 can do this? wich version do I need?
    Thanks

    Hi Narayan. Thank you.
    I have now the following doubt. If we have the following topology:
    lan-(CE)--ethe--(pe)--MPLS--(pe)--atm-(ce)-lan
    Consider a lot of atm access at the right side, but we need to use only one vlan at the left side to connect all the remote atm sites.
    You are telling me that we can convert the left CE in to a PE. But Can we maintain the router as a CE but terminating the ATM circuits (pseudowires) transported over one one vlan? ( atm over ethernet)
    I appreciate everyting.

  • 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

  • Detect device over ethernet

    Hi Everyone,
    I would like to know how do i detect device connected over ethernet by using labVIEW?
    My require is:
    I have to develop a code which detect any device connected to ethernet port.(The external device which is connected to ethernet port may be anything)
    I would like to get the IP of the device connected to my ethernet port using labVIEW.
    It will be really grateful if anyone can help me to resolve this.

    A brute force method which is commonly used is to send a ping packet to every IP address in the subnet(s) you are interested in. This is not guaranteed to work since some devices will not reply to ICMP ping packets for security reasons. Another approach which again guaranteed to work and will more likely find fewer devices would be to send a SNMP request for the system description (1.3.6.1.2.1.1.1.0) . If a device supports SNMP they will generally respond to this request.
    Many devices, especially network infrastructure devices, will not be easily managed. They will have security enabled to limit access to them. Part of this security will be to limit what types of communications they will accept and who they will talk to. Simply finding an IP address active on a network will not provide you with too much information about the type of device it is and how you may communicate with it. There are lots of network protocols out there and many devices have very specific ones they use. A general purpose network manager that can find and communicate with anything on the network is a daunting task and one that most likely will not be possible to implement. At best you will be able to find a subset of devices. As I mentioned even the most basic ping packet will not guarantee you will find everything.
    I'm not trying to rain on your parade but trying to let you know that you are trying to accomplish something that will most likely impossible to actually do. Probably the most effective way, but not very practical,  to at least find eveything would be to implement a port scanner that would exhaustively go through every IP address in your desired range and attempt to establish a connection on every TCP port (you could stop once you get a response). If a device is on the network it more than likely will communicate on at least one TCP port. All this would tell you though is that there is a device at that IP address that communicates using port x. However, as I cautioned before this type of activity will very quickly get the attention of the network staff managing the network you do this on.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

  • Itunes over ethernet?

    I have a Mac Pro in my upstairs office and it is connected to the home network by an Ethernet hardwire. The router is a Netgear model.
    I also have a Windows laptop connected to the network in the family room via WiFi.
    Is there a way for me to use the Laptop to control the iTunes library on the Mac Pro and have the audio play through my home theater in the family room? The Home Theater has access to the hardwire Ethernet and I would prefer a solution that uses the hardwire NOT WiFi....
    Thanks,
    Pete D.

    Why are there ethernet ports on both the aiport and the aiport express
    So you can plug ethernet devices into them.
    In order to do audio over ethernet, you have to convert the audio to packetized data which would then have to be converted back to audio at the far end and fed to an amp.
    You would get a customized system installed to play audio/video over CAT5 ethernet.
    Or use wifi which should work anywhere in the house unless you have a lot of wiring in the walls, shielding the signals.
    You don't simply play regular analog audio thru an ethernet wire though it would be possible. If so, it would not be used for ethernet connection.
    Keep in mind that a CAT5 cable in the wall is not ethernet. Ethernet is a communications protocol that typically uses CAT5 cabling between devices (routers and switches).
    A bit about AoE-> Audio over Ethernett

Maybe you are looking for