Magnetic lasso - closed loop only?

Hi
Is it possible for the magnetic lasso to function as an open line rather than a closed loop?
Many thanks
Andy

I suppose an open lasso is a strange concept. :)
I was after something which used the magnetic properties of the lasso ie. it clings to edges, but which was open, ie. the ends are tethered and it forms a path between the two ends. The key thing is the automatic clinging to edges close to where the mouse is traced. Can Illustrator do this?

Similar Messages

7344 servo motion switching between open and closed loop operation

I have a custom end-of-line test system presently using a 4-axis 7344 servo controller to perform various functional tests on small, brushed DC motors. The system is programmed in C/C++ and uses flex motion functions to control the motor during testing. Motors are coupled to external encoder feedback and third party PWM drives running in closed-loop torque mode from an analog command signal. The system uses all four motion axis channels on the 7344 board to independently and asynchronously test up to four production motors at a time.
In closed-loop mode, the system runs without issue, satisfying the battery of testing protocols executed by this system. I now have a request to add additional test functionality to the system. This testing must be run in open loop mode. Specifically, I need to use my +/- 10v analog output command to my torque drive to send different DAC output levels to the connected motor.drive while monitoring response.
I do not believe the flex motion library or 7344 controller includes functions to easily switch between open and closed loop mode without sending a new drive configuration. I am also under the impression that I cannot reconfigure one (or more) servo controller axis channels without disabling the entire drive. As my system runs each axis channel in an asynchronous manner, any requirement to shutdown all drives each time I change modes is an unworkable solution.
I am open to all ideas that will allow asynchronous operation of my 4 motor testing stations. If the only solution is to add a second 7344 controller and mechanical relays to switch the drive and motor wiring between two separately configured servo channels, so be it. I just want to explore any available avenue before I place a price tag on this new system requirement.
Bob

Jochen,
Thank you for the quick response. The 7344 board does an excellent job running my manufacturing motor assemblies through a custom end-of-line tester in closed loop mode. A portion of the performance history and test result couples the motor through a mechanical load and external shaft. The shaft is in contact with a linear encoder that closes my servo loop.
My new manufacturing requirement is to also sample/document how the small DC motor behaves in open loop operation. Your solution is exactly what I need to perform the additional functional tests on the product I am manufacturing. I see no reason why this cannot work. I was originally concerned that I would need to reinitialize the 7344 board after changing axis configuration. Initialization is a global event and impacts all four channels on the 7344 board.
Using flex_config_axis() to change axis configuration on a single channel without disturbing other potentially running axis channels will solve my concern. It will be several weeks before I can return to the manufacturing facility where the 7344-based testing machine is located. I will update this thread once I verify a successful result.
Bob

Difference between open loop and closed loop mode when finding the index on a stepper motor axis.

I have a test system which uses a PXI-7352 motion controller with a MID-7602 stepper motor drive to position a 200 step/revolution stepper motor with an attached 1000 line encoder. The MID-7602 is configured for 64 microsteps per step, giving 12,800 microsteps and 4000 encoder counts per revolution. The system is controlled using LabView 7.1 and NI-Motion 6.13. To home the motor, I've defined a sequence in MAX which first finds the reverse limit switch and then moves forward to the encoder index pulse.
When finding its reference in open loop mode, the system its reference at the same microstep each time. When findings its reference in closed loop mode, the system finds its reference somewhere within about a 20 microstep wide range.
I hope somebody out there with more experience with this controller can describe the difference between finding the encoder index in open loop mode and finding the encoder index in closed loop mode.
Thanks,
Mark Moss

Hello Mark,
I suspect that the behavior you are experiencing has today
with the resolution difference between your encoder and your
microstepping. Let me illustrate with an
example:
Example Setup
Stepper
Motor
NI
Motion Controller
10
steps per encoder pulse (Every 10 steps the controller gets an encoder
pulse, therefore positions 0-9 all appear to be 0 to the controller)
The
system has a maximum of 3 pull in moves set
Open Loop Scenario
The
system is commanded to go to position 9.
The
controller sends out 9 pulses.
The
motor moves to position 9.
Closed Loop Scenario
The
system is commanded to go to position 9.
The
controller sends out 9 pulses.
The
motor moves to position 9.
The
controller checks its position and sees that it is still at position 0
because it has not received an encoder pulse.
Because
the controller thinks it is still at position 0, it sends another 9 pulses
as its first pull in move.
The
motor moves to position 18.
The
controller checks its position and sees that it is at position 10 because
it has only received one encoder pulse.
Because
the controller thinks it is still at position 10, it sends1 reverse pulse
as its second pull in move.
The
motor moves to position 17.
The
controller checks its position and sees that it is at position 10 because
it has only received one encoder pulse.
Because
the controller thinks it is still at position 10, it sends and additional
single reverse pulse as its third pull in move.
The
motor moves to its final position of 16.
I believe something similar is happening with your
application as it looks for the index pulse.
Because the controller does not compensate for what it perceives as
position error in open loop mode, the motor always goes to the same commanded
position. In closed loop mode, the motor
is bouncing around inside the single index encoder pulse trying to find a
certain position.
There are several recommendations I can make towards
correcting this behavior. These
recommendations are in order of effectiveness:
Setup
your system so that there are more encoder counts per revolution than
steps per revolution.
Turn
off pull-in moves by setting them to 0 in MAX.
Use an
open loop configuration.
Play
around with the pull in window in MAX.
Regards,
Luke H

