No serial port at max

Refering to the attached images, i have a VI using serial port which i have already programmed in 1 PC. After i've installed LV and DaqMX on the 2nd PC and try to run this VI, it doesn't work. Then i realised the 2nd PC does not have Serial port detected at MAX->Devices.
What could be the problem?
I'm using LV 8.2 eval and DaqMX 8.5
Attachments:
No serial port.JPG ‏104 KB
With serial port.JPG ‏112 KB

Take a look into the software-folder in MAX. If you installed a default installation from one of NIs ADEs (e.g. LabVIEW), the driver-CD is installed after the ADE. The driver-CD contains NI VISA....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

  • Can not access serial port while upgrading from LabVIEW 6.1 to 7.0

    Hi,
    I built an application under LabVIEW 6.0.2. few years ago. This application uses LabVIEW serial features. When I upgraded to LabVIEW 6.1, my application was still working correctly.
    Today, I upgraded to LabVIEW 7.0, mass compile all VIs and now my application can not communicate with my peripheral !!!
    The program is sending the command to the peripheral. The peripheral answers but LabVIEW serial driver does not see any datas on buffer even if datas are available ... "Bytes At serial port.vi" always returns 0. I am sure that datas are available, using a COM port psy.
    Does anyone has an idea?
    I saw a lot of solutions in the forum, but I would like to know the best solution with minimum work, te
    st, and so on ... on my program.
    Regards,
    Pascal.

    Hi Pascal,
    Which is your version of NI-VISA?
    Please see the link bellow :
    http://digital.ni.com/manuals.nsf/websearch/E8D86CD680B0753D86256D2C005D8EA0
    The first test to be made is to test the communication with your serial port using MAX (Measurement and Automation Explorer) :
    Open MAX, Go to "Devices and Interfaces", then "Ports", select COM1 (or ASRL1::INSTR). Right clic on it and select "Open VISA Session" the go the "Basic I/O" then Write data, execute, Read data, execute.
    Be sure that the communication is OK. Be sure that you use the same Alias existing in MAX in your LabVIEW program.
    Now, if all is OK, try to use Serial communication examples existing in LabVIEW Help>>Examples Finder. These examples use NI-VISA VIs.
    If all above is OK and you
    still have the same problem, try to follow these instructions :
    "In order to use the old Serial Compatibility VIs in LabVIEW 7.x, you must copy the following files from a previous version of LabVIEW to the LabVIEW 7.x directory:
    Replace the serial.llb in LabVIEW 7.x with the serial.llb from a previous version of LabVIEW. This file is found in C:\Program Files\National Instruments\LabVIEW\vi.lib\instr.
    Replace the _sersup.llb file in LabVIEW 7.x with the _sersup.llb from a previous version of LabVIEW. In LabVIEW 6i and 6.1 this file is located in C:\Program Files\National Instruments\LabVIEW\vi.lib\platform. In LabVIEW 7.x (and 5.x) this file is found in C:\Program Files\National Instruments\LabVIEW\vi.lib\instr.
    Copy the file serpdrv to the C:\Program Files\National Instruments\LabVIEW 7.x directory. This file is not installed with LabVIEW 7.x, so it only needs to be copied from a previous version of LabVIEW, not replaced."
    I hope that my answer will help you.
    Sa
    naa T
    National Instruments

  • Serial ports not appearing in MAX - VISA installed.

    Hi All,
    Had a rather strange issue today that I couldn't resolve with serial ports not appearing in MAX (and hence being inaccessible to LabVIEW). Under the windows device manager it shows 4 COM ports and I have verified with an external program that they are functioning correctly.
    I had the LabVIEW 2011 SP1 f2 runtime installed, DAQmx 9.6.1 and NI-VISA 5.3 (5.2 also didn't work).
    Things I have tried:
    - Updating VISA from 5.2 to 5.3
    - Reinstalling the COM port devices under device manager
    - Changing the COM port numbers
    - Verifying that the COM ports are functioning correctly
    - Tried adding a USB to Serial converter as a new COM port
    - Reinstalling MAX
    - Reinstalling NI-VISA
    - Reinstalling everything (reboot each time when prompted)
    - Resetting the hardware configuration from within MAX
    - Run installers / MAX as administrator (this is running from the local admin account)
    - Checked that NI-VISA appears under software in MAX
    - Repaired MAX/NI-VISA
    Is there anything else that could cause the COM ports not to appear in MAX when they appear (and work correctly) in device manager when a reinstall of NI VISA / MAX won't solve?
    Certified LabVIEW Architect, Certified TestStand Developer
    NI Days (and A&DF): 2010, 2011, 2013, 2014
    NI Week: 2012, 2014
    Knowledgeable in all things Giant Tetris and WebSockets
    Solved!
    Go to Solution.

    I found the solution - it turns out that the serial ports were available to LabVIEW, they just didn't show up in MAX because installing just the runtime does not show the devices in MAX.
    Despite doing a lot of googling earlier, it didn't throw up this knowledgebase article until I searched for it under a different phrase - http://digital.ni.com/public.nsf/allkb/766FD80DAE42E52886256A0200619CFE?OpenDocument
    Certified LabVIEW Architect, Certified TestStand Developer
    NI Days (and A&DF): 2010, 2011, 2013, 2014
    NI Week: 2012, 2014
    Knowledgeable in all things Giant Tetris and WebSockets

  • Serial Port not accessible until I run MAX

    Hi!
    On my machine I can access all Serial ports perfectly. I put a Vias Resource in my VI and get a drop down menu with all my serial ports. But on other machines (Runtime v7 and VISA runtime installed) I don´t get the names (e.g. com1 com2) but only
    ASRL1:****
    ASRL2:****
    ASRL10:****
    I know that ASRL1 is COM1 but when I select it it dowsn´t work.
    If I now install MAX on the machine and run it once without changing the configuration my ports work.
    Can anybody tell me how to use the ports without using MAX??
    regards
    hmann

    Hi hmann,
    When you run MAX it is configuring your VISA alias list behinf the scenes. See "JB" answer to this question to find out how to do this without using MAX. It basicly requires editing an INI file.
    http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000238D0000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0
    I hope this help,
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Serial port writing return different in MAX and Labview

    Dear all,
    I have a very strange problem here. I had a device connected to the serial port, which can be started by sending "start\n".
    Firstly, I used the IO in MAX to send "start\n", like the first figure, and the device operated correctly.
    Then, I initialized the device, and used the program in the second figure, to write the same "start\n", but this time the device operated wrong.
    I think the serial port setting are the same, and the device is not failed (after the second step, I repeated using MAX and still it's OK).
    Could anyone to check what's wrong here?
    Many thanks!

    In your LabVIEW code, how do you know that it did not work?
    Did you receive and error on the error indicator?  You don't have any VISA Read going on, so you aren't trying to read the response.

  • I am trying to reset a serial device through serial port ,MAX is able to do it but the same command is not working in labview

    max can do it but labview cant

    - Run NI Spy Tutorial
    - Reset the serial device in MAX
    - Run the LabVIEW code
    - Post the *.spy file.
    The spy capture will show any difference in function calls to the driver.

  • 845G MAX - "PCI Serial port" coming up as new hardware

    Hi,
    I just installed the motherboard and did a fresh install of win2k sp3. I've installed the latest BIOS, Intel inf and everything from the windows update service but it's still not able to install the PCI serial port. Can anyone clue me into what I need to do?
    Thanks,
    Chris

    Dear Subhash,
    If your Ci is running then http://hostname:port should give you a start page, but if you login to perticular new instane with http://new host:new port and if this is returning some error then we can categorize as we have problem in new instance.
    Can you please paste .out logs from your work dir for new instance.
    and chek the memory settings according to following notes:
    Note 696410 - Java VM settings for EP6 on J2EE 6.20
    729178 - Java VM setting for applications running on J2EE Engine 6.20
    634689 - Central Note for Memory Issues, SAP J2EE Engine 6.20
    And specify your system configuration as well ..
    Regards
    Shailesh

  • Is it possible to choose the serial port if only the run time engine is installed

    I have an application, which communicates over the serial port. When I use the full version of Labview I can change the serial port without any problem from Com1 to Com2 (similar to the example “Hardeware input output -> serial -> Labview serial vi"). When I build an application and try to run this program on a computer where only the run time engine 6.1 is installed, it is not possible to choose the serial port. Since there is no “Measurement and Automation Explorer” available on the run time engine and no directory C:\VXIpnp is created, when the run time engine is installed, I do not see a way, how I can satisfy the computer with the information it needs for configuring
    the different ports. Any suggestions?

    Hi Daniel,
    Before LV6.1 there was LV5.1 In LV5.1 the way to Spedify a resource was to use a string control with correct VIsa Resource Class identifier. For eg. "GPIB0::11" or "ASRL1::INSTR". With Introduction of VISA Resource Name Control and linking with MAX, These names are Available from Pull Down List and Can be Aliased, meaning ASRL1 which is Serial Port 1 can be called COM1 and so on. However the old method still works with all 6.1 Controls. Only thing is you have to make sure you Dont Conflict the Class Names ie Use "GPIB::.." instead of "ASRL..." when addressing Serial Port VI's.
    To solve your Problem I would Build a Menu ring with COM1 to COM4 in the Pull Down List.
    Next, If I use the Traditonal Serial Port VI wich accepts the Integer as Seria
    l Port #. I just Wire the Menu Ring to this VI.(Remember COM1 is 0, COM2 is 1 for this VI)
    If I use VISA Config Serial Post. I build an Array Constant with Corresponding VISA Class Names So in our case a String Array Constant of 4 elements "ASRL1::INST" to "ASRL4::INST". I Use Index Array Function With the Index Wired to my Menu Ring. The Array Input Terminal Wired to the Array Constant. The Output of this Array will be correct Visa Class Name Based on slection of my Menu Ring. I can Wire this as Input to my VISA Config Serial Port Vi.
    I have attached a Small VI to Illustrate this.
    Drawback: You must Predefine what Ports you will Want to Use. Basically you define all the cases.
    I hope this Answers your Q!
    Good Luck
    Mache
    Good Luck!
    Mache
    Attachments:
    Serial_Port_Select.vi ‏36 KB

  • 0 bytes at serial port after Visa Write

    Hi,
    I'm having problems communicating with a Pollux box controlling a stepper motor (both from Micos). The Pollux box has an RS232/485 connection to the computer. 
    I have tried adaptations of LV's Basic Serial Read and Write example. Even for the basic example there has never been any bytes at the serial port after the write.
    I have attached some sample code for LV 10.0.1(64bit) and the OS is Windows Server Enterprise 2008.
    The Visa drivers have just been installed.
    After some research I have added a 'Set I/O buffer size' as advised by http://digital.ni.com/public.nsf/allkb/60DDFED7EFEFE7188625705700750821?OpenDocument
    The time-out is set to 10s, I have a wait of 1s before read and 0.5s between each write (the characters are written individually incase that was the problem).
    The write command getaxisno_ should reply with the default axis no which is 1. However, there is never any reply.
    The termination character for Venus2 is a space for transmitting commands and ASCII CR LF at the end of received data.
    I'm not sure what else could be wrong. According to MAX the device is working properly. Although, when I try to open a Visa test panel in MAX the program crashes. I'm not sure if this is a related problem.
    I'd be really grateful for any advice, have been trying to fix this for a few days now.
    Thanks in advance!
    Ciara
    Attachments:
    Getaxisno test.vi ‏18 KB

    Thanks, I'll search those now.
    When I click the test panel button, the Max window disappears and the program is closed. Next time I open it an Unexpected Error box opens with a message saying there was an unexpected error and I should search Info Code MAXKnownException.
    'The exception occurred in the NIMax process in the function (Unknown).'
    I have searched this and the info advised me to send a report with log files etc to NI which I have done. Just waiting on the reply.
    I copied the Visa resource name from MAX and the termination character is the same as what a previous owner of the equipment used in Visual Basic. 

  • The "VISA Configure Serial Port" VI will only run at 9600 Baud

    I have written a Serial Port monitor "RS232 RW.vi"  that works for the most part. The problem is that it will not respond to alternate port configuration settings.... For instance: the default RS232 Serial port configuration is:
    (COM1,9600 baud,8 data bits,1 Stop bit, None no parity)
    As a test, I am using a Null Modem Cable to connect From my LabView Com1 port to another PC running RealTerm Serial Port Monitor.. Using my newly designed "RS232 RW.vi"  With port settings of (COM1,9600 baud,8 data bits,1 Stop bit, None no parity),  I can send and receive data back and forth all day long no problems....
    However, if I configure the "RS232 RW.vi"  port to any other configuration, such as (COM1,2400 baud ,7 data bits,1 stop bit, Odd parity).. It will not take the expected chances and continues to operate @ 9600 baud etc.
    I then changed the "RS232 RW.vi"  default settings to (2400,7,1,Odd)
    it still refuses to deviate from (COM1, 9600,8,1,None...)
    I also went into the Win XP  Device Manager on the LabView system and manually configured Com1 to 2400,7,1,Odd  
    and still,.... the "RS232 RW.vi"  will only operate @ 9600,8,1,None
    Can anyone else test drive my VI and see if they have the same problem of not being able to see new changes in the Port configuration settings ..other than (COM1, 9600,8,1,None...).... ?
    FYI.. Unfortunately my LabView is running on Version 6.0 so you may need to up-convert the attached vi
    Solved!
    Go to Solution.
    Attachments:
    RS232 RW.vi ‏102 KB

    Instead of just appreciating the comments, you need to implement them.
    Having the VISA close inside the loop is definitely the problem.  And Crossrulz is 100% correct about the problem being that the serial port gets reset to the default baud rate after closing the port.  Here is the proof.
    Note that while you may have set the port settings manually in device manager, those settings are revised by the VISA driver.  If you look in Measurement and Automation Explorer under Devices and Interfaces >> Serial and Parallel, you'll see the default settings that the VISA driver uses.  If you change the setting there, your program will work the way you want.  But that is not the correct fix.  The correct fix is to get the VISA close out of the while loop.
    The port settings are established in this order.
    1.  By the Windows device drivers.
    2.  By the VISA driver as established in MAX.  Since you are useing VISA, these settings will automatically override #1.
    3.  By the port settings you set programmatically in your LabVIEW program.
    Attachments:
    Example_VI.png ‏18 KB

  • How can i browse FP 2000 via serial port same use Ethernet port(RJ 45)?

    I am a new user for  labview.I develope my program with FP 2000 but I have some problem
      1 How can i browse FP 2000 via serial port same use Ethernet port(RJ 45)? if it can Tell me please.
      2 If  I use GSM/GPRS modem via FP 2000 rs 232 port (I under stand how to send AT command) and leave it stand alone
         Can I dial modem and browse file in FP 2000 same as use Ethernetport?
    Someone please help me.Thank you very much.

    Hi!
        First, I can say that your project involves many things, I cannot describe all features in the forum, and I'm not used with GPRS modems (my modems are base band serial modems...).
        Anyway, I would say that in your project you should proceed like this:
          1) Configure your FP 2000 module via MAX and ethernet connection;
          2) Download an embedded application to your module (build in LabView Real-Time)
          3) In your application, you should build a kind of serial port manager, and by the means of serial port you send/receive commands from PC.
        The commands from PC can include "Tell me the about the FP 2000 file system ", or "switch on line X", or anything you need.
       I think it would be difficult to use Internet exp, because you use IE with TCP/IP, and TCP/IP is over ethernet.
       I know that for Windows you can find some wrappers that make you "see" the serial port as an ethernet, but these wrapper do not exist under filed Point, and you shoul build one yourself!!!(and that's not easy).
        For example, to browse your files, you should build a VI that searches through your file system, and reports, via serial, the files present in a directory (it's an example....).
        About communication between GPRS modems and FP2000, I know nothing.  I suppose that these modems accept serial inputs, so you'll have to configure your serial port on FP 2000 with the correct baud rate, parity, and so on..... and you send your data to the modem.  The modem will transfer data in its way, no matter on how it does.
        To send data to your modem you shoud take a look to some Serial communication examples.  What I suggest you, first, is to connect the serial port of FP2000 to a PC, and test communication between PC and FP2000, without modems. Just direct cable connection!  If you're able to do this, insertion of modems is the next step, and should be quite easy.  If you're not able to make the PC receive strings of data from FP2000, over  RS232, adding modems is a further complication, and you won't come out of this mess!
       So, what I say, is just build, for now, a simple embedded application for FP2000, that, using RS232, sends data to a PC (you should see data sent with use of Hyper terminal).
        To build this application, use Instrument I/O --> VISA commands (VISA open, VISA write, and Property node should be enough, for now).
       Please, let me know if this helps......
        Have a nice (programming) day!
    graziano

  • Multiple serial ports reading from a shared USB port

    I have a program that reads from 4 flow controllers, which send data through RS232 serial ports. Because the computer is located pretty far away, the vendor suggested to use an Edgeport box to convert RS232 to USB, then convert to ethernet port using a SuperBooster converter. The signal travels long distance in ethernet cable to the computer and get converted back to USB, then to the computer. In MAX, I was able to see 8 com ports from the Edgeport box, and I was able to communicate with my flow controllers.
    The problem is, it will give me some error message occasionally. Sometime it's a VISA Read error, sometime it's a VISA framing error. Could this be caused by the way the signal is transmitted?
    In the program I have four parallel WHILE loops that constantly do READ and WRITE to the 4 flow controllers. Could this be causing the errors? If so, what is the best strategy to design this program?
    Thanks

    I agree with Mike, you will need an error handling strategy that accounts for these errors.  And retries the communications.  This can be a little tricky, but very doable.  I believe some sort of statemachine approach will work best for this. 
    As for your heated probe.  I would make some sort of hardware interlock that will shut it down in case of a coolant failure.  NEVER, EVER trust the computer to be running where safety is concerned, either for personal or hardware.  There are plenty of ICs that can monitor temperature, and have warning, and alarm outputs!  Another option is some sort of watchdog on the communications bus for the coolant control, but I think this is a bit more tricky. 
    Paul <--Always Learning!!!
    sense and simplicity.
    Browse my sample VIs?

  • VISA get resource name doesn't return USB serial ports

    We built an application on a computer that had an onboard serial port - COM1.  We put the option to change the COM port in the application.  We installed the built application on a computer with no serial ports, but installed a USB to serial converter that registers as COM3.  LabView does not see this port, even with a test application to return only the VISA resource names. 
    We have verified that the port is good with another program (a Modbus simulator) and installed the latest VISA runtime v4.41 separately to no avail.
    Any suggestions at further troubleshooting would be extremely helpful.
    Joe T.
    Solved!
    Go to Solution.

    My main application still isn't working, but now the small test ones are.
    Here's what I did:
    1.  Update my LabView 8.5 with the latest VISA runtime - 4.4.  This updated the Installer as well.
    2.  Added the MAX Installer to the build.
    3.  Added  the NI-VISA Configuration Support to the build
    4.  Uninstalled the application and reinstalled it with the new install volume.
    When I run MAX, COM3 shows up.  It also shows up in the Get Resources test application.  The simple test Modbus write program works, too.  I have a sneaky feeling that COM1 may be hard-coded somewhere in the main application; our next task is to find where the communications breaks down in our code.  The bottom line seems to be a lack of experience with the Application Builder on our part.
    Thanks to all who contributed!
    Joe T.

  • Cisco Router 2600 Serial Port communications

    I am working on configuring communications Router to Router through serial port. I have seen some videos and read some documentations. My configuration is as follows: 
    R1 (DCE) -> f0/0 192.168.1.1/24 - s0/0 192.168.2.1/24 <-----> Router2 ->(DTE)  S0/1 192.168.2.2/24 f0/0 192.168.3.1.
    I have configured the routing tables at both routers. It works when I ping from router to router and router to hosts successfully. Nevertheless, I can ping from hosts to the default gateways, but I cannot ping from hosts to the serial ports (adjacency). In short I cannot communicate from Network1 to Network2. Please do I have to do any extra configuration.

    Router 1 (KelliR)
    KelliR#show ip interface brief
    Interface                  IP-Address      OK? Method Status                Protocol
    Ethernet0/0                192.168.1.1     YES manual up                    up
    Serial0/0                  192.168.3.1     YES manual up                    up
    TokenRing0/0               unassigned      YES unset  administratively down down
    Serial0/1                  unassigned      YES unset  administratively down down
    KelliR#show ip route
    Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route
    Gateway of last resort is not set
    C    192.168.1.0/24 is directly connected, Ethernet0/0
    S    192.168.2.0/24 [1/0] via 192.168.3.2
    C    192.168.3.0/24 is directly connected, Serial0/0
    ============================================
    Router 2 (HelderR)
    HelderR#
    HelderR#show ip interface brief
    Interface                  IP-Address      OK? Method Status                Protocol
    Ethernet0/0                192.168.2.1     YES manual up                    up
    Serial0/0                  192.168.3.2     YES SLARP  up                    up
    TokenRing0/0               unassigned      YES unset  administratively down down
    Serial0/1                  unassigned      YES unset  administratively down down
    HelderR#show ip route
    Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route
    Gateway of last resort is not set
    S    192.168.1.0/24 [1/0] via 192.168.3.1
    C    192.168.2.0/24 is directly connected, Ethernet0/0
    C    192.168.3.0/24 is directly connected, Serial0/0
    ============================================
    Even with  f0/0 and s0/0 configured with the addresses in any router, no host at its respective routers is able to ping the s0/0. Hosts are able to ping its ethernet ports.
    See ping comand below:
    From router KelliR
    KelliR#ping 192.168.3.2
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.3.2, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms
    KelliR#ping 192.168.2.1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.2.1, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/36 ms
    KelliR#ping 192.168.2.101
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.2.101, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms
    KelliR#
    ==================================================================================
    From router HelderR
    HelderR#ping 192.168.3.1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 32/33/36 ms
    HelderR#ping 192.168.1.1
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.1.1, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 32/32/32 ms
    HelderR#ping 192.168.1.101
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 192.168.1.101, timeout is 2 seconds:
    Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/36 ms
    HelderR#
    ====================================================
    From Host connected to KelliR
    C:\>ping 192.168.1.1
    Pinging 192.168.1.1 with 32 bytes of data:
    Reply from 192.168.1.1: bytes=32 time=2ms TTL=255
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.1: bytes=32 time=1ms TTL=255
    Ping statistics for 192.168.1.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 2ms, Average = 1ms
    C:\>ping 192.168.3.1
    Pinging 192.168.3.1 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 192.168.3.1:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
    =====================================================
    From Host connected to HelderR
    C:\Users\Helder>ping 192.168.2.1
    Pinging 192.168.2.1 with 32 bytes of data:
    Reply from 192.168.2.1: bytes=32 time=3ms TTL=255
    Reply from 192.168.2.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.2.1: bytes=32 time=1ms TTL=255
    Reply from 192.168.2.1: bytes=32 time=1ms TTL=255
    Ping statistics for 192.168.2.1:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 1ms, Maximum = 3ms, Average = 1ms
    C:\Users\Helder>ping 192.168.3.2
    Pinging 192.168.3.2 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 192.168.3.2:
        Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

  • Motion Control via Serial Port

    I have previously developed an automated video microscope application in Labview. It worked great. My setup was: NI PXI system with 1409 image board, 7344 motion controller, 7764 breakout box, stepper motors, motor drivers, and tables. Now, a customer is requiring that we use a specific brand of drivers that encompass a motion controller and are daisy-chained together. Communication will take place from a serial port, thereby bypassing the 7344. My question is: will I have to can my entire previous Labview motion/data acquisition program b/c I won't be using the 7344 controller? Or, will it be easy to specify in the program to commmunicate via the serial port rather than the card? Would this setup take place in MAX, or in the LabView applicatio
    n itself? Any nuances that I should know about? Any info would be appreciated. THANX-ROB

    Rob,
    in this case you won't be able to use any of your motion related code. The motion VIs in LabVIEW call the NI-Motion driver dll and thus they are not hardware independant. By the way, this is not a specific disadvantage of the NI-Motion driver. In fact there is not such a thing available like a standardized interface and hardware independant motion control language.
    In general you will have to use low level serial communication (VISA). That means you have to read the drive/controller manual, identify the serial command strings you need and send them to the device.
    For configuration the drive vendor should provide a utility to set the necessary parameters.
    On the other hand you could be lucky in the case that the vendor of the drive/controller provides h
    igh level LabVIEW vis. You should check with this vendor if a LabVIEW driver is available. Still you will have to rewrite your motion related part of the code.
    I'm sorry that there are no better news.
    Best regards,
    Jochen
    NI-Germany

Maybe you are looking for