Modal error with motion controller PCI-7344 during find reference sequence

I get the following error code when I start a find reference sequence (find encoder index) programmatically:
Error # -70125 occured at FindReference on Axis 1
Possible reasons:
Motion: -70125 (NIMC_wrongModeError)
The function was not executed because it was attempted at an illegal time.
When I do the find reference sequence in MAX, it works fine. But I need I programmatically after the initialization sequence. Does anyone had the same problem?

Hi,
Could you please post a little bit more informations regarding the board you are using, lv version, ni-motion version and perhaps the code, you have programmed and which is generating the error message?
Thanks.
Evrem

Similar Messages

Printing error with t-code j1inmis: Can not find PDL type for output device

Hi,
When using tr.code j1inmis,when we seeing the print preview iam getting below error.
The error with my system show the details as follow :
Cannot find PDL type for output device LP01.
My system is only abap stack.Guide me for the same how to resolve this.
Thanku

Hi,
When i submit the test through URL its working fine(http://192.17.0.12/AdobeDocumentServices/Config).In SM59 Both sides are working.
When I check The Test : FP_TEST_00 iam getting below error
ADS: com.adobe.ProcessingException: com.adobe.Processin(200101)
But
When I check The Test : FP_PDF_TEST_00 its working fine.
And When I check this test : FP_CHECK_DESTINATION_SERVICE without destination its working fine.
When i check with destination iam getting error : SYSTEM ERROR:com.adobe.ProcessingException:Problem accessing data from Destination:dest:FP_ICF_DATA_SMN//sap/bc/fp/form/layout/FP_FORM_SECURITY_TEST.XDP?fp-language=DE.
Guide me for the same two tests are working fine other two are getting error,guide me for the same to solve this,appreciate ur help.
Thanku

Printing error with t-code FBCJ: Can not find PDL for output device prtloc

Hello , folks ,
The error with my system show the details as follow :
Cannot find PDL type for output device prtlocal
Message no. FPRUNX113
Diagnosis
No PDL type has been found for the specified output device.
System Response
Error message
Procedure
Contact your system administrator.
Procedure for System Administration
For more information, see SAP Note 685571.
Our Basis can not solve the problems .
anybody know what's wrong with it ?
Thanks a lot .

other problems could be:
C drive is full
ADS folder under C:\Temp are write protected

Error with Ecc 6.0 install during Abap import of SAPView Package

Hi All,
I am getting error while installing SAP ECC 6.0 SR3 on Windows Server 2008, SQL Server 2005.
all 98 of 99 ABAP imports ran well only at the last import the error was with the SAP View Package.
SAP View Log
=============================================================================
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20300202123417
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe -ctf I I:\51034985_3\EXP3\DATA\SAPVIEW.STR C:\Program Files\sapinst_instdir\ERP\SYSTEM\MSS\CENTRAL\AS\DDLMSS.TPL SAPVIEW.TSK MSS -l SAPVIEW.log
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: job completed
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20300202123425
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20300202123426
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jan 24 2008 01:41:44
C:\usr\sap\C11\SYS\exe\uc\NTAMD64\R3load.exe -i SAPVIEW.cmd -dbcodepage 4103 -l SAPVIEW.log -loadprocedure fast
(DB) INFO: connected to DB
(DB) ERROR: DDL statement failed
(CREATE VIEW [/1CN/AMFSAPH0FOR] ( [CLIENT] , [CPE_CONDTYPE_PR] , [MM_PURCH_ORG] , [MM_VENDOR_GROUP] , [MM_VENDOR] , [MM_SUPPL_VEND] , [KSCHL] , [OBJECT_ID] , [TIMESTAMP_TO] , [RELEASE_STATUS] , [KOPOS] , [CREATED_ON] , [VARNUMH] , [TIMESTAMP_FROM] , [KSCHL_SUPP] , [COND_GROUP_ID] , [MAINT_STATUS] , [CREATED_BY] , [SUPP_EXIST] , [SCALE_DIM] , [CPE_R_RATETYPE] , [CPE_R_RATE] , [CPE_R_CURRENCY] , [CPE_R_PRICEUNIT] , [CPE_R_UOM] , [CPE_F_FORMID] ) AS SELECT T0001."CLIENT", T0001."CPE_CONDTYPE_PR", T0001."MM_PURCH_ORG", T0001."MM_VENDOR_GROUP", T0001."MM_VENDOR", T0001."MM_SUPPL_VEND", T0001."KSCHL", T0001."OBJECT_ID", T0001."TIMESTAMP_TO", T0001."RELEASE_STATUS", T0001."KOPOS", T0001."CREATED_ON", T0001."VARNUMH", T0001."TIMESTAMP_FROM", T0001."KSCHL_SUPP", T0001."COND_GROUP_ID", T0001."MAINT_STATUS", T0001."CREATED_BY", T0001."SUPP_EXIST", T0001."SCALE_DIM", T0001."CPE_R_RATETYPE", T0001."CPE_R_RATE", T0001."CPE_R_CURRENCY", T0001."CPE_R_PRICEUNIT", T0001."CPE_R_UOM", T0001."CPE_F_FORMID" FROM "/1CN/CMFSAPH0FOR" T0001)
DbSlExecute: rc = 103
(SQL error 208)
error message returned by DbSl:
Invalid object name '/1CN/CMFSAPH0FOR'.
(DB) ERROR: DDL statement failed
(CREATE VIEW [/1CN/AMFSAPH1FDT] ( [CLIENT] , [CPE_CONDTYPE_PR] , [MM_PURCH_ORG] , [MM_VENDOR_GROUP] , [MM_VENDOR] , [MM_SUPPL_VEND] , [KSCHL] , [OBJECT_ID] , [TIMESTAMP_TO] , [RELEASE_STATUS] , [KOPOS] , [CREATED_ON] , [VARNUMH] , [TIMESTAMP_FROM] , [KSCHL_SUPP] , [COND_GROUP_ID] , [MAINT_STATUS] , [CREATED_BY] , [SUPP_EXIST] , [SCALE_DIM] , [CPE_R_RATETYPE] , [CPE_R_RATE] , [CPE_R_CURRENCY] , [CPE_R_PRICEUNIT] , [CPE_R_UOM] , [CPE_F_QUANSPLITR] , [CPE_F_COMBROUT] , [CPE_F_FORCOMMUOM] , [CPE_F_FORMQUANCN] , [CPE_F_R3ACCURACY] ) AS SELECT T0001."CLIENT", T0001."CPE_CONDTYPE_PR", T0001."MM_PURCH_ORG", T0001."MM_VENDOR_GROUP", T0001."MM_VENDOR", T0001."MM_SUPPL_VEND", T0001."KSCHL", T0001."OBJECT_ID", T0001."TIMESTAMP_TO", T0001."RELEASE_STATUS", T0001."KOPOS", T0001."CREATED_ON", T0001."VARNUMH", T0001."TIMESTAMP_FROM", T0001."KSCHL_SUPP", T0001."COND_GROUP_ID", T0001."MAINT_STATUS", T0001."CREATED_BY", T0001."SUPP_EXIST", T0001."SCALE_DIM", T0001."CPE_R_RATETYPE", T0001."CPE_R_RATE", T0001."CPE_R_CURRENCY", T0001."CPE_R_PRICEUNIT", T0001."CPE_R_UOM", T0001."CPE_F_QUANSPLITR", T0001."CPE_F_COMBROUT", T0001."CPE_F_FORCOMMUOM", T0001."CPE_F_FORMQUANCN", T0001."CPE_F_R3ACCURACY" FROM "/1CN/CMFSAPH1FDT" T0001)
DbSlExecute: rc = 103
(SQL error 208)
error message returned by DbSl:
Invalid object name '/1CN/CMFSAPH1FDT'.
========================================================================================================
When i clicked on retry i get following additions in log
(DB) ERROR: db_connect rc = 256
(DB) ERROR: DbSlErrorMsg rc = 29
while debugging found that the Table from which it wants to create view does not exsist in database.
Can someone help me with this. I know its common error but most of the earlier threads are with Oracle database has someone faced this issue with Sql Server?
Edited by: darsh4u123 on Jul 23, 2009 8:28 AM
Edited by: darsh4u123 on Jul 23, 2009 8:30 AM
Edited by: darsh4u123 on Jul 23, 2009 8:31 AM

Hi,
This is not a comman error.Sometimes you have to install from the scrach if this error comes.Here the error comes in the last step in sapview creation phage but actual error may happen before this at some step between 1to 99.
Now do below things
First check that your database is up and running.
Then repeat the installation.
If error comes then open the sapinst.log and check what are the steps where the error comes.
Regards
Ashok Dalai

Matching encoder with motion controller

Can the PCI-7332 be used with an encoder having single-ended output? If so, how?
Solved!
Go to Solution.

All of the encoder inputs of the PCI-7332 are single ended. Take a look at chapter 5 of the following manual for an explanation of the encoder inputs and how to wire them. It says 7330, but this is also the manual for the 7332.
National Instruments 7330 User Manual
http://www.ni.com/pdf/manuals/370837a.pdf
Nick Keel
Product Manager - NI VeriStand and Model Interface Toolkit
National Instruments

Problems with a PCI-7344 motion controller

Hi all,
I've run into a weird problem with a NI PCI-7344 motion controller, where I
have a program that provides the motion control for my program that works
reasonably well, but when I make minor changes gets motion errors. The changes
are not specifically to the motion parts, just changing a couple of globals
that provide communication with another part of the program (and another piece
of hardware). The errors I get indicate that I am trying to enable limits
switches at the wrong time in my program. I will add that I do not get any
errors when I go through the program in debug mode
Tnx,
P.W.Monroe

The portion of my program that gets the errors uses the "Flexmotion" Find Home
and Find Index routines, which are built into the 7344 controller. In the
exampes for using these VIs, they are followed by a loop that has a VI that
monitors the status of these VIs for completion, both move complete and Home or
Index Found. The globals that I mentioned are being used to terminate the loops
if an error condition occurs elsewhere, and do not cause the program to do
anything other than terminate looking at the status and then go into a wait
loop. It crashes when it goes into the loop when I substitute a different
global, which is baffling to me, as they aren't triggering something that would
result in a race condition.

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

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

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

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

CPU-Usage during control of a DC Motor with the PCI-7344 board?

Hello!
I want do control a DC-motor (no stepper motor). Now i´m using the PCI-6527 board and simulating the delay between "high" and "low" on the Simulate-signal-vi. This works fine while no other process on the PC is running. The CPU-usage rises up to 100%. Is it possible to use the PCI-7344 board for controlling my DC-motor and having enough CPU resources to do other things like capturing pictures with a cam at the same time? The CPU is a Pentium 3 1Ghz.

The PCI-7344 is a perfect solution for your problem. This board is designed for motion control applications and it's running everything on its own DSP and CPU:
Trajectory Generation, PID control, limit switch monitoring and so on.
Thus the PC's CPU is free for other tasks. Please note that you need a position feedback signal from a quadrature encoder.
Best regards,
Jochen Klier
National Instruments Germany

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,

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

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.

Modal Error at Start Motion.flx

When I try to move an axis past a limit swich using a joystick and the Start Motion .flx subvi I get the following Modal Error.
Error # -70119 occured at Start on Axis 3
Possible reasons:
Motion: -70119 (NIMC_limitSwitchActiveError)
The desired move cannot be completed because the limit input is active in the direction of travel.
I know exactly why the error comes up. My question is:
How can I trap the error before the modal dialog box shows up? I want to be able to hande this error in a more graceful way.
Whe it happens with the Start Motion.flx, the resulting Modal Error is not very damaging to the user experience. However, when it happens during a BLEND move the results are disastrous. Help.
I am using
LabView 7.1 & NI Motion 7.2
Thanks,
Alejandro

Alejandro,
It looks like you have a user that is controlling this motor, and if they happen to hit a limit, you don't want an error to pop up, correct? There are a couple ways to attack this. I'm not positive that this would work, but there is a VI called Clear Errors.vi that clears out the errors that leave a VI. It may be able to clear the error. The better, though a little more time consuming option, would be to set up code to watch for the limits. If the limit switches are on, there can be a case structure that checks if a requested movement goes outside of the limits, and if it does, your program can edit the movement to stay within the limits. Let me know if you have any questions, or want anymore suggestions. Thank you!
-Allison S.
-Allison S.
Calibration Services
Product Support Engineer

Modal error with motion controller PCI-7344 during find reference sequence

Similar Messages

Maybe you are looking for