Why are my steppers misbehaving in closed loop mode, but work fine in open loop

I have a 7344 controlling a 4 axis prototype machine, which is configured with 50,000 steps/rev and linear encoders providing 50800 counts per inch. The physical properties of the machine are less than perfect (prototype!), so there is a considerable amount of backlash in the hardware (about 0.008" - 0.010").
The observed behaviour is as follows: when repeatedly blending in the X,Y plane using vector space 1 in closed loop mode, an axis will be driven (uncommanded) to the zero encoder reading (home position) occasionally (about 1 move in 600). I have kept a log of the commanded positions being passed to the controller (via the flex_load_vs_position function) and a move to zero is not being com
manded. The application is single-threaded, so there is no chance of race conditions. The ready state of the board is being confirmed by means of the flex_check_blend_complete function call before any blend is commanded. The programmed relationship between steps and counts/revolution have been independantly confirmed as being correct.
An A-B-A test with the only change being to initialise the X & Y steppers in open loop instead of closed loop then 'works' - although the physical positioning of the hardware is unsatisfactory due to the physical characteristics of the prototype machine already mentioned, hence the necessity to run closed loop.
I am inclined to interpret the evidence as suggesting that the 7344 is causing an 'occasional' uncommanded move to zero as a result of some interaction between pull-in moves and commanded position on a system where there is a considerable degree of 'elasticity' between the commanded position and the achieved position allied to a rapid-fire de
livery of blend moves.
This problem can be replicated under versions 5.0.1 and 5.2 of the FlexMotion software.
I can clearly run without bumping into the problem by running open loop, but unfortunately that is not acceptable in this situation. Any ideas, anyone?

