Onboard Variables in PCI 7344

Hi,
I am trying to use the 120 onboard storage locations provided PCI 7344 motion controller. Firstly, i'm not able to store floating point values in it. If I try to store 25.234, it takes in only takes 25. I have somehow overcome the problem by multiplying my number by 1000 while storing and dividing by 1000 after retreiving it, so that the decimal value vanishes while storage. I would like to know if there is any other way. Secondly, the card is able to remember the values only till my PC in ON. The data is lost once the PC is restarted. Please suggest a solution for this.
Regards,
Giridhar Rajan
Automation Engineer, Design
Cruiser Controls
Mumbai, India

Giridhar,
all the calculations on the 7344 are done in fixed point integer
arethmetic (DSPs and FPGAs typically don't support floating point
numbers). That's why onboard variables can only store integer values.
Onboard variables reside in the board's RAM so the values get lost when
the PC is turned off. If you need these values even after a restart of
your PC you will have to store the values to non-volatile memory before
turning off the PC and load them again to the onboard variables after a
restart. You could either store the values on your computer's harddrive
or in the ROM of your 7344 by using the Object Memory Managment
function. For the latter option you will have to write the onboard
variables to a buffer first and then store the buffer to the ROM.
I hope this helps,
Jochen Klier
National Instruments Germany

Similar Messages

A large program with MANY .vi's loads an onboard program to a 7344 board, later in anothor .vi I load a value into var = 1. and then run Onboard program. Program runs but value of var =1 is not used.

Onboard program calls the "Load constant to variable.vi" in first block. Same call is made in labview code just before the run program block. the variable in the onboard program ALWAYS defalts to (0). WHY???

Hello,
Thank you for contacting National Instruments.
My guess is that the variable is being overwritten by the first call (Load Constant to Variable VI) of the onboard program. The order of operations for the second VI appears to be the following:
1) Load Constant to Variable (variable 1 = 10000)
2) Run the onboard program
3) Onboard program calls Load Constant to Variable (variable 1 = 0)
Any value that the first step of the onboard program loads (step 3 above) will overwrite the value loaded just before the onboard program runs (step 1 above).
I have attached an image of the block diagrams for both VIs I used for testing. The first VI loads an initial value into variable 1, starts program storage, loads position, loads veloci
ty from variable 1, loads acceleration and deceleration, starts motion, then ends storage. The second program simply loads a new value into the variable then runs the stored program. As the variable value in the second program is modified, the velocity changes appropriately. I tested this with a PCI-7344 in LabVIEW 7.1 with NI-Motion 6.1.3.
Hopefully this will help you track down the source of the problem.
Best Regards,
Jesse D.
Applications Engineer
National Instruments
Attachments:
OnboardTestImage.JPG ‏36 KB

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

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

First of all, before connecting the drive to the 73xx controller I would check that the drive and motor configuration works correctly independent from the controller. The Gemini drives have a utility called the Motion Planner that allows you to configure your motor and drive for independent operation so you can test if the motor and drive combination are working by themselves. Refer to page 18 of the Gemini GV installation guide which you can find at the compumotor site or download from:
http://www.compumotor.com/manuals/gemini/Gemini_GV_HW_Install_Guide.pdf
Once you have tested your motor and drive combination, make sure that the drive is configured in torque mode and that the command signal is configured to be sent from the I/O connector and not through RS232 using the Motion Planner. The next step would be to connect the 7344 through the UMI-7764 breakout box in the following order:
---- UMI7764 GVU6E
---- AOut Cmd+ (pin23)
---- AOGnd Cmd- (pin24)
---- InhOut Enable- (pin2)
---- +5V Enable+ (pin24)
7344 --> EncA AX+ (pin8)
---- EncA- AX- (pin9)
---- EncB BX+ (pin10)
---- EncB- BX- (pin11)
---- Index ZX+ (pin12)
---- Index- ZX- (pin13)
---- +5V Encoder +5V (pin5)
Verify that your enable line is connected in an open collector mode (as shown in the diagram above). Our inhibit outputs can sink current but not source it so if your enable line is not behaving properly you want to make sure that the +5v supply you are suing for the UMI can source enough current for your enable line to work. Consult Compumotor on the specs of their enable switch.
Once the connections are done properly, all you need to do is configure and initialize your board for servo operation in MAX and then you can start your tuning process. Refer to the Tuning PID for servos tutorial in:
http://www.ni.com/support/motnsupp.htm
for instructions on tuning your servomotor properly. Also for more information on using MAX, refer to the following tutorial:
http://zone.ni.com/devzone/conceptd.nsf/webmain/081957EE013C7A4586256B92007818E0?opendocument

