PXI-7344

Hello,
I am using a PXI-7344 board with a UMI-7764 accessory. So I connect it to the motion control plug and it works properly (the 4 axes are all used).
Next, I get a SCB-68 block connector because I need to get 2 more analog outputs.
So, I use a cable SH68-C68-S to connect the SCB-68 block to the PXI-7344 digital I/O plug.
But I don't know in fact how to steer the Digital Output ports from PXI-7344 to use the 2 analog outputs from SCB-68.
Moreover, I would like to know if I can steer both devices from motion port and Digital port at the same time.
Anyone an idea?
Thanks

Hello,
I would like to measure some tests on charts with a PXI-4204 board and to save them in a binary file.
I am using a VI that contains the "Analog 1DI32 Wfm NChan NSamp.vi" (from "Continuous Acq & Graph Voltage to File.vi") to acquire an analog signal.
The problem is that I had to do a "mix" with other vis:
- to be able to save the data into a binary file,
- to be able to see the waveform moving from right to left and to use the X scrollbar.
Now the problem I have concerns the reading.
When I want to use the "Graph Acquired Binary Data.vi" to read the data, there is a message of error that says the input data is not incorrect....
Anyone has an idea?
Please see the 2 files enclosed: "Continuous Binary Acquired Data.vi" and "Read Graph Data Acquired Binary File.vi" (front panel +diagram)
Thanks very much for quick reply
Attachments:
Continuous data acquired (diagram).jpg ‏162 KB