Hi, and thanks for coming back so promptly. I think I need to give you some more information - sorry if it turns into a long post!
The system behaviour when it 'misbehaves' is that it starts the anomolous behaviour well clear of any home or limit switch (>6"). When it 'goes wrong', it then slews one or both axes to the zero position. Having arrived at the zero position, it then carries on with the next blend without killing the motor.
The initialisation functions include a seek to home switch, a search for the nearest index point, and a zeroing of the encoder count at the index pulse: hence the zero point is a little displaced from the home microswitch.
I believe that once the system has 'gone wrong', it is stopping at the zero point *not* the h
ome switch.
I have carried out some further tests that may be of help:
If I place a large (1 sec) inter-blend delay in the calling functions, the anomalous behaviour is not noticed. However, the start/stop nature of each move means that this test is knocking the bejezus out of a rather fragile prototype machine, so I can't do this too often!
The encoder positions are being read back on each move cycle and monitored, and they are not showing any anomolous behaviour, so I don't think they are the culprit. I have placed a 'scope on the quadrature encoder inputs and the edges are good and sharp with no real indications of noise.
I could test with a blend factor other than -1 if you think that might be illuminating?"

Closed loop configuration question

I have a motor(with encoder feedback) attached to a linear actuator(with end limit switches).
The motor has a commercially bought servo drive for control.
The servo drive will accept either a step/direction (2 seperate TTL
digital pulse train inputs) or an analog -10 to 10vdc input for
control.
The purpose is to drive a linear actuator(continiously in and out) in
closed loop operation utilizing a ( (SV) Setpoint variable)value from a
file converted to a frequency to compare with an actual ( (PV) Position
variable) measured frequency.
I have created and experimented with individual vi's allows analog
control and digital pulse train control (thankfully with the help of
examples).
Before I pose my question, I would like to make the following
observations: It is my understanding that Closed loop control
means that I dont need to know an exact position at which to drive, but
constant comparision of PV and SV through PID applictation.
Without getting into any proprietery information I can say that the
constant positioning of the linear actuator will produce a latency of 2
to 3 seconds based on the time the actuator moves to a new position and
when the PV will change. While experimenting with the analog
input, i noticed imediate response to motor velocity, but after the
motor is stopped, position is not held in place. However, while
experimenting with the Digital pulse train input, I noticed that the
servo drive can only accept one command at one time; if, halfway
through a move, position error produces a response to move the linear
actuator in the opposite or different direction, the origional move
must finish first.
Can anyone recommend the proper configuration for the closed loop control i have described?
If I can make the system work with the servo drive/motor I plan to use
the simple (pci 6014) daq card with the Analog out, or utilize the
digital out.
If I cant get this to work, we do have a pxi with 7344 motion card(I
would like to exhaust all efforts to use the PCI 6014 card).
Depending on where I go from here, I planned to use the PID vi's for the loop control.
Thanks,
Wayne Hilburn

Thanks for the reply
Jochen. I realize there is a built-in latency with windows but I
think the I/O control would be ok. A change in actuator position
will not result in an immediate change in process variable; Is
there a way to measure the latency or is it calculated? A
satisfactory reaction time could be from 1 to 1.5 sec.
Use of the PCI-6014 is to supply the control output to the servo
drive/amp, and not to drive the motor itself. As stated earlier,
while using the 6014 board, I have the choice of digital or analog
output.
Currently I am at a point where I must choose which configuration,
analog control or digital control(in the form of digital pulse train),
(i am inserting from first message)
While experimenting with the analog
input, i noticed imediate response to motor velocity, but after the
motor is stopped, position is not held in place. However, while
experimenting with the Digital pulse train input, I noticed that the
servo drive can only accept one command at one time; if, halfway
through a move, position error produces a response to move the linear
actuator in the opposite or different direction, the origional move
must finish first. .
I dont claim to understand all the limitations with the
specific boards, however, i am using an approach that is showing me the
characteristics(a couple are listed in the above paragraph) of
the hardware and software configurations.
So I am really back to my origional question; Which configuration
would be better for closed loop control, analog or digital pulse train?
Thanks,
Wayne Hilburn

Closed loop control of step motors possible with 7344?

Hi All
I have been looking around here for a while for an answer to this question.
For me, a closed loop control system is correcting for following errors all the time, also when the move is complete.
If the load on a system changes, there will often be a need for compensation in order to keep the position right. Then you need a closed loop control system.
I have made a system using DC motors with a 7342 controller. We are in the process og getting a new similar system, where the manufacturer chosed stepmotors in the believe that it can be used in closed loop.
Is it really true that the NI version of closed loop is only performing a what you call a "pull-in" at the end of the move in order to correct for lost steps or flexibility of the connection between motor and object/encoder?
I would call this "backlash compensation" or something like that.
Why dont you make a real closed loop option. The control voltage from your servo motor control, could be fed into a voltage-frequency converter with a matchin sign signal.
This shouldn't be too complicated to accomplish.
/b

You are right. NI motion control boards don't apply a control algorithm
during moves when configured in closed loop stepper mode. In this mode
the board monitors the following error during the move and generates an
error when the following error limit is exceeded and they start the
pull-in moves at the end of the move if necessary.
If you really want to do PID control with stepper motors you still
could connect an external V/f converter to the DAC outputs of the board
and control the axes like DC motor axes. Some vendors implement this
feature on their board but NI has decided not to do that as we don't
think that this approach provides a good solution. Here are some reasons:
The most important issue is the fact that you could easily exceed
the maximum rate of change of the motor frequency in the case that the
following error increases during the move. For a DC motor this would mean that the
voltage of the controller increases to compensate for this error and
the motor will follow - probably with some delay, but it will follow. For
the stepper this could mean that the acceleration becomes so high
that the motor stops immediately as it can't follow with a delay like a DC motor. What
should the controller do then? Restart the move automatically? Generate
an error? There is a big chance that you end up with a system moving in a stop and go mode.
The second issue is related to the control algorithm itself. The transfer function of a stepper motor is not really linear so it will be quite hard to find good tuning parameters. A DC motor can be tuned by analyzing the step response and the Bode plot. For the reasons that I have described in 1.) this won't work for a stepper so how should you tune it?
I have talked to some motion control engineers who have tried to control steppers with a PID algorithm and they all agree that this is a real pain and it's not recommended.
So if your system requirements involve online following error compensation I strongly recommend using a DC motor.
Best regards,
Jochen Klier
National Instruments Germany

Closed loop control of DC motor drive using PCI 6251

Hi
i am using NI PCI 6251 for closed loop control of dc drive.(shunt motor,220v, 0.5HP, 2.5A rated, 1500RPM)
the dc motor is fed from a bidirectional dc-dc converter. this converter works in boost mode(forword motoring) and buck mode(braking mode/battery charging)
the converter is built using mitsubishi IGBT module. at low voltage side of the converter a battery bank of 48V is connected and high voltage side the motor is connected.
An IR sensor is developed to measure the speed of the motor and a hall current sensor is used to sense the converter current.
in the control part i have an inner current control loop(PWM controller) and a outer speed control loop.both controllers are PI controller. To measure the speed i have used counter of the DAQ assistant, then frequency. then this frequency is converted to RPM using labview.after giving the speed and current signals to the controllers , then i started tunning the PI gain, but at the starting the duty cycles was 100%, so the IGBT got damaged immediately. now how to tune the controllers during the closed loop operation. the switching frequency of the converter is 20KHz.
can any body suggest me how to run the dc drive in closed loop ?
thanking you.

