Labview Code or stepper Problem

Hi guys.
Ive cretaed a VI to control this stepper motor but im getting erratic movement of the rotor but before i troubleshoot the program i decided to open up the motor and found the motor coils to be touching and not correctly wound. I know this is probably the wrong place to post this but i would like to confirm that the stepper is a dud before i continue to troubleshoot my code. Can anyone confrim that this stepper is indeed incorrectly wound??.
Attachments:
IMG_1900.JPG ‏1914 KB

A better scaling of the picture size would have been nice....
However, I have seen worse working, and the wires are coated . Did you measure the resistance between the connectors(and to the housing)?
So let us have a look at your wires... in the diagram and how you connected the motor to the driver. Links to the motor and driver spec are also a good idea.
Greetings from Germany
Henrik
LV since v3.1
“ground” is a convenient fantasy
'˙˙˙˙uıɐƃɐ lɐıp puɐ °06 ǝuoɥd ɹnoʎ uɹnʇ ǝsɐǝld 'ʎɹɐuıƃɐɯı sı pǝlɐıp ǝʌɐɥ noʎ ɹǝqɯnu ǝɥʇ'

Similar Messages

I am trying to have some LabVIEW code called in a New thread exit when the testStand sequence terminates

I have a Sequence that launches a sequence in a New Thread that happens to launch some LabVIEW code. The problem is when the LabVIEW code finishes, it will not close even when the TestStand sequence terminates. Is there a way to tell this LabVIEW code to Exit, I've tried the Quit LabVIEW function, but that causes a C++ RunTime Error. The LabVIEW code does end though, and it is set in the VI properties to:
Checked - Show Front Panel When Called
Checked - Close Afterwardds if originally closed
The sequence call that the LabVIEW code is launched from has the following options:
- New Thread
Unchecked - Automatically wait for the thread to complete at the end of the current sequence
Unchecked - Initially Suspended
Unchecked - Use single threaded apartment
Any clues on this would be appreciated.

Hi ADL,
Everything should close correctly if you check the checkbox "Automatically wait for the thread to complete at the end of the current sequence" in the thread settings.
With it unchecked, I am seeing the behavior you are.
Gavin Fox
Systems Software
National Instruments

GPIB: I am having some problem in running Labview code properly.

Hello,
I have written a labview code to drvie my stepper motor (using GPIB function). This code is supposed to move
the stepper motors and keep updating the current position of motors. I am having an unique problem. This code runs fine for trial no.1st, 3rd, 5th and so on. While it fails to update for trial no 2nd , 4th, 6th and so on.
The main code is "motion_update_Final_Newport.vi". It will work for labview 7 as well as 7.1.
You may not be able to run this code. However, you may be able to understand my error easily as I have figured out where is the error. The update is based on a function, which returns (string) 0 for motion not done and 1 for motion done. This value is diaplayed in "output 1" and works fine. However, "check 2" which is an indicator does not work for trial no 2nd , 4th, 6th and so on.
If you go where I have "output 1", there is a while loop and "check 2" is an indicator for check. It remains on for trial no 2nd , 4th, 6th and so on.
I am attaching the code and this is for ESP 300 motion controller Newport co. I am certain that some of you would be able to figure out the error without running the code.
Thanx in advance,
DushyantMessage Edited by Dushyant on 04-18-2005 04:43 PM
Attachments:
modified_Motion_Update_Final_7.zip ‏228 KB

