08-26-2014 01:31 PM
@Blokk wrote:
Thanks, but the problem is that, the NI site only directs me to the Ametek site. Moreover, the Ametek site does not have VISA driver for the XG model (only C++ source code and the ActiveX approach). Anyway, as I wrote above, if I get error again with my modified ActiveX driver, I will try to use the SG model's VISA driver with some modifications, using the XG manual...
EDIT: by the way: I wonder why the Ametek/Sorensen does give VISA driver for the SGI model, but not for the XG model...?
Maybe the SGI was before Ametek bought out Sorensen, Ametek owns everything now...
Anyway I am sorry about that driver link, I did not bother to folllow it. But chances are the SGI and XG are pretty simmilar when it comes to SCPI programming. You will find most things are as SCPI was origonally intended to be a universial sort of programmign interface.
I just took a quick skim through the XG manual and the SCPI commands are in there.
08-26-2014 02:43 PM
hello,
Yep, that is going to be the plan B. Right now my program is running without error since Saturday. Hopefully the proper closing of all ref-nums had eliminated the error.
I leave it running for like 10 days, and if it is OK, I will stay at the "ActiveX approach". If not, I will go for the SCPI solution...
thanks for help!
08-31-2014 06:56 AM
@nyc_(is_out_of_here) wrote:
@Blokk wrote:
Actually I only see two references: "Outputs" and "System". The reference called "AmetekXGLib.IAmetekXG" comes in as an input tunnel, and also goes out as output tunnel as you see. When I call the "Sorensen_XG_psu.vi" in init mode, I get this ref, and afterward I just store it in a shiftregister as you see...
1.) IAmetekXGOutputs
2.) IAmetekXGOutputChannel
3.) IAmetekXGSystem
4.) IAmetekXG - which you are reusing via shift register
Unclosed references cause Excel to remain running in the background which is why I notice them.
Hello,
My application (including the modified subVI with close refs) is still running without any error since the previous Saturday, so most probably the unclosed references caused the problem before. When I probed the ref outputs, they changed at every iteration, so I guess I just made a nice memory leak there. So I marked the above post as a solution.
Thanks guys for the help!
Best Regards,
08-31-2014 11:04 AM - edited 08-31-2014 11:05 AM
@Blokk wrote:
hello,
Yep, that is going to be the plan B. Right now my program is running without error since Saturday. Hopefully the proper closing of all ref-nums had eliminated the error.
I leave it running for like 10 days, and if it is OK, I will stay at the "ActiveX approach". If not, I will go for the SCPI solution...
thanks for help!
WHOAH! Let us try to unconfuse ourselves here! Either way you are going to use "SCPI" SCPI is not a means to communicate between applications (ActiveX is) but, a standard to format comand structures for instrument control.
08-31-2014 11:07 AM
08-31-2014 11:11 AM
@Blokk wrote:
Is that correct, if i say: using VISA with SCPI commands?
Not to worry. I knew what you meant. 🙂
I am glad that closing the references was the key. Less work for you. 😉
08-31-2014 11:58 AM
@Blokk wrote:
Is that correct, if i say: using VISA with SCPI commands?
No. SCPI is a agreed upon way to format strings that are used to command the conditions of instruments.
VISA... Abstracts the lower layers of the communication between devices.
08-31-2014 03:20 PM
@JÞB wrote:
@Blokk wrote:
Is that correct, if i say: using VISA with SCPI commands?No. SCPI is a agreed upon way to format strings that are used to command the conditions of instruments.
VISA... Abstracts the lower layers of the communication between devices.
Instead of just correcting him, please then tell him the correct answer.
08-31-2014 04:26 PM
@nyc_(is_out_of_here) wrote:
@JÞB wrote:
@Blokk wrote:
Is that correct, if i say: using VISA with SCPI commands?No. SCPI is a agreed upon way to format strings that are used to command the conditions of instruments.
VISA... Abstracts the lower layers of the communication between devices.
Instead of just correcting him, please then tell him the correct answer.
I would--- but I am unable to see into the OP's head and the 8-Ball I rely on for these occasions is getting a pedicure
I can try to ask leading questions though (TY nyc)
VISA is a standaradized method of comunications over multiple physical layers. SCPI, is a packaging layer helping use treat instrumwnts that can do things similar like each other .
SCPI helps format the data.
VISA Helps move data.
Untill I see something (Like code) I cannot "just give" a solution....I am confused by what the OP misunderstands.
08-31-2014 07:31 PM - edited 08-31-2014 07:33 PM
@JÞB wrote:
@nyc_(is_out_of_here) wrote:
@JÞB wrote:
@Blokk wrote:
Is that correct, if i say: using VISA with SCPI commands?No. SCPI is a agreed upon way to format strings that are used to command the conditions of instruments.
VISA... Abstracts the lower layers of the communication between devices.
Instead of just correcting him, please then tell him the correct answer.
I would--- but I am unable to see into the OP's head and the 8-Ball I rely on for these occasions is getting a pedicure
I can try to ask leading questions though (TY nyc)
VISA is a standaradized method of comunications over multiple physical layers. SCPI, is a packaging layer helping use treat instrumwnts that can do things similar like each other .
SCPI helps format the data.
VISA Helps move data.
Untill I see something (Like code) I cannot "just give" a solution....I am confused by what the OP misunderstands.
Wow, Jeff.
I am totally surprised by your confusion. Have you read the entire thread?
And the OP found a solution. So I am not understanding what you referring to by "just give" a solution.
I am asking you that since you wrote no to the OP's sentence using VISA with SCPI commands, then what should it be?
If you write no, then what should the "yes" sentence be?
What is the better terminology for the action of sending SCPI commands while using LabVIEW's VISA functions?