Hi Premenanda
The freq data receiverd from the daq assistant has the units of Hz, or in terms of motor speed, rps (rotations per second). I can see that you are trying to convert that to rpm (rotation per minute). which can be done by dividing the rps speed by 60. Instead, you are multiplying it by 60 and also comparing with 2000. the resultant multiplied value is displayed in your program only if it is smaller than 2000.which is causing the problem here.( as seen in file 'original code.png)
I have attached a file named 'modified code.png' that shows how the conversion from rps to rpm is done. Please do the required changes in your code and let me know if it works.
Attachments:
modified code.png ‏18 KB
Original code.png ‏15 KB

Creating a simple closed loop control

Hi everyone,
I need a bit of help creating a (very) simple closed loop control.
Note: I am using 3 Measurement Computing boards: one USB-2416, and two USB-TC's. Since Measurement Computing has their own driver (called ULx), it might be a bit more difficult to understand than the NI drivers, but keep in mind ULx is the equivalent to DAQmx.
I need to be able output a 0 or 1 binary value based on measurements from 4 voltage input channels compared to constants. Ie. if voltage measurement < 3.5 (constant), send a boolean value (see a, b, c, d in attached photo) which in turn gets sent to the ULx Write VI, and that outputs the binary value of 0 or 1. The problem I've run into is that I need to "compare" single chanels from different boards, which gives me single boolean values for each channel. The ULx Write VI only accepts boolean arrays. Is there a way (and there probably is, I just haven't been able to find it) of arranging these lone boolean values into a boolean array?
(see attached file for what I have so far)
PS. I am a COMPLETE rookie, only been using LV for a week or so, so please explain everything as if I have no clue what's going on.
Thanks in advance!
Solved!
Go to Solution.

Hi,
the attached example I've made should demonstrate what you need to do.
Some things to think about:
1. It seems that the ULx vis return arrays of signals. If so you can select signals with "index array" as done in my example. That consumes less space and does not change the type of the signals to variant.
2. If you compare the signals to your constants you will receive boolean arrays because every element of the measured signal is compared to the constant (see my example). You may then decide how to process that info - another hooray for signals :-)
Regards
Florian
Attachments:
Example01.vi ‏24 KB

Magnetic Lasso is FREAKING OUT

Ok, I have a problem that I've never seen before. When using the magnetic lasso tool, photoshop starts freaking out and flashing a 'transparent effect' rectangular area all over the screen. the only way to get it to stop is 'command D'
I have two students that this is happening to. In my 5 years of teaching photoshop I have never encountered this issue before. Using CS4 btw.
TIA!