Thanks a lot for trying to help me.
I am sure that I am not moving any subvi.
Steps that I am trying to accomplish:
(i) I am moving the stepper motors for a relative distance.
(ii) Then I am trying to get the motor position after delay (ms) [defined in front panel].
Now, how I am trying to accomplish:
First outer stacked sequence:
seq 0 of outer: This sets GPIB as controller in command (without this I was having trouble when I was combining this with photodiode code). Please avoid this seq.
seq 1 of outer: The motor moves to certain relative distance. (I do not think that there is anything wrong here).
seq 2 of sequence: This part does updates the motor coordinate after delay (ms). Inside this, there is a case structure to choose whether I want the update.
If I want the update, then following steps take place inside the case structure:
Inner stacked sequence:
seq 0 of inner: [This is where I think that error is taking place] Inside this, There is a while loop which terminates when the "Motion Done?"
function returns "1", else "0". Inside the flat sequence structure, first sequence "updates" the motor coordinate while second check
whether the motion is done .
Seq 1 of inner: Controller wait till motor stops.
seq 2 of inner: The motor coordnate is updated for the last time.
seq 3 of outer: It clears the GPIB.Message Edited by Dushyant on 04-19-2005 10:22 PM
Attachments:
Wait_Till_Motor_Stops.vi ‏13 KB

NI Motion Assistant LabVIEW Code Generation Error

Hello, the following is my current setup:
NI PCI-7334 motion control board
NI UMI 7774 splitter board
3 x NI P70530 Drives
3 x NI CTP12ELF10MAA00 Stepper Motors
3 x Power supply units for drives
LabVIEW 2010
NI Motion Assistant 2.6
Motion and Automation Explorer 4.7
I have built a three axis motion system that I am trying to configure with labview. After verifying that everything was set up correctly, I opened MAX, updated the firmware to my motion control board, and intitialized the controller. Since then, I have created many basic programs using the Motion Assistant Software to test the movement of my device. Everything works fine while using the Motion Assistant software (I have three axis movement, multidirectional control, and can perform various straight line and arc moves). My problems begin when I try to use the code generation feature.
When trying to use the code generation feature to output a labview diagram, I run into a problem where a dialog box pops up and says "Find the vi named ...."
Some examples of the names that come up are: Configure Vector Space.flx, Vector Space To Control.flx, Motion Error Handler.flx.
To be clear the program in Motion Assistant that I am trying to export to LabVIEW code is composed of two individual steps. One that tells X,Y, and Z motors to move forward 25 revolutions, and one step that tells them to move backwards 25 revolutions.
I have made many other programs in Motion Assistant that run fine, but I always receive similar errors when trying to use the code generation feature to export to LabVIEW. Is there something that I can do to solve my problem?
Thank you for your help.

Hi Joe,
I am using Ni-Motion Assistant 2.6, Ni-Motion 8.1, and Motion and Automated Explorer version 4.7.
The code I posted is supposed to tell Axis 1 to move 40 revolutions at 400 rpm. It works fine in Ni-Motion Assistant but when I try to generate a LabVIEW diagram I receive the following error, "Find the VI named 'Motion Error Handler.flx'". I have had it search my directory, as well as the disk that I installed both LabVIEW and Ni-Motion but no luck. Thanks for your help.
Attachments:
1111.vi ‏9 KB
1 axis movement.zip ‏8 KB

How can i convert .gif/.bmp/.jpeg file to labview code(vi)?

Hi,
I am having a .gif file which consists of vi code. I want to convert that .gif file into vi & complile it. I am using LV 6.1 & 7 express. Is is possible?
Reverse is surely possible like we can convert the vi diagram into .gif/.bmp file? But above i dont know?
Your help will really appreciated.
Best Regards,
Nirmal

If I understand your desire, it's to be able to convert a graphical image (bit map or screen photo, for example) into a functional block of LabView code, with all of the wire work done, etc. This is a task approximately equivalent to performing optical character recognition.
In the case of a non-system subvi, unless that subvi is loaded, so that it's graphical representation can be recognized by comparing the bit-map image for the subvi on the photo with the available vi's.
Another difficult problem to solve is when the bit-map has been scaled up or down, such that there's a pixel count mismatch between the VI iconic bitmap and the photographic bitmap you wish to import into your code diagram.
And if you try to do recognition on objects that have h
ad their RGB color representations changed, as can happen when JPG compression or other compression forms are used that reduce to total number of colors saved, that challenges the object recognition further.
Also, what you're interested in having is only of value to Labview programmers, so there's not a very large market for such a tool to be sold to - unlike bitmaps of scanned text to ASCII or wordprocessor applications - traditional OCR software.
All this ins't to say it can't be done, but that it's difficult, and for the person or company that undertakes it, the sales potential is limited.
Regards,
Bob Donnell

