Tags |
(This content has not been tagged yet)
|
![]() |
Oct 8 2004, 07:26 AM
Post
#1
|
||||||
|
Changing the world, one VI at a time. JKI ![]() Posts: 1697 Joined: 22-October 02 From: San Francisco, CA Member No.: 17 Using LabVIEW Since:1995 LV:8.2.1 ,8.5 ,7.1.1
My Blog
My Gallery
|
:!: Today, I discovered a serious flaw in the following FlexMotion VIs:
Wait for Blend Complete Wait for Move Complete Wait Reference The problem is that when an Error is passed into them they do not pass the "Board ID" or "Axis" values through, as one would expect. Here are some screenshots of the offenders: This can cause huge problems downstream. For example, here is some code that I wrote as part of a move command. If the move fails, I want to kill/abort the motion. But, since I no longer have valid "Board ID" or "Axis" values, the abort call fails (this is VERY bad ![]() ![]() Lucky for me, I didn't crash a motion axis before I discovered the bug. --------------------
|
|||||
|
|
||||||
| Ad |
Oct 8 2004, 07:26 AM
Post
#
|
||
|
|
|
||
|
|
|||
Jun 12 2006, 08:20 PM
Post
#2
|
|||
|
I want a LabVIEW icon under my name! Member Posts: 3 Joined: 28-September 04 From: Toronto Member No.: 728 Using LabVIEW Since:2004 LV:7.1 ,. ,.
|
Jim,
I know that this is really old post but it might help me to resolve very unpleasent issue with my application. Shortly to explain: from time to time, motor would start turning very fast, and then I would get the timeout message. Move would not be killed and I would have to the that manually from diagnostics program before I start the application again. I will try to implement your solution. Thanks for idea. Say hi to Michael. Natasa
|
||
|
|
|||
![]() ![]() |
| Time is now: 2nd December 2008 - 03:11 AM |