Vicky, did you read post 3?
Chances are you have a display driver problem.
Are you on a PC? If so, you can visit the web site of the maker of your video card and seek out their latest display driver release for the video card and operating system you have. Once you download and install the latest, reboot your system (sometimes the install doesn't require it but do so anyway) then re-test Photoshop.
Good luck!
-Noel

Strange Behavior Using Magnetic Lasso

I'm using Photoshop CS4, and experiencing odd behavior when using the Magnetic Lasso. I'm working on a project that has fairly intricate outlining and filling actions, so I'm using the magnetic lasso to do that. This involves a lot of irregular borders, so I have to do a fair amount of setting anchor points manually. It all works fine, except that I periodically get the lasso "closing" spontaneously. That is, I'll be half way around an area I'm outlining, and with no action on my part, the lasso suddenly leaps to the origin point (the pointer doesn't move, but the seleted area is completed, as if I had double clicked. This seems to happen more frequently if I am moving the mouse back and forth to get a more precise location for setting an anchor point. Does anyone have any idea what might be causing this behavior? Sometimes, depending on where I am in the process, I can simply continue by choosing to "add to the selection." But sometimes, this aribitrary closing encompases portions that I do NOT want included in the selection, so I have no choice but to Step Backwards, or Undo, and start over. If it helps, when this happens, I'm usually working on a magnified portion of the image, and have the Caps Lock pressed to give me the pointer configured as a cross within a circle, to provide more precision. Will be glad to provide any additional information that anyone considers helpful or pertinent. Any help much appreciated.

Acidclink--
Thanks for the reply. And let me say at the outset that I am NOT an experienced Photoshop user. I've used it a lot, but not much for many different projects. Until I got your suggestion, I hadn't heard the term "penning a path." But I did some reading, and I'm assuming that you are talking about using the pen tool in its path mode, to draw an irregular outline that you can then convert into a selection. Truth is, until your note, I had no idea that the pen tool could even be used in this manner. And I will certainly give it a try. But, as I understand it, the pen tool when used in this fashion creates a series of straight lines between points. That would mean, (if I am correct) that to make a curved line, you would need a lot of points close together. And in that situation, it seems to me that the Magnetic Lasso (or the Quick Selection) tool might work better.
Perhaps if I describe in a bit more detail what I am doing, it might help you and others who are generously trying to assist. I'm working with a series of state outline maps with counties outlined. Although the images are color images, they are essentially black and white. That is, I have a map of a state on a white background, with the counties of the state outlined in black. My task is to fill a single county on the map with color. So what I've been doing is using the Magntic Lasso (or the Quick Selection) tool to outline the county boundary, then use the FILL command to fill the selection with the color. As you can imagine, the county boundaries are often very irregular, with zig-zags, curves, rivers, etc. The benefit of the magnetic lasso or quick selection tool is that they do a FAIR job of following all of the irregular coutours. They ceratinly aren't perfect, and I nearly always have to add to or subtract from the selection to get a good quality selection that matches the preprinted boundaries. But, what I don't have to do is trace the entire distance of the existing boudary with precision. I just need to nudge the selection a bit in sharp pointed corners, or things like river meanders, where there are a series of "s" turns.
Having said all of that, I'm still willing to learn, and I do plan to try the pen tool to create a path as you suggest. An earlier suggestion to use the Quick Selection tool has helped me--I've been using it to grossly select an area, then using the magnetic lasso to refine the seletion. So I am learning (though slowly). And I DEFINITELY appreciate the input and suggestions.
On a different subject, I MAY have fixed the unexpected closing problem with the magnetic lasso. Since I unplugged the mouse (to try a different one which turned out to be dead), and plugged it back in again, I have not yet experienced the spontaneous closing problem. So it may be that the problem was caused by a poor connection of the mouse to the USB port. Time will tell on that.

Problem using PID toolkit and control design toolkit to design the closed loop system. (for DC motor closed loop)

Hi, i have facing some problem during i upgrade a project. This project is an opened loop system, it only achieved up to controlling the speed of motor, detecting the speed of motor, and switching the direction of motor while controlling the motor (This motor is a 12 VDC motor).
In order to improve the project, closed-loop dc motor control system will be implemented to correct the error of the motor's speed and maintaining the speed for the initial setting. I would like to use PID control method to do the closed loop system.
I already installed the PID toolkit V8.2 and control design toolkit V2.1.2, and i'm using DAQ usb 6221, LabVIEW 8.5
Below is my problem.
http://img177.imageshack.us/my.php?image=howtocreatethesetpointnx2.jpg
question: 1. How to generate a icon for set point? my setpoint is duty cycle...
2. How to feedback the output duty cycle to summing junction?
below this is my basic concept
http://img237.imageshack.us/my.php?image=closedloopbz5.jpg
Problem 2:
http://img357.imageshack.us/my.php?image=problem1yk2.jpg
question: Why PID toolkit icon cannot wire to cd series.vi?
Below is my original program...
http://rapidshare.com/files/140538836/pwm_generate-final_PSMII.vi.html

Hi Cyrus
Have you had the opportunity to see our
developer zone site on the PID toolkit? This article also has sample
code at the bottom that may help you in developing your application. I
have also linked below knowledge bases regarding setting a point
profile and generating a PWM from a digital output line.
PID toolkit
http://zone.ni.com/devzone/cda/tut/p/id/6440
How to generate a set point profile:
http://digital.ni.com/public.nsf/allkb/125F27AC143B6AFD86256C2B0004A4DC?OpenDocument
How to generate a PWM on a digital output line:
http://digital.ni.com/public.nsf/allkb/1561D31534F07D608625727900391114?OpenDocument
Thank You
Eric Reid
Thank You
Eric Reid
National Instruments
Motion R&D

NI 9505 Closed Loop Position Control Example

Hello, I have a cRIO 9073 with a NI 9505 module that I'd like to use for simple position control of a unit along a lead screw.
I don't have the softmotion module, and am trying to write a program bassed off of the "Position Control (closed loop) - NI 9505" example to control the position the small motor attached to the lead screw (Faulhaber 2342S024CR with a 512 count/rev encoder that we had laying around)
I've reviewed the manual PID tuning example, and have not had much luck getting the response that I'd like when making large position moves simply by adjusting Kp,Ki,Kd gains of the position loop, as the overshoot remains too high for this application when making large moves. The system is also oscillating about the set point, and doesn't ever seem to dampen out unless I change things other parameters on the fly such as the current limit, or current loop parameters (osciallations get worse as current limit is increased).
Can someone advise me if the components of this example are up to this task? Or on the interactions between the current limit, current loop parameters, and position loop parameters from this example, and which parameters would have the most impact on achieving desirable system performance?
Is there a VI available that can autotune such a motor?

Hello - there are many reasons why a closed loop controller can oscillate - from correct settings of controller (kp,ki,kd) to making sure signals act in the appropriate direction to deadband/friction in the actuator to badly sized signals/actuators.
Firstly, have a look at the signal your controller is outputing (ideally in LabVIEW so you can graph it). Does it oscillate - perhaps as a sawtooth, a sinewave or simply switching between maximum and minmum values. I presume the electrical motor driving the screw which is driven from some AO signal from the cRIO (could also be a PWM signal driving the motor).
I expect (from what you say about current limit) the control signal will be oscillating by switching between maximum and minimum (e.g. +10V to -10V) or oscillating like a sinewave. What values of kp, ki, kd are you using ? If kd is non-zero, set it to zero (you only need worry about this if you want to get maximum performance). Is ki non-zero ? Try setting it to zero - any better ? If you are still getting big oscillations in your control signal, keep reducing kp (e.g. half each time?) until oscillations disappear (as you reduce kp, control signal *should* get smaller - maybe not straight way though).
If this does not make oscillations go away, then it may be that you have a sign wrong in your loop - i.e. a positive control signal makes lead screw move in opposite direction controller expects. This should be a fundamental thing sorted out when setting up the loop - you could do an open test to check which way +ve voltage moves lead screw. If you find it moves in opposite direction - you can either re-wire, or put a "-1" gain on controller output.
If there is any more subtle oscillations / obersvations, then try to show some plots of the lead screw motion and control signal, as that always helps when trying to diagnose what is going wrong.
Good luck.
Consultant Control Engineer
www-isc-ltd.com

Foreach Loop only looping once

Hi,
Please be patient and bear with me, for I am new to SSIS packages.
I am using SQL Server 2008 R2 to host the SQL Agent job and the SSIS package.
I am using Visual Studio 2008 Professional Edition for designing the SSIS package. It is version 9.0.30729, Version 3.5 SP1.
I am on a Windows 8 machine.
My Foreach Loop Container seems to iterate only once when it should iterate numerous times, and this issue happens BOTH when I execute the SSIS package from within Visual Studio AND when I run a SQL Agent job to execute the SSIS package.
For the solution within Visual Studio, I have False for the property Run64BitRuntime.
In the SSIS pckg in Visual Studio, I have in the Variables pane a number of variables and these following variables pertain to my problem:
Name: objRs     Scope: the name of the SSIS package     DataType: Object    Value: System.Object
Name: txtVendorFamilyNumber   Scope: the name of the SSIS package DataType: String   Value: 111111
The value "111111" that I entered into the txtVendorFamilyNumber variable in the Variable Pane is NOT a realistic value as there are no vendor family numbers that have the value 111111. I will populate dynamically the real vendor family numbers
from within the SSIS package.
When I imported the SSIS package to SQL Server 2008 R2, via the ellipsis button for the Protection Level I chose the "Rely on server storage and roles for access control" choice.
Concerning the flow of the SSIS package, going down within Visual Studio from the beginning of the flow of the SSIS package, eventually I have an Execute SQL Task. In its General tab, it has "1252" for CodePage property, "Full result set"
for ResultSet property, "OLE DB" for ConnectionType property, "Direct input" for SQL Source Type property, "False" for BypassPrepare property, and the following for the SQLStatement property:
     select txtVendorFamilyNumber from tmpVendorFamily where VendorID = (select min(VendorID) from tmpVendorFamily)
In the tmpVendorFamily table on SQL Server 2008 R2, there are 379 rows of results for the SELECT statement above (starting with the values 100110, 100115, 100120, 100130, through the LAST row's value 106370.
In the Parameter Mapping tab of the Execute SQL Task Editor, I have nothing. In the Expressions tab of the Execute SQL Task Editor, I have nothing.
In the Result Set tab of the Execute SQL Task Editor, I have the value 0 for Result Name property and I have the value User::objRs as the value in the Variable Name property.
This Execute SQL Task has a green arrow (Constraint evaluation operation, Success in Value drop down) to the Foreach Loop Container.
In the Foreach Loop Editor, in the Collection tab, I have "Foreach ADO Enumerator" as the value in the Enumerator property. In the drop down for ADO Object Source Variable, I have chosen the User::objRs, and I have the radio button "Rows in
the first table" selected.
In the Foreach Loop Editor, in the Expressions tab, I have nothing.
In the Foreach Loop Editor, in the Variable Mappings tab, I have "User::txtVendorFamilyNumber" for the Variable property and I have the value "0" for the Index property.
So in the Foreach Loop, I first have a Script Task with the ReadOnly variable User::txtVendorFamilyNumber and with the ReadWrite variable User::TESTING_OnlyTesting that I created with a package scope, string datatype, and no default value. This Script Task
has the following code for testing purposes:
Dim strFullVerbiage As String
strFullVerbiage = "The value is: "
Dts.Variables("User::TESTING_OnlyTesting").Value = strFullVerbiage + Dts.Variables("User::txtVendorFamilyNumber").Value.ToString()
Dts.TaskResult = ScriptResults.Success
I have next in the Foreach Loop Container a Send Mail task. In the Expressions tab of the Send Mail Task Editor, I have for the Message Source property the following:
      @[User::TESTING_OnlyTesting]
The remaining tasks (including FTP Tasks) in the Foreach Loop Container are disabled for now as I am trying to figure out why the Foreach Loop only iterates the FIRST time, only iterates once.
When I run on SQL Server 2008 R2 the SELECT statement from the Execute SQL Task, I get 379 rows of results. The default value 111111 that I entered into the Variable Pane for the txtVendorFamilyNumber variable does NOT exist in any of these 379 rows of results.
The 1st row of results has for the txtVendorFamilyNumber column the value 100110. Then the subsequent rows of results have the values 100115, 100120, 100130, et cetera, ending with the value 106370 in the last row of results.
I imported the SSIS package into Integration Services on SQL Server 2008 R2. When I imported to Integration Services, in the Import Package editor for the Protection Level I chose the "Rely on server storage and roles for access control" choice
because there are FTP Tasks and we needed to use this "Rely on server storage and roles for access control" choice.
I created a SQL Agent job that executes this SSIS package.
When I run the SQL Agent job, no error happens and I get only ONE email with the value 100110 for the vendor family number in it. I should get 379 emails total, the 2nd email showing 100115, the 3rd email showing 100120, et cetera.
When I was testing while executing the SSIS package from within Visual Studio, I did NOT have the Send Mail task and I only had enabled one Script Task that had the ReadOnly variable User::txtVendorFamilyNumber and the following lines of code:
MsgBox(CType(Dts.Variables("User::txtVendorFamilyNumber").Value, String))
Dts.TaskResult = ScriptResults.Success
Executing the SSIS package with only this Script Task enabled within the Foreach Loop Container, I would get the ONE message box showing 100110 but I would not get any message box for a SECOND ITERATION of the loop.
Since my txtVendorFamilyNumber in the Variables Pane has the default hard-coded value 111111 that does NOT exist in the result set of the Execute SQL Task that feeds the Foreach Loop, and since the first and only email sent shows the value 100110 when I
run the SQL Agent job that runs the SSIS package that is set up to send an email from within the Foreach Loop Container, the FIRST LOOP seems to run correctly and shows correctly the 1st value 100110 in the 379 rows of results that populate the Foreach Loop
Container. Why does the Foreach Loop Container NOT loop more than once?
Could anybody give me any suggestions as to what the problem might be?
I thank you in advance for your consideration of my problem. I have been reading and reading on the Internet to try to find a solution but I have not solved yet my problem with the Foreach loop only iterating once.
Thanks much to you.

Gregarious greetings Arthur,
I very much appreciate your reply.
This morning I figured out my problem with the help of a fellow employee.
In my original post higher up, I had typed about the SELECT statement in the Execute SQL Task that is just before the Foreach Loop Container and that populates the User::objRs, and this SELECT statement was in the old DTS package in an old ActiveX script
task. The SELECT statement was in an old DTS package in an old ActiveX script task and I am creating a new SSIS package to replace the old DTS package so that we can move from the old version of SQL Server to a new SQL Server 2008 R2 server. Here is that
SELECT statement:
select txtVendorFamilyNumber from tmpVendorFamily where VendorID = (select min(VendorID) from tmpVendorFamily)
That SELECT statement above returns ONLY ONE result. I had not noticed it. That SELECT statement fills the objRs result set. The green arrow goes from the Execute SQL Task that has the SELECT statement down to the Foreach Loop Container that loops over the
result set. Since the SELECT statement that fills the result set only has one row of results, the Foreach Loop only looped once.
So for the Execute SQL Task that populates the result set User::objRs, I changed the SELECT statement to be the following:
--In the Utilities DB, this tmpVendorFamily table
--has only two columns named VendorID and txtVendorFamilyNumber.
SELECT DISTINCT txtVendorFamilyNumber
FROM Utilities.dbo.tmpVendorFamily
ORDER BY txtVendorFamilyNumber
Now the Foreach Loop will loop 379 times since the SELECT statement immediately above yields 379 rows of results.
So the Foreach Loop Container was fine. Its Collection tab has the "Foreach ADO Enumerator" for the Enumerator and has the "User::objRs" for the ADO Object Source Variable. Its Variable Mappings tab has "User::txtVendorFamilyNumber"
for the Variable and has "0" for the Index.
My problem was the SELECT statement in the Execute SQL Task that immediately precedes the Foreach Loop Container and that fills the User::objRs result set. The SELECT statement yielded only ONE row of results. When I corrected this morning that SELECT statement
so that it correctly yields 379 rows of results, the Foreach Loop Container loops 379 rows.
Thanks again for replying and trying to help. I very much appreciate it.
I consider this thread that I created to be closed since I figured out this morning how I needed to correct the SELECT statement in the Execute SQL Task that fills the result set on which the Foreach Loop loops.
Misko_Hviezdoslav   27-JAN-2015

Magnetic lasso problems and pixels

When using the magnetic lasso and when I create circle around figure, it goes back to lasso and does not go around whole figure for me to move. Also every time I lasso something, the little ants are around it, but I keep getting a error message that it could not complete the copy command because no pixels selected.. Need to solve the problem with lasso, then problem with the error message for no pixels selected next. Would appreciate any help you could give me. I am running PSE13 on my PC.
Trying to cut figure out of one pic and placing in another pic or background.
Would also like to know why any picture I bring out of the photo bin to work on goes immediately to the background even if I got it locked and the oirginal backgroud picture disappears.
HELP!

I have done everything you said, completed my magnetic lasso around figure, as soon as I meet and click, the lasso disappears. Yesterday when I did it and little ants moving around and let go of my mouse it changed to plain lasso inside of picture of the person but was no way to the outside and ants were still running. This morning did as you said and still problem, I tried using a brush to circle it and the ants were running just like supposed to, but when I followed your instructions edit-copy, edit-paste, I still always get the message when I click copy----Could not complete copy command because no pixels are selected every time. I have connected the loop and the little ants are still running (probably getting their little feet tired by now) and still get that error as above. Can't seem to get past that copy stage, what am I doing wrong?????
Thanks for your help in advance.
      From: hatstead <[email protected]>
To: Les Buschow <[email protected]>
Sent: Tuesday, January 20, 2015 6:24 PM
Subject: Magnetic lasso problems and pixels
Magnetic lasso problems and pixels
created by hatstead in Photoshop Elements - View the full discussion
Mr. B's pics wrote: When using the magnetic lasso and when I create circle around figure, it goes back to lasso and does not go around whole figure for me to move.
You have to navigate completely around the object that you are selecting, so that you close the loop. You can backtrack as you go along with the delete key on the keyboard, and also set additional anchor points with a left click. I find it helpful to increase the contrast, if necessary, before starting with the tool.
  .Trying to cut figure out of one pic and placing in another pic or background.
Try this
   - Open picture B, the one you wish to select something from to add to another picture.
   - Use one of the selection tools, e.g. selection brush, lasso tool, to select the object. You will see an outline ("marching ants") once the selection is complete
   - Go to Edit menu>copy to copy the selection to the clipboard
   - Open picture A, then go to Edit>paste
   - Use the move tool to position object from picture B.
   - In the layers palette you should see picture A as the background layer, and object B on a separate layer.
If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7115641#7115641 and clicking ‘Correct’ below the answer Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7115641#7115641 To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following" Start a new discussion in Photoshop Elements by email or at Adobe Community For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.

Closed loop velocity control based on load cell force

Hello,
My application is for a drill, that drills into rocks of various densities for the purpose of collecting rock core samples.
My setup has 2 motors which get controlled, one spins the drill bit at a constant velocity, the other moves the drill mechanism along a Z axis.
For efficient cutting, it is desired to apply a constant force between the drill bit and the rock. I have a load cell which measures the force being exerted by the drill bit on the rock surface, and this force can be adjusted by changing the velocity of the Z axis. So I would like to employ closed loop control to adjust the Z axis velocity to maintain a constant force on the rock.
Platform: cRIO 9073, with NI 9505 & 9215 Modules, Labview 2010 Full with RT and FPGA modules.
The load cell is by Transducer Techniques, and I use their TMO-1 module to condition the signal, the output of which is attached to an input of the 9215 module, where 0-100 lbs equates to 0-8VDC.
The motors and encoders for the Drill and Z axis are connected directly to the 9505 modules.
Right now I am using a modified version the example found in ...\examples\CompactRIO\Module Specific\NI 9505\Velocity Control (closed loop)\Velocity Control (closed loop) - NI 9505.lvproj to accomplish velocity control of the motors.
My questions are:
1) Do I have the appropriate NI hardware/software for this task?
2) With my current hardware setup, what would be an appropriate way to control my Z axis velocity rate based on Analog feedback from the load cell?
3) Development time is a critical factor, so are there any toolkits etc that are easy to get started with that would drastically decrease my development time, or do I already have everything I need?
Thank you for your time
-MK Hokie