How to send data to labview code at run time while using with (or executing the sequence)the teststand

Hello
I am new to the Teststand.
I am using labview8.0 with teststand 3.1
I have developed some labview codemodules as vi's without using the teststand utility library pallete
Now i have to run them in teststand.
While executing them(as a sequence) in teststand,i need to enter the data to the labview code at run time.For this labview front panel should appear as GUI or popup (while executing).Is it possible to do this without using teststand pallete.
or i need to change the code with teststand pallete(i think it is difficult now to change the code)
Plz provide a solution to this problem
Also one more,how and where to use the 'pass by reference' option
Thanks and Regards
Mudigondla

Hi,
see your other post http://forums.ni.com/ni/board/message?board.id=330&message.id=13914
Also, you can, specify to display the front panel of your VI when you specify your VI in your sequence file.
There are examples, for dialog panel using LabVIEW, in the examples folder of TestStand and on the NI Web Site.
Regards
Ray Farmer
Regards
Ray Farmer

Labview code for closing the command window

Hi,
This is naveen.Actually we are using 3rd paty test software for our mobile hardware testing which creates an DOS or Command window after execution.We have automated to execute this software using labview.the problem we facing is that we couldn't run the test software unless we close or kill the dos window opened in the previous run.So i like to know whether you have any labview code for closing or killing the DOS window ,i request you help me in this regard.
regards,
Naveen

Use the System Exec VI Owning Palette: Libraries & Executables VIs and Functions.
And take a look here http://www.tech-recipes.com/rx/446/xp_kill_windows_process_command_line_taskkill/
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Labview has encountered a problem and close by windows

Dear All,
Here I have one question to ask for you. it is that labview was closed automatically by windows and return a information After I run a program(This program was written in labview, it called a .dll to completed a certain process.). Please see the attached for the returned information.
who can tell me why?Thanks a lot!
Best regards,
jimmy
Attachments:
returned information.doc ‏26 KB

smercurio_fc wrote:
It's quite possible the DLL is getting garbage values from the implicit coercion and it's not smart enough to check the values for "good values" before operating with them, and that's what's causing the crash. I've seen instances where this happens, hence my recommendation to change the datatype to U8.
Can you reproduce this? This definitely shouldn't be happening. A LabVIEW coercion should happen purely inside LV and not affect the DLL in any way.
Of course, an alternative test is to call the DLL from a C program in exactly the same way as is done in the LabVIEW code and see what happens.
That is an option, although it will not necessarily help because the problem doesn't occur when calling the DLL, but only when closing the VI. Due to this, another suggestion would be to call the VI as a subVI. It was obviously designed to be called as such and that might cause the problem to stop happening. This is obviously not a real solution, because if there is memory corruption, it's best to find it near the source than at some later time, but it might work.
Try to take over the world!

Need help with Labview code for DAQmx

I'm currently trying to write Labview code for some thesis research and am having problems. I'm using the cDAQ 9172 with strain gage modules and two voltage input modules. I'll be reading/recording a voltage from an external source on one channel, while recording strains and accelerations with the other channels. I need to do all this simultaneously.
Everything I've done to this point has been in SignalExpress so I'm not sure how to program any of this. I also need to be able to calibrate the strain gages prior to each set of recordings. Any help you guys could offer would be greatly appreciated. Thanks.

Hi,
I'm not sure how much this will help you, but I've attached a screen dump of code from a project I did that sounds pretty similar to what you're working on. The code is from a subVI that I used to create the daqMX measurement task for my data acquisition. I was also using a 9172. This was written in 8.5, but the only thing that you may not have access to is the functions for null offset and shunt cal of the strain gage channels. Hopefully this will at least get you started on your way to setting this up.
Andrew Carollo
Attachments:
create task.jpg ‏208 KB