How to get a stable DA output without feedback in PCI-7344

I have a motion controoler PCI-7344 to control a PZT stage without any kind of feedback. And PCI-7344 is expected to act as a DA output with trajectory generation and onboard programming. But I am confused about how to configurate this motion card.
Another thing I want to know is what is the normal noise level of the DA output. My card's noise is very large(roughly 70mV RMS). Is this noise is normal for the PCI-7344? Or this noise is caused by my incorrect configuration and use of PCI-7344. I have tried to use the analog feedback and none feedback to configurate motion card, and the noise are the same.

If you just want to output a trajectory profile without feedback a multifunction board like the PCI-6229 would be a better choice. Simply precalculate your trajectory profiles and send them to the outputs of the board.
Best regards,
Jochen Klier
National Instruments Germany

Open Loop Problem of PCI-7344

Dear Partners
I have a big trouble....
Any suggestion would be appreciate!
Here is the hardware and software that I am using
S/W : MAX 3.1.1
           LabVIEW 7.1
           NI Motion 7.0
H/W : PCI-7344
           UMI-7764
           YASKAWA Servo Driver
I've tested my motion B/D step by step
1) Start Max3.1.1 / MySystem / Devices and Interfaces /NI Motion Devices /
       PCI7344(1)/Interactive/1-D Interactive
2) Slect "OPEN LOOP"
3) Input steps : Velocity, Acceleration, Deceleration
4) Input steps : Target Position = 100000
5) Click "Apply"
6) Click "Start"
But sometimes it stops generating steps.
it occurs very very irregularly.
I can't understand because I use "OPEN LOOP"
and "Current Trajectory Position" must increase until "TargetPosion" whether the asis move or not.
Also there is no limit signals..
Please see the image file attached.
It's very simple I control motion b/d with OPEN LOOP MODE.
and, I think the servo Driver works well because command steps and encoder pulses are equal.
Please Help me!!!
Crane
Attachments:
7334error.GIF ‏117 KB

Thank you Jasper S.
I think you understand me well.
I tell you more informations.
1) The computer is working in Windows XP Professional (Just Theme).
2) It happens also at low velocity and acceleration.
3) I think when the motor stops moving, it fails to translate into hardware steps.
Because when the motor stops, "Current Trajectory Position" and "Encoder Counts" are equal.
4) I checked status registers on the card when it works abnormally, but can't find any error message and flgs.
5) To make matters worse it happens occasionally, so it's difficult to find out the reason.
6) Strange as it may sound, when I touch the motion connector correctly,  the abnormal behavior frequency decrease.
So I tried to exchange a new motion b/d and a motion cable but it was just same error situation.
I can't understand because I just use "OPEN LOOP",  it is no matter whether servo driver works well or not.
7) Do I have to change PC? I already tried to exchange PCI Slot position.
I need more information about this.
I'm in trouble because this system is operating at foreign country.
It is fatal error even if it happens once per day....
Please help me once more. Thank you.

PCI-7344 not found in MAX 3.1.1 after installing NI-Motion 7.0

