Creating Labview VI for Newport's ESP6000 motion controller

I am working on creating a Labview VI for ESP6000 motion controller (Newport). I want to move to stages independently one by one and acquire synchronized data from the analog input of the controller during the motion of the one of the stages. If there is anyone working with Labview on ESP6000, I will be glad to dicsuss common issues, obstacles, sub vi's etc.
ceyhun

We built a test station for an automotive component with the ESP6000. The biggest limitation we ran into was the 1000-sample buffer capacity of the analog input. We were hoping that it would behave like the NI DAQ boards. It was not our choice to use the ESP6000. The customer supplied it. The whole setup cost in excess of $9,000. The NI equivalent would be about 2/3 that much. Anyway, Newport supplies a driver that does work. It takes some work to get everything going properly though.
Remember that Alliance Members are here to help. We do this stuff every day.
Daniel L. Press
PrimeTest Corp.
www.primetest.com

Similar Messages

  • LabVIEW drivers for Newport 2010A tunable diode laser?

    My group aquired a Newport 2010A tunable diode laser and failed to receive the labview drivers for remote control operation.  Does anyone have this software?

    All,
       Here is a link to a clean photocopy of the EOSI 2010 laser manual:
    https://wiki.brown.edu/confluence/download/attachments/29406/Diode+Laser+Manual.pdf?version=1
       You can also Google it using "EOSI 2010 laser" and find the maual in the link that says: "EOSI tunable laser diode systems and accessories are guaranteed
    for a period .... the 2010 laser diode. The first
    method is more sensitive but requires both .."  Good hunting.
    Sincerely,
    John Zehnpfennig
    U-Michigan Optics Lab

  • Error -10401 appears when I try to read in my Encoders (TTL-Signa​l) via a LabView-"n​uDrive 2SX-411" and Motion Controller Card

    Hy there.
    Im using two "Haidenhain ERN 420" Encoders with TTL-Output Signal
    A NI-Motion Controller 7334 with an NI-"nuDrive 2SX-411"
    When I try to Read the Encoders Position (with ex.-Programm/Source) the Message: "Error -10401 occurred at AI Group Config ... the specified device is not a NI-product" appears
    Can anybody help me to initiallize/Use the Encoders in Labview 6.01?
    thanks, phil.

    Phil,
    It looks to me according to the error that you were trying to use DAQ functions to access the Motion controller. The Motion controller uses its own functions. There are two for reading position:
    Functions Palette >> Motion & Vision >> Flexmotion >> Trajectory Control >> Read Position.
    Functions Palette >> Motion & Vision >> Flexmotion >> Analog & Digital I/O >> Read Encoder Position.
    You may find a useful example in:
    C:\Program Files\National Instruments\LabVIEW 6.1\examples\Motion\FlexMotion\One Axis.llb\One Axis Move with Position Monitor.vi
    Make sure that you have configured and initialized your board properly in MAX.
    I would suggest that you post your question on the Motion Control section and not in the LabVIEW section. Also, check the Dev
    elopment Library section of the NI Developer Zone for the Motion Control section with tutorials and example code.
    Good luck!
    Nestor.
    Nestor
    National Instruments

  • Looking for LabView driver for Suruga-Seiki motorized stage controller model D70

    I'm Looking for LabView driver for Suruga-Seiki (Japan)motorized stage controller model D70, GPIB or RS232 (optional model D92).

    Hi,
    Unfortunately, I was unable to locate a driver for your instrument. I would like you to submit a request for this driver at: http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/ and with the instrument manufacturer. We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
    If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
    http://www.ni.com/devzone/idnet/development.htm
    We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize in driver development. I would s
    uggest contacting one of the Alliance members at:
    http://www.ni.com/alliance
    An instrument driver is a collection of functions that implement the commands necessary to perform the instrument�s operations. In short, someone read the instrument user manual and implemented some of the functionality in a program for the end user. Instrument drivers are not necessary to use your instrument. They are merely time savers to help you develop your project so you do not need to study the manual before writing a program.
    There are example VI's in LV on Instrument Connectivity. If you go to the Help menu >> Examples.. >> I/O, you will see a couple and Examples.. >> Fundamentals for File and String manipulation. I would suggest tweaking them to suit your application. Also the specific command that your instrument responds to can be found from it's manual.
    Some useful resources for your application are
    ni.com > NI Developer Zone > Development Library > Instrument Connectivity
    http:/
    /search.ni.com/?col=alldocs&layout=TechResources&ql=a , to search examples and knowledge bases
    Hope this helps!
    Best Regards,
    Aaron K.
    Application Engineer
    National Instruments

  • Does sombody have a labview driver for the Scanlab rtc2 scanner controller

    From the German firm Scanlab we have a RTC2 isa card with a dll. Has somebody already written a labview driver for this card ?
    greetings from the Netherlands

    Hello Martin,
    First, don t worry it shouldn t be very complicated  I work at a reasearch center with physicist and an hospital with physicians, we probably work on something very similar, like eye surgery assisted by laser
    1- First thing first, does your scanner works with the examples provided with Scanlabs? ex.: "Hpgl.exe" with an "*.PLT" file?
    2- If so, have a look at my load correction subVI, I always do a reset before I start working with the scanner control, only once at the beginning. If the function returs :"0" zero, it s working if not, come back to me.
    regards
    Lukasz
    Attachments:
    LOAD CORR FILE (SubVI).vi ‏9 KB

  • Labview examples for Newport rotation stage Model URS50BBC

    Hi there,
    I am currently wanting to control the motion of the motorised mount using Labview, but I dont have examples, Can you ,possibly, help me please?
    The mount Model is: Newport rotation stage Model URS50BBC.
    Thank you ,
    Maab

    Hi CasiL,
    Thank you for this.
    I doenloaded them, and it is Ok now, however , the example need COM adress ,when I put 1 , it says : failed in connection and somthing about VISA identification..
    I dont know how can I found VISA or code library,I will attach the error box.
    Thank you very much,
    Maab
    Attachments:
    error labview capture.JPG ‏256 KB

  • Creating LabVIEW Executable for sub-20 Multi Interface USB Adapter

    Hi
    I'm using Sub-20 Multi Interface USB Adapter (www.xdimax.com) for GPIO and SPI. The code is based on .NET constructor Node. I can access the device and perform all the tasks but I'm unable to generate executable.
    The application comes up with this error (on any machine including the development machine)
    "This VI is not executable. The Full development version of LabVIEW is required to fix errors"
    I'm using labVIEW 8.2 and .NET Framework 4 is also installed.
    Thanks

    Hi AA76,
    That is good to know, at least we know the cause of the error.  The KB - How LabVIEW Locates .NET Assemblies shows the LabVIEW search directories.  I suspect what is probably happening in this case is the relative path.  If the system is looking for the same relative path this is probably different. You say that even on the development machine the .exe does not load the library.  Is this when you have just created the .exe or after running the installer?  If it is after running the installer what about before you build the installer?
    Finally where is the assembly located?
    Regards,
    James
    James Mc
    ========
    CLA and cRIO Fanatic
    wiresmithtech.com/blog

  • Creating LabView application for VME-GPIB device

    I am trying to learn how to create software for controlling GPIB devices attached to the VME-GPIB board. One application would be for a setup where Labview is the software used. Another is a real-time system developed with VxWorks.
    It seems to me, that in order to be able to create such a LabView application I need detailed information on the VME-GPIB VME memory layout and definitions of all of its registers. Am I right assuming that? Suppose that I am right, where can I get such detail information on the VME properties of the VME-GPIB device?
    I found such a document for the GPIB-1014 device, which seems to be a precursor to the VME-GPIB device.
    Am I correct assuming that such manual would also be essential for writing VxWorks software as well?
    Thanks in advance,
    Zen

    Zen,
    I have received your support email regarding this issue and currently working on getting you the needed information. I will contact you when it is ready.

  • LabVIEW Application Developer (CLA) - Provide LabVIEW solution for SME & MNC - Singapore based

    Hi ,
    I have accumulated years of experience in creating LabVIEW application for SME & MNC.
    In order to deliver quality solution to customer, please expect the following routine:
    Requirement gathering on software application.
    Translate business requirement into software specification, software model and architecture.
    Application coding and regular review with client. 
    Continuously application improvement and maintenance based on user feedback.
    Part of my experiences: 
    LabVIEW application development with rich-GUI features.
    Process automation or data analysis through communication (Express Controller/Serial/USB/Bluetooth etc.) in between customized hardwares and LabVIEW application.
    High pincount Digital data generation & acquisition. 
    Provide best-fit NI PXI hardwares (Digital/Analog/Serial IO/PMU etc) for customer's business requirement. 
    Visual Studio.NET programming, SQL, Scripting. 
    LabVIEW Real-time, LabVIEW FPGA
    Please feel free to drop me an email at [email protected] for a non-obligatory discussion. 
    Thanks for reading. 
    Regards,
    Drawsome

    Please look into my profile at linked in https://in.linkedin.com/in/prashantpatel21 I m interested.
    Regards,
    PBP (CLAD)
    Labview 6.1 - 2014
    KUDOS ARE WELCOMED.
    If your problem get solved then mark as solution.

  • LabVIEW driver for a ControlTechniques motor controller

    Anyone know of LabVIEW driver for a ControlTechniques
    Unidrive motor controller?
    Or any info/pointers to programming them via LabVIEW?
    Any help much appreciated
    Paul
    Dr Paul Rocca - Managing Director
    Brill Engineering Ltd, 3 Longwood Court,
    Love Lane, Cirencester, Gloucestershire
    GL7 1YG. www.brill-eng.co.uk
    Phone: 01285 883888 Fax: 01285 883876
    NI Alliance Member Since 1992
    Please note that calls may be recorded using our leading edge digital
    recording product AudioPC.
    Any opinions expressed in the email are those of the individual and not
    necessarily of the Company. This email and any files transmitted with it are
    confidential a
    nd solely for the use of the intended recipient. It may
    contain material protected by lawyer-client privilege. If you are not the
    intended recipient or the person responsible for delivering to the intended
    recipient, be advised that you have received this email in error and that
    any use is strictly prohibited. If you have received this email in error ple
    ase notify the Security Manager by telephone on +44 (0)1285 883821 or by
    email to [email protected]

    LV can interface to 232, 485, Devicenet... depending on what the controller has.
    You could find a LV/CVI driver for this (232/GPIB/ethernet only) instrument at http://www.ni.com/devzone/idnet/default.htm . If it's not listed there, it leaves you with one of a couple options. First, I would like you to submit a request for this driver at: http://zone.ni.com/idnet97.nsf/instrumentdriverrequest/
    We develop drivers based on demand and popularity so the more requests we have for it, the greater the possibility that we will develop one.
    If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
    http://www.ni.com/devzone/idnet/development.htm
    We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
    http://www.ni.com/alliance
    An instrument driver is a collection of functions that implement the commands necessary to perform the instrument�s operations. In short, someone read the instrument user manual and implemented some of the functionality in a program for the end user. Instrument drivers are not necessary to use your instrument. They are merely time savers to help you develop your project so you do not need to study the manual before writing a program. With all of this work already done for you in the driver, instrument drivers can significantly reduce development time.
    There are example VI's in LV on Instrument Connectivity. If you go to the Help menu >> Examples.. >> I/O, you will see a couple and Examples.. >> Fundamentals for File and String manipulation. I would suggest tweaking them to suit your application. Also the specific command that your instrument responds to can be found from it's manual.
    Some useful resources for your application are
    ni.com > NI Developer Zone > Development Library > Instrument Connectivity
    http://search.ni.com/?col=alldocs&layout=TechResources&ql=a , to search examples and knowledge bases
    Hope this helps.

  • How do I get labview for linux to send out ascii code to a motion controller?

    I have posted part of this problem but I will now try to clearify things. I have an x-y stage that needs motion control. I have to run the motion controller from within a linux system (RedHat 7.1) due to others in the research area. I have found a motion controller card (PCI) that will run under linux. This card is not National Instruments. I understand that they do not have drivers for their controller cards. This other card comes with the companies own software that uses ASCII codes to move the motors on the stage. I was hoping to create a program that could call those ASCII codes to move the stage. An example would be if a user wanted to have the stage move to the right he would press a b
    utton on the screen instead of typing in whatever ASCII could that move to the right happens to be. How would I go about programming something like this? I have heard of others doing things like this but I am unsure of how to program labview to send out ASCII codes to a PCI card to move motors.

    > would I go about programming something like this? I have heard of
    > others doing things like this but I am unsure of how to program
    > labview to send out ASCII codes to a PCI card to move motors.
    Look in the manual to see get familiar with the sequences of codes you
    need to write, and more importantly, where you write them to. I suspect
    a memory location, but it could be a socket or port.
    Each of these locations will have a slightly different way of accessing
    it. Once you know, search devzone for how to do it on linux, or post
    back here.
    After you can send the codes to the right location, you probably want to
    build a state machine that simplifies the interface and prevents certain
    actions from taking place. Now determine which buttons or
    keys perform
    which actions and use either the event structure or the older polling
    for control changes to affect state changes in the state machine.
    I'm summarizing here assuming that you know what a state machine is and
    why you'd want to use it. If I'm assuming too much, do some research
    and post again with more specific questions. Also be sure to look at
    example VIs as they show how to respond to UI actions.
    Greg McKaskle

  • Creating a Labview VI for controlling an Atmel at32uc3a1512 device.

    I have a custom device that has a USB port and an ethernet port,
    This device (and it's USB port) are controlled by an atmel at32uc3a1512.
    I have an old version of Labview (V8.2) nd I would like to create a VI to communicate and pass data
    back and forth with an Atmel at32uc3a1512 but I am not sure how to create a driver for this with the MAX utility.
    The device shows up in my Windows XP control panel as a USBLib device...
    Any direction, suggestions,  or links to examples or whitepapers on this is appreciated
    thanks

    Hello Japper,
    If you would like to attempt to communicate to the Atmel at32uc3a1512 as a device using USB, then the following tutorial should be useful. This details how to use NI-VISA to communicate with a USB device, however this requires detailed knowledge on how the device sends, receives, and processes data.
    USB Instrument Control Tutorial:
    http://www.ni.com/white-paper/4478/en
    If you are attempting to write LabVIEW code that will be deployed to the Atmel at32uc3a1512 as a target then that is a whole different set of needs. This device is not an officially supported target, and would require a significant amount of modification and tweaking in order to get this to work, if it is possible. The best resource that I can provide for that would be this guide on how to port LabVIEW to ARM devices. I understand that the Amtel at32uc3a1512 is not an ARM device, however this would be the closest guide that we have for porting LabVIEW as a target VI.
    LabVIEW Embedded for ARM Porting Guide - Chapter 1: Introduction:
    http://www.ni.com/white-paper/6994/en
    Let me know which method you are attempting to use the Amtel at32uc3a1512 as; either a target, or a device.
    Thanks,
    Joel
    Motion PSE
    National Instruments

  • Driver for MM4000 series (motion controller) for labview 6.1 (gpib)

    Hello,
    I need the instrument driver for a newport motion controller MM4006.
    I found the driver for MM4000 series, it could be ok, but I need it for labview 6.1 and not  for labview 7 or 8.
    Is it possible to find this driver for older version of labview than 7 or 8?
    Thanks
    Best regards.
    Ludovic

    Good idea, I'm not sure of the result, but... Here is the zip file (aviable here).
    (oups, you were faster ^^)
    Message Edité par Mathieu R. le 12-08-2006 05:19 PM
    .mrLeft{float:left} .mrInfo{border-left:solid 1px #989898;font-size:x-small;color:#989898}
    Mathieu R.  
      CTD - Certified TestStand Developer / Développeur TestStand Certifié  
      CLAD - Certified LabVIEW Associate Developer  
    Attachments:
    npmm4000.zip ‏419 KB

  • How do I create Labview VISA ports for *individual* GPIB instruments using Prologix USB GPIB controller?

    Hello,
    I'm trying to use a Prologix USB GPIB controller to control GPIB
    instruments, and I would like to have a virtual serial (VISA) port for
    *each instrument*, as is the case with a normal GPIB controller with a
    standard NI driver. However this is not what the Prologix driver
    provides -- it provides a single VISA virtual serial port for the
    entire controller. To address the instrument with GPIB address 11,
    you first send "++addr 11" to the serial port, and then you're talking
    to instrument 11. However, this means I have to change all old
    Labview programs.
    Is it possible to create a "wrapper" function of some kind that will
    define a virtual serial (VISA) port for each *instrument* on the
    controller? For example, to talk to GPIB instrument 11, call it
    ASRL3::11::INSTR, each time it is written to it would have to write to
    the virtual serial port of the controller, say ASRL3::INSTR, first "+
    +addr 11" and then the command that is sent to it.
    A clearer explanation of the difference (i.e. incompatibility), and of
    my objective:
    1) A normal GPIB controller with NI driver: I go to the NI
    Measurement & Instrumentation Panel, under GPIB, and Scan for
    Instruments; all the live instruments show up; subsequently when I
    want to use Labview programs that use VISA ports, the VISA drop boxes
    allow me to choose a different port for each instrument, e.g.
    "GPIB0::11::INSTR", "GPIB0::12::INSTR" would be instruments at
    addresses GPIB 11 and GPIB 12.
    2) The Prologix GPIB controller that plugs into a USB port: In
    Labview you get a *single* VISA virtual serial port, ASRL3::INSTR, for
    the entire GPIB0 controller. Therefore to address GPIB instrument 11,
    you write "++addr 11" to the virtual serial port ASRL3::INSTR, and
    then you are communicating with device 11, so you can write and read
    ASRL3::INSTR to talk to that device. Then to talk to device GPIB 12,
    you write "++addr 12" to the same VISA port, and then you are talking
    to that device. The problem is that this requires recoding all
    Labview code, whereas I would like to be able to use the same program
    either with a normal or with a Prologix GPIB controller. Therefore, I
    would like to create code that scans the controller for all GPIB
    attached devices and creates VISA ports for all. Such ports, when
    written to, would have to first write "++addr DEVICENUM" to
    ASRL3::INSTR (i.e. the port of the GPIB-USB controller) where
    DEVICENUM is the GPIB address of the instrument corresponding to that
    port, and then would have to do a write or read or whatever function
    is being done on that instrument VISA port.
    I haven't figured out if it is possible to do this easily. Help and
    pointers on where to look for hints would be much appreciated. Many
    thanks!
    Milos

    My first impression is that if you don't want to make any changes at all to existing programs is that the wrapper you need is one around VISA. You would need to intercept all of the calls into the NI VISA driver. If you create your own visa32.dll and in there, change the addressing and then call the real VISA driver, you might (repeat, might) get something to work. If this would even work, you still might find that you have to make significant changes anyway. The serial connection is going to be considerably slower, and interface specific functions such as service request handling, bus triggering of multiple instruments, etc., would be difficult to impossible. This would be a lot of work, imho, to just save a couple of hundred dollars over a real GPIB controller. I've seen this Prologix device before and have even used NI's RS-232->GPIB controller. The Prologix intended use to me seems to me more for a hobbyist or very casual user. Of course, I'm used to having multiple GPIB instruments worth 10s/100s of thousands of dollars and the cost of an fully compliant GPIB controller is just lost in the noise.

  • Creating Photoshop buttons for motion menus and photoshop menus

    Hi I need to create buttons in photoshop for both a photoshop menu and a motion menu on DVD studio pro program
    Can someone tell me how to do it on both different menus?
    I really need some DETAILS on how to do it. Thanks for your time and responses ahead of time

    OK, here's what I recommend you try...
    Create the footage for your motion menu background. In that footage fade in the button shapes and text for the buttons exactly as you want them to appear. Hold the final position of these buttons for at least 30 seconds. save an image of the still portion to act as a guide in photoshop. Encode that footage to MPEG2 using Compressor and import it in to DVDSP.
    Take the still image in to photoshop and add a single layer to the file. On the new layer, create a shape of some kind (an underline, tick, circle, cross, box around, arrow, etc) next to the background button text. Make these shapes (for each piece of background text) black, and leave the rest of the layer white. Hide or delete the background layer and save the result as a .pict image. Import it in to DVDSP.
    Take the motion footage and drop it in to a menu. use the loop point in the property inspector to define where the 'still' portion of that footage begins. Now drag the .pict overlay image in to the same menu, but hold it a second until the contextual menu appears... set it as the overlay. Drag out button rectangles around the background text and position for the shapes in the overlay. Make sure the rectangles don't overlap, and set up the target for these buttons as well as the navigation between them.
    Use the property inspector to adjust the colours for the overlay - set it to be a simple overlay and in grayscale. What should happen is that when the menu plays the animated sequence starts first but as soon as the loop point is reached the overlay becomes active. The first button defined will be set as selected. You should now see the menu with the buttons faded in to position and the buttons should be clickable.
    When returning to this menu you may not want the viewer to sit through the animated sequence each time. Use a script (in DVDSP4) to specify that they return to the loop point only (the bit where the buttons are) or create a second menu that is identical to the loop point and send the viewer there instead.
    As you can see, there are several steps involved and I have made assumptions that you know something about menus and constructing buttons. It is all in the manual, but you will need to be familiar with Photoshop (or whatever image editor you prefer) to do this properly.
    You do not need to try to make four layer shapes and bring them in to the menu, and if you attempt to add anything else from the templates panel to this menu then the image quality will suffer as DVDSP builds the disc. If you do want to add other shapes and text to the menu then don't do the export to MPEG2... keep it as a simple QT .mov file.
    Please let us know how you get on after trying this method, and after reading up on those manuals

Maybe you are looking for