Labview slider event handling problems - revisited

This topic asked a question that was very close to a problem I am having:
Labview slider event handling problems
That is, how do I, using an event structure and/or other means, only read out the value of a slider control after the value change is finalized?
The extra constraint I'd like to place on this, which I believe will invalidate the answer given in the thread above, is that my slider control also has a digital display which can also be used to change the value without ever using the mouse. I cannot look for a value change followed by a mouse-up event if the mouse was not used to change the value.
Any ideas how this might be accomplished? FWIW, I am using LabVIEW 7.0

Each and every incremental value-change event generated by the movement of the slider is still detected and queued up for use by the event structure and the event structure loop wades through them all before it's done.
I have come up the attached "fix" (LV v7.0) for this problem. While it is not as clean a solution as I had hoped it would be, it's the best I can manage given what LabVIEW offers me to work with and it does work in the situation where I need to use it.
Now, within the Finalize Slider Events subVI, I'm keeping track of the most-recent values seen by the subVI, checking to see if they have changed, and reporting out that fact. That gives me a Changed/Not-Changed bit within the event case that I can use to control what code then gets executed. If the event case is just playing catch-up to the real value of the control, I can now see that fact and ignore it.
In this version I've also dumped the variant output and limited the VI to using DBL values. I decided it added complication to something that was too complicated already and I wanted the output terminals for other purposes anyway (reporting of the correct "OldVal" of the control).Message Edited by Warren Massey on 04-28-2005 03:56 AM
Attachments:
slider_events[5].llb ‏77 KB

LabView code module to perform simple pass/fail *IDN? query?

LabView 7.1, TestStand 3.1, NI PCIGPIB board controlling a communications service monitor and a power supply. I'm having problems with my application sync correctly between the service monitor and GPIB board. I suspect the driver. Does anyone have a simple LabView code module to perform a *IDN? with a partial (in case they change firmware versions)string comparison that I can use in a TestStand seq. At this point if failure I could pop-up and tell operator to abort test and reboot instrument. (only way I've found to clear the buffer). Note: At times this app works fine and is inconsistant in failure times/rates.
Sorry so wordy and thanks in advance.
Using LabVIEW 2010SP1 and TestStand 4.5

Thanks for the reply Craig.
I've found I can perform a *IDN? using the Instrument I/O Assistant.vi. Ive placed this on a new block diagram and am changing it as I need. I've found in this particular case the *IDN? yields 3 tokens one of which I can use to perform a string comparison on. This will give me a boolean which I can wire to the pane for use by TestStand.
Using LabVIEW 2010SP1 and TestStand 4.5

Collection Rate issue - hanging in LabView Code

Hi guys,
I'm current programming a DAS in LabVIEW and am having problems with how often the graphs in front panel are updating. For some reason, no matter what I set the input "Collection Rate" to, it always updates every 10 seconds (regardless of what value is in the DAQmx Write timeout input). I noticed that if I removed the DAQmx Wait Until Done, then the graphs will update properly based on the collection rate. Also, I got an error out of the DAQmx Wait Until Done (200560).
However, in a watered down version of the original code, I can leave the Wait Until Done in the code and the graphs will update properly. Of note, the Wait Until Done still outputs the exact same error as the non watered down version.
So where exactly in the code is my program hanging in? I can't really find any glaring differences between the two sets of code that would make me think there's a huge problem. I don't want to have to take out the Wait Until Done VI, but if you guys think there really isn't a problem taking that out of the code then perhaps I will do that for now.
Thanks.
Attachments:
Original.vi ‏69 KB
Watered Down.vi ‏45 KB