Hi,
I updated my PCI-7344 + LabView 7.0 system with the newest NI-Motion 7.0. After the update the card was not anymore detected in MAX. There was a "broken" device PCI-7344 under NI Motion Devices, which status said something like "This device has been removed or could not be detected" and the Reset command said something like "Could not communicate with the device. Power cycle the computer..". I removed the device from the "Devices and interfaces" list and since that, MAX hasn't had a clue about the card. I've tried the "Create new.." function, but it doesn't show any NI Motion Devices or PCI-7344 anywhere else. I've also tried the Tools/Install legacy driver support, but MAX only notifies that the updates are OK. I've also tried removing the physical device, starting the computer and MAX, reinstalling the device and restarting MAX, but nothing changes. The device is recognised by BIOS as "Unknown device"; in Windows 2000 Pro, the device is well recognised as National Instruments PCI-7344.
One thing that could cause the problem is that I also have LabView 6i installed on the system, although I'm not currently using it for any purpose. Anyway, this seems to prevent the MAX from detecting the correct updates needed when using the "National Instruments Product Updates.." from Tools menu. Perhaps I need some driver software to correct this problem?
I also tried to uninstall the NI-Motion 7.0 and to install the NI-Motion 6.1.5, but after this, the MAX did not work correctly. For example, none of the branches in the configuration tree would expand and the MAX locked up when trying to use the Create New.. / NI Motion Device. Is there a way to uninstall the NI-Motion 7.0 and to replace it with NI-Motion 6.1.5 without removing all NI software from the system?
Before the update, with NI-Motion 6.1.5, the PCI-7344 card was correctly found in MAX and well usable in LabView 7.0.

Jouni,
A valid serial number is any number > 0. If you have multiple boards in you system, they must each have a unique serial number. This would be the case for any board coming out of manufacturing. The board Jochen had probably came from R&D and was a prototype board.
Your problem with downgrading from NI-Motion 7.0 to NI-Motion 6.1.5 was most likely due to the data stored in the MAX database. When you uninstall NI-Motion, the data in the MAX database remains. The NI-Motion 6.1.5 driver would not have been able to read the data correctly. The easiest way to "clear" this database is to delete the c:\Program Files\National Instruments\MAX\data folder. The only other way is to uninstall MAX, which requires that you uninstall everything. WARNING, Deleting the MAX data folder will delete all MAX settings and set them back to defaults for all NI hardware (uninstalling everything has this same affect, by the way). Downgrading is never as clean as upgrading.
The firmware on a Motion board can always be downgraded by forcing the download of firmware files. To do this, select the board in MAX under Devices and Interfaces. Click on the Firmware tab at the bottom on the window. Highlight "PCI-73XX Firmware" by clicking on it once. Right click on one of the items in the "Firmware name" column to the right. Select "Download All Files".
I do not have a good explaination for why NI-Motion 7.0 did not recognize your board. Do you have a second board you can try in the system? If not, could you ask your local sales representative if they have one you borrow for a quick test? Since the board is recognized by Windows 2000 Device Manager, I don't think there is an issue with the board, but it doesn't hurt verify this.
My best guess is that there was a confict during the installation process and your system did not get all of the required files. Though we do significant installer testing, there are rare occasions when a system is in such a state that the installation process does not function as expected. It is my experience that these rare instances do not occur on clean machines, but on machines that have had multiple products installed and uninstalled. If you do get a chance to try NI-Motion 7.0 again you may want to use these parameters to get the installer to create a log of the installation: "c:\setup.exe l*v c:\log.txt". This assumes that the setup.exe is in the c:\ directory. Go to start>>run and type this in without the quotes. The log file will be named log.txt in the c:\ directory.
Finally, you can technically use NI-Motion 7.0 in LabVIEW 6. You just need to copy the C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib\Motion folder to the vi.lib folder of LabVIEW 6. Though this is not officially supported, there is no reason it shouldn't work.
Regards,

Connecting Yaskawa Sigma II Servo Drive (SGDH) to PCI-7344 and UMI-7774

Hi,
I have NI PCI-7344 and UMI-7774 and i want to
Connect the UMI-7774 to Yaskawa Sigma II Servo Drive (SGDH) , the servo motor drive is connected to the servo motor with original Yaskawa cables.
1.  do you know if National instruments provide special cables to connect the UMI-7774 to the Yaskawa Sigma II Servo Drive (SGDH) ?
     i know there is special cable to connect this servo drive to the NI PCI-7390
     http://zone.ni.com/devzone/cda/tut/p/id/5908