1. Your hardware and software look appropriate assuming the motors are compatible with the 9505s. You didn't mention the NI SoftMotion module in your software list which is something you will need.
2. There are a few ways of doing this. One method would be to have a force PID loop that would attempt to maintain a force setpoint by directly outputting values to your torque loop. In this case, the drill would essentially move as fast as it could while maintaining the force setpoint. Another option is to have the force loop output a velocity setpoint. You would then have a velocity PID loop that outputs torque values to the torque loop. By adding this additional velocity loop you could have control over your maximum and minimum velocities. There are likely other alternatives as well, but these are the first two that come to mind.
3. Unfortunately there are no shipping examples that close the loop on force feedback. My advice would be to start with the NI 9505 shipping example and adapt it to your needs. There are quite a few things you will want to change though. Do you know if you will need to use the trajectory generator to move the drill into position before starting the force control?
Assuming you don't need any trajectory generation, you can scrap the entire RT portion of the NI 9505 example and just create the necessary FPGA code. On the FPGA, you won't need the Spline or Synchronization code either because this information would no longer be coming from RT. You could take these out and replace the position loop with a force loop and possibly a velocity loop and your FPGA program would basically be finished. In fact the only real motion IP that you will need is for the encoders (assuming you want velocity control) and PID. Then you would need to create an RT VI that allows you to send down enable, disable, PID gains, and setpoints.
If you do need trajectory generation, you would want to keep most of the example code the way that it is, but then program in a 'Force Mode' that utilizes the force and velocity controly as described above. You could think of it as having two different routines programmed side by side.
Regards,
Burt S

Magnetic lasso - closed loop only?

Similar Messages

Maybe you are looking for