Hi jchsu,
Could you please be a bit more descriptive when you say that the graphs on the front panel have trouble updating? Which graphs in particular are you referring to?
Thank you for choosing National Instruments.
Aaron Pena
National Instruments
Applications Engineer
http://www.ni.com/support

Trying to use my computer LabView code to control 4 LED's

Hello,
I'm a student working on a project at CU Boulder and I need a little bit of help. I'm kind of new to LabView but, I created a code that will create a random number, which turns on one of four LED's, and then, that LED will turn off after a slide bar (accelerometer) senses a value greater than 5 (this value will change after some accelerometer data). After this process, the random number generator will generate a new number for a new light. I'm just wondering how to tell the computer which LED icon indicates which real-life LED. Is there a way to hook up my LED's without changing my LabView code? Do I need to create a digital output DAQ assistant? Please see the attached labview code and hopefully you can help me out. We've had major problems trying to get our accelerometer to read a constant logical value and have just run into our LED problem.
Thanks, Zack
Solved!
Go to Solution.
Attachments:
Making Lights Work.vi ‏22 KB

Hi Zack,
your VI is kind of Rube-Goldberg award nominee...
"how to tell the computer which LED icon indicates which real-life LED."
Well, you have to decide where to "hook" those "real-life" LEDs. When you have made your decision you'll need some hardware driver to switch the LEDs. A DAQ assistent may be a good choice when you use NI hardware. Otherwise use the driver coming with your hardware...
"Is there a way to hook up my LED's without changing my LabView code?"
No. "Real-life" LEDs need real hardware drivers...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome
Attachments:
Making Lights Work.vi ‏12 KB

How to create a virtual FPGA and run LabVIEW code on it?

Hi
I am new to LabVIEW FPGA world. I have code written in LV 8.6 that was running on a Virtex 5. I need to run this code on a virtual FPGA but I need this to be as real as possible and maybe to acces this virtual FPGA also from another environment. Do you think this can be done? I need just a general answer to have an idea on this problem.
Thanks

If I've understood correctly, you have LabVIEW code written for an FPGA and running on an NI FPGA board, which you'd now like to run in a simulated system. I doubt this is possible since I don't think there is a way for you to simulate all the hardware (DAQ and whatever else) that is attached to the FPGA on the real hardware. Also, LabVIEW doesn't have any way of accessing an arbitrary non-NI FPGA target and without the LabVIEW interface I don't think your FPGA code will be too useful.

Expert LabVIEW code evaluation?

Does anyone know of a place (or person) that will do LabVIEW code evaluation? - To look at the actual block diagrams and give advice? I realize that's what we do here to a large extent, but I'm referring to an email exchange of info regarding a fairly large, completed and running program.
Richard

I don't think the training sessions had anything to do with the Alliance Member's failure. The Alliance Member failed because they lacked the expertise in vision systems to complete your application. Perhaps that fact was compounded by poor time management as well. I find that a good approach is to bring in the Alliance Member / consultant for a limited period, say 2 or 3 days. You let them attack part of your application or problem and from that you can gage their level of competency. If they are no good, then you've only spent a few k$ and probably learned a few tricks. There are lots of us out there. You are sure to find one that can meet your needs.
I'm obviously biased, but I have had the unfortunate experience of looki
ng at code / work-product left behind at customers of other Alliance Members. Most of the time I don't like what I see. Unfortunately, NI inside sales and the NI field sales force are not in general equipped to judge software expertise. The relatively new Certification program helps immensely, so look for the CLD (Certified LabVIEW Developer) credential. The higher-level CLA (Architect) may become a good benchmark too, but you're likely to pay a bit of a premium (rightfully so).
Alliance Members can be very helpful and we produce brilliant solutions on a daily basis. Like I always say, we do this stuff every day. There's just no substitute for that. Give us a chance (or two) to prove how useful we can be and to show you the full potential of LabVIEW.
Daniel L. Press
PrimeTest Corp.
www.primetest.com

Labview Code or stepper Problem

Similar Messages

Maybe you are looking for