(you can find in this link that this cable exist: 50 Pin cable for connecting MCA-7790Y to Yaskawa Sigma II Servo Amplifier)
     but this is not the case here, i need to connect the Servo Drive to the UMI-7774..
2. Where can i find a tutorial on how to configure the PCI-7344 in MAX to send simple commands to the Servo Drive
      i.e. to run the servo motor from position A to position B (10,000 encoder pulses)
i'll be gratefull for any help
Regards
Moti

Hi MotiM,
We do not have a cable that will let you directly connect the UMI-7774 to a Yaskawa Drive. We do sell cables that will have the Dsub connector to match the UMI-7774 with pigtails to wire to the drive. If you take a look at the product page for the UMI-7774 you can see the different cables listed under the accessories.
To perform a simple move in Measurement and Automation (MAX) is very simple. In MAX under NI-Motion select your PCI-7344. Under this section select the settings option (by default it will be called Default 7340 settings). Select the Servo radio button. Initialize your controller. Then you can select Interactive and 1-D Interactive and command your motor from there. I have attached an image with the important areas highlighted for you.
Message Edited by Adam_H on 09-19-2008 03:41 PM
Adam H
National Instruments
Applications Engineer
Attachments:
MAX.jpg ‏93 KB

Seems like my PCI-7344 has one axis faulty. Please help

Hi all,
I have a PCI-7344 with UMI7774. I am trying to read the position of a encoder connected to Axis1. But when I move the encoder shaft, the counts dont change in LabVIEW or MAX. When I connect the same encoder to Axis 2,3 or 4 then the change in encoder counts occurs. When I press the "Test resources" button in MAX it says that "The device passed the resource test successfully !". What can be the reason? Does it mean that the UMI 7774 is faulty? What does "test resources" mean??
Regards,
Giridhar Rajan
Automation Engineer, Design
Cruiser Controls
Mumbai, India

Giridhar,
"Test resources" only tests if the PCI-7344 is installed correctly in the PC by checking the communication resources that are assigned to the board. This is not a functional test of the board.
The problem that you see could be caused by a defective UMI-7774, PCI-7344 or the motion cable. If possible please exchange these components one by one with other components that you know that are working properly. I think the most probable reason for this behavior would be a defective UMI-7774 but there is also a small chance that one of the other components is broken.
Best regards,
Jochen Klier
National Instruments Germany

PCI-7344 motion controller encoder reset problem

I'm using a PCI-7344 motion controller for my application. I'm currently working on simple display of position and velocity using an encoder. I am able to read the encoder pulser, but I am unable to reset it. I want the encoder pulses to be display continously till I press a reset button on the screen. After pressing the reset button on the front panel, the encoder count should become zero and start counting again till I press stop button. Kindly give me a simple example of encoder reset using push button. Thanks.
Regards,
Giridhar Rajan
Cruiser Controls
Mumbai, India

This should do what you are looking for. I am not at the computer that has a motion controller card in it, so I have not tested it.
It resets the encoders for Axis 1 and Axis 2. Unless you have a different configuration for encoders and axes, it should work.
Hope that this helps,
Bob
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]
Attachments:
Reset encoders.vi ‏66 KB

Can I use onboard variables for load program delay?

I try to use the onboard function "load program delay" together with onboard variables. The program works and I could confirm with "read variable.flx" that the value has changed.
Versions: lv6x, flexmotion 5x

I am not sure I understand what the problem is. An onboard probgram using variables should work without any issues if you set a delay within it using the load program delay function.

Windows 2000 upgrade from win98--will i have problems with my pci-7344, pci 6110e & ni5411?

I am running win98 with my Labview 5.1. It running fine, but I would like to upgrade the os to windows 2000.
When I was running a check of the hardware, win2k said that the following hardware may not run:
pci-7344, pci-6110 & ni-5411.
will i need new drivers?
will i run into any problems?
any suggestions?
thanks!
Byron Golden
Allied Geophysical Labs
U of Houston

