LabVIEW
please answer soon
Hi student without a name,
"it didn't work" is not a very good explanation of your problems!
What didn't work? Communication problems? Problems to get correct answers? Nanosteppers don't react?
"it didn't work" is not a very good explanation of your problems!
What didn't work? Communication problems? Problems to get correct answers? Nanosteppers don't react?
Hi student,
some more hints:
- try to use style guide: left-to-right wiring, no hidden wires
- try to use less sequences or (when really needed) use flat ones
I think, untitled.vi is your main vi (and there are a lot of missing subvis!). There's a while loop which could be your control loop. But in this loop no values are changed! So you initialize your stepper once before the loop and in the loop nothing happens...
Could you: save your main vi as "development distribution" (file-> save with options) to attach all subvis?
And please explain what exactly is broken!
some more hints:
- try to use style guide: left-to-right wiring, no hidden wires
- try to use less sequences or (when really needed) use flat ones
I think, untitled.vi is your main vi (and there are a lot of missing subvis!). There's a while loop which could be your control loop. But in this loop no values are changed! So you initialize your stepper once before the loop and in the loop nothing happens...
Could you: save your main vi as "development distribution" (file-> save with options) to attach all subvis?
And please explain what exactly is broken!
hi,
it dosent react!!I thought that my program has some problems because when I used another program that write with visual basic6 that has the same algorithm it works, it moves with constant velocity,forward and backward.
a attach another subvis that I used.
Najima
it dosent react!!I thought that my program has some problems because when I used another program that write with visual basic6 that has the same algorithm it works, it moves with constant velocity,forward and backward.
a attach another subvis that I used.
Najima
Hi student,
well from the vis I cannot tell what's wrong.
But I can give some more hints:
- in each subvi you use the same kind of read/write sequence. Why not make one subvi just for the read/write access with handing over all parameters? Then you also don't need this global variable for setting the mode of the GPIB access. I already demonstrated how to do this in the "U$.vi"...
- you set the timeout of the GPIB very often. This parameter only sets the time LabView will wait for any reaction of the device, it's not the time to wait for a (real) action! To set a value of 1000000 doesn't make sense (to me)...
- your "gear" vi didn't have any connectors, so I had to redo this part - maybe there is some error in it now...
- you should use the error cluster coming out of (nearly) every LabView function - they provide some information in case of communication problems!
Try to avoid unnecessary conversions, your "to double" is not needed here. But you better put in some type conversion for the timing functions! Everytime when there's a red dot at the input of a function LabView has to convert to a different datatype with possible (rounding) errors.
My main assumption is: you handle the timeout wrong and maybe there's a problem with wrong parameters for the wait functions.
Message Edited by GerdW on 11-20-2007 02:07 PM
well from the vis I cannot tell what's wrong.
But I can give some more hints:
- in each subvi you use the same kind of read/write sequence. Why not make one subvi just for the read/write access with handing over all parameters? Then you also don't need this global variable for setting the mode of the GPIB access. I already demonstrated how to do this in the "U$.vi"...
- you set the timeout of the GPIB very often. This parameter only sets the time LabView will wait for any reaction of the device, it's not the time to wait for a (real) action! To set a value of 1000000 doesn't make sense (to me)...
- your "gear" vi didn't have any connectors, so I had to redo this part - maybe there is some error in it now...
- you should use the error cluster coming out of (nearly) every LabView function - they provide some information in case of communication problems!
Try to avoid unnecessary conversions, your "to double" is not needed here. But you better put in some type conversion for the timing functions! Everytime when there's a red dot at the input of a function LabView has to convert to a different datatype with possible (rounding) errors.
My main assumption is: you handle the timeout wrong and maybe there's a problem with wrong parameters for the wait functions.
Message Edited by GerdW on 11-20-2007 02:07 PM
Hi Najima,
you can set the timeout globally using "Set Timeout" in the GPIB palette. Usually I set it to 3000ms which should be sufficient for all GPIB devices.
What do you mean by "convert my version of vis to another one"?
you can set the timeout globally using "Set Timeout" in the GPIB palette. Usually I set it to 3000ms which should be sufficient for all GPIB devices.
What do you mean by "convert my version of vis to another one"?