Similar Messages

  • PXI 7344 motion controller as a DAQ device for ELVIS

    Hi,
    Is there a way to reconfigure a PXI-7344 motion controller with its two 68-pin connectors so as to use it as a DAQ device that would receive the signals from a NI ELVIS workstation. The 7344 has a "motion I/O connector" and a "digital I/O connector". Analog outputs are even possible if I remember well, as well as digital.
    Thanks

    Hello,
    The card does has some analog input and outputs. I would check the manual here: http://www.ni.com/pdf/manuals/370838b.pdf. The DAQmx API with a DAQ card is going to be much better than interfacing with a motion card, but you should be able to read off it at the least.
    Rahul B.
    Applications Engineer
    National Instruments

  • HSC limitation​s of the PXI-7344

    I have an application where I would like to measure position data (encoder and analog value) from a relatively fast moving mechanism - so want to use the highest sampling rate possible while keeping both measurements synced. I am using the PXI-7344 for motion control and the PXI-6221/PXIe-6361 for analog DAQ.
    My approach is to use one RTSI line to provide the DAQ sampling clock (possibly divided with a counter for even higher sampling rates with the DAQ card) to the HSC trigger of the PXI-7344. According to the PXI-7344 datasheet, the maximum trigger repetition rate is 1kHz, but the HSC has to be re-enabled in software after every capture. I have a program doing exactly that and it seems to be working fine - but I can't achieve rates on the HSC higher than approx. 150Hz. I assume the bottleneck here is either the host communication (most likely) or the PXI CPU is too slow with re-enabling the HSC (very unlikely - it is a 2.7GHz Quadcore and I am polling the HSC status as fast as possible in a while loop w/o any waits).
    My next approach would be to write an onboard program to do the same thing and write the positions into an onboard buffer which I would read after the program is done, but according to the NI-Motion help these programs run inside the RTOS on the onboard µC with a repetition rate of 2ms, which would mean a maximum HSC rate of 500Hz (theoretical).
    This is of course better than 150Hz, but now I am wondering how I could use the full capabilities of the trigger input of the card (e.g. achieve a HSC rate of 1kHz). Is this even possible/foreseen with the 7344?

    HSC rearming rate is system dependent and affected by many factors. 100 Hz is a rate, that can be achieved on most systems. You might higher rates than that, but that's not guaranteed.
    Onboard programming typically doesn't result in much better results, as the onboard CPU runs the user programs in a low priority task, which gets interrupted frequently by high priority tasks like limit switch monitoring and so on.
    In general that's the bottleneck, that explains the limitation. On a 7344 HSC needs to get rearmed after every trigger occurrence in the user program and in both cases (host and onboard programming) the rearming needs to be executed by a low priority process on the onboard CPU.
    By the way: You are referring to a 2 ms interval. In fact, that's the default value of a time slice assigned to an onboard program. This is not equal with the onboard program's cycle time, which is typically higher - depending on the amount of code and the interrupts caused by higher priority processes.
    I hope that explains the behavior. For higher HSC rates up to 2 kHz please use a 7350 board.
    Kind regards,
    Jochen Klier
    National Instruments

  • Feedback for PXI 7344 motion

    Hi,
    I use the PXI 7344 to control a wave paddle in our wave flume.
    We make regular and irregular waves.
    At this moment I use a timed loop to update the position of the paddle 40 times per second (loop time 25 ms).
    I use a linear interpolation between the current and the next position.
    The reason for not using the contoured move is as follows:
    We have also a active wave absorption system programmed into our controller. It uses 2 analog input of the PXI 7344 and calculates a correction/feedback for the wave paddle.
    Therefor the movement of the paddle is not predetermined and cannot be predicted.
    I would like to use the contoured move to generate a smoother motion of the paddle.
    Is there a way to correct the motion during the exection of a contoured move (like the analog feedback) but then programmatically (by a calculated value ) ?
    Thanks,
    Tom
    Tom Versluys - Dept. of Civil Engineering, Gent University
    Technologiepark 904, B-9052 Zwijnaarde (GENT), BELGIUM
    TEL.: +32(0)9/264.54.87, FAX: +32(0)9/264.58.37, MAIL:[email protected]

    It may be that you have already chosen to map the 7344 to the local machine. That was the case for me - I have a PXI 7344 and PXI 7350, where the 7344 was already mapped to my local machine, and the option to map to local machine was grayed out. Try pressing F5 to refresh MAX and then check under the main Devices & Interfaces tab for the PXI-7344 on IP address.
    Hope this helps.
    -Julie

  • NI Motion + PXI 7344 + s-curves

    I use Labview 7.0 and a PXI 7344 motion board.
    I try to calculate the time and the distance needed for a motorized stage to
    reach a constant speed.
    The Speed, Acceleration / Deceleration and S-curves parameters are known.
    Is there any way (vi or dll) to obtain the theoritical position, speed and
    acceleration Vs time of a movmement ?
    Or is there a way to access the data of the trajectory generator?
    The "motion assistant" plot the position, speed and acceleration Vs time of
    a movmement from the Speed, Acceleration / Deceleration and S-curves
    parameters. Is it possible to have the formulas ?
    Thanks for your help.
    Stéphane.

    Stephane,
    You can use the motion assistant to visually determine the response of the parameters that are entered. At this time the exact formula is not available.
    Austin Talley
    Applications Engineering
    National Instruments

  • What I can do to minimise my offset in velocity in PXI 7344?

    Hi,
    I am using Motion control Card (PXI 7344) to control both position and linear velocity of the cylinder shaft. I am reading analog voltage from potentiometer(input range = -5V to +5V corresponding to positions 100mm and 0mm respectively). I have used DAC output (+10 v to -10V) of the motion control card as in input to Servo valve (Note: i have not used any amplifiers inbetween) which controls the hydraulic flow which inturns controls the linear movement of the cylinder shaft. In the MAX i have used Axis 1 and configured it to velocity mode selecting only the primary feedback and primary output (I haven't used secondary one) and set PID update period to 62.5 microseconds.
    The problems I am facting righ
    t now are
    1. In the 1D interactive control of the MAX I found the current trajectory data (position and velocity) keeps on changing before starting the test (when the station if OFF) after intialising the card. I have check the Analog feedback signal from the potentiometer. It remained constant without fluctuating.
    2. I can't able to achieve the set point velocity (i.e., there is always an offset and it varies with increasing setpoint). So I have used Auto-tuning option in the MAX. It automatically sets some PID parameters but it remains changing when i do it again and again.Eventhough i make changes in the PID parameters, my offset remains the same.
    Whether I have to use Encoders as secondary feedback device or else what I can do to minimise my offset in velocity?

    Project Support,
    After reading over your description, I am still not sure that I entirely understand what is happening. Some of the questions that I have are:
    -What type of motor is hooked to Axis 1?
    -What type of feedback is Axis 1 using?
    -Does the linear movement have feedback?
    If you post back the answers to some of those questions, this forum may be a little bit better equipped to help answer your questions.
    As for the questions that you posed, if you are using analog feedback, and the system issuing that feedback is turned off, then you may be seeing fluctuations from noise in the environment. This is my best guess about what is happening with problem #1. As for problem #2, I don't fully understand what you are asking. If you could post some a
    dditional details about this problem, it may help to resolve the problem.
    I wish you the best of luck with your application.
    Regards,
    Jed R.
    Applications Engineer
    National Instruments

  • MXI-3 with PXI-7344 etc blue screens

    Dear support folk,
    This is a follow-on from unsolved problem discussed below. I have this problem on multiple computers now with varying severities. One machine is unuseable due to the frequency of blue screens. Is it our C-code perhaps? Please help - this problem is going to be the death of me!
    Old question:
    "Okay, this is driving me crazy! I've asked this question before and really didn't resolve the problem fully so here we go again. I have an MXI-3 card with PXI-6052E, 6508 and 7344 in cPCI chassis. Trouble is I get random bluescreen errors (especially towards the end of boot process but they can be anytime). This happens on just about every machine I install this hardware configuartion on. Disabling stuff like the c
    om ports and killing background processes such as virus scanners seem to help a little but have never solved the problem. The latest installation won't go at all and bluescreens every time. I tried a Win 2000 installation and the boot-up blue screens disappeared but our software would not work properly (this could well be our fault though so I will restrict my question to the boot-up bluescreens). Any help would be very much appreciated!"
    Old answer
    "Hi,
    There was a bug in the MXI-3 software that could cause a Windows page fault exception (0xE) on Windows 98. It is very rare, but there is a patch to fix it. I attached it below. If this does not solve the problem, please email us so that we can help you further. Go to http:\\www.ni.com\ask and select Email an Engineer. You will want to select PXI/VXI for the product.
    Thank you,
    Katie Shiels

    Marcus,
    The most common cause of problems with MXI-3 systems is simply not using the correct boot order. I would first verify the proper boot order (chassis first, then computer). Verify that the LINK LED comes on right after the computer boots, and that the LINK LED never, ever, blinks or strobes during operation. If the LINK LED goes out, strobes, blinks, etc, then a hardware problem with the link (PCI-MXI-3 board, PXI-MXI-3 board, or cable) is indicated.
    If you continue to have blue-screens at boot, then the next step is to "divide-and-conquor" the system. What we want to do is make sure that none of the cards in the PXI (or CompactPCI) chassis are themselves causing the problem (for example, if a card has a resource conflict). For troubleshooting purposes, remove all cards from the PXI chassis, shutdown, and then power-up again with the proper boot sequence (chassis first, computer second). If the problems disappear, then a problem or resource conflict with one of the PXI / cPCI cards is indicated.
    If the blue-screens continue, even with the hardware removed, then the next step would be to uninstall the MXI-3 Optimization software. What we are going after here is if it is during the run (every time at boot) of the MXI-3 optimization software that the blue screen occurs.
    If none of these indicate the problem, then the "divide-and-conquor" approach requires us to determine if the problem is with the MXI-3 kit itself, or something specific to that computer. Two things to try. The first is to try the MXI-3 kit on a different machine. The second is to try another MXI-3 kit (if available) with that machine.
    Through these steps, you should be able to isolate a single piece of hardware (a PXI card, the MXI-3 kit, the PC, etc) that is common to the problem.
    (note, the bug referred to by Katie was specific to running the MXI-3 optimization software, not the MXI-3 hardware in general - so if you are seeing the problem she referred to, you should see the blue-screens disappear when the MXI-3 Optimization software is uninstalled).
    As always, National Instruments Technical Support is only a phone-call away (7am - 7pm CST) if you want to work with a NI engineer on this procedure.
    Regards,
    Greg Caesar
    Applications Engineer

  • Can I connect a 15V output Encoder directly to the UMI-7764(PXI-7344)

    Is it safe to attempt the above.?
    Would additional circuitry be necessary ?

    In case you use a simple voltage divider you should clamp the line which goes into the 7344 encoder inputs with 4.7v zener diodes. In case the 'lower' resistor of the divider gets open the input circuitry of the 7344 might be damaged due to excess voltage.
    Also, when using any level converters (with voltage dividers or active circuitry) it is essential to provide a fail safe overvoltage protection to protect the 7344 inputs - and also your computer. The best method is galvanic isolation via optocouplers, but usually these need extra circutry to drive their inputs (they require several mA to drive the LED) and to re-shape their output signals since most optocouplers have rather long rise and fall times.

  • PXI crate crashing regularly

    We have a PXI crate with a MXI link to a PC running labview 6.1 (can't run 7.0 as we are using DCOM to talk to though from a VMS system). This PXI crate is full, there is the MXI card, 4 PXI-7344 to drive 15 motors and 3 PXI-6508 Digital I/O to read 10 absolute encoders. The motors that need to be driven are separated in two categories : 5 are running translation stages, closed loop and 10 are running rotation stages, with absolute encoders (the VI then adjust the motor steppings to get as close as possible to the desired absolute value). So the PXI-cards are not initialised in the same way (fast and closed loop for one of the cards, slow and open loop for two other cards, and one card is a mix between the two). The VI runs fine but everynow and then, one of the PXI-7344 cards crashes. Although very inconvenient, I used to be able to recover the system from home or from my office by using MAX, power up reset (by the way it would be good to have the power up reset button as a VI that could just be run instead of having to run MAX), then I restarted my VI which included some initialisation of the cards. Over the last few days, when I do that, the PXI-6508 cards disappear from the MAX Devices and Interfaces. The only way out is to actually go to the kit itself, turn everything off, physically pull the cards out and restart the system. This happens randomly and I am working a 24h facility which means that I have to fix this at any time during the day and night so I would really apreciate a solution to this.
     Thanks,

    Post the KP report. Then, see
    What is a kernel panic,
    Technical Note TN2063: Understanding and Debugging Kernel Panics,
    Mac OS X Kernel Panic FAQ,
    Resolving Kernel Panics, and
    Tutorial: Avoiding and eliminating Kernel panics for more details.

  • Position Control of compumotor linear servo table and GV-U6E with PCI-7344

    I'm referring PCI-7344 (not 7334).
    I have the GV-U6E which is a drive only and does not possess control functionality. the drive only version does not store or use programs. So, serial commands can not be sent through COM port by LabVIEW even though A few basic commands can be emulated.
    I am trying to do position control as I mentioned. For example, the motor should move A point to B point exactly with a certain speed. The points must be aboulte position.
    I would like you to see the reference comment that I have been contacting with in your website forum.
    http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000DD490000&USEARCHCONTEXT_CATEGORY_0=_14_&USEARCHCONTEXT_CATEGORY_S=0&UCATEGORY_0=_14_&UCATEGORY_S=0
    Regard,
    Jin Ho Lee
    ----- Original Message -----
    From:
    To:
    Sent: Thursday, September 26, 2002 5:00 PM
    Subject: Re: (Reference#1549-QYW196) "Position Control of linear servo table and GV-U6E with PCI-7344
    >
    > Note: Your reference number is included in the Subject field of this
    > message. It is very important that you do not remove or modify this
    > reference number, or your message may be returned to you.
    >
    >
    > JinHo. Compumotor is a very popular brand, and I know of several customers
    > who integrate our 7334 with Computmotor drives. However, when you say that
    > the MAX configuration doesn't fit in the compumotor drive settings, are you
    > referring to the specs from the 7344? It looks like the 7344 and the
    > Compumotor will work well together through a UMI break out box. If you're
    > referring to specific commands that the Compumotor receives, I'd have to
    > know more about the protocol. If the Compumotor needs serial commands,
    > then you can send them through the computer's COM port from LabVIEW.
    > Please let me know exactly what kind of configurations you're trying to
    > set. The 7344 can be completely configured in MAX and LabVIEW.
    >
    >
    > Best Regards
    >
    > Kyle Voosen
    > Applications Engineer
    > National Instruments
    > http://www.ni.com/support
    >
    > ------------------------------------------------------------------------------
    >
    > Problem Description :
    > "Position Control of compumotor 406LXR linear servo table and GV-U6E(motor
    > drive) with PCI-7344"
    >
    > "Since I had the answers referring:
    > http://exchange.ni.com/servlet/ ProcessRequest?RHIVEID=101&RPAGEID=135&
    > HOID=506500000008000000DD490000& USEARCHCONTEXT_CATEGORY_0=_14_&
    > USEARCHCONTEXT_CATEGORY_S=0& UCATEGORY_0=_14_&UCATEGORY_S=0
    >
    > Wiring step was done well. However, I still have a problem that MAX
    > configuration doesn't fit in compumotor drive settings. Therefore, the
    > setup is shown below, and I want to know how I can set up PCI-7344
    > configuration in MAX or LabVIEW VI.
    >
    >
    > -----------------------------------------------------
    >
    > Uploaded from device address 0
    >
    > Gemini GV Servo Drive Setup
    >
    >
    >
    > Motor Setup
    > DMTR 1703
    > Motor ID (406-x-LXR-M-x-D13-x-x-x-x-E5-x-x-x)
    > DMTIC 2.48
    > Continuous Current (Amps-RMS)
    > DMTICD 0.00
    > Continuous Current Derating (% derating at rated speed)
    > DMTKE 17.6
    > Motor Ke (Volts (0-to-peak)/krpm)
    > DMTRES 10.10
    > Motor Winding Resistance (Ohm)
    > DMTJ 119.300
    > Motor Rotor Inertia (kg*m*m*10e-6)
    > DPOLE 1
    > Number of Motor Pole Pairs
    > DMTW 40.5
    > Motor Rated Speed (rev/sec)
    > DMTIP 7.40
    > Peak Current (Amps-RMS)
    > DMTLMN 3.4
    > Minimum Motor Inductance (mH)
    > DMTLMX 3.4
    > Maximum Motor Inductance (mH)
    > DMTD 0.000000
    > Motor Damping (Nm/rad/sec)
    > DMTRWC 0.23
    > Motor Thermal Resistance (degrees Celsius/Watt)
    > DMTTCM 20.0
    > Motor Thermal Time Constant (minutes)
    > DMTTCW 0.33
    > Motor Winding Time Constant (minutes)
    > DMTAMB 40.00
    > Motor Ambient Temperature (degrees Celsius)
    > DMTMAX 90.00
    > Maximum Motor Winding Temperature (degrees Celsius)
    > DHALL 1
    > Disable Hall Sensor Checking
    > DMTLQS 0
    > Set Q Axis Inductance Saturation
    > DMTLDS 0
    > Set D Axis Inductance Saturation
    > DTHERM 0
    > Disable motor thermal switch input
    >
    >
    >
    > Drive Setup
    > DMODE 2
    > Drive Control Mode
    > DRES 8400
    > Drive Resolution (counts/rev)
    > DPWM 16
    > Drive PWM Frequency (kHz)
    > SFB 1
    > Encoder Feedback
    > ERES 8400
    > Encoder Resolution (counts/rev)
    > ORES 8400
    > Encoder Output Resolution (counts/rev)
    > DMEPIT 42.00
    > Electrical Pitch (mm)
    > SHALL 0
    > Invert Hall Sensors
    > DMTLIM 1.5
    > Torque Limit (Nm)
    > DMTSCL 1.5
    > Torque Scaling (Nm)
    > DMVLIM 119.000000
    > Velocity Limit (rev/sec)
    > DMVSCL 119.000000
    > Velocity Scaling (rev/sec)
    >
    >
    >
    > Load Setup
    > LJRAT 0.0
    > Load-to-Rotor Inertia Ratio
    > LDAMP 0.0000
    > Load Damping (Nm/rad/sec)
    >
    >
    >
    > Fault Setup
    > FLTSTP 1
    > Fault on Startup Indexer Pulses Enable
    > FLTDSB 1
    > Fault on Drive Disable Enable
    > SMPER 8400
    > Maximum Allowable Position Error (counts)
    > SMVER 0.000000
    > Maximum Allowable Velocity Error (rev/sec)
    > DIFOLD 0
    > Current Foldback Enable
    >
    >
    >
    > Digital Input Setup
    > INLVL 11000000
    > Input Active Level
    > INDEB 50
    > Input Debounce Time (milliseconds)
    > INUFD 0
    > Input User Fault Delay Time (milliseconds)
    > LH 0
    > Hardware EOT Limits Enable
    >
    >
    >
    > Digital Output Setup
    > OUTBD 0
    > Output Brake Delay Time (milliseconds)
    > OUTLVL 0100000
    > Output Active Level
    >
    >
    >
    > Analog Monitor Setup
    > DMONAV 0
    > Analog Monitor A Variable
    > DMONAS 100
    > Analog Monitor A Scaling (% of full scale output)
    > DMONBV 0
    > Analog Monitor B Variable
    > DMONBS 100
    > Analog Monitor B Scaling (% of full scale ouput)
    >
    >
    >
    > Servo Tuning
    > DIBW 1500
    > Current Loop Bandwidth (Hz)
    > DVBW 100
    > Velocity Loop Bandwidth (Hz)
    > DPBW 40.00
    > Position Loop Bandwidth (Hz)
    > SGPSIG 1.000
    > Velocity/Position Bandwidth Ratio
    > SGIRAT 1.000
    > Current Damping Ratio
    > SGVRAT 1.000
    > Velocity Damping Ratio
    > SGPRAT 1.000
    > Position Damping Ratio
    > DNOTAF 0
    > Notch Filter A Frequency (Hz)
    > DNOTAQ 1.0
    > Notch Filter A Quality Factor
    > DNOTAD 0.0000
    > Notch Filter A Depth
    > DNOTBF 0
    > Notch Filter B Frequency (Hz)
    > DNOTBQ 1.0
    > Notch Filter B Quality Factor
    > DNOTBD 0.0000
    > Notch Filter B Depth
    > DNOTLG 0
    > Notch Lag Filter Break Frequency (Hz)
    > DNOTLD 0
    > Notch Lead Filter Break Frequency (Hz)
    > SGINTE 1
    > Integrator Option
    > SGVF 0
    > Velocity Feedforward Gain (%)
    > SGAF 0
    > Acceleration Feedforward Gain (%)
    > -----------------------------------------------------
    >
    >
    > Regards,
    > JinHo"
    > NI Software :
    > LabVIEW version 6.0
    > NI Hardware :
    > Motion Control device PCI-7344
    > Driver Version :
    > no
    > OS :
    > Windows 2000
    > CPU :
    > Pentium
    > RAM :
    > 128
    > Vendor :
    > DELL
    > Customer Information :
    > Jin Ho Lee
    > North Carolina State Univ.
    > US
    > [email protected]
    > Ph: (
    > 919
    > )
    > 512-9929
    >
    >

    Yes, we used an NI PXI-7344 motion control card with an NI UMI-7764 box connected to a Gemini GV-U12E servo drive. (which is a drive only.)
    We did positional control in absolute position mode.
    I can send you an AutoCAD schematic detailing how to connect the UMI-7764 to the Gemini GV servo drive.
    In regard to the Rs232 interface to the GV servo drive,
    the GV drive only model is "configurable" not "programmable". You can create unique GV configuration files with Compumotor's Motion planner then download the configuration via Rs232 using LabVIEW as desired. Or, using LabVIEW via Rs232 you can change individual GV drive parameters on demand,
    or use the GV's two analog outputs back to LabVIEW's analog inputs to measure commanded motor current or torque, etc.etc.etc

  • How to interface with NI PCI-7344

    Hi,
    First off,i have to say im a newbie with labview so if tis is some stupid qns,my apologies.I nid to work out a program using LabView 8.0 to control a stepper motor thru NI PXI-7344 and the NI UMI-7764. The program is ready with the output as a 32-bit integer, However i am clueless to wad should i connect it to. can some1 kindly plz help me thanks
    ~Nova
    Attachments:
    Example.vi ‏18 KB

    Nova,
    Since you have a PXI-7344, it should have come with the NI-Motion
    driver. Is that something that you have installed currently? If not,
    you can find the latest version here.
    To learn how to programmatically control a stepper motor, you might
    want to start off by taking a look at some of the examples that come
    with LabVIEW. To access them, open up LabVIEW, then go to Help >>
    Find Examples...
    Using the Browse by Task option, expand the Hardware Input and Output
    folder, and then the Motion Control folder. Here you will find many
    examples that you can examine to learn her to program your motion
    control application.

  • Configure Multiple 7344's

    We have an application that requires more than 4 servo motors. We are trying to configure two 7344's in MAX. We've tried it in a PC (2 PCI-7344) and PXI (two PXI-7344). However, they cannot be configured independently in MAX. A change on one board is also reflected on the other (for example, change the encoder counts of Axis 1 on board 1, and Axis 1 on board 2 is also changed). We've got LV RT 6.1/Motion 5.2 on the PXI, and LV 7/Motion 6.0 on the PC (Win2K). HELP!!! Can two or more 7344's coexist in a chassis? Can we do all of the configuration programmatically? We need these things working ASAP...

    The configuration data for NI motion boards are kept in setting records that are identified by their name.
    By default all 7344 boards use the same setting record with the name "Default 7344 settings". In this case it's correct that changes to these settings are reflected for both boards.
    In order to use seperate settings for each board you need to select the "Default 7344 settings" entry in MAX and click on the "Change Settings" button in the toolbar on the right side in MAX. In the following dialog click on the "Create new settings..." button (folder symbol). Now you should be able to use seperate records of settings for both boards.
    Regards,
    Jochen Klier
    Applications Engineering Group Leader
    National Instruments Germany GMbH

  • MXI-4 PXI-PCI bridge

    I tried to set MXI-4cd it but I have a message that says components are already set (NI-VISA...).
    But I have basically a problem with MAX Explorer which does not recognize the PXI system.
    In my PC, the first PCI-slot is devoted to a NI PCI-6052E card.
    The second one is devoted to the PCI8331 card.
    I think the problem comes from the communication between the PCI-8331 in the PCI-slot and the PXI-8331 in the PXI-1031 chassis (bridge).
    But this one doesn't seem to be recognized.
    In MAX, there's just a device PCI-6052E in Traditional NI-DAQ-device or NI-DAQmx-device.
    So if this card is not recognized, then the PXI system (that I powered on) cannot be recognized as well (PXI-1031 and its modules PXI-GPIB, PXI-7344, PXI-4204).
    The communication must be wrong maybe because of the PCI-8331 which is not read from the PC? I wonder if the PCI-8331 in the 2nd slot at the moment should be set in the first slot instead of the PCI-6052E???
    I tried the VISA option in MAX (show ALL PXI-PCI devices accessible to VISA instead of ONLY) and then to restart the system.
    I tried as well to identify PXI as external PC or other (I can't load any PXI-1031 from CD: not a valid file), and to show PXI-buses: but PCI-6052E is shown?
    Note: basically I think I can remove the PCI-6052E board (which we shouldn't use) since the Data acquisition can be down by the PXI-4204???
    Thanks for quick answer.
    Best regards

    Hello,
    Check if your MXI-4 board show up correctly in the Windows Device Manager.
    MXI-4 boards contain two distinct PCI functions onboard and will have two separate listings in the Windows Device Manager (WDM).
    The first function will show up in the WDM listed under System devices as a PCI standard PCI-to-PCI bridge.
    The second function listing in the WDM will show up as a MXI-4 Connection Monitor when the correct MXI-4 driver is installed.
    If the MXI-4 software is not installed, the PCI-to-PCI function will still be detected and work correctly, but the MXI-4 Connection Monitor will be detected as an unknown device.
    If MAX indicates that the MXI-4 connection has timed out, the MXI-4 card did not detect that it was connected to another MXI-4 card at power-up
    time. This can occur if the host chassis is turned on before the expansion chassis, or if the MXI-4 cable is not plugged in properly. (see screnshot attached).
    Hpoe this helps.
    Matthieu G.
    AE, NI France
    Attachments:
    Screenshot.JPG ‏42 KB

  • How to do Torque mode(position-velocity disabled)using 7344 & torque xdcr signal to 7344 ANI chan ?

    Seeking advice on a preferred method to do a torque control application using a PXI-7344, a brushless DC servo motor, digital servo drive/amplifier, a torque transducer as the feedback device connected to one of the 7344's analog input channels.
    I have several torque testing applications and would appreciate comments from anyone who has done torque control using NI Motion.

    There are really two ways that this can be accomplished using the 7344. It can be done manually by reading the value of the ADC and then outputting a corresponding value on the DAC. This is all done in software and is not as fast as the onboard PID loop. This method could also be implimented with a DAQ card.
    The second method would be to set the Primary Feedback for that axis to the correct ADC Channel. Since the ADC is 12 bit, this maps the axis to -2048 to 2047 in counts. Then you could tell the axis to move to a certain target position in counts and it would actually be a torque target value, not position since counts is now in torque. I have not done this but theoretically it should work, however tuning the system may be problematic depending on it's linearity
    Hope this was helpful.
    Regards,
    JR A.
    Applications Engineer
    National Instruments

  • PLL with the Ni 5411 Arb and PXI Star

    I am trying to PLL the NI 5411 Arb with the PXI Star, but I have found no documentation indicating how to do it and it does not appear to happen automatically like some other devices. I currently have a 6608 timing card in the PXI Star Slot.

    The PXI-5411 is capable of Phase-Lock Looping with the 10MHz Backplane clock and is capable of receiving a trigger signal from the PXI Star Trigger line. However, the PXI-5411 is not capable of driving the PXI Star Trigger.
    For more information abotu how the PXI-5411 uses the PXI Trigger Lines, see the "RTSI/PXI Trigger Lines" part of "Chapter 2 - Arb Operation" in the User Manual of the board (linkes below).
    NI 5411 User Manual
    The Example program attached below (written under LabVIEW 6.1) shows how to synchronize two NI 5411 boards by first Phase-Lock Looping (PLL) their internal clocks with the 10MHz Backplane Clock provided by the chassis, and then sending a trigger line from one 5411 (the master board) to the other (the slave board).
    If you want to receive the PXI Star Trigger as the Star Trigger, you will need to use a PXI board capable of sending a signal to this pin. The only NI PXI boards capable of sending a digital trigger pulse over the PXI Star Trigger line are the PXI-5112 (High Speed Digitizer) and the PXI-7344 (Motion).
    The PXI-6608 board is not capable of driving the PXI Star Trigger line, however, if you install the PXI-6608 board in slot 2 of the PXI chassis, it will override the 10MHz clock signal provide by the PXI chassis, with the onboard OCXO 10MHz signal provided by the board itself. The PXI-6608 provides a 75 ppb accuracy 10MHz clock, that replaces the aproximately 50 ppm accuracy 10MHz clock provided by the PXI chassis. By overriding the 10MHz clock with a better accuracy one, the PXI-5411 boards will do PLL using a better reference clock.
    The only device that PLL automatically with the 10MHz backplane clock are the PXI-6115 Simultaneous Sampling boards.
    See related links for more information.
    Hope this helps,
    Claudia Lorente
    Applications Engineer
    National Instruments
    http://www.ni.com/ask
    Knowledge Base 2S2BFCQ7 : PXI Devices That Can Send and Receive Star Triggers
    About Your 6608 Device
    Knowledge Base 2NFGGQAL : OCXO Stability On The PXI-6608 Counter/Timer
    Knowledge Base 2CCF38PQ : Accuracy Problems when I Drive the PXI Backplane Clock with a PXI-6608
    Attachments:
    5411_Synchronize_Generation.vi ‏229 KB

Maybe you are looking for