Byron,
You should not have any problems when you upgrade your OS. Depending on what driver versions you have for that hardware, you may want to go ahead an upgrade your drivers anyway, though. The drivers for these devices are all available for free from our website at:
Current Driver Versions
http://digital.ni.com/softlib.nsf/webcategories/9AD71162B755F0E786256BBC005F001A?OpenDocument&node=132060_US
Try that and let me know if you have any trouble.
Regards,
Scott R.
Applications Engineer
National Instruments

PCI-7344 Device status error

MAX returns some errors after PCI-7344 installation with the last NI Motion Driver,
1- Max returns a message: "reset board before update firmware" when I try to update the firmware
2- returns another message: "Restart PC to power supply again the board"
3- When restart PC I obtain two message:
A- NI-PAL Service Manager encountered a problem and needed to close
B- NIMax has encountered a problem and needs to close. We are sorry for the inconvenience
4- Reinstall entire operative System and Driver, Labview and MAX is necessary to obtain a stable function of MAX because these error messages come back after I unistall the PCI-7344 board from PC also. (I use Norton Ghost to restore entire system for my luck)
Thanks for suggestions
Francesco

Assuming NI, the card is a PCI-GPIB.
The error ( Unknown system error (miscellaneous error).), doesn't say much. I would recomend doing the test of the card in MAX and see what happens there. Since MAX does not use VISA for instrument communication, you might have a problem with that though if NI-VISA was not installed at all, you would have a different error code. Is the instrument driver a native LabVIEW driver or are you using an IVI driver? IVI would recquire the IVI Compliance Package installed.

Connecting Yaskawa Sigma FSP Motor Drive With UMI-7774 and PCI-7344

Hi,
i have PCI-7344 and UMI-7774 that i want to connect to this Servo motor drive of Yaskawa.
1) How do i know if this motor drive is compatible with the pci-7344 and umi7774 ?
     for example: inside the UMI manual is written that the Motor drive must support "Sinusoidal Commutation"
     i look indside the Motor Drive manual and i dont found anything about this.
     this is link to the motor drive:
     http://www.yaskawa.com/site/products.nsf/products/Servo%20Amplifiers~fspsigma.html
     http://www.yaskawa.com/site/products.nsf/products/Servo%20Amplifiers~fspsigma.html?openDocument&seq=...
2) How do i connect the feedback and control lines from the UMI to the Motor drive?
i'll appreciate any help including posting a link to a tutorial that helps to understand the signals from the motor drive and the encoder
And also the umi-7344 (Phase A, Phase B, Hall sensor, inhibit, Fault, etc... )
Some powerpoint or Pdf tutorial that National instruments provide will help as well.
P.S. i read the manual of the UMI-7774 and the pci7344 manual, but i'm yet not understand what i need to do
in order to configure my motion system :
PCI-7344 , UMI-7774 , Motor Drive (Sigma FSP Yaskawa) , Servo Motor (Yaskawa)
Thanks for any help.
Regards,
Moti
Solved!
Go to Solution.

Dear Nate,
Thank you for repling to my posts, i really appreciate that.
The links you provide is very helpfull.
i'm enginner in my education, but not in this area (i'm information systems eng.)
i decided that i need to learn more about it (ni-imaq, ni-motion, line-scan camera, servo, servo drives, encoder signals, motion i/o, umi, pci7344, etc..)
So, i download the manual and help files that is needed to my application i want to build
(high speed machine vision of color line-scan camera connected to motion with rtsi synchronization and also digital i/o)
and now i'm reading ALL this, its huge amount to read, and not all the thing i understand in the begining (english is not my lang..)
Thanks again for the replies.
Best Regards,
Moti

Can i connect pci-7344 to my third party motor and drive without umi-7764 ?

Our Lab have NI pci-7344 motion controller and third party motor and drive made by other company.
We want to connect pci-7344 and third party motor & drive without umi-7764.
Just use cable.
Can we succeed to connect them ?

In general it is possible to connect the PCI-7344 to a motor drive without using a UMI-7764 but you will loose some safety features and the level of noise immunity for encoder signals will be decreased.
Please have a look at this link for more information.
Best regards,
Jochen Klier
National Instruments Germany
Message Edited by Jochen on 01-05-2007 10:19 AM

Onboard Variables in PCI 7344

Similar Messages

Maybe you are looking for